A debian user reported that when killing its X server for some reason, the xfapplet plugin was still running, with a PPID of 1 (init), and it seems to cause problems at the next xfce4-panel start. Is there a reason for this, or could we consider this as a bug? (sorry, no component for xfapplet-plugin) Cheers, -- Yves-Alexis
This bug has been reported to Ubuntu Launchpad as: https://bugs.launchpad.net/bugs/683910 I just upgraded to 10.04 (yeah, I'm a little behind the times). I have been seeing this same behavior since Karmic. It is still present in Lucid. Usually after a logout, the CPU pegs at 100% for each instance of xfapplet set up. For me, it happens for gnome sensors-applet. I must manually kill the runaway process after I login again, or from another PTY. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: xfce4-xfapplet-plugin 0.1.0-3ubuntu4 ProcVersionSignature: Ubuntu 2.6.32-26.48-generic 2.6.32.24+drm33.11 Uname: Linux 2.6.32-26-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Wed Dec 1 17:51:13 2010 ProcEnviron: PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: xfce4-xfapplet-plugin
Any news on this?
Mass-reassign all bugs from florian@ to goodies-dev@, thanks for the maintenance work! (and sorry for the bugmail spam..)
Closing all xfce4-xfapplet-plugin (archived/deprecated/unmaintained project).