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 412325 - crash in Terminal: comprimiendo un video co...
crash in Terminal: comprimiendo un video co...
Status: RESOLVED DUPLICATE of bug 352444
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-26 17:36 UTC by sbp_m
Modified: 2007-03-17 20:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description sbp_m 2007-02-26 17:36:45 UTC
Version: 2.16.1

What were you doing when the application crashed?
comprimiendo un video con mencoder


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

Memory status: size: 113045504 vsize: 0 resident: 113045504 share: 0 rss: 79613952 rss_rlim: 0
CPU usage: start_time: 1172493984 rtime: 0 utime: 7433 stime: 0 cutime:5623 cstime: 0 timeout: 1810 it_real_value: 0 frequency: 1307

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 -1225959760 (LWP 8121)]
[New Thread -1245451360 (LWP 8126)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1225959760 (LWP 8121))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 874
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #7 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #10 ORBit_RootObject_duplicate_T
    from /usr/lib/libORBit-2.so.0
  • #11 CORBA_free
    from /usr/lib/libORBit-2.so.0
  • #12 CORBA_free
    from /usr/lib/libORBit-2.so.0
  • #13 ORBit_free_T
    from /usr/lib/libORBit-2.so.0
  • #14 ORBit_free
    from /usr/lib/libORBit-2.so.0
  • #15 CORBA_free
    from /usr/lib/libORBit-2.so.0
  • #16 gnome_accessibility_module_shutdown
    from /usr/lib/gtk-2.0/modules/libatk-bridge.so
  • #17 gnome_accessibility_module_shutdown
    from /usr/lib/gtk-2.0/modules/libatk-bridge.so
  • #18 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #20 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #21 atk_object_notify_state_change
    from /usr/lib/libatk-1.0.so.0
  • #22 vte_terminal_accessible_get_type
    from /usr/lib/libvte.so.9
  • #23 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #25 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #26 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #27 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #28 gtk_widget_get_default_style
    from /usr/lib/libgtk-x11-2.0.so.0
  • #29 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 _gdk_events_init
    from /usr/lib/libgdk-x11-2.0.so.0
  • #31 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #32 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #33 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #34 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #35 ??
  • #36 ??
  • #37 _IO_stdin_used
  • #38 ??
  • #39 ??
  • #0 __kernel_vsyscall

Comment 1 André Klapper 2007-03-17 20:22:32 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 352444 ***