Bug 803364

Summary:	"dconf update" hangs forever while updating gdm
Product:	[openSUSE] openSUSE 12.3	Reporter:	Stanislav Brabec <sbrabec>
Component:	GNOME	Assignee:	E-mail List <gnome-bugs>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Critical
Priority:	P5 - None	CC:	dimstar
Version:	RC 1	Flags:	coolo: SHIP_STOPPER-
Target Milestone:	---
Hardware:	x86-64
OS:	SUSE Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Stanislav Brabec 2013-02-12 17:12:47 UTC

Had openSUSE 12.3 beta 1, called zypper dup today, and the update process hangs
on "dconf update" while updating gdm (62%). Called in live system, not chroot.

#0  0x00007f77129e8860 in __poll_nocancel () from /lib64/libc.so.6
#1  0x00007f7713490548 in g_socket_condition_timed_wait () from /usr/lib64/libgio-2.0.so.0
#2  0x00007f77134909a3 in g_socket_receive_with_blocking () from /usr/lib64/libgio-2.0.so.0
#3  0x00007f771347941f in g_input_stream_read () from /usr/lib64/libgio-2.0.so.0
#4  0x00007f77134515bc in ?? () from /usr/lib64/libgio-2.0.so.0
#5  0x00007f77134522a4 in g_buffered_input_stream_fill () from /usr/lib64/libgio-2.0.so.0
#6  0x00007f77134583f5 in g_data_input_stream_read_line () from /usr/lib64/libgio-2.0.so.0
#7  0x00007f77134cffdd in ?? () from /usr/lib64/libgio-2.0.so.0
#8  0x00007f77134d06e5 in ?? () from /usr/lib64/libgio-2.0.so.0
#9  0x00007f77134df79f in ?? () from /usr/lib64/libgio-2.0.so.0
#10 0x00007f77134dfcc1 in g_bus_get_sync () from /usr/lib64/libgio-2.0.so.0
#11 0x0000000000405249 in ?? ()
#12 0x0000000000405425 in ?? ()
#13 0x000000000040794a in ?? ()
#14 0x00007f771292aa15 in __libc_start_main () from /lib64/libc.so.6
#15 0x0000000000403469 in ?? ()

The bug may be related to bug 802525.

Comment 1 Stephan Kulow 2013-02-17 16:08:01 UTC

while rtkit is noticably by anyone, here you are alone. So I declare it no ship stopper

Comment 2 Dominique Leuenberger 2013-03-29 20:04:16 UTC

I think in the end this was the same as bug 802525...

Marking as 'dup'; if anybody disagrees, please feel free to re-open it.

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