Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#18393 - [alunn] alunn_updatescript forks and forks after updating packages
Attached to Project:
Community Packages
Opened by Dieter Rethmeyer (Dieter) - Thursday, 18 February 2010, 22:04 GMT
Last edited by Jaroslav Lichtblau (Dragonlord) - Tuesday, 28 December 2010, 21:03 GMT
Opened by Dieter Rethmeyer (Dieter) - Thursday, 18 February 2010, 22:04 GMT
Last edited by Jaroslav Lichtblau (Dragonlord) - Tuesday, 28 December 2010, 21:03 GMT
|
DetailsDescription:
alunn_updatescript forks and forks after updating packages ps aux shows one suspicious dbus and some knotify4 lines cpu usage goes up to high values as alunn_updatescript creates a lot of processes after successful package upgrade Additional info: * package version(s) alunn 0.7.16-1 * config and/or log files etc. x86_64 system on AMD doublecore alunn config for updates set to "standard kde" Steps to reproduce: use a 64-bit system with KDE desktop install alunn wait for alunn showing that packages can be upgraded right click on alunn icon to update packages run normal package update and exit alunn_updatescript check processes with ps / cpu with top |
This task depends upon
Closed by Jaroslav Lichtblau (Dragonlord)
Tuesday, 28 December 2010, 21:03 GMT
Reason for closing: No response
Additional comments about closing: Closing due to no response. Request reopen if tracking still needed.
Tuesday, 28 December 2010, 21:03 GMT
Reason for closing: No response
Additional comments about closing: Closing due to no response. Request reopen if tracking still needed.
root 17081 0.0 0.5 126684 9400 ? S 23:15 0:00 /usr/bin/knotify4
root 17082 0.0 0.0 0 0 ? Z 23:15 0:00 [knotify4] <defunct>