Comment 15 for bug 954352

Revision history for this message
Darxus (darxus) wrote :

I did some testing of the previously mentioned ppa:ricotz/staging under Precise.
It is not at all usable. Due, I believe, to problems in gtk+, not the packaging. ricotz tells me that enabling both the wayland and x11 backends for gtk+ is just broken.

Without adding a ~/.xsessionrc, X does not start. After adding ~/.xsessionrc containing

export CLUTTER_BACKEND=x11
export GDK_BACKEND=x11

X didn't start on startup, but did start when I ran startx. Didn't do much other than notify me that nautilus crashed and ask me if I wanted to report it.

I tried running gnome-terminal from the console. It gave me the expected error that DISPLAY wasn't set, so I set it (export DISPLAY=:0). Then it gave a XDG_RUNTIME_DIR not set warning, which is a wayland thing. So I set the above two BACKEND variables in that shell, and tried again, and gnome-terminal gave me:

Gdk-CRITICAL **: gdk_wayland_device_get_selection_type_atoms_libgtk_only: assertion `GDK_IS_DEVICE_CORE (gdk_device)' failed

Before doing any of this, I recommend: apt-get install ppa-purge
Also, if you end up at a text console that isn't responding to your keyboard, do alt-sysrq-r.
And if you need to switch between nvidia proprietary and nouveau drivers from the console because X won't start, you can use jockey-text, although it looks like it doesn't update /etc/X11/xorg.conf, which is necessary, so have working backup copies of that file.
You should also know about rebooting via alt-sysrq reisub, although I haven't had to do that in this process.

What I did was, freshly install Precise, then:
sudo apt-get update && apt-get dist-upgrade
sudo add-apt-repository ppa:ricotz/staging
sudo apt-get install libcairo2 libcairo-gobject2 gir1.2-gtk-3.0 libgail-3-0 libgtk-3-0 libgtk-3-bin libgtk3-common

Then to revert: sudo ppa-purge ppa:ricotz/staging

I also came across a weird bug where a third line containing "ain" was showing up in /etc/apt/sources.list.d/ricotz-staging-precise.list, probably an add-apt-repository bug. Just edit that file and delete that line.