Bug 484805 - Wrong date calculation in message list
Summary: Wrong date calculation in message list
Status: RESOLVED DUPLICATE of bug 484119
Alias: None
Product: kmail2
Classification: Applications
Component: message list (show other bugs)
Version: 6.0.1
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-03-31 08:35 UTC by Axel Braun
Modified: 2024-10-04 06:09 UTC (History)
2 users (show)

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

Attachments
messge list with wrong dates (126.26 KB, image/png)
2024-03-31 08:35 UTC, Axel Braun 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Axel Braun 2024-03-31 08:35:28 UTC 
Created attachment 167979 [details]
messge list with wrong dates

Recent kmail shows wrong dates: It sorts yesterdays messages correctly (Gestern = yesterday) but shows emails as from 'today' = Heute
Pls see screenshot

Operating System: openSUSE Tumbleweed 20240328
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.3
Kernel Version: 6.8.1-1-default (64-bit)
Graphics Platform: Wayland
Comment 1 Laurent Montel 2024-03-31 13:06:20 UTC 
Which theme do you use ?
Which account type do you use ?
Comment 2 Axel Braun 2024-03-31 13:08:57 UTC 
(In reply to Laurent Montel from comment #1)
> Which theme do you use ?

openSUSE - its preinstalled

> Which account type do you use ?

IMAP
Comment 3 Laurent Montel 2024-03-31 15:53:55 UTC 
Opensuse has a specific kmail/threading theme ?
Comment 4 Axel Braun 2024-03-31 17:04:05 UTC 
(In reply to Laurent Montel from comment #3)
> Opensuse has a specific kmail/threading theme ?

With Theme I associate something like breeze - what do you mean?
Comment 5 Laurent Montel 2024-03-31 18:39:28 UTC 
kmail-->display->list of message -> "style"...
Comment 6 Axel Braun 2024-04-01 06:47:32 UTC 
classic theme
Comment 7 Christoph Erhardt 2024-10-04 06:09:14 UTC 

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