[Bug 1964120] Re: gnome-shell crashed with SIGSEGV at ?+a7c called from (Cannot access memory at address [in stack])
Bug 1964037 mentions a similar stack trace so maybe that was the problem all along. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964120 Title: gnome-shell crashed with SIGSEGV at ?+a7c called from (Cannot access memory at address [in stack]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964120] Re: gnome-shell crashed with SIGSEGV at ?+a7c called from (Cannot access memory at address [in stack])
Looks like I hit this today in a Xorg session when testing Nvidia. The log provides no details of what caused the crash other than the system was shutting down/logging out at the time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964120 Title: gnome-shell crashed with SIGSEGV at ?+a7c called from (Cannot access memory at address [in stack]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964120] Re: gnome-shell crashed with SIGSEGV at ?+a7c called from (Cannot access memory at address [in stack])
Got directed here from bug (private due to coredump attachement) that Daniel marked a duplicate of this one. I can reliably reproduce my original issue following: 1. Fresh boot 2. Connect external monitors 3. Put laptop to sleep 4. Wake laptop from sleep (one of two external monitors is still black) 5. Go to Settings -> Display (Gnome thinks both monitors are enabled) 6. Disable the black monitor and enable it again. 7. Gnome enables the problematic monitor for a split second and then disables it instantly. Attaching prevboot.txt for the above. I have so far two workarounds for my issue Workaround 1: - go to TTY3 with Ctrl+Alt+F3 (no need to log in, just wait for all monitors to work) - go to TTY1 with Ctrl+Alt+F1 (lands on GDM log in page, I log in) - all monitors now work and applications are preserved (sometimes need to enable it in settings) Workaround 2: - power cycle the black monitor (but without messing with Settings -> Display first) Happy to provide more information or test solutions. It was driving me crazy to at least figure out reproducibility pattern and possible workarounds (stayed until 3am one night experimenting...). Not sure if useful but I also learned: - happens also on kernel 5.17 from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.17.2/amd64/ - happens also on live usb session from Ubuntu 22.04 so not likely my local changes - does not happen on live usb of fedora 36 beta (tested as it also has gnome 42) ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964120/+attachment/5580363/+files/prevboot.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964120 Title: gnome-shell crashed with SIGSEGV at ?+a7c called from (Cannot access memory at address [in stack]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964120] Re: gnome-shell crashed with SIGSEGV at ?+a7c called from (Cannot access memory at address [in stack])
If anyone can reproduce this crash then please: 1. Reproduce the crash. 2. Reboot. 3. Run: journalctl -b-1 > prevboot.txt 4. Attach the resulting text file here. ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964120 Title: gnome-shell crashed with SIGSEGV at ?+a7c called from (Cannot access memory at address [in stack]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964120] Re: gnome-shell crashed with SIGSEGV at ?+a7c called from (Cannot access memory at address [in stack])
It appears the address of a stack variable has overwritten the return address for the offending function call. So we have no stack trace. I wonder if there's a way to catch stack corruption without going so far as Valgrind... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964120 Title: gnome-shell crashed with SIGSEGV at ?+a7c called from (Cannot access memory at address [in stack]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964120] Re: gnome-shell crashed with SIGSEGV at ?+a7c called from (Cannot access memory at address [in stack])
I think the final address ending in a7c is probably raise() so that may not be useful information. This is starting to smell like stack corruption. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964120 Title: gnome-shell crashed with SIGSEGV at ?+a7c called from (Cannot access memory at address [in stack]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
