Bug 2185059

Summary: [abrt] gnome-shell: on_swap_buffer_update_result(): gnome-shell killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Oleh Horbachov <gorbyo>
Component: gnome-shellAssignee: Florian Müllner <fmuellner>
Status: NEW --- QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 38CC: adscvr, ckoep, fmuellner, gnome-sig, gorbyo, jadahl, otaylor, philip.wyett
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/ae5ff5b90c0f0374c486454dad7d6939af15a14
Whiteboard: abrt_hash:f47359e1e48ccecf5baab711e04f2ffc4fb89d00;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: proc_pid_status
none
File: maps
none
File: limits
none
File: environ
none
File: open_fds
none
File: mountinfo
none
File: os_info
none
File: cpuinfo
none
File: core_backtrace
none
File: exploitable
none
File: var_log_messages
none
File: backtrace none

Description Oleh Horbachov 2023-04-06 17:18:39 UTC 
Version-Release number of selected component:
gnome-shell-44.0-4.fc38

Additional info:
reporter:       libreport-2.17.9
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=a8a64cb89572407fab36caaa45c513b0;i=d320;b=1c78fa1ebd46409ca0f0ddf8ec779ef5;m=27bcc0cad;t=5f89677b6bf82;x=fd632030e225c429
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.9-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) 1680620931
backtrace_rating: 4
crash_function: on_swap_buffer_update_result

Truncated backtrace:
Thread no. 1 (5 frames)
 #0 on_swap_buffer_update_result at ../src/backends/native/meta-onscreen-native.c:1041
 #2 flush_callbacks.isra.0 at ../src/backends/native/meta-kms.c:261
 #3 callback_idle at ../src/backends/native/meta-kms.c:277
 #7 g_main_context_iterate.isra.0 at ../glib/gmain.c:4276
 #9 meta_context_run_main_loop at ../src/core/meta-context.c:482
Comment 1 Oleh Horbachov 2023-04-06 17:18:43 UTC 
Created attachment 1956118 [details]
File: proc_pid_status
Comment 2 Oleh Horbachov 2023-04-06 17:18:44 UTC 
Created attachment 1956119 [details]
File: maps
Comment 3 Oleh Horbachov 2023-04-06 17:18:46 UTC 
Created attachment 1956120 [details]
File: limits
Comment 4 Oleh Horbachov 2023-04-06 17:18:47 UTC 
Created attachment 1956121 [details]
File: environ
Comment 5 Oleh Horbachov 2023-04-06 17:18:49 UTC 
Created attachment 1956122 [details]
File: open_fds
Comment 6 Oleh Horbachov 2023-04-06 17:18:50 UTC 
Created attachment 1956123 [details]
File: mountinfo
Comment 7 Oleh Horbachov 2023-04-06 17:18:52 UTC 
Created attachment 1956124 [details]
File: os_info
Comment 8 Oleh Horbachov 2023-04-06 17:18:53 UTC 
Created attachment 1956125 [details]
File: cpuinfo
Comment 9 Oleh Horbachov 2023-04-06 17:18:55 UTC 
Created attachment 1956126 [details]
File: core_backtrace
Comment 10 Oleh Horbachov 2023-04-06 17:18:56 UTC 
Created attachment 1956127 [details]
File: exploitable
Comment 11 Oleh Horbachov 2023-04-06 17:18:57 UTC 
Created attachment 1956128 [details]
File: var_log_messages
Comment 12 Oleh Horbachov 2023-04-06 17:18:59 UTC 
Created attachment 1956129 [details]
File: backtrace
Comment 13 Jonas Ådahl 2023-04-06 19:49:59 UTC 
Do you know what led up to this crash? Anything like fullscreening a window, suspending/resuming, locking the screen, etc?
Comment 14 Oleh Horbachov 2023-04-07 05:51:43 UTC 
Looks the crash happened after suspending/resuming laptop
Comment 15 Jacob Emcken 2023-04-12 06:02:01 UTC 
Either my laptop was suspending or waking from suspend (several hours later) when the problem occured.
My laptop was attached to a docking station and the monitors had been turned off right after I suspended the laptop.

Attaching and detaching monitors sometimes trigger weird behavior (both crashes and pictures from one monitor showing up on another monitor)...


