Bug 515254 – crash in Panel: remote login using ssh/n...

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 515254 - crash in Panel: remote login using ssh/n...


Summary:	crash in Panel: remote login using ssh/n...


Status:	RESOLVED DUPLICATE of bug 472358

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:	2008-02-08 19:07 UTC by ccronin
Modified:	2008-02-08 20:51 UTC

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

Description ccronin 2008-02-08 19:07:11 UTC

Version: 2.18.3

What were you doing when the application crashed?
remote login using ssh/nx client


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.14-64.fc7 #1 SMP Sun Jan 20 23:54:08 EST 2008 i686
X Vendor: The XFree86 Project, Inc
X Vendor Release: 40300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 85340160 vsize: 85340160 resident: 36925440 share: 32481280 rss: 36925440 rss_rlim: 4294967295
CPU usage: start_time: 1202327715 rtime: 167 utime: 139 stime: 28 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 -1208650016 (LWP 7127)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 188563

Thread 1 (Thread -1208650016 (LWP 7127))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 strcmp
from /lib/libc.so.6
#5 panel_profile_remove_from_list
#6 panel_profile_delete_object
#7 ??
#8 g_cclosure_marshal_VOID
from /lib/libgobject-2.0.so.0
#9 g_closure_invoke
from /lib/libgobject-2.0.so.0
#10 ??
from /lib/libgobject-2.0.so.0
#11 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#12 g_signal_emit
from /lib/libgobject-2.0.so.0
#13 gtk_dialog_response
from /usr/lib/libgtk-x11-2.0.so.0
#14 ??
from /usr/lib/libgtk-x11-2.0.so.0
#15 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#16 g_closure_invoke
from /lib/libgobject-2.0.so.0
#17 ??
from /lib/libgobject-2.0.so.0
#18 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#19 g_signal_emit
from /lib/libgobject-2.0.so.0
#20 gtk_button_clicked
from /usr/lib/libgtk-x11-2.0.so.0
#21 ??
from /usr/lib/libgtk-x11-2.0.so.0
#22 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#23 ??
from /lib/libgobject-2.0.so.0
#24 g_closure_invoke
from /lib/libgobject-2.0.so.0
#25 ??
from /lib/libgobject-2.0.so.0
#26 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#27 g_signal_emit
from /lib/libgobject-2.0.so.0
#28 gtk_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#29 ??
from /usr/lib/libgtk-x11-2.0.so.0
#30 ??
from /usr/lib/libgtk-x11-2.0.so.0
#31 ??
from /lib/libgobject-2.0.so.0
#32 g_closure_invoke
from /lib/libgobject-2.0.so.0
#33 ??
from /lib/libgobject-2.0.so.0
#34 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#35 g_signal_emit
from /lib/libgobject-2.0.so.0
#36 ??
from /usr/lib/libgtk-x11-2.0.so.0
#37 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#38 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#39 ??
from /usr/lib/libgdk-x11-2.0.so.0
#40 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#41 ??
from /lib/libglib-2.0.so.0
#42 g_main_loop_run
from /lib/libglib-2.0.so.0
#43 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#44 main
#0 __kernel_vsyscall



----------- .xsession-errors (151605 sec old) ---------------------
xscreensaver: 19:58:27: 0: for window 0x3000021 (gnome-screensaver / Gnome-screensaver)
xscreensaver: 19:58:35: couldn't grab keyboard!  (AlreadyGrabbed)
xscreensaver: 19:58:39: couldn't grab keyboard!  (AlreadyGrabbed)
xscreensaver: 19:58:43: couldn't grab pointer!  (AlreadyGrabbed)
xscreensaver: 19:58:43: unable to grab keyboard or mouse!  Blanking aborted.
xscreensaver: 19:58:57: 0: unrecognised ClientMessage "_NET_ACTIVE_WINDOW" received
xscreensaver: 19:58:57: 0: for window 0x3000021 (gnome-screensaver / Gnome-screensaver)
xscreensaver: 19:59:27: 0: unrecognised ClientMessage "_NET_ACTIVE_WINDOW" received
xscreensaver: 19:59:27: 0: for window 0x3000021 (gnome-screensaver / Gnome-screensaver)
xscreensaver: 19:59:47: couldn't grab keyboard!  (AlreadyGrabbed)
xscreensaver: 19:59:51: couldn't grab keyboard!  (AlreadyGrabbed)
xscreensaver: 19:59:55: couldn't grab pointer!  (AlreadyGrabbed)
xscreensaver: 19:59:55: unable to grab keyboard or mouse!  Blanking aborted.
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Philip Withnall 2008-02-08 20:51:11 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 472358 ***