*** This bug is a duplicate of bug 432964 ***
https://bugs.launchpad.net/bugs/432964
Hi,
The original report in this bug is the same as bug 432964, please see
there for a workaround.
Other people seem to have other bugs, so could you please report them
separately?
Thanks,
James
** This
I'm getting this too:
sudo dpkg -i --force-overwrite
/var/cache/apt/archives/kerneloops-daemon_0.12+git20090217-1ubuntu4.1_i386.deb
Selecting previously deselected package kerneloops-daemon.
(Reading database ... 221449 files and directories currently installed.)
Unpacking kerneloops-daemon (from
same error nov. 19, 2009. see excerpts from term.log: [German] :
Richte kerneloops-daemon ein (0.12+git20090217-1ubuntu4.1) ...
Your account has expired; please contact your system administrator
chfn: PAM authentication failed
adduser: »/usr/bin/chfn -f Kernel Oops Tracking Daemon kernoops« gab
I have a dirty workaround:
sudo dpkg -i --force-overwrite
/var/cache/apt/archives/kerneloops-daemon_0.12+git20090217-1ubuntu3_i386.deb
This command fix my problem, but it can be risky and I may have broken
something in my system.
--
package kerneloops-daemon 0.12+git20090217-1ubuntu2
Hi,
--force-overwrite suggest a missing replaces. Do you still have
the terminal output from when you were trying these things?
Thanks,
James
--
package kerneloops-daemon 0.12+git20090217-1ubuntu2 failed to install/upgrade:
el subproceso script post-installation instalado devolvió el código
Sure, /var/log/apt/term.log shows:
Preparing to replace kerneloops-daemon 0.12+git20090217-1ubuntu2 (usando
.../kerneloops-daemon_0.12+git20090217-1ubuntu3_i386.deb) ...
* Stopping Kernel Oops catching service kerneloops [ OK ]
Unpacking replacement kerneloops-daemon ...
dpkg: error
Same for me. dpkg --configure -a dont help.
--
package kerneloops-daemon 0.12+git20090217-1ubuntu2 failed to install/upgrade:
el subproceso script post-installation instalado devolvió el código de salida
de error 1
https://bugs.launchpad.net/bugs/426083
You received this bug notification
Hi,
Thanks for taking the time to report this bug. It appears
as though something odd was going on at the time you had
these issues. Did you have any admin applications open
or anything as you were doing the updates?
If you reboot and run dpkg --configure -a in a terminal do
you still get
** Attachment added: AptOrdering.txt
http://launchpadlibrarian.net/31473196/AptOrdering.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/31473197/Dependencies.txt
** Attachment added: Dmesg.txt
http://launchpadlibrarian.net/31473198/Dmesg.txt
** Attachment
