Bug 36809

Summary: computerroom settings fails
Product: UCS Reporter: Florian Best <best>
Component: univention-libAssignee: Florian Best <best>
Status: CLOSED FIXED QA Contact: Sönke Schwardt-Krummrich <schwardt>
Severity: normal    
Priority: P5 CC: gohmann, klaeser, schwardt
Version: UCS 3.2   
Target Milestone: UCS 4.0   
Hardware: Other   
OS: Linux   
See Also: https://forge.univention.org/bugzilla/show_bug.cgi?id=31319
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):
Max CVSS v3 score:
Bug Depends on:    
Bug Blocks: 36815, 37060    

Description Florian Best univentionstaff 2014-11-18 13:31:49 CET
1. When setting some settings they got applied. After opening the settings dialog in UMC again the time changes back as if no settings were applied.
The settings/get request responses with:
"period": "14:27:33.317781"
→ is this format correct, has it changed to 4.0?

2. It's not possible to switch settings from "Kein Internet" back to "Standard (globale Einstellungen)".
Comment 1 Florian Best univentionstaff 2014-11-18 15:05:00 CET
This was caused by the changes in Bug #31319.
The computerroom module uses the atjob comments to identify the jobs for the current room. The change from that bug stripped the newline with line[:-1], the new code used .splitlines().
Comment 2 Florian Best univentionstaff 2014-11-18 15:22:30 CET
fixed in svn55934 univention-lib (4.0.4-1)
Comment 3 Sönke Schwardt-Krummrich univentionstaff 2014-11-19 16:35:42 CET
OK: code change
OK: functionality
changelog entry is not required; bug was introduced in interims version
Comment 4 Stefan Gohmann univentionstaff 2014-11-26 06:54:19 CET
UCS 4.0-0 has been released:
 http://docs.univention.de/release-notes-4.0-0-en.html
 http://docs.univention.de/release-notes-4.0-0-de.html

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