Univention Bugzilla – Bug 42095
There is no module available for the authenticated user __systemsetup__.
Last modified: 2016-09-29 17:31:09 CEST
After installing incl. S4 + updates, using ucs-kt-get on frosta (98) [UCS: 4.1-0 amd64 - generic], after the successful run of system-setup I ended up with a popup "There is no module available for the authenticated user __systemsetup__." I couldn't do anything in the window anymore except CTRL+W. The system seems to be perfectly installed and fine.
Also reported by customer via phone call. Customer installed with UCS 4.1-3 ISO, "update at end of installation" was checked.
Please have a look.
This is a regression introduced by http://errata.software-univention.de/ucs/4.1/234.html The way firefox was closed after system-setup-boot is finished has been changed. Before errata 234, a cleanup script kills the firefox process and the welcome screen shows up. This was changed, so the installation that was started with system-setup-boot < 9.0.4-33.977.201607221051 has the old JS frontend, which just waits to be killed after clicking on finish. System should be fully useable afterwards, just the firefox process is still running. (In reply to Michael Grandjean from comment #1) > Customer installed with UCS 4.1-3 ISO, "update at end of installation" was > checked. This had to be another install medium, as the 4.1-3 ISO contains the correct system-setup-boot package
AFAIS, there should no reload dialog be displayed... umc.tools.status('ignorePageReload', true) is set in the setup module. If the error occurs, it would be interesting to get the output of umc.tools.status('ignorePageReload'), it should return true as value being set.
I added a check to the u-s-s-boot postinst, which sets system/setup/boot/legacyfrontend to true, if the package is updated from an old version that will break system setup. If the variable is set, firefox will be stopped "the old way" by killing the process in 95_remove_setup_status_file. r71983 univention-system-setup 9.0.4-37 r71984 yaml
r72101 merge to ucs 4.2
Changes: OK Merge to 4.2-0: OK YAML file: I adapted the entry to be less technical [r72116]
(In reply to Alexander Kläser from comment #7) > Changes: OK > Merge to 4.2-0: OK > YAML file: I adapted the entry to be less technical [r72116] Wrong bug :) ... As discussed, this bug needs to be reopened. For 20-30sec the dialog with a hint for reloading the browser page is still visible. Although the browser session is killed afterwards, this is still somewhat irritating. As discussed, the reason seems to be that the UMC server is restarted. The local firefox browser can login automatically again, however, then it is checked whether the UMC files have been updated. We could create js_$...$ symlinks with older values (read from /var/log/apache2/access.log) via an appliance hook to avoid the message being shown.
r72135 added appliance-hooks.d/10_add_legacy_systemsetup_javascript_links r72136 yaml version 9.0.4-39.983.201608311622 r72137 merge to ucs4.2
r72168: Added plymouth stop call to enable univention-welcome-screen r72169: yaml r72170: merge to ucs4.2
(In reply to Alexander Kläser from comment #8) > [...] > As discussed, this bug needs to be reopened. For 20-30sec the dialog with a > hint for reloading the browser page is still visible. Although the browser > session is killed afterwards, this is still somewhat irritating. This is working fine now, great. I checked it successfully with a 4.1-0 UCS appliance image and with 4.1-3 as well as 4.1-2 installation DVDs. I experienced problems when directly adding the errata-test-repository into /etc/apt/sources.list on the 4.1-0 appliance. However, when adding the repo right at the beginning of the update routine from 4.1-2 to 4.1-3, it worked just fine. The update with an external browser seems fine, too. Changes: OK Merge to 4.2-0: OK YAML file: I adapted the entry to be less technical [r72116]
Just to be precise, the reload popup does not occur, the welcome screen is shown properly, and the internal firefox browser is killed.
*** Bug 41920 has been marked as a duplicate of this bug. ***
<http://errata.software-univention.de/ucs/4.1/244.html>
*** Bug 42010 has been marked as a duplicate of this bug. ***