reporter:       libreport-2.17.9
rootdir:        /
type:           CCpp
package:        gnome-shell-44.0-4.fc38
reason:         gnome-shell killed by SIGSEGV
runlevel:       N 5
cmdline:        /usr/bin/gnome-shell
uid:            1000
journald_cursor: s=a9b1e29d1d9944bf8323867555d1e7dc;i=e1054;b=d8a97cf82da64b44aeb042702d6d927a;m=2322813b4;t=5f91d02ec224a;x=d3806f7fd27e94e3
crash_function: on_swap_buffer_update_result
kernel:         6.2.10-300.fc38.x86_64
backtrace_rating: 4
executable:     /usr/bin/gnome-shell
dso_list:       /usr/bin/gnome-shell gnome-shell-44.0-4.fc38.x86_64 (Fedora Project) 1680269843
Comment 16 Benny 2023-04-21 18:17:37 UTC 
1. login to account
2. plug in an USB-C AltMode external screen
3. External screen shows up
4 start moving the mouse
5. After a few seconds the mousepointer disapear
6. External screen blinks and disapear


reporter:       libreport-2.17.9
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=006ec72a410042cdba863696b11b4b97;i=16f80;b=40ddd0b8fd254fbf82679999fbac6290;m=ce93937c;t=5f9c99a658daf;x=fc650e00edc72a7
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
backtrace_rating: 4
crash_function: on_swap_buffer_update_result
Comment 17 FedoraHat 2023-05-07 09:05:57 UTC 
Suspended laptop and powered back on. GNOME desktop crashed loosing all open apps and unsaved documents.


reporter:       libreport-2.17.9
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=cb72badc0bf84bb19e8082cf67c35e13;i=2be79;b=d4437461eb5846eb92fcc686bac4275a;m=854a0082c;t=5fb169bcf0c04;x=347190bc2ad1763f
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: on_swap_buffer_update_result
comment:        Suspended laptop and powered back on. GNOME desktop crashed loosing all open apps and unsaved documents.
Comment 18 M. Merklinger 2023-05-09 20:36:51 UTC 
The computer was suspended. After coming back from suspend (opening the lid) it didn't show me the lockscreen, but the login manager. If I remember correct there were two Gnome sessions running before the suspend (one locked; account switch).


reporter:       libreport-2.17.9
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=7e20d1102e0a4c84aee515be2aa44067;i=104d37;b=557c69ece4dc40ffb7d6fdea47ee9819;m=62e0caf4c;t=5fb3e38b7c29e;x=91890d7f4e623c62
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: on_swap_buffer_update_result
comment:        The computer was suspended. After coming back from suspend (opening the lid) it didn't show me the lockscreen, but the login manager. If I remember correct there were two Gnome sessions running before the suspend (one locked; account switch).
Comment 19 Gabriele Turchi 2023-05-13 18:45:06 UTC 
Back from suspend.


reporter:       libreport-2.17.9
runlevel:       N 5
uid:            1000
type:           CCpp
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell
executable:     /usr/bin/gnome-shell
backtrace_rating: 4
rootdir:        /
crash_function: on_swap_buffer_update_result
reason:         gnome-shell killed by SIGSEGV
package:        gnome-shell-44.1-1.fc38
kernel:         6.2.14-300.fc38.x86_64
journald_cursor: s=c755710659c043c6a7c542910487e2f5;i=194eb4;b=5e3aeef270b14aa9b8cea9ecd2e317c3;m=9e19b9817;t=5fb97543f5766;x=96b59aae49c23a0b
cmdline:        /usr/bin/gnome-shell
comment:        Back from suspend.
Comment 20 John Zamoider 2023-05-19 12:30:05 UTC 
This hour was reported 10 hours ago.
I have not touched my computer for over 24 hours.

I did do an update on my steamdeck however, and it did grab data files from Steam on this computer. Might be worth looking into.


reporter:       libreport-2.17.10
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=0853fa1423cb461a944f42a959656105;i=42d39;b=fd98e61d14524ec3916b9ccb3038f1b5;m=286ed3d6f2;t=5fc01d5eeb5cf;x=52a22c5212fd6438
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.15-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) 1683586319
backtrace_rating: 4
crash_function: on_swap_buffer_update_result
Comment 21 Tim Waugh 2023-05-23 22:22:45 UTC 
Resumed from suspend


reporter:       libreport-2.17.10
rootdir:        /
kernel:         6.2.15-300.fc38.x86_64
type:           CCpp
cmdline:        /usr/bin/gnome-shell
crash_function: on_swap_buffer_update_result
comment:        Resumed from suspend
backtrace_rating: 4
package:        gnome-shell-44.1-1.fc38
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=d6a1c99bf81a410b85bfca856285f5a4;i=12d707;b=308e8e4f1c2148b8bb8f5af6f16c448f;m=101f4c809e;t=5fc63c9431c6a;x=aa7af730fda54621
runlevel:       N 5
uid:            1000
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell
executable:     /usr/bin/gnome-shell
Comment 22 Per Jonsson 2023-05-25 05:51:03 UTC 
Have a connected screen to a ThinkPad P1 thru a ThinkPad Hub, closed lid on the laptop and when screen locks session dies.


