On Friday 06 July 2007, you wrote: > On Friday, 6. July 2007, David Booth wrote: > > On Friday 06 July 2007, you wrote: > > > On Friday, 6. July 2007, David Booth wrote: > > > > On Friday 06 July 2007, you wrote: > > > > > On Friday, 6. July 2007, David Booth wrote: > > > > > > After a seemingly successful portupgrade bringing kde up > > > > > > to 3.5.7 on a 6.2 Stable system, Kwalletmanager can no > > > > > > longer open existing wallets or create new ones. There > > > > > > is no option to open a wallet under the file menu and > > > > > > execution of the New Wallet option seems to do nothing. > > > > > > There are no error messages, just no action. Can anyone > > > > > > provide some guidance as how to troubleshoot this > > > > > > problem? > > > > > > > > > > Is it just kwalletmanager or do applications fail to open > > > > > wallets as well? What does 'dcop kded kwalletd' yield? > > > > > > > > Applications fail to open wallets as well. > > > > > > > > # dcop kded kwalletd > > > > object 'kwalletd' in application 'kded' not accessible > > > > > > This means kded isn't running - probably because it crashed. > > > Have you restarted KDE since the update yet? Do you get a > > > DrKonqi message when you start KDE telling you that kded > > > crashed? > > > > Yes, I have restarted KDE multiple times and get no message on > > startup about kded or any other problem. > > > > I can manually start kded after KDE is up and kwallet now works > > correctly, but the next restart of KDE again has no kded running. > > I suspect kded might be crashing right away after being launched by > kdeinit then. Never happened to myself, but from what I remember > reading on various mailing lists, you could try: > > - Running kbuildsycoca manually, perhaps with the --noincremental > switch. Do this without manually launching kded. > - Delete or manually resave your session: First, manually run kded, > then, in KControl/KDE Components/Session Manager, switch the 'On > Login' setting to 'Restore manually saved session', apply and > select 'Save Session' from the K-Menu. If that doesn't work, try > again with 'Start with an empty session' instead. > > More suggestions from the mailing list audience are much > appreciated at this point, since I never hit that particular > problem.
No luck with the above suggestions. I also tried creating a new user so I would start with a virgin configuration and the problem is the same. _______________________________________________ kde-freebsd mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-freebsd
