Bugs item #1349761, was opened at 2005-11-06 14:58
Message generated for change (Comment added) made by nobody
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=604306&aid=1349761&group_id=93438
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Other
Group: Linux
Status: Open
Resolution: None
Priority: 5
Submitted By: Jure Cuhalev (gandalfar)
Assigned to: Nobody/Anonymous (nobody)
Summary: Inkboard: inkscape crashes when trying to connect
Initial Comment:
I grabbed and compiled latest cvs (6th of Nov) on Ubuntu Breezy. I'
m trying to connect to my jabber server (amessage.info). I enter
details: username, pass, servername and click connect. After a
few moments I get the following crash:
(gdb) run
Starting program: /usr/local/bin/inkscape
[Thread debugging using libthread_db enabled]
[New Thread -1224575296 (LWP 1567)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1224575296 (LWP 1567)]
0xb73cdcfb in g_source_get_current_time () from /usr/lib/libglib-2.
0.so.0
(gdb) bt
#0 0xb73cdcfb in g_source_get_current_time () from /usr/lib/libglib
-2.0.so.0
#1 0xb742f1ee in lm_connection_is_open () from /usr/lib/
libloudmouth-1.so.0
#2 0xb742f30e in lm_connection_is_open () from /usr/lib/
libloudmouth-1.so.0
#3 0xb73f531c in g_vasprintf () from /usr/lib/libglib-2.0.so.0
#4 0xb73ce4ee in g_main_context_dispatch () from /usr/lib/libglib-
2.0.so.0
#5 0xb73d14f6 in g_main_context_check () from /usr/lib/libglib-2.
0.so.0
#6 0xb73d19d8 in g_main_context_iteration () from /usr/lib/libglib-
2.0.so.0
#7 0xb743110f in lm_connection_send_with_reply_and_block ()
from /usr/lib/libloudmouth-1.so.0
#8 0xb74312bc in lm_connection_authenticate_and_block () from
/usr/lib/libloudmouth-1.so.0
#9 0x0820996d in Inkscape::Whiteboard::SessionManager::
connectToServer (this=0x8701cb0, server=@0xbf870f74, port=@0
xbf870f70, username=@0xbf870f6c,
pw=@0xbf870f68, usessl=false) at jabber_whiteboard/session-
manager.cpp:243
#10 0x0818ca8a in Inkscape::UI::Dialog::
WhiteboardConnectDialogImpl::_respCallback (this=0x8eb29c8,
resp=-5) at ui/dialog/whiteboard-connect.cpp:129
#11 0x0818d690 in sigc::internal::slot_call0<sigc::bind_functor<0,
sigc::bound_mem_functor1<void, Inkscape::UI::Dialog::
WhiteboardConnectDialogImpl, int>, GtkResponseType, sigc::nil,
sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil>, void>::call_it (rep=0
x928e3c8) at mem_fun.h:1839
#12 0xb7bf73a6 in Glib::SignalProxyNormal::slot0_void_callback ()
from /usr/lib/libglibmm-2.4.so.1
#13 0xb74d0ab3 in g_cclosure_marshal_VOID__VOID () from /usr/
lib/libgobject-2.0.so.0
#14 0xb74c53a8 in g_closure_invoke () from /usr/lib/libgobject-2.0.
so.0
#15 0xb74d3e8d in g_signal_stop_emission () from /usr/lib/
libgobject-2.0.so.0
#16 0xb74d5150 in g_signal_emit_valist () from /usr/lib/libgobject-
2.0.so.0
#17 0xb74d54c3 in g_signal_emit () from /usr/lib/libgobject-2.0.so.
0
#18 0xb794c22c in gtk_button_clicked () from /usr/lib/libgtk-x11-2.
0.so.0
#19 0xb794da4c in _gtk_button_set_depressed () from /usr/lib/
libgtk-x11-2.0.so.0
#20 0xb7df4832 in Gtk::Button_Class::released_callback () from /
usr/lib/libgtkmm-2.4.so.1
#21 0xb74d0ab3 in g_cclosure_marshal_VOID__VOID () from /usr/
lib/libgobject-2.0.so.0
#22 0xb74c4d75 in g_cclosure_new_swap () from /usr/lib/libgobject
-2.0.so.0
#23 0xb74c53a8 in g_closure_invoke () from /usr/lib/libgobject-2.0.
so.0
#24 0xb74d3769 in g_signal_stop_emission () from /usr/lib/
libgobject-2.0.so.0
#25 0xb74d5150 in g_signal_emit_valist () from /usr/lib/libgobject-
2.0.so.0
#26 0xb74d54c3 in g_signal_emit () from /usr/lib/libgobject-2.0.so.
0
#27 0xb794c1a6 in gtk_button_released () from /usr/lib/libgtk-x11-
2.0.so.0
#28 0xb794d115 in _gtk_button_paint () from /usr/lib/libgtk-x11-2.0.
so.0
#29 0xb7e8b429 in Gtk::Widget_Class::button_release_event_
callback () from /usr/lib/libgtkmm-2.4.so.1
#30 0xb7a0d02c in _gtk_marshal_BOOLEAN__BOXED () from /usr
/lib/libgtk-x11-2.0.so.0
#31 0xb74c4d75 in g_cclosure_new_swap () from /usr/lib/libgobject
-2.0.so.0
#32 0xb74c53a8 in g_closure_invoke () from /usr/lib/libgobject-2.0.
so.0
#33 0xb74d3c9f in g_signal_stop_emission () from /usr/lib/
libgobject-2.0.so.0
#34 0xb74d4ec3 in g_signal_emit_valist () from /usr/lib/libgobject-
2.0.so.0
#35 0xb74d54c3 in g_signal_emit () from /usr/lib/libgobject-2.0.so.
0
#36 0xb7aef16f in gtk_widget_activate () from /usr/lib/libgtk-x11-2.
0.so.0
#37 0xb7a0b767 in gtk_propagate_event () from /usr/lib/libgtk-x11-
2.0.so.0
#38 0xb7a0bba0 in gtk_main_do_event () from /usr/lib/libgtk-x11-2.
0.so.0
#39 0xb78afb2d in _gdk_events_queue () from /usr/lib/libgdk-x11-2.
0.so.0
#40 0xb73ce4ee in g_main_context_dispatch () from /usr/lib/libglib-
2.0.so.0
#41 0xb73d14f6 in g_main_context_check () from /usr/lib/libglib-2.
0.so.0
#42 0xb73d17e3 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#43 0xb7a0ae65 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#44 0xb7e31c95 in Gtk::Main::run_impl () from /usr/lib/libgtkmm-2.
4.so.1
#45 0xb7e31b86 in Gtk::Main::run () from /usr/lib/libgtkmm-2.4.so.
1
#46 0x0806c9e1 in sp_main_gui (argc=1, argv=0xbf872174) at
main.cpp:834
#47 0x0815c270 in Inkscape::NSApplication::Application::run (this
=0xbf8720bc) at application/application.cpp:128
#48 0x0806c299 in main (argc=1, argv=0xbf872174) at main.cpp:
6690806c299 in main (argc=1, argv=0xbf872174) at main.cpp:669
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2005-11-17 21:09
Message:
Logged In: NO
Okay. I've finally had some time to poke at this issue, and
there's three things I can think of that might be causing this:
(1) This is a Loudmouth bug of some sort. I don't know if
this is true or not, but nothing in the Inkboard code itself
is popping out at me as being obviously wrong, nor do any
values being passed to Loudmouth look suspect.
(2) I'm not carrying out Loudmouth's SSL initialization
properly, which is causing the library to crash in some way.
However, SSL works on other servers (like gristle.org), so
I'm not sure if this is it.
(3) Something totally different :p
I'll keep poking at this. However, a switch to a different
Jabber client is in the works, so that very well may fix
this problem.
----------------------------------------------------------------------
Comment By: Peter J. R. Moulder (pjrm)
Date: 2005-11-08 01:03
Message:
Logged In: YES
user_id=827826
Please don't assume that the remote jabber server/client is
sending valid data. E.g. if bad data can cause a program to
crash, then there's a fair chance that malicious bad data
can do harm such as causing the program to execute arbitrary
code.
----------------------------------------------------------------------
Comment By: David Yip (dwyip)
Date: 2005-11-07 21:12
Message:
Logged In: YES
user_id=586161
Give me a day or two to get some project work out of the
way, and I'll take a look at this. There's probably some
variation in Jabber login protocol that I didn't account for.
In the meantime, do you have access to a copy of Ethereal or
similar packet sniffing tool that can export to tcpdump? If
so, can you create a test account on amessage.info, record a
login session on that test account, and attach it here? I
can compare it to "known good" servers and see if I'm
missing anything.
----------------------------------------------------------------------
Comment By: Alexandre Prokoudine (prokoudine)
Date: 2005-11-07 16:23
Message:
Logged In: YES
user_id=597819
Same sad story with my jabber.ru account I got used to
----------------------------------------------------------------------
Comment By: Jure Cuhalev (gandalfar)
Date: 2005-11-06 15:21
Message:
Logged In: YES
user_id=675570
Additional bit of info:
this happens only with my 'amessage.info' account. It works with 'gristle.
org' account.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=604306&aid=1349761&group_id=93438

