Version: 4.00.00 (KDE 4.0.0) (using 4.00.00 (KDE 4.0.0), Kubuntu packages) Compiler: gcc OS: Linux (i686) release 2.6.22-14-generic Using KDE 4.0, konqueror works fine during ~12 hours, but suddenly stopped handling cookies. At the same time, it also stopped handling CSS as well..
Any related errors in .xsession-errors ? Is kded4 process running?
On Friday 18 January 2008, Tommi Tervo wrote: [bugs.kde.org quoted mail] > ------- Additional Comments From tommi.tervo gmail com 2008-01-18 12:01 > ------- Any related errors in .xsession-errors ? No, my ~/.xsession-errors doesn't seem to be used since april 2007... :-/ > Is kded4 process running? Nop... kded4 doesn't seem to run... dc
you should find a reason why kded has crashed/vanished. Activate kded4 logging in kdebugdialog and install kde4libs-dbg package.
On Friday 18 January 2008, Tommi Tervo wrote: > ------- Additional Comments From tommi.tervo gmail com 2008-01-18 13:58 > ------- you should find a reason why kded has crashed/vanished. Activate > kded4 logging in kdebugdialog and install kde4libs-dbg package. OK, I'll try to do it this afternoon; but not sure I can make it. This will be tested on monday morning at least. But, I'll need to wait until it fails, and I'm not sure when this will occur. I'll keep you inform asap
> ------- Additional Comments From tommi.tervo gmail com 2008-01-18 13:58 > ------- you should find a reason why kded has crashed/vanished. Activate > kded4 logging in kdebugdialog and install kde4libs-dbg package. The kded4 just crashed after ~48 hours of use... I have set up the loging in kdebugdialog, but where is this log file ? I can't seem tyo find it...
On Wednesday 23 January 2008, dc@mjt.ch wrote: > The kded4 just crashed after ~48 hours of use... I have set up the loging > in kdebugdialog, but where is this log file ? I can't seem tyo find it... Oups, I found it... but discovered that my session didn't have the write permission on it. I changed it and will restyart the kded4
On Friday 18 January 2008, Tommi Tervo wrote: > ------- Additional Comments From tommi.tervo gmail com 2008-01-18 13:58 > ------- you should find a reason why kded has crashed/vanished. Activate > kded4 logging in kdebugdialog and install kde4libs-dbg package. SInce the upgrade to 4.0.1, logging seems to work, but I don't see anything particular in the log file. Since not 'time' is logged with events, I don't realy know what we are talking about... kded4 starts, then dies... It's being launch by kdeinit, but terminates... who knows when. I'd suggest to ask the debugger maintainer to add a timing info in this file : startkde: Starting up... kdeinit4: preparing to launch /usr/lib/kde4/lib/kde4/libexec/klauncher kdeinit4: Launched KLauncher, pid = 6068 result = 0 kdeinit4: opened connection to :0.0 kdeinit4: preparing to launch /usr/lib/kde4/bin/kded4 kdeinit4: Launched KDED, pid = 6069 result = 0 kdeinit4: Got EXT_EXEC '/usr/lib/kde4/bin/kbuildsycoca4' from launcher. kdeinit4: preparing to launch /usr/lib/kde4/bin/kbuildsycoca4 kbuildsycoca4 running... kdeinit4: PID 6071 terminated. kdeinit4: Got EXEC_NEW 'kconf_update' from launcher. kdeinit4: preparing to launch /usr/lib/kde4/lib/kde4/libexec/kconf_update kdeinit4: PID 6072 terminated. kdeinit4: PID 6069 terminated. kdeinit4: preparing to launch /usr/lib/kde4/bin/kcminit_startup kdeinit4: Launched 'kcminit_startup', pid = 6073 result = 0 kdeinit4: Got SETENV 'KDE_MULTIHEAD=false' from klauncher. kdeinit4: PID 6073 terminated. kdeinit4: Got KWRAPPER 'ksmserver' from socket. kdeinit4: preparing to launch /usr/lib/kde4/bin/ksmserver @ In the mean time, I restart kded4 every time it crashes (anytime between 1 and 4 days). Let me know if you need my complete .xsession-errors file (~3.6 MB)
Any message in the logs before kded4 dies? Any core file from kded4?
> ------- Additional Comments From faure kde org 2008-02-12 14:00 ------- > Any message in the logs before kded4 dies? Any core file from kded4? The file is quiet large ~1.3 MB/day and 175'000 lines/day. Since I don't realy know when it dies, I can't relate file content with the dying event. At least, there is no information which tells anything about kded in the log file. I didn't find any core file either... To help determine the action which make kded fail, I just wrote a small script which runs for ever and check if kded is alive. As soon as it dies, a message is written in the log file (with the date). The presence of kded is checked every two seconds; which should be sufficient. I'll send a mail as soon as kded goes away.
On Tuesday 12 February 2008, dc@mjt.ch wrote: > there is no information which tells anything about kded in the log > file. I usually simply look for the word "crash" :)
On Tuesday 12 February 2008, David Faure wrote: > I usually simply look for the word "crash" :) :-[] Well, I forgot to save the .xsession-error file before restarting kded; therefore, I lost the information. I'll simply until the next crash and let you know. dc
On Tuesday 12 February 2008, David Faure wrote: > ------- Additional Comments From faure kde org 2008-02-12 14:00 ------- > Any message in the logs before kded4 dies? Any core file from kded4? kded4 crshed once again. However, since I restarted my session several times, I forgot to launch my 'crash' monitor... The latest message related to kded in the .xsession-errors doesn't lead to anything very usefull. Except the line : KDE Daemon (kded) already running. Here is an extract of my .xsession-errors. (complete file is available upon request; but not on this list as it's quit big). In fact, this is the last portion of the file where kded is mentionned. kdeinit4: Got EXEC_NEW 'kio_http' from launcher. kdeinit4: preparing to launch QEventDispatcherUNIX::unregisterTimer: invalid argument konqueror(4390): Failed to lock file "/home/dc/.kde4/cache-mjtlnx5/kpc/kde-icon-cache.lock", last result = 1 kdeinit4: Got EXEC_NEW 'kio_http' from launcher. kdeinit4: preparing to launch kdeinit4: Got EXEC_NEW 'kio_http' from launcher. kdeinit4: preparing to launch QEventDispatcherUNIX::unregisterTimer: invalid argument kdeinit4: Got EXEC_NEW 'kio_http' from launcher. kdeinit4: preparing to launch kdeinit4: PID 7823 terminated. KDE Daemon (kded) already running. kded(7826): Communication problem with "kded" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" " QEventDispatcherUNIX::unregisterTimer: invalid argument kdeinit4: Got EXEC_NEW 'kio_http' from launcher. kdeinit4: preparing to launch dc
On Friday 18 January 2008, Tommi Tervo wrote: > ------- Additional Comments From tommi.tervo gmail com 2008-01-18 13:58 > ------- you should find a reason why kded has crashed/vanished. Activate > kded4 logging in kdebugdialog and install kde4libs-dbg package. I was finaly able to catch some info when the kded4 died. Here are a few lines of the .xsession-errors file. I'm currently running KDE 4.0.2, whic I installed this morning (systeme rebooted). ... QEventDispatcherUNIX::unregisterTimer: invalid argument kdeinit4: Got EXEC_NEW 'kio_http' from launcher. kdeinit4: preparing to launch kdeinit4: Got EXEC_NEW 'kio_http' from launcher. kdeinit4: preparing to launch QEventDispatcherUNIX::unregisterTimer: invalid argument kdeinit4: Got EXEC_NEW 'kio_http' from launcher. kdeinit4: preparing to launch kdeinit4: Got EXEC_NEW 'kio_http' from launcher. kdeinit4: preparing to launch QEventDispatcherUNIX::unregisterTimer: invalid argument KDE Daemon (kded) already running. kdeinit4: PID 16401 terminated. QEventDispatcherUNIX::unregisterTimer: invalid argument kded(16425): Communication problem with "kded" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" " QEventDispatcherUNIX::unregisterTimer: invalid argument KDED is dead at Thu Mar 6 13:48:28 CET 2008 <<< Line added by my daemon QEventDispatcherUNIX::unregisterTimer: invalid argument QEventDispatcherUNIX::unregisterTimer: invalid argument QEventDispatcherUNIX::unregisterTimer: invalid argument ... My daemon checks the presence of kded4 every two seconds; which means there is certainly a small delay between the death and the time I write in the file. dc
Here is another sample of the .xsession-errors file. Since the 4.0.2 update, kded4 dies very often ! My guess is that it's related somehow to konqueror... This morning, after a small update of some kde4 applics (minors), I decided to reboot. Kded4 died as soon as my sessions started to restore. I started kded4 manualy and it died two hours later... The 'KDED is dead...' can be found at the end of the output dc ... konqueror(6877) LocalDomainUriFilter::filterUri: KUrl("http://slashdot.org:80/") konqueror(6877) FixHostUriFilter::filterUri: FixHostUriFilter::filterUri: KUrl("http://slashdot.org:80/") QEventDispatcherUNIX::unregisterTimer: invalid argument QEventDispatcherUNIX::unregisterTimer: invalid argument konqueror(6147) KonqPopupMenuPrivate::setup: 4 offers KonqPopupMenu(0x9532de0) QMenu(0xbb25dd8) konqueror(6147) KonqMenuActions::addActionsTo: "/usr/lib/kde4/share/kde4/services/ServiceMenus/encryptfile.desktop" ("KonqPopupMenu/Plugin", "application/octet-stream") konqueror(6147) KonqMenuActions::addActionsTo: "/usr/lib/kde4/share/kde4/services/ServiceMenus/kget_download.desktop" ("KonqPopupMenu/Plugin", "all/allfiles") konqueror(6147) KonqMenuActions::addActionsTo: "/usr/lib/kde4/share/kde4/services/ServiceMenus/konsolehere.desktop" ("KonqPopupMenu/Plugin", "inode/directory") konqueror(6147) KonqMenuActions::addActionsTo: "/usr/lib/kde4/share/kde4/services/ServiceMenus/karbon_konqi.desktop" ("KonqPopupMenu/Plugin", "application/x-karbon") konqueror(6147) KonqMenuActions::addActionsTo: "/usr/lib/kde4/share/kde4/services/ServiceMenus/kspread_konqi.desktop" ("KonqPopupMenu/Plugin", "application/x-kspread") konqueror(6147) KonqMenuActions::addActionsTo: "/usr/lib/kde4/share/kde4/services/ServiceMenus/kchart_konqi.desktop" ("KonqPopupMenu/Plugin", "application/x-kchart") konqueror(6147) KonqMenuActions::addActionsTo: "/usr/lib/kde4/share/kde4/services/ServiceMenus/encryptfolder.desktop" ("inode/directory", "KonqPopupMenu/Plugin") konqueror(6147) KonqMenuActions::addActionsTo: "/usr/lib/kde4/share/kde4/services/ServiceMenus/krita_konqi.desktop" ("KonqPopupMenu/Plugin", "application/x-krita") konqueror(6147) KonqMenuActions::addActionsTo: "/usr/lib/kde4/share/kde4/services/ServiceMenus/installfont.desktop" ("KonqPopupMenu/Plugin", "application/x-font-ttf", "application/x-font-type1", "application/x-font-bdf", "application/x-font-pcf", "application/x-font-otf", "application/x-font-afm", "fonts/package") konqueror(6147) KonqMenuActions::addActionsTo: "/usr/lib/kde4/share/kde4/services/ServiceMenus/jukservicemenu.desktop" ("KonqPopupMenu/Plugin", "application/ogg", "audio/x-vorbis+ogg", "audio/mpeg", "audio/x-flac", "audio/x-flac+ogg", "audio/x-musepack") konqueror(6147) KonqMenuActions::addActionsTo: "/usr/lib/kde4/share/kde4/services/ServiceMenus/kexi_konqi.desktop" ("KonqPopupMenu/Plugin", "application/x-kexi") konqueror(6147) KonqMenuActions::addActionsTo: "/usr/lib/kde4/share/kde4/services/ServiceMenus/audiocd_play.desktop" ("KonqPopupMenu/Plugin", "media/audiocd") konqueror(6147) KonqMenuActions::addActionsTo: "/usr/lib/kde4/share/kde4/services/ServiceMenus/kformula_konqi.desktop" ("KonqPopupMenu/Plugin", "application/x-kformula") konqueror(6147) KonqMenuActions::addActionsTo: "/usr/lib/kde4/share/kde4/services/ServiceMenus/kivio_konqi.desktop" ("KonqPopupMenu/Plugin", "application/x-kivio") konqueror(6147) KonqMenuActions::addActionsTo: "/usr/lib/kde4/share/kde4/services/ServiceMenus/kpresenter_konqi.desktop" ("KonqPopupMenu/Plugin", "application/x-kpresenter") konqueror(6147) KonqMenuActions::addActionsTo: "/usr/lib/kde4/share/kde4/services/ServiceMenus/floppy_format.desktop" ("media/floppy_unmounted", "media/floppy5_unmounted", "KonqPopupMenu/Plugin") konqueror(6147) KonqMenuActions::addActionsTo: "/usr/lib/kde4/share/kde4/services/ServiceMenus/kword_konqi.desktop" ("KonqPopupMenu/Plugin", "application/x-kword") konqueror(6877) KConfigGroup::readXdgListEntry: List entry mime in "/usr/lib/kde4/share/kde4/apps/kjava/pluginsinfo" is not compliant with XDG standard (missing trailing semicolon). konqueror(6877) KConfigGroup::readXdgListEntry: List entry mime in "/home/dc/.kde4/share/apps/nsplugins/pluginsinfo" is not compliant with XDG standard (missing trailing semicolon). onqueror(6877) KConfigGroup::readXdgListEntry: List entry mime in "/home/dc/.kde4/share/apps/nsplugins/pluginsinfo" is not compliant with XDG standard (missing trailing semicolon). konqueror(6877) KConfigGroup::readXdgListEntry: List entry mime in "/home/dc/.kde4/share/apps/nsplugins/pluginsinfo" is not compliant with XDG standard (missing trailing semicolon). konqueror(6877) KConfigGroup::readXdgListEntry: List entry mime in "/home/dc/.kde4/share/apps/nsplugins/pluginsinfo" is not compliant with XDG standard (missing trailing semicolon). konqueror(6877) KConfigGroup::readXdgListEntry: List entry mime in "/home/dc/.kde4/share/apps/nsplugins/pluginsinfo" is not compliant with XDG standard (missing trailing semicolon). konqueror(6877) KConfigGroup::readXdgListEntry: List entry mime in "/home/dc/.kde4/share/apps/nsplugins/pluginsinfo" is not compliant with XDG standard (missing trailing semicolon). konqueror(6877) KConfigGroup::readXdgListEntry: List entry mime in "/home/dc/.kde4/share/apps/nsplugins/pluginsinfo" is not compliant with XDG standard (missing trailing semicolon). konqueror(6877) KConfigGroup::readXdgListEntry: List entry mime in "/home/dc/.kde4/share/apps/nsplugins/pluginsinfo" is not compliant with XDG standard (missing trailing semicolon). konqueror(6877) KConfigGroup::readXdgListEntry: List entry mime in "/home/dc/.kde4/share/apps/nsplugins/pluginsinfo" is not compliant with XDG standard (missing trailing semicolon). konqueror(6877) KConfigGroup::readXdgListEntry: List entry mime in "/home/dc/.kde4/share/apps/nsplugins/pluginsinfo" is not compliant with XDG standard (missing trailing semicolon). konqueror(6877) KConfigGroup::readXdgListEntry: List entry mime in "/home/dc/.kde4/share/apps/nsplugins/pluginsinfo" is not compliant with XDG standard (missing trailing semicolon). kdeinit4: Got EXEC_NEW 'kio_http' from launcher. kdeinit4: preparing to launch QDBusConnection received a message of type 3 that it shouldn't have QDBusConnection received a message of type 3 that it shouldn't have QDBusConnection received a message of type 3 that it shouldn't have QDBusConnection received a message of type 3 that it shouldn't have QDBusConnection received a message of type 3 that it shouldn't have kdeinit4: PID 6879 terminated. kdeinit4: PID 6649 terminated. kdeinit4: PID 6878 terminated. QDBusConnection received a message of type 3 that it shouldn't have QDBusConnection received a message of type 3 that it shouldn't have konqueror(6877) KConfigGroup::readXdgListEntry: List entry mime in "/usr/lib/kde4/share/kde4/apps/kjava/pluginsinfo" is not compliant with XDG standard (missing trailing semicolon). konqueror(6877) KConfigGroup::readXdgListEntry: List entry mime in "/home/dc/.kde4/share/apps/nsplugins/pluginsinfo" is not compliant with XDG standard (missing trailing semicolon). konqueror(6877) KConfigGroup::readXdgListEntry: List entry mime in "/home/dc/.kde4/share/apps/nsplugins/pluginsinfo" is not compliant with XDG standard (missing trailing semicolon). konqueror(6877) KConfigGroup::readXdgListEntry: List entry mime in "/home/dc/.kde4/share/apps/nsplugins/pluginsinfo" is not compliant with XDG standard (missing trailing semicolon). konqueror(6877) KConfigGroup::readXdgListEntry: List entry mime in "/home/dc/.kde4/share/apps/nsplugins/pluginsinfo" is not compliant with XDG standard (missing trailing semicolon). konqueror(6877) KConfigGroup::readXdgListEntry: List entry mime in "/home/dc/.kde4/share/apps/nsplugins/pluginsinfo" is not compliant with XDG standard (missing trailing semicolon). konqueror(6877) KConfigGroup::readXdgListEntry: List entry mime in "/home/dc/.kde4/share/apps/nsplugins/pluginsinfo" is not compliant with XDG standard (missing trailing semicolon). konqueror(6877) KConfigGroup::readXdgListEntry: List entry mime in "/home/dc/.kde4/share/apps/nsplugins/pluginsinfo" is not compliant with XDG standard (missing trailing semicolon). konqueror(6877) KConfigGroup::readXdgListEntry: List entry mime in "/home/dc/.kde4/share/apps/nsplugins/pluginsinfo" is not compliant with XDG standard (missing trailing semicolon). konqueror(6877) KConfigGroup::readXdgListEntry: List entry mime in "/home/dc/.kde4/share/apps/nsplugins/pluginsinfo" is not compliant with XDG standard (missing trailing semicolon). konqueror(6877) KConfigGroup::readXdgListEntry: List entry mime in "/home/dc/.kde4/share/apps/nsplugins/pluginsinfo" is not compliant with XDG standard (missing trailing semicolon). konqueror(6877) KConfigGroup::readXdgListEntry: List entry mime in "/home/dc/.kde4/share/apps/nsplugins/pluginsinfo" is not compliant with XDG standard (missing trailing semicolon). QEventDispatcherUNIX::unregisterTimer: invalid argument QDBusConnection received a message of type 3 that it shouldn't have QDBusConnection received a message of type 3 that it shouldn't have KDED is dead at Fri Mar 7 13:07:51 CET 2008 QEventDispatcherUNIX::unregisterTimer: invalid argument QEventDispatcherUNIX::unregisterTimer: invalid argument QEventDispatcherUNIX::unregisterTimer: invalid argument QEventDispatcherUNIX::unregisterTimer: invalid argument kdeinit4: Got EXT_EXEC '/usr/lib/kde4/bin/kbuildsycoca4' from launcher. kdeinit4: preparing to launch /usr/lib/kde4/bin/kbuildsycoca4 kbuildsycoca4 running... kdeinit4: PID 7048 terminated.
On Friday 07 March 2008, dc@mjt.ch wrote: [bugs.kde.org quoted mail] After updating to KDE 4.0.3, kded4 still died for strange reasons However, I have the strong feeling that it's related to konqueror's activity somehow... This time it occured just when I opened many tabs in konqueror (>20). Here are the last few lines in my .xession-errors file, just before the death of kded4. konqueror(24289) KConfigGroup::readXdgListEntry: List entry mime in "/usr/lib/kde4/share/kde4/apps/kjava/pluginsinfo" is not compliant with XDG standard (missing trailing semicolon). kdeinit4: Got EXEC_NEW 'kio_http' from launcher. kdeinit4: preparing to launch kdeinit4: Got EXEC_NEW 'kio_http' from launcher. kdeinit4: preparing to launch kdeinit4: Got EXEC_NEW 'kio_http' from launcher. kdeinit4: preparing to launch kdeinit4: PID 1979 terminated. kdeinit4: Got EXEC_NEW 'kio_http' from launcher. kdeinit4: preparing to launch konqueror(24289) KConfigGroup::readXdgListEntry: List entry mime in "/usr/lib/kde4/share/kde4/apps/kjava/pluginsinfo" is not compliant with XDG standard (missing trailing semicolon). kdeinit4: PID 3458 terminated. KDE Daemon (kded) already running. kded(3499): Communication problem with "kded" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" " KDED is dead at Wed Apr 2 14:40:45 CEST 2008 Daniel Cordey
Still valid with kde 4.1-alpha (4.0.73). dbus version: 1.2.1 I can lock my system eveytime when pressing "ALT" and generating the timeout message
Same message as in bug 162140: Can you attach gdb to kded in order to provide a backtrace? Either (if kded is already running) gdb kded `pidof kded` or (to start a new kded) gdb --args kded --nofork Alternatively, valgrind kded --nofork 2>&1 | tee vg.log
I see no ~SimpleJob warning, so I suppose this isn't the same crash as Bug 161734. However I would recommend applying the patch from http://websvn.kde.org/?view=rev&revision=825063 just to make sure it's not the same crash :)
I dont know if it's the right place, but i'm running KDE 4.1.1 and i always this bug with kded4
We fixed a large number of kded crashes recently (Bug 171870 in the globalaccel code, the favicon crash earlier on), and there's still a known crash in kdirwatch (Bug 165548) and one in kcookiejar (Bug 169731). This report is a collection of unidentified crashes which are very probably among those already. I'll close this report since it's not useful, once you get a real backtrace, subscribe to the relevant bug among those I listed above.