| 2010-04-27 08:51:00 |
Michael Vogt |
bug |
|
|
added bug |
| 2010-04-27 08:51:21 |
Michael Vogt |
nominated for series |
|
Ubuntu Lucid |
|
| 2010-04-27 08:51:21 |
Michael Vogt |
bug task added |
|
ubuntu-system-service (Ubuntu Lucid) |
|
| 2010-04-27 08:51:57 |
Michael Vogt |
ubuntu-system-service (Ubuntu Lucid): status |
New |
Confirmed |
|
| 2010-04-27 08:51:59 |
Michael Vogt |
ubuntu-system-service (Ubuntu Lucid): importance |
Undecided |
Medium |
|
| 2010-04-27 08:52:03 |
Michael Vogt |
ubuntu-system-service (Ubuntu Lucid): milestone |
|
lucid-updates |
|
| 2010-04-27 08:52:08 |
Michael Vogt |
ubuntu-system-service (Ubuntu Lucid): assignee |
|
Michael Vogt (mvo) |
|
| 2010-04-27 08:52:17 |
Launchpad Janitor |
branch linked |
|
lp:system-service |
|
| 2010-04-27 08:59:38 |
Michael Vogt |
description |
Binary package hint: ubuntu-system-service
The dbus call for "is_package_system_locked" does not check all possible locks.
This can lead to update-notifier (that uses this interface) to auto-opening update-manager when there is
a package management operation already in progress. Its a bit of a corner case as most package managers
take /var/lib/dpkg/lock (and that is already tested). But should be fixed nevertheless. |
Binary package hint: ubuntu-system-service
The dbus call for "is_package_system_locked" does not check all possible locks.
This can lead to update-notifier (that uses this interface) to auto-opening update-manager when there is
a package management operation already in progress. Its a bit of a corner case as most package managers
take /var/lib/dpkg/lock (and that is already tested). But should be fixed nevertheless.
TEST CASE:
1. use lucid and log into desktop
2. open two terminals
3. run "while true; do apt-get update; done" in the first
4. run "NO_FAKE_STAT=1 faketime -f +10d update-notifier" and verify that update-manager opens
5. close the terminals
6. install new ubuntu-system-servce and run "sudo killall system-service-d" to ensure the old one is gone
7. run "gconftool --unset /apps/update-manager/launch_time" to ensure the launch time is reset
8. repeat steps 3,4 and verify that update-manager does not open this time |
|
| 2010-04-27 09:01:01 |
Michael Vogt |
description |
Binary package hint: ubuntu-system-service
The dbus call for "is_package_system_locked" does not check all possible locks.
This can lead to update-notifier (that uses this interface) to auto-opening update-manager when there is
a package management operation already in progress. Its a bit of a corner case as most package managers
take /var/lib/dpkg/lock (and that is already tested). But should be fixed nevertheless.
TEST CASE:
1. use lucid and log into desktop
2. open two terminals
3. run "while true; do apt-get update; done" in the first
4. run "NO_FAKE_STAT=1 faketime -f +10d update-notifier" and verify that update-manager opens
5. close the terminals
6. install new ubuntu-system-servce and run "sudo killall system-service-d" to ensure the old one is gone
7. run "gconftool --unset /apps/update-manager/launch_time" to ensure the launch time is reset
8. repeat steps 3,4 and verify that update-manager does not open this time |
Binary package hint: ubuntu-system-service
The dbus call for "is_package_system_locked" does not check all possible locks.
This can lead to update-notifier (that uses this interface) to auto-opening update-manager when there is
a package management operation already in progress. Its a bit of a corner case as most package managers
take /var/lib/dpkg/lock (and that is already tested). But should be fixed nevertheless.
TEST CASE:
1. use lucid and log into desktop
2. open two terminals
3. run "while true; do apt-get update; done" in the first
4. run "NO_FAKE_STAT=1 faketime -f +10d update-notifier" and verify that update-manager opens
5. close the terminals
6. install new ubuntu-system-servce and run "sudo killall system-service-d" to ensure the old one is gone
7. run "gconftool --unset /apps/update-manager/launch_time" to ensure the launch time is reset
8. repeat steps 3,4 and verify that update-manager does not open this time
9. close the terminals that was opened in step 3
10. repeat step 4, verify that update-manager now auto-opens
|
|
| 2010-04-27 09:03:00 |
Michael Vogt |
ubuntu-system-service (Ubuntu Lucid): status |
Confirmed |
Fix Committed |
|
| 2010-04-29 05:46:50 |
Martin Pitt |
tags |
|
verification-needed |
|
| 2010-04-29 06:18:21 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/lucid-proposed/ubuntu-system-service |
|
| 2010-05-03 08:21:26 |
Launchpad Janitor |
ubuntu-system-service (Ubuntu Lucid): status |
Fix Committed |
Fix Released |
|
| 2010-05-03 08:22:51 |
Martin Pitt |
ubuntu-system-service (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2010-05-03 08:23:57 |
Martin Pitt |
ubuntu-system-service (Ubuntu Lucid): status |
Fix Released |
Fix Committed |
|
| 2010-05-13 07:20:22 |
Paul Elliott |
tags |
verification-needed |
verification-failed |
|
| 2010-07-20 09:19:16 |
Michael Vogt |
description |
Binary package hint: ubuntu-system-service
The dbus call for "is_package_system_locked" does not check all possible locks.
This can lead to update-notifier (that uses this interface) to auto-opening update-manager when there is
a package management operation already in progress. Its a bit of a corner case as most package managers
take /var/lib/dpkg/lock (and that is already tested). But should be fixed nevertheless.
TEST CASE:
1. use lucid and log into desktop
2. open two terminals
3. run "while true; do apt-get update; done" in the first
4. run "NO_FAKE_STAT=1 faketime -f +10d update-notifier" and verify that update-manager opens
5. close the terminals
6. install new ubuntu-system-servce and run "sudo killall system-service-d" to ensure the old one is gone
7. run "gconftool --unset /apps/update-manager/launch_time" to ensure the launch time is reset
8. repeat steps 3,4 and verify that update-manager does not open this time
9. close the terminals that was opened in step 3
10. repeat step 4, verify that update-manager now auto-opens
|
Binary package hint: ubuntu-system-service
The dbus call for "is_package_system_locked" does not check all possible locks.
This can lead to update-notifier (that uses this interface) to auto-opening update-manager when there is
a package management operation already in progress. Its a bit of a corner case as most package managers
take /var/lib/dpkg/lock (and that is already tested). But should be fixed nevertheless.
TEST CASE:
1. use lucid and log into desktop
2. open two terminals
3. run "while true; do apt-get update; done" in the first
4. run "killall update-notifier; NO_FAKE_STAT=1 faketime -f +10d update-notifier" and verify that update-manager opens
5. close the terminals
6. install new ubuntu-system-servce and run "sudo killall system-service-d" to ensure the old one is gone
7. run "gconftool --unset /apps/update-manager/launch_time" to ensure the launch time is reset
8. repeat steps 3,4 and verify that update-manager does not open this time
9. close the terminals that was opened in step 3
10. repeat step 4, verify that update-manager now auto-opens
|
|
| 2010-07-20 09:23:18 |
Michael Vogt |
ubuntu-system-service (Ubuntu Lucid): status |
Fix Committed |
In Progress |
|
| 2010-07-20 09:23:23 |
Michael Vogt |
ubuntu-system-service (Ubuntu Lucid): status |
In Progress |
Fix Committed |
|
| 2010-07-20 09:23:32 |
Michael Vogt |
tags |
verification-failed |
verification-needed |
|
| 2010-07-28 08:14:52 |
Martin Pitt |
tags |
verification-needed |
verification-done |
|
| 2010-07-28 08:15:20 |
Launchpad Janitor |
ubuntu-system-service (Ubuntu Lucid): status |
Fix Committed |
Fix Released |
|
| 2011-09-19 21:14:58 |
Ubuntu Foundations Team Bug Bot |
tags |
verification-done |
testcase verification-done |
|
