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 422012 - crash in XChat-GNOME IRC Chat: Right clicked on a embed...
crash in XChat-GNOME IRC Chat: Right clicked on a embed...
Status: RESOLVED DUPLICATE of bug 353946
Product: xchat-gnome
Classification: Other
Component: general
0.13
Other All
: High critical
: ---
Assigned To: xchat-gnome maintainers
xchat-gnome maintainers
Depends on:
Blocks:
 
 
Reported: 2007-03-23 20:11 UTC by texanmike
Modified: 2007-03-26 08:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description texanmike 2007-03-23 20:11:34 UTC
What were you doing when the application crashed?
Right clicked on a embedded hyperlink in a topic


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

Memory status: size: 115351552 vsize: 0 resident: 115351552 share: 0 rss: 26804224 rss_rlim: 0
CPU usage: start_time: 1174676711 rtime: 0 utime: 3871 stime: 0 cutime:3655 cstime: 0 timeout: 216 it_real_value: 0 frequency: 0

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

(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 -1226414416 (LWP 6152)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1226414416 (LWP 6152))

  • #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 strlen
    from /lib/tls/i686/cmov/libc.so.6
  • #5 g_strdup
    from /usr/lib/libglib-2.0.so.0
  • #6 g_value_dup_string
    from /usr/lib/libgobject-2.0.so.0
  • #7 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #9 sexy_url_label_set_markup
    from /usr/lib/libsexy.so.2
  • #10 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #15 gtk_widget_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 gtk_menu_shell_activate_item
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 gtk_menu_shell_append
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 gtk_menu_reorder_child
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 g_value_set_boxed
    from /usr/lib/libgobject-2.0.so.0
  • #21 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #22 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #23 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #24 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #25 gtk_widget_get_default_style
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 _gdk_events_init
    from /usr/lib/libgdk-x11-2.0.so.0
  • #29 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #30 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #31 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #32 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #33 fe_main
  • #34 main
  • #0 __kernel_vsyscall

Comment 1 David Trowbridge 2007-03-26 08:51:45 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 353946 ***