reporter:       libreport-2.17.10
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=e192a4644db14c9e81f75e8b2c452676;i=b9a43;b=321abe1d435445e9a378a8aae54c7f42;m=45078d1f;t=5fc7e186dba0e;x=42c73fdf37dd19a8
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.15-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) 1682672743
backtrace_rating: 4
crash_function: on_swap_buffer_update_result
comment:        Have a connected screen to a ThinkPad P1 thru a ThinkPad Hub, closed lid on the laptop and when screen locks session dies.
Comment 23 Johannes M. 2023-05-26 11:51:37 UTC 
This behaviour occurs if the system was idle for approx. 1.5 hours. Leaving the DisplayPort (1.4) connected 4k Monitor to switch off after a while.

Steps to reproduce:
1 Log in to a gnome shell session
2 Lock the shell and wait for 1.5 hours
3 Waking everything up by pressing CTRL key


reporter:       libreport-2.17.10
executable:     /usr/bin/gnome-shell
package:        gnome-shell-44.1-1.fc38
runlevel:       N 5
kernel:         6.2.15-300.fc38.x86_64
dso_list:       /usr/bin/gnome-shell gnome-shell-44.1-1.fc38.x86_64 (Fedora Project) 1684754259
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell
crash_function: on_swap_buffer_update_result
rootdir:        /
type:           CCpp
uid:            1000
backtrace_rating: 4
reason:         gnome-shell killed by SIGSEGV
cmdline:        /usr/bin/gnome-shell
journald_cursor: s=ab27c21e60494a979af18d56555f135b;i=1deca;b=7757c80da292455c81e20bcf32c7c3ec;m=3318c24f9;t=5fc96d5a3aa22;x=fdfa2862ec694cd4
Comment 24 Stefano Cirelli 2023-05-29 15:45:38 UTC 
I was simply filling a form in Google Maps review, when suddenly all the desktop environment disappered and no activity on the pc, like it was suspended. I then hit the spacebar on the keyboard, and the login screen appeared again.


reporter:       libreport-2.17.10
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=daea108aa7b84082bb262294b52bad7a;i=d885;b=918dc01b91c24890a6f07f85d9888372;m=22a240c7;t=5fcd6bf3e51e7;x=72b32d7d24a2255a
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.15-300.fc38.x86_64
package:        gnome-shell-44.1-1.fc38
runlevel:       N 5
backtrace_rating: 4
crash_function: on_swap_buffer_update_result
comment:        I was simply filling a form in Google Maps review, when suddenly all the desktop environment disappered and no activity on the pc, like it was suspended. I then hit the spacebar on the keyboard, and the login screen appeared again.
Comment 25 Gina Häußge 2023-05-30 16:32:56 UTC 
I sadly cannot give reproduction steps.

I went away from my desk, the laptop went to sleep (deepsleep, not s2idle). I came back an hour later, woke the laptop up, Gnome Shell crashed and I found the error entry in the log. However, sleep cycles in general work, this doesn't seem to happen in any reproducible kind of way.


reporter:       libreport-2.17.10
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=6c36ab6cb2274c75be5287705065b7db;i=180067c;b=84eabf81ba4e4c4ab1c693a7aaabb18e;m=158abe5ffa;t=5fceb7e49e97b;x=763685efaf2a2600
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.15-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) 1684743179
backtrace_rating: 4
crash_function: on_swap_buffer_update_result
Comment 26 Martin Garton 2023-06-05 15:40:50 UTC 
Shortly after unlocking the screen after inactivity, it unexpectedly went blank and I could no longer see either the lock screen or the unlocked desktop, and pressing keys etc did nothing.  I was using an external screen connected to my (closed) laptop via a usb dock. 

I did the following:
1) I opened my laptop lid and disconnected the external dock from my laptop to see if anything was displayed on the internal screen.  The internal screen showed the unlocked desktop.
2) I re-connected the dock, and shortly after both screens were active as expected
3) I closed the laptop lid in order to enable only the external screen
4) The external screen went blank again.
5) I suspended and resumed the laptop via the button on the dock (as a random attempt to fix the issue)

A few seconds later the external screen turned on and was back at the login screen, gnome-shell having apparently crashed while it was off.


reporter:       libreport-2.17.10
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=2aa74e80063d433398a5389a5967f18c;i=2d93c0;b=6bf6123ea5e240c797b46c7bbc1b4f99;m=29acd10a0;t=5fd6288ea6a87;x=267b89d4fa0e0c73
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) 1682583217
backtrace_rating: 4
crash_function: on_swap_buffer_update_result
Comment 27 j 2023-06-29 14:30:28 UTC 
resuming from suspend


