Removing libpam-systemd (without purge) breaks system
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| systemd (Ubuntu) |
Fix Released
|
Medium
|
Martin Pitt | ||
| Raring |
Fix Released
|
Medium
|
Martin Pitt | ||
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
ProcVersionSign
Uname: Linux 3.8.0-19-generic x86_64
NonfreeKernelMo
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)
Related branches
| Tim Lunn (darkxst) wrote | #1 |
| Martin Pitt (pitti) wrote | #2 |
| Changed in systemd (Ubuntu Raring): | |
| assignee: | nobody → Martin Pitt (pitti) |
| importance: | Undecided → Medium |
| status: | New → In Progress |
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in systemd (Ubuntu Raring): | |
| status: | In Progress → Fix Released |
I uploaded a fix to the raring-proposed queue.