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 404294 - crash in Terminal: This is a automated bug ...
crash in Terminal: This is a automated bug ...
Status: RESOLVED DUPLICATE of bug 359614
Product: gnome-terminal
Classification: Core
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-02-04 15:28 UTC by Sven J.
Modified: 2007-02-07 22:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Sven J. 2007-02-04 15:28:26 UTC 
Version: 2.16.1

What were you doing when the application crashed?
This is a automated bug buddy report, it may be a dupe, i dont know.
I dont now why it crashed.



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

Memory status: size: 75776000 vsize: 0 resident: 75776000 share: 0 rss: 19795968 rss_rlim: 0
CPU usage: start_time: 1170588170 rtime: 0 utime: 1676 stime: 0 cutime:1544 cstime: 0 timeout: 132 it_real_value: 0 frequency: 293

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 -1226725712 (LWP 10409)]
[New Thread -1272198240 (LWP 10413)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 107935

Thread 1 (Thread -1226725712 (LWP 10409))

  • #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 IA__gtk_widget_style_get_valist
    at gtkwidget.c line 7590
  • #5 IA__gtk_widget_style_get
    at gtkwidget.c line 7624
  • #6 gtk_widget_get_draw_rectangle
    at gtkwidget.c line 2677
  • #7 IA__gtk_widget_region_intersect
    at gtkwidget.c line 4172
  • #8 IA__gtk_container_propagate_expose
    at gtkcontainer.c line 2457
  • #9 gtk_container_expose_child
    at gtkcontainer.c line 2349
  • #10 gtk_bin_forall
    at gtkbin.c line 133
  • #11 IA__gtk_container_forall
    at gtkcontainer.c line 1261
  • #12 gtk_container_expose
    at gtkcontainer.c line 2372
  • #13 gtk_window_expose
    at gtkwindow.c line 6070
  • #14 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 84
  • #15 g_value_set_boxed
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #18 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #20 gtk_widget_event_internal
    at gtkwidget.c line 3911
  • #21 IA__gtk_main_do_event
    at gtkmain.c line 1403
  • #22 gdk_window_process_updates_internal
    at gdkwindow.c line 2324
  • #23 IA__gdk_window_process_all_updates
    at gdkwindow.c line 2387
  • #24 gdk_window_update_idle
    at gdkwindow.c line 2245
  • #25 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #26 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #27 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #28 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #29 IA__gtk_main
    at gtkmain.c line 1024
  • #30 ??
  • #31 ??
  • #32 _IO_stdin_used
  • #33 ??
  • #34 ??
  • #0 __kernel_vsyscall 






Comment 1


Mariano Suárez-Alvarez





          2007-02-07 22:02:55 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 359614 ***