reporter:       libreport-2.17.10
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=df0a344d9a1f4b6cbad2f23d478b4f29;i=2da898;b=99e7761f84454b5b917f37f7c5d048d0;m=62bcf47dd;t=5ff456fd8d7c4;x=5f0314411d6be879
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: on_swap_buffer_update_result
comment:        resuming from suspend
Comment 28 M. Merklinger 2023-06-30 07:57:12 UTC 
The computer was on sleep, when I opened the lid.
I didn't see the look screen as usual, but instead a black screen was shown.
As nothing happened within a few seconds I pressed CTRL+ALT+F1.
This brought me back to GDM, and I was able to login.

Maybe worth to mention that the computer was before on a docking station (Lenovo USB-C Dock Gen2).

I have no deterministic way to reproduce this problem. It happens only once in a while.


reporter:       libreport-2.17.10
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=37ddbd5f4d144aed83a0acf42da0ae5b;i=1dd159;b=cd9a47a2fda04e6abd9773e73ecf9e9d;m=e896dd756;t=5ff53e0a35327;x=c1c1062ef7d47261
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
dso_list:       /usr/bin/gnome-shell gnome-shell-44.2-1.fc38.x86_64 (Fedora Project) 1686426792
backtrace_rating: 4
crash_function: on_swap_buffer_update_result
Comment 29 Gerald Rapior 2023-07-09 15:17:45 UTC 
Don't wake up after the system goes to sleeping mode.


reporter:       libreport-2.17.11
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=a0a22de9bf71489abe7c00588dc5f0f5;i=337e7e;b=9eda651006064f93a42be15c12c8537c;m=46d5dc794;t=6000f2cf2b3ba;x=2a67d43e6877c980
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.11-200.fc38.x86_64
package:        gnome-shell-44.2-1.fc38
runlevel:       N 5
backtrace_rating: 4
crash_function: on_swap_buffer_update_result
comment:        Don't wake up after the system goes to sleeping mode.
Comment 30 hinrek 2023-07-18 05:47:42 UTC 
* I had Firefox and terminal open
* I pressed Suspend from the power menu in Gnome
* I went to sleep and when i came back gnome-shell had crashed


reporter:       libreport-2.17.11
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=59298859d9144ede93a1be1744a8685d;i=5e63;b=d62e937551d4460780253a5c7bb4a488;m=b8139f73;t=600b1fae8f3a7;x=294ba7371668de98
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.12-200.fc38.x86_64
package:        gnome-shell-44.2-1.fc38
runlevel:       N 5
backtrace_rating: 4
crash_function: on_swap_buffer_update_result
Comment 31 M. Merklinger 2023-07-19 08:46:54 UTC 
Unplugged the laptop from the docking station, then opened the lid.
Instead of the lockscreen it showed me the login screen.


reporter:       libreport-2.17.11
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=07568b0761a64caea9a72db866d0144b;i=293d40;b=6a8297f3ec6b418da9fede3c56393bdf;m=c03edfbe5;t=600d2656ab05d;x=a8175d8e3cc84ae
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.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) 1686426792
backtrace_rating: 4
crash_function: on_swap_buffer_update_result
Comment 32 Gina Häußge 2023-07-25 16:19:02 UTC 
I have not found a way to reliably reproduce this issue, but when it happens, it happens right after resume.

This is on a Framework 13 with an 11th gen Intel board and internal graphics. There are three external monitors attached and the lid is closed.

It happens often enough that it is very much annoying, sometimes several times per day.


reporter:       libreport-2.17.10
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=af9bd26b42bb465faded85330ec5bce3;i=529120e;b=a7953d77634b48ecab3d97d225d7aa68;m=19122bc5f9;t=600f0faa2f229;x=fa102f127052d7c6
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: on_swap_buffer_update_result
Comment 33 rwp.cpe 2023-08-03 15:38:50 UTC 
I closed the lid of my Dell XPS 15 9530 (2023) laptop and when I went to open it, the computer wouldn't do anything at all. Once it finally did, I got this alert about it crashing.


reporter:       libreport-2.17.11
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=2031e9229b8941d4ab96c08ba5d1fe5e;i=983b5;b=1778efb617ce4dae9aac760e83b1646b;m=8d0065979;t=602060b977963;x=b2da0dd8180e748
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
dso_list:       /usr/bin/gnome-shell gnome-shell-44.3-1.fc38.x86_64 (Fedora Project) 1690207428
backtrace_rating: 4
crash_function: on_swap_buffer_update_result
comment:        I closed the lid of my Dell XPS 15 9530 (2023) laptop and when I went to open it, the computer wouldn't do anything at all. Once it finally did, I got this alert about it crashing.