Bug 451833 – crash in Panel: Logging 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 451833 - crash in Panel: Logging in.


Summary:	crash in Panel: Logging 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:

Depends on:
Blocks:

Reported:	2007-06-28 05:23 UTC by clinic.blue
Modified:	2007-06-28 14:03 UTC

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

Description clinic.blue 2007-06-28 05:23:38 UTC

Version: 2.18.2

What were you doing when the application crashed?
Logging 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.3228.fc7 #1 SMP Tue Jun 12 15:37:31 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: 36638720 vsize: 36638720 resident: 18563072 share: 15159296 rss: 18563072 rss_rlim: 4294967295
CPU usage: start_time: 1183008116 rtime: 45 utime: 39 stime: 6 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 -1208621344 (LWP 4017)]
(no debugging symbols found)
0x0095e402 in __kernel_vsyscall ()

+ Trace 144290

Thread 1 (Thread -1208621344 (LWP 4017))

#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 g_slist_remove_all
from /lib/libglib-2.0.so.0
#5 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libgtk-x11-2.0.so.0
#6 g_hash_table_foreach
from /lib/libglib-2.0.so.0
#7 gtk_rc_reset_styles
from /usr/lib/libgtk-x11-2.0.so.0
#8 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libgtk-x11-2.0.so.0
#9 g_cclosure_marshal_VOID__PARAM
from /lib/libgobject-2.0.so.0
#10 g_cclosure_marshal_VOID__ENUM
from /lib/libgobject-2.0.so.0
#11 g_closure_invoke
from /lib/libgobject-2.0.so.0
#12 g_cclosure_marshal_VOID__ENUM
from /lib/libgobject-2.0.so.0
#13 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#14 g_signal_emit
from /lib/libgobject-2.0.so.0
#15 g_cclosure_marshal_VOID__ENUM
from /lib/libgobject-2.0.so.0
#16 g_cclosure_marshal_VOID__ENUM
from /lib/libgobject-2.0.so.0
#17 g_object_notify
from /lib/libgobject-2.0.so.0
#18 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libgtk-x11-2.0.so.0
#19 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#20 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libgdk-x11-2.0.so.0
#21 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#22 g_cclosure_marshal_VOID__ENUM
from /lib/libglib-2.0.so.0
#23 g_main_loop_run
from /lib/libglib-2.0.so.0
#24 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#25 main
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
Checking Display :0.0 ...
Checking for XComposite extension               : passed (v0.3)
Checking for XDamage extension                  : passed
Checking for RandR extension                    : passed
Checking for XSync extension                    : passed
Checking Screen 0 ...
Checking for GLX_SGIX_fbconfig                  : passed
Checking for GLX_EXT_texture_from_pixmap        : passed
Checking for non power of two texture support   : passed
Checking maximum texture size                   : passed (2048x2048)
--------------------------------------------------

Comment 1 palfrey 2007-06-28 14:03:28 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 ***