Forum rules
Please supply only the affected package name as title, with bugreport number (bugs.debian.org) or other sources. This feed can be subscribed to and piped into your RSS reader or conky: http://linuxbbq.org/bbs/feed.php?mode=news
-
vic
- Godot
- Posts: 2118
- Joined: Wed Oct 17, 2012 10:11 am
- Location: /bin
Unread post
by vic » Fri Oct 09, 2015 9:46 am
Got this today on BORK! 64bit. Decided to wait since I am a bit sensitive when it comes to x stuff.
Code: Select all
serious bugs of xserver-xorg-core (2:1.17.2-1.1 → 2:1.17.2-3) <Outstanding>
b1 - #798097 - Restarting logind kills Xserver
mb edit: apparently it is bug #801401
-
GekkoP
- Emacs Sancho Panza
- Posts: 5878
- Joined: Tue Sep 03, 2013 7:05 am
Unread post
by GekkoP » Fri Oct 09, 2015 10:05 am
Everything's good here.
![Image](http://s4.postimg.org/3tdshrp09/2015_10_09_110438_1019x233_scrot.jpg)
-
dkeg
- Configurator
- Posts: 3782
- Joined: Sun Nov 18, 2012 9:23 pm
- Location: Mid-Atlantic Grill
Unread post
by dkeg » Fri Oct 09, 2015 10:48 am
Logind is product of systemd, no?
Work hard; Complain less
-
simgin
- Meme Fodder
- Posts: 1167
- Joined: Sun Jan 06, 2013 12:07 am
- Location: Bradford-on-Avon, UK
Unread post
by simgin » Fri Oct 09, 2015 10:54 am
No problems here either. What have you done Vic? ;)
Someone told me that I am delusional, I almost fell off my unicorn.
-
vic
- Godot
- Posts: 2118
- Joined: Wed Oct 17, 2012 10:11 am
- Location: /bin
Unread post
by vic » Fri Oct 09, 2015 11:45 am
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.
-
GekkoP
- Emacs Sancho Panza
- Posts: 5878
- Joined: Tue Sep 03, 2013 7:05 am
Unread post
by GekkoP » Fri Oct 09, 2015 11:55 am
^ 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.
-
vic
- Godot
- Posts: 2118
- Joined: Wed Oct 17, 2012 10:11 am
- Location: /bin
Unread post
by vic » Fri Oct 09, 2015 12:13 pm
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.
-
machinebacon
- Baconator
- Posts: 10253
- Joined: Thu Sep 16, 2010 11:03 am
- Location: Pfälzerwald
-
Contact:
Unread post
by machinebacon » Fri Oct 09, 2015 3:52 pm
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.
..gnutella..
-
vic
- Godot
- Posts: 2118
- Joined: Wed Oct 17, 2012 10:11 am
- Location: /bin
Unread post
by vic » Fri Oct 09, 2015 4:19 pm
Thanks for info machinebacon, will check it up during the weekend. The comfort in this is that my main BORK! system is still untainted. :)
-
machinebacon
- Baconator
- Posts: 10253
- Joined: Thu Sep 16, 2010 11:03 am
- Location: Pfälzerwald
-
Contact:
Unread post
by machinebacon » Sat Oct 10, 2015 5:55 am
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.
..gnutella..
-
GekkoP
- Emacs Sancho Panza
- Posts: 5878
- Joined: Tue Sep 03, 2013 7:05 am
Unread post
by GekkoP » Sat Oct 10, 2015 11:12 am
I dist-upgraded and a new version of libpam-systemd. Now autologin is working again.
Code: Select all
libpam-systemd:
Installed: 227-2
Candidate: 227-2
Version table:
*** 227-2 0
500 http://ftp.de.debian.org/debian/ unstable/main amd64 Packages
100 /var/lib/dpkg/status
-
machinebacon
- Baconator
- Posts: 10253
- Joined: Thu Sep 16, 2010 11:03 am
- Location: Pfälzerwald
-
Contact:
Unread post
by machinebacon » Sat Oct 10, 2015 12:37 pm
systems without libpam-systemd need downgrade above mentioned packages. valid for those whose desktop froze after login
..gnutella..
-
dkeg
- Configurator
- Posts: 3782
- Joined: Sun Nov 18, 2012 9:23 pm
- Location: Mid-Atlantic Grill
Unread post
by dkeg » Sat Oct 10, 2015 5:17 pm
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.
Work hard; Complain less
-
machinebacon
- Baconator
- Posts: 10253
- Joined: Thu Sep 16, 2010 11:03 am
- Location: Pfälzerwald
-
Contact:
Unread post
by machinebacon » Sat Oct 10, 2015 7:39 pm
downgrade to the version you have in the archive folder.
typed it on phone, maybe typo.
or get packages from debian server manually.
..gnutella..
-
ivanovnegro
- Minister of Truth
- Posts: 5449
- Joined: Wed Oct 17, 2012 11:12 pm
Unread post
by ivanovnegro » Sun Oct 11, 2015 2:42 pm
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.
-
machinebacon
- Baconator
- Posts: 10253
- Joined: Thu Sep 16, 2010 11:03 am
- Location: Pfälzerwald
-
Contact:
Unread post
by machinebacon » Sun Oct 11, 2015 2:44 pm
thanks for translating hungarian chinese to real English:)
..gnutella..
-
wuxmedia
- Grasshopper
- Posts: 6454
- Joined: Wed Oct 17, 2012 11:32 am
- Location: Back in Blighty
-
Contact:
Unread post
by wuxmedia » Mon Oct 12, 2015 7:38 am
I'm just waiting the storm out...
-
vic
- Godot
- Posts: 2118
- Joined: Wed Oct 17, 2012 10:11 am
- Location: /bin
Unread post
by vic » Mon Oct 12, 2015 9:35 am
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
-
ivanovnegro
- Minister of Truth
- Posts: 5449
- Joined: Wed Oct 17, 2012 11:12 pm
Unread post
by ivanovnegro » Mon Oct 12, 2015 2:21 pm
I would let it open for a while. It is even a sticky until the Debian folks close the bug.