This bug is closed. Please open a new bug if you have any problems.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1779476
Title:
Ubuntu 18.04: gdm3 does not switch to graphics after
I had similar issues where the upgrade from 16.04 to 18.04 resulted in blank
screen,
The key to finding the problems was reviewing the errors in the file
/var/log/syslog
gnome-session[2851]: X Error of failed request: BadValue (integer parameter
out of range for operation)
[Expired for gdm3 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
Joachim,
You are commenting on the wrong bug. Maybe see bug 1779827 instead.
Otherwise please log a new bug of your own by running: ubuntu-bug
linux-generic
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
I noticed similar effect with very recent (4.17) kernels. In 4.16.8
there were changes in random.c due to a security flaw. The function that
detects "having enough entropy" is now strictly blocking. In the early
boot phase this is bad on any machine without enough entropy sources.
The kernel has 3
Mark,
You are commenting on the wrong bug. Please see bug 1779827 or create a
new one.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1779476
Title:
Ubuntu 18.04: gdm3 does not
Recently upgraded 2 computers to Kubuntu 18.04 and I'm also seeing this
problem in that the Kubuntu splash screen stays up for ages. As I have
only just upgraded my only other kernel was from 4.13. Installing
haveged seems to have fixed it on one computer at least.
--
You received this bug
That's intriguing. Yes please - next time this happens to anyone please
copy/move the folder contents instead of deleting them.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1779476
I tried the solution suggested by njsf (clearing /var/lib/gdm3) and it
rescued my system as well.
As suggested by Daniel I validated whether the disk was in a
deteriorated state, but this was not the case.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Thinking about it, I could better have copied the old content to see if
I could reproduce the bug by restoring the old values of the folder.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
OK. If you rediscover this bug in the next two months and figure out the
exact cause then that would be helpful. Otherwise the bug will
automatically close if no further comments are added after two months.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
I wonder if bug 1780986 is related...
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1779476
Title:
Ubuntu 18.04: gdm3 does not switch to graphics after update
To manage
No hardware errors on the Smart counters
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1779476
Title:
Ubuntu 18.04: gdm3 does not switch to graphics after update
To manage
There was no sign of corruption. Once the original gdm3 also failed and
given that the config in etc was the original, the only thing left to
check was the var/lib that I saw referenced in the Xorg cmdline.
I was able to upgrade gdm3 without problems.
The SSD did not run out of disk space it has
Great. Thanks for figuring that out.
Was there any sign of corruption? Were you able to upgrade gdm3 to the
latest version again?
I wonder - if it happens again then please check:
1. if your disk/partition is full (run: df -h); or
2. if the disk has experienced any hardware errors (run the
NOTE: Results w/ haveged installed...
I installed gdm3 3.28.0-ubuntu1 with:
apt-get install gdm3=3.28.0-0ubuntu1 libgdm1=3.28.0-0ubuntu1
gir1.2-gdm-1.0=3.28.0-0ubuntu1
After reboot gdm3 would still not start.
After I noticed the path used I decided to:
rm -rf /var/lib/gdm3/*
rm -rf
Everyone else, please either:
* Wait and watch here without commenting about your own experiences; or
* Check out bug 1779827 to see if it helps you; or
* If you are using an older Intel GPU then see bug 1727356; or
* Log a new bug of your own.
--
You received this bug notification
njsf,
The next step is that we need to find out what/where things broke for
you.
First, please try downgrading gdm3 to the original 18.04 release
version:
https://launchpad.net/ubuntu/+source/gdm3/3.28.0-0ubuntu1/+build/14516225
If that doesn't solve it then please try some older kernels and
If installing haveged doesn't help then that means everyone for whom it
did help is commenting on the wrong bug.
Please seen comment #19.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
If installing haveged doesn't help the original reporter then that means
everyone for whom it did help is commenting on the wrong bug.
Please see comment #19.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
I have serious doubts it is the same issue.
Even with haveged installed I do not get gdm3 to start as I have stated several
times already.
Please do not mark as a dup of that issue
On Jul 8, 2018, 22:40 -0400, Daniel van Vugt ,
wrote:
> OK, it sounds like plymouth is actually not related to
OK, it sounds like plymouth is actually not related to this bug. In that
case maybe we need to make this a duplicate of bug 1779827, which
already has the kernel team involved.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in
gdm3 failing to start is part of the boot process. But I'm happy to
change it back.
** Summary changed:
- Boot process hangs indefinitely. Never finishes.
+ Ubuntu 18.04: gdm3 does not switch to graphics after update
** No longer affects: plymouth (Debian)
** No longer affects: plymouth
Bug #1779827 appears to be a duplicate of this.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1779476
Title:
Ubuntu 18.04: gdm3 does not switch to graphics after update
To manage
** Also affects: plymouth (Ubuntu)
Importance: Undecided
Status: New
** Changed in: plymouth (Ubuntu)
Status: New => Incomplete
** Also affects: gdm3 (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897572
Importance: Unknown
Status: Unknown
**
Comment #34 indeed sounds like the problem.
Does installing this package fix the bug?;
https://packages.debian.org/sid/amd64/plymouth/download
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
Installed linux-headers-4.15.0-23-generic, now dkms runs properly.
Re-tested w/ 4.15.0-23-generic: gdm3 STILL does not come up, just bounces
between black screen and the systemd progress messages.
So, going back to 4.15.0-23-generic does NOT solve the original issue.
I will continue w/ haveged
It affected lightdm as well. I run unity in 18.04 and use lighdm and the
boot time has gone from 4 secs to 4 minutes with 4.15.0-24. Brad's
workaround(#21) by installing haveged also works for lightdm.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Processing triggers for linux-image-4.15.0-23-generic (4.15.0-23.25) ...
/etc/kernel/postinst.d/dkms:
Error! Your kernel headers for kernel 4.15.0-23-generic cannot be found.
Please install the linux-headers-4.15.0-23-generic package,
or use the --kernelsourcedir option to tell DKMS where it's
Going back to kernel 4.15.0-23 DOES NOT solve the gdm3 issue.
Hence the issue I reported is not solved.
Has for the _workaround_ of using lightdm in 4.15.0-23, yes, it boots faster
HOWEVER, once I installed 4.15.0-23 the bcmwl DID NOT GET BUILT/INSTALLED which
is also VERY bad, as _no WIFI_.
I agree with monkeybrain2012. The question that must then be raised is
how this breakage got into an Ubuntu software update for the masses
almost 2 months after it was known that a kernel change had broken gdm3
login, and after commits for the underlying issues had been created in
debian.
--
You
I think it might be this bug
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897572
** Bug watch added: Debian Bug tracker #897572
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897572
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
I can report a very similar experience after the update to kernel *-24.
The difference with my machine - a barebook Clevo packaged by Pioneer Computers
Australia -
is that no keyboarding, usb mouse, or touchpad use reproducably reduces the
hang time by plymouth to less than an average 90seconds.
Or just:
sudo lsof | grep /dev/random
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1779476
Title:
Ubuntu 18.04: gdm3 does not switch to graphics after update
To manage
This command should tell you the suspicious process ID(s):
sudo ls -l /proc/*/fd/* | grep /dev/random
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1779476
Title:
Ubuntu 18.04:
Sorry, my mistake. Recent kernel changes may be the trigger of this
problem but would not be the root cause. If there is any process
blocking waiting for entropy then that's the real issue. Because they
are blocking waiting indefinitely for something that might theoretically
take forever. And
Can confirm this with GDM, without haveged, on a Lenovo Thinkpad S440:
- with kernel 4.15.0-24, GDM comes up after several minutes
- if I wiggle the touchpad, in a dozen seconds
- with kernel 4.15.0-23, immediately (no issue)
Strangely, I recall that when I first experienced this issue a couple
Also, after removing haveged, please try some older kernels:
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D
and try to find the two versions closest together where one works and
the other does not.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
In trying to identify the source of the problem we will need people to
temporarily remove haveged.
Next, please reproduce the issue and just leave the machine running. Do
the graphics eventually come up after a few minutes of waiting? Please
also repeat the test but wiggle the mouse/touchpad
That's good news.
Although this bug is primarily owned by njsf so we'll wait to see what
he says. I want to make sure the original reporter is actually
experiencing the same problems as are being discussed now.
--
You received this bug notification because you are a member of Ubuntu
Desktop
Daniel,
Installing haveged fixed my issue so I'm pretty sure its the same as
this one. Therefore I won't create a bug of my own.
Thanks for the help.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
I find it disturbing we still have parts of the system that will block
start-up waiting for entropy. That's not a good user experience.
But maybe that's not the same problem as njsf is experiencing...
njsf: Do you find an older kernel fixes the problem for you too? Try one
of these:
I had to purge/reinstall lightdm for some reason (otherwise it was
flickering on/off), but now both GDM and LightDM are working as they
should on 4.15.0-24 with 'haveged' installed.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3
I believe I found a solution (or at least, a temporary workaround until
the potential bug is fixed). It seemed the bug was introduced in
4.15.0-24, as 4.15.0-23 works fine. I'm running an up-to-date 18.04
system on top of a Lenovo ThinkPad Yoga.
I would get a blank screen with both GDM and
I should add that I've only tested this with 'startx' and GDM; I haven't
tried LightDM.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1779476
Title:
Ubuntu 18.04: gdm3 does not
Turns out lightdm is working after all, almost. If you wait patiently
when the black screen appears after the Ubuntu 5 dots boot screen,
possibly as much as 4 minutes, then the desktop eventually appears,
albeit somewhat messed up, with a message box asking you to "unlock the
login keychain"
Mark,
gdm3, mutter, gnome-shell, and sometimes graphics drivers, all have
multiple bugs that can result in these same symptoms. So it is helpful
to not group bugs on the symptoms and track down the root cause of each
person's problem separately.
Otherwise when it comes to declaring a bug fixed,
> which solves the problem
I don't consider switching to lightdm to be a solution the problem. It's a
workaround.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1779476
Title:
I think I got hit by this bug too after the kernel update to
4.15.0-24-generic. Found this on askubuntu
https://askubuntu.com/questions/1051555/after-security-update-
to-4-15-0-24-generic-26-ubuntu-screen-shows-log-content which solves the
problem.
Switcing to another tty and then switching to
Another thing I noticed is that since the upgrade, all Xwayland sessions
crash on suspend, so they start anew. Only using Xorg now. Previously
all worked well with gdm3 in wayland.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3
After todays update of grub and kernel to 4.15.0-25 it now takes ~4m to get to
lightdm.
Never since my '94 486DX2 I had such poor boot-to-use times.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1779476/+attachment/5159228/+files/lspci.txt
** Description changed:
After update of gdm and kernel gdm3 no longer enables graphics.
What happens:
=
With and without:
Daniel,
Which part of what I wrote you do you another bug about? The fundamental
issue, gdm doesn't work, hence no login screen, after the latest
kernel/gdm update is the same as this bug, so why create a duplicate?
The previous issues were with past distribution versions so filing a bug
is not
Same thing on my laptop Lenovo X240.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1779476
Title:
Ubuntu 18.04: gdm3 does not switch to graphics after update
To manage
Mark,
Please log a bug of your own so we can figure that out for you.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1779476
Title:
Ubuntu 18.04: gdm3 does not switch to graphics
I'm suffering this after this update too. It is the latest in a
depressingly long list of Ubuntu updates that have ed up my system.
You really *need* better testing of updates. If you can't improve the
testing then there needs to be a way to roll-back the system to before
an update.
Instead
Thanks.
Unfortunately we are still missing some information.
Please run 'lspci -k' and send us the output. If you don't know how to
do that then just take a photo of the screen.
Please also run 'apport-collect 1779476' again. I have modified the bug
so hopefully it will give us more info the
apport information
** Tags added: apport-collected bionic package-from-proposed
** Description changed:
After update of gdm and kernel gdm3 no longer enables graphics.
What happens:
=
With and without:
WaylandEnable=false
in /etc/gdm3/custom.conf
gdm3 does not
Please log into a VT and run 'apport-collect 1779476' on the machine.
That will send us more information that we need.
** Changed in: gdm3 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3
59 matches
Mail list logo
