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 369167 - crash in XChat-GNOME IRC Chat: Trying to edit an irc se...
crash in XChat-GNOME IRC Chat: Trying to edit an irc se...
Status: RESOLVED DUPLICATE of bug 359167
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: 2006-11-02 00:43 UTC by jvitosky
Modified: 2006-11-02 00:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description jvitosky 2006-11-02 00:43:45 UTC
What were you doing when the application crashed?
Trying to edit an irc server in xchat-gnome


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

Memory status: size: 106844160 vsize: 0 resident: 106844160 share: 0 rss: 19759104 rss_rlim: 0
CPU usage: start_time: 1162427664 rtime: 0 utime: 926 stime: 0 cutime:862 cstime: 0 timeout: 64 it_real_value: 0 frequency: 3

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

Thread 1 (Thread -1226840400 (LWP 5912))

  • #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 navigation_model_get_server
  • #5 irc_network_save
  • #6 irc_network_editor_new
  • #7 g_cclosure_marshal_VOID
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_value_set_boxed
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #13 gtk_dialog_response
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 gtk_dialog_response
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 g_cclosure_marshal_VOID__VOID
    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_button_clicked
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 gtk_button_set_alignment
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 gtk_button_set_alignment
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 g_value_set_boxed
    from /usr/lib/libgobject-2.0.so.0
  • #25 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #26 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #27 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #28 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #29 gtk_widget_get_default_style
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #31 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #32 _gdk_events_init
    from /usr/lib/libgdk-x11-2.0.so.0
  • #33 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #34 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #35 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #36 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #37 fe_main
  • #38 main
  • #0 __kernel_vsyscall

Comment 1 David Trowbridge 2006-11-02 00:54:34 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 359167 ***