Bug 448923 – crash in Panel: It was shortly after log...

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 448923 - crash in Panel: It was shortly after log...


Summary:	crash in Panel: It was shortly after log...


Status:	RESOLVED DUPLICATE of bug 446183

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-18 21:29 UTC by stephen
Modified:	2007-06-19 07:58 UTC

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

Description stephen 2007-06-18 21:29:21 UTC

Version: 2.18.2

What were you doing when the application crashed?
It was shortly after log-in. A window had popped up, asking which of the X keyboard settings and GNOME keyboard settings I wanted to use (I've been trying to get a Mac keyboard to work nicely, so I've been messing around with the xorg.conf file).



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Tango

Memory status: size: 42676224 vsize: 42676224 resident: 19681280 share: 17137664 rss: 19681280 rss_rlim: 4294967295
CPU usage: start_time: 1182201919 rtime: 33 utime: 29 stime: 4 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208928544 (LWP 6113)]
(no debugging symbols found)
0x00df3402 in __kernel_vsyscall ()

+ Trace 141987

Thread 1 (Thread -1208928544 (LWP 6113))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 ??
from /usr/lib/libgtk-x11-2.0.so.0
#5 g_hash_table_foreach
from /lib/libglib-2.0.so.0
#6 gtk_rc_reset_styles
from /usr/lib/libgtk-x11-2.0.so.0
#7 ??
from /usr/lib/libgtk-x11-2.0.so.0
#8 g_cclosure_marshal_VOID__PARAM
from /lib/libgobject-2.0.so.0
#9 ??
from /lib/libgobject-2.0.so.0
#10 g_closure_invoke
from /lib/libgobject-2.0.so.0
#11 ??
from /lib/libgobject-2.0.so.0
#12 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#13 g_signal_emit
from /lib/libgobject-2.0.so.0
#14 ??
from /lib/libgobject-2.0.so.0
#15 ??
from /lib/libgobject-2.0.so.0
#16 g_object_notify
from /lib/libgobject-2.0.so.0
#17 ??
from /usr/lib/libgtk-x11-2.0.so.0
#18 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#19 ??
from /usr/lib/libgdk-x11-2.0.so.0
#20 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#21 ??
from /lib/libglib-2.0.so.0
#22 g_main_loop_run
from /lib/libglib-2.0.so.0
#23 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#24 main
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
localuser:stephen being added to access control list
SESSION_MANAGER=local/wycliffe.gowarthomas.com:/tmp/.ICE-unix/5984
(gnome-panel:6113): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
--------------------------------------------------

Comment 1 Vincent Untz 2007-06-19 07:58:56 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 446183 ***