Bug 2243157

Summary: [abrt] gnome-session: __poll(): gnome-session-binary killed by SIGABRT
Product: [Fedora] Fedora Reporter: S.J. <torkiz>
Component: gnome-sessionAssignee: GNOME SIG Unassigned <gnome-sig>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 39CC: gnome-sig, jan.public, mclasen, rhughes, rstrode, torkiz
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/628ac9193d63b4999b63e4823ffc0bb68b7276d
Whiteboard: abrt_hash:fe578eeeb5e1588f829f39adf264cb1f0494b5bc;VARIANT_ID=workstation;
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-11-27 21:34:53 UTC 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: dso_list
none
File: backtrace none

Description S.J. 2023-10-11 03:28:44 UTC 
Version-Release number of selected component:
gnome-session-45.0-3.fc39

Additional info:
reporter:       libreport-2.17.11
type:           CCpp
reason:         gnome-session-binary killed by SIGABRT
journald_cursor: s=b81823042de94128817d4f980db734cf;i=43492b;b=b387a178d21e4af1a15bf3f65365542c;m=1716880eb;t=6075d42fe7c48;x=4899044431f9f5e7
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.5.5-300.fc39.x86_64
package:        gnome-session-45.0-3.fc39
runlevel:       N 5
backtrace_rating: 4
crash_function: __poll

Truncated backtrace:
Thread no. 5 (7 frames)
 #0 __poll at ../sysdeps/unix/sysv/linux/poll.c:29
 #1 g_main_context_poll_unlocked at ../glib/gmain.c:4653
 #2 g_main_context_iterate_unlocked.isra.0 at ../glib/gmain.c:4344
 #3 g_main_context_iteration at ../glib/gmain.c:4414
 #4 dconf_gdbus_worker_thread at ../gdbus/dconf-gdbus-thread.c:82
 #5 g_thread_proxy at ../glib/gthread.c:831
 #7 clone3 at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
Comment 1 S.J. 2023-10-11 03:28:48 UTC 
Created attachment 1993411 [details]
File: proc_pid_status
Comment 2 S.J. 2023-10-11 03:28:50 UTC 
Created attachment 1993412 [details]
File: maps
Comment 3 S.J. 2023-10-11 03:28:51 UTC 
Created attachment 1993413 [details]
File: limits
Comment 4 S.J. 2023-10-11 03:28:53 UTC 
Created attachment 1993414 [details]
File: environ
Comment 5 S.J. 2023-10-11 03:28:55 UTC 
Created attachment 1993415 [details]
File: open_fds
Comment 6 S.J. 2023-10-11 03:28:56 UTC 
Created attachment 1993416 [details]
File: mountinfo
Comment 7 S.J. 2023-10-11 03:28:58 UTC 
Created attachment 1993417 [details]
File: os_info
Comment 8 S.J. 2023-10-11 03:28:59 UTC 
Created attachment 1993418 [details]
File: cpuinfo
Comment 9 S.J. 2023-10-11 03:29:01 UTC 
Created attachment 1993419 [details]
File: core_backtrace
Comment 10 S.J. 2023-10-11 03:29:02 UTC 
Created attachment 1993420 [details]
File: dso_list
Comment 11 S.J. 2023-10-11 03:29:04 UTC 
Created attachment 1993421 [details]
File: backtrace
Comment 12 Stein 2023-12-07 08:36:41 UTC 
1. Suspend and resume device
2. After resuming, press the date to show the notification panel. Everything freezes, although mouse cursor remains responsive.
3. Login to the device via SSH
4. Run gnome-session-quit --logout --force twice (because the first time has no effect)
5. observe crash


reporter:       libreport-2.17.11
type:           CCpp
reason:         gnome-session-binary killed by SIGABRT
journald_cursor: s=cbf9ebbf541c44ec859b8c3ad9d79442;i=10d5d5;b=74dc4309caa5487097fc00aefc2e7cb2;m=8629f4109;t=60bc1bf62e036;x=5c47f59c3686a44c
executable:     /usr/libexec/gnome-session-binary
cmdline:        /usr/libexec/gnome-session-binary --systemd-service --session=gnome
cgroup:         0::/user.slice/user-1001.slice/user/app.slice/app-gnome\x2dsession\x2dmanager.slice/gnome-session-manager
rootdir:        /
uid:            1001
kernel:         6.6.2-201.fc39.x86_64
package:        gnome-session-45.0-3.fc39
runlevel:       N 5
backtrace_rating: 4
crash_function: __poll
Comment 13 dobs 2023-12-18 16:35:19 UTC 
On locked PC, restarted session


