Sometimes Gmail notifies get stuck

Bug #678426 reported by Robert Dyer
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Docky
Invalid
Low
Unassigned
2.0
Fix Released
Low
Unassigned
2.1
Fix Released
Low
Unassigned
notify-sharp (Ubuntu)
New
Undecided
Unassigned

Bug Description

Sometimes Gmail will update, find a new email and fire off a notification. That notify never appears and the checker thread gets stuck. Then the next time you manually reload or it automatically reloads the thread is killed and a new checker is started.

"<unnamed thread>" tid=0x0xae8f1b70 this=0x0x2384b0 thread handle 0x4eb state : interrupted state owns ()
  at (wrapper managed-to-native) Mono.Unix.Native.Syscall.read (int,intptr,ulong) <0x00004>
  at (wrapper managed-to-native) Mono.Unix.Native.Syscall.read (int,intptr,ulong) <0x00004>
  at Mono.Unix.Native.Syscall.read (int,void*,ulong) <IL 0x00008, 0x00021>
  at Mono.Unix.UnixStream.Read (byte[],int,int) <IL 0x0003b, 0x00089>
  at NDesk.DBus.Connection.ReadMessage () <IL 0x00014, 0x0003e>
  at NDesk.DBus.PendingCall.get_Reply () <IL 0x00026, 0x00038>
  at NDesk.DBus.Connection.SendWithReplyAndBlock (NDesk.DBus.Message) <IL 0x00009, 0x00021>
  at NDesk.DBus.BusObject.SendMethodCall (string,string,string,NDesk.DBus.MessageWriter,System.Type,System.Exception&) <IL 0x0007e, 0x0012a>
  at org.freedesktop.DBus.IBusProxy.AddMatch (string) <IL 0x00042, 0x00083>
  at NDesk.DBus.Bus.AddMatch (string) <IL 0x00007, 0x0001f>
  at NDesk.DBus.BusObject.ToggleSignal (string,string,System.Delegate,bool) <IL 0x00094, 0x0011b>
  at Notifications.INotificationsProxy.add_NotificationClosed (Notifications.NotificationClosedHandler) <IL 0x00013, 0x00024>
  at Notifications.Notification..ctor () <IL 0x00061, 0x000b9>
  at Docky.Services.NotificationService.ToNotify (string,string,string) [0x00000] in /home/rdyer/branches/docky/Docky.Services/Docky.Services/NotificationService.cs:121
  at Docky.Services.NotificationService.Notify (string,string,string,Gdk.Screen,int,int) [0x00000] in /home/rdyer/branches/docky/Docky.Services/Docky.Services/NotificationService.cs:96
  at Docky.Services.NotificationService.Notify (string,string,string) [0x00070] in /home/rdyer/branches/docky/Docky.Services/Docky.Services/NotificationService.cs:91
  at Docky.Services.Logging.LogBase.SendNote (string,string,string,object[]) [0x00025] in /home/rdyer/branches/docky/Docky.Services/Docky.Services/Logging/LogBase.cs:135
  at Docky.Services.Log.Notify (string,string,string,object[]) [0x00013] in /home/rdyer/branches/docky/Docky.Services/Docky.Services/Log.cs:55
  at GMail.GMailAtom/<CheckGMail>c__AnonStorey1.<>m__9 () [0x003e2] in /home/rdyer/branches/docky/StandardPlugins/GMail/src/GMailAtom.cs:264
  at Docky.Services.SystemService/<RunOnThread>c__AnonStorey38.<>m__60 () [0x00000] in /home/rdyer/branches/docky/Docky.Services/Docky.Services/SystemService.cs:524
  at (wrapper runtime-invoke) object.runtime_invoke_void__this__ (object,intptr,intptr,intptr) <IL 0x0001c, 0x00040>

Robert Dyer (psybers)
Changed in docky:
status: New → Incomplete
Revision history for this message
Robert Dyer (psybers) wrote :

This is either an upstream issue with notify-sharp (libnotify0.4-cil) or ndesk-dbus.

Changed in docky:
status: Incomplete → Invalid
Revision history for this message
Robert Dyer (psybers) wrote :

Note that the bug tracker for notify-sharp seems to be gone so there is nowhere to file against that upstream. Until I eliminate that library as the problem I am reluctant to file upstream against ndesk-dbus.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.