[Desktop-packages] [Bug 1868440] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features() from _st_set_text_from_style()
In my case it did appear to be gTile related also. Just manually disabling the extension on the gnome extensions panel was also sufficient to trigger a crash (presumably triggering the same path as when the screen lock was activated). Presumably other extensions using libst can have the same effect. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1868440 Title: gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features() from _st_set_text_from_style() Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/7235aacf0ac9572c674e49ffcc32ddb01d46a0f0 --- This happened when I closed Chrome and moved the curser to "Power Off/Log Out, Settings .." ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 22 11:22:08 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2020-03-15 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: st_theme_node_get_font_features () from /usr/lib/gnome-shell/libst-1.0.so _st_set_text_from_style () from /usr/lib/gnome-shell/libst-1.0.so ?? () from /usr/lib/gnome-shell/libst-1.0.so ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1868440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871580] Re: Session killed instead of suspended on screen lock
Uploaded in #1871580. Looking through gnome-shell issues, #1868440 looks like it might also be the same thing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1871580 Title: Session killed instead of suspended on screen lock Status in gnome-session package in Ubuntu: Incomplete Bug description: Running focal (updated to 2020-04-08), ubuntu-on-wayland session. Trigger: either lock the screen manually (top-right-corner menu -> Lock) or wait for the auto-lock timer (Settings -> Privacy -> Screen Lock). Expected result: after unlock, previous session resumes. Observed: see login dialog instead of unlock dialog, previous session and all processes appear to have been killed. This is a fairly serious usability regression. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-session 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 10:35:16 2020 InstallationDate: Installed on 2019-05-27 (316 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: Upgraded to focal on 2020-04-06 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1871580/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871580] Re: Session killed instead of suspended on screen lock
Deleting the old _usr_bin_gnome-shell.1000.crash and collecting a fresh one. However, a quick bit of experimentation appears to show that this crash only occurs with extensions enabled - after globally disabling extensions it appears to no longer occur. I haven't bisected extensions individually, but I'm guessing `gnome-shell-pomodoro` might be a good candidate since most of the others are javascript only. Still not ideal that extensions can kill the shell. ** Attachment added: "_usr_bin_gnome-shell.1000.crash" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1871580/+attachment/5349454/+files/_usr_bin_gnome-shell.1000.crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1871580 Title: Session killed instead of suspended on screen lock Status in gnome-session package in Ubuntu: Incomplete Bug description: Running focal (updated to 2020-04-08), ubuntu-on-wayland session. Trigger: either lock the screen manually (top-right-corner menu -> Lock) or wait for the auto-lock timer (Settings -> Privacy -> Screen Lock). Expected result: after unlock, previous session resumes. Observed: see login dialog instead of unlock dialog, previous session and all processes appear to have been killed. This is a fairly serious usability regression. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-session 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 10:35:16 2020 InstallationDate: Installed on 2019-05-27 (316 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: Upgraded to focal on 2020-04-06 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1871580/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871580] Re: Session killed instead of suspended on screen lock
Lots of repetitions of: ``` ERROR: apport (pid 7294) Wed Apr 8 12:22:32 2020: called for pid 7223, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 7294) Wed Apr 8 12:22:32 2020: executable: /usr/bin/gnome-shell (command line "/usr/bin/gnome-shell") ERROR: apport (pid 7294) Wed Apr 8 12:22:32 2020: debug: session gdbus call: (true,) ERROR: apport (pid 7294) Wed Apr 8 12:22:32 2020: apport: report /var/crash/_usr_bin_gnome-shell.1000.crash already exists and unseen, doing nothing to avoid disk usage DoS ERROR: apport (pid 7377) Wed Apr 8 12:22:45 2020: called for pid 7303, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 7377) Wed Apr 8 12:22:45 2020: executable: /usr/bin/gnome-shell (command line "/usr/bin/gnome-shell") ERROR: apport (pid 7377) Wed Apr 8 12:22:45 2020: debug: session gdbus call: (true,) ERROR: apport (pid 7377) Wed Apr 8 12:22:45 2020: apport: report /var/crash/_usr_bin_gnome-shell.1000.crash already exists and unseen, doing nothing to avoid disk usage DoS ``` I guess a anti-disk filling feature is proving counterproductive here? It's also possible that I manually disabled bits of whoopsie/apport in the past. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1871580 Title: Session killed instead of suspended on screen lock Status in gnome-session package in Ubuntu: Incomplete Bug description: Running focal (updated to 2020-04-08), ubuntu-on-wayland session. Trigger: either lock the screen manually (top-right-corner menu -> Lock) or wait for the auto-lock timer (Settings -> Privacy -> Screen Lock). Expected result: after unlock, previous session resumes. Observed: see login dialog instead of unlock dialog, previous session and all processes appear to have been killed. This is a fairly serious usability regression. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-session 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 10:35:16 2020 InstallationDate: Installed on 2019-05-27 (316 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: Upgraded to focal on 2020-04-06 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1871580/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871580] Re: Session killed instead of suspended on screen lock
Session lock invoked manually (~11:00:00), lock screen displays, click mouse to get unlock. Screen freezes for ~10 seconds, then blanks briefly and shows login screen. Looks like gnome-shell crashing at about 11:00:26 - interesting lines: Apr 08 11:00:26 kallisti gnome-shell[23758]: clutter_actor_insert_child_at_index: assertion 'child->priv->parent == NULL' failed Apr 08 11:00:28 kallisti kernel: gnome-shell[23758]: segfault at 0 ip 7fce7c55445a sp 7fffada2b230 error 4 in libst-1.0.so[7fce7c532000+4b000] Apr 08 11:00:28 kallisti kernel: Code: 4d 8b 8c 24 28 01 00 00 48 98 eb 0c 0f 1f 40 00 48 83 e8 01 85 c0 78 52 4d 8b 04 c1 b9 16 00 00 00 48 89 ef 49 8b 10 48 8b 12 <48> 8b 32 f3 a6 0f 97 c2 80 da 00 84 d2 75 d7 4d 8b 40 08 49 83 78 ** Attachment added: "journal during session lock" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1871580/+attachment/5349407/+files/journal-gnome-crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1871580 Title: Session killed instead of suspended on screen lock Status in gnome-session package in Ubuntu: Incomplete Bug description: Running focal (updated to 2020-04-08), ubuntu-on-wayland session. Trigger: either lock the screen manually (top-right-corner menu -> Lock) or wait for the auto-lock timer (Settings -> Privacy -> Screen Lock). Expected result: after unlock, previous session resumes. Observed: see login dialog instead of unlock dialog, previous session and all processes appear to have been killed. This is a fairly serious usability regression. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-session 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 10:35:16 2020 InstallationDate: Installed on 2019-05-27 (316 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: Upgraded to focal on 2020-04-06 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1871580/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871580] Re: Session killed instead of suspended on screen lock
There appear to neither be any relevant crash files (there are a couple which predate upgrading this system to focal), nor are there any reports on errors.u.c for this whoopsie-id. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1871580 Title: Session killed instead of suspended on screen lock Status in gnome-session package in Ubuntu: Incomplete Bug description: Running focal (updated to 2020-04-08), ubuntu-on-wayland session. Trigger: either lock the screen manually (top-right-corner menu -> Lock) or wait for the auto-lock timer (Settings -> Privacy -> Screen Lock). Expected result: after unlock, previous session resumes. Observed: see login dialog instead of unlock dialog, previous session and all processes appear to have been killed. This is a fairly serious usability regression. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-session 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 10:35:16 2020 InstallationDate: Installed on 2019-05-27 (316 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: Upgraded to focal on 2020-04-06 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1871580/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871580] [NEW] Session killed instead of suspended on screen lock
Public bug reported: Running focal (updated to 2020-04-08), ubuntu-on-wayland session. Trigger: either lock the screen manually (top-right-corner menu -> Lock) or wait for the auto-lock timer (Settings -> Privacy -> Screen Lock). Expected result: after unlock, previous session resumes. Observed: see login dialog instead of unlock dialog, previous session and all processes appear to have been killed. This is a fairly serious usability regression. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-session 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 10:35:16 2020 InstallationDate: Installed on 2019-05-27 (316 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: Upgraded to focal on 2020-04-06 (2 days ago) ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-bug focal third-party-packages wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1871580 Title: Session killed instead of suspended on screen lock Status in gnome-session package in Ubuntu: Invalid Bug description: Running focal (updated to 2020-04-08), ubuntu-on-wayland session. Trigger: either lock the screen manually (top-right-corner menu -> Lock) or wait for the auto-lock timer (Settings -> Privacy -> Screen Lock). Expected result: after unlock, previous session resumes. Observed: see login dialog instead of unlock dialog, previous session and all processes appear to have been killed. This is a fairly serious usability regression. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-session 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 10:35:16 2020 InstallationDate: Installed on 2019-05-27 (316 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: Upgraded to focal on 2020-04-06 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1871580/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1413963] [NEW] network manager cannot configure pptp VPN
Public bug reported: Release: vivid (fresh install) Packages: network-manager 0.9.8.8-0ubuntu34 network-manager-pptp 0.9.8.2-1ubuntu2 network-manager-pptp-gnome 0.9.8.2-1ubuntu2 After installing network-manager-pptp-gnome, it is not possible to add a PPTP VPN from the networkmanager GUI. What I expected to happen: Network - Add Network Connection - VPN - Select PPTP and configure with GUI What happened: Network - Add Network Connection - VPN pptp is not listed as a possible VPN type. Cannot graphically configure VPN. Possible cause: Copying an existing VPN configuration to /etc/NetworkManager/system- connections results in a VPN which does work. The option to add a new one is possibly because of a missing file: /etc/NetworkManager/VPN/nm-pptp-service.name includes: [GNOME] properties=/usr/lib/NetworkManager/libnm-pptp-properties which does not exist after installing the above packages. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Affects: network-manager-pptp (Ubuntu) Importance: Undecided Status: New ** Also affects: network-manager-pptp (Ubuntu) Importance: Undecided Status: New ** Package changed: gnome-control-center (Ubuntu) = network-manager (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1413963 Title: network manager cannot configure pptp VPN Status in network-manager package in Ubuntu: New Status in network-manager-pptp package in Ubuntu: New Bug description: Release: vivid (fresh install) Packages: network-manager 0.9.8.8-0ubuntu34 network-manager-pptp 0.9.8.2-1ubuntu2 network-manager-pptp-gnome 0.9.8.2-1ubuntu2 After installing network-manager-pptp-gnome, it is not possible to add a PPTP VPN from the networkmanager GUI. What I expected to happen: Network - Add Network Connection - VPN - Select PPTP and configure with GUI What happened: Network - Add Network Connection - VPN pptp is not listed as a possible VPN type. Cannot graphically configure VPN. Possible cause: Copying an existing VPN configuration to /etc/NetworkManager /system-connections results in a VPN which does work. The option to add a new one is possibly because of a missing file: /etc/NetworkManager/VPN/nm-pptp-service.name includes: [GNOME] properties=/usr/lib/NetworkManager/libnm-pptp-properties which does not exist after installing the above packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1413963/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1275760] [NEW] low graphics mode due to possible race condition on precise
Public bug reported: Precise 12.04.4 x86_64, kernel 3.2.0-58-generic. lspci reports: 01:00.0 VGA compatible controller: NVIDIA Corporation GF108GL [Quadro 600] (rev a1) dpkg -l 'nvidia*' | grep '^ii' reports: ii nvidia-304 304.116-0ubuntu0.0.1 ii nvidia-319-updates 331.20-0ubuntu0.0.1 ii nvidia-331-updates 331.20-0ubuntu0.0.1 ii nvidia-common 1:0.2.44.2 ii nvidia-current 304.116-0ubuntu0.0.1 ii nvidia-settings331.20-0ubuntu0.0.1 ii nvidia-settings-304331.20-0ubuntu0.0.1 ii nvidia-settings-319-updates331.20-0ubuntu0.0.1 ii xorg 1:7.6+12ubuntu2 Since installation, this system has periodically fallen to the running in low graphics mode prompt on boot. This can always be resolved by logging into a TTY and restarting LightDM: sudo service lightdm restart. Recently (sorry I can't say precisely - probably the last month or so) the frequency of this event has increased to ~90% of boots. Sample Xorg.0.log attached, but the key lines appear to be [ 3.364] (EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module. Please see the [ 3.364] (EE) NVIDIA(0): system's kernel log for additional error messages and [ 3.364] (EE) NVIDIA(0): consult the NVIDIA README for details. [ 3.364] (EE) NVIDIA(0): *** Aborting *** While `dmesg | grep nvidia` shows [2.737764] nvidia: module license 'NVIDIA' taints kernel. [3.658332] nvidia :01:00.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [3.658338] nvidia :01:00.0: setting latency timer to 64 From the timestamps, it looks like Xorg attempts to load the nvidia drivers 300ms before the kernel has actually loaded/initialised them, and hence fails. This certainly looks like a race condition. By the time I log into a TTY, lsmod shows the `nvidia` module to be loaded and restarting lightdm succeeds. Is there any way for either Xorg to check and if necessary wait for kernel module loading, or the low graphics dialog at least include a better option for dealing with this situation? ** Affects: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New ** Attachment added: Xorg.0.log https://bugs.launchpad.net/bugs/1275760/+attachment/3967555/+files/Xorg.0.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1275760 Title: low graphics mode due to possible race condition on precise Status in “nvidia-graphics-drivers” package in Ubuntu: New Bug description: Precise 12.04.4 x86_64, kernel 3.2.0-58-generic. lspci reports: 01:00.0 VGA compatible controller: NVIDIA Corporation GF108GL [Quadro 600] (rev a1) dpkg -l 'nvidia*' | grep '^ii' reports: ii nvidia-304 304.116-0ubuntu0.0.1 ii nvidia-319-updates 331.20-0ubuntu0.0.1 ii nvidia-331-updates 331.20-0ubuntu0.0.1 ii nvidia-common 1:0.2.44.2 ii nvidia-current 304.116-0ubuntu0.0.1 ii nvidia-settings331.20-0ubuntu0.0.1 ii nvidia-settings-304331.20-0ubuntu0.0.1 ii nvidia-settings-319-updates331.20-0ubuntu0.0.1 ii xorg 1:7.6+12ubuntu2 Since installation, this system has periodically fallen to the running in low graphics mode prompt on boot. This can always be resolved by logging into a TTY and restarting LightDM: sudo service lightdm restart. Recently (sorry I can't say precisely - probably the last month or so) the frequency of this event has increased to ~90% of boots. Sample Xorg.0.log attached, but the key lines appear to be [ 3.364] (EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module. Please see the [ 3.364] (EE) NVIDIA(0): system's kernel log for additional error messages and [ 3.364] (EE) NVIDIA(0): consult the NVIDIA README for details. [ 3.364] (EE) NVIDIA(0): *** Aborting *** While `dmesg | grep nvidia` shows [2.737764] nvidia: module license 'NVIDIA' taints kernel. [3.658332] nvidia :01:00.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [3.658338] nvidia :01:00.0: setting latency timer to 64 From the timestamps, it looks like Xorg attempts to load the nvidia drivers 300ms before the kernel has actually loaded/initialised them, and hence fails. This certainly looks like a race condition. By the time I log into a TTY, lsmod shows the `nvidia` module to be loaded and restarting lightdm succeeds. Is there any way for either Xorg to check and if necessary wait for kernel module
