I seem the have the exact same problem as described in this link: https://bugs.gentoo.org/show_bug.cgi?id=496768#c7 Only the old kwalletd is not avaiable anymore in portage so I can't use the solution described there. I have two wallets: -one where programs store their passwords. This one is opened when I login to KDE. -a second one where I store other passwords (like of the bank), pincodes etc. This one is only opened manually. The second one I can't use anymore. Reproducible: Always
Please don't set the priority yourself.
Can you try this patch please? http://quickgit.kde.org/?p=kde-runtime.git&a=commitdiff&h=33a17ba0104cd94f2e33a3ac007b300553cdb417&o=plain
I was not able to solve it with the patch Probaly I didn't understand: http://wiki.gentoo.org/wiki//etc/portage/patches well enough. I placed the patch in: /etc/portage/patches/kde-base/kwalletd-3.14.3-r1/wallet.patch Also made a batchrc file in /etc/portage. rebooted the computer after compilin kwalletd again.
That looks correct, but the version is 4.14.3-r1 not 3.14.3-r1. Portage output should look look something like: >>> Preparing source in /var/tmp/portage/kde-base/kwalletd-4.14.3-r1/work/kwalletd-4.14.3 ... * Applying kwalletd-4.14.3-CVE-2013-7252.patch ... [ ok ] * Applying user patches from /etc/portage/patches//kde-base/kwalletd-4.14.3-r1 ... * wallet.patch ...
Typing a 4 instead of a 3 indead makes some differnce. Portages tries to use the patch now. So one step further. Thanks for the help so far by the way. The content of /var/tmp/portage/kde-base/kwalletd-4.14.3-r1/temp/wallet.patch.out is: ***** wallet.patch ***** PWD: /var/tmp/portage/kde-base/kwalletd-4.14.3-r1/work/kwalletd-4.14.3 ======================== PATCH COMMAND: patch -p0 -g0 -E --no-backup-if-mismatch < '/etc/portage/patches//kde-base/kwalletd-4.14.3-r1/wallet.patch' ======================== can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/kwalletd/backend/backendpersisthandler.cpp |+++ b/kwalletd/backend/backendpersisthandler.cpp -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 62 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- | |--- a/kwalletd/backend/kwalletbackend.cc |+++ b/kwalletd/backend/kwalletbackend.cc -------------------------- No file to patch. Skipping patch. 6 out of 6 hunks ignored patch program exited with status 1 ======================== PATCH COMMAND: patch -p1 -g0 -E --no-backup-if-mismatch < '/etc/portage/patches//kde-base/kwalletd-4.14.3-r1/wallet.patch' ======================== checking file kwalletd/backend/backendpersisthandler.cpp Hunk #1 succeeded at 139 (offset -1 lines). Hunk #2 FAILED at 159. 1 out of 2 hunks FAILED checking file kwalletd/backend/kwalletbackend.cc patch program exited with status 1 ======================== PATCH COMMAND: patch -p2 -g0 -E --no-backup-if-mismatch < '/etc/portage/patches//kde-base/kwalletd-4.14.3-r1/wallet.patch' ======================== can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/kwalletd/backend/backendpersisthandler.cpp |+++ b/kwalletd/backend/backendpersisthandler.cpp -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 62 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- | |--- a/kwalletd/backend/kwalletbackend.cc |+++ b/kwalletd/backend/kwalletbackend.cc -------------------------- No file to patch. Skipping patch. 6 out of 6 hunks ignored patch program exited with status 1 ======================== PATCH COMMAND: patch -p3 -g0 -E --no-backup-if-mismatch < '/etc/portage/patches//kde-base/kwalletd-4.14.3-r1/wallet.patch' ======================== can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/kwalletd/backend/backendpersisthandler.cpp |+++ b/kwalletd/backend/backendpersisthandler.cpp -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 62 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- | |--- a/kwalletd/backend/kwalletbackend.cc |+++ b/kwalletd/backend/kwalletbackend.cc -------------------------- No file to patch. Skipping patch. 6 out of 6 hunks ignored patch program exited with status 1 ======================== PATCH COMMAND: patch -p4 -g0 -E --no-backup-if-mismatch < '/etc/portage/patches//kde-base/kwalletd-4.14.3-r1/wallet.patch' ======================== can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/kwalletd/backend/backendpersisthandler.cpp |+++ b/kwalletd/backend/backendpersisthandler.cpp -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 62 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- | |--- a/kwalletd/backend/kwalletbackend.cc |+++ b/kwalletd/backend/kwalletbackend.cc -------------------------- No file to patch. Skipping patch. 6 out of 6 hunks ignored patch program exited with status 1
Is kwalletd-4.14.3-CVE-2013-7252.patch from the ebuild still being applied first? This new one depends on it.
Looking at the output of emerge it seems to me it is applying user patches first. So you are spot on with your remark. * Package: kde-base/kwalletd-4.14.3-r1 * Repository: gentoo * Maintainer: kde@gentoo.org * USE: abi_x86_64 amd64 elibc_glibc gpg kernel_linux userland_GNU * FEATURES: preserve-libs sandbox userpriv usersandbox >>> Unpacking source... * Unpacking parts of kde-runtime-4.14.3.tar.xz to /var/tmp/portage/kde-base/kwalletd-4.14.3-r1/work ... tar extract command failed at least partially - continuing anyway [ ok ] >>> Source unpacked in /var/tmp/portage/kde-base/kwalletd-4.14.3-r1/work * Applying user patches from /etc/portage/patches//kde-base/kwalletd-4.14.3-r1 ... * wallet.patch ... * Failed Patch: wallet.patch ! * ( /etc/portage/patches//kde-base/kwalletd-4.14.3-r1/wallet.patch )
I don't know why it's ignoring the ebuild patch in favour of only the user one. You could try editing the ebuild and applying the patch manually.
I don't dare to fiddle with the ebuild myself. I found a workaround though which may be useful for other people. 1. login at a console (ctrl+alt+f2) with your username 2. cd .kde4/share/apps/kwallet 3. mv kdewallet.kwl kdewallet.kwl~ 4. mv kdewallet.salt kdewallet.salt~ 5. kwl en salt files of wallet which doesn't want to open to kdewallet.kwl and kdewallet.salt 6. login to KDE. When kwallet asks for a password enter the password of the wallet which didn't work. KDE will detect the wallet is in the old format and convert it. 7. logout of KDE 9. mv kdewallet kwl and salt file back to their original name. 10. mv backup of kdewallet kwl and salt file back to their original name. It works now.
Just like to confirm this bug, and say that the patch works. Upstream bug referenced has all the detail. The patch should probably be applied in general, this will mostly affect people with multiple wallets.
Thanks for reporting. This is fixed in cvs now. Please sync in some hours to get the changes. We will stabilize the new revision after the usual wait period. + + 22 Jun 2015; Johannes Huber <johu@gentoo.org> + +files/kwalletd-4.14.3-fix-random-open.patch, +kwalletd-4.14.3-r2.ebuild: + Revision bump adds upstream patch, bug #540790. +
Arches please stabilize =kde-apps/kwalletd 4.14.3-r1 Target: amd64 ppc ppc64 x86
ppc stable
amd64 stable
x86 stable
ppc64 stable. Closing.
