Bug 2180277
| Summary: | gnome-shell crashes and sysops happens when users logout | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | lnie <lnie> | ||||||||||||
| Component: | gnome-shell | Assignee: | GNOME SIG Unassigned <gnome-sig> | ||||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||
| Priority: | unspecified | ||||||||||||||
| Version: | 38 | CC: | adscvr, awilliam, florian, fmuellner, gmarr, gnome-sig, jadahl, kparal, mihai, otaylor, philip.wyett, robatino | ||||||||||||
| Target Milestone: | --- | Keywords: | CommonBugs | ||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | Unspecified | ||||||||||||||
| OS: | Unspecified | ||||||||||||||
| Whiteboard: | RejectedBlocker AcceptedFreezeException https://discussion.fedoraproject.org/t/80859 | ||||||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2024-05-07 17:41:07 UTC | Type: | Bug | ||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||
| Documentation: | --- | CRM: | |||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||
| Embargoed: | |||||||||||||||
| Bug Depends On: | |||||||||||||||
| Bug Blocks: | 2083913 | ||||||||||||||
| Attachments: |
|
||||||||||||||
Created attachment 1952262 [details]
backtrace
Created attachment 1952263 [details]
journal
Proposed as a Blocker for 38-final by Fedora user lnie using the blocker tracking app because: Shutting down, rebooting, logging in and logging out must work using standard console commands and the mechanisms offered (if any) by all release-blocking desktops Created attachment 1952621 [details]
backtrace
I can confirm this, though I get a different backtrace (attached). I tried to reproduce lnie's setup as close as possible - I logged in, ran a terminal, used `sudo su` to become root, and set a password for root with `passwd`. Then I logged out. Things proceeded exactly as in lnie's video. This is with GNOME updated to 44.0 from updates-testing. Created attachment 1953206 [details]
my backtrace
Note I did wonder if this might also happen during user switching (which would be worse), but it doesn't seem like it. I created a second user and switched back and forth several times - no crashes, and the running session for each user was properly preserved through all the switches. I also get a crash on logout: https://retrace.fedoraproject.org/faf/reports/640384/ GDB is working since minutes to generate a backtrace, not sure if it ever finishes :D I reported 3 different crashes on logout yesterday: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6536 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6535 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6530 I guess some of them might be related to this one. > https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6536 https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2722 fixes this one. Discussed during the 2023-03-27 blocker review meeting: [0] The decision to classify this bug as a "RejectedBlocker (Final)" and an "AcceptedFreezeException (Final)" was made as this doesn't violate the release criteria, but it's a polish issue you can run into before updating so we agree it deserves an FE. [0] https://meetbot.fedoraproject.org/fedora-blocker-review/2023-03-27/f38-blocker-review.2023-03-27-16.00.txt There's an MR for this now, but it looks rather large and I'm not super inclined to try and jam it in as a late FE. well, two MRs... 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. OK, so following breadcrumbs, I believe all the fixes for this made it to F38 stable. The gjs fix, "context: Clear all vectors of JS::Heap on dispose", was in gjs 1.76.1 (F38 is at 1.76.3). The mutter fix, "clutter/backend: Allow unsetting input method", was in mutter 44.1 (F38 is at 44.9). And the gnome-shell fixes, starting at "shell/window-tracker: Disconnect signals on disposal", were in gnome-shell 44.1 (F38 is at 44.10). So I think we can call this fixed. https://bodhi.fedoraproject.org/updates/FEDORA-2023-4609e16886 (mutter and gnome-shell) https://bodhi.fedoraproject.org/updates/FEDORA-2023-a7a7913609 (gjs) |
Created attachment 1952261 [details] screencast Description of problem: As shown in the attached screencast. Version-Release number of selected component (if applicable): gnome-shell-44~rc-1.fc38.x86_64 How reproducible: always Steps to Reproduce: 1.login to the newly installed system 2.open one app 3.logout 4.gnome-abrt claims that crash and sysops happens Actual results: Expected results: Additional info: