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 378719 - crash in Terminal: running a mono network p...
crash in Terminal: running a mono network p...
Status: RESOLVED DUPLICATE of bug 348979
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: 2006-11-24 04:59 UTC by Tao Wang
Modified: 2006-11-24 05:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Tao Wang 2006-11-24 04:59:56 UTC 
Version: 2.16.0

What were you doing when the application crashed?
running a mono network program.


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.18-1.2849.fc6 #1 SMP Fri Nov 10 12:45:28 EST 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled
----------- .xsession-errors (19586 sec old) ---------------------
** 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
** 
...Too much output, ignoring rest...
--------------------------------------------------

Memory status: size: 156389376 vsize: 0 resident: 156389376 share: 0 rss: 19365888 rss_rlim: 0
CPU usage: start_time: 1164323411 rtime: 0 utime: 1440 stime: 0 cutime:900 cstime: 0 timeout: 540 it_real_value: 0 frequency: 114

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

(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 -1208781104 (LWP 3360)]
[New Thread -1255605360 (LWP 3515)]
(no debugging symbols found)
0x00536402 in __kernel_vsyscall ()

+ Trace 88954

Thread 1 (Thread -1208781104 (LWP 3360))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_type_check_is_value_type
    from /lib/libgobject-2.0.so.0
  • #5 g_value_type_compatible
    from /lib/libgobject-2.0.so.0
  • #6 g_object_class_override_property
    from /lib/libgobject-2.0.so.0
  • #7 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #8 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #9 gtk_widget_set_usize
    from /usr/lib/libgtk-x11-2.0.so.0
  • #10 gtk_widget_set_usize
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 gtk_widget_reset_rc_styles
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 gtk_rc_get_module_dir
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 gtk_icon_info_get_type
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 g_source_is_destroyed
    from /lib/libglib-2.0.so.0
  • #15 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #16 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #17 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #18 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 g_cclosure_marshal_VOID__OBJECT
  • #20 __libc_start_main
    from /lib/libc.so.6
  • #21 g_cclosure_marshal_VOID__OBJECT
  • #0 __kernel_vsyscall 






Comment 1


Mariano Suárez-Alvarez





          2006-11-24 05:03:00 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 348979 ***