Bugs item #1349761, was opened at 2005-11-06 15:58
Message generated for change (Comment added) made by dwyip
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=604306&aid=1349761&group_id=93438
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Other
Group: Linux
Status: Open
Resolution: None
Priority: 5
Submitted By: Jure Cuhalev (gandalfar)
Assigned to: Nobody/Anonymous (nobody)
Summary: Inkboard: inkscape crashes when trying to connect
Initial Comment:
I grabbed and compiled latest cvs (6th of Nov) on Ubuntu Breezy. I'
m trying to connect to my jabber server (amessage.info). I enter
details: username, pass, servername and click connect. After a
few moments I get the following crash:
(gdb) run
Starting program: /usr/local/bin/inkscape
[Thread debugging using libthread_db enabled]
[New Thread -1224575296 (LWP 1567)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1224575296 (LWP 1567)]
0xb73cdcfb in g_source_get_current_time () from /usr/lib/libglib-2.
0.so.0
(gdb) bt
#0 0xb73cdcfb in g_source_get_current_time () from /usr/lib/libglib
-2.0.so.0
#1 0xb742f1ee in lm_connection_is_open () from /usr/lib/
libloudmouth-1.so.0
#2 0xb742f30e in lm_connection_is_open () from /usr/lib/
libloudmouth-1.so.0
#3 0xb73f531c in g_vasprintf () from /usr/lib/libglib-2.0.so.0
#4 0xb73ce4ee in g_main_context_dispatch () from /usr/lib/libglib-
2.0.so.0
#5 0xb73d14f6 in g_main_context_check () from /usr/lib/libglib-2.
0.so.0
#6 0xb73d19d8 in g_main_context_iteration () from /usr/lib/libglib-
2.0.so.0
#7 0xb743110f in lm_connection_send_with_reply_and_block ()
from /usr/lib/libloudmouth-1.so.0
#8 0xb74312bc in lm_connection_authenticate_and_block () from
/usr/lib/libloudmouth-1.so.0
#9 0x0820996d in Inkscape::Whiteboard::SessionManager::
connectToServer (this=0x8701cb0, server=@0xbf870f74, port=@0
xbf870f70, username=@0xbf870f6c,
pw=@0xbf870f68, usessl=false) at jabber_whiteboard/session-
manager.cpp:243
#10 0x0818ca8a in Inkscape::UI::Dialog::
WhiteboardConnectDialogImpl::_respCallback (this=0x8eb29c8,
resp=-5) at ui/dialog/whiteboard-connect.cpp:129
#11 0x0818d690 in sigc::internal::slot_call0<sigc::bind_functor<0,
sigc::bound_mem_functor1<void, Inkscape::UI::Dialog::
WhiteboardConnectDialogImpl, int>, GtkResponseType, sigc::nil,
sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil>, void>::call_it (rep=0
x928e3c8) at mem_fun.h:1839
#12 0xb7bf73a6 in Glib::SignalProxyNormal::slot0_void_callback ()
from /usr/lib/libglibmm-2.4.so.1
#13 0xb74d0ab3 in g_cclosure_marshal_VOID__VOID () from /usr/
lib/libgobject-2.0.so.0
#14 0xb74c53a8 in g_closure_invoke () from /usr/lib/libgobject-2.0.
so.0
#15 0xb74d3e8d in g_signal_stop_emission () from /usr/lib/
libgobject-2.0.so.0
#16 0xb74d5150 in g_signal_emit_valist () from /usr/lib/libgobject-
2.0.so.0
#17 0xb74d54c3 in g_signal_emit () from /usr/lib/libgobject-2.0.so.
0
#18 0xb794c22c in gtk_button_clicked () from /usr/lib/libgtk-x11-2.
0.so.0
#19 0xb794da4c in _gtk_button_set_depressed () from /usr/lib/
libgtk-x11-2.0.so.0
#20 0xb7df4832 in Gtk::Button_Class::released_callback () from /
usr/lib/libgtkmm-2.4.so.1
#21 0xb74d0ab3 in g_cclosure_marshal_VOID__VOID () from /usr/
lib/libgobject-2.0.so.0
#22 0xb74c4d75 in g_cclosure_new_swap () from /usr/lib/libgobject
-2.0.so.0
#23 0xb74c53a8 in g_closure_invoke () from /usr/lib/libgobject-2.0.
so.0
#24 0xb74d3769 in g_signal_stop_emission () from /usr/lib/
libgobject-2.0.so.0
#25 0xb74d5150 in g_signal_emit_valist () from /usr/lib/libgobject-
2.0.so.0
#26 0xb74d54c3 in g_signal_emit () from /usr/lib/libgobject-2.0.so.
0
#27 0xb794c1a6 in gtk_button_released () from /usr/lib/libgtk-x11-
2.0.so.0
#28 0xb794d115 in _gtk_button_paint () from /usr/lib/libgtk-x11-2.0.
so.0
#29 0xb7e8b429 in Gtk::Widget_Class::button_release_event_
callback () from /usr/lib/libgtkmm-2.4.so.1
#30 0xb7a0d02c in _gtk_marshal_BOOLEAN__BOXED () from /usr
/lib/libgtk-x11-2.0.so.0
#31 0xb74c4d75 in g_cclosure_new_swap () from /usr/lib/libgobject
-2.0.so.0
#32 0xb74c53a8 in g_closure_invoke () from /usr/lib/libgobject-2.0.
so.0
#33 0xb74d3c9f in g_signal_stop_emission () from /usr/lib/
libgobject-2.0.so.0
#34 0xb74d4ec3 in g_signal_emit_valist () from /usr/lib/libgobject-
2.0.so.0
#35 0xb74d54c3 in g_signal_emit () from /usr/lib/libgobject-2.0.so.
0
#36 0xb7aef16f in gtk_widget_activate () from /usr/lib/libgtk-x11-2.
0.so.0
#37 0xb7a0b767 in gtk_propagate_event () from /usr/lib/libgtk-x11-
2.0.so.0
#38 0xb7a0bba0 in gtk_main_do_event () from /usr/lib/libgtk-x11-2.
0.so.0
#39 0xb78afb2d in _gdk_events_queue () from /usr/lib/libgdk-x11-2.
0.so.0
#40 0xb73ce4ee in g_main_context_dispatch () from /usr/lib/libglib-
2.0.so.0
#41 0xb73d14f6 in g_main_context_check () from /usr/lib/libglib-2.
0.so.0
#42 0xb73d17e3 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#43 0xb7a0ae65 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#44 0xb7e31c95 in Gtk::Main::run_impl () from /usr/lib/libgtkmm-2.
4.so.1
#45 0xb7e31b86 in Gtk::Main::run () from /usr/lib/libgtkmm-2.4.so.
1
#46 0x0806c9e1 in sp_main_gui (argc=1, argv=0xbf872174) at
main.cpp:834
#47 0x0815c270 in Inkscape::NSApplication::Application::run (this
=0xbf8720bc) at application/application.cpp:128
#48 0x0806c299 in main (argc=1, argv=0xbf872174) at main.cpp:
6690806c299 in main (argc=1, argv=0xbf872174) at main.cpp:669
----------------------------------------------------------------------
Comment By: David Yip (dwyip)
Date: 2005-11-17 22:12
Message:
Logged In: YES
user_id=586161
Sorry, that last comment was me forgetting to log in.
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2005-11-17 22:09
Message:
Logged In: NO
Okay. I've finally had some time to poke at this issue, and
there's three things I can think of that might be causing this:
(1) This is a Loudmouth bug of some sort. I don't know if
this is true or not, but nothing in the Inkboard code itself
is popping out at me as being obviously wrong, nor do any
values being passed to Loudmouth look suspect.
(2) I'm not carrying out Loudmouth's SSL initialization
properly, which is causing the library to crash in some way.
However, SSL works on other servers (like gristle.org), so
I'm not sure if this is it.
(3) Something totally different :p
I'll keep poking at this. However, a switch to a different
Jabber client is in the works, so that very well may fix
this problem.
----------------------------------------------------------------------
Comment By: Peter J. R. Moulder (pjrm)
Date: 2005-11-08 02:03
Message:
Logged In: YES
user_id=827826
Please don't assume that the remote jabber server/client is
sending valid data. E.g. if bad data can cause a program to
crash, then there's a fair chance that malicious bad data
can do harm such as causing the program to execute arbitrary
code.
----------------------------------------------------------------------
Comment By: David Yip (dwyip)
Date: 2005-11-07 22:12
Message:
Logged In: YES
user_id=586161
Give me a day or two to get some project work out of the
way, and I'll take a look at this. There's probably some
variation in Jabber login protocol that I didn't account for.
In the meantime, do you have access to a copy of Ethereal or
similar packet sniffing tool that can export to tcpdump? If
so, can you create a test account on amessage.info, record a
login session on that test account, and attach it here? I
can compare it to "known good" servers and see if I'm
missing anything.
----------------------------------------------------------------------
Comment By: Alexandre Prokoudine (prokoudine)
Date: 2005-11-07 17:23
Message:
Logged In: YES
user_id=597819
Same sad story with my jabber.ru account I got used to
----------------------------------------------------------------------
Comment By: Jure Cuhalev (gandalfar)
Date: 2005-11-06 16:21
Message:
Logged In: YES
user_id=675570
Additional bit of info:
this happens only with my 'amessage.info' account. It works with 'gristle.
org' account.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=604306&aid=1349761&group_id=93438

