Created attachment 2030566 [details]
File: proc_pid_status

Created attachment 2030567 [details]
File: maps

Created attachment 2030568 [details]
File: limits

Created attachment 2030569 [details]
File: environ

Created attachment 2030570 [details]
File: open_fds

Created attachment 2030571 [details]
File: mountinfo

Created attachment 2030572 [details]
File: os_info

Created attachment 2030573 [details]
File: cpuinfo

Created attachment 2030574 [details]
File: core_backtrace

Created attachment 2030575 [details]
File: dso_list

Created attachment 2030576 [details]
File: backtrace

gnome on wayland just quit.


reporter:       libreport-2.17.15
type:           CCpp
reason:         gnome-session-binary killed by SIGABRT
journald_cursor: s=ad5af7c780944ed3a589b39c7cc93adc;i=1ac7ea2;b=b069fa699aec4898840aede105d39eda;m=161a49d7;t=617acf23af900;x=9906588c01a48a1c
executable:     /usr/libexec/gnome-session-binary
cmdline:        /usr/libexec/gnome-session-binary --systemd-service --session=gnome
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-gnome\x2dsession\x2dmanager.slice/gnome-session-manager
rootdir:        /
uid:            1000
kernel:         6.8.8-300.fc40.x86_64
package:        gnome-session-46.0-1.fc40
runlevel:       N 5
backtrace_rating: 4
crash_function: __poll
comment:        gnome on wayland just quit.

Systematic crash on reboot


reporter:       libreport-2.17.15
type:           CCpp
reason:         gnome-session-binary killed by SIGABRT
journald_cursor: s=1edb02d54ace45319dbb1079ebc35a09;i=119018d;b=094ea2ffa24e46faa08e604488d2c231;m=543d467;t=61ab753f5b33a;x=c96eb83142139905
executable:     /usr/libexec/gnome-session-binary
cmdline:        /usr/libexec/gnome-session-binary --systemd-service --session=gnome
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-gnome\x2dsession\x2dmanager.slice/gnome-session-manager
rootdir:        /
uid:            1000
kernel:         6.8.11-300.fc40.x86_64
package:        gnome-session-46.0-1.fc40
runlevel:       N 5
backtrace_rating: 4
crash_function: __poll
comment:        Systematic crash on reboot

