Bug#681195: gdm3 displays "Oh No! Something has gone wrong" screen on Alpha

[Michael Cree]

On 13/07/12 00:57, Josselin Mouette wrote:
> Le jeudi 12 juillet 2012 à 19:33 +1200, Michael Cree a écrit : 
>> On 12/07/12 02:04, Josselin Mouette wrote:
>>> Can you attach your /etc/gdm3/greeter.gsettings file?
>>>
>>> If it wasn’t modified, you will also find useful logs
>>> in /var/log/gdm3/:0-greeter.log
>>
>> Both attached.
> 
> The settings file is OK.
> 
> The logs show that the gnome-session process is terminated right after
> being started. This might be caused either by early termination of the
> gdm-simple-greeter process, or by the gdm-simple-slave process deciding
> to kill gnome-session for a reason or another.
> 
> Either way I don’t have enough information to debug the problem, so I’ll
> leave you (or an alpha porter) at debugging what happens.

Looking more closely at that session log I see that
gnome-settings-daemon has been terminated with signal 11.  That's a
segmentation violation.

I presume gdm3 is therefore spawning other programs.  Is there a way I
can get them (or gnome-settings-daemon in particular) to run under gdb
when gdm3 is invoked?  Or get it to dump core to a findable place?  That
way, I may be able to track down where the segmentation violation is
occurring.

Cheers
Michael.