Univention Bugzilla – Bug 31382
AppCenter does not prevent concurrent operations in same session
Last modified: 2013-07-05 15:41:36 CEST
(In reply to comment #6)
> From Bug 30155:
> > Upon opening the module, the module should check for an ongoing installation,
> > and a progressbar should be prompted in that case.
> This should be addressed via this bug, as well.
This needs to be done,
if i start the agorum app installation and then close the browser, open the
browser and logon to the UMC, i can open the appcenter module and start the
installation of another app (or agorum again), then weird things happen and i
end up with
-> apt-get -f install
E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct
+++ This bug was initially created as a clone of Bug #30611 +++
Same session -> same process id -> locking mechanism fails.
Explicit check for running PackageManager added in:
Changelog, YAML updated
If a concurrent operation is noticed during App Center startup a progress bar is shown. If it is noticed just before a concurrent execution an error message is displayed. Note that the second progressbar is not very accurate as the information fetched from the server is divided by the number of concurrent app centers of the very same session. So some percentage infos may be missed. But it should work and is of course much better than a broken dpkg state.
No, still able to "install" another app after relogin (browser closed after i started an app installation). I think the second installation was terminated by the appcenter (because the first installation still runs and blocks the second installation) and the first installation runs just fine, but i got no error message, no progress bar no nothing?
Yes, just a usability flaw. The App Center was not allowed to install something. But the error occurred too late, the response was already sent to the client.
Nevertheless, fixed in
OK - errata3.1-1
OK - yaml
OK - ucs3.1-2
OK - changelog
*** Bug 29864 has been marked as a duplicate of this bug. ***