Bugs item #1349761, was opened at 2005-11-07 09:58
Message generated for change (Comment added) made by pjrm
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=604306&aid=1349761&group_id=93438
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Other
Group: Linux
Status: Open
Resolution: None
>Priority: 8
Submitted By: Jure Cuhalev (gandalfar)
Assigned to: Nobody/Anonymous (nobody)
Summary: Inkboard: inkscape crashes when trying to connect
Initial Comment:
I grabbed and compiled latest cvs (6th of Nov) on Ubuntu Breezy. I'
m trying to connect to my jabber server (amessage.info). I enter
details: username, pass, servername and click connect. After a
few moments I get the following crash:
(gdb) run
Starting program: /usr/local/bin/inkscape
[Thread debugging using libthread_db enabled]
[New Thread -1224575296 (LWP 1567)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1224575296 (LWP 1567)]
0xb73cdcfb in g_source_get_current_time () from /usr/lib/libglib-2.
0.so.0
(gdb) bt
#0 0xb73cdcfb in g_source_get_current_time () from /usr/lib/libglib
-2.0.so.0
#1 0xb742f1ee in lm_connection_is_open () from /usr/lib/
libloudmouth-1.so.0
#2 0xb742f30e in lm_connection_is_open () from /usr/lib/
libloudmouth-1.so.0
#3 0xb73f531c in g_vasprintf () from /usr/lib/libglib-2.0.so.0
#4 0xb73ce4ee in g_main_context_dispatch () from /usr/lib/libglib-
2.0.so.0
#5 0xb73d14f6 in g_main_context_check () from /usr/lib/libglib-2.
0.so.0
#6 0xb73d19d8 in g_main_context_iteration () from /usr/lib/libglib-
2.0.so.0
#7 0xb743110f in lm_connection_send_with_reply_and_block ()
from /usr/lib/libloudmouth-1.so.0
#8 0xb74312bc in lm_connection_authenticate_and_block () from
/usr/lib/libloudmouth-1.so.0
#9 0x0820996d in Inkscape::Whiteboard::SessionManager::
connectToServer (this=0x8701cb0, server=@0xbf870f74, port=@0
xbf870f70, username=@0xbf870f6c,
pw=@0xbf870f68, usessl=false) at jabber_whiteboard/session-
manager.cpp:243
#10 0x0818ca8a in Inkscape::UI::Dialog::
WhiteboardConnectDialogImpl::_respCallback (this=0x8eb29c8,
resp=-5) at ui/dialog/whiteboard-connect.cpp:129
#11 0x0818d690 in sigc::internal::slot_call0<sigc::bind_functor<0,
sigc::bound_mem_functor1<void, Inkscape::UI::Dialog::
WhiteboardConnectDialogImpl, int>, GtkResponseType, sigc::nil,
sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil>, void>::call_it (rep=0
x928e3c8) at mem_fun.h:1839
#12 0xb7bf73a6 in Glib::SignalProxyNormal::slot0_void_callback ()
from /usr/lib/libglibmm-2.4.so.1
#13 0xb74d0ab3 in g_cclosure_marshal_VOID__VOID () from /usr/
lib/libgobject-2.0.so.0
#14 0xb74c53a8 in g_closure_invoke () from /usr/lib/libgobject-2.0.
so.0
#15 0xb74d3e8d in g_signal_stop_emission () from /usr/lib/
libgobject-2.0.so.0
#16 0xb74d5150 in g_signal_emit_valist () from /usr/lib/libgobject-
2.0.so.0
#17 0xb74d54c3 in g_signal_emit () from /usr/lib/libgobject-2.0.so.
0
#18 0xb794c22c in gtk_button_clicked () from /usr/lib/libgtk-x11-2.
0.so.0
#19 0xb794da4c in _gtk_button_set_depressed () from /usr/lib/
libgtk-x11-2.0.so.0
#20 0xb7df4832 in Gtk::Button_Class::released_callback () from /
usr/lib/libgtkmm-2.4.so.1
#21 0xb74d0ab3 in g_cclosure_marshal_VOID__VOID () from /usr/
lib/libgobject-2.0.so.0
#22 0xb74c4d75 in g_cclosure_new_swap () from /usr/lib/libgobject
-2.0.so.0
#23 0xb74c53a8 in g_closure_invoke () from /usr/lib/libgobject-2.0.
so.0
#24 0xb74d3769 in g_signal_stop_emission () from /usr/lib/
libgobject-2.0.so.0
#25 0xb74d5150 in g_signal_emit_valist () from /usr/lib/libgobject-
2.0.so.0
#26 0xb74d54c3 in g_signal_emit () from /usr/lib/libgobject-2.0.so.
0
#27 0xb794c1a6 in gtk_button_released () from /usr/lib/libgtk-x11-
2.0.so.0
#28 0xb794d115 in _gtk_button_paint () from /usr/lib/libgtk-x11-2.0.
so.0
#29 0xb7e8b429 in Gtk::Widget_Class::button_release_event_
callback () from /usr/lib/libgtkmm-2.4.so.1
#30 0xb7a0d02c in _gtk_marshal_BOOLEAN__BOXED () from /usr
/lib/libgtk-x11-2.0.so.0
#31 0xb74c4d75 in g_cclosure_new_swap () from /usr/lib/libgobject
-2.0.so.0
#32 0xb74c53a8 in g_closure_invoke () from /usr/lib/libgobject-2.0.
so.0
#33 0xb74d3c9f in g_signal_stop_emission () from /usr/lib/
libgobject-2.0.so.0
#34 0xb74d4ec3 in g_signal_emit_valist () from /usr/lib/libgobject-
2.0.so.0
#35 0xb74d54c3 in g_signal_emit () from /usr/lib/libgobject-2.0.so.
0
#36 0xb7aef16f in gtk_widget_activate () from /usr/lib/libgtk-x11-2.
0.so.0
#37 0xb7a0b767 in gtk_propagate_event () from /usr/lib/libgtk-x11-
2.0.so.0
#38 0xb7a0bba0 in gtk_main_do_event () from /usr/lib/libgtk-x11-2.
0.so.0
#39 0xb78afb2d in _gdk_events_queue () from /usr/lib/libgdk-x11-2.
0.so.0
#40 0xb73ce4ee in g_main_context_dispatch () from /usr/lib/libglib-
2.0.so.0
#41 0xb73d14f6 in g_main_context_check () from /usr/lib/libglib-2.
0.so.0
#42 0xb73d17e3 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#43 0xb7a0ae65 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#44 0xb7e31c95 in Gtk::Main::run_impl () from /usr/lib/libgtkmm-2.
4.so.1
#45 0xb7e31b86 in Gtk::Main::run () from /usr/lib/libgtkmm-2.4.so.
1
#46 0x0806c9e1 in sp_main_gui (argc=1, argv=0xbf872174) at
main.cpp:834
#47 0x0815c270 in Inkscape::NSApplication::Application::run (this
=0xbf8720bc) at application/application.cpp:128
#48 0x0806c299 in main (argc=1, argv=0xbf872174) at main.cpp:
6690806c299 in main (argc=1, argv=0xbf872174) at main.cpp:669
----------------------------------------------------------------------
>Comment By: Peter J. R. Moulder (pjrm)
Date: 2005-11-24 21:09
Message:
Logged In: YES
user_id=827826
I suggest grabbing the source for libloudmouth, compiling it
with CFLAGS=-g, and linking against that version for running
gdb on it: that should give a better idea as to why it's
crashing, e.g. you can see the exact line, and you can see
what data it's using that causes it to crash. Might give a
clue as to what code is at fault and how to correct it.
Filing a bug against libloudmouth may well be useful.
Including information you've found from gdb makes it more
likely to get the problem sorted quickly.
----------------------------------------------------------------------
Comment By: David Yip (dwyip)
Date: 2005-11-18 16:12
Message:
Logged In: YES
user_id=586161
Sorry, that last comment was me forgetting to log in.
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2005-11-18 16:09
Message:
Logged In: NO
Okay. I've finally had some time to poke at this issue, and
there's three things I can think of that might be causing this:
(1) This is a Loudmouth bug of some sort. I don't know if
this is true or not, but nothing in the Inkboard code itself
is popping out at me as being obviously wrong, nor do any
values being passed to Loudmouth look suspect.
(2) I'm not carrying out Loudmouth's SSL initialization
properly, which is causing the library to crash in some way.
However, SSL works on other servers (like gristle.org), so
I'm not sure if this is it.
(3) Something totally different :p
I'll keep poking at this. However, a switch to a different
Jabber client is in the works, so that very well may fix
this problem.
----------------------------------------------------------------------
Comment By: Peter J. R. Moulder (pjrm)
Date: 2005-11-08 20:03
Message:
Logged In: YES
user_id=827826
Please don't assume that the remote jabber server/client is
sending valid data. E.g. if bad data can cause a program to
crash, then there's a fair chance that malicious bad data
can do harm such as causing the program to execute arbitrary
code.
----------------------------------------------------------------------
Comment By: David Yip (dwyip)
Date: 2005-11-08 16:12
Message:
Logged In: YES
user_id=586161
Give me a day or two to get some project work out of the
way, and I'll take a look at this. There's probably some
variation in Jabber login protocol that I didn't account for.
In the meantime, do you have access to a copy of Ethereal or
similar packet sniffing tool that can export to tcpdump? If
so, can you create a test account on amessage.info, record a
login session on that test account, and attach it here? I
can compare it to "known good" servers and see if I'm
missing anything.
----------------------------------------------------------------------
Comment By: Alexandre Prokoudine (prokoudine)
Date: 2005-11-08 11:23
Message:
Logged In: YES
user_id=597819
Same sad story with my jabber.ru account I got used to
----------------------------------------------------------------------
Comment By: Jure Cuhalev (gandalfar)
Date: 2005-11-07 10:21
Message:
Logged In: YES
user_id=675570
Additional bit of info:
this happens only with my 'amessage.info' account. It works with 'gristle.
org' account.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=604306&aid=1349761&group_id=93438

