Bug 1972961 - crash on logout
Summary: crash on logout
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 34
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Florian Müllner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-06-17 01:19 UTC by Chris Murphy
Modified: 2022-06-07 21:18 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-07 21:18:30 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
coredumpctl gdb, thread apply all bt full (120.01 KB, text/plain)
2021-06-17 01:20 UTC, Chris Murphy
no flags Details
Coredumpctl gdb all bt F35 (21.02 KB, text/plain)
2021-10-16 15:19 UTC, Geraldo Simião
no flags Details

Description Chris Murphy 2021-06-17 01:19:02 UTC
Description of problem:

Frequent crashing on logout.

Version-Release number of selected component (if applicable):
gnome-shell-40.2-1.fc34.x86_64
mutter-40.2-2.fc34.x86_64


How reproducible:
Often


Steps to Reproduce:
1. Log out
2.
3.

Actual results:

[31068.532752] gnome-shell[1775]: segfault at cedd ip 000000000000cedd sp 00007ffd7399e498 error 14
[31068.532767] Code: Unable to access opcode bytes at RIP 0xceb3.



Expected results:

Shouldn't crash


Additional info:

Comment 1 Chris Murphy 2021-06-17 01:20:01 UTC
Created attachment 1791648 [details]
coredumpctl gdb, thread apply all bt full

Comment 2 Christopher Tubbs 2021-07-09 15:26:30 UTC
This issue was opened first, but bug #1974407 seems to describe the same (or similar) problem, and has more details. Should this be closed as a duplicate of that one?

Comment 3 Christopher Tubbs 2021-07-09 16:00:55 UTC
Potential duplicate of bug #1960874 also

Comment 4 Alessio 2021-09-14 21:12:10 UTC
It happens on F35 as well

Comment 5 Geraldo Simião 2021-09-15 00:40:29 UTC
Yes, it happens on a Fedora-Workstation-Live-x86_64-35-20210913.n.0.iso wih the latest updates.

[fedora@fedora ~]$ coredumpctl info 1567
           PID: 1567 (gnome-shell)
           UID: 1000 (fedora)
           GID: 1000 (fedora)
        Signal: 11 (SEGV)
     Timestamp: Tue 2021-09-14 21:31:06 -03 (6min ago)
  Command Line: /usr/bin/gnome-shell
    Executable: /usr/bin/gnome-shell
 Control Group: /user.slice/user-1000.slice/user/session.slice/org.gnome.Shell
          Unit: user
     User Unit: org.gnome.Shell
         Slice: user-1000.slice
     Owner UID: 1000 (fedora)
       Boot ID: ef43ffa647044fa08c3bb25371c26999
    Machine ID: c81d67b402c0478fbe5bfed389f9af0d
      Hostname: fedora
       Storage: /var/lib/systemd/coredump/core.gnome-shell.1000.ef43ffa647044fa08c3bb25371c26999.1567.1631665866000000.zst (present)
     Disk Size: 19.3M
       Message: Process 1567 (gnome-shell) of user 1000 dumped core.
                
                Found module linux-vdso.so.1 with build-id: ed20e76e7305a015b02ca28805e804deda0c04d0
                Found module ISO8859-1.so with build-id: 82abac6185731f8db570415eb7d442615deeaa08
                Found module libpk-gtk-module.so with build-id: 15bdc95913646361598d71c4ca1ed44fdfcc5ae3
                Found module libcanberra-gtk-module.so with build-id: da92365f021b6e3d58e804e4a945c25c62068b89
                Found module libgioremote-volume-monitor.so with build-id: 118b59926f7a383d62031d99537e1d5c2ecaec0f
                Found module libcrypt.so.2 with build-id: 97e399e2a9fd30cc6febf6afe07e963db09720d0
                Found module libaccountsservice.so.0 with build-id: ee0daf84fb23a2ba08abc2f19c1f20ae259f9206
                Found module libopus.so.0 with build-id: 0717c4aa935190f889e12134adcb95f1173896e6
                Found module libvorbisenc.so.2 with build-id: 68b1fdf0007c752a46482443a9b599bb6cf5a64e
                Found module libFLAC.so.8 with build-id: 34324bdfee454c456c4e08456152fe5b86ba331f
                Found module libgsm.so.1 with build-id: f84c8103f3f95ee09f2c2888e21ff13c870ee056
                Found module libasyncns.so.0 with build-id: 648745a2e1c2a0a990336ca37d634b817a6861c5
                Found module libsndfile.so.1 with build-id: 5eb36acdde2df64bc32fe4f39b4a62b27790de2b
                Found module libpulsecommon-15.0.so with build-id: 610784314edf8434b1e341c44c97a92afab2a37e
                Found module libpulse-mainloop-glib.so.0 with build-id: 0d0cbf21eea0480626d13c51aca40f37f2fdaf80

Comment 6 Geraldo Simião 2021-10-16 14:50:49 UTC
it still happening on F35, but one only knows that if look on coredumctl, because gnome-shell restarts soon after crash.

  PID: 1550 (gnome-shell)
           UID: 1000 (fedora)
           GID: 1000 (fedora)
        Signal: 11 (SEGV)
     Timestamp: Sat 2021-10-16 11:46:14 -03 (2min 9s ago)
  Command Line: /usr/bin/gnome-shell
    Executable: /usr/bin/gnome-shell
 Control Group: /user.slice/user-1000.slice/user/session.slice/org.gnome.Shell
          Unit: user
     User Unit: org.gnome.Shell
         Slice: user-1000.slice
     Owner UID: 1000 (fedora)
       Boot ID: 02fa781ff9b1410291ec554a5e351315
    Machine ID: c81d67b402c0478fbe5bfed389f9af0d
      Hostname: fedora
       Storage: /var/lib/systemd/coredump/core.gnome-shell.1000.02fa781ff9b1410291ec554a5e351315.1550.1634395574000000.zst (present)
     Disk Size: 17.8M
       Message: Process 1550 (gnome-shell) of user 1000 dumped core.

Comment 7 Geraldo Simião 2021-10-16 15:19:12 UTC
Created attachment 1833671 [details]
Coredumpctl gdb all bt F35

Comment 8 Ben Cotton 2022-05-12 15:19:33 UTC
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
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 '34'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 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.

Comment 9 Ben Cotton 2022-06-07 21:18:30 UTC
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 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.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.