Created attachment 1388124 [details] stack dump obtained by coredumpctl gdb 12286 Description of problem: I can reliably crash gnome session by exiting from pan after using it for a while. Version-Release number of selected component (if applicable): gnome-shell-3.26.2-3.fc27.x86_64 How reproducible: almost every time Steps to Reproduce: 1. run pan, read news for a while 2. exit pan (sometimes the crash happens while actually using pan) Actual results: session crash, have to log back in Expected results: no cras
Filed upstream as well https://gitlab.gnome.org/GNOME/gnome-shell/issues/9
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
This is still a problem, so reopening this.
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Updating this as it is still happening in F32. It actually crashes Wayland (stack trace below). Should I reassign it to Wayland? Nov 02 00:19:31 new-host-6.home systemd-coredump[2784156]: Process 2287 (Xwayland) of user 1000 dumped core. Stack trace of thread 2287: #0 0x00007f0e0b70c9e5 raise (libc.so.6 + 0x3c9e5) #1 0x00007f0e0b6f5895 abort (libc.so.6 + 0x25895) #2 0x0000561027971510 OsAbort (Xwayland + 0x1b4510) #3 0x0000561027976469 AbortServer (Xwayland + 0x1b946> #4 0x00005610279771ba FatalError (Xwayland + 0x1ba1ba) #5 0x0000561027803ce0 xwl_log_handler (Xwayland + 0x4> #6 0x00007f0e0bdf281e wl_log (libwayland-client.so.0 > #7 0x00007f0e0bdeda5b display_handle_error (libwaylan> #8 0x00007f0e0b5e6af0 ffi_call_unix64 (libffi.so.6 + > #9 0x00007f0e0b5e62ab ffi_call (libffi.so.6 + 0x62ab) #10 0x00007f0e0bdf17e2 wl_closure_invoke (libwayland-c> #11 0x00007f0e0bdeddba dispatch_event (libwayland-clie> #12 0x00007f0e0bdef47f dispatch_queue (libwayland-clie> #13 0x0000561027803e1b xwl_read_events (Xwayland + 0x4> #14 0x000056102796f211 ospoll_wait (Xwayland + 0x1b221> #15 0x0000561027968853 WaitForSomething (Xwayland + 0x> #16 0x0000561027937107 Dispatch (Xwayland + 0x17a107) #17 0x000056102793b424 dix_main (Xwayland + 0x17e424) #18 0x00007f0e0b6f7042 __libc_start_main (libc.so.6 + > #19 0x000056102780398e _start (Xwayland + 0x4698e) Stack trace of thread 2687: #0 0x00007f0e0b8afe92 pthread_cond_wait@@GLIBC_2.3.2 > #1 0x00007f0e09ce386b n/a (radeonsi_dri.so + 0x4
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.