Bug 2322159 - Process /usr/bin/gnome-shell was killed by signal 11
Summary: Process /usr/bin/gnome-shell was killed by signal 11
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 40
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: GNOME SIG Unassigned
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-10-28 15:38 UTC by Juan Ra
Modified: 2025-05-20 20:08 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-05-20 20:08:28 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Gitlab GNOME gnome-shell issues 8006 0 None opened gnome-shell killed by SIGABRT 2024-10-29 18:21:02 UTC
Red Hat Bugzilla 712612 0 unspecified CLOSED [abrt] gnome-shell-3.0.2-1.fc15: Process /usr/bin/gnome-shell was killed by signal 11 (SIGSEGV) 2025-09-30 20:23:52 UTC
freedesktop.org Gitlab mesa mesa issues 12080 0 None opened [AMD Gpu] rendering issues 2024-10-29 18:21:02 UTC

Description Juan Ra 2024-10-28 15:38:22 UTC
Good, although this bug already has its thread comes out as closed due to the EOL of the version in which it was initially reported, in the thread that I cite you can see how the same error has been present since 2011 and continues to happen in later versions of Fedora
Original bug link: https://bugzilla.redhat.com/show_bug.cgi?id=712612
The status of the current thread is closed so I open a new thread to report that the bug continues to appear and is still present in the new versions of fedora, from the fedora bug reporting tool links to the thread of the bug already closed so it prevents to open a new one. 
In my case the error appears at any time, the last time was watching some videos on youtube.

Reproducible: Sometimes

Steps to Reproduce:
1.Login to system
2.Wait a moment to the issues apear
3.

Comment 1 Fedora Admin user for bugzilla script actions 2024-10-28 15:38:27 UTC
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!

Comment 2 Jonas Ådahl 2024-10-28 15:57:41 UTC
You'll have to be a bit more specific to make this actionable. Attach backtraces with debug symbols from coredumpctl of gnome-shell would be a start.

Comment 3 Juan Ra 2024-10-28 16:41:49 UTC
(In reply to Jonas Ådahl from comment #2)
> You'll have to be a bit more specific to make this actionable. Attach
> backtraces with debug symbols from coredumpctl of gnome-shell would be a
> start.

Sorry is my first bug report, here is the backtrace i seend to the gnome gitlab: https://pastebin.com/raw/QVPGszT7
I stop using gnome due to the this error when i try to work sesion ends and my work lost

Comment 4 Juan Ra 2024-10-28 16:42:51 UTC
This is the link to the issue open on gnome gitlab: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/8006

Comment 5 Brian J. Murrell 2024-10-29 18:24:10 UTC
(In reply to Jonas Ådahl from comment #2)
> You'll have to be a bit more specific to make this actionable. Attach
> backtraces with debug symbols from coredumpctl of gnome-shell would be a
> start.

There is lots more information in the original ticket (generated by abrt so has all of the usual abrt collateral) about this: bug 712612.

Frankly I think that ticket should have been reopened rather than restarting this all in a new ticket because it causes exactly this kind of disconnect.

Comment 6 Juan Ra 2024-10-29 19:30:57 UTC
(In reply to Brian J. Murrell from comment #5)
> (In reply to Jonas Ådahl from comment #2)
> > You'll have to be a bit more specific to make this actionable. Attach
> > backtraces with debug symbols from coredumpctl of gnome-shell would be a
> > start.
> 
> There is lots more information in the original ticket (generated by abrt so
> has all of the usual abrt collateral) about this: bug 712612.
> 
> Frankly I think that ticket should have been reopened rather than restarting
> this all in a new ticket because it causes exactly this kind of disconnect.


 I'm not sure if a closed bug can be reopened, in any case I have opened this one because reading the other's comments many people have asked for reopen it to be reopened and Red Hat's response is to create a new one.

Comment 7 Juan Ra 2024-11-04 19:56:28 UTC
I make some test using older kernel version, on kernel 6.9 the error is present but it doesn't happen that often, here are the dmesg of my system before de error and after the error using kernel 6.9
Before: https://pastebin.com/raw/ZdB8JbBv 
After: https://pastebin.com/raw/EHUnsZWc

Comment 8 Aoife Moloney 2025-04-28 14:04:22 UTC
This message is a reminder that Fedora Linux 40 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-05-13.
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 '40'.

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 40 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 Aoife Moloney 2025-05-20 20:08:28 UTC
Fedora Linux 40 entered end-of-life (EOL) status on 2025-05-13.

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


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