Bug#695985: gwibber-service: dbus starts multiple instances of gwibber because of poor service configuration

2013-01-15 Thread Pauli Nieminen
Sorry for taking this long to come back to the patch. Today I proted the changes to 3.5.2 in experimental but I still didn't figure out all build dependecies for 3.6.0. I quickly tested the interface. I also checked that only single service is started even if I remove the racy check from service

Bug#695985: gwibber-service: dbus starts multiple instances of gwibber because of poor service configuration

2013-01-15 Thread Pauli Nieminen
The master merge request can be found from https://code.launchpad.net/~paniemin/gwibber/gwibber/+merge/143341

Bug#695985: gwibber-service: dbus starts multiple instances of gwibber because of poor service configuration

2012-12-21 Thread Pauli Nieminen
On Mon, Dec 17, 2012 at 11:58 AM, Kartik Mistry kartik.mis...@gmail.comwrote: On Sat, Dec 15, 2012 at 2:39 PM, Pauli suok...@gmail.com wrote: I noticed that sometimes gwibber generates multiple notifications for a single update. I quickly figured out that issue was dbus starting multiple

Bug#695985: gwibber-service: dbus starts multiple instances of gwibber because of poor service configuration

2012-12-17 Thread Kartik Mistry
On Sat, Dec 15, 2012 at 2:39 PM, Pauli suok...@gmail.com wrote: I noticed that sometimes gwibber generates multiple notifications for a single update. I quickly figured out that issue was dbus starting multiple gwibber-service instances because a race condition in service startup. When I

Bug#695985: gwibber-service: dbus starts multiple instances of gwibber because of poor service configuration

2012-12-15 Thread Pauli
Package: gwibber-service Version: 3.0.0.1-2.2 Severity: important Tags: patch upstream Dear Maintainer, I noticed that sometimes gwibber generates multiple notifications for a single update. I quickly figured out that issue was dbus starting multiple gwibber-service instances because a race