Bug 2360515 - [abrt] gnome-shell: pushbuf_dump(): gnome-shell killed by SIGSEGV
Summary: [abrt] gnome-shell: pushbuf_dump(): gnome-shell killed by SIGSEGV
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 42
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: GNOME SIG Unassigned
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:165301de1838cc6c32d87c48b7f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-04-17 02:00 UTC by OP
Modified: 2026-05-06 12:37 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)
File: proc_pid_status (1.48 KB, text/plain)
2025-04-17 02:01 UTC, OP
no flags Details
File: maps (3.96 KB, text/plain)
2025-04-17 02:01 UTC, OP
no flags Details
File: limits (1.29 KB, text/plain)
2025-04-17 02:01 UTC, OP
no flags Details
File: environ (1.49 KB, text/plain)
2025-04-17 02:01 UTC, OP
no flags Details
File: open_fds (14.97 KB, text/plain)
2025-04-17 02:01 UTC, OP
no flags Details
File: mountinfo (3.19 KB, text/plain)
2025-04-17 02:01 UTC, OP
no flags Details
File: os_info (754 bytes, text/plain)
2025-04-17 02:01 UTC, OP
no flags Details
File: cpuinfo (3.05 KB, text/plain)
2025-04-17 02:01 UTC, OP
no flags Details
File: core_backtrace (71.14 KB, text/plain)
2025-04-17 02:01 UTC, OP
no flags Details
File: exploitable (81 bytes, text/plain)
2025-04-17 02:01 UTC, OP
no flags Details
File: dso_list (449 bytes, text/plain)
2025-04-17 02:01 UTC, OP
no flags Details
File: var_log_messages (7.42 KB, text/plain)
2025-04-17 02:01 UTC, OP
no flags Details
File: backtrace (233.30 KB, text/plain)
2025-04-17 02:01 UTC, OP
no flags Details

Description OP 2025-04-17 02:00:56 UTC
Description of problem:
Every time I try to launc a terminal, I get kicked out.   The terminal never successfully loads.  It does not matter how I try and launch the terminal.

Version-Release number of selected component:
gnome-shell-48.0-1.fc42

Additional info:
reporter:       libreport-2.17.15
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=524814ea87274d98a8e6fcc44a1458e7;i=ac610;b=7a91aac876804b18a7c8d968644cd153;m=3ea508a9;t=632db856a6efb;x=8706499a8bd2481f
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.14.2-300.fc42.x86_64
package:        gnome-shell-48.0-1.fc42
runlevel:       N 5
comment:        Every time I try to launc a terminal, I get kicked out.   The terminal never successfully loads.  It does not matter how I try and launch the terminal.
backtrace_rating: 4
crash_function: pushbuf_dump

