GNOME Bugzilla – Bug 351968
gnome-panel 2.15.91 segfaults when editing launcher properties
Last modified: 2006-08-18 21:26:00 UTC
Steps to reproduce: 1. Right click on a launcher icon and select "Properties". 2. Segfault. Stack trace: Memory status: size: 29229056 vsize: 0 resident: 29229056 share: 0 rss: 13611008 rss_rlim: 0 CPU usage: start_time: 1155923716 rtime: 0 utime: 184 stime: 0 cutime:168 cstime: 0 timeout: 16 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-panel' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1224948048 (LWP 9774)] _______________________________________________________________________________ eax:FFFFFE00 ebx:000027F6 ecx:BF96CF58 edx:00000000 eflags:00200246 esi:BF96D30C edi:B7111FF4 esp:BF96CE78 ebp:BF96CF68 eip:FFFFE410 cs:0073 ds:007B es:007B fs:0000 gs:0033 ss:007B o d I t s Z a P c [007B:BF96CE78]---------------------------------------------------------[stack] BF96CEA8 : E0 9B 35 B7 00 00 00 00 - F4 1F 11 B7 20 31 11 B7 ..5......... 1.. BF96CE98 : 00 00 00 00 4C D0 96 BF - 5C CF 96 BF E8 76 33 B7 ....L...\....v3. BF96CE88 : D4 6A EC B7 05 2A E9 B7 - F6 27 00 00 58 CF 96 BF .j...*...'..X... BF96CE78 : 68 CF 96 BF 00 00 00 00 - 58 CF 96 BF B3 DF 35 B7 h.......X.....5. [007B:BF96D30C]---------------------------------------------------------[ data] BF96D30C : 20 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ............... BF96D31C : 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................ [0073:FFFFE410]---------------------------------------------------------[ code] 0xffffe410 <__kernel_vsyscall+16>: pop %ebp 0xffffe411 <__kernel_vsyscall+17>: pop %edx 0xffffe412 <__kernel_vsyscall+18>: pop %ecx 0xffffe413 <__kernel_vsyscall+19>: ret 0xffffe414 <__kernel_vsyscall+20>: nop 0xffffe415 <__kernel_vsyscall+21>: nop ------------------------------------------------------------------------------ 0xffffe410 in __kernel_vsyscall ()
+ Trace 70682
Other information:
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. Exact dupe of bug 350613, which is a dupe of bug 350425. *** This bug has been marked as a duplicate of 350425 ***