Summary: | "POP3 Account" stays as the name for each email I set up; have to check setting each time to tell which it is! | ||
---|---|---|---|
Product: | [Applications] kmail2 | Reporter: | Ruth <ruthesroses> |
Component: | config dialog | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | ricardo |
Priority: | NOR | ||
Version: | 5.14.2 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | kmail account settings |
Description
Ruth
2020-10-15 07:16:35 UTC
Confirmed, KMail 5.17.1 (21.04.1) SOFTWARE/OS VERSIONS Operating System: Slackware 15.0beta KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.10.39 OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i5-1035G1 CPU @ 1.00GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics Created attachment 138795 [details]
kmail account settings
Forgot to add a screenshot showing the problem, sorry it's ins spanish but still understendable :)
Hmm, after searching the code for "POP3 Account" I found this 2 lines: https://invent.kde.org/pim/kdepim-runtime/-/blob/master/resources/pop3/accountwidget.cpp#L132 https://invent.kde.org/pim/kdepim-runtime/-/blob/master/resources/pop3/pop3resource.cpp#L43 Which made me think that naming/renaming the accounts should work. And it did! Maybe it's a bug only during creation of the accounts? Just in case, this is what I did: - Opened kmail, went to settings - accounts: All of the names were "POP3 Account" - Edited one by one changing their names, it still showed "POP3 Account" in the list but editing them again showed the right name inside - Closed kmail - Stopped akonadi and started it again - Started kmail, went to settings - accounts: All of the names were those i set! (In reply to Ruth from comment #0) Hi Ruth! I think this was fixed, at least my last attempt to create a new account didn't have this problem anymore. Can you confirm so we can close this bug report? Well, I believe this one can be safely closed so I'm doing it. Feel free to reopen it if needed. |