| 1 |
> Jörg Schaible wrote: |
| 2 |
> |
| 3 |
>> Hi, |
| 4 |
>> |
| 5 |
>> after the update to Plasma 5/KF5, I can no longer open (HTML) files from |
| 6 |
>> my local disk with Konqueror. It claims it does no longer know the file |
| 7 |
>> protocol. I get a similar error in Amarok when I try to apply a cover to |
| 8 |
>> an album from the local disk. It seems all KDE4-based application are |
| 9 |
>> affected. |
| 10 |
>> |
| 11 |
>> Does anybody what's causing this behavior and know how to solve it? |
| 12 |
|
| 13 |
Jörg Schaible wrote: |
| 14 |
|
| 15 |
> Anyone? After upgrading a second machine to KDE/Plasma 5, I have the same |
| 16 |
> behavior there. All KDE-4-based apps fail to interact with the file |
| 17 |
> system. Using KMail I can no longer add any attachment to an email nor |
| 18 |
> save an existing attachment to disk. |
| 19 |
|
| 20 |
OK, finally I found the culprit. I knew that it had to be something in the |
| 21 |
configuration, because I did not had the problem with a new/unused account |
| 22 |
on the same machine. |
| 23 |
|
| 24 |
After some hours of investigation (deleting and restoring files based on |
| 25 |
their modification time in the local configuration), I found out that the |
| 26 |
file protocol works if I remove the salt file of the KDE4 wallet. |
| 27 |
|
| 28 |
Well, unfortunately this prevented KMail to access the mail servers, because |
| 29 |
the wallet was no longer accessible at all. But I could save attachments ;-) |
| 30 |
|
| 31 |
In the end it turned out that the problem was caused by kwallet-pam. When I |
| 32 |
upgraded KDE 4 to 5 I also upgraded kwallet-pam directly. However, this |
| 33 |
prevents unfortunately the migration of the default wallet from KDE 4 to 5. |
| 34 |
This migration happens normally the first time when the default wallet is |
| 35 |
accessed and the user is asked for the wallet's password. |
| 36 |
|
| 37 |
It seems that the PAM system will access the wallet way to early and the |
| 38 |
migration cannot be performed. I have no idea why this finally breaks the |
| 39 |
file protocol for KDE 4 apps, but this is what happens. |
| 40 |
|
| 41 |
After deactivating the kwallet pam module (in /etc/sddm) and a reboot, the |
| 42 |
migration could be performed after the login and all apps behave properly. |
| 43 |
It is even possible to activate the PAM module again afterwards. |
| 44 |
|
| 45 |
Hope this might help others. At least a big fat warning should be added to |
| 46 |
Gentoo's KDE 5 upgrade guide. |
| 47 |
|
| 48 |
Cheers, |
| 49 |
Jörg |
Archives