Bug 447364 - Unable to set current time manually
Summary: Unable to set current time manually
Status: REOPENED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_clock (show other bugs)
Version: 5.23.4
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Paul Campbell
URL: https://github.com/systemd/systemd/is...
Keywords:
: 462380 464057 (view as bug list)
Depends on:
Blocks:
 
Reported: 2021-12-22 02:05 UTC by eo
Modified: 2023-07-29 17:55 UTC (History)
8 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Unable to set current time manually (43.52 KB, image/jpeg)
2021-12-22 02:05 UTC, eo 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description eo 2021-12-22 02:05:14 UTC 
Created attachment 144773 [details]
Unable to set current time manually

SUMMARY
Error when disabling "Set date and time automatically" 

Error: Unable to set current time


STEPS TO REPRODUCE
1. Open system settings > regional settings > Date & time.  
2. Untick "Set date and time automatically".
3. click apply. 

OBSERVED RESULT
Error: Unable to set current time

EXPECTED RESULT
manual date and time will take effect.

SOFTWARE/OS VERSIONS 
Linux: 5.15.10-arch1-1 (64-bit)
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.89.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Comment 1 David Edmundson 2021-12-24 15:49:15 UTC 
please include output from running systemsettings5 in a terminal
Comment 2 eo 2021-12-29 19:21:23 UTC 
(In reply to David Edmundson from comment #1)
> please include output from running systemsettings5 in a terminal

╰─ systemsettings5                                                                                                                                ─╯
QQmlEngine::setContextForObject(): Object already has a QQmlContext
QQmlEngine::setContextForObject(): Object already has a QQmlContext
qml: The item SubCategoryPage_QMLTYPE_111(0x561e159f79c0) is already in the PageRow
kf.coreaddons: "Could not load plugin from "
qml: The item SubCategoryPage_QMLTYPE_111(0x561e159f79c0) is already in the PageRow
Failed to set current time "org.freedesktop.timedate1.AutomaticTimeSyncEnabled" "Previous request is not finished, refusing."
kf.coreaddons: "Could not load plugin from "
Comment 3 David Edmundson 2021-12-29 22:18:29 UTC 
>Failed to set current time "org.freedesktop.timedate1.AutomaticTimeSyncEnabled"
"Previous request is not finished, refusing."


That error comes from timedated. Can you confirm it works when using timedatectl
Comment 4 eo 2021-12-30 17:06:50 UTC 
From what i observed, changes seems to take effect even if there is an Error: Unable to set current time.

-when date and time is set automatically.

╰─ timedatectl                                                                                                                                    ─╯

               Local time: Fri 2021-12-31 01:00:55 PST
           Universal time: Thu 2021-12-30 17:00:55 UTC
                 RTC time: Fri 2021-12-31 01:00:54
                Time zone: Asia/Manila (PST, +0800)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: yes



-when date and time is set manually.

╰─ timedatectl                                                                                                                                    ─╯

               Local time: Fri 2021-12-31 01:01:06 PST
           Universal time: Thu 2021-12-30 17:01:06 UTC
                 RTC time: Fri 2021-12-31 01:01:05
                Time zone: Asia/Manila (PST, +0800)
System clock synchronized: yes
              NTP service: inactive
          RTC in local TZ: yes
Comment 5 eo 2021-12-30 17:47:38 UTC 
no errors when using command
timedatectl set-ntp false
Comment 6 David Edmundson 2021-12-30 21:15:58 UTC 
I am an absolute idiot.
https://github.com/systemd/systemd/issues/17739

I investigated all this a year ago! Completely forgot.

I thought I did a local workaround, but maybe my brain is failing there too.
Comment 7 eo 2022-02-24 19:23:58 UTC 
will this bug be fixed.. tried a clean install just now and it's still the same. i know it's not a big issue but still hopeful that to get it fixed in the future.
Comment 8 eo 2022-06-21 21:42:02 UTC 
issue is occurring again.
Comment 9 Nicolas Fella 2022-12-04 22:15:17 UTC 
*** Bug 462380 has been marked as a duplicate of this bug. ***
Comment 10 yizel7 2023-01-10 19:15:57 UTC 
I can confirm i cannot set the time manually on a fresh install. Not a good first impression when i was trying to help my friend get into linux.
Comment 11 Nate Graham 2023-01-10 21:42:34 UTC 
*** Bug 464057 has been marked as a duplicate of this bug. ***