Bug 446053 – crash in Panel: login in

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 446053 - crash in Panel: login in


Summary:	crash in Panel: login in


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:

Duplicates:	446294 (view as bug list)
Depends on:
Blocks:

Reported:	2007-06-10 15:37 UTC by alexander.grullon
Modified:	2007-07-05 10:18 UTC

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

Description alexander.grullon 2007-06-10 15:37:06 UTC

Version: 2.18.2

What were you doing when the application crashed?
login in 


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.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 37314560 vsize: 37314560 resident: 17829888 share: 15237120 rss: 17829888 rss_rlim: 4294967295
CPU usage: start_time: 1181489708 rtime: 22 utime: 17 stime: 5 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 -1209002272 (LWP 8097)]
(no debugging symbols found)
0x00a4a402 in __kernel_vsyscall ()

+ Trace 139803

Thread 1 (Thread -1209002272 (LWP 8097))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 g_cclosure_marshal_VOID__ENUM
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 g_cclosure_marshal_VOID__ENUM
from /lib/libgobject-2.0.so.0
#10 g_closure_invoke
from /lib/libgobject-2.0.so.0
#11 g_cclosure_marshal_VOID__ENUM
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 g_cclosure_marshal_VOID__ENUM
from /lib/libgobject-2.0.so.0
#15 g_cclosure_marshal_VOID__ENUM
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 g_cclosure_marshal_VOID__ENUM
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:agrullon being added to access control list
SESSION_MANAGER=local/brahams:/tmp/.ICE-unix/7983
(gnome-panel:8097): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
--------------------------------------------------

Comment 1 Vincent Untz 2007-06-10 19:41:31 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!

Comment 2 André Klapper 2007-06-11 21:39:02 UTC

*** Bug 446294 has been marked as a duplicate of this bug. ***

Comment 3 André Klapper 2007-07-05 10:17:52 UTC

same issue as bug 446183

Comment 4 André Klapper 2007-07-05 10:18:31 UTC

Thanks for taking the time to report this bug.
The maintainers need more information to fix the bug. Could you please answer the questions in the bug 446183 in order to help the developers?


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