[gutsy][hardy] adept progress report incorrectly says "Removing libc6"

Bug #152396 reported by Guillaume Martres on 2007-10-13
4
Affects Status Importance Assigned to Milestone
adept (Ubuntu)
Undecided
Unassigned
dpkg (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: adept

Today I upgraded my system with adept_notifier and at some point in the upgrade process I saw "suppression de libc6"(which means "deleting libc6" in french), I panicked and clicked on "View details", and I saw that the libc6 was not actually deleted it was just the standard message: "Processing triggers for libc6..." which was wrongly parsed by adept.

Guillaume Martres (smarter) wrote :

Screenshot of the problem.

Guillaume Martres (smarter) wrote :

Alright, I found where the problem come from, "dpkg --status-fd" wrongly interprets "Processing triggers for libc6 ..." :
LANG=C sudo dpkg --status-fd 1 -r kdelibs5
status: kdelibs5: installed
(Reading database ... 158344 files and directories currently installed.)
Removing kdelibs5 ...
processing: remove: kdelibs5
status: kdelibs5: half-configured
status: kdelibs5: half-installed
status: libc6: triggers-pending
status: kdelibs5: config-files
status: kdelibs5: config-files
Processing triggers for libc6 ...
processing: trigproc: libc6
status: libc6: half-configured
ldconfig deferred processing now taking place
status: libc6: installed

And if adept saw that a package is half-configured or installed and if adept is currently removing a package, it will display "Removing $package..."

Brezhonneg (fricompte) wrote :

Problem confirmed here on Kubuntu 7.10 AMD64.

Moreover, this buggy message generally precedes an adept crash, but I am not entirely sure if this is related...

kko (kko) wrote :

I'm not sure if it is an actual bug in dpkg (i.e. whether a separate task for dpkg is needed), but at least adept interprets it wrong. The message is troubling (where it wouldn't need to be), especially if you know that adept has a tendency to do disastrous things without warning - á la bug 55549.)

I hope you don't mind if I edit the title a bit.

Changed in adept:
status: New → Confirmed
Jonathan Thomas (echidnaman) wrote :

I think it was just Adept, as Adept 3.0 doesn't have this issue.

Changed in adept:
status: Confirmed → Fix Released
Changed in dpkg:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers