Created attachment 4494 apport file of the crash I did a fresh installation of Xubuntu Precise 64 bit alternate. xfce4-sensors-plugin are fixed in the on the top in the bar. Apport file is attached. Xubuntu 12.04 64 bit Linux xubuntu2 3.2.0-25-generic #40-Ubuntu SMP Wed May 23 20:30:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux xfce4-sensors-plugin Versions: 1.2.3-2
Does the problem persist still persist? I need better reports than apport. Describe what you have done, did it run successfully before, is it already configured, do you use your old configuration from another computer or distribution? So first wipe out your configuration; then try the stand-alone application xfce4-sensors in a terminal. Does it crash? What is the return code? (Type echo $? directly afterwards.) Configure the plugin with debug symbols (./configure --enable-debug) and run the stand-alone app with gdb. In case that works, add the plugin freshly to the panel. Does it directly crash? If so, follow the guidelines for debugging panel plugins, e.g. by wrapping them via the desktop fiel with gdb. Thanks for helping in finding the bugs you encountered.
(In reply to Fabian Nowak from comment #1) I have a similar problem on Fedora 20 with xfce4-sensors-plugin-1.2.3-8.fc20.x86_64. There are a lot of similar bugreports at Fedora (in vain AFAIK): https://bugzilla.redhat.com/buglist.cgi?component=xfce4-sensors-plugin&list_id=2052898&product=Fedora Here's a backtrace: #0 0x0000003a8308040c in __GI___libc_free (mem=0x3e05809054) at malloc.c:2906 #1 0x0000003a8584ef7f in g_free (mem=0x3e05809054) at gmem.c:197 #2 0x00000000004051d7 in sensors_free (plugin=<optimized out>, sensors=0x1dddf90) at sensors-plugin.c:1091 #3 0x0000003a864104c7 in _g_closure_invoke_va (closure=closure@entry=0x1e0d360, return_value=return_value@entry=0x0, instance=instance@entry=0x1dd50d0, args=args@entry=0x7fffa0b22660, n_params=0, param_types=0x0) at gclosure.c:840 #4 0x0000003a86429749 in g_signal_emit_valist (instance=0x1dd50d0, signal_id=<optimized out>, detail=0, var_args=var_args@entry=0x7fffa0b22660) at gsignal.c:3238 #5 0x0000003a8642a3af in g_signal_emit (instance=<optimized out>, signal_id=signal_id@entry=95, detail=detail@entry=0) at gsignal.c:3386 #6 0x0000003e05409207 in xfce_panel_plugin_dispose (object=0x1dd50d0) at xfce-panel-plugin.c:907 #7 0x0000003a86416df1 in g_object_run_dispose (object=0x1dd50d0) at gobject.c:1067 #8 0x0000003b300bff97 in gtk_container_destroy (object=0x1db10d0) at gtkcontainer.c:1073 #9 0x0000003a86410298 in g_closure_invoke (closure=closure@entry=0x1d9a800, return_value=return_value@entry=0x0, n_param_values=1, param_values=param_values@entry=0x7fffa0b22920, invocation_hint=invocation_hint@entry=0x7fffa0b228c0) at gclosure.c:777 #10 0x0000003a86422704 in signal_emit_unlocked_R (node=node@entry=0x1d9a9c0, detail=detail@entry=0, instance=instance@entry=0x1db10d0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fffa0b22920) at gsignal.c:3702 #11 0x0000003a8642a0f2 in g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=var_args@entry=0x7fffa0b22aa0) at gsignal.c:3330 #12 0x0000003a8642a3af in g_signal_emit (instance=instance@entry=0x1db10d0, signal_id=<optimized out>, detail=detail@entry=0) at gsignal.c:3386 #13 0x0000003b30173b2f in gtk_object_dispose (gobject=0x1db10d0) at gtkobject.c:421 #14 0x0000003a86416df1 in g_object_run_dispose (object=0x1db10d0) at gobject.c:1067 #15 0x000000000040485f in main (argc=8, argv=0x7fffa0b22ce8) at sensors-plugin.c:2359 Abrt reports the crash every time after login from ligthdm(?), but the plugin works nevertheless: I see the heat and RPM values I configured in the panel. It's a new installation.
So, after one year without any more problems and with bugzilla.redhat.com not working currently, can we consider this bug as invalid|wontfix, please?
(In reply to Fabian Nowak from comment #3) > So, after one year without any more problems and with bugzilla.redhat.com > not working currently, can we consider this bug as invalid|wontfix, please? Very funny, dude. It was bugzilla.xfce.org that replied http 500 for hours. Here are the latest sensors_free() bugreports from Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=1188063 https://bugzilla.redhat.com/show_bug.cgi?id=1172907 https://bugzilla.redhat.com/show_bug.cgi?id=1094402 Most older ones are closed by now automatically. You could learn from them. ;) There's a saying around these parts that any problem that doesn't solve itself in a day (or year in this case) doesn't deserve your time to solve it. You can close this bug anytime, but calling it INVALID is a bit shameless.
*sigh* caring. trying to.
The reports are against 1.2.3-8.fc20. Current official release is 1.2.4 and git is 1.2.6 from 2014-04-28... So the bug is invalid because it is fixed meanwhile with no more bug reports since 2014-05-05. I cannot close the bug, so if LAZA or Jannis or Brian could please do that? If it is still valid, I need system info and that the users compile the current git version and I also need the output from configure run.
(In reply to Fabian Nowak from comment #6) > The reports are against 1.2.3-8.fc20. Current official release is 1.2.4 and > git is 1.2.6 from 2014-04-28... I'll look into how to have any of those versions in Fedora 21 then. Here's some good news: https://bugzilla.redhat.com/show_bug.cgi?id=1164400 1.2.5 is in the testing repo. > So the bug is invalid because it is fixed meanwhile with no more bug reports > since 2014-05-05. So it's FIXED then, not INVALID. Great, thanks.
Moving to the correct product and closing as requested.