Description of problem: I had firefox and openrct open. I also had an ISO of Roller Coaster Tycoon mounted in nautilus. I went to install wine through the terminal and the screen went black. Changed to a TTY, logged in, GDM started at the login prompt as soon as I logged in. I picked my user and then it went black again. Went back to the TTY I was logged into, same thing. This happened a third time and then the Gnome desktop loaded. All open apps were closed. Version-Release number of selected component: gnome-session-44~rc-1.fc38 Additional info: reporter: libreport-2.17.8 type: CCpp reason: gnome-session-binary killed by SIGABRT journald_cursor: s=9c0c2ecf5b0b4dc590d3d71ff9cfc2fe;i=8f2e;b=06587a4d13af43758de1dc05d951fa9b;m=52b11a1d5;t=5f71e04f05313;x=9072699afa6e0ab8 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.2.6-300.fc38.x86_64 package: gnome-session-44~rc-1.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: __poll comment: I had firefox and openrct open. I also had an ISO of Roller Coaster Tycoon mounted in nautilus. I went to install wine through the terminal and the screen went black. Changed to a TTY, logged in, GDM started at the login prompt as soon as I logged in. I picked my user and then it went black again. Went back to the TTY I was logged into, same thing. This happened a third time and then the Gnome desktop loaded. All open apps were closed. Truncated backtrace: Thread no. 1 (3 frames) #0 __poll at ../sysdeps/unix/sysv/linux/poll.c:29 #1 g_main_context_poll at ../glib/gmain.c:4584 #2 g_main_context_iterate.isra.0 at ../glib/gmain.c:4271
Created attachment 1951543 [details] File: proc_pid_status
Created attachment 1951544 [details] File: limits
Created attachment 1951545 [details] File: open_fds
Created attachment 1951546 [details] File: mountinfo
Created attachment 1951547 [details] File: os_info
Created attachment 1951548 [details] File: cpuinfo
Created attachment 1951549 [details] File: core_backtrace
Created attachment 1951550 [details] File: dso_list
Created attachment 1951551 [details] File: backtrace
Created attachment 1951552 [details] File: maps
Created attachment 1951553 [details] File: environ
Plugged out the charger and gnome freezed reporter: libreport-2.17.9 type: CCpp reason: gnome-session-binary killed by SIGABRT journald_cursor: s=f101fb624f584e0ba7faee85d83ee22a;i=bd02;b=2fb5b393490746449debab3021c40d30;m=22b164c6;t=5f9f59b1d1a3f;x=7b3afcc96e0fb996 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.2.11-300.fc38.x86_64 package: gnome-session-44.0-1.fc38 runlevel: N 5 comment: Plugged out the charger and gnome freezed backtrace_rating: 4 crash_function: __poll
I'm pretty sure that the reason was that I pressed "log out" several times, because it seemed to me like it wasn't working. Then it kinda bugged out and logged out, and after I logged into GNOME with Xorg (previously I was in classic GNOME with Xorg) that error popped out. reporter: libreport-2.17.9 type: CCpp reason: gnome-session-binary killed by SIGABRT journald_cursor: s=4db673121e0c4fed97e985798c5e4545;i=e950;b=c14d59bcfa2a4fecaefdf06186fba190;m=2f85ba067;t=5fb84588d0b57;x=8e9010b879a12106 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.2.14-300.fc38.x86_64 package: gnome-session-44.0-1.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: __poll
Was trying to log out, after pressing 'Log out' on the 60 window to skip the time my screen went blank and I was back on the login screen. Not sure if anything actually went wrong here, as it seems to have had the intended effect, but the 'Problem Reporting' app popped up a notification for it after I logged back in. reporter: libreport-2.17.10 type: CCpp reason: gnome-session-binary killed by SIGABRT journald_cursor: s=7f71da6453b84e5f931c20b1f5f10a5f;i=75dc7d;b=5f172e9437404f89a37e9c0b0265aaf1;m=1104b382;t=5fdd231fc591a;x=861da19365273c4d 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.3.6-200.fc38.x86_64 package: gnome-session-44.0-1.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: __poll
Was just busy reading in vivaldi, and then the mouse stopped responding and the screen did disappear reporter: libreport-2.17.11 type: CCpp reason: gnome-session-binary killed by SIGABRT journald_cursor: s=d31a4912621345e5906b5342d88f51e2;i=2a2f336;b=ee52354ca53a4c02809b664288afb335;m=33e87ea1594;t=6045a091c5c02;x=845e348b9c8551c0 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.3.12-200.fc38.x86_64 package: gnome-session-44.0-1.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: __poll comment: Was just busy reading in vivaldi, and then the mouse stopped responding and the screen did disappear
Seems like Gnome couldn't handle my laptop's main monitor's scale set to 0.75 in ~/.config/monitors.xml reporter: libreport-2.17.11 type: CCpp reason: gnome-session-binary killed by SIGABRT journald_cursor: s=8a6821c5f33c45a49efedb5b68e3368a;i=144777;b=69da2f83136146bd976f5118e6fd01fe;m=47a85403;t=61057eb1828dd;x=6c4cea475a81c294 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.6.14-100.fc38.x86_64 package: gnome-session-44.0-1.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: __poll comment: Seems like Gnome couldn't handle my laptop's main monitor's scale set to 0.75 in ~/.config/monitors.xml
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
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.