I launched the Software app;
I clicked on the Download button to download updates;
I clicked on the Update button at the top left corner to refresh updates (the previous download hasn't been finished yet);


Before that I was trying to log out. I clicked on the logout button a few times (before going to the Software app to run the updates) and nothing happened, that's when I decided to run the updates.


reporter:       libreport-2.17.15
rootdir:        /
uid:            1000
crash_function: __poll
backtrace_rating: 4
kernel:         6.9.4-200.fc40.x86_64
type:           CCpp
package:        gnome-session-46.0-1.fc40
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-gnome\x2dsession\x2dmanager.slice/gnome-session-manager
cmdline:        /usr/libexec/gnome-session-binary --systemd-service --session=gnome
executable:     /usr/libexec/gnome-session-binary
journald_cursor: s=7911aff0dba8479aa80734ccc827edc2;i=70cb;b=2b4189c8d8c64344baaefd8b699dc0be;m=41057ebe;t=61b61827e98f6;x=41a5f267f3714bd7
runlevel:       N 5
reason:         gnome-session-binary killed by SIGABRT

Since upgrading to Fedora 40 the suspend functionality does no longer work coorectly on my PC.  Computer get's into suspend mode but recovering from it seems impossible after an extended period of time (couple of hours). Not sure if this error is related to it, but it's the only anomaly I can report. 


reporter:       libreport-2.17.15
type:           CCpp
reason:         gnome-session-binary killed by SIGABRT
journald_cursor: s=1c366c1f33fc489a88739aa624fdf438;i=48b952;b=9e3936819013467487d52c86a685bf0f;m=154da5040;t=61bb62294c307;x=749f76b5dd49bf27
executable:     /usr/libexec/gnome-session-binary
cmdline:        /usr/libexec/gnome-session-binary --systemd-service --session=gnome
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-gnome\x2dsession\x2dmanager.slice/gnome-session-manager
rootdir:        /
uid:            1000
kernel:         6.8.11-300.fc40.x86_64
package:        gnome-session-46.0-1.fc40
runlevel:       N 5
backtrace_rating: 4
crash_function: __poll
comment:        Since upgrading to Fedora 40 the suspend functionality does no longer work coorectly on my PC.  Computer get's into suspend mode but recovering from it seems impossible after an extended period of time (couple of hours). Not sure if this error is related to it, but it's the only anomaly I can report.

My screen went idle, then would not come back online when I returned. The keyboard still lit up. When I pressed the power button, the PC shut down as configured in System Settings.


reporter:       libreport-2.17.15
type:           CCpp
reason:         gnome-session-binary killed by SIGABRT
journald_cursor: s=7d76686de3fc4cda9dc475c5ebb49e47;i=10f5e;b=8f131185ba62413885f97bac04d2f031;m=215bc32f;t=61e324ba0f2b9;x=d0d2e8de66a5a82d
executable:     /usr/libexec/gnome-session-binary
cmdline:        /usr/libexec/gnome-session-binary --systemd-service --session=gnome
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-gnome\x2dsession\x2dmanager.slice/gnome-session-manager
rootdir:        /
uid:            1000
kernel:         6.9.10-200.fc40.x86_64
package:        gnome-session-46.0-1.fc40
runlevel:       N 5
backtrace_rating: 4
crash_function: __poll
comment:        My screen went idle, then would not come back online when I returned. The keyboard still lit up. When I pressed the power button, the PC shut down as configured in System Settings.

This crash randomly happens while running the following command:

flatpak-builder --user --install --force-clean --verbose \
  build-dir \
  com.vysp3r.ProtonPlus.local.yml

With the code from this repo:

https://github.com/Vysp3r/ProtonPlus

I have seen this desktop session crash about 10 times today, always during the flatpak-builder process.


reporter:       libreport-2.17.15
type:           CCpp
reason:         gnome-session-ctl killed by SIGABRT
journald_cursor: s=6584f734b8cc4b46bbf3031bbd7ca56f;i=1bf9560;b=2ee6737b1b1444c6bb2641c59ed59c2f;m=37204f1896;t=62172c71f4c0c;x=f463502b0c78469e
executable:     /usr/libexec/gnome-session-ctl
cmdline:        /usr/libexec/gnome-session-ctl --monitor
rootdir:        /
uid:            1000
kernel:         6.10.6-200.fc40.x86_64
package:        gnome-session-46.0-1.fc40
runlevel:       N 5
backtrace_rating: 4
crash_function: __poll

I forgot some more details:

- The crash happens on both X11 and Wayland.
- Anyone who encounters the crash can just wait. After like half a minute, the black screen will change into the GNOME Login screen due to GNOME's own crash recovery.

Now I know that the problem I was experiencing was a BUG (regression) in Kernel 6.10.x.

- Bug 1: Data corruption in FUSE filesystems: https://lore.kernel.org/linux-fsdevel/792a3f54b1d528c2b056ae3c4ebaefe46bca8ef9.camel@bitron.ch/
- Bug 2: Data corruption in CIFS filesystems: https://lore.kernel.org/linux-mm/g87scjlif3eaff02i2u2kstullto3erb95@sonic.net/T/
- Bug 3: NVIDIA broken: https://www.gamingonlinux.com/2024/08/nvidia-driver-with-linux-kernel-6-10-causing-kernel-oops/
- Bug 4: AMD broken: https://discussion.fedoraproject.org/t/amd-apu-regression-full-halt-on-kernel-6-10-how-to-best-report/128404/4

Kernel 6.10 is a piece of crap.

Here are my instructions for installing the last available non-broken Linux kernel (6.9.x series) on Fedora 40:

```sh
GET_VERSION=6.9.12-200.fc40
sudo dnf install koji
mkcd ~/Downloads/Kernel
koji download-build --arch=x86_64 --arch=noarch kernel-${GET_VERSION}
rm -fv *debug*.rpm *uki*.rpm
rm -fv bpftool*.rpm kernel-doc*.rpm kernel-modules-internal-*.rpm kernel-selftests-internal-*.rpm kernel-tools-*.rpm libperf*.rpm perf*.rpm python*perf*.rpm rtla*.rpm rv-*.rpm

# Verify what's installed and will be installed.
sudo dnf list --installed | grep '^kernel' | cut -d' ' -f1 | sort -u
ls -alh

# Install.
sudo dnf install ./kernel-*

# Force rebuild of kernel modules (such as NVIDIA driver) for that kernel.
# Be patient. It may appear to not do anything for a while.
sudo akmods --force --rebuild --kernels ${GET_VERSION}.x86_64
```

- Reboot and ensure that the older kernel is chosen at boot.
- Verify after login that it's active:

```sh
uname -r
```

- Optionally remove every kernel except 6.9.12 (don't proceed if this gives an error/warning because that means you're attempting to remove the currently used kernel):

```sh
KEEP_VERSION=6.9.12
sudo dnf repoquery --installonly -q | grep -Fv ":${KEEP_VERSION}-" | xargs --delimiter='\n' --no-run-if-empty --open-tty sudo dnf rm --
```

- Now avoid kernel updates until kernel 6.11 is out with fixes. To avoid those, you can upgrade in a terminal like this, which runs the same process as GNOME Software would:

```sh
sudo dnf offline-upgrade download --refresh --exclude="kernel-*"
sudo dnf offline-upgrade reboot
```

If someone is on Fedora 39 and wants to downgrade too, change the first line of the shell commands I provided:

- Fedora 40: `GET_VERSION=6.9.12-200.fc40`
- Fedora 39: `GET_VERSION=6.9.12-200.fc39`

The older kernel was found via Fedora's Koji build archives, which can be used if anyone wants to get other versions:

- Search for kernel-6.9.* at Koji: https://koji.fedoraproject.org/koji/search?match=glob&type=build&terms=kernel-6.9.*

The link in the previous message is not properly clickable by Bugzilla.

Manually copy it to ensure you get the final `.*` to be able to do the search.

I made a mistake in the Fedora 39 instruction. They use a `-100` suffix. Here are the correct lines:

- Fedora 40: `GET_VERSION=6.9.12-200.fc40`
- Fedora 39: `GET_VERSION=6.9.12-100.fc39`

Have fun!

Somehow the whole GNOME session crashed. Several other application also crashed. I'm not sure what is cause and what is effect.


reporter:       libreport-2.17.15
kernel:         6.10.7-200.fc40.x86_64
package:        gnome-session-46.0-1.fc40
cmdline:        /usr/libexec/gnome-session-binary --systemd-service --session=gnome
executable:     /usr/libexec/gnome-session-binary
reason:         gnome-session-binary killed by SIGABRT
rootdir:        /
journald_cursor: s=49aacd3fd9ec4fa89a9fe07027e199f7;i=180b5e81;b=01814fcc52fc475b9faa13297dbb1eb7;m=3f4c8aa884;t=6228b5dd80875;x=8ff2801f7faebadb
type:           CCpp
backtrace_rating: 4
crash_function: __poll
uid:            1000
comment:        Somehow the whole GNOME session crashed. Several other application also crashed. I'm not sure what is cause and what is effect.
runlevel:       N 5

A crash happened. Probably when running a dnf update. The GNOME shell/session crashed.


reporter:       libreport-2.17.15
type:           CCpp
reason:         gnome-session-binary killed by SIGABRT
journald_cursor: s=bab09f8e6f144eaabdc6ab352bee9c89;i=25b6857;b=c458c61642544f87ac049ab78d6430e7;m=19fae7eaab;t=6238c409fff14;x=d699d452003f835b
executable:     /usr/libexec/gnome-session-binary
cmdline:        /usr/libexec/gnome-session-binary --systemd-service --session=gnome
rootdir:        /
uid:            1000
kernel:         6.10.11-200.fc40.x86_64
package:        gnome-session-46.0-1.fc40
runlevel:       N 5
comment:        A crash happened. Probably when running a dnf update. The GNOME shell/session crashed.
backtrace_rating: 4
crash_function: __poll

I experience nearly daily gnome shell crashes. I've no idea what triggers these crashes.


reporter:       libreport-2.17.15
kernel:         6.10.12-200.fc40.x86_64
package:        gnome-session-46.0-1.fc40
cmdline:        /usr/libexec/gnome-session-binary --systemd-service --session=gnome
executable:     /usr/libexec/gnome-session-binary
reason:         gnome-session-binary killed by SIGABRT
rootdir:        /
journald_cursor: s=1913e2ef3d2f446fa767fd094d5f186e;i=180e4fb7;b=86c73ca7712848ee97efc9499d0c4e14;m=61ea079c10;t=624a8c7f14c2c;x=4701757581780c80
type:           CCpp
backtrace_rating: 4
crash_function: __poll
uid:            1000
comment:        I experience nearly daily gnome shell crashes. I've no idea what triggers these crashes.
runlevel:       N 5

I was playing a game on steam, my save files were suddenly missing, and after exiting the game the entirety of gnome suddenly crashed. This is the third out of 3 crashes.


reporter:       libreport-2.17.15
type:           CCpp
reason:         gnome-session-binary killed by SIGABRT
journald_cursor: s=8636a1447d6442b6a3ec29e86152cd29;i=2b8a8e;b=5b589cfe6a11458ba6c2e6d8af036c4d;m=7a6284144;t=6257abaa4a4fa;x=dbf459e78a45b48f
executable:     /usr/libexec/gnome-session-binary
cmdline:        /usr/libexec/gnome-session-binary --systemd-service --session=gnome
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-gnome\x2dsession\x2dmanager.slice/gnome-session-manager
rootdir:        /
uid:            1000
kernel:         6.11.4-201.fc40.x86_64
package:        gnome-session-46.0-1.fc40
runlevel:       N 5
backtrace_rating: 4
crash_function: __poll
comment:        I was playing a game on steam, my save files were suddenly missing, and after exiting the game the entirety of gnome suddenly crashed. This is the third out of 3 crashes.

It happened while the system was sleeping...


reporter:       libreport-2.17.15
type:           CCpp
reason:         gnome-session-binary killed by SIGABRT
journald_cursor: s=867ae26341ac4a7fb9fd285d0c358ab3;i=18b10b4;b=dc45d3de1cbd41ba95614ce280eea202;m=3997d21e9c;t=618165dcdfb33;x=bc3a682c4f672009
executable:     /usr/libexec/gnome-session-binary
cmdline:        /usr/libexec/gnome-session-binary --systemd-service --session=gnome
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-gnome\x2dsession\x2dmanager.slice/gnome-session-manager
rootdir:        /
uid:            1000
kernel:         6.8.8-300.fc40.x86_64
package:        gnome-session-46.0-1.fc40
runlevel:       N 5
backtrace_rating: 4
crash_function: __poll
comment:        It happened while the system was sleeping...

Switch to the ibus-typing-booster input method and immediately press a key. It crashed the entire desktop, went to a black screen, and required you to press Ctrl+C to go back to the login screen.


reporter:       libreport-2.17.15
type:           CCpp
uid:            1000
package:        gnome-session-46.0-1.fc40
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-gnome\x2dsession\x2dmanager.slice/gnome-session-manager
kernel:         6.11.6-200.fc40.x86_64
runlevel:       N 5
backtrace_rating: 4
reason:         gnome-session-binary killed by SIGABRT
journald_cursor: s=e7ddc5841b034ce4adb62d18188af3eb;i=ba2114;b=b0e0f33de53644b0afe9e5976a6e8766;m=2e8e8dc73;t=626c2341da039;x=17c492bde7d211e1
rootdir:        /
crash_function: __poll
executable:     /usr/libexec/gnome-session-binary
comment:        Switch to the ibus-typing-booster input method and immediately press a key. It crashed the entire desktop, went to a black screen, and required you to press Ctrl+C to go back to the login screen.
cmdline:        /usr/libexec/gnome-session-binary --systemd-service --session=gnome

It crashed again. This time was ibus-table.

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.

Bug reports for this component on Red Hat Bugzilla are not actively monitored. Please consider reporting your issue directly to GNOME at https://gitlab.gnome.org/GNOME/ to improve the chances that your issue will be resolved. 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!

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.