[Bug 887946] Re: Deadlocks in main loop

2012-06-06 Thread Scott Moser
** Changed in: glib2.0 (Ubuntu Lucid)
   Importance: Undecided = Medium

** Changed in: glib2.0 (Ubuntu Lucid)
   Status: New = Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/887946

Title:
  Deadlocks in main loop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/887946/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 887946] Re: Deadlocks in main loop

2012-06-06 Thread Scott Moser
** Description changed:

  Some applications get stuck in a deadlock when utilizing glib. One of
  examples is lrmadmin, when connecting to lrmd. Upstream provided a fix
  for this bug and Ubuntu's version 11.04 and newer do not have this
  issue.
  
  Ubuntu 10.04 and 10.10 do not contain the fix. Upstream fix:
+   https://mail.gnome.org/archives/commits-list/2010-November/msg01816.html
  
- https://mail.gnome.org/archives/commits-list/2010-November/msg01816.html
+ [Impact]
+ Remove potential and demonstratable deadlocks in glib code.
+ 
+ [Test Case]
+  * Install lucid
+  * add ubuntu-ha-maintainers lucid ppa and update repo:
+apt-add-repository ppa:ubuntu-ha-maintainers/lucid-cluster ; apt-get update
+  * Install pacemaker:
+apt-get -y install pacemaker
+  * Enable corosync (/etc/default/corosync) and start it:
+sed -i -e 's/START=no/START=yes/' /etc/default/corosync
+service corosync start
+  * Open two client-server connections:
+lrmadmin -C ; lrmadmin -C
+It deadlocks on second run (it actually never finishes the first run).
+ 
+  * Kill lrmd and stop corosync:
+killall -9 lrmd ; service corosync stop
+  * install fix
+apt-get update  apt-get install libglib2.0-0
+  * Start corosync:
+service corosync start
+  * Run the test again:
+lrmadmin -C ; lrmadmin -C ; lrmadmin -C ; lrmadmin -C
+  * It doesn't deadlock.
+ 
+ [Regression Potential]
+ Regression potential should be very small.  This change is still present in 
almost unmodified upstream code to this day (g_source_unref_internal of 
glib/gmain.c).  The upstream trunk commit is at 
http://git.gnome.org/browse/glib/commit/?id=b358202856682e5cdefb0b4b8aaed3a45d9a85fa
 .

** Summary changed:

- Deadlocks in main loop
+ [SRU] Deadlocks in main loop

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/887946

Title:
  [SRU] Deadlocks in main loop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/887946/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 887946] Re: Deadlocks in main loop

2012-06-05 Thread Sebastien Bacher
** Changed in: glib2.0 (Ubuntu Maverick)
   Status: New = Won't Fix

** Changed in: glib2.0 (Ubuntu Maverick)
   Importance: Undecided = Low

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/887946

Title:
  Deadlocks in main loop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/887946/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 887946] Re: Deadlocks in main loop

2012-01-16 Thread Evan Broder
I'm unsubscribing ubuntu-sponsors from this bug. Merge-proposals
requesting a review from ubuntu-sponsors or ubuntu-branches (the
default) automatically show up in our queue for sponsorship.
Additionally subscribing ubuntu-sponsors creates an extra entry, so it
should only be used when attaching a debdiff to a bug, not when opening
a merge proposal

** Also affects: glib2.0 (Ubuntu Lucid)
   Importance: Undecided
   Status: New

** Also affects: glib2.0 (Ubuntu Maverick)
   Importance: Undecided
   Status: New

** Changed in: glib2.0 (Ubuntu)
   Status: New = Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/887946

Title:
  Deadlocks in main loop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/887946/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 887946] Re: Deadlocks in main loop

2011-11-09 Thread Launchpad Bug Tracker
** Branch linked: lp:~ivoks/ubuntu/lucid/glib2.0/887946

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/887946

Title:
  Deadlocks in main loop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/887946/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 887946] Re: Deadlocks in main loop

2011-11-09 Thread Ante Karamatić
** Branch linked: lp:~ivoks/ubuntu/maverick/glib2.0/887946

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/887946

Title:
  Deadlocks in main loop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/887946/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 887946] Re: Deadlocks in main loop

2011-11-09 Thread Ante Karamatić
Test case:

Install lucid
add ubuntu-ha-maintainers lucid ppa and update repo:
apt-add-repository ppa:ubuntu-ha-maintainers/lucid-cluster ; apt-get 
update
Install pacemaker:
apt-get -y install pacemaker
Enable corosync (/etc/default/corosync) and start it:
sed -i -e 's/START=no/START=yes/' /etc/default/corosync ; \
service corosync start
Open two client-server connections:
lrmadmin -C ; lrmadmin -C
It deadlocks on second run (it actually never finishes the first run).

Kill lrmd and stop corosync:
killall -9 lrmd ; service corosync stop
Add ppa:ivoks/glib (contains only the patch from the bzr branch):
apt-add-repository ppa:ivoks/glib ; apt-get update ; apt-get -y upgrade
Start corosync:
service corosync start
Run the test again:
lrmadmin -C ; lrmadmin -C ; lrmadmin -C ; lrmadmin -C
It doesn't deadlock.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/887946

Title:
  Deadlocks in main loop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/887946/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs