[Bug 1171691] Re: Removing libpam-systemd (without purge) breaks system
Launchpad Bug Tracker
1171691 at bugs.launchpad.net
Tue Apr 23 12:46:15 UTC 2013
This bug was fixed in the package systemd - 198-0ubuntu11
---------------
systemd (198-0ubuntu11) raring; urgency=low
* debian/libpam-systemd.systemd-logind.upstart: Don't start if
libpam-systemd is removed but not purged. (LP: #1171691)
-- Martin Pitt <martin.pitt at ubuntu.com> Tue, 23 Apr 2013 07:38:20 +0200
** Changed in: systemd (Ubuntu Raring)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1171691
Title:
Removing libpam-systemd (without purge) breaks system
Status in “systemd” package in Ubuntu:
Fix Released
Status in “systemd” source package in Raring:
Fix Released
Bug description:
If libpam-systemd is removed, without purging configuration files,
then it will break gdm/gnome-shell and quite probably any other
package that does runtime detection of logind.
This is due to the leftover upstart script still being run, which
creates various folders that make it look like logind is installed and
running.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: libpam-systemd 198-0ubuntu10
ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
Uname: Linux 3.8.0-19-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
Date: Tue Apr 23 13:40:29 2013
InstallationDate: Installed on 2012-09-23 (212 days ago)
InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha amd64(20120922)
MarkForUpload: True
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1171691/+subscriptions
More information about the foundations-bugs
mailing list