[Pkg-systemd-maintainers] Bug#730427: logind should replace console-kit in Debian
Vincent Bernat
bernat at debian.org
Sun Nov 24 23:57:30 GMT 2013
Package: systemd
Version: 204-5
Severity: normal
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi!
I am using systemd+lightdm. For some reason, console-kit stopped
working on my system. I am no longer registered in the list of
sessions after logging (ck-list-sessions is empty). However, I am
correctly registered with logind:
$ loginctl show-session $XDG_SESSION_ID
Id=5
Timestamp=lun. 2013-11-25 00:41:18 CET
TimestampMonotonic=44821763894
DefaultControlGroup=systemd:/user/500.user/5.session
VTNr=7
Display=:0
Remote=no
Service=lightdm
Leader=15734
Audit=5
Type=x11
Class=user
Active=yes
State=active
KillProcesses=no
IdleHint=no
IdleSinceHint=0
IdleSinceHintMonotonic=0
Name=bernat
However, absolutely nothing works as expected. I am unable to run
polkit-gnome-authentication-agent-1:
/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 --verbose
** (polkit-gnome-authentication-agent-1:18484): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
(polkit-gnome-authentication-agent-1:18484): polkit-gnome-1-WARNING **: Unable to determine the session we are in: GDBus.Error:org.freedesktop.ConsoleKit.Manager.GeneralError: Unable to lookup session information for process '18484'
And anything that requires an active local user just fails with
permission denied. It seems we are still massively using ConsoleKit. A
quick look at policykit-1 package shows that there is no dependency on
systemd. Therefore, I think that policykit is not able to speak with
logind. This makes the whole chain breaks.
I am filing this bug against systemd because I don't have anything in
hand for this problem. If the problem can be solved just by compiling
policykit with systemd support, please, reassign this bug.
I have also updated pamd files with pam-auth-update --force. No
change.
- -- Package-specific info:
- -- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.12-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages systemd depends on:
ii initscripts 2.88dsf-43
ii libacl1 2.2.52-1
ii libaudit1 1:2.3.2-2
ii libc6 2.17-96
ii libcap2 1:2.22-1.2
ii libcryptsetup4 2:1.6.1-1
ii libdbus-1-3 1.6.18-1
ii libgcrypt11 1.5.3-2
ii libkmod2 9-3
ii liblzma5 5.1.1alpha+20120614-2
ii libpam0g 1.1.3-10
ii libselinux1 2.2.1-1
ii libsystemd-daemon0 204-5
ii libsystemd-journal0 204-5
ii libsystemd-login0 204-5
ii libudev1 204-5
ii libwrap0 7.6.q-24
ii udev 204-5
ii util-linux 2.20.1-5.5
Versions of packages systemd recommends:
ii libpam-systemd 204-5
Versions of packages systemd suggests:
pn systemd-ui <none>
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (GNU/Linux)
iQIcBAEBCAAGBQJSkpJlAAoJEJWkL+g1NSX5AXkQAIjyNu2XToL/BHz48uLIsL13
DNU+vOpZXCJUgfo35kz1/DHTLetFriJpAbbB85fJNIoDyFjcA+Gf7XFIIvJ7Y0ue
8KOwHs9jbFZgV6Gr2P437gFNl1xIcMPLfgzKOEiDmMEeVUiLu4aTKcNFrwzo43Rv
G9hNe2E6ZfL954/Bz2KXNmKY+q8OsPwuZRgzeswxvzfTudMU4JbF4VJTwT63HU+z
J20r4aVzzouZQcdF9KIJx2CQclsbHU9IzYavt9kEGk6Hu3ly+NPckv7QyBzZvY/B
950ObwrI5UNKNHr6Ng6NvDzOr5BFFv3KGIMPdbKyLrXr5VBZQx/fY/mDImEg1X+O
7G+tOEEzsQsx4hZJl+rFaGQ1LeE0nzh5bMnTXCFGt2lCDsBoxCMbxOfWDve1xyW7
UDud7rF/KpIEqcDvrOzDBm+LXpH11fymFi0HizZjpvbb9VLLPFdoe2YVu4RRubsT
G80y8XMsfl2KwYo6BDd4BvoAhi3Ta8czqDfeSskaESzkGcsgu5LiyVfDVjjBC27q
yjPGjNP72pVnfnD8hWUxwjhaHUimsZkU+jNwU030A8UGU9Vvzi9D6Txh1kluvP8Q
4iNghDOSbRTS3WWQPTBTFc/jSrBIIqUGKsWKx9jiVyOqS5fWwUtjVXjaSAA5nyE+
xECOHV22FiNQde0XAxOe
=/4Y1
-----END PGP SIGNATURE-----
More information about the Pkg-systemd-maintainers
mailing list