Bug 489954 - When I want to switch to the next of previous month, it will jump to the 3rd next month or 3rd previous month. Same to year and decades.
Summary: When I want to switch to the next of previous month, it will jump to the 3rd ...
Status: RESOLVED DUPLICATE of bug 487631
Alias: None
Product: plasmashell
Classification: Plasma
Component: Digital Clock (show other bugs)
Version: master
Platform: Manjaro Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-07-09 02:03 UTC by wznmickey
Modified: 2024-07-09 16:35 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description wznmickey 2024-07-09 02:03:48 UTC 
***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY
When I want to switch to the next of previous month, it will jump to the 3rd next month or 3rd previous month.
Same to year and decades.

For example, If I am in July now, I would jump to April or October.
If I am in 2024, I would jump to 2021 or 2027.

STEPS TO REPRODUCE
1. Open the tab
2. Press the left or right button at the right-top place.

OBSERVED RESULT
It will go to wrong months.

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows:  NA
macOS: NA
Linux/KDE Plasma: Yes. 6.6.34-1-MANJARO (64bit) in X11.
(available in About System)
KDE Plasma Version: 6.0.5
KDE Frameworks Version:6.3.0 
Qt Version: 6.7.1

ADDITIONAL INFORMATION
Comment 1 cwo 2024-07-09 16:35:29 UTC 
Thank you for the bug report! This issue has already been fixed, the fix is available in Plasma version 6.1.0 and higher.

If you can still observe this happening after upgrading to the new version, please feel free to reopen this bug.

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