[Akonadi] [Bug 386985] akonadi CalDav resource not synching with certain servers
https://bugs.kde.org/show_bug.cgi?id=386985 Christian changed: What|Removed |Added CC||christian.tall...@gmx.de --- Comment #65 from Christian --- I can confirm that with the radicale caldav server I can only view events on the server, but new events created in KOrganizer or Merkuro Calendar are not synced to the server. I also have set up the Radicale Caldav Calendar resource on Thunderbird and my iPhone and iPad. On all devices the events can be viewed and new events can be added. Only the events from akonadi are not sent to the server. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 482568] Links don't convert cursor to a hand, and don't open when clicked
https://bugs.kde.org/show_bug.cgi?id=482568 Christian (Fuchs) changed: What|Removed |Added CC||k...@fuchsnet.ch -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 488176] New: New Akregator theme (especially max-width) breaks some usecases - allow custom CSS?
https://bugs.kde.org/show_bug.cgi?id=488176 Bug ID: 488176 Summary: New Akregator theme (especially max-width) breaks some usecases - allow custom CSS? Classification: Applications Product: akregator Version: 6.1.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: kde-b...@cboltz.de Target Milestone: --- Created attachment 170238 --> https://bugs.kde.org/attachment.cgi?id=170238=edit screenshot with some annotations SUMMARY The new Akregator theme breaks some usecases, especially by applying a max-width. For example, MediaWiki RecentChanges feeds which contain the changes as two columns get displayed with very narrow columns, and - as a side effect - need lots of scrolling. STEPS TO REPRODUCE 1. Add a RecentChanges feed from a MediaWiki installation, for example https://en.opensuse.org/index.php?title=Special:RecentChanges=atom 2. choose/view an item that has a content change (= not creation of a new page) OBSERVED RESULT Very narrow columns with old and new text, which also needs lots of scrolling (see attached screenshot). EXPECTED RESULT Use the full width, so that the columns have a reasonable width, and don't need too much scrolling. Well, at least for this usecase ;-) - and I understand that different people might have different preferences. Therefore I propose to add a config option where users can select a custom CSS file, so that they can adjust the layout to their preference. (Note: Ideally users should also have a way to see the default CSS and/or HTML template so that they know what to change - but even a pointer to the source (src/formatter/html/5.2/normalview.html) is better than nothing). A more boring solution might be to make the max-width configurable - at least for me it's the only thing I'd like to change in the new theme. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed KDE Plasma Version: 24.05.0 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 485132] DAV resource: invalid response from backend
https://bugs.kde.org/show_bug.cgi?id=485132 Christian (Fuchs) changed: What|Removed |Added CC||k...@fuchsnet.ch --- Comment #5 from Christian (Fuchs) --- Potentially the same as https://bugs.kde.org/show_bug.cgi?id=486871, the error message is indeed not helpful, but I got the same. And I can confirm that the ressource is working with every other client, including akonadi < 6.*, so this is not a bug in the ressource, but in akonadi. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 487025] New: kmail systray click is broken in 6.* if opened through kontact instead of kmail
https://bugs.kde.org/show_bug.cgi?id=487025 Bug ID: 487025 Summary: kmail systray click is broken in 6.* if opened through kontact instead of kmail Classification: Applications Product: kontact Version: 6.0.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: mail Assignee: kdepim-bugs@kde.org Reporter: k...@fuchsnet.ch Target Milestone: --- SUMMARY Kmail has an option to show a systray icon for unread mails. Clicking on this icon used to (and is supposed to, I guess, see below) toggle showing kmail if clicked. This no longer works in Plasma 6 / with KDEPim 6 if and only if kmail was started through kontact. It does work when starting kmail directly. It also occasionally starts working again after closing kontact, opening kmail, closing kmail, opening kontact. STEPS TO REPRODUCE 1. Configure kmail to show a systray icon 2. Start kontact 3. Click the icon OBSERVED RESULT The kmail (or kontact) window should toggle (minimize and un-minimize) EXPECTED RESULT Nothing happens on click Operating System: Fedora Linux 40 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.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.
[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.
[Akonadi] [Bug 480060] KDE randomly restarted when launching Audacity
https://bugs.kde.org/show_bug.cgi?id=480060 Christian Lampe changed: What|Removed |Added CC||kont...@lampe2020.de -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 480060] New: KDE randomly restarted when launching Audacity
https://bugs.kde.org/show_bug.cgi?id=480060 Bug ID: 480060 Summary: KDE randomly restarted when launching Audacity Classification: Frameworks and Libraries Product: Akonadi Version: 5.19.3 Platform: Ubuntu OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: kont...@lampe2020.de CC: c...@carlschwan.eu Target Milestone: --- Application: akonadi_sendlater_agent (5.19.3 (21.12.3)) Qt Version: 5.15.3 Frameworks Version: 5.92.0 Operating System: Linux 6.5.0-14-generic x86_64 Windowing System: Wayland Distribution: Ubuntu 22.04.3 LTS DrKonqi: 5.24.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: I tried opening Audacity while sharing my screen in a Skype call in Firefox Developer Edition 122.0b9, with the intent to show my father via Skype how he can record audio in Audacity. - Unusual behavior I noticed: Suddenly both screens went black, after a few seconds showed some `^@^@^@^@^@^@^@^@` in the TTY and KDE started back up with tons of "KDE:s kraschhanterare" windows with different processes whose name begins with "akonadi_", with the details stating it crashed with signal "Aborted (6)". Some of them include: * akonadi_mailmerge_agent * akonadi_unifiedmailbox_agent * akonadi_akonotes_resource * akonadi_maildir_resource * akonadi_archivemail_agent * [etc] Interestingly, KDE didn't crash again when opening and using Audacity in the exact same situation again. Firefox does no longer have camera access since the crash, but I haven't rebooted yet so that may fix the camera access. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: akonadi_sendlater_agent (akonadi_sendlater_agent), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140025438897152) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=140025438897152) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=140025438897152, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x7f5a4c442476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7f5a4c4287f3 in __GI_abort () at ./stdlib/abort.c:79 #9 0x7f5a4cc90ba3 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f5a41707e45 in () at /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #11 0x7f5a4171811a in QtWaylandClient::QWaylandDisplay::flushRequests() () at /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #12 0x7f5a4cef17c8 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f5a4cef4cb3 in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f5a4cef54e3 in QSocketNotifier::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f5a4db6c713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7f5a4ceb9e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f5a4cf13cc5 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f5a4a651d3b in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x7f5a4a6a7258 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x7f5a4a64f3e3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x7f5a4cf130b8 in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7f5a4ceb875b in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7f5a4cec0cf4 in QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x8b817ff4 in () #25 0x7f5a4c429d90 in __libc_start_call_main (main=main@entry=0x8b816630, argc=argc@entry=3, argv=argv@entry=0x7fffe05acdc8) at ../sysdeps/nptl/libc_start_call_main.h:58 #26 0x7f5a4c429e40 in __libc_start_main_impl (main=0x8b816630, argc=3, argv=0x7fffe05acdc8, init=, fini=, rtld_fini=, stack_end=0x7fffe05acdb8) at ../csu/libc-start.c:392 #27 0x8b816665 in () [Inferior 1 (process 3601) detached] Possible duplicates by query: bug 474747, bug 473194, bug 472861, bug 472535, bug 471164. Rapportera till https://bugs.kde.org/ -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 452565] Akonadi is creating "Unknown Organization" in $HOME/.config
https://bugs.kde.org/show_bug.cgi?id=452565 Christian Boltz changed: What|Removed |Added CC||kde-b...@cboltz.de -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 462903] Icons (e.g. reoccuring, category) in event headers impossible to read on dark colours
https://bugs.kde.org/show_bug.cgi?id=462903 --- Comment #2 from Christian (Fuchs) --- (In reply to gjditchfield from comment #1) > The icons come from the user's chosen icon theme. KOrganizer does not > choose their colors. as does the font usually use the user chosen foreground colour, but it is intelligent enough to switch to the opposite on a certain background to ensure being legible. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 462903] New: Icons (e.g. reoccuring, category) in event headers impossible to read on dark colours
https://bugs.kde.org/show_bug.cgi?id=462903 Bug ID: 462903 Summary: Icons (e.g. reoccuring, category) in event headers impossible to read on dark colours Classification: Applications Product: korganizer Version: 5.22.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: agendaview (weekview) Assignee: kdepim-bugs@kde.org Reporter: k...@fuchsnet.ch Target Milestone: --- Created attachment 154495 --> https://bugs.kde.org/attachment.cgi?id=154495=edit screenshot of the issue, text changes to white on dark backgrounds, icons stay black SUMMARY Icons in the event header use the font foreground colour (e.g. black by default) regardless of the background colour and are thus impossible to read on dark calendar colours STEPS TO REPRODUCE 1. Enable the option to show the icons in the event headers 2. Have a calendar with a dark calendar colour, e.g. dark blue OBSERVED RESULT Icons remain black, being dark on dark EXPECTED RESULT Icons change to white to give a better contrast, like the text does Operating System: Fedora Linux 37 KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 Kernel Version: 6.0.10-300.fc37.x86_64 (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3070/PCIe/SSE2 System Version: 1.0 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 377355] Kmail2 does not reset scroll position in message preview/window
https://bugs.kde.org/show_bug.cgi?id=377355 Christian Boltz changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- CC||kde-b...@cboltz.de --- Comment #5 from Christian Boltz --- I'm not the original reporter, but I sometimes (rarely) see this problem - maybe once per week (with >50 mails per day). Unfortunately so far I didn't find a pattern or explanation why this happens. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 384815] Window gets initialized with a user specified position
https://bugs.kde.org/show_bug.cgi?id=384815 Christian Muehlhaeuser changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #2 from Christian Muehlhaeuser --- Nope, can't reproduce this any longer. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 371749] Kolab - "Others users"-Calenders not discovered
https://bugs.kde.org/show_bug.cgi?id=371749 Christian Kölpin changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #5 from Christian Kölpin --- Problem still exisits. Tested with Kontact 5.21.2 (Fresh KDE Neon install this morning) The "Others Users" dosn't appear in the overview, despite the fact, that the subscribed calendars (via Serverside subscriptions) got processed correctly (events are shown, reminders pops up) -- You are receiving this mail because: You are the assignee for the bug.
[Reminder Daemon] [Bug 452264] Appointment reminder handling reduces usability and functionality between 21.12.3 and 22.03.80
https://bugs.kde.org/show_bug.cgi?id=452264 Christian Wolf changed: What|Removed |Added CC||christianlu...@web.de --- Comment #25 from Christian Wolf --- I was surprised by this regression as well as I updated my Archlinux machine. I have read the comments with this report and see it slightly different: For me, distinguishing between a task (fixed appointment) and a ToDo/task (rough time estimation) is not that strict. The extremes are a fixed appointment and a strategic document. Between them, there is a (linear, analogous) space/gradient. The different approaches mentioned here are falling within this gradient. I confirm the statements in #16 and #18 are true. These types of delays are valid and I can confirm. I want to add other points additionally: 1. I use a central Nextcloud server to sync tasks/appointments between phone and laptop. So, for me it is essential that any solution is compatible with the webdav-based appointments/tasks. 2. When driving in the car, I often get (good?) ideas. I want to fix them in a quick manner. Normally, I do not have the time to decide if this is better a task or an appointment. It's more like adding an appointment "Call Mom, mobile app" to remind me that I need to call her and ask if I need to install a certain app on her phone (just a dumb example). I will put a reminder (default 15min) after I arrived and most probably will be back on the computer. There I can process further and call her. 3. When coming to my laptop, I am typically greeted by a bunch of notifications that are informing me of whatever I need to do now. With the old korac I was able to process the tasks in "my" order. Some could be dismissed directly (already done). Others need more caring. One trick to get this done fast was to delay all still-to-be-cared-of notifications for 1-2 minutes and then dismiss all altogether. This was typically much faster than 1 on 1 dismissing. 4. I might be able to adjust to thinking if it is a hard deadline or not, most of my appointments are rather tasks instead of appointments. Explaining the concept to my parents or my girlfriend would seem rather complex. I do not know if I can get them used to the difference. 5. Speaking boldly: What would be the benefit of differentiating between appointments and tasks? The restrictions imposed by the UI to appointments hold true for tasks, are they not? 6. If you put a hamburger menu for appointments/tasks in the UI, you could think of an option to shift the event/task due time instead of delaying the notification. That might be useful as it will propagate to all synced devices. Eventually, I will have more comments, that it for now :-) Christian -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 459341] Kmail crash when trying to write recipent address in the new mail window
https://bugs.kde.org/show_bug.cgi?id=459341 Christian (Fuchs) changed: What|Removed |Added CC||k...@fuchsnet.ch -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 452507] Item details no longer shown in sidebar
https://bugs.kde.org/show_bug.cgi?id=452507 Christian (Fuchs) changed: What|Removed |Added CC||k...@fuchsnet.ch -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 283682] KMail duplicates filtered messages
https://bugs.kde.org/show_bug.cgi?id=283682 --- Comment #230 from Christian Hilberg --- Am Mittwoch, 27. April 2022, 10:57:26 CEST schrieb ederag: > https://bugs.kde.org/show_bug.cgi?id=283682 > > --- Comment #229 from ederag --- > (In reply to r.kunschke from comment #228) > > Is there any workaround or something? > > Adding this filter helped a lot here: > - match all messages > - Executed Command: /usr/bin/sleep 1, Depending on how quick the IMAP server is, this had little to no effect for me when I tried, so YMMV. (bye)^2 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 434757] Cannot sync CalDAV calendars on iCloud
https://bugs.kde.org/show_bug.cgi?id=434757 Christian Ponte changed: What|Removed |Added Status|CONFIRMED |RESOLVED CC||chpo...@pm.me Resolution|--- |FIXED --- Comment #5 from Christian Ponte --- I fixed iCloud calendar sync problems in https://invent.kde.org/frameworks/kdav/-/merge_requests/16. I didn't find any problems with the auth headers as wabbajack reported, the issue was a malformed request. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 446919] html body style bleeds into mail header
https://bugs.kde.org/show_bug.cgi?id=446919 --- Comment #1 from Christian Spanier --- Might be related to 441829 and 429393, but they overlap other HTML elements on top of the header. This bug is specifically about CSS body styles that bleed into the header. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 446919] New: html body style bleeds into mail header
https://bugs.kde.org/show_bug.cgi?id=446919 Bug ID: 446919 Summary: html body style bleeds into mail header Product: kmail2 Version: 5.19.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: k...@boxie.eu Target Milestone: --- Created attachment 144505 --> https://bugs.kde.org/attachment.cgi?id=144505=edit render bug of email header information SUMMARY I noticed that some specific (spam) mails mess up the mail header (containing from, to, and date information, see screenshot). So I created a reproducible test case that illustrates the issue. It is the that breaks rendering. STEPS TO REPRODUCE 1. Send custom HTML mail using msmtp (or similar): ```bash cat << EOF | mail -M "text/html" -s "Test" YOUR@MAIL.ADDRESS http://www.w3.org/TR/html4/loose.dtd;> Test EOF ``` 2. check your mails OBSERVED RESULT see screenshot EXPECTED RESULT readable lines. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 439165] Kontact crashed while in background
https://bugs.kde.org/show_bug.cgi?id=439165 --- Comment #5 from Christian Nitschkowski --- Created attachment 142383 --> https://bugs.kde.org/attachment.cgi?id=142383=edit New crash information added by DrKonqi kontact (5.16.2 (20.12.2)) using Qt 5.15.2 - What I was doing when the application crashed: I have Kontact opened but wasn't actively using it. I can reproduce this 100% of the time. After a certain amount of time (approximately 5 minutes, I haven't exactly timed it yet) Kontact crashes. It doesn't matter if it's just "sitting there" in the foreground, background or if I'm actively using it. -- Backtrace (Reduced): #12 0x7f33ea571ddd in GlassTable::find(Glass::Cursor*) const () from /lib64/libxapian.so.30 #13 0x7f33ea572e69 in GlassTable::get_exact_entry(std::__cxx11::basic_string, std::allocator > const&, std::__cxx11::basic_string, std::allocator >&) const () from /lib64/libxapian.so.30 #14 0x7f33ea56850e in GlassPostListTable::get_freqs(std::__cxx11::basic_string, std::allocator > const&, unsigned int*, unsigned int*, unsigned int*) const () from /lib64/libxapian.so.30 #15 0x7f33ea4ecca5 in Xapian::Database::get_termfreq(std::__cxx11::basic_string, std::allocator > const&) const () from /lib64/libxapian.so.30 #17 0x7f33ea921ff8 in Akonadi::Search::PIM::IndexedItems::indexedItems(long long) () from /lib64/libKF5AkonadiSearchPIM.so.5 -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 439165] Kontact crashed while in background
https://bugs.kde.org/show_bug.cgi?id=439165 Christian Nitschkowski changed: What|Removed |Added CC||cn...@gmx.de -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 440449] PIM events plugin in Digital Clock can no longer be configured with latest kdeplasma-addons
https://bugs.kde.org/show_bug.cgi?id=440449 Christian (Fuchs) changed: What|Removed |Added CC||k...@fuchsnet.ch -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 376981] kmail no longer displays mails
https://bugs.kde.org/show_bug.cgi?id=376981 Christian Trippe changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #2 from Christian Trippe --- I did not have that probelm for quite some time now. Therefore closing the bug. -- You are receiving this mail because: You are the assignee for the bug.
[kleopatra] [Bug 358210] Add support for secure checksums: SHA-2 instead of SHA-1 and MD5
https://bugs.kde.org/show_bug.cgi?id=358210 Christian Stadelmann changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Christian Stadelmann --- This issue has been fixed in a more recent version. With Kleopatra 3.1.11, the default is sha256sum. sha512sum is also available. Thanks! -- You are receiving this mail because: You are on the CC list for the bug.
[kmail2] [Bug 431426] Feature Request: Failed signature message is too small and non-prominent
https://bugs.kde.org/show_bug.cgi?id=431426 Christian Wolf changed: What|Removed |Added CC||christianlu...@web.de -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 431426] New: Feature Request: Failed signature message is too small and non-prominent
https://bugs.kde.org/show_bug.cgi?id=431426 Bug ID: 431426 Summary: Feature Request: Failed signature message is too small and non-prominent Product: kmail2 Version: 5.15.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: christianlu...@web.de Target Milestone: --- Created attachment 134733 --> https://bugs.kde.org/attachment.cgi?id=134733=edit Screenshot of failing signature SUMMARY When a message is signed using S/MIME (and probably GPG), a small red or green border is put around the message and a small information block is printed above the message (see screenshot). This message is ok for correctly signed messages as one does not want to bother the user with a working infrastructure. However, the failing case should be made more prominent. The message should be made bigger and "brighter". Especially for me (partly color blind), it is almost impossible to get the color "as a byproduct". I have to read the text that can be easily taken for the message of a successful signature. So, I vote to make the text at least 3 times bigger in case of failure and maybe even a thicker border. One could add this as an optional setting for disabled people in the settings if you do not want to clutter the default UI. STEPS TO REPRODUCE 1. Open an email with valid S/MIME signature 2. Open an email with invalid signature OBSERVED RESULT The messages are very close in the text appearance. EXPECTED RESULT More prominent warning of a failed signature check SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 341067] Events from caldav resource do not appear in Korganizer
https://bugs.kde.org/show_bug.cgi?id=341067 Christian Krippendorf changed: What|Removed |Added CC||cerebro...@gmx.net --- Comment #11 from Christian Krippendorf --- Same Problem here: Current debian sid. No error message from akonadiconsole while syncing, but icloud entries won't appear in korganizer. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 357139] Kontact crashed when choosing "configure completion" in kmail composer
https://bugs.kde.org/show_bug.cgi?id=357139 Christian Trippe changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #2 from Christian Trippe --- I can no longer reproduce it -- You are receiving this mail because: You are the assignee for the bug.
[kwin] [Bug 430112] "certificate expired" dialog steals focus from other applications
https://bugs.kde.org/show_bug.cgi?id=430112 Christian Boltz changed: What|Removed |Added Assignee|kdepim-bugs@kde.org |kwin-bugs-n...@kde.org Product|akregator |kwin Resolution|UPSTREAM|--- Version|5.15.3 |5.20.4 Component|general |general Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #4 from Christian Boltz --- Moving bug - Hi kwin developers, is this focus stealing bug something in your area? ;-) -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 430112] "certificate expired" dialog steals focus from other applications
https://bugs.kde.org/show_bug.cgi?id=430112 --- Comment #2 from Christian Boltz --- Currently this one should give you the error (until they update the certificate): https://twitrss.me/twitter_user_to_rss/?user=farbfiguren -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 430112] New: "certificate expired" dialog steals focus from other applications
https://bugs.kde.org/show_bug.cgi?id=430112 Bug ID: 430112 Summary: "certificate expired" dialog steals focus from other applications Product: akregator Version: 5.15.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: kde-b...@cboltz.de Target Milestone: --- SUMMARY If Akregator tries to fetch a feed over https, and the server certificate expired, the dialog saying so steals the focus. STEPS TO REPRODUCE 1. add (or have) a feed from a server with expired ssl certificate 2. fetch all feeds 3. make sure Akregator doesn't have the focus OBSERVED RESULT A dialog saying (translated back from german) "Validating the server ($domain) failed. The validity of the certificate is expired." This dialog grabs the focus, even if I'm just in another program. (Which also means that - if I'm just going to press enter in the other program - will accidently get that key press. EXPECTED RESULT Same dialog, but it shouldn't steal the focus. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.76.0 Qt Version: 15.2 -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 428449] New: wrong tab order in "edit feed" dialog
https://bugs.kde.org/show_bug.cgi?id=428449 Bug ID: 428449 Summary: wrong tab order in "edit feed" dialog Product: akregator Version: 5.15.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: kde-b...@cboltz.de Target Milestone: --- SUMMARY The "edit feed" (german: "Nachrichtenquelle bearbeiten") dialog has a broken tab order. STEPS TO REPRODUCE 1. right-click a feed and choose "edit feed" (or simply press F2) 2. press the tab key multiple times, and observe what gets selected OBSERVED RESULT - "name" gets seleted when the dialog opens - good - pressing tab leads to the "comment" field (skipping "address") - pressing tab once more leads to the OK button (skipping the checkboxes) The "address" field and the two checkboxes get skipped. EXPECTED RESULT When pressing tab, the fields should be selected in the order as they are displayed in the dialog: Name -> address -> comment -> user-defined interval [if enabled: time input field -> unit dropdown] -> tell about new articles -> OK SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed, Akregator 5.15.2 (20.08.2) KDE Plasma Version: 5.20.1 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 423672] org.kde.pim.imapresource: Failed to create folder on server: "Create failed, server replied: ... NO Mailbox already exists ... [ ALREADYEXISTS ]"
https://bugs.kde.org/show_bug.cgi?id=423672 Christian Mollekopf changed: What|Removed |Added Latest Commit|https://invent.kde.org/pim/ |https://invent.kde.org/pim/ |kimap/commit/ee2900e3539483 |kimap2/commit/ce0e9873d3a89 |b6f3d5eadfcf8cfc9c6ed42abe |7fee7fd9f8f7649ef4abd3c4627 --- Comment #6 from Christian Mollekopf --- Git commit ce0e9873d3a897fee7fd9f8f7649ef4abd3c4627 by Christian Mollekopf, on behalf of Dennis Schridde. Committed on 06/08/2020 at 12:59. Pushed by cmollekopf into branch 'master'. Idempotent CREATE and DELETE If CREATE fails with an ALREADYEXISTS response code, that is not an error since the intended result (the object existing at the target location) has been achieved. Likewise, if DELETE fails with an NONEXISTENT response code, that is not an error since the intended result (the object being gone from the target location) has been achieved. Please note that for RENAME response code ALREADYEXISTS *is* an error since the content of the source folder was not moved as intended. cf. https://tools.ietf.org/html/rfc5530#section-3 M +27 -0src/createjob.cpp M +2-1src/createjob.h M +27 -0src/deletejob.cpp M +2-1src/deletejob.h https://invent.kde.org/pim/kimap2/commit/ce0e9873d3a897fee7fd9f8f7649ef4abd3c4627 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 422962] Akonadi indexing agent crashes time and again
https://bugs.kde.org/show_bug.cgi?id=422962 --- Comment #5 from Christian Nitschkowski --- Is there any way to stop that indexing error to appear time and again? It is really annoying and gets to a point I'm actually thinking about switching to a different DE because I get those crash notificiations every few seconds. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 422962] Akonadi indexing agent crashes time and again
https://bugs.kde.org/show_bug.cgi?id=422962 --- Comment #2 from Christian Nitschkowski --- Application: akonadi_indexing_agent (akonadi_indexing_agent), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1730e8d600 (LWP 3206))] Thread 4 (Thread 0x7f172188f700 (LWP 3264)): #0 0x7f1733f1d87c in g_source_ref () from /lib64/libglib-2.0.so.0 #1 0x7f1733f1d948 in g_source_iter_next () from /lib64/libglib-2.0.so.0 #2 0x7f1733f1ef03 in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #3 0x7f1733f1f9fb in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #4 0x7f1733f1fc03 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #5 0x7f17358a0b8b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f173585391b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #7 0x7f17356bf427 in QThread::exec() () from /lib64/libQt5Core.so.5 #8 0x7f17356c0690 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #9 0x7f1734833432 in start_thread () from /lib64/libpthread.so.0 #10 0x7f17353249d3 in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f1722090700 (LWP 3263)): #0 0x7f1735319b6f in poll () from /lib64/libc.so.6 #1 0x7f1733f1face in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #2 0x7f1733f1fc03 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f17358a0b8b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f173585391b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f17356bf427 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f1735b2e51b in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #7 0x7f17356c0690 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f1734833432 in start_thread () from /lib64/libpthread.so.0 #9 0x7f17353249d3 in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f1723bc0700 (LWP 3227)): #0 0x7f1735319b6f in poll () from /lib64/libc.so.6 #1 0x7f173147d38a in _xcb_conn_wait () from /lib64/libxcb.so.1 #2 0x7f173147f71a in xcb_wait_for_event () from /lib64/libxcb.so.1 #3 0x7f1723d98c78 in QXcbEventQueue::run() () from /lib64/libQt5XcbQpa.so.5 #4 0x7f17356c0690 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x7f1734833432 in start_thread () from /lib64/libpthread.so.0 #6 0x7f17353249d3 in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f1730e8d600 (LWP 3206)): [KCrash Handler] #4 0x7f173525fa25 in raise () from /lib64/libc.so.6 #5 0x7f1735248895 in abort () from /lib64/libc.so.6 #6 0x7f17354a8961 in __gnu_cxx::__verbose_terminate_handler() [clone .cold] () from /lib64/libstdc++.so.6 #7 0x7f17354b442c in __cxxabiv1::__terminate(void (*)()) () from /lib64/libstdc++.so.6 #8 0x7f17354b4497 in std::terminate() () from /lib64/libstdc++.so.6 #9 0x7f17354b4749 in __cxa_throw () from /lib64/libstdc++.so.6 #10 0x7f1736b7a314 in GlassTable::set_overwritten() const () from /lib64/libxapian.so.30 #11 0x7f1736b7a67a in GlassTable::block_to_cursor(Glass::Cursor*, int, unsigned int) const [clone .cold] () from /lib64/libxapian.so.30 #12 0x7f1736c51a0d in GlassTable::find(Glass::Cursor*) const () from /lib64/libxapian.so.30 #13 0x7f1736c540a9 in GlassTable::get_exact_entry(std::__cxx11::basic_string, std::allocator > const&, std::__cxx11::basic_string, std::allocator >&) const () from /lib64/libxapian.so.30 #14 0x7f1736c4428b in GlassPostListTable::get_freqs(std::__cxx11::basic_string, std::allocator > const&, unsigned int*, unsigned int*, unsigned int*) const () from /lib64/libxapian.so.30 #15 0x7f1736ce7010 in Xapian::Weight::Internal::accumulate_stats(Xapian::Database::Internal const&, Xapian::RSet const&) () from /lib64/libxapian.so.30 #16 0x7f1736ca3d2b in LocalSubMatch::prepare_match(bool, Xapian::Weight::Internal&) () from /lib64/libxapian.so.30 #17 0x7f1736cac3a5 in MultiMatch::MultiMatch(Xapian::Database const&, Xapian::Query const&, unsigned int, Xapian::RSet const*, unsigned int, unsigned int, int, double, Xapian::Enquire::docid_order, unsigned int, Xapian::Enquire::Internal::sort_setting, bool, double, Xapian::Weight::Internal&, Xapian::Weight const*, std::vector, std::allocator > > const&, bool, bool) () from /lib64/libxapian.so.30 #18 0x7f1736ba3c56 in Xapian::Enquire::Internal::get_mset(unsigned int, unsigned int, unsigned int, Xapian::RSet const*, Xapian::MatchDecider const*) const () from /lib64/libxapian.so.30 #19 0x7f1736ba3f09 in Xapian::Enquire::get_mset(unsigned int, unsigned int, unsigned int, Xapian::RSet const*, Xapian::MatchDecider const*) const () from /lib64/libxapian.so.30 #20 0x7f1736dc4ae8 in Akonadi::Search::PIM::IndexedItemsPrivate::findI
[Akonadi] [Bug 422962] Akonadi indexing agent crashes time and again
https://bugs.kde.org/show_bug.cgi?id=422962 --- Comment #3 from Christian Nitschkowski --- Attached the backtrace -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 357313] Column-width in the main window, i.e. "subject", "from", "date" not kept, crowded to left
https://bugs.kde.org/show_bug.cgi?id=357313 Christian Reiner changed: What|Removed |Added CC||f...@christian-reiner.info --- Comment #7 from Christian Reiner --- I still have this issue on current KDE Neon using KMail and Kontact in version 4.20 as delivered by the distribution. It does not always happen. I have the impression that it mostly happens when I close KMail before closing the KDE session. So it could be connected to different strategies of how an application performs the shutdown. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 422962] Akonadi indexing agent crashes time and again
https://bugs.kde.org/show_bug.cgi?id=422962 Christian Nitschkowski changed: What|Removed |Added Version|unspecified |5.13.2 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 422962] New: Akonadi indexing agent crashes time and again
https://bugs.kde.org/show_bug.cgi?id=422962 Bug ID: 422962 Summary: Akonadi indexing agent crashes time and again Product: Akonadi Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Indexer Assignee: kdepim-bugs@kde.org Reporter: cn...@gmx.de CC: chrig...@fastmail.fm, dvra...@kde.org Target Milestone: --- SUMMARY Akonadi indexing agent crashes time and again, even without any user interaction without any special configuration. STEPS TO REPRODUCE 1. Login into Plasma session. OBSERVED RESULT When I login to KDE session the crash report dialog pops up during login. While the session is running a toast message will pop up every now and then telling me the indexing agent crashed. EXPECTED RESULT The indexing agent shouldn't crash. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 32 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70 Qt Version: 5.13.2 ADDITIONAL INFORMATION I upgraded from KDE 5.16 to 5.17 to 5.18 without resetting my configuration. The problem occurred already with KDE 5.16. It first came up a few days after setting up my computer and persisted over several updates. The crash can be reproduced every time. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 419694] New: Synchronization of recurring appointments with exceptions
https://bugs.kde.org/show_bug.cgi?id=419694 Bug ID: 419694 Summary: Synchronization of recurring appointments with exceptions Product: Akonadi Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: DAV Resource Assignee: kdepim-bugs@kde.org Reporter: christianlu...@web.de Target Milestone: --- TOPIC I have the problem that I want to synchronize my calendars between different devices. To do it, I use my nextcloud instance. Some more information might be in the following mail: https://mail.kde.org/pipermail/kdepim-users/2020-March/013162.html SUMMARY Recurring events cannot be managed between the instances. In fact, there are two problems that are dependant but not equal. Start by having an event that is recurring with multiple instances. STEPS TO REPRODUCE A.1. Remove one of the events in KDEPIM/Akonadi/KOrganizer A.2. Check the removed event in the other devices (either nextcloud itself of Android mobile using DAVDroid) B.1. Remove one of the events in either of the other devices B.2. Check the event in KDEPIM/Akonadi/KOrganizer OBSERVED RESULT In both cases A + B the removal is not synchronized between the devices. EXPECTED RESULT The events get synchronized successfully. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION I tried to investigate a bit. There seem to be different ways to store exceptions in recurring events in CalDAV (see https://www.kanzaki.com/docs/ical/exdate.html). I looked into the raw payload of the event in akonadiconsole. Unfortunately, the value was changed during synchronization very quickly. I could only get a short glimpse that something has happened but I was not able to read anything useful. I just saw that the string defining the exception was not formatted the same as the others. Another try revealed the following: KDEPIM seems to generate exceptions like this: > EXDATE;VALUE=DATE:20200325 The other two solutions use another syntax: > EXDATE;TZID=Europe/Berlin:20200325T22 > EXDATE;TZID=UTC:20200326T21 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 395117] HTML mails are not detected correctly
https://bugs.kde.org/show_bug.cgi?id=395117 Christian Muehlhaeuser changed: What|Removed |Added Resolution|FIXED |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #2 from Christian Muehlhaeuser --- Still happening here with 5.13.3. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 395711] Since last Update kmail didn't load external images anymore
https://bugs.kde.org/show_bug.cgi?id=395711 Christian Wolf changed: What|Removed |Added CC||christianlu...@web.de --- Comment #19 from Christian Wolf --- I think I am also affected by this bug. I disabled HTML and external references by default (I get much spam so I want to allow references only for specified origins) and click on the warning message on enable HTML manually. However I am not always asked for confirmation that the external references should be loaded. You might try to press to load the external references (or whatever you shortcut you configured). This loaded all images instantly. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 410643] Akonadi IMAP Resource / KMail cannot connect to IMAP(s) servers with configured Web-Proxy
https://bugs.kde.org/show_bug.cgi?id=410643 --- Comment #2 from Christian Quast --- Hi Wolfgang, thanks for the quick reply and linking the bug. Sorry for not seeing the related bug report earlier which didn't show up during my searches. I think it didn't show up because I included the terms "akonadi" and "kmail" in the search which aren't in the header :( again sorry for 'noise' and thanks for fixing this problem. best Christian. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 410643] New: Akonadi IMAP Resource / KMail cannot connect to IMAP(s) servers with configured Web-Proxy
wall). Instead, I do a port forwarding via SSH ssh -L11993:other.mailserver.tld:993 ssh-server. I configured Akonadi/KMail to connect to localhost 11993 to access this server, Akonadi/KMail is able connect to / retrieve mail from the server regardless of my proxy settings. Thanks for considering Christian. SOFTWARE/OS VERSIONS openSUSE Leap 15.1 (including OBS KDE/Qt repositories) Qt Version: 5.13.0-lp151.5.1.x86_64 akonadi-calendar-lang-19.04.3-lp151.137.1.noarch akonadi-calendar-tools-19.04.3-lp151.86.1.x86_64 akonadi-calendar-tools-lang-19.04.3-lp151.86.1.noarch akonadi-contact-19.04.3-lp151.106.1.x86_64 akonadi-contact-lang-19.04.3-lp151.106.1.noarch akonadi-import-wizard-19.04.3-lp151.91.1.x86_64 akonadi-import-wizard-lang-19.04.3-lp151.91.1.noarch akonadi-mime-19.04.3-lp151.96.1.x86_64 akonadi-mime-lang-19.04.3-lp151.96.1.noarch akonadi-notes-lang-19.04.3-lp151.98.1.noarch akonadi-plugin-calendar-19.04.3-lp151.137.1.x86_64 akonadi-plugin-contacts-19.04.3-lp151.106.1.x86_64 akonadi-plugin-kalarmcal-19.04.3-lp151.129.1.x86_64 akonadi-plugin-mime-19.04.3-lp151.96.1.x86_64 akonadi-search-19.04.3-lp151.132.1.x86_64 akonadi-search-lang-19.04.3-lp151.132.1.noarch akonadi-server-19.04.3-lp151.189.1.x86_64 akonadi-server-lang-19.04.3-lp151.189.1.noarch kdepim-addons-19.04.3-lp151.127.1.x86_64 kdepim-addons-lang-19.04.3-lp151.127.1.noarch kdepim-apps-libs-19.04.3-lp151.110.1.x86_64 kdepim-apps-libs-lang-19.04.3-lp151.110.1.noarch kdepim-runtime-19.04.3-lp151.175.1.x86_64 kdepim-runtime-lang-19.04.3-lp151.175.1.noarch kmail-19.04.3-lp151.108.1.x86_64 kmail-account-wizard-19.04.3-lp151.87.1.x86_64 kmail-account-wizard-lang-19.04.3-lp151.87.1.noarch kmail-application-icons-19.04.3-lp151.108.1.x86_64 kmail-lang-19.04.3-lp151.108.1.noarch kmailtransport-19.04.3-lp151.132.1.x86_64 kmailtransport-lang-19.04.3-lp151.132.1.noarch kontact-19.04.3-lp151.88.1.x86_64 kontact-lang-19.04.3-lp151.88.1.noarch kontactinterface-lang-19.04.3-lp151.123.1.noarch kpimtextedit-19.04.3-lp151.129.1.x86_64 kpimtextedit-lang-19.04.3-lp151.129.1.noarch libKF5Libkdepim5-19.04.3-lp151.111.1.x86_64 libKF5LibkdepimAkonadi5-19.04.3-lp151.111.1.x86_64 libkdepim-19.04.3-lp151.111.1.x86_64 libkdepim-lang-19.04.3-lp151.111.1.noarch pim-data-exporter-19.04.3-lp151.86.1.x86_64 pim-data-exporter-lang-19.04.3-lp151.86.1.noarch pim-sieve-editor-19.04.3-lp151.84.1.x86_64 pim-sieve-editor-lang-19.04.3-lp151.84.1.noarch pimcommon-19.04.3-lp151.123.1.x86_64 pimcommon-lang-19.04.3-lp151.123.1.noarch ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 410064] New: HTML message gets shown with wrong CSS stylings by default
https://bugs.kde.org/show_bug.cgi?id=410064 Bug ID: 410064 Summary: HTML message gets shown with wrong CSS stylings by default Product: kmail2 Version: 5.11.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: christianlu...@web.de Target Milestone: --- I have the problem that some HTML mails with included CSS styles are not readable as foreground and background color machtes up. STEPS TO REPRODUCE 1. REceive an email with some CSS based color definitions. The mail's text color gets changed by kmail. 2. Go to settings -> Appereance -> Color and check the setting to use the original color 3. The colors are as defined in the mail's CSS. OBSERVED RESULT kmail by default changes some colors even for HTML mails. Only after manually deactivating the setting the HTML mails are readable again. EXPECTED RESULT In HTML mode the CSS of the mail should not be overridden by default. In case of manually setting various colors this might or might not be desirable. But the default settings caused me to assume the rendering of kmail to be broken. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.59.0 (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.59.0 Qt Version: 5.13.0 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 410028] New: KMail crashes when changing the Folder List Appearence
https://bugs.kde.org/show_bug.cgi?id=410028 Bug ID: 410028 Summary: KMail crashes when changing the Folder List Appearence Product: kmail2 Version: 5.11.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: schuetze.christia...@gmail.com Target Milestone: --- Application: kmail (5.11.2) Qt Version: 5.13.0 Frameworks Version: 5.59.0 Operating System: Linux 5.1.16-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: 1. Open Settings > Configure KMail > Appearance > Layout 2. Changing between "Long folder list" and "Short folder list" 3. Clicking Apply => Application crashes After restarting the app the setting is applied. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd085471a40 (LWP 32259))] Thread 26 (Thread 0x7fd04f7fe700 (LWP 4479)): #0 0x7fd0932b716c in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fd08c9cb836 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7fd08c9cc203 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7fd08c9cc381 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7fd08c984641 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7fd08c9874dd in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7fd08c987bd4 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7fd08c9ce675 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7fd0932b0faa in start_thread () from /lib64/libpthread.so.0 #9 0x7fd096cdc73f in clone () from /lib64/libc.so.6 Thread 25 (Thread 0x7fd078bab700 (LWP 1352)): #0 0x7fd096ccd80c in read () from /lib64/libc.so.6 #1 0x7fd09284570f in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fd092891c8e in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7fd092893342 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7fd09289346f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7fd095894ceb in QEventDispatcherGlib::processEvents (this=0x7fd0640050b0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7fd09583d2eb in QEventLoop::exec (this=this@entry=0x7fd078baab60, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #7 0x7fd095675f91 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #8 0x7fd095677112 in QThreadPrivate::start (arg=0x55a93cefa130) at thread/qthread_unix.cpp:360 #9 0x7fd0932b0faa in start_thread () from /lib64/libpthread.so.0 #10 0x7fd096cdc73f in clone () from /lib64/libc.so.6 Thread 24 (Thread 0x7fcf5763f700 (LWP 1348)): #0 0x7fd0932b716c in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fd08c9cb836 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7fd08c9cc203 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7fd08c9cc381 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7fd08c984641 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7fd08c98782b in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7fd08c987bd4 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7fd08c9ce675 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7fd0932b0faa in start_thread () from /lib64/libpthread.so.0 #9 0x7fd096cdc73f in clone () from /lib64/libc.so.6 Thread 23 (Thread 0x7fcf57e40700 (LWP 1341)): #0 0x7fd0932b716c in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fd08c9cb836 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7fd08c9cc203 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7fd08c9cc381 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7fd08c984641 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7fd08c98782b in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7fd08c987bd4 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7fd08c9ce675 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7fd0932b0faa in start_thread () from /lib64/libpthread.so.0 #9 0x7fd096cdc73f in clone () from /lib64/libc.so.6 Thread 22 (Thread 0x7fd04700 (LWP 783)): #0 0x7fd09567757c in QMutex::lock (this=this@entry=0x55a93f5039f0) at /usr/include/c++/9/bits/atomic_base.h:769 #1 0x7fd0958953e5 in QMutexLocker::QMutexLocker (m=0x55a93f5039f0, this=) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:206 #2 QThreadData::canWaitLocked (this=0x55a93f5039c0) at
[kmail2] [Bug 371997] Delete e-mail confirmation dialogue: wrong button has the focus
https://bugs.kde.org/show_bug.cgi?id=371997 Christian (Fuchs) changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #3 from Christian (Fuchs) --- (In reply to Laurent Montel from comment #1) > Still valid in last version ? Appears to have been fixed, thank you :) -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 284172] Kmail does not correctly recognize some IMAP-Inbox-Folders
https://bugs.kde.org/show_bug.cgi?id=284172 Christian Hartmann changed: What|Removed |Added CC||chris-hartm...@gmx.de -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 292285] Cannot specify IMAP server directory
https://bugs.kde.org/show_bug.cgi?id=292285 Christian Hartmann changed: What|Removed |Added CC||chris-hartm...@gmx.de -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 406623] New: akonadi maildir resource crash cannot be reported via DrKonqi
https://bugs.kde.org/show_bug.cgi?id=406623 Bug ID: 406623 Summary: akonadi maildir resource crash cannot be reported via DrKonqi Product: Akonadi Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Maildir Resource Assignee: kdepim-bugs@kde.org Reporter: christiande...@web.de Target Milestone: --- SUMMARY If the akondadi maildir resource crashes, DrKonqi is started. However you can only get the backtrace but are not able to report the crash via DrKonqi. STEPS TO REPRODUCE 1. Let akonadi maildir resource crash 2. DrKonqi starts 3. Button to report the bug is gray and the text above says "you cannot report the bug as the application akonadi maildir resource has no address to report the bug. (translated back from German) SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.15.4 KDE Frameworks Version: 5.56 Qt Version: 5.12.2 Akonadi 19.03.80 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 406621] New: akonadi maildir resource sometimes crashes when changing folders
https://bugs.kde.org/show_bug.cgi?id=406621 Bug ID: 406621 Summary: akonadi maildir resource sometimes crashes when changing folders Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Maildir Resource Assignee: kdepim-bugs@kde.org Reporter: christiande...@web.de Target Milestone: --- Sometimes the akonadi maildir resource crashes. As far as I have observed it, it only happens when I change to mail in another folder. However it does not always happen and so far I was not able to find exact steps to reproduce it. However it happens quite regularly for me. This is using the th 19.03.80 version of KDE applications. Backtrace is attached Linux/KDE Plasma: 5.15.4 KDE Frameworks Version: 5.56 Qt Version: 5.12.2 Akonadi 19.03.80 ADDITIONAL INFORMATION Application: akonadi_maildir_resource (akonadi_maildir_resource), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb12be1f900 (LWP 17409))] Thread 4 (Thread 0x7fb1132f0700 (LWP 17462)): [KCrash Handler] #6 0x7fb12880c0e0 in raise () from /lib64/libc.so.6 #7 0x7fb12880d6c1 in abort () from /lib64/libc.so.6 #8 0x7fb128e3be83 in ?? () from /usr/lib64/libstdc++.so.6 #9 0x7fb128e41dd8 in ?? () from /usr/lib64/libstdc++.so.6 #10 0x7fb128e41e23 in std::terminate() () from /usr/lib64/libstdc++.so.6 #11 0x7fb1291c193b in qTerminate () at global/qglobal.cpp:3192 #12 0x7fb1291e596b in QThreadPrivate::start (arg=0x55e74a3d8c80) at thread/qthread_unix.cpp:373 #13 0x7fb12620d569 in start_thread () from /lib64/libpthread.so.0 #14 0x7fb1288ce81f in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fb113af1700 (LWP 17459)): #0 0x7fb1288c407b in poll () from /lib64/libc.so.6 #1 0x7fb1243ca129 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fb1243ca23c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fb12941b87b in QEventDispatcherGlib::processEvents (this=0x55e74a3bc6a0, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7fb1293bcaaa in QEventLoop::exec (this=this@entry=0x7fb113af0c80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7fb1291e403a in QThread::exec (this=) at thread/qthread.cpp:531 #6 0x7fb12a103d55 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7fb1291e57e2 in QThreadPrivate::start (arg=0x7fb12a37bd80) at thread/qthread_unix.cpp:361 #8 0x7fb12620d569 in start_thread () from /lib64/libpthread.so.0 #9 0x7fb1288ce81f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fb118b94700 (LWP 17434)): #0 0x7fb1288c407b in poll () from /lib64/libc.so.6 #1 0x7fb11f512387 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7fb11f513fba in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7fb11b9897d8 in QXcbEventQueue::run (this=0x55e74a348300) at qxcbeventqueue.cpp:228 #4 0x7fb1291e57e2 in QThreadPrivate::start (arg=0x55e74a348300) at thread/qthread_unix.cpp:361 #5 0x7fb12620d569 in start_thread () from /lib64/libpthread.so.0 #6 0x7fb1288ce81f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fb12be1f900 (LWP 17409)): #0 0x7fb126214c34 in pthread_getspecific () from /lib64/libpthread.so.0 #1 0x7fb1243f1dd0 in g_thread_self () from /usr/lib64/libglib-2.0.so.0 #2 0x7fb1243ca22d in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fb12941b87b in QEventDispatcherGlib::processEvents (this=0x55e74a327e80, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7fb1293bcaaa in QEventLoop::exec (this=this@entry=0x7fffb7ae3e00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7fb1293c5cb0 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1363 #6 0x7fb12b366b4d in Akonadi::ResourceBase::init(Akonadi::ResourceBase*) () from /usr/lib64/libKF5AkonadiAgentBase.so.5 #7 0x55e748e20271 in ?? () #8 0x7fb1287f6f4a in __libc_start_main () from /lib64/libc.so.6 #9 0x55e748e200fa in ?? () [Inferior 1 (process 17409) detached] -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 372835] Korganizer and Digital Clock/Calendar widget keep forgetting of selected Caldav resources
https://bugs.kde.org/show_bug.cgi?id=372835 Christian Wolf changed: What|Removed |Added CC||christianlu...@web.de --- Comment #4 from Christian Wolf --- I think I might be affected by the original bug as well. All my calendars are invisible upon restart of the machine. I found that restarting akonadi (using `akoandictl restart`) from a terminal while keeping korganizer open triggers the problem as well. At least in my case this disabled all calendars. Maybe you can confirm this triggers the bug as well on your installation. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 406253] New: Kontact crashes while closing
https://bugs.kde.org/show_bug.cgi?id=406253 Bug ID: 406253 Summary: Kontact crashes while closing Product: kontact Version: 5.10.3 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: gen...@moin.fi Target Milestone: --- Application: kontact (5.10.3) (Compiled from sources) Qt Version: 5.11.3 Frameworks Version: 5.54.0 Operating System: Linux 4.19.27-gentoo-r1 x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: I had read an email in the Kontact main window. Then I closed the Kontact main window selecting File>Quit. The Kontact window closed normally but then showed the Crash reporting tool. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd33470c040 (LWP 26192))] Thread 26 (Thread 0x7fd213f19700 (LWP 26370)): #0 futex_reltimed_wait_cancelable (private=0, reltime=0x7fd213f18a80, expected=0, futex_word=0x7fd213f18c68) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7fd213f18b20, mutex=0x7fd213f18c18, cond=0x7fd213f18c40) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x7fd213f18c40, mutex=0x7fd213f18c18, abstime=0x7fd213f18b20) at pthread_cond_wait.c:667 #3 0x7fd321e4a887 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7fd321e4bde7 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7fd321e4bed2 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () from /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7fd321e50f51 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7fd321e522ef in base::internal::SchedulerWorker::Thread::ThreadMain() () from /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7fd321e5cef1 in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib64/libQt5WebEngineCore.so.5 #9 0x7fd32cdfa253 in start_thread (arg=) at pthread_create.c:486 #10 0x7fd3310c65af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 25 (Thread 0x7fd216194700 (LWP 26369)): #0 futex_reltimed_wait_cancelable (private=0, reltime=0x7fd216193a80, expected=0, futex_word=0x7fd216193c68) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7fd216193b20, mutex=0x7fd216193c18, cond=0x7fd216193c40) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x7fd216193c40, mutex=0x7fd216193c18, abstime=0x7fd216193b20) at pthread_cond_wait.c:667 #3 0x7fd321e4a887 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7fd321e4bde7 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7fd321e4bed2 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () from /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7fd321e50f51 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7fd321e524d9 in base::internal::SchedulerWorker::Thread::ThreadMain() () from /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7fd321e5cef1 in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib64/libQt5WebEngineCore.so.5 #9 0x7fd32cdfa253 in start_thread (arg=) at pthread_create.c:486 #10 0x7fd3310c65af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 24 (Thread 0x7fd22cf35700 (LWP 26228)): #0 __GI___libc_write (fd=2, buf=0x7fd22cf31f80, nbytes=39) at ../sysdeps/unix/sysv/linux/write.c:26 #1 0x7fd33103f65d in _IO_new_file_write (f=0x7fd331389680 <_IO_2_1_stderr_>, data=0x7fd22cf31f80, n=39) at fileops.c:1183 #2 0x7fd33103e833 in new_do_write (fp=fp@entry=0x7fd331389680 <_IO_2_1_stderr_>, data=data@entry=0x7fd22cf31f80 "[warn] epoll_wait: Bad file descriptor\n", to_do=to_do@entry=39) at libioP.h:839 #3 0x7fd33103fede in _IO_new_file_xsputn (f=0x7fd331389680 <_IO_2_1_stderr_>, data=, n=39) at fileops.c:1262 #4 0x7fd331013a78 in buffered_vfprintf (s=s@entry=0x7fd331389680 <_IO_2_1_stderr_>, format=format@entry=0x7fd318ffc9f8 "[%s] %s\n", args=args@entry=0x7fd22cf34540) at ../libio/libioP.h:839 #5 0x7fd331011072 in _IO_vfprintf_internal (s=s@entry=0x7fd331389680 <_IO_2_1_stderr_>, format=0x7fd318ffc9f8 "[%s] %s\n", ap=ap@entry=0x7fd22cf34540) at vfprintf.c:1296 #6 0x7fd3310d83ac in __fprintf_chk () at fprintf_chk.c:35 #7 0x7fd318fe4f47 in fprintf (__fmt=0x7fd318ffc9f8 "[%s] %s\n", __stream=) at
[kmail2] [Bug 405791] Crash when clicking on a mail that contains vcard.vcf attachment
https://bugs.kde.org/show_bug.cgi?id=405791 --- Comment #2 from Christian --- Created attachment 119036 --> https://bugs.kde.org/attachment.cgi?id=119036=edit Example vcf that crashes my kmail instance With the attached (dummy) vcf file that contains two entries, I can reproduce this crash every time. To reproduce: Save the attached all.vcf file somewhere; create a new message to myself with this file attached and send the message; receive the message and left-click on it -> crash. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 405791] Crash when clicking on a mail that contains vcard.vcf attachment
https://bugs.kde.org/show_bug.cgi?id=405791 --- Comment #1 from Christian --- Just for completeness: I'm running LANG=de_DE.UTF-8. When starting kmail from the command line, I get the following message approx. 100 times (i.e. once for each address in the vcard.vcf): org.kde.pim.kcontacts: address format database incomplete (no format for locale "en" found). Using default address formatting. org.kde.pim.kcontacts: address format database incomplete (no format for locale "en" found). Using default address formatting. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 405791] New: Crash when clicking on a mail that contains vcard.vcf attachment
https://bugs.kde.org/show_bug.cgi?id=405791 Bug ID: 405791 Summary: Crash when clicking on a mail that contains vcard.vcf attachment Product: kmail2 Version: 5.7.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: christ...@cstimming.de Target Milestone: --- Application: kmail (5.7.3) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-46-generic x86_64 Distribution: Ubuntu 18.04.2 LTS -- Information about the crash: - What I was doing when the application crashed: In KMail's list of mails in the inbox, I clicked on one mail that contains a vcard.vcf attachment. Kmail crashes instantly, before I see any parts of that actual mail. As a side-effect, I can't get rid of this mail because before I can delete or move that mail, I have to select it by clicking on it, but this crashes kmail as mentioned. The vcard.vcf attachment of that mail contains a somewhat larger list of multiple adresses - approx. 100 addresses inside that vcard file. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1d99642b80 (LWP 28515))] Thread 29 (Thread 0x7f1c70f01700 (LWP 28576)): #0 0x7f1d8c02e9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55f81ce5f228) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f1d8c02e9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55f81ce5f1d8, cond=0x55f81ce5f200) at pthread_cond_wait.c:502 #2 0x7f1d8c02e9f3 in __pthread_cond_wait (cond=0x55f81ce5f200, mutex=0x55f81ce5f1d8) at pthread_cond_wait.c:655 #3 0x7f1d80ecfc95 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f1d80ed0177 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f1d80ed0f11 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f1d80ecd5eb in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f1d8c0286db in start_thread (arg=0x7f1c70f01700) at pthread_create.c:463 #8 0x7f1d9673888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 28 (Thread 0x7f1c71702700 (LWP 28575)): #0 0x7f1d8c02e9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55f81ce5f22c) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f1d8c02e9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55f81ce5f1d8, cond=0x55f81ce5f200) at pthread_cond_wait.c:502 #2 0x7f1d8c02e9f3 in __pthread_cond_wait (cond=0x55f81ce5f200, mutex=0x55f81ce5f1d8) at pthread_cond_wait.c:655 #3 0x7f1d80ecfc95 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f1d80ed0177 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f1d80ed0f11 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f1d80ecd5eb in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f1d8c0286db in start_thread (arg=0x7f1c71702700) at pthread_create.c:463 #8 0x7f1d9673888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 27 (Thread 0x7f1cf3f8c700 (LWP 28573)): #0 0x7f1d8c02e9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f1d7d798fb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f1d8c02e9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f1d7d798f68, cond=0x7f1d7d798f90) at pthread_cond_wait.c:502 #2 0x7f1d8c02e9f3 in __pthread_cond_wait (cond=0x7f1d7d798f90, mutex=0x7f1d7d798f68) at pthread_cond_wait.c:655 #3 0x7f1d7d4a25f4 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7f1d7d4a2639 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7f1d8c0286db in start_thread (arg=0x7f1cf3f8c700) at pthread_create.c:463 #6 0x7f1d9673888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 26 (Thread 0x7f1cf5de9700 (LWP 28561)): #0 0x7f1d9672bbf9 in __GI___poll (fds=0x7f1d4c02b780, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f1d8a3d3539 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f1d8a3d364c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f1d970749bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f1d97019a1a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f1d96e3823a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f1d96e3d17d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f1d8c0286db in start_thread (arg=0x7f1cf5de9700) at pthread_create.c:463 #8
[Akonadi] [Bug 397316] akonadi loses connection with IMAP server after suspend (but not only, DB error too)
https://bugs.kde.org/show_bug.cgi?id=397316 Christian Muehlhaeuser changed: What|Removed |Added CC||mue...@gmail.com --- Comment #2 from Christian Muehlhaeuser --- Same here, happy to provide more logs. Restarting the akonadiserver only lasts for a few minutes here, then I'm back to square 1. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 405491] KMail (in Kontact) crashing upon start or shortly after
https://bugs.kde.org/show_bug.cgi?id=405491 --- Comment #7 from Christian Hilberg --- (In reply to Christian Hilberg from comment #6) > [...] > > Sadly, setting > > vblank_mode=0 __GL_SYNC_TO_VBLANK=0 > > does not fix the issue for me. It does, however, if using the NVidia binary blob (390xx for me). -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 405491] KMail (in Kontact) crashing upon start or shortly after
https://bugs.kde.org/show_bug.cgi?id=405491 --- Comment #6 from Christian Hilberg --- (In reply to Christoph Feck from comment #5) > Crash is in nouveau_dri.so OpenGL driver. > > Please report this issue directly to nouveau developers. See also > https://nouveau.freedesktop.org/wiki/Bugs/ This looks right. It is a known bug upstream, see https://bugreports.qt.io/browse/QTBUG-41242 https://bugs.freedesktop.org/show_bug.cgi?id=91632 Building against OpenGL ES (instead of GLX) seems to evade the issue. Sadly, setting vblank_mode=0 __GL_SYNC_TO_VBLANK=0 does not fix the issue for me. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 405491] KMail (in Kontact) crashing upon start or shortly after
https://bugs.kde.org/show_bug.cgi?id=405491 --- Comment #4 from Christian Hilberg --- Created attachment 118814 --> https://bugs.kde.org/attachment.cgi?id=118814=edit KMail crash trace w/ dbg syms Crash trace with full debug symbols -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 405491] KMail (in Kontact) crashing upon start or shortly after
https://bugs.kde.org/show_bug.cgi?id=405491 --- Comment #3 from Christian Hilberg --- Just as Martin in 404052, I missed debug syms. Got them installed now and trying to get another backtrace. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 404052] Crash during/after filtering inbox, probably related to Qt WebEngine integration
https://bugs.kde.org/show_bug.cgi?id=404052 Christian Hilberg changed: What|Removed |Added CC||hilb...@unix-ag.org --- Comment #12 from Christian Hilberg --- https://bugs.kde.org/show_bug.cgi?id=405491 might be related, though no mail filtering needed (opening a few mails is enough) -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 405491] KMail (in Kontact) crashing upon start or shortly after
https://bugs.kde.org/show_bug.cgi?id=405491 --- Comment #2 from Christian Hilberg --- https://bugs.kde.org/show_bug.cgi?id=404052 might be related, though I do not need to kick off any filters to make the crash happen. Opening E-Mail is enough, it will usually crash after a few mails to be opened. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 405491] KMail (in Kontact) crashing upon start or shortly after
https://bugs.kde.org/show_bug.cgi?id=405491 Christian Hilberg changed: What|Removed |Added Component|general |mail CC||hilb...@unix-ag.org --- Comment #1 from Christian Hilberg --- KMail/Kontact version is 5.9.3 (not selectable in "Version"). -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 405491] New: KMail (in Kontact) crashing upon start or shortly after
https://bugs.kde.org/show_bug.cgi?id=405491 Bug ID: 405491 Summary: KMail (in Kontact) crashing upon start or shortly after Product: kontact Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: hilb...@unix-ag.org Target Milestone: --- Application: kontact (5.9.3) Qt Version: 5.11.3 Frameworks Version: 5.54.0 Operating System: Linux 4.19.0-2-amd64 x86_64 Distribution: Debian GNU/Linux buster/sid -- Information about the crash: Open KMail (in Kontact), it crashes. If it does not, it will do so shortly after. Open a few E-Mails and there you go. I suspect that the crash might be due to graphics handling in the nouveau driver. Experienced the same issue on the nvidia legacy 390 binary driver. Sometimes just before the crash I can see the message pane flashing in red color. This is not the latest KMail but the one packaged with Debian/Buster. I'd like to file a bug with Debian referencing this one on kde.org. They might need to backport an existing fix. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb441e1ff00 (LWP 21090))] Thread 33 (Thread 0x7fb30f7fe700 (LWP 21192)): #0 0x7fb4556053f9 in futex_reltimed_wait_cancelable (private=0, reltime=0x7fb30f7fd400, expected=0, futex_word=0x7fb30f7fd5e8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7fb4556053f9 in __pthread_cond_wait_common (abstime=0x7fb30f7fd4a0, mutex=0x7fb30f7fd598, cond=0x7fb30f7fd5c0) at pthread_cond_wait.c:533 #2 0x7fb4556053f9 in __pthread_cond_timedwait (cond=0x7fb30f7fd5c0, mutex=0x7fb30f7fd598, abstime=0x7fb30f7fd4a0) at pthread_cond_wait.c:667 #3 0x7fb44f19aa37 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fb44f19d30a in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fb44f19d3f2 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fb44f1a1981 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fb44f1a2e61 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7fb44f1abc81 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7fb4555fefa3 in start_thread (arg=) at pthread_create.c:486 #10 0x7fb4567b982f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 32 (Thread 0x7fb319325700 (LWP 21190)): #0 0x7fb4556053f9 in futex_reltimed_wait_cancelable (private=0, reltime=0x7fb319324400, expected=0, futex_word=0x7fb3193245e8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7fb4556053f9 in __pthread_cond_wait_common (abstime=0x7fb3193244a0, mutex=0x7fb319324598, cond=0x7fb3193245c0) at pthread_cond_wait.c:533 #2 0x7fb4556053f9 in __pthread_cond_timedwait (cond=0x7fb3193245c0, mutex=0x7fb319324598, abstime=0x7fb3193244a0) at pthread_cond_wait.c:667 #3 0x7fb44f19aa37 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fb44f19d30a in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fb44f19d3f2 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fb44f1a1981 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fb44f1a2e61 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7fb44f1abc81 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7fb4555fefa3 in start_thread (arg=) at pthread_create.c:486 #10 0x7fb4567b982f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 31 (Thread 0x7fb30700 (LWP 21177)): #0 0x7fb454a782a7 in g_main_context_release () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fb454a790f6 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb454a7925c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb456cde04b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fb456c8b14b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fb456ada0d6 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fb456ae3c77 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fb4555fefa3 in start_thread (arg=) at pthread_create.c:486 #8 0x7fb4567b982f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 30 (Thread 0x7fb31bfff700 (LWP 21156)): #0 0x7fb4556053f9 in futex_reltimed_wait_cancelable (private=0, reltime=0x7fb31bffe400, expected=0, futex_word=0x7fb31bffe5e8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7fb4556053f9 in
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 Christian Boltz changed: What|Removed |Added CC||kde-b...@cboltz.de -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
[kontact] [Bug 403359] Kontact crashes when closing email window
https://bugs.kde.org/show_bug.cgi?id=403359 Christian Trippe changed: What|Removed |Added CC||christiande...@web.de -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 398847] Kaddressbook not parsing gmail contacts
https://bugs.kde.org/show_bug.cgi?id=398847 Christian Hartmann changed: What|Removed |Added CC||chris-hartm...@gmx.de -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 400494] Kontact crashes - clicking other news-feed URL in Akregator while internal webview is opened
https://bugs.kde.org/show_bug.cgi?id=400494 Christian Trippe changed: What|Removed |Added CC||christiande...@web.de -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 399167] Akonadi enters deadlock state which makes it completely unuseable
https://bugs.kde.org/show_bug.cgi?id=399167 Christian Boltz changed: What|Removed |Added CC||kde-b...@cboltz.de -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 399693] New: Standard Calendar changed after update
https://bugs.kde.org/show_bug.cgi?id=399693 Bug ID: 399693 Summary: Standard Calendar changed after update Product: korganizer Version: 5.9.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: christian.saem...@gmx.de Target Milestone: --- After each update, KOrganizer resets the standard calendar to another calendar in my list. That often leads to me adding private appointments to a group calendar which is very annoying. I'm on the openSUSE Tumbleweed packages, not sure if this is a KOrganizer or openSUSE issue. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 398399] using + to move to next unread message keeps the current message also selected
https://bugs.kde.org/show_bug.cgi?id=398399 --- Comment #5 from Christian Kalkhoff --- I still cannot reproduce. But I have had similar issues regarding the last message in the list. When I deleted them, the message list went empty and i had to switch to anouther folder and back to get the list again. That might be related somehow, but is just a guess. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 398399] using + to move to next unread message keeps the current message also selected
https://bugs.kde.org/show_bug.cgi?id=398399 Christian Kalkhoff changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |UNCONFIRMED --- Comment #3 from Christian Kalkhoff --- I did some tests but wasn't able to reproduce in kontact/kmail 5.9.1 on Archlinux. Not sure when 5.9.1 will be released to you by OpenSUSE but chances are, that the bug got fixed in the meantime. So if nobody else is able to reproduce, I would suggest you to wait for 5.9.1 and see if the problem persists. I will have my focus on the described behaviour in my daily usage of kontact, but I cannot remember that something alike happend to me in the past. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 398399] using + to move to next unread message keeps the current message also selected
https://bugs.kde.org/show_bug.cgi?id=398399 Christian Kalkhoff changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO CC||e...@softmetz.de --- Comment #1 from Christian Kalkhoff --- I am unable to reproduce this bug in 5.9.1 on Archlinux. Are you able to update and reproduce? If not, can you please tell which message list mode, ordering, grouping, etc you are using? -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 398431] KOrganizer task category view doesn't work
https://bugs.kde.org/show_bug.cgi?id=398431 Christian Kalkhoff changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||e...@softmetz.de Resolution|--- |INVALID --- Comment #2 from Christian Kalkhoff --- As requested by the reporter I am closing this. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 357647] Journal shows HTML source instead of rendered rich text in entry list and print preview
https://bugs.kde.org/show_bug.cgi?id=357647 Christian Kalkhoff changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #5 from Christian Kalkhoff --- Just tried to reproduce the bug. As it turns out, it works as expected in current versions. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 345992] Keyboard shortcut assigned to "archive mail" works once, unconfigures itself
https://bugs.kde.org/show_bug.cgi?id=345992 Christian Kalkhoff changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from Christian Kalkhoff --- The bug seems to have been fixed in current versions. So I am closing it. -- You are receiving this mail because: You are the assignee for the bug.
[kmail] [Bug 141199] template per idendity: double scrollbars
https://bugs.kde.org/show_bug.cgi?id=141199 Christian Boltz changed: What|Removed |Added Resolution|UNMAINTAINED|FIXED --- Comment #6 from Christian Boltz --- Actually this was fixed years ago (see my comment from 2010) - but back then, I didn't have enough bugzilla permissions to mark the bug as fixed ;-) -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 385847] Kontact crashes on restart
https://bugs.kde.org/show_bug.cgi?id=385847 --- Comment #2 from Christian --- Created attachment 114634 --> https://bugs.kde.org/attachment.cgi?id=114634=edit New crash information added by DrKonqi kontact (5.8.3) using Qt 5.9.6 - What I was doing when the application crashed: I started Kontact from the start menu because it had disappeared from the screen when a new email was arriving. The crash message appeared when Kontact was starting up, with the main window visible on the overview screen. -- Backtrace (Reduced): #7 0x7fb3ebe05d77 in QtWebEngineCore::NetworkDelegateQt::OnBeforeURLRequest(net::URLRequest*, base::Callback const&, GURL*) () from /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7fb3ecb92556 in net::NetworkDelegate::NotifyBeforeURLRequest(net::URLRequest*, base::Callback const&, GURL*) () from /usr/lib64/libQt5WebEngineCore.so.5 #9 0x7fb3ecc992fb in net::URLRequest::Start() () from /usr/lib64/libQt5WebEngineCore.so.5 #10 0x7fb3ec18a9f0 in content::ResourceLoader::StartRequestInternal() () from /usr/lib64/libQt5WebEngineCore.so.5 #11 0x7fb3ec18ab00 in content::ResourceLoader::StartRequest() () from /usr/lib64/libQt5WebEngineCore.so.5 -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 385847] Kontact crashes on restart
https://bugs.kde.org/show_bug.cgi?id=385847 Christian changed: What|Removed |Added CC||gen...@moin.fi -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 395117] New: HTML mails are not detected correctly
https://bugs.kde.org/show_bug.cgi?id=395117 Bug ID: 395117 Summary: HTML mails are not detected correctly Product: kmail2 Version: 5.8.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: mue...@gmail.com Target Milestone: --- More often than not, KMail in recent times tells me that HTML mails are just plain text messages, even though they show correctly in other Mail clients and I can see the HTML part in the mail's source. === Example mail source === ... Content-Type: Multipart/Alternative; boundary="Boundary-00=_RC6YVA40" ... --Boundary-00=_RC6YVA40 Content-Type: Text/Plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable [---001:00:0---] --Boundary-00=_RC6YVA40 Content-Type: Text/Html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable ... -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 393899] Kontact-17.12.3 Window position not restored correctly when logging in to KDE desktop
https://bugs.kde.org/show_bug.cgi?id=393899 Christian <gen...@moin.fi> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #2 from Christian <gen...@moin.fi> --- Does not happen regularly - closing this bug report myself. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 393898] Kmail2 EWS does not load contacts - version 17.12.3
https://bugs.kde.org/show_bug.cgi?id=393898 --- Comment #3 from Christian <gen...@moin.fi> --- Dear Krzysztof! (Thanks by the way for having made this piece of software, I'm very happy about it.) I edited that line in the [Rules] section to state =true (before it was =false). In the system log, the entries that appear now are: touko 07 10:22:22 puolukka akonadi_ews_resource[4302]: org.kde.pim.ews.client.request: Starting SyncFolderItems request (folder: EwsId(1yxfcpf, qai4hn), state: 1ejz0gd touko 07 10:22:22 puolukka akonadi_ews_resource[4302]: org.kde.pim.ews.client.request: Got SyncFolderItems response (0 changes, last included: true, state: r7s0bd) Every time I right-click on the folder and "update", it gives two similar lines, the state from the last "response" is shown as the state of the next "request", the other information remains the same. I'm attaching the log for akonadi_ews_resource, starting from when I logged in to KDE and opened Kontact. Note, there are two EWS accounts but both are on the same server and have the same problem. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 393898] Kmail2 EWS does not load contacts - version 17.12.3
https://bugs.kde.org/show_bug.cgi?id=393898 --- Comment #2 from Christian <gen...@moin.fi> --- Created attachment 112459 --> https://bugs.kde.org/attachment.cgi?id=112459=edit from system log -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 393899] Kontact-17.12.3 Window position not restored correctly when logging in to KDE desktop
https://bugs.kde.org/show_bug.cgi?id=393899 --- Comment #1 from Christian <gen...@moin.fi> --- Hmm, this behaviour doesn't happen every time. Maybe it has to do with akgregator - sometimes I see a message in Kontact saying that akgregator did not shut down correctly the last time it was run. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 393899] New: Kontact-17.12.3 Window position not restored correctly when logging in to KDE desktop
https://bugs.kde.org/show_bug.cgi?id=393899 Bug ID: 393899 Summary: Kontact-17.12.3 Window position not restored correctly when logging in to KDE desktop Product: kontact Version: unspecified Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: gen...@moin.fi Target Milestone: --- When I leave Kontact open and log out, then log in again, Kontact is re-opened (as expected), but its window position is wrong. Steps to reproduce: 1. Put a panel at the top of the screen 2. Maximize Kontact window - it covers the area that is not occupied by the panel. 3. Log out and log in again Expected behaviour: Kontact window should be in the same place as before Actual behaviour: Kontact window has the same size as before, but it is shifted up to the top of the screen so that its window title is hidden by the panel - and there is a little bit of desktop visible at the bottom of the screen. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 393898] New: Kmail2 EWS does not load contacts - version 17.12.3
https://bugs.kde.org/show_bug.cgi?id=393898 Bug ID: 393898 Summary: Kmail2 EWS does not load contacts - version 17.12.3 Product: Akonadi Version: unspecified Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: EWS Resource Assignee: kdepim-bugs@kde.org Reporter: gen...@moin.fi CC: kri...@op.pl Target Milestone: --- I managed to set up my Exchange account in KMail2 now that there's a patch for bug 390798 (unable to login to EWS account). Email folders, receiving and sending, and read-only calendar works. But I cannot see any contacts in the Contacts folder. Observed behaviour: When I open the "Addressbook" tab, I can see the Contacts folder shown in the tree under my account. KMail2 is indicating that the folder is updating. (After a while, it shows that the updating is finished, but it is very slow.) When I right-click the folder and select Properties, I can see the count of contacts (Statistics: Content - 118 objects. Size - 0 B.) But no contacts are shown in the folder in KMail and I cannot access my contacts. Desired behaviour: The contact folder shows all the contacts that are on the EWS account. Note: My contacts are stored in the Contacts folder and not in a Global Address List (GAL) - I read on the old akonadi-EWS blog that GAL are not yet supported. This should not be the problem here. I am not sure how to obtain debug information for this bug - can someone advise me? Thanks! -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 393002] Akonadi-ews does not save password in kwallet
https://bugs.kde.org/show_bug.cgi?id=393002 Christian <gen...@moin.fi> changed: What|Removed |Added CC||gen...@moin.fi --- Comment #3 from Christian <gen...@moin.fi> --- Bug still present in version 17.12.3 - can't find this version number in the version dropdown though. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 390798] Akonadi EWS failed to authenticate with Exchange Server
https://bugs.kde.org/show_bug.cgi?id=390798 --- Comment #13 from Christian <gen...@moin.fi> --- Stefan, thanks! I've applied that patch to kdepim-runtime 17.12.3 and it fixed my problem. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 389369] Can't Authenticate to Office 365
https://bugs.kde.org/show_bug.cgi?id=389369 Christian <gen...@moin.fi> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||gen...@moin.fi Resolution|--- |DUPLICATE --- Comment #6 from Christian <gen...@moin.fi> --- Probably a duplicate of bug 393002 *** This bug has been marked as a duplicate of bug 393002 *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 393002] Akonadi-ews does not save password in kwallet
https://bugs.kde.org/show_bug.cgi?id=393002 Christian <gen...@moin.fi> changed: What|Removed |Added CC||ereno...@hotmail.com --- Comment #2 from Christian <gen...@moin.fi> --- *** Bug 389369 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 390799] EWS resource didn't appear in list of directory
https://bugs.kde.org/show_bug.cgi?id=390799 Christian <gen...@moin.fi> changed: What|Removed |Added Resolution|--- |DUPLICATE CC||gen...@moin.fi Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christian <gen...@moin.fi> --- Possibly a duplicate of bug 390798 ? *** This bug has been marked as a duplicate of bug 390798 *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 390798] Akonadi EWS failed to authenticate with Exchange Server
https://bugs.kde.org/show_bug.cgi?id=390798 --- Comment #10 from Christian <gen...@moin.fi> --- *** Bug 390799 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 390139] EWS Password not saved and Server Offline
https://bugs.kde.org/show_bug.cgi?id=390139 Christian <gen...@moin.fi> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||gen...@moin.fi --- Comment #2 from Christian <gen...@moin.fi> --- Possibly a duplicate of bug 390798 ? *** This bug has been marked as a duplicate of bug 390798 *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 390798] Akonadi EWS failed to authenticate with Exchange Server
https://bugs.kde.org/show_bug.cgi?id=390798 --- Comment #9 from Christian <gen...@moin.fi> --- *** Bug 390139 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 390798] Akonadi EWS failed to authenticate with Exchange Server
https://bugs.kde.org/show_bug.cgi?id=390798 --- Comment #7 from Christian <gen...@moin.fi> --- Anders, the behaviour you mentioned with the password not being stored sounds more like bug 393002, not this bug (where the password is stored but EWS fails to connect). -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 390798] Akonadi EWS failed to authenticate with Exchange Server
https://bugs.kde.org/show_bug.cgi?id=390798 Christian <gen...@moin.fi> changed: What|Removed |Added CC||gen...@moin.fi --- Comment #4 from Christian <gen...@moin.fi> --- I have the same issue with kdepim version 17.12.3. The password is stored in the password dialog, and clicking on "Try connect" works - the status on the tab "Status" changes to OK then and presents the Exchange version number (in my case, 14.3.361.1 Exchange 2010 SP3). But the "Subscription" tab shows "Failed to retrieve folder list", and when I close the dialog with OK, the account itself shows "Unable to connect to Exchange server". If you need more info to diagnose this problem, please let me know. Another, maybe unrelated issue - in the Evolution EWS plugin, I can login to the EWS account using my email address and password. In the akonadi plugin, I have to use a strange user name that took me a while to find in the interface of the Exchange webmail. (In reply to Olivier from comment #0) > Once configured Akonadi EWS plugin, clikc on "Test Connection work", but > click on "OK" failed and plugin remains not connected. > > Once activate kio_http debug, it seems that the NTLM handshake is correctly > executed when testing the connection. Akonadi EWS try without any auth, got > a 401, then try with simple NTLM v1, got 401 again, and finally try with > NTLMv2 and got a 200 OK. When clicking on "OK", Akonadi EWS just try NTLMv1 > and newer try NTLMv2. > > It seems that this bugs is related to old NTLM problem in kio_http patched > by the author of akonadi_ews plugin. > > Note that same credential with Exchange or Thunderbird work fine and that > using a kerberos ticket allows authentication. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 390131] Sorting of folders in folder tree
https://bugs.kde.org/show_bug.cgi?id=390131 Christian Muehlhaeuser <mue...@gmail.com> changed: What|Removed |Added CC||mue...@gmail.com --- Comment #2 from Christian Muehlhaeuser <mue...@gmail.com> --- I have weird sorting results, too: - Automatically sorting by Name puts the account "GMail" before "Beehive" - Manually sorting by drag & drop doesn't seem to work at all (even though selected in the header's context menu) -- You are receiving this mail because: You are the assignee for the bug.
