Gnome Packagekit crashes when entering a package name search in Ubuntu Noble

Bug #2046843 reported by Xavier Guillot
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gnome-packagekit (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Hi, I run Ubuntu development branch 24.04 and I have a problem with Gnome PackageKit 43.0-2 : application launches well, but if I write a program / package name in the search field and click on"Enter", it crashes and closes :

$ gpk-application

(gpk-application:12334): PackageKit-CRITICAL **: 17:52:58.785: pk_client_generic_finish: assertion 'G_IS_TASK (res)' failed
Erreur de segmentation (core dumped)

$ gpk-application

(gpk-application:32194): PackageKit-CRITICAL **: 22:23:35.001: pk_client_generic_finish: assertion 'G_IS_TASK (res)' failed
Erreur de segmentation (core dumped)

description: updated
Revision history for this message
Xavier Guillot (valeryan-24) wrote :

As many programs have the "core dumped" error, this is perhaps the explanation, related to AppArmor:

https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/2046844/comments/3

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-packagekit (Ubuntu):
status: New → Confirmed
Revision history for this message
John Johansen (jjohansen) wrote :

I have confirmed this is not due to the AppArmor user namespace restriction. When trying to search for an application the application will crash with the following segfault

[79854.520976] gpk-application[19250]: segfault at 8 ip 00005930eec2dba8 sp 00007fff471b6b70 error 4 in gpk-application[5930eec24000+d000] likely on CPU 1 (core 0, socket 1)
[79854.520985] Code: 85 ff 0f 85 72 fd ff ff e9 72 fd ff ff 0f 1f 44 00 00 48 8b 44 24 30 48 8d 15 37 46 00 00 be 10 00 00 00 48 8d 3d c2 34 00 00 <48> 8b 48 08 31 c0 e8 6d 79 ff ff c7 43 04 00 00 00 00 48 8b 7b 50

Revision history for this message
Xavier Guillot (valeryan-24) wrote :

I still have the issue on Ubuntu 24.04 final :

$ gpk-application

(gpk-application:36353): PackageKit-CRITICAL **: 19:38:03.762: pk_client_generic_finish: assertion 'G_IS_TASK (res)' failed
Erreur de segmentation (core dumped)

Revision history for this message
Mantas Kriaučiūnas (mantas) wrote :

Same issue on Ubuntu 24.04 LTS - I write something in the search field and press "Enter", then gnome-packagekit crashes and closes :( Here is output from terminal:

mantas@Ubuntu-24-Baltix:~$ gpk-application -v
14:22:32 GnomePackageKit Verbose debugging enabled (on console 1)
14:22:32 PackageKit role now get-repo-list
14:22:32 GnomePackageKit CLEAR search
14:22:32 GnomePackageKit no input
14:22:32 GnomePackageKit CLEAR search
14:22:32 GnomePackageKit no input
14:22:32 PackageKit notify::connected
14:22:32 GnomePackageKit state=5
14:22:32 GnomePackageKit set search type=1
14:22:32 GnomePackageKit CLEAR welcome
14:22:32 GnomePackageKit now wait
14:22:32 PackageKit emit transaction-list-changed
14:22:32 GnomePackageKit now setup
14:22:32 GnomePackageKit now query
14:22:32 GnomePackageKit now finished
14:22:32 PackageKit emit transaction-list-changed
14:22:51 GnomePackageKit CLEAR search
14:22:51 GnomePackageKit find browser
14:22:51 PackageKit adding state 0x60642424e4f0
14:22:51 PackageKit role now search-details
14:22:51 GnomePackageKit now wait
14:22:51 PackageKit emit transaction-list-changed
14:22:51 GnomePackageKit now setup
14:22:51 GnomePackageKit now loading-cache
14:22:51 GnomePackageKit now query
14:22:53 GnomePackageKit now finished
14:22:53 PackageKit remove state 0x60642424e4f0
14:22:53 PackageKit emit transaction-list-changed

(gpk-application:18772): PackageKit-CRITICAL **: 14:22:53.337: pk_client_generic_finish: assertion 'G_IS_TASK (res)' failed
Trace/breakpoint trap

Revision history for this message
Xavier Guillot (valeryan-24) wrote :

Hi, to help resolve the issue and its cause : I just updated to Ubuntu development branch 24.10 and bug isn't there anymore, Gnome Packagekit doesn't crash - so one or many of the updates have corrected the bug.

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.