Truncated backtrace:
Thread no. 1 (64 frames)
 #0 pushbuf_dump at ../src/gallium/winsys/nouveau/drm/nouveau.c:1122
 #1 pushbuf_submit at ../src/gallium/winsys/nouveau/drm/nouveau.c:1195
 #2 pushbuf_flush at ../src/gallium/winsys/nouveau/drm/nouveau.c:1233
 #3 pushbuf_refn at ../src/gallium/winsys/nouveau/drm/nouveau.c:1486
 #4 nouveau_pushbuf_refn at ../src/gallium/winsys/nouveau/drm/nouveau.c:1701
 #5 nvc0_screen_fence_emit at ../src/gallium/drivers/nouveau/nvc0/nvc0_screen.c:676
 #6 _nouveau_fence_emit at ../src/gallium/drivers/nouveau/nouveau_fence.c:95
 #7 _nouveau_fence_next at ../src/gallium/drivers/nouveau/nouveau_fence.c:291
 #8 nvc0_default_kick_notify at ../src/gallium/drivers/nouveau/nvc0/nvc0_context.c:285
 #9 pushbuf_submit at ../src/gallium/winsys/nouveau/drm/nouveau.c:1165
 #10 pushbuf_flush at ../src/gallium/winsys/nouveau/drm/nouveau.c:1233
 #11 pushbuf_refn at ../src/gallium/winsys/nouveau/drm/nouveau.c:1486
 #12 nouveau_pushbuf_refn at ../src/gallium/winsys/nouveau/drm/nouveau.c:1701
 #13 PUSH_REFN at ../src/gallium/drivers/nouveau/nouveau_winsys.h:80
 #14 PUSH_REF1 at ../src/gallium/drivers/nouveau/nouveau_winsys.h:89
 #15 nvc0_cb_bo_push at ../src/gallium/drivers/nouveau/nvc0/nvc0_transfer.c:601
 #16 nvc0_constbufs_validate at ../src/gallium/drivers/nouveau/nvc0/nvc0_state_validate.c:549
 #17 nvc0_state_validate at ../src/gallium/drivers/nouveau/nvc0/nvc0_state_validate.c:933
 #18 nvc0_state_validate_3d at ../src/gallium/drivers/nouveau/nvc0/nvc0_state_validate.c:951
 #19 nvc0_draw_vbo at ../src/gallium/drivers/nouveau/nvc0/nvc0_vbo.c:1160
 #20 _mesa_draw_arrays at ../src/mesa/main/draw.c:1178
 #21 cogl_framebuffer_driver_draw_attributes at ../cogl/cogl/cogl-framebuffer-driver.c:114
 #22 _cogl_framebuffer_draw_attributes at ../cogl/cogl/cogl-framebuffer.c:2156
 #23 _cogl_journal_flush_modelview_and_entries at ../cogl/cogl/cogl-journal.c:326
 #24 batch_and_call at ../cogl/cogl/cogl-journal.c:274
 #27 _cogl_journal_flush_texcoord_vbo_offsets_and_entries at ../cogl/cogl/cogl-journal.c:553
 #28 batch_and_call at ../cogl/cogl/cogl-journal.c:267
 #30 _cogl_journal_flush_vbo_offsets_and_entries at ../cogl/cogl/cogl-journal.c:661
 #31 batch_and_call at ../cogl/cogl/cogl-journal.c:274
 #35 _cogl_journal_flush_viewport_and_entries at ../cogl/cogl/cogl-journal.c:1113
 #36 batch_and_call at ../cogl/cogl/cogl-journal.c:274
 #38 _cogl_journal_flush at ../cogl/cogl/cogl-journal.c:1462
 #39 cogl_onscreen_swap_buffers_with_damage at ../cogl/cogl/cogl-onscreen.c:290
 #40 swap_framebuffer at ../src/backends/meta-stage-impl.c:308
 #41 meta_stage_impl_redraw_view_primary at ../src/backends/meta-stage-impl.c:738
 #42 meta_stage_impl_redraw_view at ../src/backends/meta-stage-impl.c:819
 #43 meta_stage_native_redraw_view at ../src/backends/native/meta-stage-native.c:128
 #44 _clutter_stage_window_redraw_view at ../clutter/clutter/clutter-stage-window.c:78
 #45 handle_frame_clock_frame at ../clutter/clutter/clutter-stage-view.c:1095
 #46 clutter_frame_clock_dispatch at ../clutter/clutter/clutter-frame-clock.c:1549
 #47 frame_clock_source_dispatch at ../clutter/clutter/clutter-frame-clock.c:1584
 #49 g_main_context_dispatch_unlocked at ../glib/gmain.c:4249
 #50 g_main_context_iterate_unlocked at ../glib/gmain.c:4314
 #52 meta_context_run_main_loop at ../src/core/meta-context.c:576
 #53 ffi_call_unix64 at ../src/x86/unix64.S:104
 #54 ffi_call_int at ../src/x86/ffi64.c:673
 #55 ffi_call at ../src/x86/ffi64.c:710
 #56 Gjs::Function::invoke at ../gi/function.cpp:1050
 #57 Gjs::Function::call at /usr/include/mozjs-128/js/RootingAPI.h:616
 #58 CallJSNative at /usr/src/debug/mozjs128-128.8.1-1.fc42.x86_64/js/src/vm/Interpreter.cpp:481
 #59 js::InternalCallOrConstruct at /usr/src/debug/mozjs128-128.8.1-1.fc42.x86_64/js/src/vm/Interpreter.cpp:561
 #60 InternalCall at /usr/src/debug/mozjs128-128.8.1-1.fc42.x86_64/js/src/vm/Interpreter.cpp:642
 #61 js::CallFromStack at /usr/src/debug/mozjs128-128.8.1-1.fc42.x86_64/js/src/vm/Interpreter.cpp:647
 #62 js::Interpret at /usr/src/debug/mozjs128-128.8.1-1.fc42.x86_64/js/src/vm/Interpreter.cpp:3190
 #63 MaybeEnterInterpreterTrampoline at /usr/src/debug/mozjs128-128.8.1-1.fc42.x86_64/js/src/vm/Interpreter.cpp:395
 #64 js::RunScript at /usr/src/debug/mozjs128-128.8.1-1.fc42.x86_64/js/src/vm/Interpreter.cpp:453
 #65 js::InternalCallOrConstruct at /usr/src/debug/mozjs128-128.8.1-1.fc42.x86_64/js/src/vm/Interpreter.cpp:607
 #66 InternalCall at /usr/src/debug/mozjs128-128.8.1-1.fc42.x86_64/js/src/vm/Interpreter.cpp:642
 #67 js::Call at /usr/src/debug/mozjs128-128.8.1-1.fc42.x86_64/js/src/vm/Interpreter.cpp:674
 #68 JS::Call at /usr/src/debug/mozjs128-128.8.1-1.fc42.x86_64/js/src/vm/CallAndConstruct.cpp:119
 #70 GjsContextPrivate::run_main_loop_hook at ../gjs/context.cpp:1399
 #71 GjsContextPrivate::eval_module at ../gjs/context.cpp:1516
 #72 gjs_context_eval_module at ../gjs/context.cpp:1295
 #73 gjs_context_eval_module_file at ../gjs/context.cpp:1600


