[korganizer] [Bug 483823] New event button does not use currently selected date as default
https://bugs.kde.org/show_bug.cgi?id=483823 Nick changed: What|Removed |Added CC||mobile.har...@outlook.com --- Comment #1 from Nick --- Just tried to duplicate this on Neon but korganiser crashes when I execute step 2! Bug report raised. If I can get past step 2 I'll report back. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 484327] Bad initial window sizes
https://bugs.kde.org/show_bug.cgi?id=484327 --- Comment #1 from Kevin Krammer --- New observation: main window and composer seem to access the same size information. I just realized that the observed 760x830 mentioned in the report are the size of my non-maximized composer window. To verify I resized the composer to some new shape and then quit Kmail after closing the composer. On restart Kmail came up with that new geometry. If I do not un-maximize the composer and quit Kmail then it restarts in maximized state. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 484328] New: Kmail config dialog takes about 40 seconds to show up
https://bugs.kde.org/show_bug.cgi?id=484328 Bug ID: 484328 Summary: Kmail config dialog takes about 40 seconds to show up Classification: Applications Product: kmail2 Version: 6.0.1 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: config dialog Assignee: kdepim-bugs@kde.org Reporter: kram...@kde.org Target Milestone: --- Created attachment 167655 --> https://bugs.kde.org/attachment.cgi?id=167655=edit Kmail log entries from journald SUMMARY Since upgrade to 6.0 opening the Kmail config dialog for the first time after startup takes 30-40 seconds, with CPU load spiking. Most likely related to querying font information because it spams the log with OpenType messages (see attachment). STEPS TO REPRODUCE 1. Start Kmail 2. Settings -> Configure Kmail 3. OBSERVED RESULT 30-40 seconds of high CPU load before dialog shows up. log (via journalctl) gets hundreds of entries related to OpenType EXPECTED RESULT Config dialog shows up in a couple of seconds. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Neon 6.0 (available in About System) KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 484327] New: Bad initial window sizes
https://bugs.kde.org/show_bug.cgi?id=484327 Bug ID: 484327 Summary: Bad initial window sizes Classification: Applications Product: kmail2 Version: 6.0.1 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: kram...@kde.org Target Milestone: --- SUMMARY After upgrading to 6.0 the initial size of the Kmail main window, the composer window and the attachment selection window are not what I would expect them to be. When I start Kmail after logging in, it appears in a rather small window, about 760x830. I had it maximized before ending the session and I can reproduce this even when just quitting Kmail and restarting it. So I have to maximize it after every start. Once maximized, it will open composer windows also maximized (it does not do that before it got maximized itself) After manually unmaximizing the composer window (and closing it either by canceling or sending) any new composer is created in non-maximized form for a while (have not been able to determine yet when it resets to maximized). In almost ironic opposition, the dialog for selecting attachments is always opened with minimal size (screenshot attached). STEPS TO REPRODUCE 1. Start Kmail 2. Open composer (new mail or reply, shortcut or toolbar) OBSERVED RESULT Kmail main window does not restore its maximized state. Composer window seems to follow the main windows maximized state. Attachment dialog is too small. EXPECTED RESULT Kmail main window is restored to the size it had when closing. Composer opens in the size it had last. Attachment dialog can be used right away without needing to be resized to actually see files. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon 6.0 (available in About System) KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 483737] akregator icon, in systray does not follow dark breeze theme.
https://bugs.kde.org/show_bug.cgi?id=483737 Nick changed: What|Removed |Added CC||mobile.har...@outlook.com --- Comment #2 from Nick --- Created attachment 167641 --> https://bugs.kde.org/attachment.cgi?id=167641=edit Confirmed Confirmed on Neon 6.0.2 / Wayland / Akregator .deb 24.02.1. -- You are receiving this mail because: You are the assignee for the bug.
[frameworks-kcalendarcore] [Bug 484306] New: The testdateserialization test fails since the beginning of March
https://bugs.kde.org/show_bug.cgi?id=484306 Bug ID: 484306 Summary: The testdateserialization test fails since the beginning of March Classification: Frameworks and Libraries Product: frameworks-kcalendarcore Version: 5.114.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: kde-ident...@planete-kraus.eu Target Milestone: --- SUMMARY Hello! When building kcalendarcore 5.114.0 for Guix, we observe a consistent failure since the beginning of March. Maybe it will work again in April? STEPS TO REPRODUCE 1. Wait after February 29, 2024 2. Run the test suite OBSERVED RESULT Test testdateserialization fails with the following output: * Start testing of TestDateSerialization * Config: Using QtTest library 5.15.10, Qt 5.15.10 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 11.3.0), unknown unknown PASS : TestDateSerialization::initTestCase() PASS : TestDateSerialization::testNewRecurringTodo() FAIL! : TestDateSerialization::testTodoCompletedOnce() Compared values are not the same Actual (todo->dtStart(false)) : 2024/04/01 00:00:00.000[CEST] Expected (startDate.addMonths(1)): 2024/04/01 01:00:00.000[CEST] Loc: [/tmp/guix-build-kcalendarcore-5.114.0.drv-0/kcalendarcore-5.114.0/autotests/testdateserialization.cpp(79)] PASS : TestDateSerialization::testUTCOffset() PASS : TestDateSerialization::cleanupTestCase() Totals: 4 passed, 1 failed, 0 skipped, 0 blacklisted, 4ms * Finished testing of TestDateSerialization * EXPECTED RESULT The test should pass. SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A Linux/KDE Plasma: This is a testsuite failure (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.114.0 Qt Version: ADDITIONAL INFORMATION This links shows all build failures occur in March: http://ci.guix.gnu.org/search?query=kcalendarcore It may resume working correctly in April, I don’t know. I am not a regular KDE user, so I hope the provided information is useful to you, but do not hesitate to ask for more precise information. Best regards, Vivien -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 484281] Some UI elements do not use localised key names
https://bugs.kde.org/show_bug.cgi?id=484281 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel --- in kaddressbook here it's translated same in kmail. dnd is translated too. -- You are receiving this mail because: You are the assignee for the bug.
