Bug 443392 – crash in Panel: changing panel settings

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 443392 - crash in Panel: changing panel settings


Summary:	crash in Panel: changing panel settings


Status:	RESOLVED DUPLICATE of bug 419622

Product:	gnome-panel
Classification:	Other
Component:	general
Version:	2.18.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Panel Maintainers
QA Contact:	Panel Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-06-03 01:08 UTC by bettsd
Modified:	2007-06-09 04:00 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Attachments
gconfigtool log (15.75 KB, text/plain) 2007-06-09 04:00 UTC, bettsd	Details

Description bettsd 2007-06-03 01:08:13 UTC

Version: 2.18.1

What were you doing when the application crashed?
changing panel settings


Distribution: Mandriva Linux release 2007.1 (Official) for i586
Gnome Release: 2.18.0 2007-03-15 (Mandriva)
BugBuddy Version: 2.18.0

System: Linux 2.6.17-14mdv #1 SMP Wed May 9 21:11:43 MDT 2007 i686
X Vendor: The X.Org Group
X Vendor Release: 6600
Selinux: No
Accessibility: Disabled
GTK+ Theme: Ia Ora Free
Icon Theme: gnome

Memory status: size: 45817856 vsize: 45817856 resident: 12455936 share: 9703424 rss: 12455936 rss_rlim: 4294967295
CPU usage: start_time: 1180832841 rtime: 16 utime: 14 stime: 2 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gnome-panel'

(no debugging symbols found)
Using host libthread_db library "/lib/i686/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226602816 (LWP 6518)]
(no debugging symbols found)
0xbfffe410 in __kernel_vsyscall ()

+ Trace 137660

Thread 1 (Thread -1226602816 (LWP 6518))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/i686/libpthread.so.0
#2 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/i686/libc.so.6
#6 abort
from /lib/i686/libc.so.6
#7 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#10 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libORBit-2.so.0
#11 CORBA_any__freekids
from /usr/lib/libORBit-2.so.0
#12 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libORBit-2.so.0
#13 CORBA_exception_free
from /usr/lib/libORBit-2.so.0
#14 CORBA_exception_set
from /usr/lib/libORBit-2.so.0
#15 CORBA_exception_set_system
from /usr/lib/libORBit-2.so.0
#16 ORBit_small_invoke_stub
from /usr/lib/libORBit-2.so.0
#17 ORBit_small_invoke_stub_n
from /usr/lib/libORBit-2.so.0
#18 ORBit_c_stub_invoke
from /usr/lib/libORBit-2.so.0
#19 Bonobo_Control_getProperties
from /usr/lib/libbonobo-2.so.0
#20 bonobo_control_frame_get_control_property_bag
from /usr/lib/libbonoboui-2.so.0
#21 ??
#22 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libbonobo-2.so.0
#23 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libbonobo-2.so.0
#24 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libORBit-2.so.0
#25 giop_invoke_async
from /usr/lib/libORBit-2.so.0
#26 giop_connection_handle_input
from /usr/lib/libORBit-2.so.0
#27 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libORBit-2.so.0
#28 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libORBit-2.so.0
#29 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#30 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libglib-2.0.so.0
#31 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#32 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#33 main
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
[FVWM][FvwmErrorHandler]: <<ERROR>> *** internal error ***
[FVWM][FvwmErrorHandler]: <<ERROR>> Request 33, Error 10, EventType: 0
[FVWM][FvwmErrorHandler]: <<ERROR>> *** internal error ***
[FVWM][FvwmErrorHandler]: <<ERROR>> Request 33, Error 10, EventType: 0
[FVWM][Read]: <<ERROR>> file 'extra' not found in /root/.fvwm-metisse or /usr/share/fvwm-insitu
Initializing gnome-mount extension
[FVWM][Echo]: fvwmi StartFunction executed
[FVWM][Echo]: fvwmi SessionInitFunction executed
[FvwmPager-Floating][FlocaleGetFontSet]: (-*-fixed-medium-r-semicondensed-*-13-*-*-*-*-*-*-*,-*-fixed-medium-r-normal-*-14-*-*-*-*-*-*-*,-*-*-medium-r-normal-*-16-*-*-*-*-*-*-*) Missing font charsets:
KSC5601.1987-0, GB2312.1980-0
You can not run beagle as root.  Beagle is designed to run from your own
user account.  If you want to create multiuser or system-wide indexes, use
the beagle-build-index tool.
You can override this setting using the beagle-config or beagle-settings tools.
--------------------------------------------------

Comment 1 Pedro Villavicencio 2007-06-03 01:10:41 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 419622 ***

Comment 2 bettsd 2007-06-03 16:50:17 UTC

I was adding applets to the panel.  After some work i found that the gnome sensors applet locked down the panel.  I had to disable metissa to get the panel to remove the applet. I still can't use the applet without it crashing

Comment 3 Frederic Crozat 2007-06-06 08:11:45 UTC

hmm, which sensor applet did you add exactly ? 

Could you run gconftool -R /apps/panel and attach the log here ?

Thanks you.

Comment 4 bettsd 2007-06-09 04:00:16 UTC

Created attachment 89634 [details]
gconfigtool log