Potential duplicate: bug 1184963

Comment 1 OP 2025-04-17 02:01:00 UTC
Created attachment 2085352 [details]
File: proc_pid_status

Comment 2 OP 2025-04-17 02:01:01 UTC
Created attachment 2085353 [details]
File: maps

Comment 3 OP 2025-04-17 02:01:03 UTC
Created attachment 2085354 [details]
File: limits

Comment 4 OP 2025-04-17 02:01:04 UTC
Created attachment 2085355 [details]
File: environ

Comment 5 OP 2025-04-17 02:01:06 UTC
Created attachment 2085356 [details]
File: open_fds

Comment 6 OP 2025-04-17 02:01:07 UTC
Created attachment 2085357 [details]
File: mountinfo

Comment 7 OP 2025-04-17 02:01:08 UTC
Created attachment 2085358 [details]
File: os_info

Comment 8 OP 2025-04-17 02:01:10 UTC
Created attachment 2085359 [details]
File: cpuinfo

Comment 9 OP 2025-04-17 02:01:11 UTC
Created attachment 2085360 [details]
File: core_backtrace

Comment 10 OP 2025-04-17 02:01:13 UTC
Created attachment 2085361 [details]
File: exploitable

Comment 11 OP 2025-04-17 02:01:14 UTC
Created attachment 2085362 [details]
File: dso_list

Comment 12 OP 2025-04-17 02:01:16 UTC
Created attachment 2085363 [details]
File: var_log_messages

Comment 13 OP 2025-04-17 02:01:17 UTC
Created attachment 2085364 [details]
File: backtrace

Comment 14 Fedora Admin user for bugzilla script actions 2025-04-17 02:11:10 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 15 kaden.keep 2025-04-18 01:46:24 UTC
Allow the PC to sleep and fall into suspend mode (through the timeout, not manually triggered). On reawaken, this bug happens. Additionally, a monitor is connected to the nvidia RTX4050 HDMI port. This is almost always accompanied by: 
Bug 2360864 - [abrt] nouveau_channel_killed: WARNING: CPU: 12 PID: 10986 at ./include/linux/dma-fence.h:587 nouveau_fence_context_kill+0x91/0xa0 [nouveau] [nouveau]


reporter:       libreport-2.17.15
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=171bb93e19e54548a0372521ea7d785e;i=7876;b=b36b6af8e7c1468494ed980a24015979;m=4b5758b8;t=632f37d663960;x=bd1c042e8498b5cf
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.14.2-300.fc42.x86_64
package:        gnome-shell-48.1-1.fc42
runlevel:       N 5
backtrace_rating: 4
crash_function: pushbuf_dump

Comment 16 kaden.keep 2025-04-18 02:02:45 UTC
This error typically also occurs: 
This is a minor update (do not send email) Bug 2360868 - [abrt] nouveau_bo_move: WARNING: CPU: 6 PID: 10314 at drivers/gpu/drm/nouveau/nouveau_bo.c:1008 nouveau_bo_move_ntfy.part.0+0xea/0x150 [nouveau] [nouveau]

Comment 17 OP 2025-04-19 17:32:54 UTC
Gnome related url -->  https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/8119

New to the process.  At a huge disadvantage by not being able to get to a terminal where most things are done.

