[Bug 570583] Re: does not check all required locks in is_package_system_locked

Ubuntu QA's Bug Bot bug-stats at murraytwins.com
Mon Sep 19 21:14:58 UTC 2011


** Tags added: testcase

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubuntu-system-service in
Ubuntu.
https://bugs.launchpad.net/bugs/570583

Title:
  does not check all required locks in is_package_system_locked

Status in “ubuntu-system-service” package in Ubuntu:
  Fix Released
Status in “ubuntu-system-service” source package in Lucid:
  Fix Released

Bug 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 "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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-service/+bug/570583/+subscriptions




More information about the foundations-bugs mailing list