Empathy plugin causes gnome-do to freeze/crash

[Martin Florian]

The Empathy plugin is currently completely unusable on Ubuntu 12.04. For example:
1. Start gnome-do
2. Write chat and select one of your contacts
3. Press Enter
Effect: nothing happens, gnome-do can't be summoned again and needs to be killed.

I tried starting gnome-do in a shell with "--debug", there was no new line after I tried to open a chat. I tried the latest gnome-do-plugins package from raring (0.8.4-5), no change.

My system:

$ lsb_release -rd
Description: Ubuntu 12.04.2 LTS
Release: 12.04

$ apt-cache policy gnome-do-plugins
gnome-do-plugins:
  Installed: 0.8.4-5
  Candidate: 0.8.4-5
  Version table:
 *** 0.8.4-5 0
        100 /var/lib/dpkg/status
     0.8.4-3build1 0
        500 http://ftp-stud.hs-esslingen.de/ubuntu/ precise/universe amd64 Packages

+ I'm using gnome classic, don't know if that might influence something.

Please tell if more information on my part might be helpful.

[Chris Halse Rogers (raof)]

Hi! Thanks for your bug report.

On Wed, Apr 10, 2013 at 8:04 PM, Martin Florian
<email address hidden> wrote:
> Public bug reported:
>
> The Empathy plugin is currently completely unusable on Ubuntu 12.04.
> For example:
> 1. Start gnome-do
> 2. Write chat and select one of your contacts
> 3. Press Enter
> Effect: nothing happens, gnome-do can't be summoned again and needs
> to be killed.
>
> I tried starting gnome-do in a shell with "--debug", there was no new
> line after I tried to open a chat.
>

Did gnome-do crash (ie: no new line, and the terminal prompt returned)
or did it just silently fail to do anything?

[Martin Florian (mflorian)]

Hi,

there was no new line in the terminal I ran gnome-do from, but the terminal prompt did not return. So gnome-do remained alive but unresponsive, i.e. couldn't be summoned. Ctrl+C or killing it was the only thing left to do, so it seemed.

Thanks for your interest in this bug!

[Chris Halse Rogers (raof)]

Ok. That suggests that the empathy plugin is causing a deadlock
somewhere¹. Could you run ‘gnome-do --debug’ from a terminal,
cause Do to lock up, and then from a *different* terminal run
“killall -SIGQUIT gnome-do”? That will dump the state of all the Do
threads to the console you ran gnome-do from. Could you please attach
that output?

¹: I should really get around to finishing the work required to make
that impossible ☺

[Martin Florian (mflorian)]

Hi,

there you go, this is the output from "gnome-do --debug" starting from when I did "killall -SIGQUIT gnome-do":

XXX@XXX:~$ gnome-do --debug

[...]

Full thread dump:

"Universe Update Dispatcher" tid=0x0xae4fdb40 this=0x0xb5181a80 thread handle 0x4c1 state : interrupted state owns ()
  at (wrapper managed-to-native) System.Threading.WaitHandle.WaitOne_internal (System.Threading.WaitHandle,intptr,int,bool) <0xffffffff>
  at System.Threading.WaitHandle.WaitOne () <0x0005f>
  at DBus.PendingCall.get_Reply () <0x000c3>
  at DBus.Connection.SendWithReplyAndBlock (DBus.Message) <0x00023>
  at DBus.BusObject.SendMethodCall (string,string,string,DBus.MessageWriter,System.Type,System.Exception&) <0x0014b>
  at AccountManagerQuery.IAccountManagerQueryProxy.FindAccounts (System.Collections.Generic.IDictionary`2<string, object>) <0x000a7>
  at EmpathyPlugin.EmpathyPlugin.GetAllAccounts () <0x0008b>
  at EmpathyPlugin.EmpathyPlugin.GetConnectedAccounts () <0x0000b>
  at EmpathyPlugin.EmpathyPlugin.GetAllContacts () <0x0000b>
  at EmpathyPlugin.EmpathyContactItemSource.ForceUpdateItems () <0x0003f>
  at EmpathyPlugin.EmpathyContactItemSource.UpdateItems () <0x00013>
  at Do.Universe.Safe.SafeItemSource.UpdateItems () <0x0001b>
  at Do.Core.UniverseManager.ReloadSource (Do.Universe.ItemSource,System.Collections.Generic.Dictionary`2<string, Do.Universe.Item>) <0x000c8>
  at Do.Core.UniverseManager/<ReloadUniverse>c__AnonStorey10.<>m__27 (Do.Universe.ItemSource) <0x0001b>
  at System.Linq.EnumerableExtensions.ForEach<T> (System.Collections.Generic.IEnumerable`1<T>,System.Action`1<T>) <0x00084>
  at Do.Core.UniverseManager.ReloadUniverse () <0x000e7>
  at Do.Core.UniverseManager.UniverseUpdateLoop () <0x0009b>
  at System.Threading.Thread.StartInternal () <0x00057>
  at (wrapper runtime-invoke) object.runtime_invoke_void__this__ (object,intptr,intptr,intptr) <0xffffffff>

"<unnamed thread>" tid=0x0xb7713700 this=0x0x56f18 thread handle 0x403 state : waiting on 0x46d : Event owns ()
  at (wrapper managed-to-native) System.Threading.WaitHandle.WaitOne_internal (System.Threading.WaitHandle,intptr,int,bool) <0xffffffff>
  at System.Threading.WaitHandle.WaitOne () <0x0005f>
  at DBus.PendingCall.get_Reply () <0x000c3>
  at DBus.Connection.SendWithReplyAndBlock (DBus.Message) <0x00023>
  at DBus.BusObject.SendMethodCall (string,string,string,DBus.MessageWriter,System.Type,System.Exception&) <0x0014b>
  at AccountManagerQuery.IAccountManagerQueryProxy.FindAccounts (System.Collections.Generic.IDictionary`2<string, object>) <0x000a7>
  at EmpathyPlugin.EmpathyPlugin.GetAllAccounts () <0x0008b>
  at EmpathyPlugin.EmpathyPlugin.GetConnectedAccounts () <0x0000b>
  at EmpathyPlugin.EmpathyPlugin.GetBuddyIsOnlineAndAccount (string,EmpathyPlugin.Account&) <0x00027>
  at EmpathyPlugin.EmpathyPlugin.OpenConversationWithBuddy (string,string) <0x0001b>
  at EmpathyPlugin.EmpathyPlugin.OpenConversationWithBuddy (string) <0x00013>
  at EmpathyPlugin.EmpathyChatAction/<Perform>c__Iterator8.MoveNext () <0x0022f>
  at System.Collections.Generic.List`1.AddEnumerable (System.Collections.Generic.IEnumerable`1<T>) <0x0008f>
  at System.Collections.Generic.List`1..ctor (System.Colle...

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.