[Akonadi] [Bug 441214] SMTP passwords aren't being saved
https://bugs.kde.org/show_bug.cgi?id=441214 --- Comment #3 from Caleb Cushing --- Created attachment 140886 --> https://bugs.kde.org/attachment.cgi?id=140886=edit journalctl just for user -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 441214] SMTP passwords aren't being saved
https://bugs.kde.org/show_bug.cgi?id=441214 --- Comment #2 from Caleb Cushing --- Ok, more weirdness I wiped out the imap and the mailtransports in kwallet manager after closing kontact first. I came back, and imap is still getting fetched without those; and saving the password still doesn't take even though one was added to mailtransports. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 441214] SMTP passwords aren't being saved
https://bugs.kde.org/show_bug.cgi?id=441214 Caleb Cushing changed: What|Removed |Added Summary|App Armor blocking password |SMTP passwords aren't being |save|saved -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 441214] App Armor blocking password save
https://bugs.kde.org/show_bug.cgi?id=441214 --- Comment #1 from Caleb Cushing --- I no longer think this is app armor, at least not the source of my problem. I disabled app armor, rebooted my system and the problem stil exists where it isn't persisting the smtp password. I've tried editing the sending settings, and adding it there with the save box checked. I come back there's no ***, when it asks me on send I make sure the save box is checked. still nothing, still asks me the next time. I could do with a workaround. I'd save the password myself if I knew what it was going to look at. I have looked via kwallet manager and under mailtransports -> passwords it is saved in there, and it's the same password as under imap -> akonadi... and when I paste it into the prompt on send it works. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 441214] New: App Armor blocking password save
https://bugs.kde.org/show_bug.cgi?id=441214 Bug ID: 441214 Summary: App Armor blocking password save Product: Akonadi Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: xenoterrac...@gmail.com Target Milestone: --- SUMMARY I'm getting a log, and my smtp password for google isn't saving, it's super weird. STEPS TO REPRODUCE I'm not 100% on this, I feel like there might be another thing I'm missing 1. enable app armor 2. use gmail settings for kmail 3. send email OBSERVED RESULT kmail always asks for the smtp password, for some reason this is only happening for smtp, and only gmail, so weird. I'm seeing this log AVC apparmor="DENIED" operation="open" profile="/usr/bin/akonadiserver" name="/etc/authselect/nsswitch.conf" pid=31873 comm="0x557056b51380-" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 EXPECTED RESULT password should be getting saved, no error SOFTWARE/OS VERSIONS apparmor: 3.0.1 Akonadi: 21.0.8 Operating System: Manjaro Linux KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.10.59-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-10610U CPU @ 1.80GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics ADDITIONAL INFORMATION here's the additional surrounding logs, they might be relevant, not sure The reason I think it might be a KDE bug, is because it looks like the last "arch" bug like this got resolved in KDE. https://bugs.archlinux.org/task/64890 Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) org.kde.pim.messagecomposer: Impossible to specify TO! It's a bug snapperd.service: Deactivated successfully. SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=snapperd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' static bool LibSecretKeyring::findPassword(const QString&, const QString&, QKeychain::JobPrivate*) static bool LibSecretKeyring::findPassword(const QString&, const QString&, QKeychain::JobPrivate*) We have an error during reading password "Entry not found" static bool LibSecretKeyring::findPassword(const QString&, const QString&, QKeychain::JobPrivate*) We have an error during reading password "Entry not found" static bool LibSecretKeyring::findPassword(const QString&, const QString&, QKeychain::JobPrivate*) We have an error during reading password "Entry not found" We have an error during reading password "Entry not found" static bool LibSecretKeyring::findPassword(const QString&, const QString&, QKeychain::JobPrivate*) We have an error during reading password "Entry not found" static bool LibSecretKeyring::findPassword(const QString&, const QString&, QKeychain::JobPrivate*) We have an error during reading password "Entry not found" void SendJob::setFrom(const QString ) "caleb.cush...@people-meeter.com" d->m_returnPath "" AVC apparmor="DENIED" operation="open" profile="/usr/bin/akonadiserver" name="/etc/authselect/nsswitch.conf" pid=31873 comm="0x557056b51380-" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 org.kde.pim.akonadiserver.search: Executing search "akonadi_newmailnotifier_agent-SearchSession" org.kde.pim.akonadiserver.search: Search "akonadi_newmailnotifier_agent-SearchSession" done (without remote search) app-gnome-org.kde.kwalletmanager5-72003.scope: Consumed 2.949s CPU time. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 441195] Gmail with MFA shouldn't require an app specific password
https://bugs.kde.org/show_bug.cgi?id=441195 --- Comment #2 from Caleb Cushing --- Ok, to make korganizer work with google, there's a "google groupware" this works basically how I think that logging into gmail shold work. I'm fairly confident that it could just request the additional permissions, and that it should be a shared component for all PIM, instead of seemingly just available for korganizer, although it *also* grabs your contacts for kaddressbook. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 441209] signed by a PGP key that doesn't match uid is still "green"
https://bugs.kde.org/show_bug.cgi?id=441209 --- Comment #1 from Caleb Cushing --- To me, this should be *red* the problem here is that if your key is compromised but not your email, someone could still send messages as you and people who've already imported your key might not even notice the mismatch. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 441209] New: signed by a PGP key that doesn't match uid is still "green"
https://bugs.kde.org/show_bug.cgi?id=441209 Bug ID: 441209 Summary: signed by a PGP key that doesn't match uid is still "green" Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: crypto Assignee: kdepim-b...@kde.org Reporter: xenoterrac...@gmail.com Target Milestone: --- Created attachment 140865 --> https://bugs.kde.org/attachment.cgi?id=140865=edit screenshot of the green path with sender/receiver SUMMARY using a trusted key to sign with a UID that it doesn't have shouldn't be green. note: evolution warns about this. STEPS TO REPRODUCE 1. create 2 sets of full gpg keys 2. use another client to sign sending one of your emails with the other emails key. I did this with a misconfiguration via fairemail. OBSERVED RESULT kmail shows green and all happy EXPECTED RESULT kmail should show yellow or red because that key isn't approved for that uid. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Kmail: 5.18.0 Operating System: Manjaro Linux KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.10.59-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-10610U CPU @ 1.80GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 441195] Gmail with MFA shouldn't require an app specific password
https://bugs.kde.org/show_bug.cgi?id=441195 --- Comment #1 from Caleb Cushing --- Oh, I've seen at least one other bug that I'm not finding now about this, but it was marked fixed, so I decided to open a new one. I'm not sure if it's a regression though. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 441195] New: Gmail with MFA shouldn't require an app specific password
https://bugs.kde.org/show_bug.cgi?id=441195 Bug ID: 441195 Summary: Gmail with MFA shouldn't require an app specific password Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: misc Assignee: kdepim-b...@kde.org Reporter: xenoterrac...@gmail.com Target Milestone: --- Created attachment 140853 --> https://bugs.kde.org/attachment.cgi?id=140853=edit video showing popup message SUMMARY Attempt to add Gmail STEPS TO REPRODUCE 1. Settings 2. Add Account 3. Next 4. Next OBSERVED RESULT some unreadable message flashes see video EXPECTED RESULT To prompt a web view that allows you to enable authentication via an oidc grant. Also, that message needs to stay visible. SOFTWARE/OS VERSIONS Kmail: 5.18.0 Operating System: Manjaro Linux KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.10.59-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-10610U CPU @ 1.80GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics ADDITIONAL INFORMATION Not actually using KDE, just running kmail in gnome 40 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 441193] support auto configuration by SRV records only
https://bugs.kde.org/show_bug.cgi?id=441193 --- Comment #1 from Caleb Cushing --- oh, side note, I'm not actually running KDE, I'm using Gnome 40, but using kmail in hopes that I like it better. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 441193] New: support auto configuration by SRV records only
https://bugs.kde.org/show_bug.cgi?id=441193 Bug ID: 441193 Summary: support auto configuration by SRV records only Product: kmail2 Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: misc Assignee: kdepim-b...@kde.org Reporter: xenoterrac...@gmail.com Target Milestone: --- SUMMARY I'd like to be able to have kmail autoconfigure email based on dns. I found this answer on ServerFault regarding appropriate settings. https://serverfault.com/a/172373/6852 there is also an _autodiscover endpoint, but that requires a web server to be set up. In case it is supposed to work, you can see my DNS here. STEPS TO REPRODUCE 1. Settings 2. Add Account 3. Enter my.em...@mydomain.com (in my case this is caleb.cush...@people-meeter.com) 4. Next 5. Next 6. Generic Imap Server (I suspect this shouldn't even show) 7. Next OBSERVED RESULT incoming and outgoing server is just the root domain, e.g. people-meeter.com EXPECTED RESULT imappro.zoho.com and smtppro.zoho.com SOFTWARE/OS VERSIONS Kmail: 5.18.0, but it's not in your list. Operating System: Manjaro Linux KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.10.59-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-10610U CPU @ 1.80GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics ADDITIONAL INFORMATION ❯ dig _imaps._tcp.people-meeter.com SRV +noall +answer _imaps._tcp.people-meeter.com. 1799 IN SRV 10 10 993 imappro.zoho.com. ❯ dig _submission._tcp.people-meeter.com SRV +noall +answer _submission._tcp.people-meeter.com. 1799 IN SRV 10 10 587 smtppro.zoho.com. -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 228902] First character in digital clock cut off in panel
https://bugs.kde.org/show_bug.cgi?id=228902 --- Comment #28 from Caleb Cushing --- and this is why I've abandoned KDE On Fri, Jun 8, 2018 at 1:28 PM Nate Graham wrote: > > https://bugs.kde.org/show_bug.cgi?id=228902 > > Nate Graham changed: > >What|Removed |Added > > Resolution|--- |UNMAINTAINED > Status|CONFIRMED |RESOLVED > > --- Comment #27 from Nate Graham --- > Hello! > > This bug report was filed for KDE Plasma 4, which reached end-of-support > status > in August 2015. KDE Plasma 5's desktop shell has been almost completely > rewritten for better performance and usability, so it is likely that this bug > has already been resolved in Plasma 5. > > Accordingly, we hope you understand why we must close this bug report. If the > issue described here is still present in KDE Plasma 5.12 or later, please > feel > free to open a new ticket in the "plasmashell" product after reading > https://community.kde.org/Get_Involved/Bug_Reporting > > If you would like to get involved in KDE's bug triaging effort so that future > mass bug closes like this are less likely, please read > https://community.kde.org/Get_Involved#Bug_Triaging > > Thanks for your understanding! > > Nate Graham > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