Bugs item #1349761, was opened at 2005-11-06 14:58
Message generated for change (Comment added) made by bryce
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=604306&aid=1349761&group_id=93438
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Other
Group: Linux
Status: Open
Resolution: None
>Priority: 9
Submitted By: Jure Cuhalev (gandalfar)
Assigned to: Nobody/Anonymous (nobody)
Summary: Inkboard: inkscape crashes when trying to connect
Initial Comment:
I grabbed and compiled latest cvs (6th of Nov) on Ubuntu Breezy. I'
m trying to connect to my jabber server (amessage.info). I enter
details: username, pass, servername and click connect. After a
few moments I get the following crash:
(gdb) run
Starting program: /usr/local/bin/inkscape
[Thread debugging using libthread_db enabled]
[New Thread -1224575296 (LWP 1567)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1224575296 (LWP 1567)]
0xb73cdcfb in g_source_get_current_time () from /usr/lib/libglib-2.
0.so.0
(gdb) bt
#0 0xb73cdcfb in g_source_get_current_time () from /usr/lib/libglib
-2.0.so.0
#1 0xb742f1ee in lm_connection_is_open () from /usr/lib/
libloudmouth-1.so.0
#2 0xb742f30e in lm_connection_is_open () from /usr/lib/
libloudmouth-1.so.0
#3 0xb73f531c in g_vasprintf () from /usr/lib/libglib-2.0.so.0
#4 0xb73ce4ee in g_main_context_dispatch () from /usr/lib/libglib-
2.0.so.0
#5 0xb73d14f6 in g_main_context_check () from /usr/lib/libglib-2.
0.so.0
#6 0xb73d19d8 in g_main_context_iteration () from /usr/lib/libglib-
2.0.so.0
#7 0xb743110f in lm_connection_send_with_reply_and_block ()
from /usr/lib/libloudmouth-1.so.0
#8 0xb74312bc in lm_connection_authenticate_and_block () from
/usr/lib/libloudmouth-1.so.0
#9 0x0820996d in Inkscape::Whiteboard::SessionManager::
connectToServer (this=0x8701cb0, server=@0xbf870f74, port=@0
xbf870f70, username=@0xbf870f6c,
pw=@0xbf870f68, usessl=false) at jabber_whiteboard/session-
manager.cpp:243
#10 0x0818ca8a in Inkscape::UI::Dialog::
WhiteboardConnectDialogImpl::_respCallback (this=0x8eb29c8,
resp=-5) at ui/dialog/whiteboard-connect.cpp:129
#11 0x0818d690 in sigc::internal::slot_call0<sigc::bind_functor<0,
sigc::bound_mem_functor1<void, Inkscape::UI::Dialog::
WhiteboardConnectDialogImpl, int>, GtkResponseType, sigc::nil,
sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil>, void>::call_it (rep=0
x928e3c8) at mem_fun.h:1839
#12 0xb7bf73a6 in Glib::SignalProxyNormal::slot0_void_callback ()
from /usr/lib/libglibmm-2.4.so.1
#13 0xb74d0ab3 in g_cclosure_marshal_VOID__VOID () from /usr/
lib/libgobject-2.0.so.0
#14 0xb74c53a8 in g_closure_invoke () from /usr/lib/libgobject-2.0.
so.0
#15 0xb74d3e8d in g_signal_stop_emission () from /usr/lib/
libgobject-2.0.so.0
#16 0xb74d5150 in g_signal_emit_valist () from /usr/lib/libgobject-
2.0.so.0
#17 0xb74d54c3 in g_signal_emit () from /usr/lib/libgobject-2.0.so.
0
#18 0xb794c22c in gtk_button_clicked () from /usr/lib/libgtk-x11-2.
0.so.0
#19 0xb794da4c in _gtk_button_set_depressed () from /usr/lib/
libgtk-x11-2.0.so.0
#20 0xb7df4832 in Gtk::Button_Class::released_callback () from /
usr/lib/libgtkmm-2.4.so.1
#21 0xb74d0ab3 in g_cclosure_marshal_VOID__VOID () from /usr/
lib/libgobject-2.0.so.0
#22 0xb74c4d75 in g_cclosure_new_swap () from /usr/lib/libgobject
-2.0.so.0
#23 0xb74c53a8 in g_closure_invoke () from /usr/lib/libgobject-2.0.
so.0
#24 0xb74d3769 in g_signal_stop_emission () from /usr/lib/
libgobject-2.0.so.0
#25 0xb74d5150 in g_signal_emit_valist () from /usr/lib/libgobject-
2.0.so.0
#26 0xb74d54c3 in g_signal_emit () from /usr/lib/libgobject-2.0.so.
0
#27 0xb794c1a6 in gtk_button_released () from /usr/lib/libgtk-x11-
2.0.so.0
#28 0xb794d115 in _gtk_button_paint () from /usr/lib/libgtk-x11-2.0.
so.0
#29 0xb7e8b429 in Gtk::Widget_Class::button_release_event_
callback () from /usr/lib/libgtkmm-2.4.so.1
#30 0xb7a0d02c in _gtk_marshal_BOOLEAN__BOXED () from /usr
/lib/libgtk-x11-2.0.so.0
#31 0xb74c4d75 in g_cclosure_new_swap () from /usr/lib/libgobject
-2.0.so.0
#32 0xb74c53a8 in g_closure_invoke () from /usr/lib/libgobject-2.0.
so.0
#33 0xb74d3c9f in g_signal_stop_emission () from /usr/lib/
libgobject-2.0.so.0
#34 0xb74d4ec3 in g_signal_emit_valist () from /usr/lib/libgobject-
2.0.so.0
#35 0xb74d54c3 in g_signal_emit () from /usr/lib/libgobject-2.0.so.
0
#36 0xb7aef16f in gtk_widget_activate () from /usr/lib/libgtk-x11-2.
0.so.0
#37 0xb7a0b767 in gtk_propagate_event () from /usr/lib/libgtk-x11-
2.0.so.0
#38 0xb7a0bba0 in gtk_main_do_event () from /usr/lib/libgtk-x11-2.
0.so.0
#39 0xb78afb2d in _gdk_events_queue () from /usr/lib/libgdk-x11-2.
0.so.0
#40 0xb73ce4ee in g_main_context_dispatch () from /usr/lib/libglib-
2.0.so.0
#41 0xb73d14f6 in g_main_context_check () from /usr/lib/libglib-2.
0.so.0
#42 0xb73d17e3 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#43 0xb7a0ae65 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#44 0xb7e31c95 in Gtk::Main::run_impl () from /usr/lib/libgtkmm-2.
4.so.1
#45 0xb7e31b86 in Gtk::Main::run () from /usr/lib/libgtkmm-2.4.so.
1
#46 0x0806c9e1 in sp_main_gui (argc=1, argv=0xbf872174) at
main.cpp:834
#47 0x0815c270 in Inkscape::NSApplication::Application::run (this
=0xbf8720bc) at application/application.cpp:128
#48 0x0806c299 in main (argc=1, argv=0xbf872174) at main.cpp:
6690806c299 in main (argc=1, argv=0xbf872174) at main.cpp:669
----------------------------------------------------------------------
>Comment By: Bryce Harrington (bryce)
Date: 2006-05-24 17:42
Message:
Logged In: YES
user_id=4782
Moving this one to 9 since it is a crash bug. However, I'm
not going to include this as a MUST-FIX for 0.44, because in
0.44 inkboard is not enabled by default, and is only being
advertised for experimental purposes.
However, since much work is planned for inkboard in coming
months, this is an important one to get closed.
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2006-04-22 14:38
Message:
Logged In: NO
I assume I have the same problem. I haven't compiled a
debug version.
With amessage.de a sessions looks like this (recorded with
ethereal, comments by me):
<!-- client -->
<?xml version='1.0' encoding='UTF-8'?>
<stream:stream xmlns="jabber:client"
xmlns:stream="http://etherx.jabber.org/streams";
to="amessage.de/Inkboard" id="msg_1">
<!-- server -->
<stream:stream
xmlns:stream='http://etherx.jabber.org/streams';
version='1.0'>
<!-- client -->
<iq type="get" id="msg_2">
<query xmlns="jabber:iq:auth">
<username>falscherhase</username>
</query>
</iq>
<!-- server -->
<stream:error>
<host-unknown
xmlns='urn:ietf:params:xml:ns:xmpp-streams'/>
<text
xmlns='urn:ietf:params:xml:ns:xmpp-streams'>Invalid to
address</text>
</stream:error>
</stream:stream>
while it works with gristle.org:
<!-- client -->
<?xml version='1.0' encoding='UTF-8'?>
<stream:stream xmlns="jabber:client"
xmlns:stream="http://etherx.jabber.org/streams";
to="gristle.org/Inkboard" id="msg_1">
<!-- server -->
<?xml version='1.0'?>
<stream:stream
xmlns:stream='http://etherx.jabber.org/streams';
id='444A9EF5' xmlns='jabber:client'
from='gristle.org/Inkboard'>
<!-- client -->
<iq type="get" id="msg_2">
<query xmlns="jabber:iq:auth">
<username>falscherhase</username>
</query>
</iq>
<!-- server -->
<iq type='result' id='msg_2'>
<query xmlns='jabber:iq:auth'>
<username>falscherhase</username>
<password/>
<digest/>
<sequence>499</sequence>
<token>444A9EBB</token>
<resource/>
</query>
</iq>
<!-- client -->
<iq type="set" id="msg_3">
<query xmlns="jabber:iq:auth">
<username>falscherhase</username>
<digest>56....................................47</digest>
<resource>Inkboard</resource>
</query>
</iq>
<!-- server -->
...
----------------------------------------------------------------------
Comment By: Peter J. R. Moulder (pjrm)
Date: 2005-11-24 02:09
Message:
Logged In: YES
user_id=827826
I suggest grabbing the source for libloudmouth, compiling it
with CFLAGS=-g, and linking against that version for running
gdb on it: that should give a better idea as to why it's
crashing, e.g. you can see the exact line, and you can see
what data it's using that causes it to crash. Might give a
clue as to what code is at fault and how to correct it.
Filing a bug against libloudmouth may well be useful.
Including information you've found from gdb makes it more
likely to get the problem sorted quickly.
----------------------------------------------------------------------
Comment By: David Yip (dwyip)
Date: 2005-11-17 21:12
Message:
Logged In: YES
user_id=586161
Sorry, that last comment was me forgetting to log in.
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2005-11-17 21:09
Message:
Logged In: NO
Okay. I've finally had some time to poke at this issue, and
there's three things I can think of that might be causing this:
(1) This is a Loudmouth bug of some sort. I don't know if
this is true or not, but nothing in the Inkboard code itself
is popping out at me as being obviously wrong, nor do any
values being passed to Loudmouth look suspect.
(2) I'm not carrying out Loudmouth's SSL initialization
properly, which is causing the library to crash in some way.
However, SSL works on other servers (like gristle.org), so
I'm not sure if this is it.
(3) Something totally different :p
I'll keep poking at this. However, a switch to a different
Jabber client is in the works, so that very well may fix
this problem.
----------------------------------------------------------------------
Comment By: Peter J. R. Moulder (pjrm)
Date: 2005-11-08 01:03
Message:
Logged In: YES
user_id=827826
Please don't assume that the remote jabber server/client is
sending valid data. E.g. if bad data can cause a program to
crash, then there's a fair chance that malicious bad data
can do harm such as causing the program to execute arbitrary
code.
----------------------------------------------------------------------
Comment By: David Yip (dwyip)
Date: 2005-11-07 21:12
Message:
Logged In: YES
user_id=586161
Give me a day or two to get some project work out of the
way, and I'll take a look at this. There's probably some
variation in Jabber login protocol that I didn't account for.
In the meantime, do you have access to a copy of Ethereal or
similar packet sniffing tool that can export to tcpdump? If
so, can you create a test account on amessage.info, record a
login session on that test account, and attach it here? I
can compare it to "known good" servers and see if I'm
missing anything.
----------------------------------------------------------------------
Comment By: Alexandre Prokoudine (prokoudine)
Date: 2005-11-07 16:23
Message:
Logged In: YES
user_id=597819
Same sad story with my jabber.ru account I got used to
----------------------------------------------------------------------
Comment By: Jure Cuhalev (gandalfar)
Date: 2005-11-06 15:21
Message:
Logged In: YES
user_id=675570
Additional bit of info:
this happens only with my 'amessage.info' account. It works with 'gristle.
org' account.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=604306&aid=1349761&group_id=93438

