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 366124 - crash in Terminal: Openining editing termin...
crash in Terminal: Openining editing termin...
Status: RESOLVED DUPLICATE of bug 352265
Product: gnome-terminal
Classification: Core
Component: general
2.14.x
Other All
: High critical
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-10-28 07:05 UTC by zal91
Modified: 2006-10-29 00:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description zal91 2006-10-28 07:05:05 UTC 
Version: 2.14.2

What were you doing when the application crashed?
Openining editing terminal profile.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 75866112 vsize: 0 resident: 75866112 share: 0 rss: 20471808 rss_rlim: 0
CPU usage: start_time: 1162019018 rtime: 0 utime: 228 stime: 0 cutime:204 cstime: 0 timeout: 24 it_real_value: 0 frequency: 34

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226049872 (LWP 4765)]
[New Thread -1261732960 (LWP 4771)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 79136

Thread 1 (Thread -1226049872 (LWP 4765))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 ??
  • #5 ??
  • #6 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #7 ??
  • #8 gdk_x11_drawable_get_xdisplay
    from /usr/lib/libgdk-x11-2.0.so.0
  • #9 gdk_x11_drawable_get_xdisplay
    from /usr/lib/libgdk-x11-2.0.so.0
  • #10 gdk_events_pending
    from /usr/lib/libgdk-x11-2.0.so.0
  • #11 _gdk_events_queue
    from /usr/lib/libgdk-x11-2.0.so.0
  • #12 _gdk_events_init
    from /usr/lib/libgdk-x11-2.0.so.0
  • #13 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #14 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #15 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #16 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 ??
  • #18 ??
  • #19 _IO_stdin_used
  • #20 ??
  • #21 ??
  • #0 __kernel_vsyscall 






Comment 1


Mariano Suárez-Alvarez





          2006-10-29 00:20:41 UTC
        



Thanks for the bug report.

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!

This particular bug has already been reported into our bug tracking system.

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