Listaller Manager hangs at:"detecting package..."

Bug #561012 reported by Christian
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Listaller
Fix Released
High
Matthias Klumpp
0.4b
Fix Released
High
Matthias Klumpp
packagekit (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

If I try to remove package using Listaller Manager(Sumode), the application hangs and has to be terminated.

Revision history for this message
Christian (christian-bley2) wrote :
Revision history for this message
Christian (christian-bley2) wrote :
Revision history for this message
Matthias Klumpp (ximion) wrote :

Need to investigate...

Changed in listaller:
assignee: nobody → Matthias Klumpp (ximion)
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Matthias Klumpp (ximion) wrote :

Could you please attach the output of the "pkmon" command?

(Install package "packagekit", then open two Terminals. Execute "pkmon" in the first, in the second run Listaller Manager. Execute the desired removal-action and wait some time until Listaller does not react anymore. Attach the output which "pkmon" displayed to this bugreport)

Changed in listaller:
status: Triaged → Incomplete
Revision history for this message
Matthias Klumpp (ximion) wrote :

Set to alpha-1 milestone.

Changed in listaller:
milestone: none → 0.4-alpha1
Revision history for this message
Christian (christian-bley2) wrote :

here's the output of pkmon:

christian@christian-laptop:~$ pkmon
Transactions:
 [none]

thats all

Revision history for this message
Matthias Klumpp (ximion) wrote :

Which application did you try to remove?
Which PackageKit-Version do you have? This seems to be an error in PackageKit or the PackageKit-Bindings.
But it's really strange that Listaller does not display the PackageKit error message or just notifies about a failed action.
Do you use the GTK+-Version of listallmgr? Have you tried the same with the Qt4 version?

Revision history for this message
Matthias Klumpp (ximion) wrote :

Okay, this only appears in the GTK2 version of Listaller cause of a call to g_main_loop_run() inside of the library.
I'll try to find a better way to handle this, but it might take some time.
(Set priority to "high", cause it breaks every Listaller module which is compiled for GTK+)

Changed in listaller:
importance: Medium → High
status: Incomplete → In Progress
Revision history for this message
Matthias Klumpp (ximion) wrote :

Hmm, the problem seems to be very deep inside the component set, the mainloop is not the reason.
I'll updated this report if I have any news.

Revision history for this message
Matthias Klumpp (ximion) wrote :

Damn! This bug needs major API/ABI changes on libInstaller to be fixed. Cause this bug has to be fixed for 0.4b, the new version cannot be released on the date we preferred.
This task may delay a release for at least three weeks.

Matthias Klumpp (ximion)
tags: added: distribution-specific packagekit
Revision history for this message
Matthias Klumpp (ximion) wrote :

This is a bug in the PackageKit version Ubuntu uses.
There was a Listaller bug too which was a consequence of the PackageKit bug and has been fixed in the last commit. The API changes have been applied on every Listaller module.
The problem with PackageKit remains.
I executed the same commands on a brand-new Fedora 12 machine and everything worked just fine.
Packagekitd gived the following verbose output:
--------------
TI:19:50:14 FI:pk-transaction.c FN:pk_transaction_set_hints,4699

 - SetHints method called: locale=de_DE.UTF-8, background=false,
interactive=true
TI:19:50:14 FI:pk-transaction.c FN:pk_transaction_set_hint,4678

 - unknown option: interactive with value true

TI:19:50:16 FI:pk-transaction-list.c
FN:pk_transaction_list_is_consistent,734

 - checking consistency as length 1

TI:19:50:16 FI:pk-transaction-list.c
FN:pk_transaction_list_print,702

 - State:
0 unknown /183_dbcdddea_data running[0] committed[0] finished[0]
background[0]

TI:19:50:16 FI:pk-transaction-list.c
FN:pk_transaction_list_is_consistent,763

 - 1 have an unknown role (GetTid then nothing?)

TI:19:50:16 FI:pk-transaction-list.c
FN:pk_transaction_list_is_consistent,767

 - 1 have not been committed and may be pending auth

TI:19:50:16 FI:pk-engine.c FN:pk_engine_get_seconds_idle,750

 - engine idle zero as 1 transactions in progress

TI:19:50:16 FI:pk-main.c FN:pk_main_timeout_check_cb,139

 - idle is 0

Matthias Klumpp (ximion)
Changed in listaller:
milestone: 0.4-alpha1 → none
Matthias Klumpp (ximion)
summary: - listaller hangs at:"detecting package..."
+ API call of PackageKit GLib2-API does not work on Ubuntu
description: updated
Matthias Klumpp (ximion)
description: updated
Matthias Klumpp (ximion)
summary: - API call of PackageKit GLib2-API does not work on Ubuntu
+ Listaller API call of PackageKit GLib2-API does not work on Ubuntu
tags: added: libinstaller
tags: added: manager
Matthias Klumpp (ximion)
Changed in packagekit (Ubuntu):
status: New → Invalid
Revision history for this message
Matthias Klumpp (ximion) wrote : Re: Listaller API call of PackageKit GLib2-API does not work on Ubuntu

The master branch contains now a patch against this.
Listaller GTK+ modules should not hang anymore while executing PackageKit actions.
Thanks for your bug report!

description: updated
Changed in listaller:
status: In Progress → Fix Released
Matthias Klumpp (ximion)
summary: - Listaller API call of PackageKit GLib2-API does not work on Ubuntu
+ Listaller Manager hangs at:"detecting package..."
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.