Bug 447716 – crash in Panel: Logging in after hang.

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 447716 - crash in Panel: Logging in after hang.


Summary:	crash in Panel: Logging in after hang.


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-14 23:55 UTC by john
Modified:	2007-06-15 13:52 UTC

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

Description john 2007-06-14 23:55:40 UTC

Version: 2.18.2

What were you doing when the application crashed?
Logging in after hang.


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: Echo

Memory status: size: 52826112 vsize: 52826112 resident: 25346048 share: 22458368 rss: 25346048 rss_rlim: 4294967295
CPU usage: start_time: 1181865283 rtime: 18 utime: 15 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 "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208129824 (LWP 4437)]
(no debugging symbols found)
0x0068b402 in __kernel_vsyscall ()

+ Trace 141081

Thread 1 (Thread -1208129824 (LWP 4437))

#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:jhover being added to access control list
SESSION_MANAGER=local/eclipse.saros.us:/tmp/.ICE-unix/4328
SSH_AUTH_SOCK=/tmp/ssh-Qdxqdz4448/agent.4448; export SSH_AUTH_SOCK;
SSH_AGENT_PID=4450; export SSH_AGENT_PID;
echo Agent pid 4450;
Unable to open desktop file /usr/share/applications/livna-totem.desktop for panel launcher: No such file or directory
Unable to open desktop file /usr/share/applications/fedora-celestia.desktop for panel launcher: No such file or directory
Unable to open desktop file /usr/share/applications/gnome-banshee.desktop for panel launcher: No such file or directory
(gnome-panel:4437): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
--------------------------------------------------

Comment 1 Vincent Untz 2007-06-15 13:52:18 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 ***