Summary: | xfce-extra/xfce4-sensors-plugin-1.0.0 segmentation fault | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | churchmice <firefoxelectric> |
Component: | Current packages | Assignee: | XFCE Team <xfce> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | gaurdro, kmeagher, pamelus, tesoro302, vityokster |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
URL: | http://bugzilla.xfce.org/show_bug.cgi?id=6603 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Patch which fixes segfault at the expense of possibly reduced functionality |
Description
churchmice
2010-05-06 13:45:30 UTC
I have similar problem. But dmesg says: xfce4-sensors-p[29745]: segfault at 0 ip b6c7f1ff sp bfd90230 error 4 in libglib-2.0.so.0.2200.5[b6c27000+ca000] xfce4-sensors-p[29860]: segfault at 0 ip b6c541ff sp bf85b970 error 4 in libglib-2.0.so.0.2200.5[b6bfc000+ca000] xfce4-sensors-p[29921]: segfault at 0 ip b6d3e1ff sp bf8292c0 error 4 in libglib-2.0.so.0.2200.5[b6ce6000+ca000] please attach a gdb backtrace. see http://www.gentoo.org/proj/en/qa/backtraces.xml and http://wiki.xfce.org/howto/panel_plugin_debug for more information. I get the same problem I tried to get a stack track by remerging xfce4-sensors-plugins with -ggdb and FEATURES='nostrip' and following the insturctions to get a stacktrace from an xfce plugin, it was rather unhelpful: GNU gdb (Gentoo 7.1 p1) 7.1 Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". For bug reporting instructions, please see: <http://bugs.gentoo.org/>... Reading symbols from /usr/libexec/xfce4/panel-plugins/xfce4-sensors-plugin...done. Starting program: /usr/libexec/xfce4/panel-plugins/xfce4-sensors-plugin socket_id=0 name=xfce4-sensors-plugin-gdb id=12786759745 display_name=Sensor plugin GDB size=30 screen_position=10 [Thread debugging using libthread_db enabled] Program exited with code 01. No stack. The program is not being run. that doesn't look like it crashed Yes, but from the users point of view unexpectedly exiting with error state 1 isn't any better. I forgot to mention that this is probably a hardware/driver specific bug because it started doing this after I changed motherboards on the same gentoo install. If you have any further suggestions as to how to debug this problem let me know and I will try. well, as long as it doesn't segfault, that's a different bug. so, please open a new bug for your issue. Sorry I wasn't clearer earlier. When I run it in gdb I get the Exit with code 01 posted above. But, when I run it without gdb i get the same segfault: xfce4-sensors-p[11147]: segfault at 0 ip 00007f151e5b0b52 sp 00007fff32dc11e8 error 4 in libc-2.11.2.so[7f151e534000+150000] so it is the same bug, just running it in gdb somehow prevents the segfault an makes it exit unexpectedly. Created attachment 240879 [details, diff]
Patch which fixes segfault at the expense of possibly reduced functionality
Additional research is required. I do not have time atm.
Oops, forgot to post this Experiencing the same problem. Attaching a temporary patch (solves the problem but possibly disables some functionality) which illustrates the problematic line. Apparently, font=0, hence the segfault when calling strlen(font). the problematic line is lib/configuration.c line 110 Same problem here. tail -f /var/log/messages says: Aug 23 17:40:42 tuxie kernel: [ 7379.401190] xfce4-sensors-p[7976]: segfault at 0 ip b6b4b693 sp bfae787c error 4 in libc-2.11.2.so[b6ad7000+143000] immediatelly after click on "Close" button in "Add applet" dialog. After downgrade to 0.10.99.6 I can't even start "Add applet" dialog. Running xfce4-sensors from console returns: $ xfce4-sensors *** glibc detected *** xfce4-sensors: free(): invalid pointer: 0xb78235b2 *** ======= Backtrace: ========= /lib/libc.so.6(+0x6c534)[0xb71ba534] /lib/libc.so.6(+0x6ddb3)[0xb71bbdb3] /lib/libc.so.6(cfree+0x6d)[0xb71bed8d] /usr/lib/libglib-2.0.so.0(g_free+0x37)[0xb72f6c77] So potentially this is libc problem? Livid's patch fixed problem for me also. Same problem here. Can we have the patch in portage? (In reply to comment #12) > Same problem here. Can we have the patch in portage? > agreed. from reading the patch it would be fairly trivial and better than running gkrellm just for one sensor to work. I have confirmed that the patch by Livid works via an overlay with no other modifications. http://pastebin.com/ddcfkrth for the modified ebuild in full. Please update in portage. #PATCHES=( "${FILESDIR}/${P}-missing_includedir.patch" # "${FILESDIR}/${P}-without_libnotify.patch" #+ "${FILESDIR}/${P}-segfault.patch" ) (In reply to comment #8) > Created an attachment (id=240879) [details] > Patch which fixes segfault at the expense of possibly reduced functionality > > Additional research is required. I do not have time atm. > +*xfce4-sensors-plugin-1.0.0-r1 (18 Dec 2010) + + 18 Dec 2010; Samuli Suominen <ssuominen@gentoo.org> + +xfce4-sensors-plugin-1.0.0-r1.ebuild, + +files/xfce4-sensors-plugin-1.0.0-segfault_workaround.patch: + Apply a workaround for segfault wrt #318755 by Livid. Please comment and continue discussion in http://bugzilla.xfce.org/show_bug.cgi?id=6603 instead of here so it'll get fixed for next release. |