Bug 314224

Summary: clock freezes after modifying layout.js
Product: [Plasma] plasma4 Reporter: adrelanos
Component: widget-clockAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal    
Priority: NOR    
Version: 4.8.4   
Target Milestone: ---   
Platform: Debian testing   
OS: Linux   
Latest Commit: Version Fixed In:

Description adrelanos 2013-02-01 00:11:11 UTC
I modified the file
"/usr/share/kde4/apps/plasma/layout-templates/org.kde.plasma-desktop.defaultPanel/contents/layout.js".
(Just for ease of testing, I know about kde path stacking.)

Original File (from Debian Wheezy):

------------------------------------------------------------

var panel = new Panel
if (panelIds.length == 1) {
    // we are the only panel, so set the location for the user
    panel.location = 'bottom'
}

panel.height = screenGeometry(panel.screen).height > 1024 ? 35 : 27
panel.addWidget("launcher")
panel.addWidget("org.kde.showActivityManager")
panel.addWidget("pager")
tasks = panel.addWidget("tasks")
panel.addWidget("systemtray")
panel.addWidget("digital-clock")

tasks.currentConfigGroup = new Array("Launchers")
tasks.writeConfig("browser", "preferred://browser, , , ")
tasks.writeConfig("filemanager", "preferred://filemanager, , , ")

------------------------------------------------------------

Diff for Modified File:

------------------------------------------------------------

--- 1   2012-12-13 17:44:13.412226851 +0000
+++ 2   2012-12-13 17:44:34.532227597 +0000
@@ -10,7 +10,27 @@ panel.addWidget("org.kde.showActivityMan
 panel.addWidget("pager")
 tasks = panel.addWidget("tasks")
 panel.addWidget("systemtray")
-panel.addWidget("digital-clock")
+
+// Whonix changes
+clock = panel.addWidget("digital-clock")
+clock.writeConfig("Share", "false")
+clock.writeConfig("announceInterval", "0")
+clock.writeConfig("calendarType", "locale")
+clock.writeConfig("dateStyle", "4")
+clock.writeConfig("defaultTimezone", "UTC")
+clock.writeConfig("displayEvents", "true")
+clock.writeConfig("displayHolidays", "false")
+clock.writeConfig("holidaysRegions", "")
+clock.writeConfig("holidaysRegionsDaysOff", "")
+clock.writeConfig("plainClockDrawShadow", "true")
+clock.writeConfig("plainClockFont", "DejaVu Sans,14,-1,0,50,0,0,0,0,0")
+clock.writeConfig("showSeconds", "true")
+clock.writeConfig("showTimezone", "true")
+clock.writeConfig("timeZones", "UTC")
+clock.writeConfig("timezone", "UTC")
+clock.writeConfig("useCustomColor", "false")
+clock.writeConfig("useCustomShadowColor", "false")
+// End of Whonix changes

 tasks.currentConfigGroup = new Array("Launchers")
 tasks.writeConfig("browser", "preferred://browser, , , ")

------------------------------------------------------------

Diff for "Lighter" modified File:

------------------------------------------------------------

--- 1   2012-12-13 17:44:13.412226851 +0000
+++ 3   2012-12-13 17:44:59.608228916 +0000
@@ -10,7 +10,17 @@ panel.addWidget("org.kde.showActivityMan
 panel.addWidget("pager")
 tasks = panel.addWidget("tasks")
 panel.addWidget("systemtray")
-panel.addWidget("digital-clock")
+
+// Whonix changes
+clock = panel.addWidget("digital-clock")
+clock.writeConfig("dateStyle", "4")
+clock.writeConfig("defaultTimezone", "UTC")
+clock.writeConfig("displayHolidays", "false")
+clock.writeConfig("showSeconds", "true")
+clock.writeConfig("showTimezone", "true")
+clock.writeConfig("timeZones", "UTC")
+clock.writeConfig("timezone", "UTC")
+// End of Whonix changes

 tasks.currentConfigGroup = new Array("Launchers")
 tasks.writeConfig("browser", "preferred://browser, , , ")

------------------------------------------------------------

Both times, the clock is configured as I wish, but the seconds are
frozen. To get it running it is required to view the digital clock
settings and press ok. Then it's working.

Reproducible: Always

Steps to Reproduce:
1. open the file:
kdesudo kwrite /usr/share/kde4/apps/plasma/layout-templates/org.kde.plasma-desktop.defaultPanel/contents/layout.js

2. add the following content:

var panel = new Panel
if (panelIds.length == 1) {
    // we are the only panel, so set the location for the user
    panel.location = 'bottom'
}

panel.height = screenGeometry(panel.screen).height > 1024 ? 35 : 27
panel.addWidget("launcher")
panel.addWidget("org.kde.showActivityManager")
panel.addWidget("pager")
tasks = panel.addWidget("tasks")
panel.addWidget("systemtray")
panel.addWidget("digital-clock")

// Whonix changes
clock = panel.addWidget("digital-clock")
clock.writeConfig("Share", "false")
clock.writeConfig("announceInterval", "0")
clock.writeConfig("calendarType", "locale")
clock.writeConfig("dateStyle", "4")
clock.writeConfig("defaultTimezone", "UTC")
clock.writeConfig("displayEvents", "true")
clock.writeConfig("displayHolidays", "false")
clock.writeConfig("holidaysRegions", "")
clock.writeConfig("holidaysRegionsDaysOff", "")
clock.writeConfig("plainClockDrawShadow", "true")
clock.writeConfig("plainClockFont", "DejaVu Sans,14,-1,0,50,0,0,0,0,0")
clock.writeConfig("showSeconds", "true")
clock.writeConfig("showTimezone", "true")
clock.writeConfig("timeZones", "UTC")
clock.writeConfig("timezone", "UTC")
clock.writeConfig("useCustomColor", "false")
clock.writeConfig("useCustomShadowColor", "false")
// End of Whonix changes

tasks.currentConfigGroup = new Array("Launchers")
tasks.writeConfig("browser", "preferred://browser, , , ")
tasks.writeConfig("filemanager", "preferred://filemanager, , , ")

3. create a new user account, for example: sudo adduser testuser

4. login as testuser
Actual Results:  
The clock is configured as I wish, but the seconds are
frozen. To get it running it is required to view the digital clock
settings and press ok. Then it's working.

Expected Results:  
The clock is configured as I wish and I can see second by second pass by.
Comment 1 Nate Graham 2018-06-08 19:49:46 UTC
Hello!

This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug is already resolved in Plasma 5.

Accordingly, we hope you understand why we must close this bug report. If the issue described  here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting

If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging

Thanks for your understanding!

Nate Graham