Bug 39688 - Repository settings and package management modules cannot be opened
Repository settings and package management modules cannot be opened
Status: CLOSED FIXED
Product: UCS
Classification: Unclassified
Component: UMC - App-Center
UCS 4.1
Other Linux
: P5 normal (vote)
: UCS 4.1
Assigned To: Dirk Wiesenthal
Eduard Mai
: interim-2
Depends on:
Blocks: 39929
  Show dependency treegraph
 
Reported: 2015-10-30 16:04 CET by Alexander Kläser
Modified: 2015-11-17 12:11 CET (History)
1 user (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): Error handling
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Kläser univentionstaff 2015-10-30 16:04:23 CET
When opening either the package management or the repository settings module, I received the following error and the package remains empty:

"TypeError: Cannot read property '_searchSidebar' of undefined at declare.postCreate (http://192.168.0.188:8011/univention-management-console/js_$20153010154401$/umc/modules/appcenter.js:88:23)
Comment 1 Florian Best univentionstaff 2015-10-30 16:44:13 CET
I observed this error somewhen too in the regular app center or apps module.

I don't remember anymore but I think it was after (un)installing a app due to autorefresh.
Comment 2 Dirk Wiesenthal univentionstaff 2015-10-31 00:33:50 CET
Fixed in
  univention-appcenter 5.0.14-6.44.201510310030
Comment 3 Eduard Mai univentionstaff 2015-11-10 15:31:22 CET
Fix - OK
debian/changelog - OK
Comment 4 Stefan Gohmann univentionstaff 2015-11-17 12:11:55 CET
UCS 4.1 has been released:
 https://docs.software-univention.de/release-notes-4.1-0-en.html
 https://docs.software-univention.de/release-notes-4.1-0-de.html

If this error occurs again, please use "Clone This Bug".