This bug has been reported on Ubuntu Launchpad as https://bugs.launchpad.net/bugs/574932 The plugin crashed after login in a xfce session Description: Ubuntu 10.04 LTS Release: 10.04 xfce4-sensors-plugin: Instalados: 0.10.99.6-2 Candidato: 0.10.99.6-2 Tabla de versión: *** 0.10.99.6-2 0 500 http://archive.ubuntu.com/ubuntu/ lucid/universe Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 10.04 Package: xfce4-sensors-plugin 0.10.99.6-2 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Mon May 3 15:31:09 2010 ExecutablePath: /usr/lib/xfce4-sensors-plugin/xfce4/panel-plugins/xfce4-sensors-plugin ProcCmdline: /usr/lib/xfce4-sensors-plugin/xfce4/panel-plugins/xfce4-sensors-plugin socket_id 25165862 name xfce4-sensors-plugin id 11953655596 display_name Sensor\ plugin size 34 screen_position 11 ProcEnviron: LANG=es_ES.utf8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x47c8bb: mov 0x4(%edi),%edx PC (0x0047c8bb) ok source "0x4(%edi)" (0x092c154c) not located in a known VMA region (needed readable region)! destination "%edx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: xfce4-sensors-plugin StacktraceTop: malloc_consolidate (av=<value optimized out>) at malloc.c:5136 _int_malloc (av=<value optimized out>, _int_memalign (av=<value optimized out>, alignment=512, *__GI___libc_memalign (alignment=512, bytes=504) __posix_memalign (memptr=0xbf87feec, alignment=148214104, Title: xfce4-sensors-plugin crashed with SIGSEGV in memalign() UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video XsessionErrors: (polkit-gnome-authentication-agent-1:1317): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (xfce4-cpugraph-plugin:1369): Gtk-CRITICAL **: gtk_container_set_border_width: assertion `GTK_IS_CONTAINER (container)' failed Stacktrace available: http://launchpadlibrarian.net/47755170/Stacktrace.txt
Thanks for the report; however it is against a rather old version on an old distribution, (release-)upgrading will fix it for you. As a sidenote, I wonder why xfce4-cpugraph-plugin is intermingled with the report; you might also want to investigate in the wrong assertion of the cpugraph plugin and file a bug report there, too.
I guess this is fixed by fixing bug 8745 *** This bug has been marked as a duplicate of bug 8745 ***