Bugs item #1349761, was opened at 2005-11-06 15:58
Message generated for change (Comment added) made by dwyip
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=604306&aid=1349761&group_id=93438
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Other
Group: Linux
Status: Open
Resolution: None
Priority: 9
Submitted By: Jure Cuhalev (gandalfar)
Assigned to: Nobody/Anonymous (nobody)
Summary: Inkboard: inkscape crashes when trying to connect
Initial Comment:
I grabbed and compiled latest cvs (6th of Nov) on Ubuntu Breezy. I'
m trying to connect to my jabber server (amessage.info). I enter
details: username, pass, servername and click connect. After a
few moments I get the following crash:
(gdb) run
Starting program: /usr/local/bin/inkscape
[Thread debugging using libthread_db enabled]
[New Thread -1224575296 (LWP 1567)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1224575296 (LWP 1567)]
0xb73cdcfb in g_source_get_current_time () from /usr/lib/libglib-2.
0.so.0
(gdb) bt
#0 0xb73cdcfb in g_source_get_current_time () from /usr/lib/libglib
-2.0.so.0
#1 0xb742f1ee in lm_connection_is_open () from /usr/lib/
libloudmouth-1.so.0
#2 0xb742f30e in lm_connection_is_open () from /usr/lib/
libloudmouth-1.so.0
#3 0xb73f531c in g_vasprintf () from /usr/lib/libglib-2.0.so.0
#4 0xb73ce4ee in g_main_context_dispatch () from /usr/lib/libglib-
2.0.so.0
#5 0xb73d14f6 in g_main_context_check () from /usr/lib/libglib-2.
0.so.0
#6 0xb73d19d8 in g_main_context_iteration () from /usr/lib/libglib-
2.0.so.0
#7 0xb743110f in lm_connection_send_with_reply_and_block ()
from /usr/lib/libloudmouth-1.so.0
#8 0xb74312bc in lm_connection_authenticate_and_block () from
/usr/lib/libloudmouth-1.so.0
#9 0x0820996d in Inkscape::Whiteboard::SessionManager::
connectToServer (this=0x8701cb0, server=@0xbf870f74, port=@0
xbf870f70, username=@0xbf870f6c,
pw=@0xbf870f68, usessl=false) at jabber_whiteboard/session-
manager.cpp:243
#10 0x0818ca8a in Inkscape::UI::Dialog::
WhiteboardConnectDialogImpl::_respCallback (this=0x8eb29c8,
resp=-5) at ui/dialog/whiteboard-connect.cpp:129
#11 0x0818d690 in sigc::internal::slot_call0<sigc::bind_functor<0,
sigc::bound_mem_functor1<void, Inkscape::UI::Dialog::
WhiteboardConnectDialogImpl, int>, GtkResponseType, sigc::nil,
sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil>, void>::call_it (rep=0
x928e3c8) at mem_fun.h:1839
#12 0xb7bf73a6 in Glib::SignalProxyNormal::slot0_void_callback ()
from /usr/lib/libglibmm-2.4.so.1
#13 0xb74d0ab3 in g_cclosure_marshal_VOID__VOID () from /usr/
lib/libgobject-2.0.so.0
#14 0xb74c53a8 in g_closure_invoke () from /usr/lib/libgobject-2.0.
so.0
#15 0xb74d3e8d in g_signal_stop_emission () from /usr/lib/
libgobject-2.0.so.0
#16 0xb74d5150 in g_signal_emit_valist () from /usr/lib/libgobject-
2.0.so.0
#17 0xb74d54c3 in g_signal_emit () from /usr/lib/libgobject-2.0.so.
0
#18 0xb794c22c in gtk_button_clicked () from /usr/lib/libgtk-x11-2.
0.so.0
#19 0xb794da4c in _gtk_button_set_depressed () from /usr/lib/
libgtk-x11-2.0.so.0
#20 0xb7df4832 in Gtk::Button_Class::released_callback () from /
usr/lib/libgtkmm-2.4.so.1
#21 0xb74d0ab3 in g_cclosure_marshal_VOID__VOID () from /usr/
lib/libgobject-2.0.so.0
#22 0xb74c4d75 in g_cclosure_new_swap () from /usr/lib/libgobject
-2.0.so.0
#23 0xb74c53a8 in g_closure_invoke () from /usr/lib/libgobject-2.0.
so.0
#24 0xb74d3769 in g_signal_stop_emission () from /usr/lib/
libgobject-2.0.so.0
#25 0xb74d5150 in g_signal_emit_valist () from /usr/lib/libgobject-
2.0.so.0
#26 0xb74d54c3 in g_signal_emit () from /usr/lib/libgobject-2.0.so.
0
#27 0xb794c1a6 in gtk_button_released () from /usr/lib/libgtk-x11-
2.0.so.0
#28 0xb794d115 in _gtk_button_paint () from /usr/lib/libgtk-x11-2.0.
so.0
#29 0xb7e8b429 in Gtk::Widget_Class::button_release_event_
callback () from /usr/lib/libgtkmm-2.4.so.1
#30 0xb7a0d02c in _gtk_marshal_BOOLEAN__BOXED () from /usr
/lib/libgtk-x11-2.0.so.0
#31 0xb74c4d75 in g_cclosure_new_swap () from /usr/lib/libgobject
-2.0.so.0
#32 0xb74c53a8 in g_closure_invoke () from /usr/lib/libgobject-2.0.
so.0
#33 0xb74d3c9f in g_signal_stop_emission () from /usr/lib/
libgobject-2.0.so.0
#34 0xb74d4ec3 in g_signal_emit_valist () from /usr/lib/libgobject-
2.0.so.0
#35 0xb74d54c3 in g_signal_emit () from /usr/lib/libgobject-2.0.so.
0
#36 0xb7aef16f in gtk_widget_activate () from /usr/lib/libgtk-x11-2.
0.so.0
#37 0xb7a0b767 in gtk_propagate_event () from /usr/lib/libgtk-x11-
2.0.so.0
#38 0xb7a0bba0 in gtk_main_do_event () from /usr/lib/libgtk-x11-2.
0.so.0
#39 0xb78afb2d in _gdk_events_queue () from /usr/lib/libgdk-x11-2.
0.so.0
#40 0xb73ce4ee in g_main_context_dispatch () from /usr/lib/libglib-
2.0.so.0
#41 0xb73d14f6 in g_main_context_check () from /usr/lib/libglib-2.
0.so.0
#42 0xb73d17e3 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#43 0xb7a0ae65 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#44 0xb7e31c95 in Gtk::Main::run_impl () from /usr/lib/libgtkmm-2.
4.so.1
#45 0xb7e31b86 in Gtk::Main::run () from /usr/lib/libgtkmm-2.4.so.
1
#46 0x0806c9e1 in sp_main_gui (argc=1, argv=0xbf872174) at
main.cpp:834
#47 0x0815c270 in Inkscape::NSApplication::Application::run (this
=0xbf8720bc) at application/application.cpp:128
#48 0x0806c299 in main (argc=1, argv=0xbf872174) at main.cpp:
6690806c299 in main (argc=1, argv=0xbf872174) at main.cpp:669
----------------------------------------------------------------------
Comment By: David Yip (dwyip)
Date: 2006-05-26 02:54
Message:
Logged In: YES
user_id=586161
This might have been fixed with newer versions of Loudmouth
and all the miscellaneous bugfixes that have been going
into the Inkboard connection logic. I'll check to see if
this really is the case.
----------------------------------------------------------------------
Comment By: Bryce Harrington (bryce)
Date: 2006-05-24 18:42
Message:
Logged In: YES
user_id=4782
Moving this one to 9 since it is a crash bug. However, I'm
not going to include this as a MUST-FIX for 0.44, because in
0.44 inkboard is not enabled by default, and is only being
advertised for experimental purposes.
However, since much work is planned for inkboard in coming
months, this is an important one to get closed.
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2006-04-22 15:38
Message:
Logged In: NO
I assume I have the same problem. I haven't compiled a
debug version.
With amessage.de a sessions looks like this (recorded with
ethereal, comments by me):
<!-- client -->
<?xml version='1.0' encoding='UTF-8'?>
<stream:stream xmlns="jabber:client"
xmlns:stream="http://etherx.jabber.org/streams";
to="amessage.de/Inkboard" id="msg_1">
<!-- server -->
<stream:stream
xmlns:stream='http://etherx.jabber.org/streams';
version='1.0'>
<!-- client -->
<iq type="get" id="msg_2">
<query xmlns="jabber:iq:auth">
<username>falscherhase</username>
</query>
</iq>
<!-- server -->
<stream:error>
<host-unknown
xmlns='urn:ietf:params:xml:ns:xmpp-streams'/>
<text
xmlns='urn:ietf:params:xml:ns:xmpp-streams'>Invalid to
address</text>
</stream:error>
</stream:stream>
while it works with gristle.org:
<!-- client -->
<?xml version='1.0' encoding='UTF-8'?>
<stream:stream xmlns="jabber:client"
xmlns:stream="http://etherx.jabber.org/streams";
to="gristle.org/Inkboard" id="msg_1">
<!-- server -->
<?xml version='1.0'?>
<stream:stream
xmlns:stream='http://etherx.jabber.org/streams';
id='444A9EF5' xmlns='jabber:client'
from='gristle.org/Inkboard'>
<!-- client -->
<iq type="get" id="msg_2">
<query xmlns="jabber:iq:auth">
<username>falscherhase</username>
</query>
</iq>
<!-- server -->
<iq type='result' id='msg_2'>
<query xmlns='jabber:iq:auth'>
<username>falscherhase</username>
<password/>
<digest/>
<sequence>499</sequence>
<token>444A9EBB</token>
<resource/>
</query>
</iq>
<!-- client -->
<iq type="set" id="msg_3">
<query xmlns="jabber:iq:auth">
<username>falscherhase</username>
<digest>56....................................47</digest>
<resource>Inkboard</resource>
</query>
</iq>
<!-- server -->
...
----------------------------------------------------------------------
Comment By: Peter J. R. Moulder (pjrm)
Date: 2005-11-24 03:09
Message:
Logged In: YES
user_id=827826
I suggest grabbing the source for libloudmouth, compiling it
with CFLAGS=-g, and linking against that version for running
gdb on it: that should give a better idea as to why it's
crashing, e.g. you can see the exact line, and you can see
what data it's using that causes it to crash. Might give a
clue as to what code is at fault and how to correct it.
Filing a bug against libloudmouth may well be useful.
Including information you've found from gdb makes it more
likely to get the problem sorted quickly.
----------------------------------------------------------------------
Comment By: David Yip (dwyip)
Date: 2005-11-17 22:12
Message:
Logged In: YES
user_id=586161
Sorry, that last comment was me forgetting to log in.
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2005-11-17 22:09
Message:
Logged In: NO
Okay. I've finally had some time to poke at this issue, and
there's three things I can think of that might be causing this:
(1) This is a Loudmouth bug of some sort. I don't know if
this is true or not, but nothing in the Inkboard code itself
is popping out at me as being obviously wrong, nor do any
values being passed to Loudmouth look suspect.
(2) I'm not carrying out Loudmouth's SSL initialization
properly, which is causing the library to crash in some way.
However, SSL works on other servers (like gristle.org), so
I'm not sure if this is it.
(3) Something totally different :p
I'll keep poking at this. However, a switch to a different
Jabber client is in the works, so that very well may fix
this problem.
----------------------------------------------------------------------
Comment By: Peter J. R. Moulder (pjrm)
Date: 2005-11-08 02:03
Message:
Logged In: YES
user_id=827826
Please don't assume that the remote jabber server/client is
sending valid data. E.g. if bad data can cause a program to
crash, then there's a fair chance that malicious bad data
can do harm such as causing the program to execute arbitrary
code.
----------------------------------------------------------------------
Comment By: David Yip (dwyip)
Date: 2005-11-07 22:12
Message:
Logged In: YES
user_id=586161
Give me a day or two to get some project work out of the
way, and I'll take a look at this. There's probably some
variation in Jabber login protocol that I didn't account for.
In the meantime, do you have access to a copy of Ethereal or
similar packet sniffing tool that can export to tcpdump? If
so, can you create a test account on amessage.info, record a
login session on that test account, and attach it here? I
can compare it to "known good" servers and see if I'm
missing anything.
----------------------------------------------------------------------
Comment By: Alexandre Prokoudine (prokoudine)
Date: 2005-11-07 17:23
Message:
Logged In: YES
user_id=597819
Same sad story with my jabber.ru account I got used to
----------------------------------------------------------------------
Comment By: Jure Cuhalev (gandalfar)
Date: 2005-11-06 16:21
Message:
Logged In: YES
user_id=675570
Additional bit of info:
this happens only with my 'amessage.info' account. It works with 'gristle.
org' account.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=604306&aid=1349761&group_id=93438

