GTK3 crash in various operations

[Timo Jyrinki]

GTK3 crash on this specific machine, preventing lightdm from starting (with GTK3 using greeter), apport-collect for finishing and using menus or multiple tabs in GNOME Terminal.

--- original lightdm report ---

My yakkety installation is now for some reason in shape that lightdm only starts with a black screen, although mouse cursor is shown and movable and "wifi networks available" popup is shown at the top right corner.

After some while this disappears and the system goes to some sort of tty switching loop where sometimes text cursor is shown and sometimes just blank screen. If I want to recover text console control of machine I need to quickly after booting switch to tty1 and stop lightdm.

This started happening last week after some upgrades and a reboot.

I've tried reinstalling and everything I can think of, but I can't fix it. Meanwhile using sddm I can't log in to Unity 7 or 8, and gdm doesn't start at all. So I'm using sddm + Plasma now but would like to be also be able to run Unity 7 and Unity 8.

I couldn't also use ubuntu-bug since I can't use the browser interface from command line (otherwise it works fine until that point) and it segfaults under Plasma environment while collecting information.

[Robert Ancell (robert-ancell)]

Looking at your seat0-greeter.log seems to show something might be going wrong with unity-settings-daemon / your X server:

(unity-settings-daemon:2377): Gdk-WARNING **: unity-settings-daemon: Fatal IO error 11 (Resurssi ei tilapäisesti ole käytettävissä) on X server :0.

Did you recently update any drivers?

[Timo Jyrinki (timo-jyrinki)]

Not other than standard kernel updates in yakkety. It's Intel Braswell hardware.

[Timo Jyrinki (timo-jyrinki)]

Anyway, there are multiple gtk related applications crashing so probably not related to lightdm directly. For example the apport-collect that crashes at some point, or if I open menus in GNOME Terminal or create a new tab.

Zero problems using Qt/KDE apps however.

I agree this is pretty "Incomplete" for glib/GTK too...

[Timo Jyrinki (timo-jyrinki)]

Oh, right, I needed to attach to the gnome-terminal.server to get a backtrace. Here it is, and there seems to be indeed a crash in GTK+3 for me.

[Timo Jyrinki (timo-jyrinki)]

Managed also to gdb into the python process before apport-collect crashed, looks similar: http://pastebin.ubuntu.com/23268999/

On the plus side, since I pinpointed it now to GTK3, I was able to install lightdm-kde-greeter to get non-GTK3 greeter for lightdm, and I can now log in to Unity 8 (which doesn't work with alternative display managers) which is the main test purpose of the machine currently.

[Timo Jyrinki (timo-jyrinki)]

apport-collected info from earlier time for the machine can be seen at bug #1609745.