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 370800 - crash in Terminal: Right clicked on a URL
crash in Terminal: Right clicked on a URL
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-05 00:20 UTC by Seva Epsteyn
Modified: 2006-11-05 04:41 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Seva Epsteyn 2006-11-05 00:20:47 UTC
Version: 2.16.0

What were you doing when the application crashed?
Right clicked on a URL


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

Memory status: size: 66641920 vsize: 0 resident: 66641920 share: 0 rss: 15753216 rss_rlim: 0
CPU usage: start_time: 1162597668 rtime: 0 utime: 512 stime: 0 cutime:470 cstime: 0 timeout: 42 it_real_value: 0 frequency: 2

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 -1208903984 (LWP 3066)]
[New Thread -1215755376 (LWP 3071)]
(no debugging symbols found)
0x00461402 in __kernel_vsyscall ()

Thread 1 (Thread -1208903984 (LWP 3066))

  • #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_box_pack_start_defaults
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 gtk_container_forall
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 gtk_widget_set_usize
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 gtk_button_box_set_child_size
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 gtk_container_forall
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 gtk_widget_set_usize
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 gtk_notebook_popup_enable
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 gtk_container_forall
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 gtk_widget_set_usize
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 gtk_box_pack_start_defaults
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 gtk_container_forall
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 gtk_widget_set_usize
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 gtk_button_box_set_child_size
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 gtk_container_forall
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 gtk_widget_set_usize
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 gtk_widget_reset_rc_styles
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 gtk_rc_get_module_dir
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 gtk_icon_info_get_type
    from /usr/lib/libgtk-x11-2.0.so.0
  • #29 g_source_is_destroyed
    from /lib/libglib-2.0.so.0
  • #30 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #31 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #32 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #33 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #34 g_cclosure_marshal_VOID__OBJECT
  • #35 __libc_start_main
    from /lib/libc.so.6
  • #36 g_cclosure_marshal_VOID__OBJECT
  • #0 __kernel_vsyscall

Comment 1 Karsten Bräckelmann 2006-11-05 04:41:20 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 ***