Bug 448116 – crash in Panel: logging on

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 448116 - crash in Panel: logging on


Summary:	crash in Panel: logging on


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-16 06:07 UTC by dann26
Modified:	2007-06-16 07:48 UTC

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

Description dann26 2007-06-16 06:07:59 UTC

Version: 2.18.2

What were you doing when the application crashed?
logging on


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: Amaranth
Icon Theme: Amaranth

Memory status: size: 55660544 vsize: 55660544 resident: 23896064 share: 20897792 rss: 23896064 rss_rlim: 4294967295
CPU usage: start_time: 1181974028 rtime: 22 utime: 19 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 -1209022752 (LWP 2854)]
(no debugging symbols found)
0x00fb1402 in __kernel_vsyscall ()

+ Trace 141381

Thread 1 (Thread -1209022752 (LWP 2854))

#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 ??
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 ??
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 ??
from /usr/lib/libgtk-x11-2.0.so.0
#19 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#20 ??
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 (8 sec old) ---------------------
localuser:root being added to access control list
SESSION_MANAGER=local/equilibrium:/tmp/.ICE-unix/2735
Xgl is not running: compiz/beryl will not be launched.
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
winscard_clnt.c:3349:SCardCheckDaemonAvailability() PCSC Not Running
Debug: Loading Beagle.Util.Conf+IndexingConfig from indexing.xml
(gnome-panel:2854): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
Debug: Loading Beagle.Util.Conf+DaemonConfig from daemon.xml
Debug: Loading Beagle.Util.Conf+SearchingConfig from searching.xml
Always: Starting Beagle Daemon (version 0.2.16.2)
Always: Running on Mono 1.2.3
Always: Using sqlite version 3
Always: Command Line: /usr/lib/beagle/BeagleDaemon.exe --autostarted --bg
kbuildsycoca running...
--------------------------------------------------

Comment 1 Vincent Untz 2007-06-16 07:48:01 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 ***