[Bug 1866222] Re: GNOME Shell crashed with signal 11
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866222 Title: GNOME Shell crashed with signal 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866222] Re: GNOME Shell crashed with signal 11
Stéphane, please subscribe to bug 1866368 for your issue. Based on the information in comment #8. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866222 Title: GNOME Shell crashed with signal 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866222] Re: GNOME Shell crashed with signal 11
Stéphane, please do not comment on this bug. Instead please open a new bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866222 Title: GNOME Shell crashed with signal 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866222] Re: GNOME Shell crashed with signal 11
I will look into it. Here is how to reproduce the bug very easily: - open LibreOffice Writer - open Firefox - resize and move the windows so that they don't overlap - drag the Firefox tab (not window) over LibreOffice Then you instantly get the crash. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866222 Title: GNOME Shell crashed with signal 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866222] Re: GNOME Shell crashed with signal 11
Hello Stéphane Witzmann (swzn), Please: https://wiki.ubuntu.com/DebuggingProgramCrash Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866222 Title: GNOME Shell crashed with signal 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866222] Re: GNOME Shell crashed with signal 11
Here is the backtrace and registers. At first I couldn't reproduce the bug by just moving youtube videos (in firefox) around. But then when I had a document in LibreOffice Writer open (which is the situation I was in over the last few days of crashes), it happened very easily. --- Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault. 0x7f6555da3624 in wl_resource_get_version () from /usr/lib/x86_64-linux-gnu/libwayland-server.so.0 (gdb) bt #0 0x7f6555da3624 in wl_resource_get_version () from /usr/lib/x86_64-linux-gnu/libwayland-server.so.0 #1 0x7f65563fe3f9 in ?? () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 #2 0x7f65563ff413 in ?? () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 #3 0x7f6556420110 in ?? () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 #4 0x7f65563dee69 in ?? () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 #5 0x7f6555ff0f6f in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #6 0x7f6555ff135a in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #7 0x7f6555fb9094 in gdk_display_get_event () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #8 0x7f6555ff1006 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #9 0x7f6556ef0fbd in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7f6556ef1240 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7f6556ef1533 in g_main_loop_run () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7f65563bb970 in meta_run () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 #13 0x560782a19d85 in ?? () #14 0x7f655613d1e3 in __libc_start_main (main=0x560782a19930, argc=1, argv=0x7ffe0362fc48, init=, fini=, rtld_fini=, stack_end=0x7ffe0362fc38) at ../csu/libc-start.c:308 #15 0x560782a19f5e in ?? () (gdb) info registers rax0xffb0 -80 rbx0x56078765c2c0 94590336352960 rcx0x7 7 rdx0x5607850dab40 94590297025344 rsi0x5607857211d0 94590303605200 rdi0x0 0 rbp0x 0x rsp0x7ffe0362f698 0x7ffe0362f698 r8 0x7f650c003300 140071969764096 r9 0x56078a5d8740 94590386145088 r100x560784463018 94590283952152 r110x7ffe0362f538 140728955237688 r120x1 1 r130x7f650c003350 140071969764176 r140x56078765c2c0 94590336352960 r150x560784e680b0 94590294458544 rip0x7f6555da3624 0x7f6555da3624 eflags 0x10202 [ IF RF ] cs 0x3351 ss 0x2b43 ds 0x0 0 es 0x0 0 fs 0x0 0 gs 0x0 0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866222 Title: GNOME Shell crashed with signal 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866222] Re: GNOME Shell crashed with signal 11
Here is a log with a few crashes. It seems to always come after a few of these: Mar 6 01:24:57 wolfenstein rtkit-daemon[1197]: Supervising 9 threads of 5 processes of 1 users. Mar 6 01:30:29 wolfenstein rtkit-daemon[1197]: message repeated 19 times: [ Supervising 9 threads of 5 processes of 1 users.] Mar 6 01:30:29 wolfenstein rtkit-daemon[1197]: Successfully made thread 122522 of process 122427 owned by '1000' RT at priority 10. The log lacks the last crash (~19:20) since I attached gdb to the running gnome-shell process but couldn't switch back to the console gdb was started from (frozen screen, but I could hear the video was still playing). Will try attaching through ssh from another computer next time. ** Attachment added: "log.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866222/+attachment/5334373/+files/log.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866222 Title: GNOME Shell crashed with signal 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866222] Re: GNOME Shell crashed with signal 11
Unfortunately the bug is still incomplete because all we have is: [79676.217368] jik-x1 gnome-shell[3082]: GNOME Shell crashed with signal 11 meaning nobody can possibly work on this yet. Next time it happens, please reboot and then immediately run: journalctl -b-1 > prevboot.txt and attach the file 'prevboot.txt' here. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866222 Title: GNOME Shell crashed with signal 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866222] Re: GNOME Shell crashed with signal 11
I already have the workaround in bug 994921 and have for a long time. My system has generated and reported crashes as recently as February 28. There's no crash for this in /var/crash. There's no crash for this on errors.ubuntu.com. For some reason, when this crash occurs it's not generating a crash that can be reported to Ubuntu. It's still a bug that needs to be fixed, though, obviously, so I am changing the status of this bug from Incomplete back to New. ** Changed in: gnome-shell (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/1866222 Title: GNOME Shell crashed with signal 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866222] Re: GNOME Shell crashed with signal 11
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866222 Title: GNOME Shell crashed with signal 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866222] Re: GNOME Shell crashed with signal 11
Thanks for the bug report. There is a hint of the issue in the attached logs: [79661.914093] jik-x1 gnome-shell[3082]: 0x1800143: frame_complete callback never occurred for frame 464843 [79661.914311] jik-x1 gnome-shell[3082]: 0x1800143: frame_complete callback never occurred for frame 464842 [79676.217368] jik-x1 gnome-shell[3082]: GNOME Shell crashed with signal 11 Although it crashed 15 seconds after those errors so those are probably not the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866222 Title: GNOME Shell crashed with signal 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866222] Re: GNOME Shell crashed with signal 11
Got the same bug (GNOME Shell crashed with signal 11 after a short video freeze) on 20.04. It's pretty recent, it's been crashing my computer a couple of times a day since March 3 (according to the logs). I keep my computer updated every day. Seems to happen when I move a video from one monitor to the other. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866222 Title: GNOME Shell crashed with signal 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
