Since upgrading to 7.0 Stable, I've noticed an occasional problem with
konqueror. I've been recompiling my ports for the past few weeks and have
noticed that some sites are complaining about cookies not being enabled.
Further investigation has revealed that if I start konqueror from the
terminal prompt, I can get an error message:
khtml (dom) Can't communicate with the cookiejar!
A workaround I've discovered is to run kded first. Konqueror works with
cookies after that.
Question:
What process is NOT running kded during the startx process? Where is there a
log to track this?
--
Paul Horechuk
Think Free
Use Open Source Software
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
On Tue, Jul 15, 2008 at 2:57 PM, Paul Horechuk <horechuk@csolve.net> wrote:> Since upgrading to 7.0 Stable, I've noticed an occasional problem with > konqueror. I've been recompiling my ports for the past few weeks and have > noticed that some sites are complaining about cookies not being enabled. > Further investigation has revealed that if I start konqueror from the > terminal prompt, I can get an error message: > khtml (dom) Can't communicate with the cookiejar! > > A workaround I've discovered is to run kded first. Konqueror works with > cookies after that. >I have also noticed this with KDE 3.5.8 and 3.5.9. The problem isn't that kded is not being run, the real problem is that something is causing kded to core dump. Search your system for *.core files. The only solution I found was to restart kded, and then cookies worked. Scot