| 2011-11-09 09:34:25 |
Ante Karamatić |
bug |
|
|
added bug |
| 2011-11-09 09:40:27 |
Launchpad Janitor |
branch linked |
|
lp:~ivoks/ubuntu/lucid/glib2.0/887946 |
|
| 2011-11-09 11:55:39 |
Ante Karamatić |
branch linked |
|
lp:~ivoks/ubuntu/maverick/glib2.0/887946 |
|
| 2012-01-16 18:37:52 |
Sebastien Bacher |
bug |
|
|
added subscriber Ubuntu Sponsors Team |
| 2012-01-16 22:06:45 |
Evan Broder |
nominated for series |
|
Ubuntu Lucid |
|
| 2012-01-16 22:06:45 |
Evan Broder |
bug task added |
|
glib2.0 (Ubuntu Lucid) |
|
| 2012-01-16 22:06:45 |
Evan Broder |
nominated for series |
|
Ubuntu Maverick |
|
| 2012-01-16 22:06:45 |
Evan Broder |
bug task added |
|
glib2.0 (Ubuntu Maverick) |
|
| 2012-01-16 22:06:59 |
Evan Broder |
glib2.0 (Ubuntu): status |
New |
Invalid |
|
| 2012-01-16 22:10:29 |
Evan Broder |
removed subscriber Ubuntu Sponsors Team |
|
|
|
| 2012-06-05 19:42:48 |
Sebastien Bacher |
glib2.0 (Ubuntu Maverick): status |
New |
Won't Fix |
|
| 2012-06-05 19:42:51 |
Sebastien Bacher |
glib2.0 (Ubuntu Maverick): importance |
Undecided |
Low |
|
| 2012-06-06 17:41:47 |
Scott Moser |
glib2.0 (Ubuntu Lucid): importance |
Undecided |
Medium |
|
| 2012-06-06 17:41:47 |
Scott Moser |
glib2.0 (Ubuntu Lucid): status |
New |
Confirmed |
|
| 2012-06-06 17:51:11 |
Scott Moser |
description |
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 |
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
[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 . |
|
| 2012-06-06 17:52:09 |
Scott Moser |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2012-06-06 17:53:03 |
Scott Moser |
summary |
Deadlocks in main loop |
[SRU] Deadlocks in main loop |
|
| 2012-06-08 07:23:39 |
Ante Karamatić |
description |
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
[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 . |
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
[Impact]
Remove potential and demonstratable deadlocks in glib code.
[Test Case]
* Install lucid
* Install python-software-properties:
apt-get install python-software-properties
* 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 . |
|
| 2012-06-08 07:29:07 |
Ante Karamatić |
description |
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
[Impact]
Remove potential and demonstratable deadlocks in glib code.
[Test Case]
* Install lucid
* Install python-software-properties:
apt-get install python-software-properties
* 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 . |
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
[Impact]
Remove potential and demonstratable deadlocks in glib code.
[Test Case]
* Install lucid
* Install python-software-properties:
apt-get install python-software-properties
* add ubuntu-ha-maintainers lucid ppa and update repo:
apt-add-repository ppa:ubuntu-ha-maintainers/ppa ; 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 . |
|
| 2012-06-08 07:33:27 |
Ante Karamatić |
description |
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
[Impact]
Remove potential and demonstratable deadlocks in glib code.
[Test Case]
* Install lucid
* Install python-software-properties:
apt-get install python-software-properties
* add ubuntu-ha-maintainers lucid ppa and update repo:
apt-add-repository ppa:ubuntu-ha-maintainers/ppa ; 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 . |
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
[Impact]
Remove potential and demonstratable deadlocks in glib code.
[Development Fix]
Bug is fixed in Ubuntu 11.04 and later.
[Stable Fix]
Proposed fix is cherry picked from the, at the time, latest version of glib. This part of the code did not change since then.
[Test Case]
* Install lucid
* Install python-software-properties:
apt-get install python-software-properties
* add ubuntu-ha-maintainers lucid ppa and update repo:
apt-add-repository ppa:ubuntu-ha-maintainers/ppa ; 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 . |
|
| 2012-06-08 07:34:23 |
Ante Karamatić |
description |
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
[Impact]
Remove potential and demonstratable deadlocks in glib code.
[Development Fix]
Bug is fixed in Ubuntu 11.04 and later.
[Stable Fix]
Proposed fix is cherry picked from the, at the time, latest version of glib. This part of the code did not change since then.
[Test Case]
* Install lucid
* Install python-software-properties:
apt-get install python-software-properties
* add ubuntu-ha-maintainers lucid ppa and update repo:
apt-add-repository ppa:ubuntu-ha-maintainers/ppa ; 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 . |
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
[Impact]
Remove potential and demonstratable deadlocks in glib code.
[Development Fix]
Bug is fixed in Ubuntu 11.04 and later by the simple fact that these version have newer version of glib2.0 which contains this fix.
[Stable Fix]
Proposed fix is cherry picked from the upstream's, at the time, latest version of glib. This part of the code did not change since then.
[Test Case]
* Install lucid
* Install python-software-properties:
apt-get install python-software-properties
* add ubuntu-ha-maintainers lucid ppa and update repo:
apt-add-repository ppa:ubuntu-ha-maintainers/ppa ; 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 . |
|
| 2012-06-08 07:36:00 |
Ante Karamatić |
branch unlinked |
lp:~ivoks/ubuntu/maverick/glib2.0/887946 |
|
|
| 2012-07-10 04:14:13 |
Chris Halse Rogers |
glib2.0 (Ubuntu Lucid): status |
Confirmed |
Fix Committed |
|
| 2012-07-10 04:14:17 |
Chris Halse Rogers |
bug |
|
|
added subscriber SRU Verification |
| 2012-07-10 04:14:20 |
Chris Halse Rogers |
tags |
|
verification-needed |
|
| 2012-07-10 05:26:45 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/lucid-proposed/glib2.0 |
|
| 2012-11-15 09:17:52 |
Ante Karamatić |
tags |
verification-needed |
verification-done |
|
| 2012-11-15 16:32:05 |
Brian Murray |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2012-11-15 16:32:12 |
Launchpad Janitor |
glib2.0 (Ubuntu Lucid): status |
Fix Committed |
Fix Released |
|
| 2012-11-15 16:54:54 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/lucid-updates/glib2.0 |
|
