Bug 446957 – crash in Panel: I was logged to home com...

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 446957 - crash in Panel: I was logged to home com...


Summary:	crash in Panel: I was logged to home com...


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-13 01:24 UTC by krzeczyca
Modified:	2007-06-13 02:14 UTC

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

Description krzeczyca 2007-06-13 01:24:38 UTC

Version: 2.18.2

What were you doing when the application crashed?
I was logged to home computer using nomachine client at work. When I came back home and tried to log in I got this "Bug reporting tool".


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: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 48082944 vsize: 48082944 resident: 25649152 share: 22487040 rss: 25649152 rss_rlim: 4294967295
CPU usage: start_time: 1181697659 rtime: 24 utime: 20 stime: 4 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 -1208686880 (LWP 8129)]
(no debugging symbols found)
0x00cd1402 in __kernel_vsyscall ()

+ Trace 140508

Thread 1 (Thread -1208686880 (LWP 8129))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 ??
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 ??
from /lib/libgobject-2.0.so.0
#11 g_closure_invoke
from /lib/libgobject-2.0.so.0
#12 ??
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 ??
from /lib/libgobject-2.0.so.0
#16 ??
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 ??
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 ---------------------
localuser:krzeczyca being added to access control list
SESSION_MANAGER=local/fedora.home.local:/tmp/.ICE-unix/8006
** 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
(gnome-panel:8129): 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 Pedro Villavicencio 2007-06-13 02:14:52 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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