package kdm 4:4.3.5-0ubuntu1~karmic1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #522442 reported by r_avital
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kdebase-workspace (Ubuntu)
New
Undecided
Unassigned

Bug Description

package kdm 4:4.3.5-0ubuntu1~karmic1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Release 9.10

apt-cache policy returns:
  Installed: 4:4.3.5-0ubuntu1~karmic1
  Candidate: 4:4.3.5-0ubuntu1~karmic1
  Version table:
 *** 4:4.3.5-0ubuntu1~karmic1 0
        500 http://us.archive.ubuntu.com karmic-backports/main Packages
        100 /var/lib/dpkg/status
     4:4.3.2-0ubuntu7.1 0
        500 http://us.archive.ubuntu.com karmic-updates/main Packages
     4:4.3.2-0ubuntu7 0
        500 http://us.archive.ubuntu.com karmic/main Packages
W: Unable to locate package 4:4.3.5-0ubuntu1~karmic1

Expected: successful completion of weekly update.
Instead: Exited with above error message

ProblemType: Package
Architecture: i386
Date: Fri Feb 12 09:43:03 2010
DistroRelease: Ubuntu 9.10
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
NonfreeKernelModules: nvidia
Package: kdm 4:4.3.5-0ubuntu1~karmic1
ProcVersionSignature: Ubuntu 2.6.31-20.57-generic
SourcePackage: kdebase-workspace
Title: package kdm 4:4.3.5-0ubuntu1~karmic1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Uname: Linux 2.6.31-20-generic i686

Revision history for this message
r_avital (ravital) wrote :
Revision history for this message
Monkey (monkey-libre) wrote :

I´ve assigned this bug to the kdm package. Thank You for making Ubuntu better.

affects: ubuntu → kdebase-workspace (Ubuntu)
Revision history for this message
Rich (rincebrain) wrote :

Problem is that it can't find whatever it thinks the default DM should be - in my case, gdm-2.20, and so errors out.

My solution was to symlink the filename it was searching for (gdm-2.20) to the actual binary name (gdm) in /usr/sbin, and it passes configure correctly.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.