[Akonadi] [Bug 486874] New: "Akonadi crashed" when applying dark theme
https://bugs.kde.org/show_bug.cgi?id=486874 Bug ID: 486874 Summary: "Akonadi crashed" when applying dark theme Classification: Frameworks and Libraries Product: Akonadi Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: re...@protonmail.ch CC: c...@carlschwan.eu Target Milestone: --- Application: akonadiserver (5.22.3 (22.12.3)) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-21-amd64 x86_64 Windowing System: Wayland Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [KCrashBackend] -- Information about the crash: Upon hitting "Apply" to change to Breeze Dark in Plasma Appearance settings, all open programmes crashed or closed. Error message presented was, "Akonadi crashed". Firefox also crashed. Freetube, Dolphin windows, other programmes' windows, all closed. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Segmentation fault [KCrash Handler] #4 0x56116be331cc in ?? () #5 0x7f0a286dd6f0 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0a286b16cd in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f0a286b4681 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f0a2870a153 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f0a26fd47a9 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7f0a26fd4a38 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7f0a26fd4acc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7f0a28709836 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f0a286b017b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f0a286b82d6 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x56116be30450 in ?? () #16 0x7f0a2824624a in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #17 0x7f0a28246305 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #18 0x56116be32c81 in ?? () [Inferior 1 (process 2317) detached] The reporter indicates this bug may be a duplicate of or related to bug 479341, bug 479342, bug 479344. Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 467147] Falkon and KMail (qtwebengine-based(?)) crash in QtWaylandClient::QWaylandWindow::handleScreensChanged() when DP screen is going to standby or powered off
https://bugs.kde.org/show_bug.cgi?id=467147 oso changed: What|Removed |Added Resolution|FIXED |DUPLICATE --- Comment #10 from oso --- *** This bug has been marked as a duplicate of bug 484326 *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 467147] Falkon and KMail (qtwebengine-based(?)) crash in QtWaylandClient::QWaylandWindow::handleScreensChanged() when DP screen is going to standby or powered off
https://bugs.kde.org/show_bug.cgi?id=467147 oso changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=484326| -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 467147] Falkon and KMail (qtwebengine-based(?)) crash in QtWaylandClient::QWaylandWindow::handleScreensChanged() when DP screen is going to standby or powered off
https://bugs.kde.org/show_bug.cgi?id=467147 oso changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=484326 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 467147] Falkon and KMail (qtwebengine-based(?)) crash in QtWaylandClient::QWaylandWindow::handleScreensChanged() when DP screen is going to standby or powered off
https://bugs.kde.org/show_bug.cgi?id=467147 oso changed: What|Removed |Added Resolution|DUPLICATE |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 486871] New: Can't fetch caldav or carddav from Nextcloud in Fedora 40, driver error
https://bugs.kde.org/show_bug.cgi?id=486871 Bug ID: 486871 Summary: Can't fetch caldav or carddav from Nextcloud in Fedora 40, driver error Classification: Frameworks and Libraries Product: Akonadi Version: 6.0.2 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: DAV Resource Assignee: kdepim-bugs@kde.org Reporter: k...@fuchsnet.ch CC: c...@carlschwan.eu Target Milestone: --- SUMMARY Since re-installing a fresh Fedora 40 after using Fedora 39, I am no longer able to add my nextcloud calendar or addressbooks in akonadi. The error message shown in the window is completely useless (driver error, on German, couldn't get it to show it in English), on the console it's a bit more usefull, org.kde.pim.akonadiserver: Handler exception when handling command FetchCollections on connection akonadi_davgroupware_resource_0 (0x560355340ab0) : Hierarchical RID does not specify an existing collection org.kde.pim.davresource: Unable to fetch collections 320 "Ungültige Antwort des Treibers" STEPS TO REPRODUCE 1. Install Fedora 40 with akonadi 6.0.2 2. Try to add a nextcloud ressource, either via the built in Nextcloud setting in the drop down or by specifying the URLs manually OBSERVED RESULT You get the above error EXPECTED RESULT It works The same nextcloud instance works with other software, e.g. a still running KDE 5.* based kontact on my desktop box, davx on Android etc. Operating System: Fedora Linux 40 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.9-300.fc40.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i5-8265U CPU @ 1.60GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: LENOVO Product Name: 20NQS30W00 System Version: ThinkPad X390 Yoga -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 467147] Falkon and KMail (qtwebengine-based(?)) crash in QtWaylandClient::QWaylandWindow::handleScreensChanged() when DP screen is going to standby or powered off
https://bugs.kde.org/show_bug.cgi?id=467147 oso changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=473020| -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 467147] Falkon and KMail (qtwebengine-based(?)) crash in QtWaylandClient::QWaylandWindow::handleScreensChanged() when DP screen is going to standby or powered off
https://bugs.kde.org/show_bug.cgi?id=467147 oso changed: What|Removed |Added See Also|https://bugs.kde.org/show_b |https://bugs.kde.org/show_b |ug.cgi?id=461886, |ug.cgi?id=473020 |https://bugs.kde.org/show_b | |ug.cgi?id=419492, | |https://bugs.kde.org/show_b | |ug.cgi?id=474811| CC||osobuko...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 486861] New: Memory leak in EWS resource
https://bugs.kde.org/show_bug.cgi?id=486861 Bug ID: 486861 Summary: Memory leak in EWS resource Classification: Frameworks and Libraries Product: Akonadi Version: 6.0.2 Platform: Neon OS: Linux Status: REPORTED Severity: major Priority: NOR Component: EWS Resource Assignee: kdepim-bugs@kde.org Reporter: m_loui...@yahoo.com CC: c...@carlschwan.eu, kri...@op.pl Target Milestone: --- SUMMARY The memory usage of the EWS resource keeps growing until I kill the process. STEPS TO REPRODUCE 1. Configure an EWS resources 2. Sync it 3. Wait a few hours OBSERVED RESULT The akonadi_ews_resource process uses all available RAM and renders the system unusable. On my system, the resource leaks about 1MB/s so I need to restart it after ~1h. EXPECTED RESULT Memory usage is roughly constant. SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.5.0-28-generic (64-bit) Graphics Platform: Wayland Memory: 15.3 Gio of RAM ADDITIONAL INFORMATION My mailbox contains thousands of emails totaling about 1GB. The akonadi log gets filled quickly with the following message: org.kde.pim.ews.client: Failed to process EWS request: I'm willing to investigate more (and find the leak) if someone would tell me how to start an agent manually. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 339214] Starting KMail gives message "Could not create collection trash resourceId: 3 [MailCommon::Kernel::createDefaultCollectionDone, MailCommon::Kernel::emergencyExit]
https://bugs.kde.org/show_bug.cgi?id=339214 h...@runiq.de changed: What|Removed |Added CC||h...@runiq.de -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 486838] New: flatpak: file dialogue to add attachment has by default no read permission to any files
https://bugs.kde.org/show_bug.cgi?id=486838 Bug ID: 486838 Summary: flatpak: file dialogue to add attachment has by default no read permission to any files Classification: Applications Product: kmail2 Version: 6.0.2 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: rob...@riemann.cc Target Milestone: --- Recently, I switched to Kinoite 40 and installed Kontact as flatpak from the fedora flatpak repository. It is now in version 6.0.2. When I try to draft an email and click on 'add attachment', a file picker opens that cannot see any files. I have then reconfigured the flatpak permissions and added manually create access to all user files and /tmp. I would expect Kmail/Kontact to possess the necessary permissions by default. Reproducible: Always Steps to Reproduce: 1. install fedora kontact flatpak 2. create a new email 3. try to add an attachment using the file picker Actual Results: notice that no file can be selected in file picker Expected Results: I can choose any file from the system in the file picker Down-stream bug report for the Fedora project: https://bugzilla.redhat.com/show_bug.cgi?id=2279924 -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 486837] New: upon new contact creation, KAddressbook always warns: Location was not saved. Do you want to close editor?
https://bugs.kde.org/show_bug.cgi?id=486837 Bug ID: 486837 Summary: upon new contact creation, KAddressbook always warns: Location was not saved. Do you want to close editor? Classification: Applications Product: kaddressbook Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: rob...@riemann.cc Target Milestone: --- Created attachment 169358 --> https://bugs.kde.org/attachment.cgi?id=169358&action=edit screenshot with warning message SUMMARY When I create a new contact or edit an existing contract, I get the following warning even though I have not touched any location-related elements in the contact card: "Location was not saved. Do you want to close editor?" STEPS TO REPRODUCE 1. create a new contact in an addressbook (I use a carddav remote addressbook) 2. add a name and an email address 3. click save 4. see the warning: Location was not saved. Do you want to close editor? OBSERVED RESULT I get a warning that I have to accept. EXPECTED RESULT I only get such a warning if I have changed the location fields. SOFTWARE/OS VERSIONS I am using the fedora repository flatpak of kontact in version 6.0.2. ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 486836] New: more privacy for event invitees when sending out calendar invitees or share ICS files
https://bugs.kde.org/show_bug.cgi?id=486836 Bug ID: 486836 Summary: more privacy for event invitees when sending out calendar invitees or share ICS files Classification: Applications Product: korganizer Version: 6.0.2 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: invitations Assignee: kdepim-bugs@kde.org Reporter: rob...@riemann.cc Target Milestone: --- I tagged this as a feature request. However, in some regions with strict privacy laws demanding "data minimisation" and privacy by default, this could be interpreted as a legal obligation that would merit a classification as bug. SUMMARY KOrganizer allows to share event details with invitees using two ways: 1. add people as participants 2. right click on event and click on "send as iCalendar..." In both cases, the names and mail addresses of invitees are revealed to other invitees, thus impacting their privacy. Note that in all cases, the actual contact data sharing is not made transparent to the event organiser. STEPS TO REPRODUCE 1. create a new event 2. add two people as invitees 3. see that each invitee can see in the email all other invitees 4. go back to Korganiser and click right on an event in the month view, choose in the context menu "send as iCalendar" and add two mail addresses 5. find in the sent mail folder that both mail addresses are in the "to" instead of "bcc" OBSERVED RESULT Invitees see mail addresses and names of other invitees. EXPECTED RESULT Invitees can only see mail addresses and names of other invitees if the event organiser has made an explicit choice to share this data. Linux/KDE Plasma: 6.0 I am using Kontact flatpak 6.0.2 from the fedora repository. According to some Matrix channel, the fedora flatpak is built the same way like the KDE kontact flatpak on flathub. ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 486835] New: Composer window geometries are mixed up with kmail main window geometries
https://bugs.kde.org/show_bug.cgi?id=486835 Bug ID: 486835 Summary: Composer window geometries are mixed up with kmail main window geometries Classification: Applications Product: kmail2 Version: 6.0.2 Platform: openSUSE OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: h...@urpla.net Target Milestone: --- First of all, still running on X11 because bko#377162, sorry! With earlier kmail versions, the composer windows managed its own geometries, e.g. creating a new mail used the window size and position of the last composer window. With 24.02.2, this behaviour is lost, and kmail main window geometries are mixed up with composer window geometries: a new composer window inherits the main window size. In my setup, I'm running kmail main window vertically expanded on a huge 30" screen (since ages). But now, new composer windows are drawn with the same size. Before, it maintained the composer window geometries independently of the main window, and appeared a lot smaller in my setup. Another indication of this new behaviour and the mix-up is reproduced like this: Start up kmail. Resize vertical size to take the full screen height (up to the control panel, of course). Open a new mail. Resize the composer window to a different size, say half of the main window. Close the main window. Close the composer window. Restart kmail, et voilà, the main window appears with the size of the last composer window. This is a regression from my point of view. The kmail main and composer windows should manage their geometries independently. The new behaviour looks and feels ugly, as well as usability is awkward. Also, semantically, main and composer windows act quite different semantically, hence their geometries should be managed separately as well. Operating System: openSUSE Tumbleweed 20240429 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-7-preempt (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor Memory: 62.4 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3060/PCIe/SSE2 Manufacturer: ASUS kmail 24.02.2 -- You are receiving this mail because: You are the assignee for the bug.
[frameworks-kio] [Bug 486796] Tiny dialog to attach files
https://bugs.kde.org/show_bug.cgi?id=486796 Grósz Dániel changed: What|Removed |Added Assignee|kdepim-bugs@kde.org |kio-bugs-n...@kde.org CC||kdelibs-b...@kde.org Version|6.0.2 |6.1.0 Component|composer|Open/save dialogs Product|kmail2 |frameworks-kio --- Comment #2 from Grósz Dániel --- (In reply to Laurent Montel from comment #1) > Hi, > kmail uses kfiledialog we don't provide it. > => it's not a kmail bug. > Regards Moving the bug to frameworks-kio. However, it doesn't happen anywhere else, so I assume it depends in some way on how KMail uses the dialog in that particular case, though I don't know where the bug actually is. -- You are receiving this mail because: You are the assignee for the bug.
