Bug 793527 – Attempt to open user acounts panel freezes control-center

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 793527 - Attempt to open user acounts panel freezes control-center


Summary:	Attempt to open user acounts panel freezes control-center


Status:	RESOLVED DUPLICATE of bug 782627

Product:	gnome-control-center
Classification:	Core
Component:	User Accounts
Version:	3.26.x
Hardware:	Other Linux

Importance:	Normal major
Target Milestone:	---
Assigned To:	Control-Center Maintainers
QA Contact:	Control-Center Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2018-02-17 10:33 UTC by Christian Kirbach
Modified:	2018-02-19 10:29 UTC

See Also:
GNOME target:	---
GNOME version:	---

Attachments
stack trace - missing db symbols (10.13 KB, text/plain) 2018-02-17 10:33 UTC, Christian Kirbach	Details

Description Christian Kirbach 2018-02-17 10:33:07 UTC

Created attachment 368466 [details]
stack trace - missing db symbols

[nazgul@rivendell ~]$ gnome-control-center --version
gnome-control-center 3.26.2

I had the time and date panel open, then attempted to open the user accounts panel. control centre froze and went unresponsive for at least minutes until i killed it.

The issue is not reproducible.

I took a gdb trace and an strace, knowing that my system lacks debugging symbols, hoping the information may be useful enough.

To me it looks like it blocks on a futex.


[nazgul@rivendell ~]$ sudo strace -p 2331
strace: Process 2331 attached
futex(0x55daed92c2e0, FUTEX_WAIT_PRIVATE, 0, NULL

.. and nothing more happens.

+ Trace 238400

Thread 1 (Thread 0x7f34760a3a00 (LWP 2331))

#0 pthread_cond_wait
#1 pw_thread_loop_wait
#2 0x00007f342b96a2b6 in
#3 gst_device_provider_start
#4 gst_device_monitor_start
#5 g_type_create_instance
#6 0x00007f346e990729 in
#7 g_object_new_with_properties
#8 g_object_new
#9 um_photo_dialog_new
#10 0x000055daeb5286a6 in
#11 g_type_create_instance
#12 0x00007f346e990729 in
#13 g_object_new_valist
#14 g_object_new
#15 0x000055daeb4a6f9d in
#16 g_cclosure_marshal_VOID__STRINGv
#17 0x00007f346e98aea6 in
#18 g_signal_emit_valist
#19 g_signal_emit
#20 0x000055daeb4a5819 in
#21 g_closure_invoke
#22 0x00007f346e99eb50 in
#23 g_signal_emit_valist
#24 g_signal_emit
#25 0x00007f3470270e72 in
#26 ffi_call_unix64
#27 ffi_call
#28 g_cclosure_marshal_generic_va
#29 0x00007f346e98aea6 in
#30 g_signal_emit_valist
#31 g_signal_emit
#32 0x00007f347022e4ea in
#33 g_cclosure_marshal_VOID__BOXEDv
#34 0x00007f346e98aea6 in
#35 g_signal_emit_valist
#36 g_signal_emit
#37 0x00007f347022b67f in
#38 0x00007f347022ccfb in
#39 0x00007f347022fa87 in
#40 gtk_event_controller_handle_event
#41 0x00007f34703cad54 in
#42 0x00007f3470279ca8 in
#43 0x00007f346e98aea6 in
#44 g_signal_emit_valist
#45 g_signal_emit
#46 0x00007f34703cd0e5 in
#47 0x00007f3470276a0b in
#48 gtk_main_do_event
#49 0x00007f346fd819f6 in
#50 0x00007f346fdb41d5 in
#51 g_main_context_dispatch
#52 0x00007f346e6b1081 in
#53 g_main_context_iteration
#54 g_application_run
#55 main

Comment 1 Strangiato 2018-02-17 11:21:00 UTC

I can confirm this problem on Arch Linux, Gnome 3.26.2.

Comment 2 Felipe Borges 2018-02-19 09:07:56 UTC

Seems related to Bug 783789.

Comment 3 Ondrej Holy 2018-02-19 10:29:09 UTC

This is NOTGNOME, but let's mark this as duplicate, because the patches should at least prevent the hang.

*** This bug has been marked as a duplicate of bug 782627 ***