Created attachment 1429320 [details]
File: backtrace

Created attachment 1429321 [details]
File: cgroup

Created attachment 1429322 [details]
File: core_backtrace

Created attachment 1429323 [details]
File: cpuinfo

Created attachment 1429324 [details]
File: dso_list

Created attachment 1429325 [details]
File: environ

Created attachment 1429326 [details]
File: exploitable

Created attachment 1429327 [details]
File: limits

Created attachment 1429328 [details]
File: maps

Created attachment 1429329 [details]
File: mountinfo

Created attachment 1429330 [details]
File: open_fds

Created attachment 1429331 [details]
File: proc_pid_status

Created attachment 1429332 [details]
File: var_log_messages

Every openQA F28 update test run appears to be hitting this (in the base_services_start test) since the base image was regenerated earlier today:

https://openqa.fedoraproject.org/tests/232810?machine=64bit&version=28&limit_previous=100&distri=fedora&test=base_services_start&flavor=updates-workstation&arch=x86_64#previous

this is probably because https://bodhi.fedoraproject.org/updates/FEDORA-2018-c1d39b6bd2 got included in the base image at that point, I believe; I think this was broken by that update.

The service crashes a little less than a minute after it starts:

May 01 22:34:43 localhost.localdomain systemd[1]: Starting Accounts Service...
May 01 22:34:43 localhost.localdomain accounts-daemon[698]: started daemon version 0.6.47
May 01 22:34:43 localhost.localdomain systemd[1]: Started Accounts Service.
May 01 22:35:25 ibm-p8-kvm-03-guest-02.virt.pnr.lab.eng.rdu2.redhat.com accounts-daemon[698]: g_variant_is_object_path: assertion 'string != NULL' failed
May 01 22:35:25 ibm-p8-kvm-03-guest-02.virt.pnr.lab.eng.rdu2.redhat.com accounts-daemon[698]: g_variant_new_object_path: assertion 'g_variant_is_object_path (object_path)' failed
May 01 22:35:26 ibm-p8-kvm-03-guest-02.virt.pnr.lab.eng.rdu2.redhat.com systemd[1]: accounts-daemon.service: Main process exited, code=dumped, status=11/SEGV
May 01 22:35:26 ibm-p8-kvm-03-guest-02.virt.pnr.lab.eng.rdu2.redhat.com systemd[1]: accounts-daemon.service: Failed with result 'core-dump'.

*** Bug 1575083 has been marked as a duplicate of this bug. ***

I think I see what the problem is, can someone give this scratch build a try when it finishes?

https://koji.fedoraproject.org/koji/taskinfo?taskID=26771649

I was experiencing the problem (accountsservice SIGSEGV at every boot with the same backtrace).
Using the 0.6.47-2.fc28 package solves the problem here, accountsservice stays running after a reboot.

*** Bug 1575151 has been marked as a duplicate of this bug. ***

