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
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 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 (Ubunt
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.
https://bugs.la
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.
https://bugs.launchpad.net/bugs/9375
*** 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 Ub
*** 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 file
*** 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 file
*** 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 file
*** 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 file
*** 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 file
*** 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 g_thread_abort(
*** 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 g_thread_abort(
*** 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 file
*** 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 g_thread_abort
*** 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 file
*** 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 g_thread_abort(
*** 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 file
*** 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 t
The dpkg log shows an interesting message for you:
Preparing to replace latex-xft-fonts 0.1-8 (using
.../latex-xft-fonts_1.6.7-1~lucid1_all.deb) ...
E: /var/lib/defoma/locked exists.
E: Another defoma process seems running, or you aren't root.
E: If you are root and defoma process isn't running un
Chris, thanks for tracking it down. Do you feel like reporting it
upstream? I don't see the bug yet on
https://bugzilla.gnome.org/buglist.cgi?product=glib&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&version=2.31.x
I have added glib to the list of affected packages
** Also affects: glib2.0 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/932627
Title:
nautilus crashes when opening any folder or file
To manage
Please attach /var/log/apt/term.log. I want to see a former failure
recorded in your log file.
In any case, the bug is in dropbox.com's package (version 0.7.1) not in
the Ubuntu package (version 0.7.1-2). There's not much that I can do.
--
You received this bug notification because you are a mem
http://raphaelhertzog.com/2011/09/13/understand-dpkg-and-dont-get-stuck-
with-a-maintainer-script-failure/ might help you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/937390
Title:
package nautilu
The log shows that it's the dropbox package from dropbox's website that is
failing:
Start-Date: 2012-02-19 17:55:59
Commandline: synaptic
Purge: nautilus-dropbox:amd64 (0.7.1)
And that the upgrade from dropbox's version to the Ubuntu version failed a bit
earlier:
Start-Date: 2012-02-19 17:55:0
*** 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
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Apparently this bug affects people who have enabled PPA with
developement versions of glib. Anyone that is affected, please post the
output of this command: dpkg-query -W libglib2.0-0
It's not yet clear whether the bug is in glib or in nautilus-dropbox.
--
You received this bug notification beca
Apparently this bug affects people who have enabled PPA with
developement versions of glib. Anyone that is affected, please post the
output of this command: dpkg-query -W libglib2.0-0
It's not yet clear whether the bug is in glib or in nautilus-dropbox.
--
You received this bug notification beca
Thank you for the report. I committed a different fix in the upstream
git repository (changing debug() to print all parameters).
I don't think this warrants an immediate upload to Ubuntu, it will be
fixed the next time the package is synced with Debian.
** Changed in: dpkg (Ubuntu)
Status:
n you attach the /var/lib/dpkg/status that
triggers 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/
--
** 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 notific
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
B
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
`./usr/share/icons/oxy
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 thi
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
https://wiki.ubuntu.com/Backtrace
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
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.
https://bu
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 beca
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
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
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:
nautilus-
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 v
This is mostly fixed in quilt 0.50 upstream. The remaining fix (for
quilt push) will follow shortly (and is properly tracked on the debian
side).
** Changed in: quilt (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Thanks for your report but the attached log file doesn't show the error
and thus there's nothing we can do with this report. Somehow dkms failed
to install, but we don't know why. It might just be a corrupted .deb
file...
** Changed in: dpkg (Ubuntu)
Status: New => Invalid
--
You received
Ok, thanks for the supplementary input. There's nothing we can do on the
dpkg side since we're now properly rejecting the package... I'm
reassigning it to update-manager since that's where special upgrade
checks are put. But it will be difficult to detect in the general case.
But it might be possib
Public bug reported:
Please sync wordpress 3.3.1+dfsg-1 (universe) from Debian testing (main)
Changelog entries since current precise version 3.3+dfsg-1:
wordpress (3.3.1+dfsg-1) unstable; urgency=low
* New upstream security release. Fixes CVE-2012-0287.
-- Raphaël Hertzog Wed, 04 Jan
y does not
begin with a field.
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 of Ubuntu
Bugs, which is subscribed to
*** This bug is a duplicate of bug 545790 ***
https://bugs.launchpad.net/bugs/545790
** This bug has been marked a duplicate of bug 545790
package PACKAGE failed to install/upgrade: error writing to '': Success
--
You received this bug notification because you are a member of Ubuntu
Bugs,
> thanks for having my name misspelled intentionally.
Dude, sorry, it was not intentional.
Anyway, I'm now marking the bug as invalid because those warnings are to
be expected during early setup. You can file a bug against debootstrap
if you want because the 3 warnings about missing
description/m
ng up a new debian/ubuntu installation with debootstrap or
similar (which I suspect is your case here).
There's just no way to satisfy the pre-dependencies during an initial
installation that doesn't have all the essential packages already
unpacked...
If that's effectively your cas
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
And exactly what is the problem that you reported ? Because I see lots
of warning but nothing like a bug or an error here.
** 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.
h
Please use #900566 to track the problem on the qwt side. This bug is now
for the dpkg side of the problem.
--
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" vers
It means someone changed the status without justification. This is a
dpkg bug but a rather minor one.
dpkg simplifies some versions like "0:1.0" into "1.0" or "1.0-" into
"1.0" but it should not do that to avoid the kind of problem described
here.
** Changed in: dpkg (Ubuntu)
Status: Fix C
#873435 is the corresponding bug for dpkg.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/900566
Title:
libqwt-dev should use "6.0.0" instead of "6.0.0-" in Replaces field
To manage notifications ab
The problem is that "Replaces: libqwt5-qt4-dev (<< 6.0.0-)" is rewritten
into "Replaces: libqwt5-qt4-dev (<< 6.0.0)" by dpkg in the status file
and apt detects the difference... and thinks the package has changed.
Please drop that useless dash in the version.
** This bug is no longer a duplicate
The fix has been committed upstream in commit
c07f7fea4206bc002578b2032871c9f63457bde8.
** Changed in: dpkg (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
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
If you don't give any context about when and how dpkg has generated this
message, there's nothing we can do about it. And it's unlikely to be a
bug in dpkg... if anything it would be a bug in the tool that calls dpkg
and that instructs him to ignore some problems.
** Changed in: dpkg (Ubuntu)
*** This bug is a duplicate of bug 900904 ***
https://bugs.launchpad.net/bugs/900904
** This bug has been marked a duplicate of bug 900904
warnings in bootstrap.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
A warning is not an error, there are situations where they can
rightfully be emitted. I'm not sure what bootstrap.log refers to... but
if you want to get rid of those warnings you should file a bug against
the tool that generates this log file. Is it debootstrap maybe ?
** Changed in: dpkg (Ubuntu
update ?
At least I see no direct reason why a running dropbox would be affected by
an ongoing upgrade.
> Download got stuck at 52%, so I killed the process, which caused the
> update to fail.
This is fixed with newer nautilus-dropbox (>= 0.7.0-2).
status fixreleased
Cheers,
--
Rap
This issue has been fixed with version 0.7.0-1 of the package and newer
(available in precise).
** 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.l
tered. Alas you did
not seem interested in pursuing this.
Cheers,
Raphaël Hertzog.
** Changed in: nautilus-dropbox (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
The underlying error is this one. It's not dpkg's fault at least. Maybe
you have some security policy that forbids this operation, or maybe it's
mounted read-only or something similar.
Unpacking replacement memtest86+ ...
dpkg: error processing
/var/cache/apt/archives/memtest86+_4.00-2ubuntu3_i38
This bug is related to http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=651065 and http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=651143
The real underlying problem is likely an intermediary proxy that refuses
the download.
** Bug watch added: Debian Bug tracker #651065
http://bugs.debian.
This bug is related to http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=651065 and http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=651143
** Changed in: nautilus-dropbox (Ubuntu)
Status: New => Confirmed
** Bug watch added: Debian Bug tracker #651065
http://bugs.debian.org/cgi-bin/bu
** 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/905223
Title:
dropbox crashed with GpgmeError in verify_signature(): (7, 58, u'No
data')
To manage notifications abo
This is not a bug in dpkg, it just tells that the file can't be found.
It might be a bug in apt or something else that removed the file from
where it was expected.
** Package changed: dpkg (Ubuntu) => apt (Ubuntu)
** Changed in: apt (Ubuntu)
Status: New => Incomplete
--
You received this
The underlying problem is in fglrx:
Preparing to replace fglrx 2:8.861-0ubuntu1 (using
.../fglrx_2%3a8.881-0ubuntu4.1_i386.deb) ...
Removing all DKMS Modules
Done.
One or more files have been altered since installation.
Uninstall will not be completed. See /etc/ati/fglrx-uninstall.log for
deta
Input/Output error is a sign of failing hardware more than a sign of a
bug. Sorry. I'm closing the bug as invalid. Please check your hard disk
and your memory.
Preparing to replace libsane-hpaio 3.10.6-1ubuntu10.2 (using
.../libsane-hpaio_3.11.1-2ubuntu2_i386.deb) ...
Unpacking replacement libsan
*** This bug is a duplicate of bug 907645 ***
https://bugs.launchpad.net/bugs/907645
** This bug has been marked a duplicate of bug 907645
package libsane-hpaio 3.10.6-1ubuntu10.2 failed to install/upgrade:
ErrorMessage: package libsane-hpaio is already installed and configured
--
You re
*** This bug is a duplicate of bug 907645 ***
https://bugs.launchpad.net/bugs/907645
** This bug has been marked a duplicate of bug 907645
package libsane-hpaio 3.10.6-1ubuntu10.2 failed to install/upgrade:
ErrorMessage: package libsane-hpaio is already installed and configured
--
You re
dpkg is not responsible of this progress bar, it's debconf.
** Package changed: dpkg (Ubuntu) => debconf (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/906682
Title:
Extracting templates fr
logic to restrict the
test to multi-arch same packages.
It seems to work now.
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/
** Attachment added: "patch"
https://
Here's the proposed patch for dpkg. Not tested but should be ok.
** Attachment added: "Dpkg patch"
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/902603/+attachment/2634152/+files/patch
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed t
Please provide the log of what you see on the terminal, you should have
a copy in /var/log/apt/term.log.
** Package changed: dpkg (Ubuntu) => grub2 (Ubuntu)
** Changed in: grub2 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bu
. The kernel problem is not new (cf the old
failures against dpkg that I reassigned), it's just that it triggered more
easily under some circumstances in Precise.
It would be interesting to have the opinion of the kernel team on whether
it's easy to backport the fix on older kernels.
Cheer
I don't really understand what's happening here. The installation fails
because libreoffice-core is not installed... but it looks like it is
since we see it's being upgraded. But the upgrade shows warnings that
are not generated by dpkg but that are still attributed to dpkg.
Preparing to replace l
Input/output error is a sign of defective hardware usually and not a
bug.
Unpacking replacement freedroidrpg-data ...
dpkg-deb (subprocess): failed to read on buffer copy for failed to write
to pipe in copy: Input/output error
dpkg-deb: error: subprocess paste returned error exit status 2
dpkg:
This shows that the Dropbox-provided package is correctly installed. I
have no idea why gdebi would not work in this situation. Reaffecting the
bug against this package.
** Package changed: nautilus-dropbox (Ubuntu) => gdebi (Ubuntu)
--
You received this bug notification because you are a member
>
> I hope, i can define the problem is now correct.
Please give me the output of "dpkg -s nautilus-dropbox". This command is
to be typed on a terminal.
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Pre-order a copy of the Debian Administrator's Handbook and help
liberate it
the Dropbox icon
> appeared and synchronized my folders!
The package provided by dropbox install binaries in your /home and if you
installed an autostart script that point to those binaries (which can be
done with "dropbox autostart") then the it might run even if the package
is not correc
And ?
Oneiric is released, it won't get a new version. If you want to prepare
a backport, feel free to go ahead but the latest versions of the package
do not bring much enhancements and it's only a wrapper, you always get
the latest version of dropbox itself from Dropbox anyway.
Precise will auto
The attached log files do not show any error. I'm afraid there's nothing
we can do if you don't show exactly what failed and how it failed.
The error message in the title suggests that dkms failed to unpack (and
then apt wrongfully tried to configure it) but we don't know why.
** Package changed:
The kernel unexpectedly returning EINVAL for I/O is not something new
unfortunately, I saw it in a few dpkg related bug reports too:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-backport-natty/+bug/827942
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/773850
--
You received this b
On Fri, 02 Dec 2011, Jason U wrote:
> Thanks for your help. Were do I enter this information?
In a terminal.
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
It looks like /var/lib/dpkg/available is corrupted, you can try to run
"sudo dpkg --clear-avail" to get rid of your problem.
** 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.
ht
Please attach /var/lib/dpkg/available. It looks like corrupted. You can
then fix your problem with "sudo dpkg --clear-avail".
** 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
Jared, please attach a tarball with /var/lib/dpkg/status and the content
of /var/lib/dpkg/triggers/. And what dpkg invocation is failing exactly
?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/798793
*** This bug is a duplicate of bug 573696 ***
https://bugs.launchpad.net/bugs/573696
** This bug has been marked a duplicate of bug 573696
dpkg: ../../src/archives.c:763: tarobject: Assertion `r == stab.st_size'
failed. Aborted
--
You received this bug notification because you are a memb
You can reinstate the backup file like you did. But doing this
automatically would not be good. It would hide a severe problem. And
instead of looking at changing your memory or your disk, you'd continue
to not notice that your system is starting to not work properly.
--
You received this bug not
Input/output error is a sign of failing hardware, not of a bug in dpkg.
Unpacking replacement kbd ...
dpkg-deb (subprocess): failed to read on buffer copy for failed to write
to pipe in copy: Input/output error
dpkg-deb: error: subprocess paste returned error exit status 2
dpkg: error processin
*** This bug is a duplicate of bug 897264 ***
https://bugs.launchpad.net/bugs/897264
** This bug has been marked a duplicate of bug 897264
package bash-completion 1:1.3-1ubuntu3 failed to install/upgrade:
ErrorMessage: package bash-completion is already installed and configured
--
You re
*** This bug is a duplicate of bug 897264 ***
https://bugs.launchpad.net/bugs/897264
** This bug has been marked a duplicate of bug 897264
package bash-completion 1:1.3-1ubuntu3 failed to install/upgrade:
ErrorMessage: package bash-completion is already installed and configured
--
You re
(Eliah I get the mail by a group subscription, no need to subscribe me)
It's a wrong good idea IMO. A computer where you can't trust data stored
in your filesystem is not very useful. That said I agree that dpkg could
give more clue as to what can be done to recover. But then it's merely a
wishlis
** Changed in: dpkg (Ubuntu)
Importance: Undecided => Medium
** Changed in: dpkg (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/896817
Title:
[precise] dpkg
This is really weird, apt removes a package (openoffice.org-common) and
then tries to install another package that pre-depends on the removed
package. I don't know how apt can expect this to work...
** Package changed: dpkg (Ubuntu) => apt (Ubuntu)
--
You received this bug notification because y
dpkg does not produce invalid .list files. Data gets corrupted by bad
hardware (disk/memory/filesystem bugs) and after that dpkg complains
about the corrupted data.
All those .list files are important. If one gets corrupted, you can
remove it but you should immediately reinstall the corresponding
201 - 300 of 914 matches
Mail list logo
