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
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 l
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 s
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 remot
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 Ubu
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
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 notifica
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
Ti
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.
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 o
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
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
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
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
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.launchpa
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
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 disp
... 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
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 hav
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 i
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 fi
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.ne
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.ne
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-
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 sle
25 matches
Mail list logo