Bugs item #1349761, was opened at 2005-11-06 15:58
Message generated for change (Comment added) made by dwyip
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=604306&aid=1349761&group_id=93438
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Other
Group: Linux
Status: Open
Resolution: None
Priority: 9
Submitted By: Jure Cuhalev (gandalfar)
Assigned to: Nobody/Anonymous (nobody)
Summary: Inkboard: inkscape crashes when trying to connect
Initial Comment:
I grabbed and compiled latest cvs (6th of Nov) on Ubuntu Breezy. I'
m trying to connect to my jabber server (amessage.info). I enter
details: username, pass, servername and click connect. After a
few moments I get the following crash:
(gdb) run
Starting program: /usr/local/bin/inkscape
[Thread debugging using libthread_db enabled]
[New Thread -1224575296 (LWP 1567)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1224575296 (LWP 1567)]
0xb73cdcfb in g_source_get_current_time () from /usr/lib/libglib-2.
0.so.0
(gdb) bt
#0 0xb73cdcfb in g_source_get_current_time () from /usr/lib/libglib
-2.0.so.0
#1 0xb742f1ee in lm_connection_is_open () from /usr/lib/
libloudmouth-1.so.0
#2 0xb742f30e in lm_connection_is_open () from /usr/lib/
libloudmouth-1.so.0
#3 0xb73f531c in g_vasprintf () from /usr/lib/libglib-2.0.so.0
#4 0xb73ce4ee in g_main_context_dispatch () from /usr/lib/libglib-
2.0.so.0
#5 0xb73d14f6 in g_main_context_check () from /usr/lib/libglib-2.
0.so.0
#6 0xb73d19d8 in g_main_context_iteration () from /usr/lib/libglib-
2.0.so.0
#7 0xb743110f in lm_connection_send_with_reply_and_block ()
from /usr/lib/libloudmouth-1.so.0
#8 0xb74312bc in lm_connection_authenticate_and_block () from
/usr/lib/libloudmouth-1.so.0
#9 0x0820996d in Inkscape::Whiteboard::SessionManager::
connectToServer (this=0x8701cb0, server=@0xbf870f74, port=@0
xbf870f70, username=@0xbf870f6c,
pw=@0xbf870f68, usessl=false) at jabber_whiteboard/session-
manager.cpp:243
#10 0x0818ca8a in Inkscape::UI::Dialog::
WhiteboardConnectDialogImpl::_respCallback (this=0x8eb29c8,
resp=-5) at ui/dialog/whiteboard-connect.cpp:129
#11 0x0818d690 in sigc::internal::slot_call0<sigc::bind_functor<0,
sigc::bound_mem_functor1<void, Inkscape::UI::Dialog::
WhiteboardConnectDialogImpl, int>, GtkResponseType, sigc::nil,
sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil>, void>::call_it (rep=0
x928e3c8) at mem_fun.h:1839
#12 0xb7bf73a6 in Glib::SignalProxyNormal::slot0_void_callback ()
from /usr/lib/libglibmm-2.4.so.1
#13 0xb74d0ab3 in g_cclosure_marshal_VOID__VOID () from /usr/
lib/libgobject-2.0.so.0
#14 0xb74c53a8 in g_closure_invoke () from /usr/lib/libgobject-2.0.
so.0
#15 0xb74d3e8d in g_signal_stop_emission () from /usr/lib/
libgobject-2.0.so.0
#16 0xb74d5150 in g_signal_emit_valist () from /usr/lib/libgobject-
2.0.so.0
#17 0xb74d54c3 in g_signal_emit () from /usr/lib/libgobject-2.0.so.
0
#18 0xb794c22c in gtk_button_clicked () from /usr/lib/libgtk-x11-2.
0.so.0
#19 0xb794da4c in _gtk_button_set_depressed () from /usr/lib/
libgtk-x11-2.0.so.0
#20 0xb7df4832 in Gtk::Button_Class::released_callback () from /
usr/lib/libgtkmm-2.4.so.1
#21 0xb74d0ab3 in g_cclosure_marshal_VOID__VOID () from /usr/
lib/libgobject-2.0.so.0
#22 0xb74c4d75 in g_cclosure_new_swap () from /usr/lib/libgobject
-2.0.so.0
#23 0xb74c53a8 in g_closure_invoke () from /usr/lib/libgobject-2.0.
so.0
#24 0xb74d3769 in g_signal_stop_emission () from /usr/lib/
libgobject-2.0.so.0
#25 0xb74d5150 in g_signal_emit_valist () from /usr/lib/libgobject-
2.0.so.0
#26 0xb74d54c3 in g_signal_emit () from /usr/lib/libgobject-2.0.so.
0
#27 0xb794c1a6 in gtk_button_released () from /usr/lib/libgtk-x11-
2.0.so.0
#28 0xb794d115 in _gtk_button_paint () from /usr/lib/libgtk-x11-2.0.
so.0
#29 0xb7e8b429 in Gtk::Widget_Class::button_release_event_
callback () from /usr/lib/libgtkmm-2.4.so.1
#30 0xb7a0d02c in _gtk_marshal_BOOLEAN__BOXED () from /usr
/lib/libgtk-x11-2.0.so.0
#31 0xb74c4d75 in g_cclosure_new_swap () from /usr/lib/libgobject
-2.0.so.0
#32 0xb74c53a8 in g_closure_invoke () from /usr/lib/libgobject-2.0.
so.0
#33 0xb74d3c9f in g_signal_stop_emission () from /usr/lib/
libgobject-2.0.so.0
#34 0xb74d4ec3 in g_signal_emit_valist () from /usr/lib/libgobject-
2.0.so.0
#35 0xb74d54c3 in g_signal_emit () from /usr/lib/libgobject-2.0.so.
0
#36 0xb7aef16f in gtk_widget_activate () from /usr/lib/libgtk-x11-2.
0.so.0
#37 0xb7a0b767 in gtk_propagate_event () from /usr/lib/libgtk-x11-
2.0.so.0
#38 0xb7a0bba0 in gtk_main_do_event () from /usr/lib/libgtk-x11-2.
0.so.0
#39 0xb78afb2d in _gdk_events_queue () from /usr/lib/libgdk-x11-2.
0.so.0
#40 0xb73ce4ee in g_main_context_dispatch () from /usr/lib/libglib-
2.0.so.0
#41 0xb73d14f6 in g_main_context_check () from /usr/lib/libglib-2.
0.so.0
#42 0xb73d17e3 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#43 0xb7a0ae65 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#44 0xb7e31c95 in Gtk::Main::run_impl () from /usr/lib/libgtkmm-2.
4.so.1
#45 0xb7e31b86 in Gtk::Main::run () from /usr/lib/libgtkmm-2.4.so.
1
#46 0x0806c9e1 in sp_main_gui (argc=1, argv=0xbf872174) at
main.cpp:834
#47 0x0815c270 in Inkscape::NSApplication::Application::run (this
=0xbf8720bc) at application/application.cpp:128
#48 0x0806c299 in main (argc=1, argv=0xbf872174) at main.cpp:
6690806c299 in main (argc=1, argv=0xbf872174) at main.cpp:669
----------------------------------------------------------------------
Comment By: David Yip (dwyip)
Date: 2006-05-28 20:50
Message:
Logged In: YES
user_id=586161
I have been able to connect to amessage.info and amessage.de
with the Inkboard code in trunk, so I think this problem has
been fixed.
gandalfar: If possible, please try to connect to
amessage.info again, using the latest revision in trunk. If
you still get the crash, please report the crash in this
thread, and add the version of Loudmouth you are using. Thanks!
----------------------------------------------------------------------
Comment By: David Yip (dwyip)
Date: 2006-05-26 02:54
Message:
Logged In: YES
user_id=586161
This might have been fixed with newer versions of Loudmouth
and all the miscellaneous bugfixes that have been going
into the Inkboard connection logic. I'll check to see if
this really is the case.
----------------------------------------------------------------------
Comment By: Bryce Harrington (bryce)
Date: 2006-05-24 18:42
Message:
Logged In: YES
user_id=4782
Moving this one to 9 since it is a crash bug. However, I'm
not going to include this as a MUST-FIX for 0.44, because in
0.44 inkboard is not enabled by default, and is only being
advertised for experimental purposes.
However, since much work is planned for inkboard in coming
months, this is an important one to get closed.
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2006-04-22 15:38
Message:
Logged In: NO
I assume I have the same problem. I haven't compiled a
debug version.
With amessage.de a sessions looks like this (recorded with
ethereal, comments by me):
<!-- client -->
<?xml version='1.0' encoding='UTF-8'?>
<stream:stream xmlns="jabber:client"
xmlns:stream="http://etherx.jabber.org/streams";
to="amessage.de/Inkboard" id="msg_1">
<!-- server -->
<stream:stream
xmlns:stream='http://etherx.jabber.org/streams';
version='1.0'>
<!-- client -->
<iq type="get" id="msg_2">
<query xmlns="jabber:iq:auth">
<username>falscherhase</username>
</query>
</iq>
<!-- server -->
<stream:error>
<host-unknown
xmlns='urn:ietf:params:xml:ns:xmpp-streams'/>
<text
xmlns='urn:ietf:params:xml:ns:xmpp-streams'>Invalid to
address</text>
</stream:error>
</stream:stream>
while it works with gristle.org:
<!-- client -->
<?xml version='1.0' encoding='UTF-8'?>
<stream:stream xmlns="jabber:client"
xmlns:stream="http://etherx.jabber.org/streams";
to="gristle.org/Inkboard" id="msg_1">
<!-- server -->
<?xml version='1.0'?>
<stream:stream
xmlns:stream='http://etherx.jabber.org/streams';
id='444A9EF5' xmlns='jabber:client'
from='gristle.org/Inkboard'>
<!-- client -->
<iq type="get" id="msg_2">
<query xmlns="jabber:iq:auth">
<username>falscherhase</username>
</query>
</iq>
<!-- server -->
<iq type='result' id='msg_2'>
<query xmlns='jabber:iq:auth'>
<username>falscherhase</username>
<password/>
<digest/>
<sequence>499</sequence>
<token>444A9EBB</token>
<resource/>
</query>
</iq>
<!-- client -->
<iq type="set" id="msg_3">
<query xmlns="jabber:iq:auth">
<username>falscherhase</username>
<digest>56....................................47</digest>
<resource>Inkboard</resource>
</query>
</iq>
<!-- server -->
...
----------------------------------------------------------------------
Comment By: Peter J. R. Moulder (pjrm)
Date: 2005-11-24 03:09
Message:
Logged In: YES
user_id=827826
I suggest grabbing the source for libloudmouth, compiling it
with CFLAGS=-g, and linking against that version for running
gdb on it: that should give a better idea as to why it's
crashing, e.g. you can see the exact line, and you can see
what data it's using that causes it to crash. Might give a
clue as to what code is at fault and how to correct it.
Filing a bug against libloudmouth may well be useful.
Including information you've found from gdb makes it more
likely to get the problem sorted quickly.
----------------------------------------------------------------------
Comment By: David Yip (dwyip)
Date: 2005-11-17 22:12
Message:
Logged In: YES
user_id=586161
Sorry, that last comment was me forgetting to log in.
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2005-11-17 22:09
Message:
Logged In: NO
Okay. I've finally had some time to poke at this issue, and
there's three things I can think of that might be causing this:
(1) This is a Loudmouth bug of some sort. I don't know if
this is true or not, but nothing in the Inkboard code itself
is popping out at me as being obviously wrong, nor do any
values being passed to Loudmouth look suspect.
(2) I'm not carrying out Loudmouth's SSL initialization
properly, which is causing the library to crash in some way.
However, SSL works on other servers (like gristle.org), so
I'm not sure if this is it.
(3) Something totally different :p
I'll keep poking at this. However, a switch to a different
Jabber client is in the works, so that very well may fix
this problem.
----------------------------------------------------------------------
Comment By: Peter J. R. Moulder (pjrm)
Date: 2005-11-08 02:03
Message:
Logged In: YES
user_id=827826
Please don't assume that the remote jabber server/client is
sending valid data. E.g. if bad data can cause a program to
crash, then there's a fair chance that malicious bad data
can do harm such as causing the program to execute arbitrary
code.
----------------------------------------------------------------------
Comment By: David Yip (dwyip)
Date: 2005-11-07 22:12
Message:
Logged In: YES
user_id=586161
Give me a day or two to get some project work out of the
way, and I'll take a look at this. There's probably some
variation in Jabber login protocol that I didn't account for.
In the meantime, do you have access to a copy of Ethereal or
similar packet sniffing tool that can export to tcpdump? If
so, can you create a test account on amessage.info, record a
login session on that test account, and attach it here? I
can compare it to "known good" servers and see if I'm
missing anything.
----------------------------------------------------------------------
Comment By: Alexandre Prokoudine (prokoudine)
Date: 2005-11-07 17:23
Message:
Logged In: YES
user_id=597819
Same sad story with my jabber.ru account I got used to
----------------------------------------------------------------------
Comment By: Jure Cuhalev (gandalfar)
Date: 2005-11-06 16:21
Message:
Logged In: YES
user_id=675570
Additional bit of info:
this happens only with my 'amessage.info' account. It works with 'gristle.
org' account.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=604306&aid=1349761&group_id=93438