I just did it, the basic conditions seem to be: - lots of apps open taking up more than physical RAM requires swaping to allow update-manager to load (this is always true on my machine) - hit the icon multiple times before update-manager can load
This suggests to me that a race condition is created where the notifier assumes that running the manager is atomic, but if the system has not managed to free the ram to create the job, notifier is happy to initiate another one, since no manager currently exists. In some sense notifier "does" what I want, but not for those of us living beyond our means RAM wise. -- menubar alert does not limit concurrent execution https://bugs.launchpad.net/bugs/296832 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
