Bug 931435 - gdm-session-worker sigabrt
gdm-session-worker sigabrt
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: GNOME
Other Other
: P5 - None : Normal (vote)
: ---
Assigned To: openSUSE GNOME
E-mail List
Depends on:
  Show dependency treegraph
Reported: 2015-05-19 09:21 UTC by Martin Pluskal
Modified: 2020-06-26 08:41 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

backtrace (6.62 KB, text/plain)
2015-05-19 09:21 UTC, Martin Pluskal
core (116.33 KB, application/x-xz)
2015-05-19 15:40 UTC, Martin Pluskal

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Pluskal 2015-05-19 09:21:19 UTC
Created attachment 634690 [details]

After reboot with recent factory, gdm is terminated, after that it is restarted and works fine.

Core was generated by `gdm-session-worker [pam/gdm-launch-environment]'.
Program terminated with signal SIGABRT, Aborted.
#0  0x00007fae7aa623c7 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55
55      ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0  0x00007fae7aa623c7 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55
#1  0x00007fae7aa6379a in __GI_abort () at abort.c:78
#2  0x00007fae7b8e61b5 in g_assertion_message (domain=domain@entry=0x7fae7b66069a "AccountsService", file=file@entry=0x7fae7b661200 "act-user-manager.c", line=line@entry=2564, 
    func=func@entry=0x7fae7b663978 <__FUNCTION__.27349> "load_users", message=message@entry=0x13f5630 "assertion failed: (manager->priv->accounts_proxy != NULL)") at gtestutils.c:2356
#3  0x00007fae7b8e624a in g_assertion_message_expr (domain=domain@entry=0x7fae7b66069a "AccountsService", file=file@entry=0x7fae7b661200 "act-user-manager.c", line=line@entry=2564, 
    func=func@entry=0x7fae7b663978 <__FUNCTION__.27349> "load_users", expr=expr@entry=0x7fae7b662390 "manager->priv->accounts_proxy != NULL") at gtestutils.c:2371
#4  0x00007fae7b64bc66 in load_users (manager=0x13dc100) at act-user-manager.c:2564
#5  load_idle (manager=0x13dc100) at act-user-manager.c:2615
#6  0x00007fae7b8c1b55 in g_main_dispatch (context=0x13d81f0) at gmain.c:3122
#7  g_main_context_dispatch (context=context@entry=0x13d81f0) at gmain.c:3737
#8  0x00007fae7b8c1ec8 in g_main_context_iterate (context=0x13d81f0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3808
#9  0x00007fae7b8c218a in g_main_loop_run (loop=0x13f2c10) at gmain.c:4002
#10 0x0000000000408b34 in main (argc=1, argv=0x7fff4d13b0f8) at session-worker-main.c:132
Comment 1 Martin Pluskal 2015-05-19 15:40:00 UTC
Created attachment 634745 [details]
Comment 2 Andrei Dziahel 2016-05-05 05:38:34 UTC
+1 here, got entries with same backtrace in `coredumpctl list`.
Comment 3 Dominique Leuenberger 2020-06-26 08:41:09 UTC
This seems to be related to all the other crashes you had at around that time.

WE have moved up to GNOME 3.36 by now (SLE/Leap GNOME 3.34) and this should no longer happen