Ubuntu doesn't start, with a message 'Started GNOME Display Manager. Dispatcher Service… system changes.pp link was shut down'Ubuntu gets stuck in a login loopGDM3 does not start in Ubuntu 18.04Issue with Ethernet dropping Connection Irregularly Ubuntu-BudgieUbuntu Grub Screen Problems13.10 Saucy login issues since update from 13.04 - boots in to text modeUbuntu not booting properly with GTX 970Ubuntu won't boot ufter upgrade to 15.04, stuck on gnome display managerUbuntu gives a purple screen while bootingUbuntu login screen won't let me log inupdated to 18.04, no login screenStarted GNOME Display Manager Issue on Ubuntu 18.04.02
What determines the time factor in a court reaching a decision?
Am I being run backwards?
Equality operator does not get defined for a custom spaceship operator implementation in C++20
The Extended Participial Phrase
Average Two Letters
Getting data from Seagate ST-238R drive
Should I report a security vulnerability?
How did Krennic locate the Erso family's hideout?
How much energy does a bee/micro robot need per second of flight?
Why do Muslim refugees seek asylum in Europe and not in rich countries in the Middle East?
Is energy more fundamental than force?
Making sense of possessed dolls: how could they actually kill people?
How to implement bus sharing / DMA on a 6502 system
Horizontally mirror a brainflak program
My boss wants me to recreate everything I have done for my previous employer
Why do airline tickets have titles in addition to names?
Cases bugged - lines overlapping
Can a professor do an internship?
Really bizarre dystopian children’s film with hundreds of young boys forced to play piano
Space complexity for storing integers in Python
Jazz Chords: How can a Bbmaj9 be explained in the key of A major?
Counterpart of cyclotomic polynomials for elliptic divisibility sequences
Origin of 〜かった?
Having trouble understanding condition for Rolle's Theorem (russian translation)
Ubuntu doesn't start, with a message 'Started GNOME Display Manager. Dispatcher Service… system changes.pp link was shut down'
Ubuntu gets stuck in a login loopGDM3 does not start in Ubuntu 18.04Issue with Ethernet dropping Connection Irregularly Ubuntu-BudgieUbuntu Grub Screen Problems13.10 Saucy login issues since update from 13.04 - boots in to text modeUbuntu not booting properly with GTX 970Ubuntu won't boot ufter upgrade to 15.04, stuck on gnome display managerUbuntu gives a purple screen while bootingUbuntu login screen won't let me log inupdated to 18.04, no login screenStarted GNOME Display Manager Issue on Ubuntu 18.04.02
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;
For some reason, Ubuntu 18.04 refuses to start. It has worked previously - with some minor problems related to my Nvidia GPU drivers (which I fixed by going nomodeset and installing proprietary drivers), and later some problems with Ethernet connection (which I solved using these solutions: Issue with Ethernet dropping Connection Irregularly Ubuntu-Budgie and https://ubuntu-mate.community/t/stop-network-disconnecting-in-ubuntu/829 - I used both and I'm not sure which one was the one that worked).
I haven't messed with system or system files in any way last time I turned Ubuntu on.
Currently, after the Ubuntu logo splash loading screen, the screen (filled with text) starts to flicker at regular intervals, showing these messages on screen with no change (it took like 5 minutes to take these photos because they only flicker on for a short time, then they disappear for a couple seconds, then reappear again - etc).
In recovery mode menu I tried option to "repair broken packages" - it seemingly succeeded but it didn't help at all, now different messages flicker with no change in behavior.
Here are the images: https://imgur.com/a/VU4jD4e 1-3 are the images at first, II1 - II3 are after Repair Packages attempt. If they're identical (I think they might be but I'm not sure) then I guess you have two versions of the images?
Using recovery mode simply nets "out of range/60khz" error on my display, and nomodeset does nothing, it still results in flickering text. Yesterday (last time I used Ubuntu) everything was OK.
My computer specs are:
CPU: Intel Xeon E3120 3.16 GHz
RAM: 4GB
GPU: Nvidia Quadro NVS 290
HDD: 2TB, split into two partitions (1TB Windows 10 and 1TB Ubuntu 18.04)
I'm using an external sound card, as this system (made to be a server) lacks one by default.
I'm posting this from Windows 10 on the same computer which seems unaffected (similarly GRUB works perfectly fine), so I doubt it's a hardware issue.
EDIT: Full text of the final line of text:
EDIT 2: I left it running for 40 minutes now, and it doesn't seem to start. Still, I will leave it running overnight. Also the screen now looks like that:
https://imgur.com/a/zhoq0Uk
EDIT 3: I tried logging into text mode by replacing "quiet splash" with "text". To my surprise it did the same thing - flickering text - though with a different message:
Interestingly, when I pressed Ctrl+Alt+F3, I was shown a text login screen, but after about 5 seconds it vanished and the screen started flickering again.
As for this question being a duplicate - switching the display manager to lightdm from the root shell (in recovery mode menu) seemed partially successful - I now see the login screen, but Ubuntu refuses to accept my login, as trying to login using a correct password simply causes the screen to go black, and then I'm dumped back to the login screen.
However, I can press Ctrl+Alt+F3 from HERE, and this console, unlike the GUI lightdm login screen, accepts my login for some reason.
This allowed me to attempt every solution presented in GDM3 does not start in Ubuntu 18.04 - and none of them do anything - the Wayland thing, Slim solution, gnome-desktop - none of them. I tried installing and switching to Slim, but does basically the same thing as LightDM - when I type in my username and password, I get an error saying failed to execute login command
, black screen, and login screen restarts. And just like with LightDM, I can use Ctrl+Alt+F3 to log into text mode.
Also I tried to get to /var/log
and look at logs using less
, but I can't notice any obvious errors - at least no lines claiming 'error'. It would definitely help if I was able to somehow copy those files to my Windows partition and share their content here - I guess I will look into that tomorrow.
EDIT 4: When rereading Xorg.1.log, I noticed some errors - it appears that there is a bunch of errors involving "Wacom Bamboo PT" - invalid type 'cursor for this device
and similar stuff (in addition to cursor there was lasso touch, pad, stylus, eraser...). However, I'm not sure if that could be the issue as this problem occurs regardless of whether my Wacom tablet was plugged in or not.
However, later down the line I found more errors: client bug: timer event8 debounce: offset negative
- that line was repeated over and over, followed by bracketed values: (-6ms), (-21ms), timer event8 debounce short offset negative (-77ms)
, (-14ms), (-26ms), (-32ms) and timer event8 debounce short offset negative (-46ms)
However, there was no such error in Xorg.0.log
boot dual-boot 18.04
|
show 5 more comments
For some reason, Ubuntu 18.04 refuses to start. It has worked previously - with some minor problems related to my Nvidia GPU drivers (which I fixed by going nomodeset and installing proprietary drivers), and later some problems with Ethernet connection (which I solved using these solutions: Issue with Ethernet dropping Connection Irregularly Ubuntu-Budgie and https://ubuntu-mate.community/t/stop-network-disconnecting-in-ubuntu/829 - I used both and I'm not sure which one was the one that worked).
I haven't messed with system or system files in any way last time I turned Ubuntu on.
Currently, after the Ubuntu logo splash loading screen, the screen (filled with text) starts to flicker at regular intervals, showing these messages on screen with no change (it took like 5 minutes to take these photos because they only flicker on for a short time, then they disappear for a couple seconds, then reappear again - etc).
In recovery mode menu I tried option to "repair broken packages" - it seemingly succeeded but it didn't help at all, now different messages flicker with no change in behavior.
Here are the images: https://imgur.com/a/VU4jD4e 1-3 are the images at first, II1 - II3 are after Repair Packages attempt. If they're identical (I think they might be but I'm not sure) then I guess you have two versions of the images?
Using recovery mode simply nets "out of range/60khz" error on my display, and nomodeset does nothing, it still results in flickering text. Yesterday (last time I used Ubuntu) everything was OK.
My computer specs are:
CPU: Intel Xeon E3120 3.16 GHz
RAM: 4GB
GPU: Nvidia Quadro NVS 290
HDD: 2TB, split into two partitions (1TB Windows 10 and 1TB Ubuntu 18.04)
I'm using an external sound card, as this system (made to be a server) lacks one by default.
I'm posting this from Windows 10 on the same computer which seems unaffected (similarly GRUB works perfectly fine), so I doubt it's a hardware issue.
EDIT: Full text of the final line of text:
EDIT 2: I left it running for 40 minutes now, and it doesn't seem to start. Still, I will leave it running overnight. Also the screen now looks like that:
https://imgur.com/a/zhoq0Uk
EDIT 3: I tried logging into text mode by replacing "quiet splash" with "text". To my surprise it did the same thing - flickering text - though with a different message:
Interestingly, when I pressed Ctrl+Alt+F3, I was shown a text login screen, but after about 5 seconds it vanished and the screen started flickering again.
As for this question being a duplicate - switching the display manager to lightdm from the root shell (in recovery mode menu) seemed partially successful - I now see the login screen, but Ubuntu refuses to accept my login, as trying to login using a correct password simply causes the screen to go black, and then I'm dumped back to the login screen.
However, I can press Ctrl+Alt+F3 from HERE, and this console, unlike the GUI lightdm login screen, accepts my login for some reason.
This allowed me to attempt every solution presented in GDM3 does not start in Ubuntu 18.04 - and none of them do anything - the Wayland thing, Slim solution, gnome-desktop - none of them. I tried installing and switching to Slim, but does basically the same thing as LightDM - when I type in my username and password, I get an error saying failed to execute login command
, black screen, and login screen restarts. And just like with LightDM, I can use Ctrl+Alt+F3 to log into text mode.
Also I tried to get to /var/log
and look at logs using less
, but I can't notice any obvious errors - at least no lines claiming 'error'. It would definitely help if I was able to somehow copy those files to my Windows partition and share their content here - I guess I will look into that tomorrow.
EDIT 4: When rereading Xorg.1.log, I noticed some errors - it appears that there is a bunch of errors involving "Wacom Bamboo PT" - invalid type 'cursor for this device
and similar stuff (in addition to cursor there was lasso touch, pad, stylus, eraser...). However, I'm not sure if that could be the issue as this problem occurs regardless of whether my Wacom tablet was plugged in or not.
However, later down the line I found more errors: client bug: timer event8 debounce: offset negative
- that line was repeated over and over, followed by bracketed values: (-6ms), (-21ms), timer event8 debounce short offset negative (-77ms)
, (-14ms), (-26ms), (-32ms) and timer event8 debounce short offset negative (-46ms)
However, there was no such error in Xorg.0.log
boot dual-boot 18.04
Could you provide more information about what happened between the last time it booted successfully and now? What changed? As a first step, allow the machine time to boot. The last screen cap shows that the display manager is up and running, so the login screen should be coming up. Then see this link to resolve the network interfaces issue.
– Karthik
Aug 5 at 17:47
I guess the problem you are seeing is that the display manager tries to start, fails, tries to start again, fails, etc. So your screen is switching between text mode and graphics mode all the time, that why the flickering. If you can then try to ssh into the machine and thencd /var/log
. See which log files were updated most recently:ls -latr
. Then have a look at those files:less some_log_file
("q" will terminate the pager). You'll probably find the error in theXorg.0.log
if you have that on your system.
– Tomáš Pospíšek
Aug 5 at 17:55
Like I said, I don't believe anything has changed whatsoever. All I did in the last session was watch some Youtube videos using Firefox, and changed the screen sleep setting from 5 minutes of inactivity to 15 minutes. But thanks, I will try that.
– shinobody
Aug 5 at 18:31
"If you can then try to ssh into the machine" i have no idea what that means. Looking it up nets this article: linuxize.com/post/how-to-enable-ssh-on-ubuntu-18-04 - which is definitely impossible, I can't log in to install it, nor do I have any idea how to set up a LAN or how to find out IP of the problematic machine (I'm pretty sure I have dynamic IP).
– shinobody
Aug 5 at 19:05
1
Possible duplicate of GDM3 does not start in Ubuntu 18.04
– Gunnar Hjalmarsson
Aug 5 at 19:51
|
show 5 more comments
For some reason, Ubuntu 18.04 refuses to start. It has worked previously - with some minor problems related to my Nvidia GPU drivers (which I fixed by going nomodeset and installing proprietary drivers), and later some problems with Ethernet connection (which I solved using these solutions: Issue with Ethernet dropping Connection Irregularly Ubuntu-Budgie and https://ubuntu-mate.community/t/stop-network-disconnecting-in-ubuntu/829 - I used both and I'm not sure which one was the one that worked).
I haven't messed with system or system files in any way last time I turned Ubuntu on.
Currently, after the Ubuntu logo splash loading screen, the screen (filled with text) starts to flicker at regular intervals, showing these messages on screen with no change (it took like 5 minutes to take these photos because they only flicker on for a short time, then they disappear for a couple seconds, then reappear again - etc).
In recovery mode menu I tried option to "repair broken packages" - it seemingly succeeded but it didn't help at all, now different messages flicker with no change in behavior.
Here are the images: https://imgur.com/a/VU4jD4e 1-3 are the images at first, II1 - II3 are after Repair Packages attempt. If they're identical (I think they might be but I'm not sure) then I guess you have two versions of the images?
Using recovery mode simply nets "out of range/60khz" error on my display, and nomodeset does nothing, it still results in flickering text. Yesterday (last time I used Ubuntu) everything was OK.
My computer specs are:
CPU: Intel Xeon E3120 3.16 GHz
RAM: 4GB
GPU: Nvidia Quadro NVS 290
HDD: 2TB, split into two partitions (1TB Windows 10 and 1TB Ubuntu 18.04)
I'm using an external sound card, as this system (made to be a server) lacks one by default.
I'm posting this from Windows 10 on the same computer which seems unaffected (similarly GRUB works perfectly fine), so I doubt it's a hardware issue.
EDIT: Full text of the final line of text:
EDIT 2: I left it running for 40 minutes now, and it doesn't seem to start. Still, I will leave it running overnight. Also the screen now looks like that:
https://imgur.com/a/zhoq0Uk
EDIT 3: I tried logging into text mode by replacing "quiet splash" with "text". To my surprise it did the same thing - flickering text - though with a different message:
Interestingly, when I pressed Ctrl+Alt+F3, I was shown a text login screen, but after about 5 seconds it vanished and the screen started flickering again.
As for this question being a duplicate - switching the display manager to lightdm from the root shell (in recovery mode menu) seemed partially successful - I now see the login screen, but Ubuntu refuses to accept my login, as trying to login using a correct password simply causes the screen to go black, and then I'm dumped back to the login screen.
However, I can press Ctrl+Alt+F3 from HERE, and this console, unlike the GUI lightdm login screen, accepts my login for some reason.
This allowed me to attempt every solution presented in GDM3 does not start in Ubuntu 18.04 - and none of them do anything - the Wayland thing, Slim solution, gnome-desktop - none of them. I tried installing and switching to Slim, but does basically the same thing as LightDM - when I type in my username and password, I get an error saying failed to execute login command
, black screen, and login screen restarts. And just like with LightDM, I can use Ctrl+Alt+F3 to log into text mode.
Also I tried to get to /var/log
and look at logs using less
, but I can't notice any obvious errors - at least no lines claiming 'error'. It would definitely help if I was able to somehow copy those files to my Windows partition and share their content here - I guess I will look into that tomorrow.
EDIT 4: When rereading Xorg.1.log, I noticed some errors - it appears that there is a bunch of errors involving "Wacom Bamboo PT" - invalid type 'cursor for this device
and similar stuff (in addition to cursor there was lasso touch, pad, stylus, eraser...). However, I'm not sure if that could be the issue as this problem occurs regardless of whether my Wacom tablet was plugged in or not.
However, later down the line I found more errors: client bug: timer event8 debounce: offset negative
- that line was repeated over and over, followed by bracketed values: (-6ms), (-21ms), timer event8 debounce short offset negative (-77ms)
, (-14ms), (-26ms), (-32ms) and timer event8 debounce short offset negative (-46ms)
However, there was no such error in Xorg.0.log
boot dual-boot 18.04
For some reason, Ubuntu 18.04 refuses to start. It has worked previously - with some minor problems related to my Nvidia GPU drivers (which I fixed by going nomodeset and installing proprietary drivers), and later some problems with Ethernet connection (which I solved using these solutions: Issue with Ethernet dropping Connection Irregularly Ubuntu-Budgie and https://ubuntu-mate.community/t/stop-network-disconnecting-in-ubuntu/829 - I used both and I'm not sure which one was the one that worked).
I haven't messed with system or system files in any way last time I turned Ubuntu on.
Currently, after the Ubuntu logo splash loading screen, the screen (filled with text) starts to flicker at regular intervals, showing these messages on screen with no change (it took like 5 minutes to take these photos because they only flicker on for a short time, then they disappear for a couple seconds, then reappear again - etc).
In recovery mode menu I tried option to "repair broken packages" - it seemingly succeeded but it didn't help at all, now different messages flicker with no change in behavior.
Here are the images: https://imgur.com/a/VU4jD4e 1-3 are the images at first, II1 - II3 are after Repair Packages attempt. If they're identical (I think they might be but I'm not sure) then I guess you have two versions of the images?
Using recovery mode simply nets "out of range/60khz" error on my display, and nomodeset does nothing, it still results in flickering text. Yesterday (last time I used Ubuntu) everything was OK.
My computer specs are:
CPU: Intel Xeon E3120 3.16 GHz
RAM: 4GB
GPU: Nvidia Quadro NVS 290
HDD: 2TB, split into two partitions (1TB Windows 10 and 1TB Ubuntu 18.04)
I'm using an external sound card, as this system (made to be a server) lacks one by default.
I'm posting this from Windows 10 on the same computer which seems unaffected (similarly GRUB works perfectly fine), so I doubt it's a hardware issue.
EDIT: Full text of the final line of text:
EDIT 2: I left it running for 40 minutes now, and it doesn't seem to start. Still, I will leave it running overnight. Also the screen now looks like that:
https://imgur.com/a/zhoq0Uk
EDIT 3: I tried logging into text mode by replacing "quiet splash" with "text". To my surprise it did the same thing - flickering text - though with a different message:
Interestingly, when I pressed Ctrl+Alt+F3, I was shown a text login screen, but after about 5 seconds it vanished and the screen started flickering again.
As for this question being a duplicate - switching the display manager to lightdm from the root shell (in recovery mode menu) seemed partially successful - I now see the login screen, but Ubuntu refuses to accept my login, as trying to login using a correct password simply causes the screen to go black, and then I'm dumped back to the login screen.
However, I can press Ctrl+Alt+F3 from HERE, and this console, unlike the GUI lightdm login screen, accepts my login for some reason.
This allowed me to attempt every solution presented in GDM3 does not start in Ubuntu 18.04 - and none of them do anything - the Wayland thing, Slim solution, gnome-desktop - none of them. I tried installing and switching to Slim, but does basically the same thing as LightDM - when I type in my username and password, I get an error saying failed to execute login command
, black screen, and login screen restarts. And just like with LightDM, I can use Ctrl+Alt+F3 to log into text mode.
Also I tried to get to /var/log
and look at logs using less
, but I can't notice any obvious errors - at least no lines claiming 'error'. It would definitely help if I was able to somehow copy those files to my Windows partition and share their content here - I guess I will look into that tomorrow.
EDIT 4: When rereading Xorg.1.log, I noticed some errors - it appears that there is a bunch of errors involving "Wacom Bamboo PT" - invalid type 'cursor for this device
and similar stuff (in addition to cursor there was lasso touch, pad, stylus, eraser...). However, I'm not sure if that could be the issue as this problem occurs regardless of whether my Wacom tablet was plugged in or not.
However, later down the line I found more errors: client bug: timer event8 debounce: offset negative
- that line was repeated over and over, followed by bracketed values: (-6ms), (-21ms), timer event8 debounce short offset negative (-77ms)
, (-14ms), (-26ms), (-32ms) and timer event8 debounce short offset negative (-46ms)
However, there was no such error in Xorg.0.log
boot dual-boot 18.04
boot dual-boot 18.04
edited Aug 6 at 4:13
karel
70.1k15 gold badges158 silver badges184 bronze badges
70.1k15 gold badges158 silver badges184 bronze badges
asked Aug 5 at 16:35
shinobodyshinobody
639 bronze badges
639 bronze badges
Could you provide more information about what happened between the last time it booted successfully and now? What changed? As a first step, allow the machine time to boot. The last screen cap shows that the display manager is up and running, so the login screen should be coming up. Then see this link to resolve the network interfaces issue.
– Karthik
Aug 5 at 17:47
I guess the problem you are seeing is that the display manager tries to start, fails, tries to start again, fails, etc. So your screen is switching between text mode and graphics mode all the time, that why the flickering. If you can then try to ssh into the machine and thencd /var/log
. See which log files were updated most recently:ls -latr
. Then have a look at those files:less some_log_file
("q" will terminate the pager). You'll probably find the error in theXorg.0.log
if you have that on your system.
– Tomáš Pospíšek
Aug 5 at 17:55
Like I said, I don't believe anything has changed whatsoever. All I did in the last session was watch some Youtube videos using Firefox, and changed the screen sleep setting from 5 minutes of inactivity to 15 minutes. But thanks, I will try that.
– shinobody
Aug 5 at 18:31
"If you can then try to ssh into the machine" i have no idea what that means. Looking it up nets this article: linuxize.com/post/how-to-enable-ssh-on-ubuntu-18-04 - which is definitely impossible, I can't log in to install it, nor do I have any idea how to set up a LAN or how to find out IP of the problematic machine (I'm pretty sure I have dynamic IP).
– shinobody
Aug 5 at 19:05
1
Possible duplicate of GDM3 does not start in Ubuntu 18.04
– Gunnar Hjalmarsson
Aug 5 at 19:51
|
show 5 more comments
Could you provide more information about what happened between the last time it booted successfully and now? What changed? As a first step, allow the machine time to boot. The last screen cap shows that the display manager is up and running, so the login screen should be coming up. Then see this link to resolve the network interfaces issue.
– Karthik
Aug 5 at 17:47
I guess the problem you are seeing is that the display manager tries to start, fails, tries to start again, fails, etc. So your screen is switching between text mode and graphics mode all the time, that why the flickering. If you can then try to ssh into the machine and thencd /var/log
. See which log files were updated most recently:ls -latr
. Then have a look at those files:less some_log_file
("q" will terminate the pager). You'll probably find the error in theXorg.0.log
if you have that on your system.
– Tomáš Pospíšek
Aug 5 at 17:55
Like I said, I don't believe anything has changed whatsoever. All I did in the last session was watch some Youtube videos using Firefox, and changed the screen sleep setting from 5 minutes of inactivity to 15 minutes. But thanks, I will try that.
– shinobody
Aug 5 at 18:31
"If you can then try to ssh into the machine" i have no idea what that means. Looking it up nets this article: linuxize.com/post/how-to-enable-ssh-on-ubuntu-18-04 - which is definitely impossible, I can't log in to install it, nor do I have any idea how to set up a LAN or how to find out IP of the problematic machine (I'm pretty sure I have dynamic IP).
– shinobody
Aug 5 at 19:05
1
Possible duplicate of GDM3 does not start in Ubuntu 18.04
– Gunnar Hjalmarsson
Aug 5 at 19:51
Could you provide more information about what happened between the last time it booted successfully and now? What changed? As a first step, allow the machine time to boot. The last screen cap shows that the display manager is up and running, so the login screen should be coming up. Then see this link to resolve the network interfaces issue.
– Karthik
Aug 5 at 17:47
Could you provide more information about what happened between the last time it booted successfully and now? What changed? As a first step, allow the machine time to boot. The last screen cap shows that the display manager is up and running, so the login screen should be coming up. Then see this link to resolve the network interfaces issue.
– Karthik
Aug 5 at 17:47
I guess the problem you are seeing is that the display manager tries to start, fails, tries to start again, fails, etc. So your screen is switching between text mode and graphics mode all the time, that why the flickering. If you can then try to ssh into the machine and then
cd /var/log
. See which log files were updated most recently: ls -latr
. Then have a look at those files: less some_log_file
("q" will terminate the pager). You'll probably find the error in the Xorg.0.log
if you have that on your system.– Tomáš Pospíšek
Aug 5 at 17:55
I guess the problem you are seeing is that the display manager tries to start, fails, tries to start again, fails, etc. So your screen is switching between text mode and graphics mode all the time, that why the flickering. If you can then try to ssh into the machine and then
cd /var/log
. See which log files were updated most recently: ls -latr
. Then have a look at those files: less some_log_file
("q" will terminate the pager). You'll probably find the error in the Xorg.0.log
if you have that on your system.– Tomáš Pospíšek
Aug 5 at 17:55
Like I said, I don't believe anything has changed whatsoever. All I did in the last session was watch some Youtube videos using Firefox, and changed the screen sleep setting from 5 minutes of inactivity to 15 minutes. But thanks, I will try that.
– shinobody
Aug 5 at 18:31
Like I said, I don't believe anything has changed whatsoever. All I did in the last session was watch some Youtube videos using Firefox, and changed the screen sleep setting from 5 minutes of inactivity to 15 minutes. But thanks, I will try that.
– shinobody
Aug 5 at 18:31
"If you can then try to ssh into the machine" i have no idea what that means. Looking it up nets this article: linuxize.com/post/how-to-enable-ssh-on-ubuntu-18-04 - which is definitely impossible, I can't log in to install it, nor do I have any idea how to set up a LAN or how to find out IP of the problematic machine (I'm pretty sure I have dynamic IP).
– shinobody
Aug 5 at 19:05
"If you can then try to ssh into the machine" i have no idea what that means. Looking it up nets this article: linuxize.com/post/how-to-enable-ssh-on-ubuntu-18-04 - which is definitely impossible, I can't log in to install it, nor do I have any idea how to set up a LAN or how to find out IP of the problematic machine (I'm pretty sure I have dynamic IP).
– shinobody
Aug 5 at 19:05
1
1
Possible duplicate of GDM3 does not start in Ubuntu 18.04
– Gunnar Hjalmarsson
Aug 5 at 19:51
Possible duplicate of GDM3 does not start in Ubuntu 18.04
– Gunnar Hjalmarsson
Aug 5 at 19:51
|
show 5 more comments
1 Answer
1
active
oldest
votes
Solved! In recovery mode after enabling networking I selected dpkg - Repair broken packages, and then in root shell I used apt update
and then apt dist-upgrade
and this seems to have solved the problem. I'm not sure why it worked, but it worked.
add a comment
|
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/4.0/"u003ecc by-sa 4.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1163595%2fubuntu-doesnt-start-with-a-message-started-gnome-display-manager-dispatcher%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Solved! In recovery mode after enabling networking I selected dpkg - Repair broken packages, and then in root shell I used apt update
and then apt dist-upgrade
and this seems to have solved the problem. I'm not sure why it worked, but it worked.
add a comment
|
Solved! In recovery mode after enabling networking I selected dpkg - Repair broken packages, and then in root shell I used apt update
and then apt dist-upgrade
and this seems to have solved the problem. I'm not sure why it worked, but it worked.
add a comment
|
Solved! In recovery mode after enabling networking I selected dpkg - Repair broken packages, and then in root shell I used apt update
and then apt dist-upgrade
and this seems to have solved the problem. I'm not sure why it worked, but it worked.
Solved! In recovery mode after enabling networking I selected dpkg - Repair broken packages, and then in root shell I used apt update
and then apt dist-upgrade
and this seems to have solved the problem. I'm not sure why it worked, but it worked.
answered Aug 7 at 15:25
shinobodyshinobody
639 bronze badges
639 bronze badges
add a comment
|
add a comment
|
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1163595%2fubuntu-doesnt-start-with-a-message-started-gnome-display-manager-dispatcher%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Could you provide more information about what happened between the last time it booted successfully and now? What changed? As a first step, allow the machine time to boot. The last screen cap shows that the display manager is up and running, so the login screen should be coming up. Then see this link to resolve the network interfaces issue.
– Karthik
Aug 5 at 17:47
I guess the problem you are seeing is that the display manager tries to start, fails, tries to start again, fails, etc. So your screen is switching between text mode and graphics mode all the time, that why the flickering. If you can then try to ssh into the machine and then
cd /var/log
. See which log files were updated most recently:ls -latr
. Then have a look at those files:less some_log_file
("q" will terminate the pager). You'll probably find the error in theXorg.0.log
if you have that on your system.– Tomáš Pospíšek
Aug 5 at 17:55
Like I said, I don't believe anything has changed whatsoever. All I did in the last session was watch some Youtube videos using Firefox, and changed the screen sleep setting from 5 minutes of inactivity to 15 minutes. But thanks, I will try that.
– shinobody
Aug 5 at 18:31
"If you can then try to ssh into the machine" i have no idea what that means. Looking it up nets this article: linuxize.com/post/how-to-enable-ssh-on-ubuntu-18-04 - which is definitely impossible, I can't log in to install it, nor do I have any idea how to set up a LAN or how to find out IP of the problematic machine (I'm pretty sure I have dynamic IP).
– shinobody
Aug 5 at 19:05
1
Possible duplicate of GDM3 does not start in Ubuntu 18.04
– Gunnar Hjalmarsson
Aug 5 at 19:51