Version: (using KDE KDE 3.1) Installed from: Compiled From Sources Compiler: gcc 2.95.3 sparc sun Solaris 2.7 OS: Solaris For some unknown reason it appears that kcookiejar has crashed and I am unable to restart it. In konqueror if I try and enable cookies I get the message: "I can't enable cookies, because the cookie daemon could not be started." It was working before and suddenly stopped working. I can restart KDE and it still doesn't work. If I go to the konqueror settings and click on Cookies I get the message: "This control module could not start the cookie server process. It will not be possible to manage received cookies." Also, while trying to edit the cookies I got a crash with the following trace: Retry #1: Retry #2: Retry #3: Retry #4: [New LWP 1 ] [New Thread 1 (LWP 1)] [Switching to Thread 1 (LWP 1)] 0xfde1a444 in _waitid () from /usr/lib/libc.so.1 #0 0xfde1a444 in _waitid () from /usr/lib/libc.so.1 #1 0xfddd8360 in _waitpid () from /usr/lib/libc.so.1 #2 0xfdceb05c in waitpid () from /usr/lib/libthread.so.1 #3 0xfdce9354 in __libthread_segvhdlr () from /usr/lib/libthread.so.1 #4 0xfdcebdfc in __sighndlr () from /usr/lib/libthread.so.1 #5 <signal handler called> #6 0xfda31948 in KCookiesMain::save (this=0x920f0) at kcookiesmain.cpp:74 #7 0xfdc65dd0 in KCDialog::slotApply (this=0xd2038) at kcdialog.cpp:71 #8 0xfef5ce38 in KDialogBase::qt_invoke (this=0xd2038, _id=74, _o=0xffbedf80) at kdialogbase.moc:366 #9 0xfdc65b1c in KCDialog::qt_invoke (this=0xd2038, _id=74, _o=0xffbedf80) at kcdialog.moc:101 #10 0xfe387afc in QObject::activate_signal () from /tools/qt/qt-3.1.1/lib/libqt-mt.so.3 #11 0xfe387900 in QObject::activate_signal () from /tools/qt/qt-3.1.1/lib/libqt-mt.so.3 #12 0xfe6fefc4 in QButton::clicked () from /tools/qt/qt-3.1.1/lib/libqt-mt.so.3 #13 0xfe4264c8 in QButton::mouseReleaseEvent () from /tools/qt/qt-3.1.1/lib/libqt-mt.so.3 #14 0xfe3c5adc in QWidget::event () from /tools/qt/qt-3.1.1/lib/libqt-mt.so.3 #15 0xfe31aae0 in QApplication::internalNotify () from /tools/qt/qt-3.1.1/lib/libqt-mt.so.3 #16 0xfe31a46c in QApplication::notify () from /tools/qt/qt-3.1.1/lib/libqt-mt.so.3 #17 0xfec69f24 in KApplication::notify (this=0xffbee918, receiver=0xd6d38, event=0xffbee330) at kapplication.cpp:453 #18 0xfe2b3280 in QETWidget::translateMouseEvent () from /tools/qt/qt-3.1.1/lib/libqt-mt.so.3 #19 0xfe2b0ab8 in QApplication::x11ProcessEvent () from /tools/qt/qt-3.1.1/lib/libqt-mt.so.3 #20 0xfe2c8098 in QEventLoop::processEvents () from /tools/qt/qt-3.1.1/lib/libqt-mt.so.3 #21 0xfe331880 in QEventLoop::enterLoop () from /tools/qt/qt-3.1.1/lib/libqt-mt.so.3 #22 0xfe31ad34 in QApplication::enter_loop () from /tools/qt/qt-3.1.1/lib/libqt-mt.so.3 #23 0xfe51da1c in QDialog::exec () from /tools/qt/qt-3.1.1/lib/libqt-mt.so.3 #24 0xfdc608c0 in main (_argc=-4265792, _argv=0x920f0) at kcmshell.cpp:247 #25 0x00014ec0 in _end () #26 0x00015c7c in handle_launcher_request (sock=9) at kinit.cpp:1023 #27 0x0001612c in handle_requests (waitForPid=0) at kinit.cpp:1189 #28 0x00017124 in main (argc=0, argv=0xffbeef54, envp=0xffbeef64) at kinit.cpp:1540 And finally, whenever I attempt to load kcookiejar through dcop with the statement dcop kded kded loadModule kcookiejar it replies with false and does not load the module. I don't know if this means anything or not.
Subject: KDE_3_1_BRANCH: kdebase/kcontrol/kio CVS commit by waba: Don't crash when management module is disabled. (BR 55584) CCMAIL: 55584@bugs.kde.org M +2 -0 kcookiesmain.cpp 1.13.2.1 --- kdebase/kcontrol/kio/kcookiesmain.cpp #1.13:1.13.2.1 @@ -20,4 +20,6 @@ KCookiesMain::KCookiesMain(QWidget *pare : KCModule(parent, name) { + management = 0; + bool managerOK = false; QByteArray data;
Subject: Re: New: kcookiejar stops working and can't be restarted Is kded still running when this happens? > Retry #1: > Retry #2: > Retry #3: > Retry #4: I have no idea where these "Retry #n:" things come from. They are not pat of any KDE code. > #6 0xfda31948 in KCookiesMain::save (this=0x920f0) at kcookiesmain.cpp:74 > #7 0xfdc65dd0 in KCDialog::slotApply (this=0xd2038) at kcdialog.cpp:71 I have fixed this crash. Cheers, Waldo
Subject: Re: kcookiejar stops working and can't be restarted As far as I know kded is still running. It is difficult to tell, since on Solaris I cannot get the names of any KDE apps, only kdeinit (and this is with the long ps listing). I managed to get kcookiejar to start working again on my setup by changing the startkde script so it manually starts kded. I then killed kded and restarted it after KDE was up and now I can load kcookiejar. The person sitting across from me cannot get his working, however. As for the Retry, this is common on Solaris in my experience. It may be due to the slow performance in our environment. Most of us have Ultra 5 workstations running at around 300MHz with everything loaded over NFS. Any idea on why kcookiejar won't start? I've tried enabling debug messages for both kcookiejar and kded, but nothing gets printed. According to dcop, kded returns false when I issue the command dcop kded kded loadModule kcookiejar. -Aaron Waldo Bastian wrote: >------- You are receiving this mail because: ------- >You reported the bug, or are watching the reporter. > >http://bugs.kde.org/show_bug.cgi?id=55584 > > > > >------- Additional Comments From bastian@kde.org 2003-03-06 15:35 ------- >Subject: Re: New: kcookiejar stops working and can't be restarted > >Is kded still running when this happens? > > > >>Retry #1: >>Retry #2: >>Retry #3: >>Retry #4: >> >> > >I have no idea where these "Retry #n:" things come from. They are not pat of >any KDE code. > > > >>#6 0xfda31948 in KCookiesMain::save (this=0x920f0) at kcookiesmain.cpp:74 >>#7 0xfdc65dd0 in KCDialog::slotApply (this=0xd2038) at kcdialog.cpp:71 >> >> > >I have fixed this crash. > >Cheers, >Waldo > >
Subject: Re: kcookiejar stops working and can't be restarted if "dcop kded kded loadModule kcookiejar" returns false then kded is indeed still running. Can you start kded manually and then strace what kded does when you run "dcop kded kded loadModule kcookiejar". (Assuming you have strace or something comparable on solaris) Cheers, Waldo
Subject: Re: kcookiejar stops working and can't be restarted I will try and do this when I can recreate the problem. I don't have strace or an equivelent on Solaris 7, which is what I am running (it is in Solaris 8, though). The next time it happens I can bring up kded in gdb or ddd, though. -Aaron Waldo Bastian wrote: >------- You are receiving this mail because: ------- >You reported the bug, or are watching the reporter. > >http://bugs.kde.org/show_bug.cgi?id=55584 > > > > >------- Additional Comments From bastian@kde.org 2003-03-07 11:48 ------- >Subject: Re: kcookiejar stops working and can't be restarted > >if "dcop kded kded loadModule kcookiejar" returns false then kded is indeed >still running. Can you start kded manually and then strace what kded does >when you run "dcop kded kded loadModule kcookiejar". >(Assuming you have strace or something comparable on solaris) > >Cheers, >Waldo > >
I found the source of the problem after attaching ddd to kded. It seems that libgcc_s.so.1 was not in the LD_LIBRARY_PATH and hence it could not load the necessary library. After creating a symlink to the appropriate place it is now working. One more bug due to a stupid user :)