Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#56546 - [gnome-control-center] gnome-control-center user-accounts hangs

Attached to Project: Arch Linux
Opened by Pawel Sawicki (blispx) - Saturday, 02 December 2017, 22:09 GMT
Last edited by Eli Schwartz (eschwartz) - Tuesday, 12 December 2017, 00:13 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Jan Steffens (heftig)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No



Does not start, hangs. What a strange second run in the same session opens correctly

Additional info:
gnome-control-center 3.26.2

Steps to reproduce:
This task depends upon

Closed by  Eli Schwartz (eschwartz)
Tuesday, 12 December 2017, 00:13 GMT
Reason for closing:  Fixed
Additional comments about closing:  see last comment
Comment by Pawel Sawicki (blispx) - Saturday, 02 December 2017, 22:12 GMT
strace log
Comment by Kerr (zefkerrigan) - Monday, 11 December 2017, 17:36 GMT
Hi! I have a same problem with the User accounts panel in the gnome-control-center. After a fresh start of GNOME, the User accounts panel hangs the first time I try to start it. But, if I kill this process, then all subsequent launches of the User accounts panel occur normally until Arch Linux restarts, after which the User accounts panel hangs up again only at the first attempt to start, after which it starts normally again.

Additional info:
* package version.
I use only the latest version of all packages.
* config and/or log files etc.
Unfortunately, I was not able to get a useful console output. But, I attached 2 videos here:

Steps to reproduce:
Ondrej Holy [gnome-control-center developer] offered his patches to solve this bug.
It's available here:

Thank you!
Comment by Pawel Sawicki (blispx) - Tuesday, 12 December 2017, 00:02 GMT
The latest system update fixes this problem, I'm not sure which packet but the last one was vala