Siduction Forum
Siduction Forum => Upgrade Warnings => Topic started by: samoht on 2015/06/24, 13:02:41
-
After d-u-ing today lightdm did not launch.
Error messages (... sorry for German localization :-[ ):
policykit-1 (0.112-5.2) wird eingerichtet ...
Neue Version der Konfigurationsdatei /etc/dbus-1/system.d/org.freedesktop.PolicyKit1.conf wird installiert ...
adduser: Warnung: Das Home-Verzeichnis »/var/lib/polkit-1« gehört nicht dem Benutzer, den Sie gerade anlegen.
Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24)
Failed to execute operation: Die Wartezeit für die Verbindung ist abgelaufen
Removing obsolete conffile /etc/polkit-1/nullbackend.conf.d/50-nullbackend.conf ...
Removing obsolete conffile /etc/polkit-1/localauthority.conf.d/50-localauthority.conf ...
Removing obsolete conffile /etc/polkit-1/localauthority.conf.d/51-debian-sudo.conf ...
Downgrading policykit-1 to testing/unstable resolved this issue.
# LANG=C apt-cache policy policykit-1
policykit-1:
Installed: 0.105-8
Candidate: 0.112-5.2
Version table:
0.112-5.2 0
500 http://ftp.spline.de/pub/siduction/extra/ unstable/main amd64 Packages
0.112-5 0
1 http://ftp.de.debian.org/debian/ experimental/main amd64 Packages
*** 0.105-8 0
500 http://ftp.de.debian.org/debian/ testing/main amd64 Packages
500 http://ftp.de.debian.org/debian/ unstable/main amd64 Packages
-
It did not break here, but I do see some new errors about the session.
root@imerabox:/# apt-cache policy policykit-1
policykit-1:
Installed: 0.112-5.2
Candidate: 0.112-5.2
Version table:
*** 0.112-5.2 0
500 ftp://ftp.gtlib.gatech.edu/pub/siduction/extra/ unstable/main amd64 Packages
100 /var/lib/dpkg/status
0.105-8 0
500 http://http.debian.net/debian/ unstable/main amd64 Packages
root@imerabox:/# systemctl status lightdm
● lightdm.service - Light Display Manager
Loaded: loaded (/lib/systemd/system/lightdm.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2015-06-24 10:14:44 EDT; 3h 48min ago
Docs: man:lightdm(1)
Process: 17024 ExecStartPre=/bin/sh -c [ "$(cat /etc/X11/default-display-manager 2>/dev/null)" = "/usr/sbin/lightdm" ] (code=exited, status=0/SUCCESS)
Main PID: 17028 (lightdm)
CGroup: /system.slice/lightdm.service
├─17028 /usr/sbin/lightdm
├─17033 /usr/bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
└─17063 ssh-agent
Jun 24 10:14:44 imerabox systemd[1]: Starting Light Display Manager...
Jun 24 10:14:44 imerabox lightdm[17028]: ** (lightdm:17028): WARNING **: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.Servi...ervice files
Jun 24 10:14:44 imerabox systemd[1]: Started Light Display Manager.
Jun 24 10:14:44 imerabox lightdm[17028]: ** (lightdm:17028): CRITICAL **: session_get_login1_session_id: assertion 'session != NULL' failed
Jun 24 10:14:44 imerabox lightdm[17028]: ** (lightdm:17028): CRITICAL **: session_get_login1_session_id: assertion 'session != NULL' failed
Jun 24 10:14:44 imerabox lightdm[17028]: ** (lightdm:17028): CRITICAL **: session_get_login1_session_id: assertion 'session != NULL' failed
Jun 24 10:14:45 imerabox lightdm[17028]: ** (process:17057): WARNING **: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.Servi...ervice files
Jun 24 10:14:45 imerabox lightdm[17057]: pam_unix(lightdm-autologin:session): session opened for user don by (uid=0)Hint: Some lines were ellipsized, use -l to show in full.
-
https://bbs.archlinux.org/viewtopic.php?id=185216
-
hello samoht,
i remember i have seen those message from policikit-1 while dist-upgrading.
Lightdm works fine here™.
Let's assume the two incidents are unrelated.
Does X still start (does text mode login disappear, or do you see a mouse cursor on an empty screen)?
Are you able to login in text mode (perhaps you need to press Ctrl-Alt-F1)? You can run "siduction-irc".
greetings
musca
-
Thanks to all for helpful comments.
Today I upgraded the packages policykit-1 and lightdm again and all went well.
I suppose the reason for lightdm 's failing launch was not the upgraded package policykit-1.
Greetings
Tom
-
This moment I did a full d-u, but still policykit-1 complains like cited by samoth in his first posting. No problem starting X though (this is my notebook with systemd running). No autostart here.