Packagekit may crash while installing

[tick@…]

After installing and uninstalling for many times.
The packagekitd may go away.

Maybe it is because *opkg fork failed* but I am not knowing why now.

It's seems nothing related with assassin.

---

root@fic-gta01:~$ assassin install 'tcl;8.4.11-r5;armv4t;'
DEBUG: (assassin.c, 53): get_properties: Type: 0 status: 0 T->package is
tcl;8.4.11-r5;armv4t;
DEBUG: (pkutil.c, 105): packagekit_thread: g_main_loop_run starts
DEBUG: (pkutil.c, 64): pkg_client_initialize: Getting new pk_connection
DEBUG: (pkutil.c, 67): pkg_client_initialize: Getting new pk_client
DEBUG: (pkutil.c, 21): check_connection: check PASS!!
DEBUG: (pkutil.c, 32): check_packagekit: Connection is fine!!
DEBUG: (confirm_command.c, 65): do_confirm:
CP.target->package=tcl;8.4.11-r5;armv4t;
DEBUG: (gears.c, 24): autolayout_type_message: type x=12,y= 0,w=104,h=32
DEBUG: (gears.c, 31): autolayout_button: button move to ( 0,125)
DEBUG: (gears.c, 31): autolayout_button: button move to (240,125)
DEBUG: (assassin.c, 79): main: ecore main loop runs
DEBUG: (confirm_command.c, 18): assassin_confirm_positive: Yes selected!!
DEBUG: (confirm_command.c, 21): assassin_confirm_positive:
cp->target->package=tcl;8.4.11-r5;armv4t;
DEBUG: (actions.c, 160): action: Try to install: tcl;8.4.11-r5;armv4t;
DEBUG: (gears.c, 162): new_Progressbar: text = Downloading
DEBUG: (actions.c, 122): pk_status_change_cb: 0;daeebcde;data Status: setup 0
DEBUG: (actions.c, 135): pk_status_change_cb: target->status=1
DEBUG: (actions.c, 122): pk_status_change_cb: 0;daeebcde;data Status: install
7
DEBUG: (actions.c, 135): pk_status_change_cb: target->status=3
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=0
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 0
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=0
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 0
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=0
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 0
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=0
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 0
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=0
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 0
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=0
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 0
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=0
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 0
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=0
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 0
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=0
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 0
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=0
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 0
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=0
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 0
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=0
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 0
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=0
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 0
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=0
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 0
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=0
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 0
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 0
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 2
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 4
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=4
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 4
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 6
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 8
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 10
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 12
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 14
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 16
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 18
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=18
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 18
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 20
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 22
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 24
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 26
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 29
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 31
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 33
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=33
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 33
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 35
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 37
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 39
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 41
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 43
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 45
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 47
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=47
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 47
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 49
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 51
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 53
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 55
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 57
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 59
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 62
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 64
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=64
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 64
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 66
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 68
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 70
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 72
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 74
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 76
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 78
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=78
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 78
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 80
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 82
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 84
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 86
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 88
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 90
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 92
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 95
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 97
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=97
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 97
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 99
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 100

DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=100
opkg: fork failed
DEBUG: (pkutil.c, 54): pk_connection_changed_cb: Connection changed event
happened!!
DEBUG: (pkutil.c, 57): pk_connection_changed_cb: The daemon went away...DEBUG:
(actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2 progress=100

[thomas@…]

I have tried using pkcon to install and remove a package several times and I
have not managed to reproduce this error.

Today I fixed an issue with the progress bar code which may have resulted in a
crash. Could you please test again using pkcon and see if you can still
reproduce this bug with the latest code. If you can, please run packagekitd
inside gdb and attach a stack trace if it crashes.

[tick@…]

DEBUG: (actions.c, 122): pk_message_cb: details is Downloading
​http://192.168.0.200/build/deploy/glibc/ipk/armv4t//aspell_0.60.5-r0_armv4t.ipk

DEBUG: (actions.c, 75): pk_progress_cb: Progress Update 2
DEBUG: (actions.c, 75): pk_progress_cb: Progress Update 26
DEBUG: (actions.c, 75): pk_progress_cb: Progress Update 52
DEBUG: (actions.c, 75): pk_progress_cb: Progress Update 74
DEBUG: (actions.c, 14): eavs_progress_bar_cb: Update Progess bar status=2
progress=74
DEBUG: (actions.c, 42): eavs_progress_bar_cb: progress is 74
DEBUG: (actions.c, 75): pk_progress_cb: Progress Update 100

opkg: fork failed
DEBUG: (pkutil.c, 54): pk_connection_changed_cb: Connection changed event happened!!
DEBUG: (pkutil.c, 57): pk_connection_changed_cb: The daemon went away...DEBUG:
(actions.c, 14): eavs_progress_bar_cb: Update Progess bar status=2 progress=100
DEBUG: (actions.c, 14): eavs_progress_bar_cb: Update Progess bar status=2
progress=100
...
DEBUG: (actions.c, 14): eavs_progress_bar_cb: Update Progess bar status=2
progress=100
DEBUG: (actions.c, 14): eavs_progress_bar_cb: Update Progess bar status=2
progress=100
DEBUG: (actions.c, 14): eavs_progress_bar_cb: Update Progess bar status=2
progress=100

[1] + Segmentation fault packagekitd

[thomas@…]

I haven't reproduced this on my desktop yet. Please recompile the packagekitd
packages with debugging enabled to produce a useful backtrace. This will be the
only way to debug the issue.

[thomas@…]

I've just fixed a memory corruption issue with opkg, which could have been
related to this bug. I've also tested opkg with valgrind for both install and
remove actions, and it does not detect any memory issues.

Please try again with the latest version of opkg and if there is still a
problem, produce a backtrace with gdb.

[tick@…]

Hi Allen,

Please verify if this issue is fixed.

Thanks,
Tick

[tick@…]

bug fixed