Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#47422 - [chromium] kwallet5 integration
Attached to Project:
Arch Linux
Opened by Bartholomäus Kwapinski (bartki) - Thursday, 17 December 2015, 13:31 GMT
Last edited by Evangelos Foutras (foutrelis) - Sunday, 20 December 2015, 11:09 GMT
Opened by Bartholomäus Kwapinski (bartki) - Thursday, 17 December 2015, 13:31 GMT
Last edited by Evangelos Foutras (foutrelis) - Sunday, 20 December 2015, 11:09 GMT
|
DetailsProposition: Patch chromium to include kwallet5 integration. See (4)
Packages: * chromium 47.0.2526.106-1 does not include kwallet5 integration Explanation: Chromium is limited and defaults to using kwallet (v4) if run under KDE. In contrast, Plasma 5 and apps (e.g. plasma-nm, kwalletmanager5) utilize kwallet5. (1) Running chromium under Plasma 5 results in having two instances of kwallet simultaneously, along with two password prompts. (2) Only wallet v5 can be managed using the GUI kwalletmanager5. This is inconvenient. (3) Since Plasma 4 was officially dropped on 10th of Dec, I assume that using KDE4 apps (like kwallet4) will be discouraged in near future. Additional info: This request was met upstream on 7th of Oct. but is not included in the official release to date. I have attached the corresponding patchfile. See: https://code.google.com/p/chromium/issues/detail?id=500281 (4) Side note: Is there a possibility to read up at which point in time (4) will hit the official release? 
chromium-kwallet5.patch
(32.3 KiB)
|
This task depends upon
Closed by Evangelos Foutras (foutrelis)
Sunday, 20 December 2015, 11:09 GMT
Reason for closing: Implemented
Additional comments about closing: chromium 47.0.2526.106-2 supports kwallet5; the migration issue will be tracked upstream.
Sunday, 20 December 2015, 11:09 GMT
Reason for closing: Implemented
Additional comments about closing: chromium 47.0.2526.106-2 supports kwallet5; the migration issue will be tracked upstream.
Cr-Commit-Position: refs/heads/master@{#352620}
If you compare the above against the branch_base_position column of [1], it should be part of Chromium 48.
[1] https://omahaproxy.appspot.com/
Those two password prompts originate from the "KDE Wallet Migration Agent". The same happens if kwalletd5 is not running and you start it in a terminal (pkill kwalletd; kwalletd5). The migration fails for some reason and thus you get the same two prompts again when kwalletd5 is started again.
Note that without kdebase-runtime installed (which contains /usr/bin/kwalletd) the kwallet5 integration works fine.
@Antonio @Felix Any idea why the migration is failing here?
Add the following to ~/.config/kwalletrc:
[Migration]
showMigrationWizard=true
Then kill and restart kwalletd5. It should then enable the UI for the kwallet migrator, which shows detailed information about the migration process and why it fails.
I added the [Migration]-section in kwalletrc and set the variable showMigrationWizard to true, the only entry so far was "First Use=false" in section [Wallet]. After I launched chromium the kwallet-migration-wizard started and offered me a dialog with some options, so I decided to migrate immediately. Then I got a log with a lot of entries, some were skipped because they were already migratded. After all I got a new entry in section [Migration]"alreadyMigrated=true".
After re-launch of chromium nothing happend so far, and when I entered a site who needs credentials kwallet pop up and ask for the password and process "kwalletd5" started.
That is exact the behaviour I known before, only prompting for a password after I opend a site who needs credentials, and ask only once.
I thinks thats the solution for me, thanks again for your right advice.