Using haze on Maemo with Conversations. Apparently every incoming Lotus Sametime message crashes Conversations and sends it into crash-restart-crash loop until the protocol is disabled. I opened a bug report on Conversations, but it is possible that the plugin sends something really invalid data and the issue should be inspected also from the other perspective. If someone could give me instructions on how to gather more detailed information on the issue I would attempt to obtain it.
Could you get debugging output from Haze, and dbus-monitor output, as follows: * Set your presence to Offline; * Open a terminal, and run `HAZE_PERSIST=1 HAZE_DEBUG=all /usr/lib/telepathy/telepathy-haze 2>&1 | tee haze.log`; * Open another terminal, and run `dbus-monitor | tee dbus-monitor.log`; * Set your presence back to Available, reproduce the bug. Conversations should not be crashing, so it's certainly buggy, but it'd be interesting to know if Haze is doing something stupid.
Created attachment 38237 [details] First attempt of haze log
Created attachment 38238 [details] First attempt of dbus log
Okay there you go, although I think something did not go correctly with starting the haze because it quit, and I got "can not connect to account" error unlike earlier => it was started perhaps wrong. Couldn't get to reproduce the problem, couldn't log in.
The content of attachment 38238 [details] has been deleted by Tollef Fog Heen <tfheen@err.no> who provided the following reason: password The token used to delete this attachment was generated at 2010-08-28 07:31:23 PDT.
(In reply to comment #4) > Okay there you go, although I think something did not go correctly with > starting the haze because it quit Yeah, that's pretty weird. I don't understand why it's aborting. I'll take a look at the Sametime prpl. Sorry, asking for a full dbus-monitor log was a mistake. The log contained your password; it's been deleted. Since Haze is misbehaving when you turn on its debugging output... could you let Haze automatically launch as normal, and instead just get the output of `dbus-monitor member=MessageReceived` and reproduce the bug? This will only contain the text contents of incoming messages.
(In reply to comment #6) > (In reply to comment #4) > > Okay there you go, although I think something did not go correctly with > > starting the haze because it quit > > Yeah, that's pretty weird. I don't understand why it's aborting. I'll take a > look at the Sametime prpl. Heh. The Sametime prpl changes the g_log handler to be libpurple's debug functions. Unfortunately, Haze directs libpurple's debug output into g_log... Loop!
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-haze/issues/42.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.