Bug 451107 – crash in Panel: Logging into desktop

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 451107 - crash in Panel: Logging into desktop


Summary:	crash in Panel: Logging into desktop


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-26 01:34 UTC by marcrho
Modified:	2007-06-26 09:41 UTC

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

Description marcrho 2007-06-26 01:34:29 UTC

Version: 2.18.2

What were you doing when the application crashed?
Logging into desktop 


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 14:56:37 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Tango

Memory status: size: 348930048 vsize: 348930048 resident: 33931264 share: 29929472 rss: 33931264 rss_rlim: 18446744073709551615
CPU usage: start_time: 1182821487 rtime: 29 utime: 26 stime: 3 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496331792 (LWP 2777)]
(no debugging symbols found)
0x00000031d460d865 in waitpid () from /lib64/libpthread.so.0

+ Trace 143731

Thread 1 (Thread 46912496331792 (LWP 2777))

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



----------- .xsession-errors ---------------------
localuser:[username] being added to access control list
SESSION_MANAGER=local/[hostname]:/tmp/.ICE-unix/2700
Initializing nautilus-open-terminal extension
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
exception when creating syslog handler: (2, 'No such file or directory')
(gnome-panel:2777): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
Window manager warning: Lost connection to the display ':0.0';
most likely the X server was shut down or you killed/destroyed
the window manager.
--------------------------------------------------

Comment 1 Vincent Untz 2007-06-26 09:41:53 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 ***