This bug is closed because the original reporter said the bug is gone.
If you would like to keep discussing a similar issue then please open a
new bug by:
1. Switching back to gdm3
2. Run: ubuntu-bug gdm3
which will open a new bug.
--
You received this bug notification because you are a
I have this bug (and some other related ones) on a Lenovo ThinkPad L540
running Ubuntu 18.04.2. I switched to using lightdm which works around
the issues, but I don't like lightdm as much.
I see it's marked "Fix Released" above; excuse the ignorant question,
but does this mean I will soon be
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764643
Title:
Logout after console use freezes GUI
To manage notifications
I'm sorry, but I no longer have the crash-report.
I performed a clean install of Ubuntu (now 18.04) and the bug is gone.
Next to the release difference (17.10 to 18.04), I did not install the
nVidia proprietary driver.
For me, this problem's solved.
--
You received this bug notification
> I now have a crash report of this call to killall. Should I report it,
and include its number here, as I did before?
Yes please.
** Tags added: artful
** Changed in: gdm3 (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Seems related to https://bugs.launchpad.net/bugs/1758512 .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764643
Title:
Logout after console use freezes GUI
To manage notifications about this bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gdm3 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764643
Title:
Finally making some headway, I tried the following:
1. boot the system.
2. at the graphical login prompt, switch to another console (Ctrl+Alt+F2)
3. login
4. logout
The screen displays the GUI login prompt but hangs. I can still login on
this console using the braille display.
5. Log in from
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764643
Title:
Logout after console use freezes GUI
To manage notifications about this
Trying to reproduce on different system (laptop).
Same Ubuntu release and GNOME/my desktop system, GDM packages.
$ lsb_release -rd
Description:Ubuntu 17.10
Release:17.10
$ apt-cache policy gdm3
gdm3:
Installed: 3.26.1-3ubuntu3
Candidate: 3.26.1-3ubuntu3
Version table:
***
Trying to pin this bug down, I deactivated nVIDIA's driver, reactivated
nouveau and rebooted.
Sadly, the problem still persists.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764643
Title:
Logout
Thanks.
I uninstalled LIRC, just to be on the safe side.
Orca is necessary for my using the computer.
I uncommented the line #WaylandEnable=false and rebooted.
The problem still persists.
Then, without logging in graphically, I switched to tty3 (Ctrl+Alt+F3).
Logged in, executed a single command
Thanks.
Those bugs show you're using nvidia-384, which might be related.
Although I could not find anything that was obviously frozen.
If you edit /etc/gdm3/custom.conf and uncomment this line:
#WaylandEnable=false
does that fix it?
Also you seem to have a lot of these errors (in case
As requested, I killed both gdm3 and gnome-shell.
The bug-ids are #1764672 and #1764674 respectively.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764643
Title:
Logout after console use
In that case, maybe the gdm3 (or gnome-shell) process is hung. Can you
please try forcing it to dump core in that state?
killall -ABRT gdm3
killall -ABRT gnome-shell
Then wait a while and check for crash files again.
--
You received this bug notification because you are a member of Ubuntu
I followed your instructions; commented out the line in
/etc/apport/crashdb.conf, reproduced the problem, but there are no
crash-files in /var/crash.
Sorry.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It sounds like some component has crashed. Please:
1. Apply the workaround from bug 994921.
2. Reproduce the problem.
3. Look in /var/crash for crash files and then run:
ubuntu-bug /var/crash/YOURFILE.crash
4. Tell us here the ID of the new bug created.
** Changed in: gdm3 (Ubuntu)
17 matches
Mail list logo
