Bug 52991 - Segfault of packagekitd in pk-transaction
Summary: Segfault of packagekitd in pk-transaction
Status: RESOLVED NOTABUG
Alias: None
Product: PackageKit
Classification: Unclassified
Component: core (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Richard Hughes
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-31 07:40 UTC by tomw
Modified: 2018-08-21 15:52 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
packagekitd --verbose (35.14 KB, text/plain)
2012-07-31 07:40 UTC, tomw
Details

Note You need to log in before you can comment on or make changes to this bug.
Description tomw 2012-07-31 07:40:30 UTC
Created attachment 64981 [details]
packagekitd --verbose

When trying to install a package using the packagekit-glib2 pk_task_install_packages_async packagekitd crashes in pk_trasnsaction_download_size_remaining_cb. 


#0  0x08055eff in pk_transaction_download_size_remaining_cb (job=0x8230018, 
    download_size_remaining=580175452337879778, transaction=0xb7cf6ff4) at pk-transaction.c:1927
#1  0x080630e3 in pk_backend_job_call_vfunc_idle_cb (user_data=0x80d0608) at pk-backend-job.c:587
#2  0xb7c43850 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb7c45d86 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb7c46125 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0xb7c4656b in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0
#6  0x08052e44 in main (argc=1, argv=0xbffff6c4) at pk-main.c:352


this happens both in 0.8.1 and in latest git master
Comment 1 Richard Hughes 2018-08-21 15:52:24 UTC
We moved the upstream bugtracker to GitHub a long time ago. If this issue still affects you please re-create the issue here: https://github.com/hughsie/PackageKit/issues
 
Sorry for the impersonal message, and fingers crossed your issue no longer happens. Thanks.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.