You should give more info on how you managed to get into this situation.
The real problem is that the postdrop group has been removed while it
was still in use by dpkg for some statoverride information. Either
postfix did drop the group without unregistering the statoverride, or
you made a mistake
This is update-inetd not working due to missing File/Temp.pm module.
What's the output of dpkg -S File/Temp.pm ? And dpkg -s perl-modules
update-inetd ?
In any case it's not a dpkg issue... maybe samba should also be improved
to not fail when update-inetd fails in postrm ? Not sure.
** Package
Clint, where do you see a *circular* dependency? The dependencies that
you show are not circular.
Also the ordering of package installation is decided by apt and not
dpkg, so this is an apt bug if any.
** Also affects: apt (Ubuntu)
Importance: Undecided
Status: New
--
You received
Upstream doesn't impose anything. ubuntu has made the choice to keep
that setting via the Dpkg::Vendor infrastructure. Thus marking it as
wontfix for dpkg.
** Changed in: dpkg (Ubuntu)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server
Reassigning to fglrx since its preinst script is failing.
** Package changed: dpkg (Ubuntu) = fglrx-installer (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/860822
Title:
package fglrx
Do you have the oneiric version of nautilus-dropbox installed ? Are you
on i386 or on amd64 ?
Does a rebuild of the package fix the problem for you ? You can learn
how to rebuild a package here: http://raphaelhertzog.com/2010/12/15
/howto-to-rebuild-debian-packages/
--
You received this bug
Gary, so drop /usr/lib/python2.6/dist-
packages/gwibber/microblog/dispatcher.py and retry.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/573696
Title:
dpkg: ../../src/archives.c:763: tarobject:
The fix for this has been included in dpkg 1.16.1 upstream.
** Changed in: dpkg (Ubuntu)
Status: Confirmed = Fix Committed
** Bug watch added: Debian Bug tracker #639229
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639229
** Also affects: dpkg (Debian) via
The log in #861827 seems to indicate that it's the postrm of kde-
window-manager that we're upgrading from that is hanging...
** Package changed: dpkg (Ubuntu) = kde-workspace (Ubuntu)
** Changed in: kde-workspace (Ubuntu)
Status: Incomplete = New
--
You received this bug notification
Search no longer, 0.6.8-1 works fine but 0.6.9 from the dropbox
repository is probably not compiled for Nautilus 3.2...
Please don't file bug against Ubuntu if you're not using the official
Ubuntu package. I would suggest to disable the dropbox repository and
downgrade to the Ubuntu package.
**
You have been given bad advice. They meant sudo dpkg --configure -a or
sudo apt-get -f install. But this is not a user support channel... so
I'm closing this bug report since it doesn't contain any useful bug.
Concerning the dpkg-mainscript-helper: error: couldn't identify the
package error
Please read the error message, it's not a bug in the package but a
problem with your connection to the dropbox servers. When your internet
connection works again, sudo dpkg --configure -a will finish the
installation of nautilus-dropbox.
** Changed in: nautilus-dropbox (Ubuntu)
Status: New
I'm afraid this has been hastily reassigned, there's no data in the bug
log to decide where the problem is. There's no proof that dpkg is
blocking and I'm quite sure it doesn't. However one of the packages that
you are trying to install might well try to interact with you on the
terminal and if
šumski, this article explains that it's a corrupted .deb file and thus
an invalid bug report... not that the bug must be reassigned to dpkg and
reopened!
** Changed in: dpkg (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This is already fixed in newer releases (0.7.1-*).
** Changed in: nautilus-dropbox (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/945502
Title:
package
*** This bug is a duplicate of bug 937546 ***
https://bugs.launchpad.net/bugs/937546
** This bug has been marked a duplicate of bug 937546
package nautilus-dropbox (not installed) failed to install/upgrade:
subprocess installed post-removal script returned error exit status 2
--
You
This was a bug in glib, it has been fixed in the mean time.
** Visibility changed to: Public
** Changed in: nautilus-dropbox (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This was a bug in glib, it has been fixed in the mean time.
** Visibility changed to: Public
** Changed in: nautilus-dropbox (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The segmentation fault happens in the shared-mime-info package (in its
postinst script). It's not a bug in dpkg.
** Package changed: dpkg (Ubuntu) = shared-mime-info (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
dpkg is just reporting that rm failed. Somehow I doubt it's a bug in
rm, it's more likely an underlying hardware problem (memory corrupted?).
Reassigning to coreutils but changing it to incomplete because I doubt
anyone can reproduce it...
** Package changed: dpkg (Ubuntu) = coreutils (Ubuntu)
Installing binaries in ~/.dropbox-dist/ of each user and letting any
user process update them there is certainly not a good choice from a
security point of view (and it's certainly not in line with the Debian
policy). Having a single way to install the binary system-wide and
having that mechanism
For the record, just like any wrapper, the user can force an update/re-
installation at any point of time with dropbox update.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/909488
Title:
*** This bug is a duplicate of bug 932627 ***
https://bugs.launchpad.net/bugs/932627
** This bug has been marked a duplicate of bug 937784
nautilus crashed with SIGABRT in g_thread_abort()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
*** This bug is a duplicate of bug 932627 ***
https://bugs.launchpad.net/bugs/932627
** This bug is no longer a duplicate of bug 937784
nautilus crashed with SIGABRT in g_thread_abort()
** This bug has been marked a duplicate of bug 932627
nautilus crashes when opening any folder or
*** This bug is a duplicate of bug 932627 ***
https://bugs.launchpad.net/bugs/932627
** This bug is no longer a duplicate of bug 937784
nautilus crashed with SIGABRT in g_thread_abort()
** This bug has been marked a duplicate of bug 932627
nautilus crashes when opening any folder or
*** This bug is a duplicate of bug 932627 ***
https://bugs.launchpad.net/bugs/932627
** This bug is no longer a duplicate of bug 937872
nautilus crashed with SIGABRT in g_thread_abort()
** This bug has been marked a duplicate of bug 937784
nautilus crashed with SIGABRT in
*** This bug is a duplicate of bug 932627 ***
https://bugs.launchpad.net/bugs/932627
** This bug has been marked a duplicate of bug 937784
nautilus crashed with SIGABRT in g_thread_abort()
** This bug is no longer a duplicate of bug 937784
nautilus crashed with SIGABRT in
*** This bug is a duplicate of bug 932627 ***
https://bugs.launchpad.net/bugs/932627
** This bug is no longer a duplicate of bug 937784
nautilus crashed with SIGABRT in g_thread_abort()
** This bug has been marked a duplicate of bug 932627
nautilus crashes when opening any folder or
*** This bug is a duplicate of bug 932627 ***
https://bugs.launchpad.net/bugs/932627
** This bug is no longer a duplicate of bug 937872
nautilus crashed with SIGABRT in g_thread_abort()
** This bug has been marked a duplicate of bug 937784
nautilus crashed with SIGABRT in
*** This bug is a duplicate of bug 932627 ***
https://bugs.launchpad.net/bugs/932627
** This bug is no longer a duplicate of bug 937872
nautilus crashed with SIGABRT in g_thread_abort()
** This bug has been marked a duplicate of bug 937784
nautilus crashed with SIGABRT in
*** This bug is a duplicate of bug 932627 ***
https://bugs.launchpad.net/bugs/932627
** This bug is no longer a duplicate of bug 937784
nautilus crashed with SIGABRT in g_thread_abort()
** This bug has been marked a duplicate of bug 932627
nautilus crashes when opening any folder or
*** This bug is a duplicate of bug 932627 ***
https://bugs.launchpad.net/bugs/932627
** This bug is no longer a duplicate of bug 937784
nautilus crashed with SIGABRT in g_thread_abort()
** This bug has been marked a duplicate of bug 932627
nautilus crashes when opening any folder or
*** This bug is a duplicate of bug 932627 ***
https://bugs.launchpad.net/bugs/932627
** This bug is no longer a duplicate of bug 937784
nautilus crashed with SIGABRT in g_thread_abort()
** This bug has been marked a duplicate of bug 932627
nautilus crashes when opening any folder or
*** This bug is a duplicate of bug 932627 ***
https://bugs.launchpad.net/bugs/932627
** This bug is no longer a duplicate of bug 937784
nautilus crashed with SIGABRT in g_thread_abort()
** This bug has been marked a duplicate of bug 932627
nautilus crashes when opening any folder or
*** This bug is a duplicate of bug 932627 ***
https://bugs.launchpad.net/bugs/932627
** This bug is no longer a duplicate of bug 937784
nautilus crashed with SIGABRT in g_thread_abort()
** This bug has been marked a duplicate of bug 932627
nautilus crashes when opening any folder or
*** This bug is a duplicate of bug 932627 ***
https://bugs.launchpad.net/bugs/932627
** This bug has been marked a duplicate of bug 932627
nautilus crashes when opening any folder or file (nautilus-dropbox and new
glib)
--
You received this bug notification because you are a member of
Snoopyski, are you sure you're referring to the same problem ? (aka this
bug is about the post-removal script failing during upgrade... nothing
else).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello, thanks for your report but I'm afraid you don't provide enough
information about the failure and dpkg is probably not the right package
for this report.
Please look in the logs (of the terminal or in /var/log/apt/) and find
the underlying error and file the bug (or reassign this one moving
The underlying error comes from tar but it looks like some weird kernel
problem because I don't see how open can fail with invalid argument.
** Package changed: dpkg (Ubuntu) = linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New = Incomplete
--
You received this bug notification
nautilus-dropbox_0.7.1_i386.deb is not the Ubuntu package so there's
nothing we can do.
The version 0.7.1-2 is in precise and depends on libnautilus-extension1a
which is in precise.
** Changed in: nautilus-dropbox (Ubuntu)
Status: New = Invalid
--
You received this bug notification
Did it query you for getting root rights?
You should not have permissions issues if you are root and dropbox
update is supposed to ask for root rights (via policy kit).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm marking it as invalid, per your request. But there's still something
weird with the error reported. It doesn't make sense to not have the
right to do unpack the new version. What filesystem are you using on
/var/? Do you have some unusual security policy?
** Changed in: nautilus-dropbox
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that there was an error on your system when
trying to install a particular package. Please execute the following
command, as it will clear your package cache, in a terminal:
sudo apt-get clean
Then try
Sticking the ellipsis to the last word makes it impossible to select the
last word by double clicking on it. It's also more difficult to parse
for scripts. It's not a big deal when the word before the ellipsis is
just an English word, but when it's a dynamic value like in this case, I
believe it's
Brian, can you verify if uninstalling nautilus-dropbox fixes the
problem? And if reinstalling it triggers it again?
If removing nautilus-dropbox doesn't fix the problem, try the same with
nautilus-share.
It would be great if you could provide a gdb backtrace, see
You fixed the problem a bit too quickly... now tell me how can I
reproduce it?
You should have made a backup of all the important files in
/var/lib/dpkg/ (at least status, possibly the content of the updates
directory too, if not empty) when you were encountering the problem.
--
You received
dpkg is giving the proper error message:
dpkg: error processing
/var/cache/apt/archives/oxygen-icon-theme_4%%3a4.8.0-0ubuntu1_all.deb
(--unpack):
unable to create
`/usr/share/icons/oxygen/16x16/actions/meeting-participant-request-response.png.dpkg-new'
(while processing
Unless someone else can reproduce it, or provide instructions to
reproduce it, I fear this bug will rot uselessly. Thus I'm currently
marking it as incomplete.
** Changed in: dpkg (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
** Changed in: dpkg (Ubuntu)
Importance: Undecided = Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/873435
Title:
dpkg should not simplify version numbers in dependencies
To manage
this bug ? I don't have any oneiric chroot to reproduce it
quickly...
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Pre-order a copy of the Debian Administrator's Handbook and help
liberate it: http://debian-handbook.info/liberation/
--
You received this bug notification because you are a member
It seems to me that the proper fix is rather to not try to sort the list
of packages if we don't have any meaningful value in
listfile_phys_offs... thus the attached patch.
** Attachment added: Don't try to sort when nothing to sort on
** Changed in: dpkg (Ubuntu)
Status: New = Triaged
** Changed in: dpkg (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/872734
Title:
dpkg coredumps
A fix has been committed upstream, see commit
916bdba9095bd361cb2bccd6f566ecffdb206193.
http://anonscm.debian.org/gitweb/?p=dpkg/dpkg.git;a=commitdiff;h=916bdba9095bd361cb2bccd6f566ecffdb206193
** Changed in: dpkg (Ubuntu)
Status: Triaged = Fix Committed
--
You received this bug
I guess you're referring to liblcms1 (and not libcms1 which doesn't
exist). That packages indeed has a Provides/Conflicts/Replaces on a
virtual package liblcms.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This patch seems to fix the problem for me. I have integrated it in my
pu/multiarch/full branch so it will land in dpkg upstream with the rest
of the multiarch branch.
** Attachment added: Patch to let dselect ignore conflict via a virtual
package between 2 instances of the same package
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that there was an error on your system when
trying to install a particular package. Please execute the following
command, as it will clear your package cache, in a terminal:
sudo apt-get clean
Then try
I'm afraid this is more a local problem than a real bug in dpkg. Looking
at dmesg, there are many errors generated by your hard disk. What
filesystem are you using?
** Changed in: dpkg (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 873737 ***
https://bugs.launchpad.net/bugs/873737
** This bug has been marked a duplicate of bug 873737
package dia-common 0.97.1-7build1 failed to install/upgrade: ErrorMessage:
package dia-common is already installed and configured
--
You received
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that there was an error on your system when
trying to install a particular package. Please execute the following
command, as it will clear your package cache, in a terminal:
sudo apt-get clean
Then try
The real error is this one. I suggest you get more memory on your
computer and/or add some swap.
Unpacking libjaxp1.3-java (from
.../libjaxp1.3-java_1.3.05-1ubuntu1_all.deb) ...
dpkg: unrecoverable fatal error, aborting:
fork failed: Cannot allocate memory
** Changed in: dpkg (Ubuntu)
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that there was an error on your system when
trying to install a particular package. Please execute the following
command, as it will clear your package cache, in a terminal:
sudo apt-get clean
Then try
*** This bug is a duplicate of bug 874140 ***
https://bugs.launchpad.net/bugs/874140
** This bug has been marked a duplicate of bug 874140
package libreoffice-common 1:3.3.3-1ubuntu2 failed to install/upgrade:
ErrorMessage: package libreoffice-common is already installed and configured
*** This bug is a duplicate of bug 874140 ***
https://bugs.launchpad.net/bugs/874140
** This bug has been marked a duplicate of bug 874140
package libreoffice-common 1:3.3.3-1ubuntu2 failed to install/upgrade:
ErrorMessage: package libreoffice-common is already installed and configured
So you fixed the problem and it's not really a dpkg bug. I doubt this
copy of the libc was put there by an official package. I'm thus closing
this bug.
** Changed in: dpkg (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that there was an error on your system when
trying to install a particular package. Please execute the following
command, as it will clear your package cache, in a terminal:
sudo apt-get clean
Then try
The error is really a hardware problem or something similar, it's not a
bug in dpkg. Input/output error is just an error that comes back from
the hardware.
Unpacking replacement apt-utils ...
dpkg (subprocess): unable to execute old post-removal script
(/var/lib/dpkg/info/apt-utils.postrm):
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that there was an error on your system when
trying to install a particular package. Please execute the following
command, as it will clear your package cache, in a terminal:
sudo apt-get clean
Then try
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that there was an error on your system when
trying to install a particular package. Please execute the following
command, as it will clear your package cache, in a terminal:
sudo apt-get clean
Then try
This error is really weird. dpkg-deb has been called hundreds of times
without problem but here we get a weird linking failure... reassigning
to eglibc in case they have an idea but it's probably a glitch that
can't really be explained.
Unpacking replacement libgtk2.0-cil ...
dpkg-deb:
The real error is this one. This should in theory never happen as dpkg
creates the required directories before trying to unpack files. Did you
remove some files or directories while dpkg was working ?
Unpacking replacement bash ...
Replaced by files in installed package bash-completion ...
The real error is the one below and it doesn't make sense to me. Can you
show us the output of ls -l /mnt ? Do you use some security module
(selinux, smack, etc.) that could refuse the access to /mnt ?
Can you show us the output of mount ? Did you have something mounted
on /mnt during the install
The initial error seems to come from APT which fails to install
openoffice.org-core because it failed to deal with a conflict and thus
dpkg failed...
Selecting previously deselected package openoffice.org-core.
dpkg: regarding .../openoffice.org-core_1%3a3.2.0-7ubuntu4.2_i386.deb
containing
What version of dpkg were you using? The latest version 1.16.0.3ubuntu2
is supposed to fix this.
** Changed in: dpkg (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I see it's in oneiric only currently. I asked Steve Langasek Colin
Watson to prepare an SRU some time ago not sure if it will happen, we'll
see.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/801437
The error message is the following:
Unpacking replacement texlive-font-utils ...
dpkg: error processing /var/cache/apt/archives/texlive-font-
utils_2009-10ubuntu1_all.deb (--unpack):
failed to stat (dereference) existing symlink `/usr/share/doc/texlive-
doc/fonts/fontinst/test/testsc.tex':
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that there was an error on your system when
trying to install a particular package. Please execute the following
command, as it will clear your package cache, in a terminal:
sudo apt-get clean
Then try
*** This bug is a duplicate of bug 809223 ***
https://bugs.launchpad.net/bugs/809223
** This bug has been marked a duplicate of bug 809223
package startupmanager 1.9.13-5 failed to install/upgrade: package
startupmanager is already installed and configured
--
You received this bug
We need the complete upgrade log where you saw this error message,
without it this bug cannot be further investigated.
** Changed in: dpkg (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm afraid the attached log do not give any information about the
problem you encountered. Thus I'm marking this bug as invalid.
** Changed in: dpkg (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
We need a log of the terminal where we see the output of the calls to
dpkg. I think it's /var/log/apt/term.log or something like that (I can't
remember).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you, that was the right file. It looks like apt is the culprit.
It installs both packages entirely and then tries to configure it a
second time for no good reason. It's weird because apt usually does
unpack + configure in 2 steps, and here it looks like it called dpkg
-i directly for those 2
Input/output error means that there's failing hardware involved, it's
not a bug in dpkg, sorry.
** Changed in: dpkg (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The error is in pam:
Preparing to replace libpam-modules 1.1.2-2ubuntu8.3 (using .../libpam-
modules_1.1.3-2ubuntu1_i386.deb) ...
dpkg: error processing /var/cache/apt/archives/libpam-
modules_1.1.3-2ubuntu1_i386.deb (--unpack):
subprocess new pre-installation script returned error exit status
The fact that several packages are affected does not mean that dpkg is
at fault reassigning back to foomatic-filters, one should look
what's common between the 3 postinst.
** Package changed: dpkg (Ubuntu) = foomatic-filters (Ubuntu)
--
You received this bug notification because you are a
This is a file corruption problem and not a bug in dpkg. Do sudo apt-
get clean and retry.
Unpacking vlc-data (from .../vlc-data_1.0.6-1ubuntu1.8_all.deb) ...
dpkg-deb: subprocess paste killed by signal (Broken pipe)
dpkg: error processing
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/846871
Title:
dropbox crashed with KeyError in __getitem__(): 'content-length'
To manage notifications about this bug
This is a network problem between you and the Dropbox server at the time
of the installation, it fails on purpose in that case as dropbox can't
be installed if it can't be downloaded.
** Changed in: nautilus-dropbox (Ubuntu)
Status: New = Invalid
--
You received this bug notification
Please use --debug=3 (or --debug=13) and resend your log. My guess is
that it's not dpkg that gets blocked but one of the maintainer scripts.
In which case this bug should be filed against apt and not dpkg.
** Changed in: dpkg (Ubuntu)
Status: New = Incomplete
--
You received this bug
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/840423
Title:
dpkg assert failure: dpkg: ../../src/filesdb.c:668: findnamenode:
Assertion `(*pointerp)-name[0] ==
Please run sudo dpkg --clear-avail and sudo dpkg -P virtualbox-2.2
virtualbox-3.0. It should fix most of your problems.
** Changed in: dpkg (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
,
--
Raphaël Hertzog ◈ Debian Developer
Pre-order a copy of the Debian Administrator's Handbook and help
liberate it: http://debian-handbook.info/go/ulule-rh/
** Patch added:
0001-dpkg-do-not-try-to-drop-files-from-other-packages-in.patch
https://bugs.launchpad.net/bugs/863675/+attachment
the error messages that appear before this. This
is only a summary of the failures, and we need to see the exact error
message. You might be able to to find a more complete log
in /var/log/apt/.
At this point, it seems unlikely to be a bug in dpkg.
status incomplete
Cheers,
--
Raphaël Hertzog
So I confirm it's not a bug in dpkg, it's the libreoffice package whose
postrm script are failing. But the error message mentions files in /opt/
so it's not an official ubuntu package and there's probably not much
that we can do.
Reassigning to libreoffice anyway. Maybe it's a bug in unopkg.
**
*** This bug is a duplicate of bug 866577 ***
https://bugs.launchpad.net/bugs/866577
** This bug has been marked a duplicate of bug 866577
package mount 2.17.2-9.1ubuntu4 failed to install/upgrade: ErrorMessage:
package mount is already installed and configured
--
You received this bug
*** This bug is a duplicate of bug 866577 ***
https://bugs.launchpad.net/bugs/866577
** This bug has been marked a duplicate of bug 866577
package mount 2.17.2-9.1ubuntu4 failed to install/upgrade: ErrorMessage:
package mount is already installed and configured
--
You received this bug
*** This bug is a duplicate of bug 866577 ***
https://bugs.launchpad.net/bugs/866577
** This bug has been marked a duplicate of bug 866577
package mount 2.17.2-9.1ubuntu4 failed to install/upgrade: ErrorMessage:
package mount is already installed and configured
--
You received this bug
The initial problem is this one:
Setting up libpam0g (1.1.3-2ubuntu1) ...
Checking for services that may need to be restarted...Checking init
scripts...
WARNING: init script for samba not found.
dpkg: error processing libpam0g (--configure):
subprocess installed post-installation script
Ok, reassigning to sshfs then because I don't see why root should not
have the right to stat a file even if remote mounted
** Package changed: dpkg (Ubuntu) = sshfs-fuse (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The log says:
Preparing to replace libc6 2.13-0ubuntu13 (using
.../libc6_2.13-20ubuntu5_i386.deb) ...
So you upgraded from 2.13-0ubuntu13 to 2.13-20ubuntu5. There's no way
that libc-2.12.1.so was a packaged file... at least not coming from the
libc6 package in version 2.13!
In any case, it's
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that there was an error on your system when
trying to install a particular package. Please execute the following
command, as it will clear your package cache, in a terminal:
sudo apt-get clean
Then try
1 - 100 of 918 matches
Mail list logo
