Bug 344570 (Jim)

Summary: Date & Time crash when updating TZ
Product: [Unmaintained] plasma4 Reporter: Jim <snafuxnj>
Component: widget-systemtrayAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: snafuxnj
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: crash report

Description Jim 2015-02-25 21:30:51 UTC
Application: kcmshell4 (4.14.1)
KDE Platform Version: 4.14.1
Qt Version: 4.8.6
Operating System: Linux 3.16.0-30-generic x86_64
Distribution: Ubuntu 14.10

-- Information about the crash:
- What I was doing when the application crashed:
right click on clock in taskbar -> Adjust Date and Time -> toggle """"""Set date and time automatically -> Click Time Zone tab -> _verify TZ_ -> Click Apply -> Click OK (iirc) == CRASH
Comment 1 Jim 2015-02-25 21:31:17 UTC
Created attachment 91296 [details]
crash report
Comment 2 Jim 2015-02-25 21:33:40 UTC
(In reply to Jim from comment #0)
> Application: kcmshell4 (4.14.1)
> KDE Platform Version: 4.14.1
> Qt Version: 4.8.6
> Operating System: Linux 3.16.0-30-generic x86_64
> Distribution: Ubuntu 14.10
> 
> -- Information about the crash:
> - What I was doing when the application crashed:
> right click on clock in taskbar -> Adjust Date and Time -> toggle """"""Set
> date and time automatically -> Click Time Zone tab -> _verify TZ_ -> Click
> Apply -> Click OK (iirc) == CRASH

Note that after I attempted the above steps, I received the following alert:

Unable to authenticate/execute the action: 6, 

Additionally, the date/time did NOT update. So, I attempted to make the change again using the same steps as mentioned above. I received the same error and crash.
Comment 3 Jim 2015-02-25 21:40:13 UTC
I talked to Dr Google who said that one can fix the issue by running a dpkg-reconfigure. However, I decided to do it via "Digital Clock Settings" and setting my local TZ. So, there seems to be some disparity here. Nevertheless, it's a non-blocking issue.
Comment 4 Christoph Feck 2015-02-25 23:36:09 UTC

*** This bug has been marked as a duplicate of bug 344558 ***