Bugzilla – Bug 133267
xchat (from edge) core dumps on startup
Last modified: 2005-11-11 17:09:09 UTC
xchat (on an SL-OSS-edge system) core dumps after selecting the network to connect to. (gdb) where #0 0x4097600f in free () from /lib/libc.so.6 #1 0x424e45ec in PySys_SetArgv () from /opt/gnome/lib/xchat/plugins/python.so #2 0x42476b90 in xchat_plugin_init () from /opt/gnome/lib/xchat/plugins/python.so #3 0x08092fd5 in plugin_add () #4 0x080933e7 in plugin_load () #5 0x08093426 in plugin_load () #6 0x0809c10a in for_files () #7 0x0809319c in plugin_auto_load () #8 0x0809d56f in new_ircwindow () #9 0x0809760f in servlist_connect () #10 0x0806ef90 in search_open () #11 0x4049974b in g_cclosure_marshal_VOID__VOID () from /opt/gnome/lib/libgobject-2.0.so.0 #12 0x4048ca9b in g_closure_invoke () from /opt/gnome/lib/libgobject-2.0.so.0 #13 0x4049d42d in g_signal_connect_closure_by_id () from /opt/gnome/lib/libgobject-2.0.so.0 #14 0x4049e929 in g_signal_emit_valist () from /opt/gnome/lib/libgobject-2.0.so.0 #15 0x4049eae5 in g_signal_emit () from /opt/gnome/lib/libgobject-2.0.so.0 #16 0x40094de1 in gtk_button_clicked () from /opt/gnome/lib/libgtk-x11-2.0.so.0 #17 0x400966e8 in gtk_button_set_alignment () from /opt/gnome/lib/libgtk-x11-2.0.so.0 ---Type <return> to continue, or q <return> to quit--- #18 0x4049974b in g_cclosure_marshal_VOID__VOID () from /opt/gnome/lib/libgobject-2.0.so.0 #19 0x4048b0d7 in g_value_set_static_boxed () from /opt/gnome/lib/libgobject-2.0.so.0 #20 0x4048ca9b in g_closure_invoke () from /opt/gnome/lib/libgobject-2.0.so.0 #21 0x4049d8b8 in g_signal_connect_closure_by_id () from /opt/gnome/lib/libgobject-2.0.so.0 #22 0x4049e929 in g_signal_emit_valist () from /opt/gnome/lib/libgobject-2.0.so.0 #23 0x4049eae5 in g_signal_emit () from /opt/gnome/lib/libgobject-2.0.so.0 #24 0x40094e71 in gtk_button_released () from /opt/gnome/lib/libgtk-x11-2.0.so.0 #25 0x40094edf in gtk_button_released () from /opt/gnome/lib/libgtk-x11-2.0.so.0 #26 0x401639a0 in gtk_marshal_BOOLEAN__VOID () from /opt/gnome/lib/libgtk-x11-2.0.so.0 #27 0x4048b0d7 in g_value_set_static_boxed () from /opt/gnome/lib/libgobject-2.0.so.0 #28 0x4048ca9b in g_closure_invoke () from /opt/gnome/lib/libgobject-2.0.so.0 #29 0x4049da6f in g_signal_connect_closure_by_id () from /opt/gnome/lib/libgobject-2.0.so.0 #30 0x4049e708 in g_signal_emit_valist () from /opt/gnome/lib/libgobject-2.0.so.0 ---Type <return> to continue, or q <return> to quit--- #31 0x4049eae5 in g_signal_emit () from /opt/gnome/lib/libgobject-2.0.so.0 #32 0x4024e244 in gtk_widget_get_default_style () from /opt/gnome/lib/libgtk-x11-2.0.so.0 #33 0x4015d443 in gtk_propagate_event () from /opt/gnome/lib/libgtk-x11-2.0.so.0 #34 0x4015e697 in gtk_main_do_event () from /opt/gnome/lib/libgtk-x11-2.0.so.0 #35 0x4036037a in gdk_add_client_message_filter () from /opt/gnome/lib/libgdk-x11-2.0.so.0 #36 0x408b3aac in g_main_context_dispatch () from /opt/gnome/lib/libglib-2.0.so.0 #37 0x408b6d86 in g_main_context_check () from /opt/gnome/lib/libglib-2.0.so.0 #38 0x408b7147 in g_main_loop_run () from /opt/gnome/lib/libglib-2.0.so.0 #39 0x4015eb11 in gtk_main () from /opt/gnome/lib/libgtk-x11-2.0.so.0 #40 0x0805eabb in fe_main () #41 0x0809e49c in main () (gdb)
Its dumping in python - we have another python plugin bug as well, 131376.
Moving the python maintainer for a look. Marking as major because this could be a wider python issue.
Could you please attach the output of 'rpm -qa | grep python' ?
python-orbit-2.0.1-7 kdebindings3-python-3.4.92-2 python-gnome-extras-2.11.3-6 gstreamer-python-0.8.2-1 python-urlgrabber-2.9.7-3 python-elementtree-1.2.6-4 python-tk-2.4.2-2 python-gtk-2.8.2-3 python-2.4.2-2 libxml2-python-2.6.22-2 python-curses-2.4.2-2 python-sqlite-1.1.6-5 python-devel-2.4.2-2 python-imaging-1.1.5-2 python-xml-2.4.2-2 python-gnome-2.12.0-7 python-numeric-24.0-3 dbus-1-python-0.50-3 rpm-python-4.1.1-228
FWIW, xchat works fine once I clobber /opt/gnome/lib/xchat/plugins/python.so.
It was a bug in python, in patch python-2.4.2-canonicalize2.patch. I just submitted fixed python package.
*** Bug 131376 has been marked as a duplicate of this bug. ***