** Changed in: dpkg (Debian)
Status: Unknown = 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/262451
Title:
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry =
Hi Sergio
you are very right, When we are working on Lucid it does not make any sense to
keep working on old issues.
regards
Rajinder
--
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
https://bugs.launchpad.net/bugs/262451
You received this bug notification
Thank you for reporting this bug to Ubuntu. Intrepid Ibex 8.10 reached EOL on
30 March 2010.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please feel free to report any other bugs you may find.
Thank you.
** Changed in: dpkg (Ubuntu
I realized I had made a mistake, Intrepid Ibex 8.10 will reach EOL on
30 APRIL 2010.
Sorry for this.
Anyway, I think that one month doesn't make any difference now.
--
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
https://bugs.launchpad.net/bugs/262451
You
** Changed in: dpkg (Ubuntu)
Assignee: (unassigned) = piyu28 (hereiam10)
--
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
https://bugs.launchpad.net/bugs/262451
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Fixed in ubuntu since jaunty
dpkg (1.14.21) unstable; urgency=low
[...]
[ Guillem Jover ]
* When loading the status file fix up any inconsistent package in state
triggers-awaited w/o the corresponding package with pending triggers.
Closes: #487637, #486843, #489068
** Also affects:
Removed invalid bug tasks
** Changed in: pkgsel (Debian)
Status: New = Invalid
** Changed in: busybox
Status: New = Invalid
--
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
https://bugs.launchpad.net/bugs/262451
You received this bug
** Also affects: busybox
Importance: Undecided
Status: New
** Also affects: pkgsel (Debian)
Importance: Undecided
Status: New
--
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
https://bugs.launchpad.net/bugs/262451
You received this bug
** Branch linked: lp:ubuntu/karmic/ufw
--
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
https://bugs.launchpad.net/bugs/262451
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Changed in: dpkg (Ubuntu Intrepid)
Assignee: Ahmed Faissl (ahmedfaissl) = (unassigned)
--
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
https://bugs.launchpad.net/bugs/262451
You received this bug notification because you are a member of Ubuntu
Bugs,
I had lots of package updates reported as pending based on
$ sudo dpkg --audit
but there is no need to purge all of them (at least it wasn't for me). The
work-around was simply to reinstall gxine, as suggested e.g. in
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/262451/comments/40.
The
This https://edge.launchpad.net/ubuntu/+source/dpkg/1.14.20ubuntu6.1
version of dpkg in intrepid-updates should fix the problem with the
inconsistent triggers-awaited database that prevents dpkg --configure
-a from working correctly.
--
dpkg: ../../src/packages.c:221: process_queue: Assertion
** Changed in: ufw (Ubuntu Intrepid)
Status: Confirmed = Fix Released
** Changed in: ufw (Ubuntu)
Status: Confirmed = Fix Released
--
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
https://bugs.launchpad.net/bugs/262451
You received this bug
I upgraded my system from Intrepid to the new Jaunty. the system hanged
as usual during restarting HAL, so I expected being asked to enter the
usual 'sudo dpkg --configure -a' which supposed to fail and enter the
dilemma again.. but when I entered it I surprised that everything is
fixed without
for me, removing and reinstalling xmms2 and related modules solved the
error, seems it updates some gxine stuff when I do.
--
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
https://bugs.launchpad.net/bugs/262451
You received this bug notification because you
Removing gxine worked for me too.
--
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
https://bugs.launchpad.net/bugs/262451
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Krzysztof Debski's fix worked for me.
Thanks!
--
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
https://bugs.launchpad.net/bugs/262451
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Removed gxine, but that did not help me - I think my problems were with
cups and removing/re-installing that fixed it... but now gotta work out
how it was configured again - doh
--
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
Amsterdam / Berlin / Bern
/ Rome / Stockholm / Vienna
Subject: [Bug 262451] Re: dpkg: ../../src/packages.c:221: process_queue:
Assertion `dependtry = 4' failed.
Removed gxine, but that did not help me - I think my problems were with
cups and removing/re-installing that fixed it... but now
Same problem here.
codedpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed./code
$ sudo dpkg --remove gxine
$ sudo apt-get install gxine
... fixed the problem.
--
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
I fixed it this way:
Apt-get update reported errors for round about 10 packages, including cups and
fomatic. I purged this packages and let apt purge all stuff it wanted to remove
additionally.
Then I installed these packages anew and all was OK.
--
dpkg: ../../src/packages.c:221:
I am having a similar error in intrepid. During a large update the
update manager reported that not all packages installed correctly and
made this suggestion:
E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to
correct the problem.
After attempting the command in the terminal
fix:
sudo dpkg --remove gxineplugin
sudo dpkg --remove gxine
sudo dpkg --configure -a
sudo apt-get install gxine
** Changed in: dpkg (Ubuntu Intrepid)
Status: Fix Committed = Confirmed
** Changed in: dpkg (Ubuntu)
Status: Fix Released = Confirmed
** Changed in: ufw (Ubuntu)
Here a link to the solution.
http://techxplorer.com/2006/05/21/resolving-an-odd-dpkg-error-in-ubuntu/
--
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
https://bugs.launchpad.net/bugs/262451
You received this bug notification because you are a member of Ubuntu
I think I had the same, but mine affects cups, which i can't remove
because tons of other stuff depend on it.
--
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
https://bugs.launchpad.net/bugs/262451
You received this bug notification because you are a member of
I had the same problem with dpkg --configure -a
removing gxine and after configuring the rest reinstalling it helped for
me as well.
Log attached.
** Attachment added: log
http://launchpadlibrarian.net/21850491/log
--
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
I had the same with gxine and cups, try dpkg -r --force-depends cups to
force removal of cups and then try apt-get -f install which will install
it again but without problem Worked for me
--
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
Likewise happened to me today. Likewise removing gxine fixed the
problem.
Re-installing gxine afterwards went fine.
Weird.
--
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
https://bugs.launchpad.net/bugs/262451
You received this bug notification because you
remove --purge apt..?! you got to be kidding..!
I mean, I would remove apt if someone just told me how to get it back..!
--
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
https://bugs.launchpad.net/bugs/262451
You received this bug notification because you are
1. Updated repositories today with update-manager
2. Upgraded packages with the same desktop tool.
3. Update manager warned that not all the packages were well-installed
4. When I run sudo aptitude search '~i'gstreamer in a terminal, it returns me
the message:
E: dpkg was interrupted, you must
I don't have gzine installed at all..!!
But I Came out with a good handsom way..
from your system menu (or settings in kde) launch the Hardware Testing wizard.
and do all the testing, don't skip anything. and preferably submit it to
launchpad. (i did) :)
then do your usual 'sudo dpkg --configure
** Changed in: dpkg (Ubuntu Intrepid)
Assignee: (unassigned) = Ahmed Faissl (ahmedfaissl)
Status: Triaged = Fix Released
--
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
https://bugs.launchpad.net/bugs/262451
You received this bug notification
** Changed in: dpkg (Ubuntu Intrepid)
Status: Fix Released = Fix Committed
--
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
https://bugs.launchpad.net/bugs/262451
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I have this too, after trying to update my (32bit x86) intrepid system:
r...@oxygene:~# dpkg --configure -a
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
Aborted
And some error before where I dist-upgrade'd the system (I tried to
handle this with dpkg
Confirmed for my case too: removing gxine allowed me to run dpkg
--configure -a without this assertion. Then I reinstalled gxine.
--
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
https://bugs.launchpad.net/bugs/262451
You received this bug notification
Same happened here with today updates. Uninstalling gxine fixed the
issue.
--
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
https://bugs.launchpad.net/bugs/262451
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
This happend to me today while upgrading my intrepid to latest packages.
dpkg always crashed while --configure -a
A dpkg --audit showed me
The following packages are only half configured, probably due to problems
configuring them the first time. The configuration should be retried using
dpkg
Those people were probably winding you up. apt is an essential package,
and removing it will uninstall a lot of other stuff too. And it will be
difficult to reinstall everything
--
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
Just a quick note-- some people have also said
sudo apt-get remove --purge apt
Seems to help in some cases --
--
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
https://bugs.launchpad.net/bugs/262451
You received this bug notification because you are a member
I got the same issue. It's first manifestation was when something has
complained about a symlink in /usr during an update, but i wasn't paying
attention and lost the logs. After reading and trying several things, i
got to removing cups, and here's what i get:
~$ sudo dpkg --remove cups
(Reading
Hi, I have the same problem here. I upgraded my system with the usual
apt-get update and apt-get upgrade. Now I am getting the same error. My
system is unusable. How can I fix it?
--
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
As suggested by someone in this or a related bug, I uninstalled cupsys
and the problem went away.
On Sun, 2009-01-11 at 00:47 +, hkais wrote:
Hi, I have the same problem here. I upgraded my system with the usual
apt-get update and apt-get upgrade. Now I am getting the same error. My
It appeared on my machine today.
--
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
https://bugs.launchpad.net/bugs/262451
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
It may be that we should be backporting the Debian fix to Intrepid to
fix these upgrade corner cases. The fix in Jaunty should be sufficient
there.
** Changed in: dpkg (Ubuntu Intrepid)
Status: Won't Fix = Triaged
--
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry =
** Changed in: dpkg (Ubuntu)
Status: Confirmed = Fix Released
--
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
https://bugs.launchpad.net/bugs/262451
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I've just installed my AMD64 workstation with Ibex 8.10. Everything
is more or less fine except for dpkg and apt-get. After installing
and running the upgrade I get the following error...
166 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
7 not fully installed or removed.
Need
Upgraded to Intrepid, and after trying to reconfigure packages dpkg
won't do nothing anymore:
~ # dpkg --configure -a
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
zsh: abort dpkg --configure -a
Any way to handle this?
--
dpkg:
I've got it with waiting. I'd tried much things - nothing helps. then i
would track the bug here - and he wasn't there any more.
list with grep (i've forgotton how) packages with errors and try to
delete these.
--
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
I've removed cupsys and cups, and then things went back to normal.
On Sun, Nov 9, 2008 at 12:05 AM, Raphael Michel (ger)
[EMAIL PROTECTED] wrote:
I've got it with waiting. I'd tried much things - nothing helps. then i
would track the bug here - and he wasn't there any more.
list with grep
Exactly the same error like Bogdan Butnaru' on my computer.
Is it wise to wait for an fix or should i try to reinstall dpkg /
Ubuntu?
Launchpad Lanitor: How can i install a package withoud dpkg?
--
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
Oh, and by the way, how can I get rid of this? dpkg and aptitude halt on
every execution due to the error. Is there a known way of cleaning
things out, so that I can resume updating my system?
--
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
In my case it's not even reporting on a certain package failing:
$ sudo dpkg --configure -a
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
Aborted (core dumped)
--
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
I'm not sure if this is interesting, but in my case this assertion
failed after I forcefully stopped an ongoing update.
(I started update-manager and told it to update, there were a few more
than a hundred packages to update. However on this machine updates slow
down everything, and I had
@Colin, there are similar dpkg issues with cups in bug 290956 and
python-sip4 in bug 279709 .
--
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
https://bugs.launchpad.net/bugs/262451
You received this bug notification because you are a member of Ubuntu
Bugs,
Thanks, Jamie. This isn't release-critical in dpkg for intrepid any
more, although I'd still like to figure out why this broke in the first
place; on reconsideration I'm not really sure that the fix in Debian to
fix up the database on reload would have helped here, and the problem is
that the
** Also affects: ufw (Ubuntu)
Importance: Undecided
Status: New
--
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
https://bugs.launchpad.net/bugs/262451
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
In fact, while it's clearly a dpkg bug that it's tripping an assertion,
the proximate cause is ufw's trigger failing as follows:
Sep 3 08:16:40 in-target: Processing triggers for ufw ...
Sep 3 08:16:51 kernel: [17312.770421] ip_tables: (C) 2000-2006 Netfilter Core
Team
Sep 3 08:16:52
** Changed in: ufw (Ubuntu Intrepid)
Assignee: (unassigned) = Jamie Strandboge (jdstrand)
Status: New = Triaged
--
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
https://bugs.launchpad.net/bugs/262451
You received this bug notification because you
Fix committed to bzr. Will upload later today.
** Changed in: ufw (Ubuntu Intrepid)
Status: Triaged = Fix Committed
--
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
https://bugs.launchpad.net/bugs/262451
You received this bug notification because you
This bug was fixed in the package ufw - 0.22
---
ufw (0.22) intrepid; urgency=low
* fix confusing output of 'app update' command (LP: #261932)
* only reload during 'app update' if the profile name is used in
the current ruleset (LP: #261323)
* don't reload user rules if not
I have at least managed to reproduce this. Now the trick will be
reducing it to a non-enormous test case ...
--
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
https://bugs.launchpad.net/bugs/262451
You received this bug notification because you are a member of
Hmm, well, dpkg 1.14.21 is supposed to fix http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=486843 which at least has the same symptoms. I'm a
bit perturbed because this seems to be cleaning up after a bogus state
that dpkg shouldn't have managed to get itself into short of ENOSPC,
which isn't
** Changed in: dpkg (Ubuntu Intrepid)
Importance: Undecided = High
Status: New = Confirmed
--
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
https://bugs.launchpad.net/bugs/262451
You received this bug notification because you are a member of Ubuntu
It's back.
logs:
http://dev.personnelware.com/carl/temp/Sep03/a/qemu/
--
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
https://bugs.launchpad.net/bugs/262451
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: dpkg (Ubuntu)
Status: New = Invalid
--
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
https://bugs.launchpad.net/bugs/262451
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I'm not sure why you marked this as Invalid in dpkg at the same time as
reassigning the bug? Undoing that.
** Changed in: dpkg (Ubuntu)
Status: Invalid = New
--
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
https://bugs.launchpad.net/bugs/262451
You
Invalid because it was no longer erroring
I will swear I filled in Comment on this change (optional) with
something like:
seems fixed now. This is no longer happening:
in-target: dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry
= 4' failed.
Opening a new bug for
** Attachment added: syslog
http://launchpadlibrarian.net/17150135/syslog
--
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
https://bugs.launchpad.net/bugs/262451
You received this bug notification because you are a member of Ubuntu
Bugs, which is
more lines worth looking at:
Aug 28 20:18:08 in-target: Use of uninitialized value $x in scalar assignment
at /usr/share/perl/5.10/utf8_heavy.pl line 242, GEN0 line 1.
Aug 28 20:18:08 in-target: Use of uninitialized value $x in pattern match (m//)
at /usr/share/perl/5.10/utf8_heavy.pl line 243,
(07:06:14 PM) slangasek: CarlFK: the assertion is in dpkg, so there's a dpkg bug
sladen slangasek
(07:06:32 PM) slangasek: CarlFK: if fixing that bug doesn't fix the overall
problem, then iterate ;)
** Changed in: dpkg (Ubuntu)
Sourcepackagename: None = dpkg
--
dpkg: ../../src/packages.c:221:
70 matches
Mail list logo
