| Summary: | KWallet not starting, loading wallets, or working with apps | ||
|---|---|---|---|
| Product: | [Unmaintained] kdelibs | Reporter: | Dave Haefner <dave> |
| Component: | kwallet | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | davidshen84, lemma |
| Priority: | NOR | ||
| Version: | 4.1 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Dave Haefner
2008-10-07 21:07:38 UTC
That sounds like something that is hard to debug. Could you please what you have in ~/.kde4/share/apps/kwallet? Do you see any output if you launch kwalletd (instead of kwalletmanager) from the commandline? I guess you checked for the obvious (kwallet enabled in systemsettings), but does ~/.kde4/share/config/kwalletrc sport anything strange? I too have this problem except i'm using an svn version of KDE. running kwalletd gives no output even with --no-fork when trying to access or create a new wallet. I deleted the old wallet, which did nothing. KDE should have write access to the folder. kwalletrc: [Auto Allow] kdewallet= [Auto Deny] kdewallet= [Wallet] Close When Idle=false Close on Screensaver=false Enabled=true First Use=false Idle Timeout=10 Launch Manager=true Leave Manager Open=false Leave Open=true Prompt on Open=true Use One Wallet=true Michael,
I missed that you had commented on this, sorry. Here is the info you asked about:
~/.kde4/share/apps/kwallet only contains two files:
.directory
kdewallet.kwl
kwalletd returns nothing when launched from the command line.
I would not know what constitutes "strange" in kwalletrc, so here it is:
[Auto Allow]
kdewallet=KDE Daemon
[Auto Deny]
kdewallet=
[Wallet]
Close When Idle=false
Close on Screensaver=false
Default Wallet=kdewallet
Enabled=true
First Use=false
Idle Timeout=10
Launch Manager=true
Leave Manager Open=true
Leave Open=true
Prompt on Open=false
Use One Wallet=true
...more info in next post...
An OpenSUSE update has partially fixed the problem. Here are the versions I am now running: dave@apollo:~> kwalletd -v Qt: 4.4.3 KDE: 4.1.3 (KDE 4.1.3) "release 51.1" KDE Wallet Service: 0.1 dave@apollo:~> kwalletmanager -v Qt: 4.4.3 KDE: 4.1.3 (KDE 4.1.3) "release 51.1" KDE Wallet Manager: 1.2 dave@apollo:~> Initially after this upgrade the situation remained unchanged. However I added one new username/password combination and the service worked normally for that one FTP site. Kwallet still will not use the previously entered username/password combinations, but it will use any new ones I put in. I re-entered some of the previous ones by hand, and it will now see those. So it looks like I will have to re-enter all my passwords manually. Not good, there are a LOT of them. One other thing that helped was installing kde4dialog. For some reason that is not included in the OpenSUSE distro kde4 installation, but kwallet seems to use it for some things. Not seeing any output from kwalletd might be the result of kwalletd already running. To try this check ps output or type "kquitapp kwalletd && kwalletd" in which case kwalletd will be shutdown and restarted. Your configs look pretty normal. If you start kwalletmanager manually, are you able to browse the wallets' contents? Aren't the wallets used at all or is that specific to certain applications (like kwallet or kopete) or to certain uses in konqueror (eg. works for ftp but not for storing form contents) ? ps -ax showed kwalletd running. On shutdown/restart this is what I got: dave@apollo:~> kquitapp kwalletd && kwalletd kwalletd(16248): Communication problem with "kwalletd" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" " Yes, I can browse through the kwallet, and it shows my passwords are there, but it does not use them. I first noticed this with FTP, then saw it on websites, forms, etc. The only ones it uses are the one I have put in manually since the last update, the ones prior to that it will not use. That's entirely strange. If you're able to browse the wallet using kwalletmanager it means it's basically working (DBus wise). I'm sorry, but at the current point there's not much I can do about it because I can't reproduce the problem myself :-( I agree it's strange, but I have had to implement a workaround. I have dropped back to KDE 3.5.9 for now. Too many little problems with the 4.X release that were not resolvable. It's not just this one, but many. Most have been reported by others as far as I can tell. Timothy and Dave, in case you've updated to 4.2, can you still reproduce this bug? Unfortunately my distribution has yet to release 4.2, and I find no point in running the SVN anymore. When bugs have been reported for the SVN, they have been ignored, even if there were patches attached. I upgraded to 4.2 via Yast yesterday to test it out. Because I upgraded, and did not do a fresh install, that may have influenced the bug. KWallet does now start and run, and appears to be functioning. However, in the previous report I mentioned that it did not see my previous passwords. Now it sees them, but will not use them, but it does know they are there because when I enter the replacement it places it right below the original with a "-1" appender. So I am still left with the problem of having to re-enter all my passwords by hand. I have the same issue here. My system is Gentoo, KDE5. KWallet seems to work fine when I was using KDE4. After I started my system, I am prompted by KWallet to type in my password so to unlock the key ring. But after that, I cannot start the KWalletManager. In the Journal, the error message repeats: Aug 09 07:48:57 dell org.kde.kwalletd[344]: kwalletd(7816): Communication problem with "kwalletd" , it probably crashed. Aug 09 07:48:57 dell org.kde.kwalletd[344]: Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" " 'pgrep kwalletd' could not find kwalletd process, but found kwalletd5 process. Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |