The various PAM packages explicitly declare themselves as multi-arch
compatible. Of course they could just drop their Multi-Arch: flag again
so that you can only have the native PAM stack installed, not a foreign
arch one in parallel. However, I suppose there was a specific reason to
make them
5260 mkdir(/run/systemd/seats, 0755) = -1 ENOENT (No such file or
directory)
That's worrying. That means that the /etc/init/systemd-logind.conf
upstart job failed somehow.
* Do you have the libpam-systemd package installed? If that's missing,
nothing will work really.
* If you do sudo
However with the update (and a restart) I've seen that the
suspend/restart/shutdown icons are still grayed out in my lightdm, and
that the suspend menu is still missing from my KDE, but things are
better
** Changed in: systemd (Ubuntu)
Status: Incomplete = Confirmed
--
You received this
Hi,
To answer your questions :
1/
julien@pcathlon64:~$ aptitude search libpam-systemd
i libpam-systemd - system and
service manager - PAM module
i libpam-systemd:i386 - system and
service
Do I get that right, you have an amd64 system, but had libpam-
systemd:i386 installed, and that confused PAM? Hmm, I wonder how this
can be avoided.
With the right libpam-systemd installed, do you still get that Cannot
launch daemon error? What does the upstart job say now (i. e. sudo
start
Hi,
I had both libpam-systemd:i386 and libpam-sytemd:amd64 on my AMD64
system and this confused PAM.
The upstart job now works fine, I don't have the cannot start daemon.
I didn't post the result of sudo start systemd-logind but it said
started daemon systemd-logind or something like this. And
To avoid this, it might be possible to set some kind of conflict between
the i386 module and the amd64 module ? OK it smells, but this might be
an option. What do you think ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
I've also fixed the issue for the suspend feature and lightdm feature by
removing packages libpam-modules:i386 and libpam-cap:i386, which have
the same kind of conflict as explained above. I don't know what happened
during the upgrade, but it looks like the upgrade tool was a bit lost
between
I've also found this in my syslog :
Mar 26 07:46:00 pcathlon64 dbus[1249]: [system] Activating service
name='org.freedesktop.login1' (using servicehelper)
Mar 26 07:46:00 pcathlon64 dbus[1249]: [system] Activated service
'org.freedesktop.login1' failed: Cannot launch daemon, file not found or
Also tried with qdbus with the following line (as I'm using KDE) :
qdbus --system org.freedesktop.login1 /org/freedesktop/login1
org.freedesktop.login1.Manager.CanReboot
Error: org.freedesktop.DBus.Error.Spawn.ExecFailed
Cannot launch daemon, file not found or permissions invalid
--
You
Another stuff in my auth.log which may help :
Mar 26 21:13:14 pcathlon64 sudo: PAM unable to dlopen(pam_cap.so):
/lib/security/pam_cap.so: Ne peut ouvrir le fichier d'objet p
artagé: Aucun fichier ou dossier de ce type
Mar 26 21:13:14 pcathlon64 sudo: PAM adding faulty module: pam_cap.so
-- On
After installing pamcap in 64 bits message PAM unable to
dlopen(pam_cap.so): /lib/security/pam_cap.so disappeared, however the
issue is still there. :-(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Oh, if it doesn't work, please copypaste the entire output, there
should be an error message (like permission denied by polkit or
something). Please also give me the output of loginctl.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
As your normal user in a GUI session, can you please give me the output
of
gdbus call -y -d org.freedesktop.login1 -o /org/freedesktop/login1 -m
org.freedesktop.login1.Manager.CanReboot
That ought to be something like ('yes',).
If that says yes, can you confirm that rebooting works with
Hi,
When launching gdbus, error is :
julien@pcathlon64:~$ gdbus call -y -d org.freedesktop.login1 -o
/org/freedesktop/login1 -m org.freedesktop.login1.Manager.CanReboot
Erreur : GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Cannot launch
daemon, file not found or permissions invalid
Oh and from my lightdm logs I also get the following messages :
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Aucun
fichier ou dossier de ce type
QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
Bus::open: Can not get ibus-daemon's address.
If you run
sudo /lib/systemd/systemd-logind
what happens? I suppose this crashes somehow? If not, press Control-C to
end it again. Please copypaste the output.
logind (now replaced with systemd)
For the record, that's wrong. ConsoleKit has been replaced with logind,
and we don't use systemd
Hi,
For the output, it gives me the following :
administrateur@pcathlon64:~$ sudo /lib/systemd/systemd-logind
[sudo] password for administrateur:
Watching system buttons on /dev/input/event1 (Power Button)
Watching system buttons on /dev/input/event0 (Power Button)
New seat seat0.
Failed to
** Changed in: systemd (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1295521
Title:
cannot shutdown/suspend/restart from the GUI
To manage
Failed to save seat data for seat0: No such file or directory
Interesting. But the mere fact that this worked and got so far shows
that logind isn't running by default, which it should. Can you please do
sudo strace -fvvs1024 -o /tmp/logind.txt /lib/systemd/systemd-logind
and attach
Attached file.
** Attachment added: logind.txt
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1295521/+attachment/4043358/+files/logind.txt
** Changed in: systemd (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
** Also affects: lightdm
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1295521
Title:
cannot shutdown/suspend/restart from the GUI
To manage
** Package changed: shadow (Ubuntu) = lightdm (Ubuntu)
** Package changed: lightdm (Ubuntu) = systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1295521
Title:
cannot
23 matches
Mail list logo
