[kmail2] [Bug 415160] New: Compilation failure, MessageViewer::Viewer has no member named 'dkimWidgetInfo'
https://bugs.kde.org/show_bug.cgi?id=415160 Bug ID: 415160 Summary: Compilation failure, MessageViewer::Viewer has no member named 'dkimWidgetInfo' Product: kmail2 Version: 5.13.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: bribb...@disroot.org Target Milestone: --- SUMMARY The latest KMail release (service release 19.12.0) fails to compile on Alpine Linux (a musl based system) STEPS TO REPRODUCE 1. Compile KMail like normal on a Musl system OBSERVED RESULT /home/builder/aports/testing/kmail/src/kmail-19.12.0/src/kmreadermainwin.cpp:114:59: error: 'class MessageViewer::Viewer' has no member named 'dkimWidgetInfo' 114 | statusBar()->addPermanentWidget(mReaderWin->viewer()->dkimWidgetInfo()); EXPECTED RESULT Compilation to succeed SOFTWARE/OS VERSIONS Linux/KDE Plasma: Alpine Linux edge, kernel 5.4.3 (available in About System) KDE Plasma Version: 5.17.3 KDE Frameworks Version: 5.64.0 Qt Version: 5.12.5 ADDITIONAL INFORMATION This system is based on Musl which I'd normally blame, but it doesn't seem to be the case here. I am however not sure where MessageViewer comes from. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 415145] AkonadiCalendar can't handle specific RECURRENCE-ID;TZID value
https://bugs.kde.org/show_bug.cgi?id=415145 Christophe Giboudeaux changed: What|Removed |Added CC||win...@kde.org -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 415145] AkonadiCalendar can't handle specific RECURRENCE-ID;TZID value
https://bugs.kde.org/show_bug.cgi?id=415145 Miikka changed: What|Removed |Added CC||miikka.veijo...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 415145] New: AkonadiCalendar can't handle specific RECURRENCE-ID;TZID value
https://bugs.kde.org/show_bug.cgi?id=415145 Bug ID: 415145 Summary: AkonadiCalendar can't handle specific RECURRENCE-ID;TZID value Product: Akonadi Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: miikka.veijo...@gmail.com Target Milestone: --- SUMMARY Akonadi does not handle vCal events correctly when there's a specific RECURRENCE-ID;TZID set. I'm using Korganizer & Akonadi with Office365 (EWS) and in vCal events pulled from there there is RECURRENCE-ID;TZID set and if it's set to "Europe/Budapest:20191210T10" Korganizer and konsolecalendar are not able to show these events at all (konsolecalendar crashes and Korganizer says: org.kde.pim.akonadicalendar: Can't find any incidence with ui XXX even the event with that ID exists: I'm even able examine the event using akonadiconsole). When I manually remove that RECURRENCE-ID;TZID line from vcal event everything works normally. And if I set it to RECURRENCE-ID;TZID=Europe/Budapest:20191210 everything works normally. Only if the line continues with that ...T10 (Europe/Budapest:20191210T10) this bug appears. STEPS TO REPRODUCE 1. Create a vCalendar file where is RECURRENCE-ID;TZID with value: Europe/Budapest:20191210T10 2. Korganizer does not show these events at all and konsolecalendar crashes when trying to show this specific event by using --uid argument EXPECTED RESULT Events should show up in Korganizer and in konsolecalendar normally. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Operating System: openSUSE Leap 15.1 KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.1 Kernel Version: 4.12.14-lp151.28.36-default OS Type: 64-bit Processors: 4 × AMD Opteron™ Processor 6272 Memory: 5.8 GiB of RAM ADDITIONAL INFORMATION Akonadi version: 19.12.0-lp151.108.1.x86_64 I copied the konsolecalendar crash information here: https://pastebin.com/Mriy6z9s -- 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.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 Andrea Scarpino changed: What|Removed |Added CC|scarp...@kde.org| -- 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 Eike Hein changed: What|Removed |Added CC||h...@kde.org --- Comment #90 from Eike Hein --- With my board hat on: We'll look into what we can do to push this forward. Daniel, could you send us info on the ticket you raised with Google so we may take it up for you if you're too busy? Note we'll push for getting this process and the access credentials documented with the sysadmin team, to avoid things getting stuck in the future. If you need to escalate to us it usually already went wrong ideal-process-wise :-) -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 415123] New: Kmail ignores font settings for new emails
https://bugs.kde.org/show_bug.cgi?id=415123 Bug ID: 415123 Summary: Kmail ignores font settings for new emails Product: kmail2 Version: 5.11.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: bugs.kde.att...@online.de Target Milestone: --- SUMMARY Kmail sets the font for new emails always to "DejaVu Sans" and ignores my own font settings. STEPS TO REPRODUCE 1. Launch Kmail 2. Open the "configure" dialog 3. Click on "Appearance" 4. Change the font to a font of your choice 5. Close the "configure" dialog 6. Click on "new email" OBSERVED RESULT The font for new emails is set to "DejaVu Sans" EXPECTED RESULT Kmail should use the font for new emails from the "configure" dialog. SOFTWARE/OS VERSIONS Operating System: Fedora 31 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.64.0 Qt Version: 5.12.5 Kernel Version: 5.3.15-300.fc31.x86_64 OS Type: 64-bit ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