reporter:       libreport-2.17.11
type:           CCpp
reason:         gnome-session-binary killed by SIGABRT
journald_cursor: s=4e33bac2c19940dfaa4a38659c26d562;i=2fe3e87;b=e6a503f8fca244178695056769310aad;m=b8631d8a0;t=60ccafff882e0;x=5ead5d775deb67ea
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.6-200.fc39.x86_64
package:        gnome-session-45.0-3.fc39
runlevel:       N 5
backtrace_rating: 4
crash_function: __poll
comment:        On locked PC, restarted session
Comment 14 Rick Calvo 2024-01-13 13:12:42 UTC 
I believe the issue started when I switched to the new gnome shell light  theme.


reporter:       libreport-2.17.11
type:           CCpp
reason:         gnome-session-ctl killed by SIGABRT
journald_cursor: s=b382dae35cb248e19693be0dd1291d5b;i=18fa2;b=b2829918860e407d92e078b2f702b83d;m=4bfd1841b;t=60ed375b124fb;x=bc2425d173488c77
executable:     /usr/libexec/gnome-session-ctl
cmdline:        /usr/libexec/gnome-session-ctl --monitor
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/gnome-session-monitor.service
rootdir:        /
uid:            1000
kernel:         6.6.9-200.fc39.x86_64
package:        gnome-session-45.0-3.fc39
runlevel:       N 5
backtrace_rating: 4
crash_function: __poll
comment:        I believe the issue started when I switched to the new gnome shell light  theme.
Comment 15 Brian J. Murrell 2024-03-31 14:00:06 UTC 
Don't know how or why this happened.


reporter:       libreport-2.17.11
rootdir:        /
executable:     /usr/libexec/gnome-session-binary
cmdline:        /usr/libexec/gnome-session-binary --systemd-service --session=gnome
cgroup:         0::/user.slice/user-1001.slice/user/app.slice/app-gnome\x2dsession\x2dmanager.slice/gnome-session-manager
journald_cursor: s=9e6e59098bd94255a567942cfffd6080;i=8ae4ef5;b=be773f11d72241639e48c3ef76d16511;m=29c6aa84ef9;t=60e4b35713908;x=dc2a5b90e2e3145b
package:        gnome-session-45.0-3.fc39
uid:            1001
runlevel:       N 5
crash_function: __poll
comment:        Don't know how or why this happened.
backtrace_rating: 4
type:           CCpp
kernel:         6.5.11-300.fc39.x86_64
reason:         gnome-session-binary killed by SIGABRT
Comment 16 Gilbert Fernandes 2024-04-07 01:07:49 UTC 
just did a logoff.


reporter:       libreport-2.17.11
type:           CCpp
reason:         gnome-session-binary killed by SIGABRT
journald_cursor: s=e1fb7b30793b4ca4a1f49a273488f1b1;i=146b9d;b=f5264c24521140a9b793132717cf02bf;m=20b230361;t=615774c16cf9b;x=3b7c633c42eea126
executable:     /usr/libexec/gnome-session-binary
cmdline:        /usr/libexec/gnome-session-binary --systemd-service --session=gnome
rootdir:        /
uid:            1000
kernel:         6.8.4-200.fc39.x86_64
package:        gnome-session-45.0-3.fc39
runlevel:       N 5
backtrace_rating: 4
crash_function: __poll
comment:        just did a logoff.
Comment 17 Liam 2024-04-08 12:14:10 UTC 
Seconds after logging in with wayland, first boot after an update


reporter:       libreport-2.17.11
type:           CCpp
reason:         gnome-session-binary killed by SIGABRT
journald_cursor: s=86b26d9cfdb04fa5823b2ee5c1b3283f;i=27f776;b=228ebe5632164bd895a8413a93eb632b;m=628cfa2;t=61594b8157be0;x=7c3e99370631eab2
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.4-200.fc39.x86_64
package:        gnome-session-45.0-3.fc39
runlevel:       N 5
backtrace_rating: 4
crash_function: __poll
comment:        Seconds after logging in with wayland, first boot after an update
Comment 18 Fedora Admin user for bugzilla script actions 2024-04-19 15:53:53 UTC 
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
Comment 19 Mauro 2024-07-04 22:00:49 UTC 
Just tipe super+l to lockscreen adn when I try to login again the gnome have been crached.


reporter:       libreport-2.17.11
type:           CCpp
reason:         gnome-session-binary killed by SIGABRT
journald_cursor: s=3261734a712a4db9a6a3f4d5a173b168;i=73bcc;b=4d93021fe7e3443aa81ad51bc78cc8b3;m=3f7a7cafc;t=61c72d71ec3fe;x=31fbf8f0a26b675f
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.7-100.fc39.x86_64
package:        gnome-session-45.0-3.fc39
runlevel:       N 5
backtrace_rating: 4
crash_function: __poll
comment:        Just tipe super+l to lockscreen adn when I try to login again the gnome have been crached.
Comment 20 Aoife Moloney 2024-11-27 21:34:53 UTC 
Fedora Linux 39 entered end-of-life (EOL) status on 2024-11-26.

Fedora Linux 39 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.