GUI won't boot after package update: Restoring Resolver State [closed]
Linux Mint Rosa dual boot with windows 10
Nvidia GTX 870M
Suddenly can't get to Linux Mint gui after running a package update to upgrade python. Everytime I login it kicks me back out. flashing this message quickly in the screen
speech dispatcher disabled; edit /etc/default/speech-dispatcher
saned disabled: edit /etc/default/saned
restoring resolver state
it does not (freeze) as in the majority of other posts with this message it flashes and kicks me back to the login. There is another message that flashes very quickly after I pick an OS from grub but it is so fast it cannot be caught even with a camera. I can however get in through command line
Output from xsession-error
[![enter image description here][1]][1]
Stuff I've tried
- running endless varients of package repair and package install command lines
- installing and uninstalling virtualbox, virtualbox-dkms etc
2b: going down a rabbithole trying to get virtualbox-dkms to build and to get an outside version of virtualbox on the system - creating a test account to try to login
- logging in with all the older kernels avaliable under the grub menu.
- logging into the commandline and then trying startx or start mdm (startx brings me to a black screen with a mouse pointer)
- Removing nvidia
EDIT: I ended up settling on the workaround of installing xfce over it and so far it seems to have worked. I still have no idea what the problem was and things might be out of place here or there but is a lot better than nothing.
[1]https://i.stack.imgur.com/kbgFF.jpg
linux-mint kernel gui graphics
edited Dec 20 '18 at 6:37
Rui F Ribeiro
39k1479130
asked Dec 20 '18 at 1:34
A D
113
closed as off-topic by Rui F Ribeiro, JigglyNaga, schily, Jeff Schaller, Mr Shunz Dec 20 '18 at 15:56
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – Rui F Ribeiro, JigglyNaga, schily, Jeff Schaller, Mr Shunz
If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
Linux Mint Rosa dual boot with windows 10
Nvidia GTX 870M
Suddenly can't get to Linux Mint gui after running a package update to upgrade python. Everytime I login it kicks me back out. flashing this message quickly in the screen
speech dispatcher disabled; edit /etc/default/speech-dispatcher
saned disabled: edit /etc/default/saned
restoring resolver state
it does not (freeze) as in the majority of other posts with this message it flashes and kicks me back to the login. There is another message that flashes very quickly after I pick an OS from grub but it is so fast it cannot be caught even with a camera. I can however get in through command line
Output from xsession-error
[![enter image description here][1]][1]
Stuff I've tried
- running endless varients of package repair and package install command lines
- installing and uninstalling virtualbox, virtualbox-dkms etc
2b: going down a rabbithole trying to get virtualbox-dkms to build and to get an outside version of virtualbox on the system - creating a test account to try to login
- logging in with all the older kernels avaliable under the grub menu.
- logging into the commandline and then trying startx or start mdm (startx brings me to a black screen with a mouse pointer)
- Removing nvidia
EDIT: I ended up settling on the workaround of installing xfce over it and so far it seems to have worked. I still have no idea what the problem was and things might be out of place here or there but is a lot better than nothing.
[1]https://i.stack.imgur.com/kbgFF.jpg
linux-mint kernel gui graphics
edited Dec 20 '18 at 6:37
Rui F Ribeiro
39k1479130
asked Dec 20 '18 at 1:34
A D
113
closed as off-topic by Rui F Ribeiro, JigglyNaga, schily, Jeff Schaller, Mr Shunz Dec 20 '18 at 15:56
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – Rui F Ribeiro, JigglyNaga, schily, Jeff Schaller, Mr Shunz
If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
Linux Mint Rosa dual boot with windows 10
Nvidia GTX 870M
Suddenly can't get to Linux Mint gui after running a package update to upgrade python. Everytime I login it kicks me back out. flashing this message quickly in the screen
speech dispatcher disabled; edit /etc/default/speech-dispatcher
saned disabled: edit /etc/default/saned
restoring resolver state
it does not (freeze) as in the majority of other posts with this message it flashes and kicks me back to the login. There is another message that flashes very quickly after I pick an OS from grub but it is so fast it cannot be caught even with a camera. I can however get in through command line
Output from xsession-error
[![enter image description here][1]][1]
Stuff I've tried
- running endless varients of package repair and package install command lines
- installing and uninstalling virtualbox, virtualbox-dkms etc
2b: going down a rabbithole trying to get virtualbox-dkms to build and to get an outside version of virtualbox on the system - creating a test account to try to login
- logging in with all the older kernels avaliable under the grub menu.
- logging into the commandline and then trying startx or start mdm (startx brings me to a black screen with a mouse pointer)
- Removing nvidia
EDIT: I ended up settling on the workaround of installing xfce over it and so far it seems to have worked. I still have no idea what the problem was and things might be out of place here or there but is a lot better than nothing.
[1]https://i.stack.imgur.com/kbgFF.jpg
linux-mint kernel gui graphics
edited Dec 20 '18 at 6:37
Rui F Ribeiro
39k1479130
asked Dec 20 '18 at 1:34
A D
113
Linux Mint Rosa dual boot with windows 10
Nvidia GTX 870M
Suddenly can't get to Linux Mint gui after running a package update to upgrade python. Everytime I login it kicks me back out. flashing this message quickly in the screen
speech dispatcher disabled; edit /etc/default/speech-dispatcher
saned disabled: edit /etc/default/saned
restoring resolver state
it does not (freeze) as in the majority of other posts with this message it flashes and kicks me back to the login. There is another message that flashes very quickly after I pick an OS from grub but it is so fast it cannot be caught even with a camera. I can however get in through command line
Output from xsession-error
[![enter image description here][1]][1]
Stuff I've tried
- running endless varients of package repair and package install command lines
- installing and uninstalling virtualbox, virtualbox-dkms etc
2b: going down a rabbithole trying to get virtualbox-dkms to build and to get an outside version of virtualbox on the system - creating a test account to try to login
- logging in with all the older kernels avaliable under the grub menu.
- logging into the commandline and then trying startx or start mdm (startx brings me to a black screen with a mouse pointer)
- Removing nvidia
EDIT: I ended up settling on the workaround of installing xfce over it and so far it seems to have worked. I still have no idea what the problem was and things might be out of place here or there but is a lot better than nothing.
[1]https://i.stack.imgur.com/kbgFF.jpg
linux-mint kernel gui graphics
linux-mint kernel gui graphics
edited Dec 20 '18 at 6:37
Rui F Ribeiro
39k1479130
asked Dec 20 '18 at 1:34
A D
113
edited Dec 20 '18 at 6:37
Rui F Ribeiro
39k1479130
asked Dec 20 '18 at 1:34
A D
113
edited Dec 20 '18 at 6:37
Rui F Ribeiro
39k1479130
edited Dec 20 '18 at 6:37
Rui F Ribeiro
39k1479130
edited Dec 20 '18 at 6:37
Rui F Ribeiro
39k1479130
39k1479130
asked Dec 20 '18 at 1:34
A D
113
asked Dec 20 '18 at 1:34
A D
113
asked Dec 20 '18 at 1:34
A D
113
113
closed as off-topic by Rui F Ribeiro, JigglyNaga, schily, Jeff Schaller, Mr Shunz Dec 20 '18 at 15:56
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – Rui F Ribeiro, JigglyNaga, schily, Jeff Schaller, Mr Shunz
If this question can be reworded to fit the rules in the help center, please edit the question.
closed as off-topic by Rui F Ribeiro, JigglyNaga, schily, Jeff Schaller, Mr Shunz Dec 20 '18 at 15:56
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – Rui F Ribeiro, JigglyNaga, schily, Jeff Schaller, Mr Shunz
If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