(In reply to Philippe Troin from comment #17)
> I was experiencing the problem (accountsservice SIGSEGV at every boot with
> the same backtrace).
> Using the 0.6.47-2.fc28 package solves the problem here, accountsservice
> stays running after a reboot.

I spoke too soon, it seems to still be crashing with the same backtrace.

*** Bug 1575187 has been marked as a duplicate of this bug. ***

*** Bug 1575253 has been marked as a duplicate of this bug. ***

Similar problem has been detected:

Freshly logged in into gnome.

reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        /usr/libexec/accounts-daemon
crash_function: g_variant_is_trusted
executable:     /usr/libexec/accounts-daemon
journald_cursor: s=55bf7705993047ad9bebf765eea38d8a;i=12ee73;b=df69d2a181fe485ab6004bef8c0216af;m=e0da9fd;t=56b4a7f25012f;x=c75f245c74818e05
kernel:         4.16.6-300.fc28.x86_64
package:        accountsservice-0.6.47-1.fc28
reason:         accounts-daemon killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            0

(In reply to Philippe Troin from comment #19)
> (In reply to Philippe Troin from comment #17)
> > I was experiencing the problem (accountsservice SIGSEGV at every boot with
> > the same backtrace).
> > Using the 0.6.47-2.fc28 package solves the problem here, accountsservice
> > stays running after a reboot.
> 
> I spoke too soon, it seems to still be crashing with the same backtrace.

Hmm, it really seemed like the fix.  does it print the same message to the log ?
Could it be you're seeing a notification from an old abrt run ?

(In reply to Ray Strode [halfline] from comment #23)
> (In reply to Philippe Troin from comment #19)
> > (In reply to Philippe Troin from comment #17)
> > > I was experiencing the problem (accountsservice SIGSEGV at every boot with
> > > the same backtrace).
> > > Using the 0.6.47-2.fc28 package solves the problem here, accountsservice
> > > stays running after a reboot.
> > 
> > I spoke too soon, it seems to still be crashing with the same backtrace.
> 
> Hmm, it really seemed like the fix.  does it print the same message to the
> log ?
> Could it be you're seeing a notification from an old abrt run ?

I'm trying again.

(In reply to Philippe Troin from comment #24)
> (In reply to Ray Strode [halfline] from comment #23)
> > (In reply to Philippe Troin from comment #19)
> > > (In reply to Philippe Troin from comment #17)
> > > > I was experiencing the problem (accountsservice SIGSEGV at every boot with
> > > > the same backtrace).
> > > > Using the 0.6.47-2.fc28 package solves the problem here, accountsservice
> > > > stays running after a reboot.
> > > 
> > > I spoke too soon, it seems to still be crashing with the same backtrace.
> > 
> > Hmm, it really seemed like the fix.  does it print the same message to the
> > log ?
> > Could it be you're seeing a notification from an old abrt run ?
> 
> I'm trying again.

Confirming I'm still seeing a crash after reboot with 0.6.47-2.fc28.

# rpm -qa accountsservice* | sort
accountsservice-0.6.47-2.fc28.x86_64
accountsservice-debuginfo-0.6.47-2.fc28.x86_64
accountsservice-debugsource-0.6.47-2.fc28.x86_64
accountsservice-devel-0.6.47-2.fc28.x86_64
accountsservice-libs-0.6.47-2.fc28.i686
accountsservice-libs-0.6.47-2.fc28.x86_64
accountsservice-libs-debuginfo-0.6.47-2.fc28.x86_64
# journalctl -b | grep accounts
May 07 13:56:13 fnew64 accounts-daemon[894]: started daemon version 0.6.47
May 07 13:56:13 fnew64 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=accounts-daemon comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 07 14:02:04 fnew64 accounts-daemon[894]: g_variant_is_object_path: assertion 'string != NULL' failed
May 07 14:02:04 fnew64 accounts-daemon[894]: g_variant_new_object_path: assertion 'g_variant_is_object_path (object_path)' failed
May 07 14:02:04 fnew64 audit[894]: ANOM_ABEND auid=4294967295 uid=0 gid=0 ses=4294967295 pid=894 comm="accounts-daemon" exe="/usr/libexec/accounts-daemon" sig=11 res=1
May 07 14:02:04 fnew64 kernel: accounts-daemon[894]: segfault at 20 ip 00007f26a60a2444 sp 00007ffc7183e2b8 error 4 in libglib-2.0.so.0.5600.1[7f26a6019000+115000]
May 07 14:02:04 fnew64 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=accounts-daemon comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
May 07 14:02:04 fnew64 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=accounts-daemon comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 07 14:02:04 fnew64 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=accounts-daemon comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 07 14:02:04 fnew64 systemd[1]: accounts-daemon.service: Main process exited, code=dumped, status=11/SEGV
May 07 14:02:04 fnew64 systemd[1]: accounts-daemon.service: Failed with result 'core-dump'.
May 07 14:02:04 fnew64 systemd[1]: accounts-daemon.service: Service has no hold-off time, scheduling restart.
May 07 14:02:04 fnew64 systemd[1]: accounts-daemon.service: Scheduled restart job, restart counter is at 1.
May 07 14:02:04 fnew64 accounts-daemon[2012]: started daemon version 0.6.47
May 07 14:02:04 fnew64 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=accounts-daemon comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 07 14:02:04 fnew64 systemd-coredump[2011]: Process 894 (accounts-daemon) of user 0 dumped core.
                                               #5  0x000056138de8d12f _accounts_accounts_on_signal_user_deleted (accounts-daemon)
                                               #13 0x000056138de82b9f reload_users (accounts-daemon)
                                               #14 0x000056138de82c9d reload_users_timeout (accounts-daemon)
                                               #19 0x000056138de81dbc main (accounts-daemon)
                                               #21 0x000056138de81f9a _start (accounts-daemon)
# coredumpctl gdb 894
           PID: 894 (accounts-daemon)
           UID: 0 (root)
           GID: 0 (root)
        Signal: 11 (SEGV)
     Timestamp: Mon 2018-05-07 14:02:04 PDT (2min 58s ago)
  Command Line: /usr/libexec/accounts-daemon
    Executable: /usr/libexec/accounts-daemon
 Control Group: /system.slice/accounts-daemon.service
          Unit: accounts-daemon.service
         Slice: system.slice
       Boot ID: d1f4a1c6121f448eb3504808b7b31017
    Machine ID: b59a48bf466e084b0782036c229d94a9
      Hostname: fnew64
       Storage: /var/lib/systemd/coredump/core.accounts-daemon.0.d1f4a1c6121f448eb3504808b7b31017.894.1525726924000000.lz4
       Message: Process 894 (accounts-daemon) of user 0 dumped core.
                
                Stack trace of thread 894:
                #0  0x00007f26a60a2444 g_variant_is_trusted (libglib-2.0.so.0)
                #1  0x00007f26a609edcb g_variant_builder_add_value (libglib-2.0.so.0)
                #2  0x00007f26a60a0702 g_variant_valist_new (libglib-2.0.so.0)
                #3  0x00007f26a60a0b82 g_variant_new_va (libglib-2.0.so.0)
                #4  0x00007f26a60a0cdb g_variant_new (libglib-2.0.so.0)
                #5  0x000056138de8d12f _accounts_accounts_on_signal_user_deleted (accounts-daemon)
                #6  0x00007f26a517f03e ffi_call_unix64 (libffi.so.6)
                #7  0x00007f26a517e9ff ffi_call (libffi.so.6)
                #8  0x00007f26a63405a5 g_cclosure_marshal_generic (libgobject-2.0.so.0)
                #9  0x00007f26a633fadd g_closure_invoke (libgobject-2.0.so.0)
                #10 0x00007f26a63526e4 signal_emit_unlocked_R (libgobject-2.0.so.0)
                #11 0x00007f26a635bfda g_signal_emit_valist (libgobject-2.0.so.0)
                #12 0x00007f26a635cab4 g_signal_emit_by_name (libgobject-2.0.so.0)
                #13 0x000056138de82b9f reload_users (accounts-daemon)
                #14 0x000056138de82c9d reload_users_timeout (accounts-daemon)
                #15 0x00007f26a6066291 g_timeout_dispatch (libglib-2.0.so.0)
                #16 0x00007f26a60657cd g_main_context_dispatch (libglib-2.0.so.0)
                #17 0x00007f26a6065b98 g_main_context_iterate.isra.21 (libglib-2.0.so.0)
                #18 0x00007f26a6065ec2 g_main_loop_run (libglib-2.0.so.0)
                #19 0x000056138de81dbc main (accounts-daemon)
                #20 0x00007f26a5a651bb __libc_start_main (libc.so.6)
                #21 0x000056138de81f9a _start (accounts-daemon)
                
                Stack trace of thread 913:
                #0  0x00007f26a5b31929 __poll (libc.so.6)
                #1  0x00007f26a6065b06 g_main_context_iterate.isra.21 (libglib-2.0.so.0)
                #2  0x00007f26a6065ec2 g_main_loop_run (libglib-2.0.so.0)
                #3  0x00007f26a665560a gdbus_shared_thread_func (libgio-2.0.so.0)
                #4  0x00007f26a608dcea g_thread_proxy (libglib-2.0.so.0)
                #5  0x00007f26a5389564 start_thread (libpthread.so.0)
                #6  0x00007f26a5b3c31f __clone (libc.so.6)
                
                Stack trace of thread 911:
                #0  0x00007f26a5b31929 __poll (libc.so.6)
                #1  0x00007f26a6065b06 g_main_context_iterate.isra.21 (libglib-2.0.so.0)
                #2  0x00007f26a6065c30 g_main_context_iteration (libglib-2.0.so.0)
                #3  0x00007f26a6065c81 glib_worker_main (libglib-2.0.so.0)
                #4  0x00007f26a608dcea g_thread_proxy (libglib-2.0.so.0)
                #5  0x00007f26a5389564 start_thread (libpthread.so.0)
                #6  0x00007f26a5b3c31f __clone (libc.so.6)

Could it be related to the newish transient users systemd feature?

okay i'll do another build that avoids the code path in the crashing scenario. i'm a little iffy on how that could happen though.  I guess a user is getting added and removed before it gets registered.

actually I think I see the problem now. I'm going to throw one more build over the wall that may or may not work. If it doesn't work, then I'll switch to the fallback plan alluded to in comment 26.

https://koji.fedoraproject.org/koji/taskinfo?taskID=26857182

The new build in comment 28 seems to fix the issue in my case

Yeah, fix seems to work in a manual replication of one of the affected openQA cases too.

(In reply to Ray Strode [halfline] from comment #28)
> https://koji.fedoraproject.org/koji/taskinfo?taskID=26857182

(In reply to Trond H. Amundsen from comment #29)
> The new build in comment 28 seems to fix the issue in my case

Same for me.  The packages linked from comment 28 seem to fix the problem.
I did a few reboots, and account-daemon doesn't crash anymore.

*** Bug 1576604 has been marked as a duplicate of this bug. ***

accountsservice-0.6.48-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-213e7536b3

accountsservice-0.6.49-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-0e8688f4f0

*** Bug 1577074 has been marked as a duplicate of this bug. ***

Similar problem has been detected:

I just tried to login; sometimes it works, sometimes it crashes

reporter:       libreport-2.9.5
backtrace_rating: 3
cmdline:        /usr/libexec/accounts-daemon
crash_function: g_variant_is_trusted
executable:     /usr/libexec/accounts-daemon
journald_cursor: s=01a0ea1e1158489ea70642ad534befdf;i=1d7ec81;b=c6c371d31bb544dba1893cbc72e85cad;m=3bd6cd05;t=56bf0c6c63d2b;x=b2664a7d586cf513
kernel:         4.16.7-300.fc28.x86_64
package:        accountsservice-0.6.47-1.fc28
reason:         accounts-daemon killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            0

accountsservice-0.6.49-1.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-0e8688f4f0

Similar problem has been detected:

I could not select guest login on login screen after enabling the "allow guest login" option in settings.

reporter:       libreport-2.9.5
backtrace_rating: 3
cmdline:        /usr/libexec/accounts-daemon
crash_function: g_variant_is_trusted
executable:     /usr/libexec/accounts-daemon
journald_cursor: s=44f1186103154fd68b0ec29d9a3b5fd6;i=906;b=efb57a86dc9a459488bb117992565946;m=8034b52;t=56c03f3b7f062;x=f69f99521bdb15a0
kernel:         4.16.7-300.fc28.x86_64
package:        accountsservice-0.6.47-1.fc28
reason:         accounts-daemon killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            0

accountsservice-0.6.49-1.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.

*** Bug 1578015 has been marked as a duplicate of this bug. ***