When I exit xfce4 and enter again I get an error message stating that cpugraph has unexpectedly exited the panel and that it should be restarted. Two options appear: restart, and cancel. Restarting shows the same message indefinitively, so the only option is cancel its load (it's removed) and adding it again, and then configuring it again. I'm using debian and the versions are 4.8.0.3 for xfce4 and 1.0.3-1+b1 for xfce4-cpugraph-plugin. Best solution would be to solve this error, I don't know the cause, please let me know if I can help with the diagnose or if there is anything I can do wrt this. An acceptable workaround would be adding and configuring cpugraph with a script. That would be faster and easier, because this happens every time I exit xfce4... I could probably even add this script to the boot of xfce4. Thank you.
It shows this message because the plugin itself crashed, and the wrapper proposes you to restart it - but the plugin crashes again. Since you're using debian, i suppose there's a way to get a backtrace, find a coredump, or something with more details about your configuration so that other people can try to reproduce the issue. How is the plugin configured (colors/refresh speed/cpu cores/etc....) ? Paste the content of .config/xfce4/panel/cpugraph-*.rc here (dont worry it contains no sensitive informations)
These are the contents of that configuration file: UpdateInterval=3 TimeScale=0 Size=28 Mode=0 Frame=0 Border=0 Bars=0 TrackedCore=0 Command=top InTerminal=1 StartupNotification=0 ColorMode=0 Foreground1=#000082105fb8 Foreground2=#ffff00000000 Foreground3=#00000000ffff Background=#eeeeeeeeefef BarsColor=#4b4b69698383 The path is: ~/.config/xfce4/panel/cpugraph-11.rc Please let me know about any other information that may be helpful. I tried to search on /var/log/ but I could not find anything related with xfce, I don't know where those messages may be. Thank you.
Mass-reassign all bugs from florian@ to goodies-dev@, thanks for the maintenance work! (and sorry for the bugmail spam..)
This is a very old bug, probably it got fixed since then, if not please reopen (or file a new bug).