Arch Linux

gim

Member

Registered: 2013-07-27

Posts: 35

DM breakage after last update

For the first time in 2 years using Arch I have no idea what to do, please help. Which recent package update could cause display managers fail to show up at start? Instead of login prompt I get a black screen or just a bootup output stuck there (without any error messages). I'm using GDM, though I tried to launch lightdm and it behaves the same way.

Some logs after launcing "lightdm --test-mode --debug":
lightdm.log: http://slexy.org/view/s2myvLYxTw
x-0.log: http://slexy.org/view/s2K4KjXbMZ

Here is a list of packages I updated before that happened:

[2015-02-18 22:34] [ALPM] upgraded libsystemd (218-1 -> 218-2)
[2015-02-18 22:34] [ALPM] upgraded perl (5.20.1-1 -> 5.20.2-1)
[2015-02-18 22:34] [ALPM] upgraded krb5 (1.13-1 -> 1.13.1-1)
[2015-02-18 22:34] [ALPM] warning: directory ownership differs on /var/log/journal/remote/
filesystem: 0:994  package: 0:0
[2015-02-18 22:34] [ALPM] upgraded systemd (218-1 -> 218-2)
[2015-02-18 22:34] [ALPM] upgraded android-udev (r124-1 -> r135-1)
[2015-02-18 22:34] [ALPM] upgraded ca-certificates-mozilla (3.17.3-2 -> 3.17.4-1)
[2015-02-18 22:34] [ALPM] upgraded libinput (0.7.0-1 -> 0.10.0-1)
[2015-02-18 22:34] [ALPM] upgraded wayland (1.6.1-1 -> 1.7.0-1)
[2015-02-18 22:34] [ALPM] upgraded clutter (1.20.0-2 -> 1.20.0-3)
[2015-02-18 22:34] [ALPM] upgraded exempi (2.2.1-2 -> 2.2.2-1)
[2015-02-18 22:34] [ALPM] upgraded nspr (4.10.7-1 -> 4.10.8-1)
[2015-02-18 22:34] [ALPM] upgraded gedit (3.14.2-1 -> 3.14.3-1)
[2015-02-18 22:34] [ALPM] upgraded ghostscript (9.15-1 -> 9.15-2)
[2015-02-18 22:34] [ALPM] upgraded go (2:1.4.1-1 -> 2:1.4.2-1)
[2015-02-18 22:34] [ALPM] upgraded nss (3.17.3-2 -> 3.17.4-1)
[2015-02-18 22:34] [ALPM] upgraded gufw (15.04.0-1 -> 15.04.4-1)
[2015-02-18 22:34] [ALPM] upgraded lib32-krb5 (1.13-1 -> 1.13.1-1)
[2015-02-18 22:34] [ALPM] upgraded lib32-libpciaccess (0.13.2-1 -> 0.13.3-1)
[2015-02-18 22:34] [ALPM] upgraded libcanberra (0.30-4 -> 0.30-5)
[2015-02-18 22:34] [ALPM] upgraded libcanberra-pulse (0.30-4 -> 0.30-5)
[2015-02-18 22:34] [ALPM] upgraded libwnck (2.30.7-2 -> 2.31.0-1)
[2015-02-18 22:34] [ALPM] upgraded lirc (1:0.9.2-1 -> 1:0.9.2.a-1)
[2015-02-18 22:34] [ALPM] upgraded mpv (0.7.3-1 -> 0.8.0-1)
[2015-02-18 22:34] [ALPM] upgraded powertop (2.7-1 -> 2.7-2)
[2015-02-18 22:34] [ALPM] upgraded system-config-printer (1.5.5-1 -> 1.5.5-2)
[2015-02-18 22:34] [ALPM] upgraded systemd-sysvcompat (218-1 -> 218-2)
[2015-02-18 22:35] [ALPM] upgraded virtualbox-host-dkms (4.3.20-6 -> 4.3.22-1)

Downgrading these fixed the issue

clutter
exempi
nspr
nss
gufw
libcanberra
libcanberra-pulse
libwnck
lirc
systemd-sysvcompat
systemd

Then I tried to do -Syu again and downgrade them one-by-one to see which one caused this. And now even if I downgrade everything again, issue is still present. Any ideas what's happening?

UPD: Looks like lightdm works now, but I can't login in to gnome-shell. GNOME shows a big window saying "Oh no, something gone wrong" and with the only button - "log out".

Last edited by gim (2015-02-19 09:30:48)

gim

Member

Registered: 2013-07-27

Posts: 35

Re: DM breakage after last update

Some weird shit. I noticed that pacman lose some file associations and "ldconfig" had some issues with "/usr/lib/libwnck-1.so.22.3.31" (which were not owned by any package too). I removed "/usr/lib/libwnck-1.so.22.3.31" and reinstalled ALL packages from official repositories like this:

pacman -S $(pacman -Qqn) --force

Now it works allright... No idea, I did nothing but package updates on my system for the past week.

Last edited by gim (2015-02-19 11:02:52)