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 515842 - crash in Panel: using the terminal
crash in Panel: using the terminal
Status: RESOLVED DUPLICATE of bug 504600
Product: gnome-panel
Classification: Other
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-02-11 18:57 UTC by eric.saxe
Modified: 2008-02-11 19:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description eric.saxe 2008-02-11 18:57:53 UTC 
Version: 2.20.1

What were you doing when the application crashed?
using the terminal


Distribution:                    Solaris Express Community Edition snv_82 X86
Gnome Release: 2.20.2 2008-01-15 (Sun Microsystems, Inc.)
BugBuddy Version: 2.20.1

X Vendor: Sun Microsystems, Inc.
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: nimbus
Icon Theme: nimbus

Memory status: size: 139997184 vsize: 139997184 resident: 18817024 share: 393216 rss: 18817024 rss_rlim: 0
CPU usage: start_time: 0 rtime: 86 utime: 669285 stime: 191361 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/gnome-panel'

(no debugging symbols found)
sol-thread active.
Retry #1:
Retry #2:
Retry #3:
Retry #4:
[New LWP    1        ]
[New Thread 1 (LWP 1)]

+ Trace 188861

Thread 1 (LWP 1)

  • #0 _waitid
    from /lib/libc.so.1
  • #1 _waitpid
    from /lib/libc.so.1
  • #2 waitpid_cancel
    from /lib/libc.so.1
  • #3 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #5 __1cNrun_bug_buddy6Fpkclp0_b_
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 __1cMcheck_if_gdb6Fpv_b_
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #7 _ex_text0
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #8 __sighndlr
    from /lib/libc.so.1
  • #9 call_user_handler
    from /lib/libc.so.1
  • #10 <signal handler called>
  • #11 ??
  • #12 handle_cached_dir_changed
    from /usr/lib/libgnome-menu.so.2
  • #13 emit_events_in_idle
    from /usr/lib/libgnome-menu.so.2
  • #14 g_idle_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #15 g_main_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #16 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #17 g_main_context_iterate
    from /usr/lib/libglib-2.0.so.0
  • #18 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #19 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 main 

Thread 1 (LWP    1        ):
#-1 0xfef03f35 in _waitid () from /lib/libc.so.1
No symbol table info available.
#-1 0xfef03f35 in _waitid () from /lib/libc.so.1


----------- .xsession-errors (111627435 sec old) ---------------------
/etc/X11/gdm/PreSession/Default: Registering your session with wtmp and utmp
/etc/X11/gdm/PreSession/Default: running: /usr/bin/X11/sessreg -a -w /var/log/wtmp -u /var/run/utmp -x "/var/lib/gdm/:0.Xservers" -h "" -l :0 esaxe
/etc/X11/gdm/Xsession: Beginning session setup...
/etc/X11/gdm/Xsession: line 1: uname: command not found
/etc/X11/gdm/Xsession: line 1: uname: command not found
/etc/X11/gdm/Xsession: line 1: /usr/ucb/arch: No such file or directory
/etc/X11/gdm/Xsession: line 1: /usr/bin/uname: No such file or directory
/etc/X11/gdm/Xsession: line 1: uname: command not found
/etc/X11/gdm/Xsession: line 136: xmodmap: command not found
/etc/X11/gdm/Xsession: Setup done, will execute: /usr/bin/ssh-agent -- gnome-session
/usr/bin/ssh-agent: error while loading shared libraries: libsocket.so.1: cannot open shared object file: No such file or directory
--------------------------------------------------
Comment 1 Philip Withnall 2008-02-11 19:03:41 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 504600 ***