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
Created attachment 1956118 [details] File: proc_pid_status
Created attachment 1956119 [details] File: maps
Created attachment 1956120 [details] File: limits
Created attachment 1956121 [details] File: environ
Created attachment 1956122 [details] File: open_fds
Created attachment 1956123 [details] File: mountinfo
Created attachment 1956124 [details] File: os_info
Created attachment 1956125 [details] File: cpuinfo
Created attachment 1956126 [details] File: core_backtrace
Created attachment 1956127 [details] File: exploitable
Created attachment 1956128 [details] File: var_log_messages
Created attachment 1956129 [details] File: backtrace
Do you know what led up to this crash? Anything like fullscreening a window, suspending/resuming, locking the screen, etc?
Looks the crash happened after suspending/resuming laptop
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
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
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.
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).
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.
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
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
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.
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
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.
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
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
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
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
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.
* 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
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
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
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.
Screen went to sleep after idle lock. Upon moving the mouse, the lock screen briefly appeared, followed by a crash. reporter: libreport-2.17.11 type: CCpp reason: gnome-shell killed by SIGSEGV journald_cursor: s=c4680780f7f148e0ad3823c55165f34a;i=4abb83;b=9891fe329d484d928f8fbb8980006bc8;m=1eae95203;t=6038823631118;x=e760aa850bf35568 executable: /usr/bin/gnome-shell cmdline: /usr/bin/gnome-shell cgroup: 0::/user.slice/user-1972012866.slice/user/session.slice/org.gnome.Shell rootdir: / uid: 1972012866 kernel: 6.4.11-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) 1689856677 comment: Screen went to sleep after idle lock. Upon moving the mouse, the lock screen briefly appeared, followed by a crash. backtrace_rating: 4 crash_function: on_swap_buffer_update_result
I suspended then resumed my laptop reporter: libreport-2.17.11 type: CCpp reason: gnome-shell killed by SIGSEGV journald_cursor: s=88ee0ddbedca4b0a8cae7732c60f25c7;i=1a259a;b=ede54111fbd342179b48bc2b1948cf4a;m=12f7a5f602;t=6040fb945944e;x=a08d306df481dd2d 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.12-200.fc38.x86_64 package: gnome-shell-44.4-1.fc38 runlevel: N 5 dso_list: /usr/bin/gnome-shell gnome-shell-44.4-1.fc38.x86_64 (Fedora Project) 1693003629 backtrace_rating: 4 crash_function: on_swap_buffer_update_result comment: I suspended then resumed my laptop
The problem occurs with a Thinkpad T490 in conjunction with a Lenovo Thunderbolt 3/4 universal dock, model 40B0. It can be reproduced in most cases by: 1. Having the laptop connected to the dock, waiting for everything to reach "steady state" 2. Suspending the laptop 3. Disconnecting the dock from the laptop while the laptop is suspended 4. Resuming the laptop The lock screen might be briefly visible, then the screen turns black for a brief moment and you get a similar screen. This similar screen though is the login manager, not the lockscreen anymore, as gnome-shell has crashed at this point. I am not sure about the factor that makes the crash happen in "most cases" - maybe it is the timing, either on the suspend-and-disconnect side, or on the wakeup side, maybe when interacting with the system too fast after resume. reporter: libreport-2.17.11 dso_list: /usr/bin/gnome-shell gnome-shell-44.5-1.fc38.x86_64 (Fedora Project) 1695368754 package: gnome-shell-44.5-1.fc38 rootdir: / runlevel: N 5 uid: 1000 executable: /usr/bin/gnome-shell cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell type: CCpp cmdline: /usr/bin/gnome-shell journald_cursor: s=8549574e714b468f8d62a3c321a53652;i=93f6f;b=4cedc11d7f6a40878371e2687e8a3158;m=194f714d;t=60966f21e2db6;x=7957e68b966b4381 backtrace_rating: 4 kernel: 6.5.8-200.fc38.x86_64 reason: gnome-shell killed by SIGSEGV crash_function: on_swap_buffer_update_result
Openned laptop lid to wake from sleep. Screen brightness was turned all the way down (this is a regular occurence). I hit F6 (which is the screen brightness increase button and all of a sudden I saw a text buffer with (ostensibly) the ASCII equivalent for the screen brightness key being printed. reporter: libreport-2.17.11 type: CCpp reason: gnome-shell killed by SIGSEGV journald_cursor: s=b22190be914840e5a5aaaf81a515a617;i=2b2c8d;b=42ee3888f7af4bf2aefe21c62a5ee2f5;m=35877489b;t=6099ad8a0a658;x=18136351005a7b51 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.5.9-200.fc38.x86_64 package: gnome-shell-44.6-1.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: on_swap_buffer_update_result
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!
1 - run command "sudo dnf update" 2 - fedora download and install updates 3 - run command "sudo rebbot now" 4 - system reboot and when it loads my secondaries screens didn't work and the system crash. reporter: libreport-2.17.11 type: CCpp reason: gnome-shell killed by SIGSEGV journald_cursor: s=3c347a0aae064341984961b35ef4dde4;i=18c944;b=58f1299235fc435da88da005db321ea6;m=b5c770c;t=60c629e71591d;x=9eac5ed30665633f 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.6.4-100.fc38.x86_64 package: gnome-shell-44.6-1.fc38 runlevel: N 5 dso_list: /usr/bin/gnome-shell gnome-shell-44.6-1.fc38.x86_64 (Fedora Project) 1698942385 backtrace_rating: 4 crash_function: on_swap_buffer_update_result
1 - I installed the updates from Fedora on January 29th using the quick install on power off 2 - After the updated is completed the computer shutdown. 3 - Then I turn it on again to boot the first time after the update. 4 - Was in this time that the problem happens. My seconds screens didn't work and gnome shell was very slow. reporter: libreport-2.17.11 type: CCpp reason: gnome-shell killed by SIGSEGV journald_cursor: s=3c347a0aae064341984961b35ef4dde4;i=26a45b;b=4b9451717e074856971712989265a460;m=9a2a0ed;t=61028053d78d4;x=6ff57fff7bad4c26 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.6.13-100.fc38.x86_64 package: gnome-shell-44.8-1.fc38 runlevel: N 5 dso_list: /usr/bin/gnome-shell gnome-shell-44.8-1.fc38.x86_64 (Fedora Project) 1705525666 backtrace_rating: 4 crash_function: on_swap_buffer_update_result
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.
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 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.