| 1 |
Hi Mick, |
| 2 |
|
| 3 |
Mick wrote: |
| 4 |
|
| 5 |
> On Thursday 08 Jun 2017 02:04:44 Jörg Schaible wrote: |
| 6 |
>> Mick wrote: |
| 7 |
>> > On Tuesday 06 Jun 2017 16:35:40 you wrote: |
| 8 |
>> >> Hi All, |
| 9 |
>> >> |
| 10 |
>> >> I've updated a number of kde (plasma) packages, including kde- |
| 11 |
>> >> frameworks/kwallet-5.34.0-r1. A depclean action wanted to remove |
| 12 |
>> >> kde-apps/kwalletd-16.04.3-r1 and I let it do its tha'ng. |
| 13 |
>> >> |
| 14 |
>> >> Following a new login I discovered that *every* time I wanted to send |
| 15 |
>> >> a |
| 16 |
>> >> message I was being asked for the SMTP password. For some users with |
| 17 |
>> >> 6 or |
| 18 |
>> >> more email accounts this soon became tiresome. The pop up advises |
| 19 |
>> >> that the password should be saved in kwallet and offers the choice to |
| 20 |
>> >> save it in ... |
| 21 |
>> >> the configuration file! It also advises that although it will be |
| 22 |
>> >> obfuscated |
| 23 |
>> >> it will not be safe in the configuration file. There are two buttons, |
| 24 |
>> >> one to save the password in the configuration file and another to not |
| 25 |
>> >> save it (at all). |
| 26 |
>> >> |
| 27 |
>> >> So to retain what sanity I may have left, I had to re-install kde- |
| 28 |
>> >> apps/kwalletd-16.04.3-r1, which appears to be able to manage SMTP |
| 29 |
>> >> passwords without asking each time the user. |
| 30 |
>> >> |
| 31 |
>> >> Have you noticed the same? Is there a fix or workaround for this? |
| 32 |
>> > |
| 33 |
>> > Just to clarify, there doesn't seem to be a problem with IMAP4 |
| 34 |
>> > passwords, only with SMTP. |
| 35 |
>> > |
| 36 |
>> > When updating to kde-frameworks/kwallet-5.34.0-r1 I noticed this elog |
| 37 |
>> > message, which implies I should no longer need the old kwalletd4: |
| 38 |
>> > |
| 39 |
>> > "LOG: postinst |
| 40 |
>> > Starting with 5.34.0-r1, kwallet is able to serve applications |
| 41 |
>> > that still require old kwalletd4. After migration has finished, |
| 42 |
>> > kde-apps/kwalletd can be removed." |
| 43 |
>> > |
| 44 |
>> > So, do I have to wait for Kmail:4 to be updated to Kmail:5 before I |
| 45 |
>> > give up on kwalletd4 despite the above message? |
| 46 |
>> |
| 47 |
>> I had the same problem. But event if kwalletd is installed, it was no |
| 48 |
>> longer started. |
| 49 |
> |
| 50 |
> Yes, this seems to be the problem. Starting Kmail does not launch |
| 51 |
> kwalletd5 and as a consequence kmail starts asking for each email account |
| 52 |
> password separately. |
| 53 |
> |
| 54 |
> I guess until kmail:5 is installed I will have to start kwalletd5 by hand. |
| 55 |
|
| 56 |
My situation is different, since I use kwallet-pam. That one will start |
| 57 |
kwallet5 automatically and I am not asked by KMail for passwords (after it |
| 58 |
now also uses kwallet5). |
| 59 |
|
| 60 |
>> Note, you should install knotify:4 if you want notifications about failed |
| 61 |
>> mail delivery from KMail. That was removed for me in an dependency |
| 62 |
>> clean-up, because I had no entry for it in world. |
| 63 |
> |
| 64 |
> Hmm ... I thought kde-apps/knotify:4 was replaced with kde- |
| 65 |
> frameworks/knotifyconfig:5? |
| 66 |
|
| 67 |
I simply recognized following line in the error log: |
| 68 |
|
| 69 |
akonadi_newmailnotifier_agent(6002)/kdeui (KNotification) |
| 70 |
KNotification::slotReceivedIdError: Error while contacting notify daemon |
| 71 |
"The name org.kde.knotify was not provided by any .service files" |
| 72 |
|
| 73 |
After installing knotify:4 I suddenly got desktopn messages from KMail |
| 74 |
again. |
| 75 |
|
| 76 |
> A user complained that new messages no longer create a popup. |
| 77 |
|
| 78 |
Seems to match the error log. |
| 79 |
|
| 80 |
Cheers, |
| 81 |
Jörg |
Archives