[Akonadi] [Bug 415271] akonadi does not create the file_lost+found folder
https://bugs.kde.org/show_bug.cgi?id=415271 Wolfgang Bauer changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Version Fixed In||5.10.1 CC||wba...@tmo.at Latest Commit||https://cgit.kde.org/akonad ||i.git/commit/?id=28f2916db1 ||a2ad98b00250eb4d5dd92ca1548 ||c50 Version|GIT (master)|unspecified --- Comment #1 from Wolfgang Bauer --- (In reply to Stefanos Harhalakis from comment #0) > I'm using akonadi server 4:18.08.3-7 (debian testing). That's not "GIT (master)" though, but rather 5.9.3 (which is over a year old and no longer available in bugzilla's version field). The problem however was fixed already in 18.12.1 (5.10.1): https://cgit.kde.org/akonadi.git/commit/?id=28f2916db1a2ad98b00250eb4d5dd92ca1548c50 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 415254] [regression] HTML viewer complains about "external references to images etc." when there are no images
https://bugs.kde.org/show_bug.cgi?id=415254
--- Comment #3 from Thiago Macieira ---
(In reply to Laurent Montel from comment #2)
> Git commit 56f1d42f68ed2f597fc599e4952ee81e579cd355 by Laurent Montel.
> Committed on 17/12/2019 at 06:05.
> Pushed by mlaurent into branch 'release/19.12'.
>
> Fix Bug 415254 - [regression] HTML viewer complains about "external
> references to images etc." when there are no images
>
> FIXED-IN: 5.13.1
>
> M +2-2
> messageviewer/src/messagepartthemes/default/defaultrenderer.cpp
>
> https://commits.kde.org/messagelib/56f1d42f68ed2f597fc599e4952ee81e579cd355
+if (str.contains(QRegularExpression(QLatin1String("https://...;>, with the quotes? The code above this section
deals with href=", but not src=.
This will also trigger as a false positive in the following HTML:
Some text goes here blah blah src=http://example.com
--
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 #95 from Nicholas Sushkin --- Google is disabling password access altogether I got the following email yesterday: From: The G Suite Team Beginning June 15, 2020, non-Google apps that use only a password to access Google accounts will no longer be supported. Starting February 15, 2021, G Suite accounts will only allow access to apps using OAuth. Password-based access will no longer be supported. Dear Administrator, We're constantly working to improve the security of your organization's Google accounts. As part of this effort, and in consideration of the current threat landscape, we'll be turning off access to less secure apps (LSA) — non-Google apps that can access your Google account with only a username and password, without requiring any additional verification steps. Access through only a username and password makes your account more vulnerable to hijacking attempts. Moving forward, only apps that support a more modern and secure access method called OAuth will be able to access your G Suite account. Access to LSAs will be turned off in two stages: June 15, 2020 - Users who try to connect to an LSA for the first time will no longer be able to do so. This includes third-party apps that allow password-only access to Google calendars, contacts, and email via protocols such as CalDAV, CardDAV and IMAP. Users who have connected to LSAs prior to this date will be able to continue using them until usage of all LSAs is turned off. February 15, 2021 - Access to LSAs will be turned off for all G Suite accounts. What do I need to do? To continue using a specific app with your G Suite accounts, users in your organization must switch to a more secure type of access called OAuth. This connection method allows apps to access accounts with a digital key instead of requiring a user to reveal their username and password. We recommend that you share the user instructions (included below) with individuals in your organization to help them make the necessary changes. Alternatively, if your organization is using custom tools, you can ask the developer of the tool to update it to use OAuth. Developer instructions are also included below. MDM configuration If your organization uses a mobile device management (MDM) provider to configure CalDAV, CardDAV, and Exchange ActiveSync (Google Sync) profiles, these services will be phased out according to the timeline below: June 15, 2020 - MDM push of IMAP, CalDAV, CardDAV, and Exchange ActiveSync (Google Sync) will no longer work for new users. February 15, 2021 - MDM push of IMAP, CalDAV, CardDAV, and Exchange ActiveSync (Google Sync) will no longer work for existing users. Admins will need to push a Google Account using their MDM provider, which will re-add their Google accounts to iOS devices using OAuth. Other less secure apps For any other LSA, ask the developer of the app you are using to start supporting OAuth. If you use other apps on iOS or MacOS that access your G Suite account information through only a password, most access issues can be resolved by removing then re-adding your account. When you add it back, make sure to select Google as the account type to automatically use OAuth. Scanners and other devices No change is required for scanners or other devices using simple mail transfer protocol (SMTP) or LSAs to send emails. If you replace your device, look for one that sends email using OAuth. User instructions If you are using an app that accesses your Google account with only a username and password, take one of the following actions to switch to a more secure method and continue to access your email, calendar, or contacts. If you do not take one of the following actions, when LSA access is discontinued after February 15, 2021, you will begin receiving an error message that your username-password combination is incorrect. Email If you are using stand-alone Outlook 2016 or earlier, move to Office 365 (a web-based version of Outlook) or Outlook 2019, both of which support OAuth access. Alternatively you can use G Suite Sync for Microsoft Outlook. If you are using Thunderbird or another email client, re-add your Google Account and configure it to use IMAP with OAuth. If you are using the mail app on iOS or MacOS, or Outlook for Mac, and use only a password to login, you'll need to remove and re-add your account. When you add it back, select “sign in with Google” to automatically use OAuth. Mac OS iOS mail app view Mac OS mail app view iOS Calendar If you use CalDAV to give an app or device access to your calendar, switch to a method that supports OAuth. We recommend the Google Calendar app [Web/iOS/Android] as the most secure app to use with your G Suite account. If your G Suite account is linked to the calendar app in iOS or MacOS and uses only a password to
[kmail2] [Bug 415254] [regression] HTML viewer complains about "external references to images etc." when there are no images
https://bugs.kde.org/show_bug.cgi?id=415254 Laurent Montel changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||5.13.1 Latest Commit||https://commits.kde.org/mes ||sagelib/56f1d42f68ed2f597fc ||599e4952ee81e579cd355 Status|ASSIGNED|RESOLVED --- Comment #2 from Laurent Montel --- Git commit 56f1d42f68ed2f597fc599e4952ee81e579cd355 by Laurent Montel. Committed on 17/12/2019 at 06:05. Pushed by mlaurent into branch 'release/19.12'. Fix Bug 415254 - [regression] HTML viewer complains about "external references to images etc." when there are no images FIXED-IN: 5.13.1 M +2-2messageviewer/src/messagepartthemes/default/defaultrenderer.cpp https://commits.kde.org/messagelib/56f1d42f68ed2f597fc599e4952ee81e579cd355 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 415254] [regression] HTML viewer complains about "external references to images etc." when there are no images
https://bugs.kde.org/show_bug.cgi?id=415254 Laurent Montel changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED CC||mon...@kde.org --- Comment #1 from Laurent Montel --- I confirm it. I will work on it soon. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 414782] Change the priority order of the text color
https://bugs.kde.org/show_bug.cgi?id=414782 --- Comment #2 from Alexandre Bonneau --- It's true that ideally, you should be able to quickly know how messages are marked. However, just using bold/italic is not enough in my opinion to distinguish marks between them, specially if you quickly browse your emails using the mouse wheel to see if there are any outstanding TODOs. Color in that case is more visible. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 415271] New: akonadi does not create the file_lost+found folder
https://bugs.kde.org/show_bug.cgi?id=415271 Bug ID: 415271 Summary: akonadi does not create the file_lost+found folder Product: Akonadi Version: GIT (master) Platform: Debian testing OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: v...@v13.gr Target Milestone: --- It seems that akonadi does not create the file_lost+found directory which results in "akonadictl fsck" failing to move files there. See here: https://github.com/KDE/akonadi/blob/ed93384ff692a684a1ade9bbc283ba495c0b3fe3/src/server/storagejanitor.cpp#L460-L466 There isn't anything that creates the directory. In my case, I was running fsck continuously without any effect. The result was like this: Found unreferenced external file: /home/v13/.local/share/akonadi/file_db_data/56/5634856_r0 Found unreferenced external file: /home/v13/.local/share/akonadi/file_db_data/27/7826627_r0 Found unreferenced external file: /home/v13/.local/share/akonadi/file_db_data/08/5711008_r1 And then: Moved 105853 unreferenced files to lost+found. But nothing was being moved. Then, once I created it by hand, it moved 3.8GB I tried restarting akonadi in case it creates the directory, but nothing I'm using akonadi server 4:18.08.3-7 (debian testing). -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 361764] Cannot add event to calendar with correct time: Add event window will not accept an "A.M." time
https://bugs.kde.org/show_bug.cgi?id=361764 betlogbet...@gmail.com changed: What|Removed |Added CC||betlogbet...@gmail.com --- Comment #27 from betlogbet...@gmail.com --- TL:DR; if you want ISO datetimestamps in regional settings use en_AU as default, and (custom) specify en_SE in Time field. This also makes korganizer work properly (becausue there is no AM or PM). However there is obviously still an issue with en_AU being set globally, as it forces AM to be set as PM. Some time ago I was typing to force systemwide ISO datetime formatting, and did some tinkering with custom locale files. So the AM->PM issue may be related in my case. However as far as i know and can see I removed all said tinkering. Global en_AU is broken when entering AM into korganizer However the below locale settings works just fine. user@betlognuc:~$ locale locale: Cannot set LC_ALL to default locale: No such file or directory LANG=en_AU.UTF-8 LANGUAGE=en_AU:en LC_CTYPE="en_AU.UTF-8" LC_NUMERIC="en_AU.UTF-8" LC_TIME=en_SE.UTF-8 LC_COLLATE="en_AU.UTF-8" LC_MONETARY="en_AU.UTF-8" LC_MESSAGES="en_AU.UTF-8" LC_PAPER="en_AU.UTF-8" LC_NAME="en_AU.UTF-8" LC_ADDRESS="en_AU.UTF-8" LC_TELEPHONE="en_AU.UTF-8" LC_MEASUREMENT="en_AU.UTF-8" LC_IDENTIFICATION="en_AU.UTF-8" LC_ALL= I wrote this before noticing the match at bottom of list... and see that other Australians have same issue I had, so I will paste in case the details are relevant somehow: SUMMARY Cannot set event time to AM Application forces all new events to PM Particularly annoying because my system is set to ISO 24 hour. STEPS TO REPRODUCE 1. create event 2. type 10:00, 1000, or 10:00 AM or 3. mouse select and scroll to 10:00 AM OBSERVED RESULT 10:00 PM is selected EXPECTED RESULT 10:00 AM should be selected SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 18.04 KDE Plasma Version: 5.12.9 KDE Frameworks Version: 5.44.0 Qt Version: 5.9.5 ADDITIONAL INFORMATION kernel version 4.15.0-72-generic 64-bit Due to another issue (inability to remove a personal calendar.ics) I have recently uninstalled, purged and apt reinstalled korganizer -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 414843] Crashes on autocompletion of email address
https://bugs.kde.org/show_bug.cgi?id=414843 Aaron Williams changed: What|Removed |Added CC||aar...@doofus.org -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 415258] New: Kontact crashes shortly after startup
https://bugs.kde.org/show_bug.cgi?id=415258 Bug ID: 415258 Summary: Kontact crashes shortly after startup Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: gree...@kde.org Target Milestone: --- Application: kontact (5.13.0 (19.12.0)) Qt Version: 5.13.1 Frameworks Version: 5.64.0 Operating System: Linux 5.3.12-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: While reading/navigating through emails, kontact crashes within 20 to 30 seconds after launch of the application Currently running: kontact-19.12.0-110.1.x86_64 kontact-debugsource-19.12.0-110.1.x86_64 kontactinterface-lang-19.12.0-144.1.noarch kontact-debuginfo-19.12.0-110.1.x86_64 kontact-lang-19.12.0-110.1.noarch This is on openSUSE Tumbleweed with the KDE:Applications and KDE:Extra repos enabled The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5129db4a40 (LWP 7740))] Thread 42 (Thread 0x7f4fbadb3700 (LWP 7879)): #0 0x7f513b51fbdf in poll () from /lib64/libc.so.6 #1 0x7f513840a27e in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f513840a39f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f513a18e98b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7f513a1370cb in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f5139f6f021 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7f5139f701a2 in ?? () from /usr/lib64/libQt5Core.so.5 #7 0x7f5138e64f2a in start_thread () from /lib64/libpthread.so.0 #8 0x7f513b52a4af in clone () from /lib64/libc.so.6 Thread 41 (Thread 0x7f4fd617c700 (LWP 7856)): #0 0x7f5138e6b9ca in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f5132d9d516 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f5132d9dee3 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f5132d9e061 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f5132d56191 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f5132d5937b in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f5132d59724 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f5132da0355 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7f5138e64f2a in start_thread () from /lib64/libpthread.so.0 #9 0x7f513b52a4af in clone () from /lib64/libc.so.6 Thread 40 (Thread 0x7f4fd6c7d700 (LWP 7855)): #0 0x7f5138e6b6a5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f5125f28b8b in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f5125f28a37 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f5138e64f2a in start_thread () from /lib64/libpthread.so.0 #4 0x7f513b52a4af in clone () from /lib64/libc.so.6 Thread 39 (Thread 0x7f4fd77fe700 (LWP 7854)): #0 0x7f5138e6b6a5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f5132d9d41c in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f5132d9def0 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f5132d9e01f in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f5132d56166 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f5132d5937b in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f5132d59764 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f5132da0355 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7f5138e64f2a in start_thread () from /lib64/libpthread.so.0 #9 0x7f513b52a4af in clone () from /lib64/libc.so.6 Thread 38 (Thread 0x7f4fd7fff700 (LWP 7851)): #0 0x7f513b4b0ca7 in __lll_lock_wait_private () from /lib64/libc.so.6 #1 0x7f513b498b0e in buffered_vfprintf () from /lib64/libc.so.6 #2 0x7f513b495a24 in __vfprintf_internal () from /lib64/libc.so.6 #3 0x7f513b53889f in __fprintf_chk () from /lib64/libc.so.6 #4 0x7f512e749f2e in event_logv_ () from /usr/lib64/libevent-2.1.so.7 #5 0x7f512e74cb15 in event_warn () from /usr/lib64/libevent-2.1.so.7 #6 0x7f512e74e678 in ?? () from /usr/lib64/libevent-2.1.so.7 #7 0x7f512e75f086 in event_base_loop () from /usr/lib64/libevent-2.1.so.7 #8 0x7f5132da41b8 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #9 0x7f5132d302d7 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #10 0x7f5132d6749f in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #11 0x7f5132da0355 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #12 0x7f5138e64f2a in start_thread ()
[kaddressbook] [Bug 415222] Kaddressbook no tags in exported vcard
https://bugs.kde.org/show_bug.cgi?id=415222 --- Comment #2 from zvezdin --- Thank you for the update. So it seems that this thread is essentially a duplicate from the 2014 one you linked. In any case I am quite unfamiliar with any of the technologies used in kaddressbook otherwise I could attempt migrating the patch. Given how old this is already, what could possibly be done at this stage to fix this? I'm pretty sure I'm not the only one looking to use kaddressbook as a frontend/editor of a cross-device syncronization of contacts and it's a pity that such a small issue can disrupt this potential. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 415254] New: [regression] HTML viewer complains about "external references to images etc." when there are no images
https://bugs.kde.org/show_bug.cgi?id=415254 Bug ID: 415254 Summary: [regression] HTML viewer complains about "external references to images etc." when there are no images Product: kmail2 Version: 5.12.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: message list Assignee: kdepim-bugs@kde.org Reporter: thi...@kde.org Target Milestone: --- SUMMARY When viewing ANY HTML email, KMail displays Note: This HTML message may contain external references to images etc. For security/privacy reasons external references are not loaded. If you trust the sender of this message then you can load the external references for this message by clicking here. Up until last week (19.08), this message only showed if there were image links to non-attached images. This also correlates with a change in style: up until last week, it displayed in a white background inside a red outline, now (19.12) it's got a reddish background. STEPS TO REPRODUCE 1. Send yourself an HTML email with no images 2. Open it in KMail OBSERVED RESULT The message appears at the top. EXPECTED RESULT No message appears. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.17.4 KDE Frameworks: 5.64.0 Qt: 5.13.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 415253] New: Moving GMail IMAP Inbox messages from Unified Inbox removes them from Unified Inbox, but not from corresponding GMail Inbox.
https://bugs.kde.org/show_bug.cgi?id=415253 Bug ID: 415253 Summary: Moving GMail IMAP Inbox messages from Unified Inbox removes them from Unified Inbox, but not from corresponding GMail Inbox. Product: kmail2 Version: 5.11.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: fred_we...@charter.net Target Milestone: --- SUMMARY Moving GMail IMAP Inbox messages from Unified Inbox removes them from Unified Inbox, but not from corresponding GMail Inbox. STEPS TO REPRODUCE 1. Create Unified folder containing multiple IMAP Inboxes, including GMail. 2. Retrieve new messages from multiple IMAP accounts. 3. Move new messages from Unified Inbox to any local folder/s. OBSERVED RESULT - Messages are removed from Unified Inbox folder. - Messages exist in target folder/s. - GMail messages remain in IMAP Inboxes. EXPECTED RESULT GMail essages should be removed from IMAP Inbox as well. 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 410167] Cannot change or enter time for calendar entry
https://bugs.kde.org/show_bug.cgi?id=410167 --- Comment #12 from B Rhodes --- That's the fix. The Canadian locale is broken and the error messages useless. -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 415222] Kaddressbook no tags in exported vcard
https://bugs.kde.org/show_bug.cgi?id=415222 Jonathan Marten changed: What|Removed |Added CC||j...@keelhaul.me.uk Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Jonathan Marten --- Categories export is explicitly disabled for VCard: https://cgit.kde.org/kcontacts.git/tree/src/vcardtool.cpp#n257 Possibly because the export would only output the internal Akonadi category IDs, which are not useful for any other non-Akonadi application or import. I had developed a fix for PIM 4 to output the category names instead, but it got overtaken by the PIM 5 release and still needs to be ported. See also bug 332358. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 415245] New: Create Maildir ressource on valid maildir could result in not showing mails
https://bugs.kde.org/show_bug.cgi?id=415245 Bug ID: 415245 Summary: Create Maildir ressource on valid maildir could result in not showing mails Product: Akonadi Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Maildir Resource Assignee: kdepim-bugs@kde.org Reporter: criss...@gmx.de Target Milestone: --- I have the problem found, when I adding a new maildir ressource for a maildir located in my home directory (e.g. ~/MailStore/Account2), the ressource will added but no mails are shown in ressource. STEPS TO REPRODUCE 1. Copy maildir to home dir somewhere (e.g. ~/MailStore/Account2) 2. create new maildir ressource for the maildir copied (e.g. ~/MailStore/Account2) OBSERVED RESULT The ressource is added but its shown empty (no mail or folder). A interesting thing is, that sometimes it works when I let create it on desired location (e.g. ~/.local/share/akonadi_maildir_resource_2). When that works fine, remove the created directory and replace the folder by a symbolic link to the desired maildir it found the mails and folders. Also, I can't rename the resource name (I guess it takes the name from folder but that seem to work only on creation. EXPECTED RESULT The ressource is added and it shows contents (mails and folders). SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.3.0-24-lowlatency #26~18.04.2-Ubuntu SMP PREEMPT Tue Nov 26 14:39:35 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux KDE Plasma Version: 5.12.9.1-0ubuntu0.1build1~ubuntu18.04~ppa1 KDE Frameworks Version: 5.47.0-0ubuntu1~ubuntu18.04~ppa1 Qt Version: 5.9.5 ADDITIONAL INFORMATION Starting akonadi using "akonadictl start" shows: org.kde.pim.akonadicontrol: "AgentManager::agentInstanceSynchronizeCollection" Agent instance "akonadi_maildir_resource_2" has no resource interface! org.kde.pim.akonadiserver: "Cannot connect to agent instance with identifier 'akonadi_maildir_resource_2', error message: '' -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 415160] Compilation failure, MessageViewer::Viewer has no member named 'dkimWidgetInfo'
https://bugs.kde.org/show_bug.cgi?id=415160 --- Comment #6 from Bart Ribbers --- Ha, yup, that was it, it solved it. Interesting, I didn't even realize qca-qt5 was a dependency. It isn't listed in CMakeLists.txt and it's not printed when running CMake. I guess it's not as optional anymore ;) -- You are receiving this mail because: You are the assignee for the bug.
