FS#24164 - dconf upgrade prevented xorg start with gdm

Attached to Project: Arch Linux
Opened by Clayton Hardiman (cjazz) - Sunday, 08 May 2011, 07:23 GMT
Last edited by Ionut Biru (wonder) - Sunday, 08 May 2011, 13:17 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:In addition to causing segmentation fault with Firefox, as reported in  FS#24160 , the upgrade to dconf 0.7.4-1 seemed to be instrumental in causing xorg to fail with gdm running. No visible GDM display upon boot -- just three error messages indicating GDMDisplay lasting just over one second, followed by a message that GdmLocalDisplayFactory had reached the "maximum number of X display failures." Downgrading dconf to version 0.7.3-2 fixed my issues with both Firefox and gdm.


Steps to reproduce: Upgrade dconf to 0.7.4-1 and boot Arch Linux running daemon gdm.
This task depends upon

Closed by  Ionut Biru (wonder)
Sunday, 08 May 2011, 13:17 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#24160 
Comment by Ionut Biru (wonder) - Sunday, 08 May 2011, 07:30 GMT
just report it upstream. it will be nice to recompile gdm with debug symbols and look after than in /var/log/gdm for backtraces
Comment by Clayton Hardiman (cjazz) - Sunday, 08 May 2011, 07:33 GMT
Thanks. Will do.
Comment by Greg (dolby) - Sunday, 08 May 2011, 07:34 GMT
Can you reproduce it using the inittab method for running gdm?
Comment by Ionut Biru (wonder) - Sunday, 08 May 2011, 10:14 GMT
so what you guys need to do is to recompile dconf and firefox/xulrunner with debug symbols and get a gdb trace.

https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces#One_package_settings_only

then paste it here and https://bugzilla.gnome.org/show_bug.cgi?id=649635

Loading...