[Bug 1720149] Re: gnome-shell segv on wake from display or system sleep
Thanks. Unfortunately it seems that crash file is not one of the convenient ones with a readable stack trace built in so we need to submit it for processing. Please run this command on the original machine: ubuntu-bug /path/to/_usr_bin_gnome-shell.1000.crash I am making this bug private while the file remains attached, for security. ** Information type changed from Public to Private -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1720149 Title: gnome-shell segv on wake from display or system sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720149] Re: gnome-shell segv on wake from display or system sleep
It just happened, so attached the crash file that was generated. NB: gnome-shell 3.26.1-0ubuntu2 mutter 3.26.1-1 libmutter-1-0 3.26.1-1 NB: I notice there's also a libmutter-0-0 installed, possibly a hangover from the original zesty install. but ldd $(which gnome-shell) indicates it's linked to libmutter-1.so.0 so it's presumably irrelevant. I've now removed it anyway. This was a bit of a messy event. It went something like this: Attempted to wake system (from displaysleep, wasn't suspended) It appeared at first to work! My session was there. But the displays config was wrong. I noticed that my 4K monitor had (again, I think it's *its* problem) woken up thinking it's a 1440p monitor. As this is usually fixed by powercycling it, I did so. The second monitor (actually the first in discovery order), which is *actually* a 1440p monitor, also went to sleep. Power-cycling *it* woke them both up, (I think; things got confusing) but at that point it came back to the gdm login screen. So I'm guessing around then was where the gnome-shell crash happened. Often it's simpler than that. I wake the system up, it comes up logged- out. ** Attachment added: "_usr_bin_gnome-shell.1000.crash" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+attachment/4967524/+files/_usr_bin_gnome-shell.1000.crash -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1720149 Title: gnome-shell segv on wake from display or system sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1720149] Re: gnome-shell segv on wake from display or system sleep
I’m afk today but will try to get this information on Wednesday. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1720149 Title: gnome-shell segv on wake from display or system sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720149] Re: gnome-shell segv on wake from display or system sleep
Rachel, We are tracking hundreds of gnome-shell crashes right now and have had a few recent ones related to monitor configurations too. In order to make progress on this bug we either need a stack trace (look in /var/crash for crash files), or someone who experiences the problem to debug it remotely (use a second machine to attach a debugger to gnome-shell and get a trace of the crash that way). My concern is that the problem description without a stack trace is so vague it can easily be mistaken for some other bug. So please try to gather that additional information. This may help: http://wiki.ubuntu.com/DebuggingProgramCrash And this is only a request for Rachel right now, so as to avoid confusion from other peoples' similar issues. ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1720149 Title: gnome-shell segv on wake from display or system sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720149] Re: gnome-shell segv on wake from display or system sleep
Looks like this... https://bugzilla.gnome.org/show_bug.cgi?id=783853 ** Bug watch added: GNOME Bug Tracker #783853 https://bugzilla.gnome.org/show_bug.cgi?id=783853 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1720149 Title: gnome-shell segv on wake from display or system sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720149] Re: gnome-shell segv on wake from display or system sleep
That wouldn't surprise me. I've seen other reports, on IRC, to the same effect. Sadly, displayport is not optional here, not if I actually want to run my monitors at full resolution. Someone mentioned it being a "known bug" in mutter? However they didn't link to it and I wasn't at the keyboard at the time to nag them to do so. It would explain how I haven't seen it at all on the laptop, which I only use with its internal screen. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1720149 Title: gnome-shell segv on wake from display or system sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720149] Re: gnome-shell segv on wake from display or system sleep
This issue is occurring for me too with amdgpu. I experience the same problem under both Xorg and Wayland sessions. This is only an issue with my monitor connected via DisplayPort - when I connect via HDMI gnome- shell does not crash if the monitor goes to sleep. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1720149 Title: gnome-shell segv on wake from display or system sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720149] Re: gnome-shell segv on wake from display or system sleep
ok, same symptoms occurred with the default theme. So after all it looks like the shell theme has nothing to do with it. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1720149 Title: gnome-shell segv on wake from display or system sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720149] Re: gnome-shell segv on wake from display or system sleep
well I spoke too soon. Crash occurred with the locally 'built' arc theme. Slightly different though in that this time it *did* hang the system. But it started with the same segv message logged. So back to the default+Ambiance theme to test that for longer. Problem with trying to prove a negative. You can only say "Well it hasn't crashed *yet*" until it does. Damn, I liked that theme. :-( (Of course, now to try to prove the same negative about the default theme... I kind of hope it fails too now so it's not my favourite theme's fault.) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1720149 Title: gnome-shell segv on wake from display or system sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720149] Re: gnome-shell segv on wake from display or system sleep
Of interest, I can reproduce this on Ubuntu 17.10 beta, however it doesn't occur on Debian Stretch. However I didn't test theme settings, and was running Pop_OS! themes at the time. Next I will see if it occurs with stock themes. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1720149 Title: gnome-shell segv on wake from display or system sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720149] Re: gnome-shell segv on wake from display or system sleep
arc-theme package uninstalled and instead arc gtk & shell themes installed manually as directed in its github page via autogen. This appears not to be triggering the crash. even though the autogen doesn't know any gnome > 3.22. It may be that similarly rebuilding the arc-theme package for a gnome 3.26 environment would fix it, but I still don't really have a theory as to why it should break, let alone only on nvidia. There's no binaries in it afaik. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1720149 Title: gnome-shell segv on wake from display or system sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720149] Re: gnome-shell segv on wake from display or system sleep
I think my modeset=1 test earlier was invalid; I don't think that change was ever applied. It *did* get applied just now with a routine dist- upgrade, which included an update to console-setup, which forced update- initramfs. And then the system was unbootable except via the recovery system. syslog is full of crashes like this in rapid succession: Sep 30 13:33:38 fleetfoot kernel: [ 117.641448] [ cut here ] Sep 30 13:33:38 fleetfoot kernel: [ 117.641467] WARNING: CPU: 0 PID: 221 at /build/linux-s_bACt/linux-4.13.0/drivers/gpu/drm/drm_atomic_helper.c:1682 drm_atomic_helper_commit_hw_done+0x99/0xa0 [drm_kms_helper] Sep 30 13:33:38 fleetfoot kernel: [ 117.641468] Modules linked in: rfcomm hid_magicmouse hidp cmac bnep nls_iso8859_1 nvidia_uvm(POE) hid_apple joydev input_leds hid_generic ath3k btusb btrtl btbcm btintel bluetooth snd_usb_audio snd_usbmidi_lib usbhid hid ecdh_generic snd_hda_codec_hdmi eeepc_wmi asus_wmi cmdlinepart intel_spi_platform intel_rapl intel_spi spi_nor wmi_bmof sparse_keymap mtd x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm snd_hda_codec_realtek snd_hda_codec_generic irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_intel snd_hda_codec pcbc snd_hda_core snd_hwdep arc4 snd_pcm snd_seq_midi ath9k aesni_intel snd_seq_midi_event ath9k_common ath9k_hw snd_rawmidi aes_x86_64 crypto_simd snd_seq glue_helper cryptd ath intel_cstate snd_seq_device intel_rapl_perf mac80211 snd_timer cfg80211 snd soundcore Sep 30 13:33:38 fleetfoot kernel: [ 117.641496] mei_me mei shpchp lpc_ich wmi mac_hid nct6775 hwmon_vid coretemp parport_pc ppdev lp parport ip_tables x_tables autofs4 nvidia_drm(POE) nvidia_modeset(POE) i915 nvidia(POE) i2c_algo_bit drm_kms_helper e1000e syscopyarea sysfillrect sysimgblt fb_sys_fops ahci ptp drm libahci pps_core video Sep 30 13:33:38 fleetfoot kernel: [ 117.641507] CPU: 0 PID: 221 Comm: kworker/u16:6 Tainted: PW OE 4.13.0-12-generic #13-Ubuntu Sep 30 13:33:38 fleetfoot kernel: [ 117.641507] Hardware name: ASUS All Series/Z87I-PRO, BIOS 1005 11/26/2014 Sep 30 13:33:38 fleetfoot kernel: [ 117.641511] Workqueue: events_unbound commit_work [drm_kms_helper] Sep 30 13:33:38 fleetfoot kernel: [ 117.641512] task: 970a91cec5c0 task.stack: b72901e5c000 Sep 30 13:33:38 fleetfoot kernel: [ 117.641515] RIP: 0010:drm_atomic_helper_commit_hw_done+0x99/0xa0 [drm_kms_helper] Sep 30 13:33:38 fleetfoot kernel: [ 117.641515] RSP: 0018:b72901e5fdb8 EFLAGS: 00010286 Sep 30 13:33:38 fleetfoot kernel: [ 117.641516] RAX: 970a8ff8b008 RBX: 0004 RCX: 970a9ca0c000 Sep 30 13:33:38 fleetfoot kernel: [ 117.641516] RDX: 970a8dce1400 RSI: 0001 RDI: 970a93a56c08 Sep 30 13:33:38 fleetfoot kernel: [ 117.641517] RBP: b72901e5fdd8 R08: 970aafa12398 R09: 0018 Sep 30 13:33:38 fleetfoot kernel: [ 117.641517] R10: b72901e5fd88 R11: 0372 R12: 0001 Sep 30 13:33:38 fleetfoot kernel: [ 117.641518] R13: 970a97780b40 R14: 970a93a56c08 R15: 970a93a56c08 Sep 30 13:33:38 fleetfoot kernel: [ 117.641518] FS: () GS:970aafa0() knlGS: Sep 30 13:33:38 fleetfoot kernel: [ 117.641519] CS: 0010 DS: ES: CR0: 80050033 Sep 30 13:33:38 fleetfoot kernel: [ 117.641519] CR2: 7fa55cd3a010 CR3: 0003ff609000 CR4: 001406f0 Sep 30 13:33:38 fleetfoot kernel: [ 117.641520] DR0: DR1: DR2: Sep 30 13:33:38 fleetfoot kernel: [ 117.641520] DR3: DR6: fffe0ff0 DR7: 0400 Sep 30 13:33:38 fleetfoot kernel: [ 117.641521] Call Trace: Sep 30 13:33:38 fleetfoot kernel: [ 117.641524] nvidia_drm_atomic_helper_commit_tail+0x10e/0x170 [nvidia_drm] Sep 30 13:33:38 fleetfoot kernel: [ 117.641527] commit_tail+0x3f/0x60 [drm_kms_helper] Sep 30 13:33:38 fleetfoot kernel: [ 117.641530] commit_work+0x12/0x20 [drm_kms_helper] Sep 30 13:33:38 fleetfoot kernel: [ 117.641532] process_one_work+0x1e7/0x410 Sep 30 13:33:38 fleetfoot kernel: [ 117.641533] worker_thread+0x4a/0x410 Sep 30 13:33:38 fleetfoot kernel: [ 117.641534] kthread+0x125/0x140 Sep 30 13:33:38 fleetfoot kernel: [ 117.641535] ? process_one_work+0x410/0x410 Sep 30 13:33:38 fleetfoot kernel: [ 117.641536] ? kthread_create_on_node+0x70/0x70 Sep 30 13:33:38 fleetfoot kernel: [ 117.641538] ret_from_fork+0x25/0x30 Sep 30 13:33:38 fleetfoot kernel: [ 117.641538] Code: 7d 30 e8 db b8 2c fa 48 89 df c6 07 00 0f 1f 40 00 49 8b 4e 08 41 83 c4 01 44 39 a1 38 03 00 00 7f 98 5b 41 5c 41 5d 41 5e 5d c3 <0f> ff eb c0 f3 c3 90 0f 1f 44 00 00 48 8b 4f 08 8b 81 38 03 00 Sep 30 13:33:38 fleetfoot kernel: [ 117.641552] ---[ end trace ab364b2a1fae43bb ]--- Sep 30 13:33:39 fleetfoot kernel: [ 117.974932] [ cut here ] However that's probably offtopic here, and just speaks to nvidia kms
[Bug 1720149] Re: gnome-shell segv on wake from display or system sleep
It may be the Arc shell theme, in interaction with nVidia: I was unable to reproduce the problem on the Macbook Pro using Xorg gnome session, and that still with the Arc shell theme. Both a short (few minutes) and long (greater than one hour) display sleeps tested. I was also unable to reproduce it on the nVidia-equipped desktop with the Default shell theme selected, on either short or long display sleep. needs-root-rights is still set to yes in this configuration (ie: the same as tested yesterday evening except for switching back to default themes.) I don't know how a theme can cause a segfault, it's just image assets and css. But I'll leave it on Default for now to see if the issue does after all recur. I'll also go back to modeset=1 but needs-root-rights left unset, and wait and see. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1720149 Title: gnome-shell segv on wake from display or system sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720149] Re: gnome-shell segv on wake from display or system sleep
That would appear to be very different from what we're trying to report here: 1. It's not hanging. It's presumably exiting, forcing a logout, and it all happens before the monitors are awake enough to show a picture. We're not in a hung state at any point. 2. It's not only suspend, it's wake from only display-sleep too. The rest of the computer isn't suspended or sleeping in any manner. It *also* failed, in the exact same manner, on wake from suspend, but this suggests the problem isn't in suspending or waking from that, but just about the display sleep/wake. 3. It's only affecting nVidia (or at least, for me, it seems not to be also affecting Intel, but I haven't tried such a long sleep under Intel/Xorg and I should - tomorrow, as I'm in bed now). I bet there's no problem. :-) 4. It appears to be only affecting Xorg, although of course with nVidia there's too much else broken when trying to force it to use Wayland (which is, after all, not enabled by default for these reasons). Certainly no such problems on Intel/Wayland which *does* regularly get to sleep for long periods of time between uses, and I've never seen it hang on wake. (Hardware of my Intel graphics machine is an Early 2015 13" Retina Macbook Pro. This specifically is a Broadwell Core-i5 with Intel Iris 6100, and I've only attempted to use it on its own screen, not with any external screens connected. Generally, it runs Linux brilliantly, as far as I've so far tried, and is very happy with Wayland. All hardware just works OOTB.) I'm not using the default ubuntu session (with or without wayland) on either machine, but the GNOME session - wayland on the intel, xorg on the nvidia. Basically just because I wanted vanilla dash-to-dock. I'm not running many extensions, dash to dock, a wallpaper changer, ubuntu appindicators (which isn't working on Xorg on either machine btw, to be the subject of another bug report when I get a round tuit)... and nothing else that I remember right now while I'm not at it. Come to think of it, I do need to test using the default gnome shell theme rather than Arc's. I will tomorrow. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1720149 Title: gnome-shell segv on wake from display or system sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720149] Re: gnome-shell segv on wake from display or system sleep
I've had GNOME Shell hang on wake from suspend some times. I have Intel graphics, not NVIDIA. I am using the default Ubuntu session (Wayland). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1720149 Title: gnome-shell segv on wake from display or system sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720149] Re: gnome-shell segv on wake from display or system sleep
neither change made a difference in the end. the needs-root-rights change (instead of, not as well as, modeset) didn't help either, after a long sleep. Why instead-of not as-well-as? Because the manpage for Xwrapper.config said that its default setting of 'auto' turns needs-root-rights off is kms is enabled and on if it's enabled. So i daresay setting it directly is superfluous, it's controlled by enabling modeset or not. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1720149 Title: gnome-shell segv on wake from display or system sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720149] Re: gnome-shell segv on wake from display or system sleep
Just to +1 - those changes did not impact 'long term sleep' crashing the shell. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1720149 Title: gnome-shell segv on wake from display or system sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720149] Re: gnome-shell segv on wake from display or system sleep
... and the answer is no. After a longer display-sleep i woke it up to find myself back at the login prompt. Definitely that and not the lock screen. This may in part be related to long-term issues I have with this monitor. Early-revision Dell P2715Q 4K monitors have known firmware- related issues with waking from sleep. It has phases. Sometimes it just works. Sometimes it's narcoleptic, taking the form of just going straight back to sleep after an attempted wake. And sometimes it wakes thinking it's just a 1440p monitor, and I don't notice until I get some text on the screen and think 'that doesn't look right'. That's what happened this time, and I think only happens after a longer sleep. Generally the fix in this instance is to switch the monitor off and on again, and it comes on secure in its identity as a 4K monitor. But as I switched it off, the session I'd just logged into again was again logged out. So I'm guessing Xorg/nVidia/Gnome between them are seeing a *change* in the monitor configuration attached to the computer. I would say it's still a bug that its response to that is to bug out, rather than shape itself around the new reality, but I don't know if that's just something we'll need Wayland working to deal with more gracefully. syslog covering the wake-up attached, FWIW (it's quite busy). There's one segfault in there looking similar to those I saw earlier, from the moment of trying to wake it up: Sep 29 13:59:01 fleetfoot kernel: [15526.672810] gnome-shell[26357]: segfault at 2c ip 7fb47879d434 sp 7ffd919279a8 error 4 in libmutter-1.so.0.0.0[7fb4786ff000+14] However grepping for it in syslog I also see it happened twice earlier today too, while I was away from the computer: Sep 29 10:59:10 fleetfoot kernel: [ 4736.585186] gnome-shell[1892]: segfault at 2c ip 7fb1e3549434 sp 7fff343753c8 error 4 in libmutter-1.so.0.0.0[7fb1e34ab000+14] Sep 29 12:26:32 fleetfoot kernel: [ 9977.733747] gnome-shell[21408]: segfault at 2c ip 7f9d9f7be434 sp 7ffd5a80ce88 error 4 in libmutter-1.so.0.0.0[7f9d9f72+14] It's possible this was triggered by the cat stepping on the keyboard or trackpad. I can also see there *wasn't* any segfault at the time I switched the monitor off and on again, and yet I was still bumped out of my gnome session. I dare suggest that even if the monitor's dodgy and even if the driver is having issues, gnome-shell should not segfault, but fail more gracefully. (Or is it libmutter that's segfaulting?) I'm going to try enabling that 'needs root rights' setting. ** Attachment added: "syslog.wakeup" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+attachment/4958680/+files/syslog.wakeup -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1720149 Title: gnome-shell segv on wake from display or system sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720149] Re: gnome-shell segv on wake from display or system sleep
I tried the modeset change first, as that one we'd presumably prefer to be true anyway one day, whereas giving stuff root that isn't supposed to have root never feels right. :-) It worked. I left it to display sleep for a couple of minutes and on wake I came right back to the desktop. (I don't have screen lock on, so no password needed.) In case the length of sleep makes a difference (don't know why it should) I'll leave it to cut in normally when I go out for a couple of hours shortly, and see what happens when I get back. NB: I had tried enabling this before as part of forcing nvidia to use wayland. I disabled it because (in Wayland) it was terribly sluggish and in the logs I was seeing nvidia_drm panic and presumably relaunch almost continuously, on the 4.13 kernel. Nouveau was also failing on that kernel, even worse, giving just a black screen. That was when I decided to try harder to have a working Xorg system again. :-) But I hadn't tried turning modeset on and still use xorg; I didn't know there was a point in doing so. It seems to be happy. BTW FWIW rachel@fleetfoot:~$ apt-cache policy nvidia-384 nvidia-384: Installed: 384.90-0ubuntu0~gpu17.10.1 Candidate: 384.90-0ubuntu0~gpu17.10.1 Version table: *** 384.90-0ubuntu0~gpu17.10.1 500 500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1720149 Title: gnome-shell segv on wake from display or system sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720149] Re: gnome-shell segv on wake from display or system sleep
I also edited /etc/modprobe.d/nvidia-graphics-drivers.conf and set 'modeset=1' for the nvidia driver where it was previously 0, you might give that a shot and if that works we can mark this a duplicate. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1720149 Title: gnome-shell segv on wake from display or system sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720149] Re: gnome-shell segv on wake from display or system sleep
After some research I believe this may be related: * https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1672033 * https://devtalk.nvidia.com/default/topic/1000172/linux/root-less-xorg-does-not-detect-displays-which-leads-to-segfault-in-mutter/ I am trying a work around, let me know if this fixes anything: echo 'needs_root_rights = yes' | sudo tee -a /etc/X11/Xwrapper.config and reboot. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1720149 Title: gnome-shell segv on wake from display or system sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720149] Re: gnome-shell segv on wake from display or system sleep
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1720149 Title: gnome-shell segv on wake from display or system sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720149] Re: gnome-shell segv on wake from display or system sleep
I can't reproduce this in Xorg on my non-nvidia machine (on which I normally run Wayland because I can). It appears to be nvidia specific. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1720149 Title: gnome-shell segv on wake from display or system sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720149] Re: gnome-shell segv on wake from display or system sleep
I have the same issue - screen blank is enabled, suspend is disabled. Using proprietary NVidia driver also. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1720149 Title: gnome-shell segv on wake from display or system sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720149] Re: gnome-shell segv on wake from display or system sleep
Forgot to mention - running on the daily build of Ubuntu 17.10 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1720149 Title: gnome-shell segv on wake from display or system sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
