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 427357 - crash in Panel: adding gnome-terminal la...
crash in Panel: adding gnome-terminal la...
Status: RESOLVED DUPLICATE of bug 422966
Product: gnome-panel
Classification: Other
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-04-07 19:12 UTC by Chris Wall
Modified: 2007-07-03 12:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Chris Wall 2007-04-07 19:12:30 UTC 
Version: 2.18.0

What were you doing when the application crashed?
adding gnome-terminal launcher to the desktop


Distribution: Gentoo Base System release 1.12.9
Gnome Release: 2.18.0 2007-04-07 (Gentoo)
BugBuddy Version: 2.18.0

System: Linux 2.6.19-gentoo-r5 #1 Fri Feb 16 19:04:12 CST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 158076928 vsize: 158076928 resident: 21409792 share: 15405056 rss: 21409792 rss_rlim: 18446744073709551615
CPU usage: start_time: 1175966925 rtime: 203 utime: 187 stime: 16 cutime:0 cstime: 2 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 47813015681728 (LWP 9408)]
0x00002b7c544f0ab5 in waitpid () from /lib/libpthread.so.0

+ Trace 125853

Thread 1 (Thread 47813015681728 (LWP 9408))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 ??
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 g_str_hash
    from /usr/lib/libglib-2.0.so.0
  • #4 g_hash_table_remove
    from /usr/lib/libglib-2.0.so.0
  • #5 ??
    from /usr/lib/libgnome-menu.so.2
  • #6 ??
    from /usr/lib/libgnome-menu.so.2
  • #7 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #8 ??
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #10 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 main
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors (85 sec old) ---------------------
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
gnome-mount 0.5
--------------------------------------------------
Comment 1 palfrey 2007-04-07 21:29:57 UTC 
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot
to solve the problem, so it will be hard for the developers to fix that crash.
Can you get us a stack trace with debugging symbols? Please see
http://live.gnome.org/GettingTraces for more information on how to do so.
Thanks in advance!
Comment 2 Bruno Boaventura 2007-05-11 13:39:16 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!
Comment 3 Karsten Bräckelmann 2007-07-03 12:22:58 UTC 
Thanks for taking the time to report this bug.

This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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