[kmail2] [Bug 486119] Replying to a particular HTML message hangs Kmail
https://bugs.kde.org/show_bug.cgi?id=486119 --- Comment #4 from Peter --- I ran kmail from a terminal, and got the messages, QAbstractAnimation::pause: Cannot pause a stopped animation org.kde.pim.kmail: setFcc: collection invalid "" Path override failed for key base::DIR_APP_DICTIONARIES and path '/usr/bin/qtwebengine_dictionaries' Path override failed for key base::DIR_APP_DICTIONARIES and path '/usr/lib/qt6/libexec/qtwebengine_dictionaries' Path override failed for key base::DIR_APP_DICTIONARIES and path '/usr/lib/qt6/libexec/qtwebengine_dictionaries' Is this significant? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 486119] Replying to a particular HTML message hangs Kmail
https://bugs.kde.org/show_bug.cgi?id=486119 --- Comment #3 from Peter --- (In reply to Peter from comment #0) > SUMMARY > I have one HTML email chain, in particular, for which replying causes Kmail > to hang. > > STEPS TO REPRODUCE > 1. Start Kmail > 2. Select HTML email. > 3. Select Reply to. > > OBSERVED RESULT > Kmail hangs. Sometimes it opens the composer after a number of minutes. > However, if I try to compose a reply, the window hangs, with title bar > showing it as 'not responding', after entering a couple of lines. > > Strangely, there is one more kmail task listed in Task Managerthan in > System Monitor. (See screenshot.) > > Even if I kill the kmail process, or reboot, the kmail process is still > there, in the same hung state. > > EXPECTED RESULT > > > SOFTWARE/OS VERSIONS > Operating System: KDE neon 6.0 > KDE Plasma Version: 6.0.4 > KDE Frameworks Version: 6.1.0 > Qt Version: 6.7.0 > Kernel Version: 6.5.0-28-generic (64-bit) > Graphics Platform: Wayland > Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz > Memory: 7.5 GiB of RAM > Graphics Processor: Mesa Intel® Xe Graphics > Manufacturer: Dell Inc. > Product Name: XPS 13 9305 > > ADDITIONAL INFORMATION > I realise this isn't much information to go on, but I can attempt to provide > more if someone lets me know what to provide. (Would a copy of the message > be any help?) > > This seems similar to #484729, but this bug is reported as fixed. What makes the problem worse is that, on terminating and restarting the Kmail process, both a main Kmail window and a composer window for the reply try to open, resulting in Kmail hanging again. This can happen again and again. Eventually, I will manage to restart Kmail properly, but I haven't managed to identify what allows this to happen. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 486835] New: Composer window geometries are mixed up with kmail main window geometries
https://bugs.kde.org/show_bug.cgi?id=486835 Bug ID: 486835 Summary: Composer window geometries are mixed up with kmail main window geometries Classification: Applications Product: kmail2 Version: 6.0.2 Platform: openSUSE OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: h...@urpla.net Target Milestone: --- First of all, still running on X11 because bko#377162, sorry! With earlier kmail versions, the composer windows managed its own geometries, e.g. creating a new mail used the window size and position of the last composer window. With 24.02.2, this behaviour is lost, and kmail main window geometries are mixed up with composer window geometries: a new composer window inherits the main window size. In my setup, I'm running kmail main window vertically expanded on a huge 30" screen (since ages). But now, new composer windows are drawn with the same size. Before, it maintained the composer window geometries independently of the main window, and appeared a lot smaller in my setup. Another indication of this new behaviour and the mix-up is reproduced like this: Start up kmail. Resize vertical size to take the full screen height (up to the control panel, of course). Open a new mail. Resize the composer window to a different size, say half of the main window. Close the main window. Close the composer window. Restart kmail, et voilà, the main window appears with the size of the last composer window. This is a regression from my point of view. The kmail main and composer windows should manage their geometries independently. The new behaviour looks and feels ugly, as well as usability is awkward. Also, semantically, main and composer windows act quite different semantically, hence their geometries should be managed separately as well. Operating System: openSUSE Tumbleweed 20240429 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-7-preempt (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor Memory: 62.4 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3060/PCIe/SSE2 Manufacturer: ASUS kmail 24.02.2 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 486119] Replying to a particular HTML message hangs Kmail
https://bugs.kde.org/show_bug.cgi?id=486119 --- Comment #2 from Peter --- Created attachment 168897 --> https://bugs.kde.org/attachment.cgi?id=168897=edit Screenshot -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 486119] Replying to a particular HTML message hangs Kmail
https://bugs.kde.org/show_bug.cgi?id=486119 --- Comment #1 from Peter --- Created attachment 168896 --> https://bugs.kde.org/attachment.cgi?id=168896=edit Screenshot -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 486119] New: Replying to a particular HTML message hangs Kmail
https://bugs.kde.org/show_bug.cgi?id=486119 Bug ID: 486119 Summary: Replying to a particular HTML message hangs Kmail Classification: Applications Product: kmail2 Version: 6.0.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: misc Assignee: kdepim-bugs@kde.org Reporter: p.wibber...@btinternet.com Target Milestone: --- SUMMARY I have one HTML email chain, in particular, for which replying causes Kmail to hang. STEPS TO REPRODUCE 1. Start Kmail 2. Select HTML email. 3. Select Reply to. OBSERVED RESULT Kmail hangs. Sometimes it opens the composer after a number of minutes. However, if I try to compose a reply, the window hangs, with title bar showing it as 'not responding', after entering a couple of lines. Strangely, there is one more kmail task listed in Task Managerthan in System Monitor. (See screenshot.) Even if I kill the kmail process, or reboot, the kmail process is still there, in the same hung state. EXPECTED RESULT SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.5.0-28-generic (64-bit) Graphics Platform: Wayland Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: Dell Inc. Product Name: XPS 13 9305 ADDITIONAL INFORMATION I realise this isn't much information to go on, but I can attempt to provide more if someone lets me know what to provide. (Would a copy of the message be any help?) This seems similar to #484729, but this bug is reported as fixed. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 467832] Add ability to change position of subject column in classic list view
https://bugs.kde.org/show_bug.cgi?id=467832 --- Comment #5 from Peter --- (In reply to Peter from comment #4) > (In reply to Laurent Montel from comment #1) > > We put it in first column because we have support for thread message. > > => it will be wierd if we change it. > > by default it's better to show subject in first column > (In reply to heinoldk from comment #3) > > (In reply to Laurent Montel from comment #1) > > > We put it in first column because we have support for thread message. > > > => it will be wierd if we change it. > > > by default it's better to show subject in first column > > > > Thank you for the fast reply. > > I don't quite see how having the subject in the first column is coupled to > > supporting message threads. I added another example from Gnome Revolution > > which demonstrates how it could look like. > > Of course, having robust defaults is good and I don't want to convince you > > to change these. > > I was just hoping for more customizability in this regard and thought it > > could be possible without too much effort or additional complexity. > Hi Laurent, > > Ideally, I'd like to have tags displayed in the first column, but if I > right-click the top of the message list, and check Important and/or Action, > I can't drag those extra columns to the left. I see that there's a > Read/Unread icon on the very left-hand side, which seems to be part of the > Subject column, but I can't work out how to add other tags to this ( > although I could swear I succeeded with a previous installation of KMail). > I tried the Message - Mark Message menu, but this is confusing - why is the > functionality different for different tags, i.e. a menu item for 'Mark > Message as Unread' but a checkbox for 'Remove Important Mark'? - and doesn't > appear to have any effect. > > Many thanks and regards. > > KMail 6.0.1 (24.02.1) I've just worked out that you can achieve whatever you want - this must be what I'd done in a previous installation - by defining a new theme under Settings -> Configure KMail - > Appearance -> Message List -> Configure -> Appearance. This includes having anything, other than Subject, in the first column. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 467832] Add ability to change position of subject column in classic list view
https://bugs.kde.org/show_bug.cgi?id=467832 Peter changed: What|Removed |Added CC||p.wibber...@btinternet.com --- Comment #4 from Peter --- (In reply to Laurent Montel from comment #1) > We put it in first column because we have support for thread message. > => it will be wierd if we change it. > by default it's better to show subject in first column (In reply to heinoldk from comment #3) > (In reply to Laurent Montel from comment #1) > > We put it in first column because we have support for thread message. > > => it will be wierd if we change it. > > by default it's better to show subject in first column > > Thank you for the fast reply. > I don't quite see how having the subject in the first column is coupled to > supporting message threads. I added another example from Gnome Revolution > which demonstrates how it could look like. > Of course, having robust defaults is good and I don't want to convince you > to change these. > I was just hoping for more customizability in this regard and thought it > could be possible without too much effort or additional complexity. Hi Laurent, Ideally, I'd like to have tags displayed in the first column, but if I right-click the top of the message list, and check Important and/or Action, I can't drag those extra columns to the left. I see that there's a Read/Unread icon on the very left-hand side, which seems to be part of the Subject column, but I can't work out how to add other tags to this ( although I could swear I succeeded with a previous installation of KMail). I tried the Message - Mark Message menu, but this is confusing - why is the functionality different for different tags, i.e. a menu item for 'Mark Message as Unread' but a checkbox for 'Remove Important Mark'? - and doesn't appear to have any effect. Many thanks and regards. KMail 6.0.1 (24.02.1) -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 484149] New: kmail crashes due to missing libZXing.so.3
https://bugs.kde.org/show_bug.cgi?id=484149 Bug ID: 484149 Summary: kmail crashes due to missing libZXing.so.3 Classification: Applications Product: kmail2 Version: 6.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: misc Assignee: kdepim-bugs@kde.org Reporter: p.wibber...@btinternet.com Target Milestone: --- SUMMARY *** As of yesterday (20 March 2024) Kmail started crashing every time I tried to launch it. Launching it from Konsole, it reported missing libZXing.so.3. 1. Start kmail 2. 3. OBSERVED RESULT Kmail crashes, reporting libZXing.so.3 EXPECTED RESULT kmail should start normally. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon 6.0 (available in About System) KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION The problem is fixed by installed libZXing. Is this a new dependency? If not, why did it disappear? Thanks and regards -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 480733] Kmail 'Export to PDF' crops message
https://bugs.kde.org/show_bug.cgi?id=480733 --- Comment #4 from Peter --- Hi Laurent, I don't know whether it's the same issue or something entirely different, but I also get the problem with 'Print' and 'Print Preview'. I get it with kmail 6.0.0, too. Thanks and regards -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 480733] Kmail 'Export to PDF' crops message
https://bugs.kde.org/show_bug.cgi?id=480733 --- Comment #3 from Peter --- Laurent, Apologies for not seeing your messages earlier. Do I understand you have the information you need? Thanks and regards. P -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 481317] Kmail crashed when forwarding a message
https://bugs.kde.org/show_bug.cgi?id=481317 --- Comment #1 from Peter --- Created attachment 165817 --> https://bugs.kde.org/attachment.cgi?id=165817=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 481317] New: Kmail crashed when forwarding a message
https://bugs.kde.org/show_bug.cgi?id=481317 Bug ID: 481317 Summary: Kmail crashed when forwarding a message Classification: Applications Product: kmail2 Version: unspecified Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: p.wibber...@btinternet.com Target Milestone: --- Application: kmail (5.24.4 (23.08.4)) Qt Version: 5.15.12 Frameworks Version: 5.114.0 Operating System: Linux 6.5.0-17-generic x86_64 Windowing System: X11 Distribution: KDE neon 5.27 DrKonqi: 5.27.10 [CoredumpBackend] -- Information about the crash: Kmail crashed when I selected 'Forward' for a particular email. The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #6 0x7f58712b2aa7 in MimeTreeParser::ObjectTreeParser::processType(KMime::Content*, MimeTreeParser::ProcessResult&, QByteArray const&) () from /lib/x86_64-linux-gnu/libKPim5MimeTreeParser.so.5 #7 0x7f58712b31fd in MimeTreeParser::ObjectTreeParser::parseObjectTreeInternal(KMime::Content*, bool) () from /lib/x86_64-linux-gnu/libKPim5MimeTreeParser.so.5 #8 0x7f58712b34ff in MimeTreeParser::ObjectTreeParser::parseObjectTree(KMime::Content*, bool) () from /lib/x86_64-linux-gnu/libKPim5MimeTreeParser.so.5 #9 0x7f5871e5b982 in TemplateParser::TemplateParserJob::processWithTemplate(QString const&) () from /lib/x86_64-linux-gnu/libKPim5TemplateParser.so.5 #10 0x7f5871e5d0b8 in TemplateParser::TemplateParserJob::process(QSharedPointer const&, long long) () from /lib/x86_64-linux-gnu/libKPim5TemplateParser.so.5 Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 480733] New: Kmail 'Export to PDF' crops message
https://bugs.kde.org/show_bug.cgi?id=480733 Bug ID: 480733 Summary: Kmail 'Export to PDF' crops message Classification: Applications Product: kmail2 Version: 5.24.4 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: p.wibber...@btinternet.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Open a email that is more than one page long. 2. Select 'Export to PDF' OBSERVED RESULT The PDF file is missing message text at the bottom and top of each page, as if some of the message is being printed outside the 'print area'. A similar problem arises if the message is printed to PDF file. The Margins in File.Print.Properties has a default value of 0.14in, but increasing this to 1.14in or decreasing it to zero does not seem to solve the problem. EXPECTED RESULT The PDF file should show all of the message text, regardless of the margins. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon 5.27 (available in About System) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.114.0 Qt Version: 5.15.12 ADDITIONAL INFORMATION -- 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 #236 from Peter Humphrey --- I think the real problem in KMail is in the handling of locally stored emails. Since I installed a local server to fetch POP3 mails from my ISP and serve them to KMail as IMAP4, the problem has largely gone away. The problem was still present at in interim stage when I was downloading all mails from my IMAP4 server, but now that I leave them on the server I don't see the problem any more. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 473897] Cannot add Google Groupware, "Configured account does not exist" then "Resource is not configured"
https://bugs.kde.org/show_bug.cgi?id=473897 --- Comment #26 from Peter Ries --- same for me: works now. Used akonadi console directly. didn't try other options. Thanks!! -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 473897] Cannot add Google Groupware, "Configured account does not exist" then "Resource is not configured"
https://bugs.kde.org/show_bug.cgi?id=473897 Peter Ries changed: What|Removed |Added CC||peterrie...@yahoo.de --- Comment #19 from Peter Ries --- I updated toad to 23.08.01 - no luck. Still the not syncing issue. After trying to re-add google account it remains in state (not configured) -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 470820] Unable to configure Google Calendar
https://bugs.kde.org/show_bug.cgi?id=470820 Peter Ries changed: What|Removed |Added CC||peterrie...@yahoo.de --- Comment #2 from Peter Ries --- same issue for me. after google calendar stopped syncing (most likely when update kde gear from 23.04 -> 23.08) today when 23.08.01 came out calendar still was not syncing. I removed google groupware account and re-added it. But it came with no dialog. Just being displayed "Google Groupware (not configured)". Klick on Edit does not do anything. Reboot, clear ~/.cache... no effect - any way to help with logs? How / where to look? -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 357819] Korganizer doesn't send calendar events to Google account
https://bugs.kde.org/show_bug.cgi?id=357819 --- Comment #10 from Peter Ries --- unfortunately not fixed in 23.08.01 which came out today -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 373348] Korganizer doesn't fetch events from Google
https://bugs.kde.org/show_bug.cgi?id=373348 --- Comment #7 from Peter Ries --- Thanks Colin, I just wanted to add the in fo that the error obviously came with the update from 23.04.3-1 -> 23.08.0-1 (tested in a VM that was not updated yet and worked fine) -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 357819] Korganizer doesn't send calendar events to Google account
https://bugs.kde.org/show_bug.cgi?id=357819 Peter Ries changed: What|Removed |Added CC||peterrie...@yahoo.de --- Comment #8 from Peter Ries --- @jack: can confirm that it stopped working somewhen during the last days. My Calendar synced fine in both directions but I saw that some newer events were not synced anymore. I tried adding an event to Korganizer as well as Google via browser. Both only stayed where I created them. No sync. PIM mudule says "Ready". I even tried to re-authenticate. No effect. No sync. As said: it worked fine until ~ 4 weeks ago. No clue where to debug. -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 373348] Korganizer doesn't fetch events from Google
https://bugs.kde.org/show_bug.cgi?id=373348 Peter Ries changed: What|Removed |Added CC||peterrie...@yahoo.de --- Comment #5 from Peter Ries --- @jack: can confirm that it stopped working somewhen during the last days. My Calendar synced fine in both directions but I saw that some newer events were not synced anymore. I tried adding an event to Korganizer as well as Google via browser. Both only stayed where I created them. No sync. PIM mudule says "Ready". I even tried to re-authenticate. No effect. No sync. As said: it worked fine until ~ 4 weeks ago. No clue where to debug. -- You are receiving this mail because: You are on the CC list for the bug.
[kmail2] [Bug 473007] Feature request: allow the time of day of automatic archives to be specified.
https://bugs.kde.org/show_bug.cgi?id=473007 --- Comment #7 from Peter Humphrey --- Thank you! -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 473007] Feature request: allow the time of day of automatic archives to be specified.
https://bugs.kde.org/show_bug.cgi?id=473007 Peter Humphrey changed: What|Removed |Added CC||pe...@prh.myzen.co.uk --- Comment #4 from Peter Humphrey --- (In reply to Laurent Montel from comment #2) > Created attachment 160853 [details] > dialog for configuring archive folder > > Do you speak about this dialog ? Yes, that's the one. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 473007] New: Feature request: allow the time of day of automatic archives to be specified.
https://bugs.kde.org/show_bug.cgi?id=473007 Bug ID: 473007 Summary: Feature request: allow the time of day of automatic archives to be specified. Classification: Applications Product: kmail2 Version: 5.23.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: pe...@prh.myzen.co.uk Target Milestone: --- SUMMARY I'd prefer that automatic archives of KMail's messages were done during the night, so that incoming mail does not disturb the operation. STEPS TO REPRODUCE 1. Select the Configure Automatic Archiving dialogue 2. Fill in the boxes as required. 3. There's no way to specify the time of day that the archive should be made. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 Kernel version: 6.1.41-gentoo (64-bit) ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 472052] New: Crash when Find Messages
https://bugs.kde.org/show_bug.cgi?id=472052 Bug ID: 472052 Summary: Crash when Find Messages Classification: Applications Product: kmail2 Version: unspecified Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: p.wibber...@btinternet.com Target Milestone: --- Application: kmail (5.23.2 (23.04.2)) Qt Version: 5.15.10 Frameworks Version: 5.107.0 Operating System: Linux 5.19.0-46-generic x86_64 Windowing System: X11 Distribution: KDE neon 5.27 DrKonqi: 5.27.6 [CoredumpBackend] -- Information about the crash: Kmail crashed when searching in all folders using 'Find Messages'. The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #6 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140131755254208) at ./nptl/pthread_kill.c:44 #7 __pthread_kill_internal (signo=6, threadid=140131755254208) at ./nptl/pthread_kill.c:78 #8 __GI___pthread_kill (threadid=140131755254208, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #9 0x7f7300442476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #10 0x7f73004287f3 in __GI_abort () at ./stdlib/abort.c:79 Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 467148] ALTER DATABASE akonadi REFRESH COLLATION VERSION
https://bugs.kde.org/show_bug.cgi?id=467148 Hans-Peter Jansen changed: What|Removed |Added CC||h...@urpla.net --- Comment #1 from Hans-Peter Jansen --- Hi Axel, can confirm this issue for akonadi with postgres here! This fixed it for me: $ export $(grep Host $HOME/.config/akonadi/akonadiserverrc) $ psql -h $Host akonadi akonadi=# ALTER DATABASE akonadi REFRESH COLLATION VERSION; HINWEIS: Version wird von 2.36 in 2.37 geändert ALTER DATABASE akonadi=# \q -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 467746] New: Korganizer Events not appearing in Google Calendar
https://bugs.kde.org/show_bug.cgi?id=467746 Bug ID: 467746 Summary: Korganizer Events not appearing in Google Calendar Classification: Applications Product: korganizer Version: 5.22.3 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: groupware Assignee: kdepim-bugs@kde.org Reporter: p.wibber...@btinternet.com Target Milestone: --- SUMMARY I have added a Google Calendar. Events in Google Calendar are imported into Korganizer, but events in Korganizer are not being exported to Google Calendar. I am convinced this used to work, but it seems to have stopped at some while ago (not sure when). STEPS TO REPRODUCE 1. Create Event in Korganizer 2. Create Event in Google Calendar 3. Sync with Google Calendar by selecting Configure Korganizer -> General -> Calendars -> Google Groupware -> Restart OBSERVED RESULT Google Calendar event appears in Korganizer, BUT Korganizer Event does not appear in Google Calendar EXPECTED RESULT Google Calendar event appears in Korganizer, AND Korganizer Event appears in Google Calendar SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon 5.27 (available in About this System) KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION This used to work some months ago, but seems to have stopped at some point (not sure when). Akonadiconsole shows the message, ' kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "%1, %2" msgid_plural: "" msgctxt: "Two statuses, for example \"Online, Running (66%)\" or \"Offline, Broken\"" '. I have no idea whether this is relevant. Any further troubleshooting ideas gratefully received. Thanks and regards -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 400281] WebEngine initialized from a plugin
https://bugs.kde.org/show_bug.cgi?id=400281 Peter Humphrey changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- CC||pe...@prh.myzen.co.uk --- Comment #3 from Peter Humphrey --- Cannot repeat now. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 462963] New: Multiple Default Reminders
https://bugs.kde.org/show_bug.cgi?id=462963 Bug ID: 462963 Summary: Multiple Default Reminders Classification: Applications Product: korganizer Version: 5.21.3 Platform: Neon OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: p.wibber...@btinternet.com Target Milestone: --- SUMMARY *** Just as it is possible to set multiple reminders for individual events, it would be very useful if the Configure.Time and Date page allowed the setting of more than one default reminder. Thanks and regards *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 448106] KOrganizer crashes on startup
https://bugs.kde.org/show_bug.cgi?id=448106 --- Comment #3 from Peter Huyoff --- Created attachment 154220 --> https://bugs.kde.org/attachment.cgi?id=154220=edit KOrganizer crashes every time, i try o start it. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 425205] KMail crashes on first start after Tumbleweed dist-upgrade
https://bugs.kde.org/show_bug.cgi?id=425205 Peter Huyoff changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #4 from Peter Huyoff --- This error no longer occurs on my systems and can therefore be closed! -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 385081] Misleading choice of recipient list title instead of addresses
https://bugs.kde.org/show_bug.cgi?id=385081
--- Comment #3 from Peter ---
Hello,
apparently the bug is gone with Kontact 5.19.3
Thanks a lot
Peter Willadt
fon +49 72 31 10 24 30
fax +49 72 31 13 95 43
%-%-%-%-%-%-%-%-%-%-%-%-%-%-%-%-%-%-%-%-
\def\hackerspiel{\message{User:}
\read-1to\nam\message{Password:}
\read-1to\pwd\message{Sorry, invalid. Try again:}
\next}\let\next\hackerspiel\hackerspiel
%-%-%-%-%-%-%-%-%-%-%-%-%-%-%-%-%-%-%-%-
--
You are receiving this mail because:
You are the assignee for the bug.
[kmail2] [Bug 385081] Misleading choice of recipient list title instead of addresses
https://bugs.kde.org/show_bug.cgi?id=385081 Peter changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #2 from Peter --- With Contact 5.19.3, the bug is gone. List gets resolved to individual addresses. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 393421] No ability to hide the HTML Message Status Bar
https://bugs.kde.org/show_bug.cgi?id=393421 --- Comment #69 from Peter Humphrey --- This is still the wrong decision. You are taking away my responsibility for my own actions. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 423904] KMail crashes while gmail-sync
https://bugs.kde.org/show_bug.cgi?id=423904 --- Comment #2 from Peter Huyoff --- With the actual version of KMail, this bug doesn't exist. 12.10.2022 05:49:46 Justin Zobel : > https://bugs.kde.org/show_bug.cgi?id=423904 > > Justin Zobel changed: > > What |Removed |Added > > Status|REPORTED |NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #1 from Justin Zobel --- > Thank you for reporting this crash in KDE software. As it has been a while > since this issue was reported, can we please ask you to see if you can > reproduce the crash with a recent software version? > > If you can reproduce the issue, please change the status to "CONFIRMED" when > replying. Thank you! > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 362579] Segfault when selecting multiple adresses from contact list
https://bugs.kde.org/show_bug.cgi?id=362579 --- Comment #12 from Peter --- Bug is still present with 5.19.3 (when choosing recipients with shift-click). -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 362579] Segfault when selecting multiple adresses from contact list
https://bugs.kde.org/show_bug.cgi?id=362579 --- Comment #10 from Peter --- Am Samstag, 8. Oktober 2022, 02:38:47 CEST schrieben Sie: > https://bugs.kde.org/show_bug.cgi?id=362579 > > Justin Zobel changed: > >What|Removed |Added > > Resolution|--- |WAITINGFORINFO > Status|CONFIRMED |NEEDSINFO > > --- Comment #9 from Justin Zobel --- > Thank you for reporting this crash in KDE software. As it has been a while > since this issue was reported, can we please ask you to see if you can > reproduce the crash with a recent software version? > > If you can reproduce the issue, please change the status to "CONFIRMED" when > replying. Thank you! seems to be fixed with version 5.19.3 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 459186] New: akondi crash
https://bugs.kde.org/show_bug.cgi?id=459186 Bug ID: 459186 Summary: akondi crash Product: Akonadi Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: petertheco...@yahoo.com Target Milestone: --- Application: akonadiserver (5.20.1 (22.04.1)) Qt Version: 5.15.5 Frameworks Version: 5.97.0 Operating System: Linux 5.19.8-200.fc36.x86_64 x86_64 Windowing System: Wayland Distribution: Fedora Linux 36 (KDE Plasma) DrKonqi: 5.25.5 [KCrashBackend] -- Information about the crash: it just crashed while loading cities:sky-lines. It has never happened before The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Segmentation fault [KCrash Handler] #4 0x55830c38b1eb in Akonadi::Server::AkonadiServer::connectionDisconnected() () #5 0x7f1d57aa42b4 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #6 0x7f1d57a7a1fb in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #7 0x7f1d57a7d584 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #8 0x7f1d57acb457 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #9 0x7f1d55ce3faf in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #10 0x7f1d55d392c8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #11 0x7f1d55ce1940 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #12 0x7f1d57acaf4a in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #13 0x7f1d57a78c6a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #14 0x7f1d57a80d32 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #15 0x55830c380f88 in main () [Inferior 1 (process 4223) detached] Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 458345] New: Marking a thread to be ignored has no effect
https://bugs.kde.org/show_bug.cgi?id=458345 Bug ID: 458345 Summary: Marking a thread to be ignored has no effect Product: kmail2 Version: 5.20.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: pe...@prh.myzen.co.uk Target Milestone: --- SUMMARY Marking a thread to be ignored has no effect: it simply marks its messages Read. The next email to come in in the same thread is displayed as usual. This has been true in the last few versions of KMail2. EXPECTED RESULT Ignore means ignore. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.24.6 and some earlier (available in About System) KDE Plasma Version: 5.24.6 and some earlier KDE Frameworks Version: 5.96.0 Qt Version: ADDITIONAL INFORMATION -- 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 #233 from Peter Humphrey --- New symptom. I have a local server that fetches POP3 mail from my ISP and serves it as IMAP4. I've had only rare duplicates since setting this arrangement up a few years ago. I discovered yesterday that creating a KMail POP3 account led immediately to numerous duplicates, as half-expected, but the key point here is that duplicates kept occurring, even after I'd deleted the POP3 account and rebooted. This is KMail version 5.20.3 (22.04.3) on Gentoo stable, Plasma version 5.24.6-r1. I tried postgres several years ago but it didn't improve anything, so I'm sticking with mariadb. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 455441] New: 'Record invitation in my calendar' appears to have no effect
https://bugs.kde.org/show_bug.cgi?id=455441 Bug ID: 455441 Summary: 'Record invitation in my calendar' appears to have no effect Product: kmail2 Version: 5.20.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: misc Assignee: kdepim-bugs@kde.org Reporter: p.wibber...@btinternet.com Target Milestone: --- SUMMARY *** 'Record invitation in my calendar' appears to have no effect. *** STEPS TO REPRODUCE 1. Receive meeting invitation (I suspect originating from Outlook) 2. Select 'Record invitation in my calendar' OBSERVED RESULT No event appears in Korganizer EXPECTED RESULT The event should appear in Korganizer SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon 5.25 (available in About System) KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 ADDITIONAL INFORMATION Sorry, it's not much to go on. Any advice on how to help diagnose the problem gratefully received. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 454257] Crash on save of attachment (tar.gz)
https://bugs.kde.org/show_bug.cgi?id=454257 --- Comment #1 from Hans-Peter Jansen --- Saving the same attachment after restart didn't crash! -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 454257] New: Crash on save of attachment (tar.gz)
https://bugs.kde.org/show_bug.cgi?id=454257
Bug ID: 454257
Summary: Crash on save of attachment (tar.gz)
Product: kmail2
Version: unspecified
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: kdepim-bugs@kde.org
Reporter: h...@urpla.net
Target Milestone: ---
Application: kmail (5.20.1 (22.04.1))
Qt Version: 5.15.2
Frameworks Version: 5.94.0
Operating System: Linux 5.17.9-2-preempt x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.24.5 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
Saving an tar.gz attachment. As far as I can see, the existing reports crash
pattern don't match.
What's probably important to note: this is kmail and friends from the first
full distribution rebuild with gcc12 in openSUSE TW 20220520.
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 0x7fcadeca756e in
QVector::begin(QTypedArrayData::const_iterator)
const (this=) at /usr/include/qt5/QtCore/qvector.h:220
#7 KMime::Content::headerByType(char const*) const
(this=this@entry=0x55e600c86030, type=0x7fcadecc0046
"Content-Transfer-Encoding") at
/usr/src/debug/kmime-22.04.1-1.1.x86_64/src/kmime_content.cpp:616
#8 0x7fcadeca822a in
KMime::Content::header(bool)
(create=true, this=0x55e600c86030) at
/usr/src/debug/kmime-22.04.1-1.1.x86_64/src/kmime_content.h:681
#9 KMime::Content::contentTransferEncoding(bool) (this=0x55e600c86030,
create=) at
/usr/src/debug/kmime-22.04.1-1.1.x86_64/src/kmime_content.cpp:873
#10 0x7fcadeca8805 in KMime::Content::decodedContent()
(this=this@entry=0x55e600c86030) at
/usr/src/debug/kmime-22.04.1-1.1.x86_64/src/kmime_content.cpp:316
#11 0x7fcadf70f2c5 in MessageViewer::Util::saveContent(QWidget*,
KMime::Content*, QUrl const&) (url=..., content=0x55e600c86030,
parent=0x55e5fe030e70) at
/usr/src/debug/messagelib-22.04.1-1.1.x86_64/messageviewer/src/utils/messageviewerutil.cpp:423
#12 MessageViewer::Util::saveContents(QWidget*, QVector
const&, QList&) (parent=0x55e5fe030e70, contents=,
urlList=...) at
/usr/src/debug/messagelib-22.04.1-1.1.x86_64/messageviewer/src/utils/messageviewerutil.cpp:326
#13 0x7fcadf6d7dfe in
MessageViewer::ViewerPrivate::openAttachment(KMime::Content*, QUrl const&)
(this=0x55e5fe0b5aa0, node=, url=) at
/usr/src/debug/messagelib-22.04.1-1.1.x86_64/messageviewer/src/viewer/viewer_p.cpp:324
#14 0x7fcadf6e6ac3 in MessageViewer::AttachmentURLHandler::handleClick(QUrl
const&, MessageViewer::ViewerPrivate*) const (this=,
url=, w=0x55e5fe0b5aa0) at
/usr/src/debug/messagelib-22.04.1-1.1.x86_64/messageviewer/src/viewer/urlhandlermanager.cpp:667
#15 0x7fcadf6df12d in MessageViewer::URLHandlerManager::handleClick(QUrl
const&, MessageViewer::ViewerPrivate*) const (w=0x55e5fe0b5aa0, url=...,
this=) at
/usr/src/debug/messagelib-22.04.1-1.1.x86_64/messageviewer/src/viewer/urlhandlermanager.cpp:283
#16 MessageViewer::ViewerPrivate::slotUrlOpen(QUrl const&)
(this=0x55e5fe0b5aa0, url=) at
/usr/src/debug/messagelib-22.04.1-1.1.x86_64/messageviewer/src/viewer/viewer_p.cpp:1907
#17 0x7fcae07e3660 in QObject::event(QEvent*) (this=0x55e5fe0b5aa0,
e=0x55e601fc24e0) at kernel/qobject.cpp:1314
#18 0x7fcae136437e in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x55e5fe0b5aa0, e=0x55e601fc24e0) at
kernel/qapplication.cpp:3632
#19 0x7fcae07b7988 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x55e5fe0b5aa0, event=0x55e601fc24e0) at
kernel/qcoreapplication.cpp:1064
#20 0x7fcae07ba921 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (receiver=0x0, event_type=0, data=0x55e5fd7c9fc0) at
kernel/qcoreapplication.cpp:1821
#21 0x7fcae080fec3 in postEventSourceDispatch(GSource*, GSourceFunc,
gpointer) (s=0x55e5fd902c70) at kernel/qeventdispatcher_glib.cpp:277
#22 0x7fcada375da0 in g_main_dispatch (context=0x7fcacc005010) at
../glib/gmain.c:3417
#23 g_main_context_dispatch (context=0x7fcacc005010) at ../glib/gmain.c:4135
#24 0x7fcada376158 in g_main_context_iterate
(context=context@entry=0x7fcacc005010, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4211
#25 0x7fcada3761ec in g_main_context_iteration (context=0x7fcacc005010,
may_block=1) at ../glib/gmain.c:4276
#26 0x7fcae080f5a6 in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x55e5fd910bb0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#27 0x7fcae07b63fb in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fffbee093b0, flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#28 0x7fcae07be566 in
[korganizer] [Bug 452480] Kmail doesn't display calendar invites
https://bugs.kde.org/show_bug.cgi?id=452480 --- Comment #10 from Peter --- Sorted with this evenings update to KDE Neon. Many thanks. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 452480] Kmail doesn't display calendar invites
https://bugs.kde.org/show_bug.cgi?id=452480 Peter changed: What|Removed |Added CC||p.wibber...@btinternet.com --- Comment #8 from Peter --- Just noticed this problem today (KDE Neon 5.24 User Edition with KMail Version 5.20.0 (22.04.0)). Excellent news that there's already a fix. Can you say when Kmail 5.20.1 will be released for KDE Neon User Edition? Many thanks and regards -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 448106] KOrganizer crashes on startup
https://bugs.kde.org/show_bug.cgi?id=448106 --- Comment #2 from Peter Huyoff --- Created attachment 145258 --> https://bugs.kde.org/attachment.cgi?id=145258=edit crash of today ;) This is todays log... -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 446457] New: Two finger scrolling not working in message body
https://bugs.kde.org/show_bug.cgi?id=446457 Bug ID: 446457 Summary: Two finger scrolling not working in message body Product: kontact Version: 5.18.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: mail Assignee: kdepim-bugs@kde.org Reporter: pn...@infoteq.com.au Target Milestone: --- SUMMARY On two KDE Neon systems set up the same way, two finger scrolling works everywhere in Kontact, except in the message body. STEPS TO REPRODUCE 1. Open an email 2. Try to scroll with a touch pad in the message body. 3. OBSERVED RESULT Nothing happens. EXPECTED RESULT The message body scrolls (and probably zooms I'd guess). SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 5.23 (available in About System) KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.3 Wayland login. ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 393421] No ability to hide the HTML Message Status Bar
https://bugs.kde.org/show_bug.cgi?id=393421 --- Comment #67 from Peter Humphrey --- (In reply to Niels from comment #66) > Surprised to find that we cannot disable the bar (anymore), but are still > allowed to obfuscate it by changing its colors. This makes little sense, > unless the goal is to have kmail's appearance be less attractive and > inconsistent. Maintainer knows best. Well, he thinks we shouldn't be allowed to assess our own risks. Arrogance personified. Just shrug and move on... -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 429344] All Mail Accounts (on KMail) crashed after latest updates
https://bugs.kde.org/show_bug.cgi?id=429344 Peter Huyoff changed: What|Removed |Added CC||peter.huy...@gmx.de -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 438037] EWS handling fails after successful login
https://bugs.kde.org/show_bug.cgi?id=438037 Hans-Peter Jansen changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #1 from Hans-Peter Jansen --- After another package refresh to 20210601 and a reboot, EWS is operating correctly. A minor nitpick: kmail loast all filters during transition from an imap based O365 access to EWS. Other than that, I'm a happy kmail camper again.. (and being this since about 20 years right now). Sorry for the churn. -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 438037] New: EWS handling fails after successful login
https://bugs.kde.org/show_bug.cgi?id=438037 Bug ID: 438037 Summary: EWS handling fails after successful login Product: kdepim Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: h...@urpla.net Target Milestone: --- Following https://userbase.kde.org/Kmail/Configuring_Kmail/Accounts/Office_365, I successfully created an EWS resource. I was able to subscribe to certain mailbox folder, hence it received to folder list successfully, but not any mails are fetched and akonadi shows: org.kde.pim.akonadiserver: Error while handling command FetchCollections on connection akonadi_ews_resource_2 (0x55b872a25050) Please register the custom scheme 'urn' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. org.kde.pim.ews.client: Starting OAuth2 authentication org.kde.pim.ews.client: Launching browser for authentication org.kde.pim.ews.client: PKeyAuth certificates not found js: Uncaught TypeError: n.saveSharedData is not a function js: Uncaught TypeError: n.saveSharedData is not a function js: Uncaught TypeError: n.saveSharedData is not a function js: Uncaught TypeError: n.saveSharedData is not a function org.kde.pim.ews.client: Authentication succeeded setMap: "access-token" setMap: "refresh-token" Please register the custom scheme 'urn' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. org.kde.pim.akonadiserver: Error while handling command FetchCollections on connection akonadi_ews_resource_2 (0x55b872a25050) Also, the authentication dialog is displayed on every akonadi/kmail start-up, it's not able to remember the login data (well, this is okta), and the web page requests akonadi permissions every time. Operating System: openSUSE Tumbleweed 20210524 KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.12.6-3-preempt OS Type: 64-bit Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: GeForce GTX 760/PCIe/SSE2 Kmail: 5.17.1 kdepim-runtime: 21.04.1 All TW "official" builds, no special repos in this respect. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 436877] New: Akregator process runaway on arm (PinePhone)
https://bugs.kde.org/show_bug.cgi?id=436877 Bug ID: 436877 Summary: Akregator process runaway on arm (PinePhone) Product: akregator Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: peterjon...@zohomail.com Target Milestone: --- SUMMARY Greetings, I installed Akregator on my PinePhone (Manjaro Plasma mobile) both through the normal Flatpack and then manually using pacman and had the same outcome. When starting Akregator it hangs with the CPU pegged. I also saw in top that mysql was running. I let it run for a few minutes to make sure it wasn't a setup action. The process had to be killed, then when restarted it says Akregator did not shut down properly, restore, don't restore, etc. The CPU was still pegged at 100%. I am willing to test since this is an unusual platform. Thanks, Peter Jones STEPS TO REPRODUCE 1. Install on PinePhone (arm) 2. Start program 3. OBSERVED RESULT CPU pegged, unresponsive EXPECTED RESULT Start normally SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 372850] KMail crashes on startup
https://bugs.kde.org/show_bug.cgi?id=372850 Peter Grobarcik changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #2 from Peter Grobarcik --- After new update: KMail Version 5.16.0 (20.12.0) KDE Frameworks 5.77.0 Qt 5.15.2 (kompiliert gegen 5.15.2) Das xcb Fenstersystem The bug does not appear anymore. -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 429480] kaddressbook fails to compile on QT 5.15.2 due to deprecated print routine
https://bugs.kde.org/show_bug.cgi?id=429480 Peter Humphrey changed: What|Removed |Added Summary|kaddressbook fails to |kaddressbook fails to |compile on QT 5.15.2 due to |compile on QT 5.15.2 due to |depreciated print routine |deprecated print routine CC||pe...@prh.myzen.co.uk -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 428466] New: Kmail Crash when using a Kontakt-group instead single e-mail-address
https://bugs.kde.org/show_bug.cgi?id=428466 Bug ID: 428466 Summary: Kmail Crash when using a Kontakt-group instead single e-mail-address Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: braun...@t-online.de Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1.edit by program Kontact a group-name with eight receivers ( different e-mail-addresses ) 2. type in program KMail group-name as receiver and save or send the edited mail 3. Open the e-mail OBSERVED RESULT Crash EXPECTED RESULT using alle Group-Members as receiver of the e-mail as in older program-version SOFTWARE/OS VERSIONS Linux/KDE (available in About System) KDE Plasma Version: 5.12.9 KDE Frameworks Version: 5.44.0 ADDITIONAL INFORMATION Qt-Version 5.9-5 Kernel Version 5.4.0-52 generic -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 426432] kmail 5.15.1: Crash when sending encrypted mail
https://bugs.kde.org/show_bug.cgi?id=426432 Hans-Peter Jansen changed: What|Removed |Added CC||h...@urpla.net --- Comment #6 from Hans-Peter Jansen --- If I understand you correctly, this is usual behavior for a gdb session. At the moment, gdb chimes in, all debugged processes are halted. Just type bt or bt -full and post the result. Also, you may want to just run gdb kmail. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 425510] New: gmail smtp sending is broken
https://bugs.kde.org/show_bug.cgi?id=425510 Bug ID: 425510 Summary: gmail smtp sending is broken Product: kmail2 Version: 5.15.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: commands and actions Assignee: kdepim-bugs@kde.org Reporter: zel...@gmail.com Target Milestone: --- SUMMARY Email stuck in outbox while using Gmail SMTP STEPS TO REPRODUCE 1. Set plain AUTH and generate google application password for kmail 2. set password for sending and try to send mail 3. email is stuck in outbox OBSERVED RESULT this worked once and never again. Terminal output shows: org.kde.pim.mailtransport: Tried to update password state of non-cloned transport. org.kde.pim.mailtransportakonadi: Item doesn't have DispatchModeAttribute. org.kde.pim.mailtransport: Tried to update password state of non-cloned transport. org.kde.kitinerary: Cannot find external extractor: "kitinerary-extractor" qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 38797, resource id: 140510560, major code: 130 (Unknown), minor code: 3 I've experienced this after setting the Enable Undo Send option. After disabling the option, the test email went out, but a second email that I sent without changed got stuck again. EXPECTED RESULT email should go out SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 425205] KMail crashes on first start after Tumbleweed dist-upgrade
https://bugs.kde.org/show_bug.cgi?id=425205 Peter Huyoff changed: What|Removed |Added CC||peter.huy...@gmx.de -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 425205] New: KMail crashes on first start after Tumbleweed dist-upgrade
https://bugs.kde.org/show_bug.cgi?id=425205 Bug ID: 425205 Summary: KMail crashes on first start after Tumbleweed dist-upgrade Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: peter.huy...@gmx.de Target Milestone: --- Application: akonadiserver (5.14.3 (20.04.3)) Qt Version: 5.15.0 Frameworks Version: 5.72.0 Operating System: Linux 5.7.11-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - Unusual behavior I noticed: After the latest dist-upgrade plasma-desktop doesn`t come up. (Maybe the proprietary nvidia drivers not compile and nouveau has problems with plasma) KMail runs up in fullscreen but akonadi crashes. After restarting it, KMail runs properly. The crash can be reproduced sometimes. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Segmentation fault [KCrash Handler] #4 0x7fd8834cb9de in std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x7fd83080) at /usr/include/c++/10/bits/atomic_base.h:420 #5 QAtomicOps::loadRelaxed (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239 #6 QBasicAtomicInteger::loadRelaxed (this=0x7fd83080) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:107 #7 QtPrivate::RefCount::deref (this=0x7fd83080) at ../../include/QtCore/../../src/corelib/tools/qrefcount.h:66 #8 QString::operator= (this=this@entry=0x7fd830465088, other=...) at text/qstring.cpp:2395 #9 0x55b6267d7864 in Akonadi::Server::ItemRetrievalManager::retrievalJobFinished (this=0x55b62785bd20, request=0x7fd830465070, errorMsg=...) at /usr/src/debug/akonadi-server-20.04.3-1.1.x86_64/src/server/storage/itemretrievalmanager.cpp:176 #10 0x7fd88365f0f6 in QtPrivate::QSlotObjectBase::call (a=0x7fd87d5778b0, r=0x55b62785bd20, this=0x7fd868008130) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #11 doActivate (sender=0x7fd87802e7c0, signal_index=3, argv=argv@entry=0x7fd87d5778b0) at kernel/qobject.cpp:3886 #12 0x7fd883658450 in QMetaObject::activate (sender=sender@entry=0x7fd87802e7c0, m=m@entry=0x55b626899000 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fd87d5778b0) at kernel/qobject.cpp:3946 #13 0x55b6267d9378 in Akonadi::Server::AbstractItemRetrievalJob::requestCompleted (_t2=..., _t1=, this=0x7fd87802e7c0) at /usr/src/debug/akonadi-server-20.04.3-1.1.x86_64/build/src/server/libakonadiserver_autogen/5XLNPBDXWK/moc_itemretrievaljob.cpp:136 #14 Akonadi::Server::ItemRetrievalJob::callFinished (this=0x7fd87802e7c0, watcher=) at /usr/src/debug/akonadi-server-20.04.3-1.1.x86_64/src/server/storage/itemretrievaljob.cpp:78 #15 0x7fd88365f0f6 in QtPrivate::QSlotObjectBase::call (a=0x7fd87d577a00, r=0x7fd87802e7c0, this=0x7fd8680084c0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #16 doActivate (sender=0x7fd868005380, signal_index=3, argv=argv@entry=0x7fd87d577a00) at kernel/qobject.cpp:3886 #17 0x7fd883658450 in QMetaObject::activate (sender=, m=m@entry=0x7fd8839de5e0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fd87d577a00) at kernel/qobject.cpp:3946 #18 0x7fd8839beabf in QDBusPendingCallWatcher::finished (this=, _t1=) at .moc/moc_qdbuspendingcall.cpp:158 #19 0x7fd883654b41 in QObject::event (this=0x7fd868005380, e=0x55b62785fda0) at kernel/qobject.cpp:1314 #20 0x7fd883628bef in doNotify (event=0x55b62785fda0, receiver=0x7fd868005380) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:116 #21 QCoreApplication::notify (event=, receiver=, this=) at kernel/qcoreapplication.cpp:1137 #22 QCoreApplication::notifyInternal2 (receiver=0x7fd868005380, event=0x55b62785fda0) at kernel/qcoreapplication.cpp:1061 #23 0x7fd88362b641 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x55b627825c20) at kernel/qcoreapplication.cpp:1815 #24 0x7fd8836809d3 in postEventSourceDispatch (s=0x7fd8680047b0) at kernel/qeventdispatcher_glib.cpp:277 #25 0x7fd8819bd2b7 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #26 0x7fd8819bd638 in ?? () from /usr/lib64/libglib-2.0.so.0 #27 0x7fd8819bd6ef in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #28 0x7fd88368005f in QEventDispatcherGlib::processEvents (this=0x7fd868000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #29 0x7fd8836275db in QEventLoop::exec (this=this@entry=0x7fd87d577da0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #30 0x7fd88344973e in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #31 0x7fd88344a871 in
[kmail2] [Bug 423904] New: KMail crashes while gmail-sync
https://bugs.kde.org/show_bug.cgi?id=423904 Bug ID: 423904 Summary: KMail crashes while gmail-sync Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: peter.huy...@gmx.de Target Milestone: --- Application: kmail (5.14.2 (20.04.2)) Qt Version: 5.15.0 Frameworks Version: 5.71.0 Operating System: Linux 5.7.5-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Before this crash, akonadi crashes multiple times. KMail runned then with empty Screen and aconadictl -fsck has corrected a lot of issuses. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #4 std::__atomic_base::load (__m=std::memory_order_relaxed, this=) at /usr/include/c++/10/bits/atomic_base.h:420 #5 QAtomicOps::loadRelaxed (_q_value=) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239 #6 QBasicAtomicInteger::loadRelaxed (this=) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:107 #7 QtPrivate::RefCount::isShared (this=) at ../../include/QtCore/../../src/corelib/tools/qrefcount.h:101 #8 QList::append (this=0x100, t=@0x7ffe166e43a0: 0x55a57f76ff70) at ../../include/QtCore/../../src/corelib/tools/qlist.h:622 #9 0x7ff70b3aeba0 in QWidget::insertAction (this=this@entry=0x55a57f76ff70, before=, before@entry=0x0, action=0x55a57f6352b0) at kernel/qwidget.cpp:3130 #10 0x7ff70a12c35b in KXMLGUI::ActionList::plug (index=, container=0x55a57f76ff70, this=0x55a57f6868a0) at /usr/src/debug/kxmlgui-5.71.0-1.1.x86_64/src/kxmlguifactory_p.cpp:45 #11 KXMLGUI::ContainerNode::plugActionList (mergingIdxIt=..., mergingIdxIt=..., state=..., this=0x55a57f7185b0) at /usr/src/debug/kxmlgui-5.71.0-1.1.x86_64/src/kxmlguifactory_p.cpp:234 #12 KXMLGUI::ContainerNode::plugActionList (this=0x55a57f7185b0, state=...) at /usr/src/debug/kxmlgui-5.71.0-1.1.x86_64/src/kxmlguifactory_p.cpp:204 #13 0x7ff70a12c3e1 in KXMLGUI::ContainerNode::plugActionList (this=0x55a57f640700, state=...) at /usr/src/debug/kxmlgui-5.71.0-1.1.x86_64/src/kxmlguifactory_p.cpp:208 #14 0x7ff70a12c3e1 in KXMLGUI::ContainerNode::plugActionList (this=0x55a57f686630, state=...) at /usr/src/debug/kxmlgui-5.71.0-1.1.x86_64/src/kxmlguifactory_p.cpp:208 #15 0x7ff70a133721 in KXMLGUIFactory::plugActionList (this=0x55a57f8d8c80, client=0x7ff6f0008110, name=..., actionList=...) at /usr/src/debug/kxmlgui-5.71.0-1.1.x86_64/src/kxmlguifactory.cpp:574 #16 0x7ff7091ecf50 in PimCommon::PluginInterface::initializePluginActions (this=0x7ffe166e46f0, prefix=..., guiClient=0x7ff6f0008110) at /usr/src/debug/pimcommon-20.04.2-1.1.x86_64/src/pimcommonakonadi/genericplugins/plugininterface.cpp:168 #17 0x7ff70bb65900 in KMMainWidget::initializePluginActions (this=0x55a5830f7b30) at /usr/src/debug/kmail-20.04.2-1.1.x86_64/src/kmmainwidget.cpp:4217 #18 0x7ff70bb6c574 in KMMainWidget::slotShowStartupFolder (this=0x55a5830f7b30) at /usr/src/debug/kmail-20.04.2-1.1.x86_64/src/kmmainwidget.cpp:4121 #19 0x7ff70a84da31 in QObject::event (this=0x55a5830f7b30, e=0x55a57f7d5220) at kernel/qobject.cpp:1314 #20 0x7ff70b3780cf in QApplicationPrivate::notify_helper (this=, receiver=0x55a5830f7b30, e=0x55a57f7d5220) at kernel/qapplication.cpp:3671 #21 0x7ff70a821b0a in QCoreApplication::notifyInternal2 (receiver=0x55a5830f7b30, event=0x55a57f7d5220) at ../../include/QtCore/5.15.0/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:325 #22 0x7ff70a824531 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x55a57ee1a510) at kernel/qcoreapplication.cpp:1815 #23 0x7ff70a8798c3 in postEventSourceDispatch (s=0x55a57ef37e70) at kernel/qeventdispatcher_glib.cpp:277 #24 0x7ff70755f2c7 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #25 0x7ff70755f648 in ?? () from /usr/lib64/libglib-2.0.so.0 #26 0x7ff70755f6ff in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #27 0x7ff70a878f4f in QEventDispatcherGlib::processEvents (this=0x55a57ef3f840, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #28 0x7ff70a8204cb in QEventLoop::exec (this=this@entry=0x7ffe166e4b90, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #29 0x7ff70a828730 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #30 0x55a57ec92386 in main (argc=, argv=) at /usr/include/qt5/QtCore/qcoreapplication.h:116 [Inferior 1 (process 12275) detached] Possible duplicates by query: bug 422092, bug 421432, bug 420495, bug 419785, bug 418784. Reported using DrKonqi -- You are receiving this mail because: You are the
[Akonadi] [Bug 422092] Akonadi Server crashing in ItemRetrievalManager while syncing GMail
https://bugs.kde.org/show_bug.cgi?id=422092 Peter Huyoff changed: What|Removed |Added CC||peter.huy...@gmx.de -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 422388] New: KMail crashes after restarting it
https://bugs.kde.org/show_bug.cgi?id=422388 Bug ID: 422388 Summary: KMail crashes after restarting it Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: peter.huy...@gmx.de Target Milestone: --- Application: kmail (5.14.1 (20.04.0)) Qt Version: 5.14.1 Frameworks Version: 5.70.0 Operating System: Linux 5.6.14-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Backtrace: A useful backtrace could not be generated Possible duplicates by query: bug 422374, bug 422200, bug 422199, bug 422185, bug 422151. Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 422199] Akonadi crashes while KMail fetches IMAP-Servers
https://bugs.kde.org/show_bug.cgi?id=422199 Peter Huyoff changed: What|Removed |Added CC||peter.huy...@gmx.de -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 422199] New: Akonadi crashes while KMail fetches IMAP-Servers
https://bugs.kde.org/show_bug.cgi?id=422199 Bug ID: 422199 Summary: Akonadi crashes while KMail fetches IMAP-Servers Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: peter.huy...@gmx.de Target Milestone: --- Application: akonadiserver (5.14.1 (20.04.0)) Qt Version: 5.14.1 Frameworks Version: 5.70.0 Operating System: Linux 5.6.12-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: System powered on, KMail starts and begins fetching IMAP-Servers. Then Akonadi crashes, but runs fine after restarting it. -- Backtrace (Reduced): #4 0x7fccf0f55b19 in qHash (key=..., seed=608053022) at ../../include/QtCore/../../src/corelib/text/qstring.h:266 #5 0x56376fa81a3b in QHash::findNode (this=this@entry=0x56376fbef338, akey=..., ahp=ahp@entry=0x0) at /usr/include/qt5/QtCore/qhash.h:950 #6 0x56376fa83f3e in QHash::remove (akey=..., this=0x56376fbef338) at /usr/include/qt5/QtCore/qrefcount.h:102 #7 Akonadi::Server::ItemRetrievalManager::retrievalJobFinished (this=0x56376fbef300, request=0x7fcca0481830, errorMsg=...) at /usr/src/debug/akonadi-server-20.04.1-1.1.x86_64/src/server/storage/itemretrievalmanager.cpp:179 #8 0x7fccf11259de in QtPrivate::QSlotObjectBase::call (a=0x7fcce6ffc810, r=0x56376fbef300, this=0x7fccdc00d890) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 The reporter indicates this bug may be a duplicate of or related to bug 421077. Possible duplicates by query: bug 422092, bug 421820, bug 421812, bug 421681, bug 421668. Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 422150] New: akonadi crashes on nearly every restart
https://bugs.kde.org/show_bug.cgi?id=422150 Bug ID: 422150 Summary: akonadi crashes on nearly every restart Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: peter.huy...@gmx.de Target Milestone: --- Application: akonadiserver (5.14.1 (20.04.0)) Qt Version: 5.14.1 Frameworks Version: 5.70.0 Operating System: Linux 5.6.12-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Backtrace: A useful backtrace could not be generated Possible duplicates by query: bug 422092, bug 422017, bug 421930, bug 421909, bug 421820. Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 421416] Search and merge identical contacts doubles entries
https://bugs.kde.org/show_bug.cgi?id=421416 --- Comment #1 from Hans-Peter Jansen --- Update: manually selecting and merging doubles (well, multiplies to be exact) the notes as well. -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 421416] New: Search and merge identical contacts doubles entries
https://bugs.kde.org/show_bug.cgi?id=421416 Bug ID: 421416 Summary: Search and merge identical contacts doubles entries Product: kaddressbook Version: 5.14.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: h...@urpla.net CC: to...@kde.org Target Milestone: --- Created attachment 128394 --> https://bugs.kde.org/attachment.cgi?id=128394=edit This entry was tripled, and contained one phone number and one note (entry outdated) SUMMARY When searching and then merging identical contacts from my google account, some address items (addresses, phone numbers, notes, ...) are not merged correctly. Note, that this is a result of akonadi doubling/tripling my google contacts internally. This might be related to the dysfunction in this area for some time. STEPS TO REPRODUCE 1. Have a couple of identical contacts in your google account 2. Select "Search doubled contacts" -> "All contacts" 3. Select item, watch result OBSERVED RESULT Some entries are doubled EXPECTED RESULT Identical items are eliminated SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE TW 20200507 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION It makes a difference, if I choose identical entries manually. Then it works as expected. -- 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 #222 from Peter Humphrey --- (In reply to ederag from comment #221) > grep -i error /home/ederag/.local/share/akonadi/db_data/mysql.err > Here, I see: $ grep -i error .local/share/akonadi/db_data/mysql.err 2020-05-08 13:12:10 0 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist 2020-05-08 13:12:10 9 [ERROR] InnoDB: Table `mysql`.`innodb_table_stats` not found. I don't know how long that's been happening, because I haven't had any duplicates for quite a long time. I remember, though, that when I was getting them, that error log had numerous errors of various types. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 421077] New: Akonadi crashes after almost any boot
https://bugs.kde.org/show_bug.cgi?id=421077 Bug ID: 421077 Summary: Akonadi crashes after almost any boot Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: peter.huy...@gmx.de Target Milestone: --- Application: akonadiserver (5.14.0 (20.04.0)) Qt Version: 5.14.1 Frameworks Version: 5.69.0 Operating System: Linux 5.6.8-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Since last OpenSuse Tumbleweed-Update Akonadi crashes after almost any boot. A handful restarts of akonadi later KMail runs normal. The crash can be reproduced every time. -- Backtrace (Reduced): #6 0x7ff2524c1544 in QSqlResult::~QSqlResult (this=, __in_chrg=) at ../../include/QtCore/../../src/corelib/tools/qhash.h:601 #7 0x7ff24d2344eb in QMYSQLResult::~QMYSQLResult (this=0x7ff204003a60, __in_chrg=) at qsql_mysql.cpp:457 #8 QMYSQLResult::~QMYSQLResult (this=0x7ff204003a60, __in_chrg=) at qsql_mysql.cpp:458 #9 0x7ff2524b1562 in QSqlQueryPrivate::~QSqlQueryPrivate (this=0x7ff204048920, __in_chrg=) at kernel/qsqlquery.cpp:94 #10 0x7ff2524b1901 in QSqlQuery::~QSqlQuery (this=, __in_chrg=) at kernel/qsqlquery.cpp:248 Possible duplicates by query: bug 376822. Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 394784] KMAIl 5.8.1: Reply to HTML-mail in text mode includes content from last mail
https://bugs.kde.org/show_bug.cgi?id=394784 Peter Humphrey changed: What|Removed |Added CC||pe...@prh.myzen.co.uk --- Comment #9 from Peter Humphrey --- (In reply to Laurent Montel from comment #7) > (In reply to Rigo Wenning from comment #6) > > confirmed from here. Marking text and only having that text in the reply was > > handy and does not work anymore. kontact 13.2 in opensuse tumbleweed > > 20200229 > > normal there is a bug in qtwebengine < 5.14.2 when we don't clear selection > so we can reply with previous selection text. So I disabled it. I don't understand. What did you disable? Is the previous behaviour restored? -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 --- Comment #109 from Hans-Peter Jansen --- May I kindly ask you to read https://bugs.kde.org/show_bug.cgi?id=404990#c91 Thanks -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 386985] akonadi CalDav resource not synching with certain servers
https://bugs.kde.org/show_bug.cgi?id=386985 Peter changed: What|Removed |Added CC||peter.lad...@mailbox.org --- Comment #44 from Peter --- YEP, confirmed! very fine after a long time! -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 --- Comment #91 from Hans-Peter Jansen --- Dear audience, Regarding this issue, simple workarounds exist, follow https://bugs.kde.org/show_bug.cgi?id=410700 please. In general, it would be nice to not spread FUD about Akonadi/Kmail. As a long time heavy user (once started with KDE 2), I can confirm, that Akonadi/Kmail is one of the most powerful MUAs available today. If you have high demands, you need to tweak the defaults a bit (e.g. by using PostgreSQL) and provide enough resources. But be assured, that the only MUA that comes close, Thunderbird, start to suck rocks, if you throw enough mails on it. My biggest mailbox is about 140 GB(!), and I have a dozen accounts to manage.. Kmail starts in less than 60 seconds, with a full scan on it! Try this with Thunderbird. Sure, issues exist. An currently, the google integration sucks in several ways. But basically, it is good enough to be used on a daily base. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 410700] kmail no longer allows addition of gmail account
https://bugs.kde.org/show_bug.cgi?id=410700 --- Comment #7 from Hans-Peter Jansen --- Hi, it is working fine, for me now. If IMAP access isn't working for you, but you did the other changes already, it's most probably, that access needs to be granted for less secure apps: https://myaccount.google.com/lesssecureapps -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 384184] SubToDo is displayed as blank line
https://bugs.kde.org/show_bug.cgi?id=384184 Peter Kreussel changed: What|Removed |Added CC||pri...@peter-kreussel.de --- Comment #2 from Peter Kreussel --- Same problem for me with DAV-Groupware-Ressource on Kontact/Akonadi 19.08.3 using DAV-Groupware-Ressources. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 410700] kmail no longer allows addition of gmail account
https://bugs.kde.org/show_bug.cgi?id=410700 --- Comment #6 from Hans-Peter Jansen --- Well, not here. IMAP option is enabled in my gmail account. Keep User name: full gmail address Modify IMAP-Server: imap.gmail.com -> imap.googlemail.com Keep Encryption: SSL/TLS, Port 993 Modify Authorization method: Gmail -> PLAIN Result: A02 NO Invalid credentials ( Failure ) [ AUTHENTICATIONFAILED ] I can only abort the akonadi login to google. username and password are correct! I rechecked with Firefox wallet, compared Firefox password with akonadi password of this very account, etc... Retested by removing the akonadi google account, and adding it from scratch. Access of kwallet is granted. openSUSE Tumbleweed 20191112 -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 410700] kmail no longer allows addition of gmail account
https://bugs.kde.org/show_bug.cgi?id=410700 Hans-Peter Jansen changed: What|Removed |Added CC||h...@urpla.net -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 --- Comment #74 from Hans-Peter Jansen --- Well, it seems, that the relationship to google is lacking in general. Here's an assortment of my own findings: https://bugs.kde.org/show_bug.cgi?id=414010, https://bugs.kde.org/show_bug.cgi?id=410936 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 Hans-Peter Jansen changed: What|Removed |Added CC||h...@urpla.net -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 397512] Sent emails appear as "unread" in the "Sent" folder
https://bugs.kde.org/show_bug.cgi?id=397512 Hans-Peter Jansen changed: What|Removed |Added CC||h...@urpla.net Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #4 from Hans-Peter Jansen --- With kmail 5.12.2, *some* sent mails end up unread in the sent folder, akonadi postgres backend, with cyrus imap server (openSUSE 15.0). There's no clear pattern visible, but just opening the mail doesn't help. Those mails need to be flagged "read" manually, and the state icon is different. See attachment. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20191030 KDE Plasma Version: 5.17.1 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 397512] Sent emails appear as "unread" in the "Sent" folder
https://bugs.kde.org/show_bug.cgi?id=397512 --- Comment #5 from Hans-Peter Jansen --- Created attachment 123674 --> https://bugs.kde.org/attachment.cgi?id=123674=edit middle icon show such an "unread" mail, after manually flagging "read" -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 298349] kmail2 composer (still) fails to display non-ascii characters in quoted text on reply with some mails (only with nested multipart mime parts?)
https://bugs.kde.org/show_bug.cgi?id=298349 Hans-Peter Jansen changed: What|Removed |Added CC||h...@urpla.net --- Comment #16 from Hans-Peter Jansen --- Still confirmed for 5.12.2 (as of openSUSE Tumbleweed 20191014). Unchecking "Keep original charset..." fixed it, but since this option is enabled by default, it would probably be a good idea to change the default until this issue is finally fixed. -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 385510] Cannot add address book folder to Personal contacts resource
https://bugs.kde.org/show_bug.cgi?id=385510 Hans-Peter Eck changed: What|Removed |Added CC||h...@eck-dv.de --- Comment #6 from Hans-Peter Eck --- For me it is the same problem still remaining. In the end, my workaround is switching to Mozilla Thunderbird and purging kontact completely from my systems. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 317656] Postponed reminders are sometimes lost when KOrganizer/Kontact/korgac are shut down
https://bugs.kde.org/show_bug.cgi?id=317656 Peter Gückel changed: What|Removed |Added CC|pguec...@gmail.com | -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 411204] New: With two email accounts, SPF sees emails as being from the 'Set as Default' account, leading to authentication/DMARC problems when sending from other account
https://bugs.kde.org/show_bug.cgi?id=411204 Bug ID: 411204 Summary: With two email accounts, SPF sees emails as being from the 'Set as Default' account, leading to authentication/DMARC problems when sending from other account Product: kmail2 Version: 5.12.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: p.wibber...@btinternet.com Target Milestone: --- SUMMARY If there are two email accounts, Sending Policy Framework seems to think emails are sent always from the 'Set as Default' account, leading to authentication/DMARC problems when sending from other account. STEPS TO REPRODUCE 1.Under Accounts.Sending, set up two SMTP Sending Accounts with different ISPs 2.One of the accounts will be 'Set as Default' 3.Send a message to a Gmail account with each Account. 4. Under Account.Sending swap 'Set as Default' to the other account. OBSERVED RESULT The email from the Sending Account which is 'Set as Default' will be delivered; the email from the other account will fail on DMARC policies. When the 'Set as Default' is swapped to the other account, the account from which the email is successfully delivered and the account from which the email is rejected will swap over. EXPECTED RESULT Emails from both accounts should be sent and not rejected. SOFTWARE/OS VERSIONS KDE Plasma Version: Linux/KDE neon Plasma LTS Edition 5.12, Release 18.04 Kernel: 4.15.0-58-generic 64-bit KDE Frameworks Version: 5.61.0 Qt Version: 5.12.3 Kmail 5.12.0 ( Version 4:19.08.0-0xneon+18.04+bionic+build33 from ubuntu-bionic-universe (KDE neon Plasma LTS) ) ADDITIONAL INFORMATION A record in a "mail not deliverered message" was: "Received-SPF: softfail (transitioning domain of sa-prd-fep-014.btinternet.com does not designate 74.208.4.204 as permitted sender)". Here, 74.208.4.204 is an IP address belonging to 1&1, which was the service provider for the email account which was 'Set as Default'. I am not sure whether this is a duplicate of Bug 393185, which is marked as "Resolved Not a Bug". If so, it is not clear why this is not a bug, as it makes the account other than the default account almost unusable for sending emails. Thanks and regards -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 410936] New: Google account address book synchronisation issues
https://bugs.kde.org/show_bug.cgi?id=410936 Bug ID: 410936 Summary: Google account address book synchronisation issues Product: kaddressbook Version: 5.11.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: h...@urpla.net CC: to...@kde.org Target Milestone: --- SUMMARY * KAddressBook doesn't show (sync) new entries, most (old) contact entries are available, although an attempt to re-login to the google account seems to be successful. * Some contact groups show up multiple times (one contains items, the other is empty). * Having selected the address book and all sub-folders (address groups), combining contacts attempts to combine all contacts, that appear in more than one group. Combining does work, if no sub-folders (address groups) are selected, and the selected contacts are limited to exactly this google account with sub-folders disabled. STEPS TO REPRODUCE Add Google account Create a new contact Sync address book Query new contact check google address sub-folders (address groups) select google address book and all sub-folders (address groups) and combine similar contacts. OBSERVED RESULT no new contact found some address groups appear twice combining contacts show too many entries EXPECTED RESULT new contact show up after sync every contact group should appear only once combining contacts should ignore group membership SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE TW 20190810 KDE Plasma Version: 5.16.4 KDE Frameworks Version: 5.60.0 Qt Version: 5.13.0 -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 317656] Postponed reminders are sometimes lost when KOrganizer/Kontact/korgac are shut down
https://bugs.kde.org/show_bug.cgi?id=317656 --- Comment #15 from Peter Gückel --- (In reply to Filipus Klutiero from comment #14) > Thanks but I am afraid that problem is different. The issue tracked in this > ticket is about postponed reminders (reminders can only be postponed after > they initially trigger). > > A 15 minutes duration is sufficient for events to display in the monthly > view. But you can create a longer event if you want to be sure. If this is only about postponed reminders, then why is my "different" bug #332448, as you indicate, listed as a duplicate of this one? -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 317656] Postponed reminders are sometimes lost when KOrganizer/Kontact/korgac are shut down
https://bugs.kde.org/show_bug.cgi?id=317656 --- Comment #13 from Peter Gückel --- OK, I made a mistake with the first test. I set the reminder, but I forgot to set a trigger time. I just ran another test. I verified the calendar.ics file and it was shown and so was a triger time. I even manually clicked Update Calendar on the lower left panel of korganizer, because I just never know how often akonadi and calendar.ics get synced (but it appears to be immediate). Anyway, I did not log out, I just unplugged the laptop and closed the lid. I waited until 5 minutes after the trigger time and no reminder appeared. The reminder seems to be lost. What is curious, is that I created the appointment to begin at 11:15 and end at 11:30, but it did not show in the main (right) panel in korganizer, even though it was in calendar.ics (I verified with kwrite). Is this because the appointment was only 15 minutes in duration, too skinny for display? I verified and I definitely had left the 'blocks from other appointments' box (don't recall exact name) in the default activated setting. I will run some more tests tomorrow (enough for today), but I think this problem persists! -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 317656] Postponed reminders are sometimes lost when KOrganizer/Kontact/korgac are shut down
https://bugs.kde.org/show_bug.cgi?id=317656 --- Comment #12 from Peter Gückel --- It seems that the package number and application number are not the same: I have Korganizer 5.11.2. Anyway, I did in fact just create an amnesia test and I suspended the computer before and resumed after the trigger time and the reminder DID NOT occur upon system resumption. I believe this is an error, as important reminders will simply be lost. [I use Korganizer daily for important reminders, such as renewal times for my passports, registration renewals for my motorcycles and truck, firearms license renewals, recurring sports classes, monthly condo fee and credit card payments, etc.—basically anything that recurs on a longterm and recurring basis. I am on my laptop a lot and these reminders are VERY IMPORTANT to me. I use android's calendar on my phone primarily for one-time reminders, like doctor's appointments, dentist, bankers, etc.—things I need to plan my day and prevent future appointment conflicts.] -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 317656] Postponed reminders are sometimes lost when KOrganizer/Kontact/korgac are shut down
https://bugs.kde.org/show_bug.cgi?id=317656 Peter Gückel changed: What|Removed |Added CC||pguec...@gmail.com --- Comment #11 from Peter Gückel --- By the way, I am now using Fedora 30 with korganizer-19.04.2-1.fc30.x86_64. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 332448] korganizer reminder has amnesia
https://bugs.kde.org/show_bug.cgi?id=332448 --- Comment #7 from Peter Gückel --- I cannot say, at this time. I still use korganizer for reminders on my laptop, but mainly for birthdays reminders and monthly bill payment reminders. I have moved the rest of my reminders to my android phone. I have been trying to watch, but I have not detected anything, but I have not paid accute attention. In the past, the amnesia would occur not just when I turned the computer off, but also when I suspended it. Upon reboot or resume, reminders that should have been triggered during the down time were simply lost. Again, I cannot confirm resolution nor continued issues. I will try to be more attentive, by suspending the computer when I know a reminder is due, to see if it is lost or appears upon resuming, but this could take me quite a long time to report back :-) Then, again, since it took you 5½ years to get back to my bug, I suppose long time is relative. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 409224] kmail with >=mariadb-10.4.6: not able to refresh email list: Unable to append status flags
https://bugs.kde.org/show_bug.cgi?id=409224 Peter Humphrey changed: What|Removed |Added CC||pe...@prh.myzen.co.uk -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 407955] New: Enable time-of-day of automatic archiving to be specified
https://bugs.kde.org/show_bug.cgi?id=407955 Bug ID: 407955 Summary: Enable time-of-day of automatic archiving to be specified Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: commands and actions Assignee: kdepim-bugs@kde.org Reporter: pe...@prh.myzen.co.uk Target Milestone: --- SUMMARY When I enable automatic archiving of emails, I cannot specify the time of day when the archiving should be done, nor can I see when it will be. Please add user selection of this time. SOFTWARE/OS VERSIONS Gentoo testing system gcc 8.3.0, sys-kernel/gentoo-sources 5.1.4 QT 5.12.3, KDE frameworks 5.58.0, KDE plasma 5.15.5 KDE apps 19.04.1 incl KMail 19.04.1 (5.10.2), akonadi 19.04.0 x11-drivers/xf86-video-amdgpu 19.0.0 dev-libs/amdgpu-pro-opencl 18.20.684755 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 387061] Large messages don't display in the viewer pane (eg. New Tumbleweed snapshot 20171117 released!)
https://bugs.kde.org/show_bug.cgi?id=387061 Hans-Peter Jansen changed: What|Removed |Added CC||h...@urpla.net -- 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 #219 from Peter Humphrey --- > Please consider that it is very hard for maintainers > to fix a bug that is not reproducible on their setup. True, but there's nothing to stop them from enlisting help from knowledgeable users (at least a few have offered, including me). They won't do it though; I can only speculate as to why not. -- 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 #205 from Peter Humphrey --- (In reply to Eric Depagne from comment #203) > (In reply to Tristan Miller from comment #202) > > Is this problem still reproducible in the latest version of KMail? There > > haven't been any comments on this bug in over a year; I'm wondering if > > that's because the problem has been fixed or because it has driven most of > > the user base away. I'd love to return to using KMail but can't as long as > > this message duplication problem persists. (I was getting dozens of > > duplicated messages every day, which was too much to put up with.) > > It has been fixed I believe, since it disappeared from my kmail in 2015. It certainly hasn't. I still get numerous duplicates daily on this Gentoo box. I think the comments dried up because (a) there was nothing new to add; (b) users grew tired of banging on to no avail. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 406552] Kontact crashed while clicking on specific email (scam)
https://bugs.kde.org/show_bug.cgi?id=406552 Peter Kuchar changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Peter Kuchar --- problem doesn't appear anymore in a new version -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 406552] New: Kontact crashed while clicking on specific email (scam)
https://bugs.kde.org/show_bug.cgi?id=406552 Bug ID: 406552 Summary: Kontact crashed while clicking on specific email (scam) Product: kontact Version: 5.10.3 Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: mail Assignee: kdepim-bugs@kde.org Reporter: ma...@gmx.com Target Milestone: --- SUMMARY I've observed that kontact only crashes when I click on a mail that triggers (scam warning). In Kmail directly I can see an email with the warning (this email may be a scam), but in Kontact the thing kills whole application STEPS TO REPRODUCE 1. click on the email which may be reported as scam 2. kontact crashes OBSERVED RESULT kontact crashes EXPECTED RESULT email may be shown properly SOFTWARE/OS VERSIONS Application: kontact (5.10.3) Qt Version: 5.12.2 Frameworks Version: 5.56.0 Operating System: Linux 5.0.5-1-MANJARO x86_64 Distribution: "Manjaro Linux" ADDITIONAL INFORMATION [New Thread 0x7ffeda77c700 (LWP 6452)] [New Thread 0x7ffed9f7b700 (LWP 6453)] [New Thread 0x7ffed977a700 (LWP 6454)] [Detaching after fork from child process 6457] [Detaching after fork from child process 6459] [Detaching after fork from child process 6461] [Detaching after fork from child process 6463] [Detaching after fork from child process 6465] [6362:6386:0414/203349.279981:ERROR:nss_util.cc(674)] Error initializing NSS with a persistent database (sql:/home/cqs/.pki/nssdb): NSS error code: -8023 [6362:6386:0414/203349.280063:ERROR:nss_util.cc(154)] Error initializing NSS without a persistent database: NSS error code: -8023 [6362:6386:0414/203349.280069:FATAL:nss_util.cc(156)] nss_error=-8023, os_error=0 Thread 21 "TaskSchedulerFo" received signal SIGABRT, Aborted. [Switching to Thread 0x7fff8affd700 (LWP 6386)] 0x7677dd7f in raise () from /usr/lib/libc.so.6 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 406261] New: Kmail2 crashes when accepting meeting invitation
https://bugs.kde.org/show_bug.cgi?id=406261 Bug ID: 406261 Summary: Kmail2 crashes when accepting meeting invitation Product: kmail2 Version: 5.10.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: p.wibber...@btinternet.com Target Milestone: --- Application: kmail (5.10.3) Qt Version: 5.12.0 Frameworks Version: 5.56.0 Operating System: Linux 4.15.0-47-generic x86_64 Distribution: KDE neon LTS User Edition 5.12 -- Information about the crash: Kmail2 crashed at the moment that I clicked the Accept button in a meeting invitation. 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 0x7f1aa4013bc0 (LWP 10078))] Thread 30 (Thread 0x7f1939a4b700 (LWP 13399)): #0 0x7f1a7b81e57d in pa_pstream_unref () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #1 0x7f1a7b81eab9 in () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #2 0x7f1a7b81f33f in () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #3 0x7f1a833da108 in pa_mainloop_dispatch () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f1a833da4de in pa_mainloop_iterate () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f1a833da560 in pa_mainloop_run () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f1a833e83c9 in () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #7 0x7f1a7b82f318 in () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #8 0x7f1a968106db in start_thread (arg=0x7f1939a4b700) at pthread_create.c:463 #9 0x7f1aa106588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 29 (Thread 0x7f193affd700 (LWP 13380)): #0 0x7f1aa10540b4 in __GI___libc_read (fd=111, buf=0x7f193affc7d0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f1a94988cd0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f1a94944027 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f1a949444e0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f1a9494464c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f1aa199b15b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f1aa193c64a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f1aa176441a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f1aa1765bc2 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f1a968106db in start_thread (arg=0x7f193affd700) at pthread_create.c:463 #10 0x7f1aa106588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 28 (Thread 0x7f193b7fe700 (LWP 13379)): #0 0x7f1a96816ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f193b7fd710, expected=0, futex_word=0x7f193b7fd8f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f1a96816ed9 in __pthread_cond_wait_common (abstime=0x7f193b7fd7b0, mutex=0x7f193b7fd8a8, cond=0x7f193b7fd8d0) at pthread_cond_wait.c:533 #2 0x7f1a96816ed9 in __pthread_cond_timedwait (cond=0x7f193b7fd8d0, mutex=0x7f193b7fd8a8, abstime=0x7f193b7fd7b0) at pthread_cond_wait.c:667 #3 0x7f1a8b775177 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f1a8b775ada in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f1a8b775bc2 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f1a8b733851 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f1a8b736387 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f1a8b736974 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f1a8b777cd1 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f1a968106db in start_thread (arg=0x7f193b7fe700) at pthread_create.c:463 #11 0x7f1aa106588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 27 (Thread 0x7f193bfff700 (LWP 13378)): #0 0x7f1a96816ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f193bffe710, expected=0, futex_word=0x7f193bffe8f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f1a96816ed9 in __pthread_cond_wait_common (abstime=0x7f193bffe7b0, mutex=0x7f193bffe8a8, cond=0x7f193bffe8d0) at pthread_cond_wait.c:533 #2 0x7f1a96816ed9 in __pthread_cond_timedwait (cond=0x7f193bffe8d0, mutex=0x7f193bffe8a8, abstime=0x7f193bffe7b0) at pthread_cond_wait.c:667 #3 0x7f1a8b775177 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f1a8b775ada in () at