Comment 19 Alexander Schrøder 2025-05-12 06:55:12 UTC
This crash happened shortly after bringing my computer back from sleep and logging back into my account.


reporter:       libreport-2.17.15
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=77ad966067e84c299d9873c55869f40d;i=25d70;b=9005645fe3a84796963757f7d3defd4c;m=cb86a8cb;t=634ea9a91ee8b;x=eeedf6871baa6903
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.14.0-63.fc42.x86_64
package:        gnome-shell-48.0-1.fc42
runlevel:       N 5
dso_list:       /usr/bin/gnome-shell gnome-shell-48.0-1.fc42.x86_64 (Fedora Project) 1744200904
backtrace_rating: 4
crash_function: pushbuf_dump
comment:        This crash happened shortly after bringing my computer back from sleep and logging back into my account.

Comment 20 Nexcool 2025-06-24 14:08:41 UTC
The laptop went to sleep and came back with this error. 


reporter:       libreport-2.17.15
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=c3ad6792ff094ea1a66f5edb0d737822;i=d205;b=2057f49143f04de386e645420496298a;m=12454e29f;t=63851bca52288;x=4c6c8dd9fe71d9be
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.14.11-300.fc42.x86_64
package:        gnome-shell-48.2-1.fc42
runlevel:       N 5
dso_list:       /usr/bin/gnome-shell gnome-shell-48.2-1.fc42.x86_64 (Fedora Project) 1750713368
backtrace_rating: 4
crash_function: pushbuf_dump
comment:        The laptop went to sleep and came back with this error.

Comment 21 johau17 2025-07-15 11:11:00 UTC
opening the new shell application
Sometimes also installing an application from the store


reporter:       libreport-2.17.15
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=186642b0b2e1498faa2152a04451cf04;i=ff2;b=a3dff38ca81d4465826367e35fb7ae7d;m=77cf295;t=6372c03991af0;x=71ec9e80f344bb4e
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.14.0-63.fc42.x86_64
package:        gnome-shell-48.0-1.fc42
runlevel:       N 5
backtrace_rating: 4
crash_function: pushbuf_dump

Comment 22 Gabriel M. Beddingfield 2025-11-12 03:50:24 UTC
I wasn't doing anything special. I had the browser open with a couple of tabs. A crash like this has happened a few times today.


reporter:       libreport-2.17.15
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=d2634b869dbe47c19cde0071e09ec42b;i=18c80548a;b=25b4745165b64293b5d151c1cc572ffd;m=17883b7c;t=6435592267f74;x=d6bb3edd786af773
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.17.7-200.fc42.x86_64
package:        gnome-shell-48.6-1.fc42
runlevel:       N 5
backtrace_rating: 4
crash_function: pushbuf_dump
comment:        I wasn't doing anything special. I had the browser open with a couple of tabs. A crash like this has happened a few times today.

Comment 23 Gabriel M. Beddingfield 2025-11-15 18:31:10 UTC
I was using the Google chrome browser, but other than that wasn't doing anything noticeable.


reporter:       libreport-2.17.15
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=d2634b869dbe47c19cde0071e09ec42b;i=18d8b6288;b=a12fdf2e585e4055b55297fc7f165a3c;m=4447d6bf;t=643a62935e1ab;x=84f87e6d40285c70
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.17.7-200.fc42.x86_64
package:        gnome-shell-48.6-1.fc42
runlevel:       N 5
backtrace_rating: 4
crash_function: pushbuf_dump
comment:        I was using the Google chrome browser, but other than that wasn't doing anything noticeable.

Comment 24 Gabriel M. Beddingfield 2025-11-16 23:15:13 UTC
I was running OBS studio, recording a video unattended. No browser was up.

I've been having this kind of crash like... multiple times a day. I was using Wayland. This crash was with Xorg.


reporter:       libreport-2.17.15
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=d2634b869dbe47c19cde0071e09ec42b;i=18d8c51e2;b=a12fdf2e585e4055b55297fc7f165a3c;m=15ba5a96bd;t=643bb9f48a1a9;x=f9b553ebe8ab5651
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.17.7-200.fc42.x86_64
package:        gnome-shell-48.6-1.fc42
runlevel:       N 5
backtrace_rating: 4
crash_function: pushbuf_dump

Comment 25 Fedora Release Engineering 2026-05-06 12:37:11 UTC
This message is a reminder that Fedora Linux 42 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 42 on 2026-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 '42'.

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 42 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.


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