Description of problem: GNOME Shell randomly crashed when logging in. Version-Release number of selected component: gnome-shell-44~beta-2.fc38 Additional info: reporter: libreport-2.17.7 type: CCpp reason: gnome-shell killed by SIGSEGV journald_cursor: s=28e399cd7e0349c2a6fb36f446d6a06d;i=eca;b=9ede4c1f55cc477297b40e870dfd0b35;m=dbc75b44;t=5f5871e2bce75;x=b7864e5fe8cde081 executable: /usr/bin/gnome-shell cmdline: /usr/bin/gnome-shell cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell rootdir: / uid: 1000 kernel: 6.2.0-63.fc38.x86_64 package: gnome-shell-44~beta-2.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: Gjs::Closure::is_valid() const comment: GNOME Shell randomly crashed when logging in. Truncated backtrace: Thread no. 0 (2 frames) #0 Gjs::Closure::is_valid() const at ../gi/closure.h:91 #1 GjsCallbackTrampoline::callback_closure(_GIArgument**, void*) at ../gi/function.cpp:290
Created attachment 1946336 [details] File: proc_pid_status
Created attachment 1946337 [details] File: maps
Created attachment 1946338 [details] File: limits
Created attachment 1946339 [details] File: environ
Created attachment 1946340 [details] File: open_fds
Created attachment 1946341 [details] File: mountinfo
Created attachment 1946342 [details] File: os_info
Created attachment 1946343 [details] File: cpuinfo
Created attachment 1946344 [details] File: core_backtrace
Created attachment 1946345 [details] File: exploitable
Created attachment 1946346 [details] File: dso_list
Created attachment 1946347 [details] File: var_log_messages
Created attachment 1946348 [details] File: backtrace
Problem appeared immediately after I logged in. reporter: libreport-2.17.9 type: CCpp reason: gnome-shell killed by SIGSEGV journald_cursor: s=84a3d2da8a4742c986e52210f8036b11;i=67191;b=6dbbc24c401b4742b1c66850cf07901b;m=903e43e;t=5f7cb5f10e2ba;x=42757e22433022e6 executable: /usr/bin/gnome-shell cmdline: /usr/bin/gnome-shell cgroup: 0::/user.slice/user-501.slice/user/session.slice/org.gnome.Shell rootdir: / uid: 501 kernel: 6.2.8-300.fc38.x86_64 package: gnome-shell-44.0-4.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: Gjs::Closure::is_valid() const comment: Problem appeared immediately after I logged in.
logout and login back in reporter: libreport-2.17.9 type: CCpp reason: gnome-shell killed by SIGSEGV journald_cursor: s=9a6fae7b7420497a99ec03f995c04c04;i=17155;b=9d140762579447e683c7e7f9ad4db5c9;m=c4c0c56e;t=5f9a68095977a;x=e7ffc62d67e1c9e9 executable: /usr/bin/gnome-shell cmdline: /usr/bin/gnome-shell cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell rootdir: / uid: 1000 kernel: 6.2.11-300.fc38.x86_64 package: gnome-shell-44.0-4.fc38 runlevel: N 5 dso_list: /usr/bin/gnome-shell gnome-shell-44.0-4.fc38.x86_64 (Fedora Project) 1681796536 backtrace_rating: 4 crash_function: Gjs::Closure::is_valid() const comment: logout and login back in
Terminating a session after a notice an update for an extension was available. Logged in again and the crash report was there. reporter: libreport-2.17.9 type: CCpp reason: gnome-shell killed by SIGSEGV journald_cursor: s=c2c5dedaddb14c22a7c9269574f23c36;i=177a7d;b=3d408e76dbfe424a89fb77dcc991f4a9;m=384d676;t=5fa0e8f5a0cec;x=cb1d1861b523fc99 executable: /usr/bin/gnome-shell cmdline: /usr/bin/gnome-shell cgroup: 0::/user.slice/user-20528.slice/user/session.slice/org.gnome.Shell rootdir: / uid: 20528 kernel: 6.2.11-300.fc38.x86_64 package: gnome-shell-44.0-4.fc38 runlevel: N 5 dso_list: /usr/bin/gnome-shell gnome-shell-44.0-4.fc38.x86_64 (Fedora Project) 1681453885 backtrace_rating: 4 crash_function: Gjs::Closure::is_valid() const
Never seen this on fc37, marking as regression
Judging by the reported time of the failure, it occurred while nobody was logged in; the display was merely the login screen. I may have been logged in via ssh but do not recall details. reporter: libreport-2.17.9 journald_cursor: s=78ca7afea9f745ed85924a13cdd0d7bb;i=3b01ec;b=b61afa9b92ee498bbd38f54456a43922;m=36c7077c3;t=5f9e33abaf117;x=e8245daddcf588f8 cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell package: gnome-shell-44.0-4.fc38 reason: gnome-shell killed by SIGSEGV kernel: 6.2.11-300.fc38.x86_64 crash_function: Gjs::Closure::is_valid() const comment: Judging by the reported time of the failure, it occurred while nobody was logged in; the display was merely the login screen. I may have been logged in via ssh but do not recall details. cmdline: /usr/bin/gnome-shell rootdir: / uid: 1000 runlevel: N 5 backtrace_rating: 4 executable: /usr/bin/gnome-shell type: CCpp
I was logged out because of an gnome extension update and I got this error after logging back in reporter: libreport-2.17.9 type: CCpp reason: gnome-shell killed by SIGSEGV journald_cursor: s=ae6718a4669b4735aa9984621891c6d8;i=3f68d0f;b=d3586874d7ba40cd8af36736ecfd718b;m=4209a82;t=5faf1d6ea06ae;x=1f0ae33588cfd273 executable: /usr/bin/gnome-shell cmdline: /usr/bin/gnome-shell cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell rootdir: / uid: 1000 kernel: 6.2.14-300.fc38.x86_64 package: gnome-shell-44.1-1.fc38 runlevel: N 5 dso_list: /usr/bin/gnome-shell gnome-shell-44.1-1.fc38.x86_64 (Fedora Project) 1682713012 backtrace_rating: 4 crash_function: Gjs::Closure::is_valid() const comment: I was logged out because of an gnome extension update and I got this error after logging back in
I think it happend upon 'dnf update' reporter: libreport-2.17.9 type: CCpp reason: gnome-shell killed by SIGSEGV journald_cursor: s=58bb902149254c5aaf7152c45e566d63;i=851ef;b=2fc510de693a4a2286cb6954b222e08a;m=395c8fb50;t=5fb526a13ee22;x=e6565e031c967426 executable: /usr/bin/gnome-shell cmdline: /usr/bin/gnome-shell cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell rootdir: / uid: 1000 kernel: 6.3.1-200.fc38.x86_64+debug package: gnome-shell-44.1-1.fc38 runlevel: N 5 dso_list: /usr/bin/gnome-shell gnome-shell-44.1-1.fc38.x86_64 (Fedora Project) 1682706236 backtrace_rating: 4 crash_function: Gjs::Closure::is_valid() const comment: I think it happend upon 'dnf update'
Fiddling with a multi-monitor setup. Not sure if this is related, but Settings shows high resolutions chosen for external monitors, yet, they are actually set into a lower resolution that is closer to the laptop's builtin display's resolution. Even then, the tray in the top line is beyond the edge of the external monitors and thus not visible and not accessible. reporter: libreport-2.17.9 type: CCpp reason: gnome-shell killed by SIGSEGV journald_cursor: s=460f061ccfd549ebab7f34dcf4bbb24b;i=17e922;b=00fbbe7929fa4f45bb1c33f7844047c9;m=9750c5d17;t=5fb6f3b8dfab5;x=2d788fbadd90b78 executable: /usr/bin/gnome-shell cmdline: /usr/bin/gnome-shell cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell rootdir: / uid: 1000 kernel: 6.2.14-300.fc38.x86_64 package: gnome-shell-44.1-1.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: Gjs::Closure::is_valid() const
The problem araised after rebooting the worksation. Previous steps include: The Shell appearance was changed with Gnome Tweaks. The Nordic-Polar-v40 theme was selected reporter: libreport-2.17.9 type: CCpp reason: gnome-shell killed by SIGSEGV journald_cursor: s=95533c5f6215487f9db1242893f21bcb;i=78607;b=0b2dcabbd3eb4f98937ed4d2aacf835d;m=b6f36d5;t=5fb99bcfb0bfd;x=3902189301dd5c49 executable: /usr/bin/gnome-shell cmdline: /usr/bin/gnome-shell cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell rootdir: / uid: 1000 kernel: 6.2.14-300.fc38.x86_64 package: gnome-shell-44.1-1.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: Gjs::Closure::is_valid() const
still happening on gnome-shell-44.1-1.fc38 for me as well.
Updated extension, logout and logback in. reporter: libreport-2.17.10 type: CCpp reason: gnome-shell killed by SIGSEGV journald_cursor: s=a28e6239a28c4a75a64b47916fb207f6;i=104325;b=2c59e2b4d9e643968eafc0ff140cbcf5;m=3f4146d;t=5fd40287a4483;x=449f08e4fdcb5bf6 executable: /usr/bin/gnome-shell cmdline: /usr/bin/gnome-shell cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell rootdir: / uid: 1000 kernel: 6.3.4-201.fc38.x86_64 package: gnome-shell-44.1-1.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: Gjs::Closure::is_valid() const comment: Updated extension, logout and logback in.
I logget out of the current session to apply a gnome extension update and recieved this error after logging back in reporter: libreport-2.17.10 type: CCpp reason: gnome-shell killed by SIGSEGV journald_cursor: s=ae6718a4669b4735aa9984621891c6d8;i=439c64b;b=3c3c5a54d84f4f01aa2009c94fd81bfc;m=331de74;t=5fd872b803a00;x=ca682c2afc184893 executable: /usr/bin/gnome-shell cmdline: /usr/bin/gnome-shell cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell rootdir: / uid: 1000 kernel: 6.3.5-200.fc38.x86_64 package: gnome-shell-44.1-1.fc38 runlevel: N 5 dso_list: /usr/bin/gnome-shell gnome-shell-44.1-1.fc38.x86_64 (Fedora Project) 1682713012 backtrace_rating: 4 crash_function: Gjs::Closure::is_valid() const comment: I logget out of the current session to apply a gnome extension update and recieved this error after logging back in
logout to update extension reporter: libreport-2.17.10 type: CCpp reason: gnome-shell killed by SIGSEGV journald_cursor: s=06e068dc3db141589c83bac8b5de033f;i=13c66;b=4da444f648bf4a6eb3bd655198e3c2ad;m=5b3de9c;t=5fefa84d5e2f7;x=540f3de90175e0d5 executable: /usr/bin/gnome-shell cmdline: /usr/bin/gnome-shell cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell rootdir: / uid: 1000 kernel: 6.3.8-200.fc38.x86_64 package: gnome-shell-44.2-1.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: Gjs::Closure::is_valid() const comment: logout to update extension
Probably happened while the system was shutting down reporter: libreport-2.17.11 type: CCpp reason: gnome-shell killed by SIGSEGV journald_cursor: s=c2c5dedaddb14c22a7c9269574f23c36;i=329b9a;b=5517dcae2cee4b7ea51fc2295dcaa148;m=3aeb7e47d;t=600e8524f07ea;x=f54f45aac8b21882 executable: /usr/bin/gnome-shell cmdline: /usr/bin/gnome-shell cgroup: 0::/user.slice/user-20528.slice/user/session.slice/org.gnome.Shell rootdir: / uid: 20528 kernel: 6.3.12-200.fc38.x86_64 package: gnome-shell-44.2-1.fc38 runlevel: N 5 dso_list: /usr/bin/gnome-shell gnome-shell-44.2-1.fc38.x86_64 (Fedora Project) 1686565158 backtrace_rating: 4 crash_function: Gjs::Closure::is_valid() const comment: Probably happened while the system was shutting down
update extensions and then logout reporter: libreport-2.17.11 type: CCpp reason: gnome-shell killed by SIGSEGV journald_cursor: s=c3db08857f29472ba0d2ef9b844336fb;i=11c556;b=95d7b0f43e484e81b1e317dce8df7e65;m=2025715;t=601f6a9bc68fc;x=74b40d6872271c3b executable: /usr/bin/gnome-shell cmdline: /usr/bin/gnome-shell cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell rootdir: / uid: 1000 kernel: 6.4.6-200.fc38.x86_64 package: gnome-shell-44.3-1.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: Gjs::Closure::is_valid() const comment: update extensions and then logout
Crash being reported by gnome after user logout -> login reporter: libreport-2.17.11 type: CCpp reason: gnome-shell killed by SIGSEGV journald_cursor: s=d55ba4aed8c2444ea5fbf6009128fe30;i=12c8c3;b=5f52f4d40f5241a995e06e3c204e69b9;m=146cc1cd48;t=6065253911f63;x=2a2f90dc9b492a0f executable: /usr/bin/gnome-shell cmdline: /usr/bin/gnome-shell cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell rootdir: / uid: 1000 kernel: 6.4.15-200.fc38.x86_64 package: gnome-shell-44.5-1.fc38 runlevel: N 5 comment: Crash being reported by gnome after user logout -> login backtrace_rating: 4 crash_function: Gjs::Closure::is_valid() const
spcific case: was playing a game (steam, proton, railroad trycoon II) and gnome crashed at random. general case crashs like this seem to happen frquently, while the computer is unattended (user locked, no being activly used) i'll come home from work and gnome will be on the login screen reporter: libreport-2.17.11 type: CCpp reason: gnome-shell killed by SIGSEGV journald_cursor: s=0e77d4eef1b846ceb48df9867dedaf1e;i=1c1ccd;b=217ae7b7b38c41afae7fd69e6f084d24;m=12585ac56e3;t=607a1f1c59e99;x=774ef7974527b9a executable: /usr/bin/gnome-shell cmdline: /usr/bin/gnome-shell cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell rootdir: / uid: 1000 kernel: 6.5.5-200.fc38.x86_64 package: gnome-shell-44.5-1.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: Gjs::Closure::is_valid() const
When the desktop started it just displayed this failure, now I don't know which application crashed, but just guessing, I had my VPN configured to start with the desktop and when my VPN is not connected it blocks any other connection, maybe that's it, a pid it couldn't connect and it crashed, I dunno ¯\(ã)/¯ reporter: libreport-2.17.11 type: CCpp reason: gnome-shell killed by SIGSEGV journald_cursor: s=1e8361c545d344a7878dc3ad2a9ba6c4;i=1de9a;b=9a20140e7cfc492581ec04d8a11638dc;m=1acdf2c9b;t=608f34f330481;x=67dd0f3817029c53 executable: /usr/bin/gnome-shell cmdline: /usr/bin/gnome-shell cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell rootdir: / uid: 1000 kernel: 6.5.8-200.fc38.x86_64 package: gnome-shell-44.5-1.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: Gjs::Closure::is_valid() const
This component is maintained by the GNOME project. Issues with it should be reported directly to GNOME at https://gitlab.gnome.org/GNOME/. This issue should only be kept open if it: 1. Relates to Fedora packaging or integration with other Fedora components 2. Is required for Fedora release processes, such as blocker bugs and freeze exceptions If this issue isn't needed for either of these two reasons, please: * create an issue with GNOME * add a link to the GNOME issue here * close this issue as CLOSED/UPSTREAM Thank you!
This message is a reminder that Fedora Linux 38 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 38 on 2024-05-21. 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 'version' of '38'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 38 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.