LinuxBBQ

Got this today on BORK! 64bit. Decided to wait since I am a bit sensitive when it comes to x stuff.

mb edit: apparently it is bug #801401

Everything's good here.

Logind is product of systemd, no?

No problems here either. What have you done Vic? ;)

Hehehe...something evil has creeped into my system it seems. Yes I believe logind is something systemd stuff. Saw the same on another install were there definitely are systemd.

^ I'm on systemd too, and the only minor issue I had was the automatic login (as detailed by pidsley in another topic) not working. A simple startx did the trick, so I'm ok.

I have an install that is very similar to the one in my first post. So, performed the upgrade, could not log in. Took the startx route, came into the desktop, but there everything were frozen, had to pull the plug. Grub claims that it is sysvinit though. Aaaaaargh.

on some hardware a pkill -9 X can put the system into non-responsive mode. alt sysreq reisub works, or pulling the plug. this has been around for quite a while, i estimate 8 months or so. not sure if logind is to blame, happens on xinit.
make sure you have no zzz-... files in /etc/login.d/ except bash-related entries. sometimes live-boot drops a shitty startx script there, which IMO should not happen in sysvinit.
logind comes from libpam-systemd, which is probably pulled in by some shit like udisks, policykit or sustemd. if you don't need automount and gvfs, drop polkit and udisks2 to remove logind in libpam.

Thanks for info machinebacon, will check it up during the weekend. The comfort in this is that my main BORK! system is still untainted. :)

FIX:

you can do this in a TTY (e.g. TTY2)
It should show the affected xserver packages. you can then try startx in TTY1 or reboot.

I dist-upgraded and a new version of libpam-systemd. Now autologin is working again.

systems without libpam-systemd need downgrade above mentioned packages. valid for those whose desktop froze after login

machinebacon wrote:FIX:

you can do this in a TTY (e.g. TTY2)

Code: Select all

tail -n 15 /var/log/apt/history.log|grep xs

It should show the affected xserver packages.

Code: Select all

sudo dpkg -i xserver-xorg-core2%3a1.17.2-1.1_i386.deb xserver-common-2%3a1.17.2-1.1_all.deb xserver-xorg_1%3a1.17.2-1.1_i386.deb 

you can then try startx in TTY1 or reboot.

I'm having trouble with this. says 'cannot access archive:no such file or directory'

If I startx I get in but am unable to do anything but hard power off. No access even to tty. I can see the output with the tail syntax above.

downgrade to the version you have in the archive folder.
typed it on phone, maybe typo.
or get packages from debian server manually.

In short, people having problems with the d-u, put xserver-xorg-core on hold. If you already pulled the newer package try reverting that e.g. by downloading the older xserver package from the Debian mirrors.

thanks for translating hungarian chinese to real English:)

I'm just waiting the storm out...

Thanks for input, cheers and good advice. Got shit working again, but this old laptop is such a piece of shit that I nearly smashed it. Promise that I will dispose of it at the crappy lappy junkyard before the end of this year. I saw no sign of the bug on another
Sid install and du went well. Yeah and me...forgot to check Siductiion forums again??? How schmucky stupid is it possible to be???
Like vic! Well lesson learnt for the twentytwelth time or something I suppose. Til next time that is. :D

I would let it open for a while. It is even a sticky until the Debian folks close the bug.