Ubuntu
kde4libs package

[KDE 4] Konquerors cookie system dies (kded4 dies)

Bug #194425 reported by hangy on 2008-02-22

Affects		Status	Importance	Assigned to	Milestone
	kde4libs (Ubuntu)	Invalid	High	Rich Johnson

Bug Description

Binary package hint: konqueror-kde4

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)"

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-f/Unpacked/Failed-cfg/Half-inst/t-aWait/T-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Beschreibung
+++-================================================-===================================-==============================================================
ii konqueror-kde4 4:4.0.1-0ubuntu2 KDE 4's advanced file manager, web browser and document viewer

Sometimes, the system managing cookies for Konqueror seems to die randomly.
I do not notice that problem unless I open a website where I need a cookie - then cookies just do not work any more and the Konqueror settings dialogue says that it cannot connect to the cookie system or smth. like that (will take a screenshot next time).

I know that this bug report is not a lot of help, but it probably become more helpful if anyone knows what program to debug permanently to get that problem (hopefully not exposing all cookies to launchpad :P) traced back. Unfortunately, the crash seems to be totally randomly from my POV, so I have not procedure on how to reproduce the crash up to now.

Tags:

Revision history for this message

Rich Johnson (nixternal) wrote on 2008-02-22:

I haven't been able to reproduce this yet. I have created a few cookie sites here on the office server with no luck, cleared out all of my cookies and went to Google, YouTube, University Email Website, and more...Any other hints on what I can do to try and get this to fail? Thanks!

Changed in kdebase-kde4:
assignee:	nobody → nixternal
status:	New → Incomplete

Revision history for this message

hangy (hangy) wrote on 2008-02-22:

Screenshot of Konquerors cookie settings tab not opening correctly. Edit (19.5 KiB, image/png)

The problem is that I do not know how to reproduce it either. I was hoping to get information on what process to debug to get further information on this topic.
The crash is not noticable via messagebox or anything directly, you just notice that you do not have cookies working any more and logging out of KDE and logging in agains gets them back. To me, it seems like it can occur while you are working on the computer or even if you just have it idle and the session locked ...

Revision history for this message

Onlinelli (cornelius-maihoefer) wrote on 2008-03-01:

I can confirm this. At a clean install of Hardy-KDE4, I even encountered more problems see Bug #196520 (missing dependency: kdebase-bin-kde4). But after solving that, I still had the same promt as in the screenshot above. I'm not quite sure, but after installing kde4-core, this was gone.... (Can you reproduce, Hangy?)

Revision history for this message

hangy (hangy) wrote on 2008-03-02:

I cannot confirm this one, as far as I can tell, I got kde4-core installed all the time.

kde4-core:
  Installed: 3.3
  Candidate: 3.3
  Version table:
*** 3.3 0
        500 http://archive.ubuntu.com hardy/universe Packages
        100 /var/lib/dpkg/status

Revision history for this message

hangy (hangy) wrote on 2008-03-16:

Just noticed ... kde4-core is version 3.3? :D Just some inconsistent versioning scheme or something else? Also, is there anything new on this bug? :)

Revision history for this message

Yuriy Kozlov (yuriy-kozlov) wrote on 2008-03-27:

I think I've ran into this problem a few times. When this happens, please check if kded4 is running. If it's not, run it and see if that fixes your problem.

Revision history for this message

hangy (hangy) wrote on 2008-03-30:

Yeah right, kded4 was not running. However, I was not able to run it from Konsole or another shell, without anything not reacting any more ...

Revision history for this message

Yuriy Kozlov (yuriy-kozlov) wrote on 2008-06-19:

I haven't run into this (kded4 dying) in a while. Anybody else?

Revision history for this message

hangy (hangy) wrote on 2008-06-22:

Just happened to me again five minutes ago.

kded4 -v
Qt: 4.4.0
KDE: 4.0.5 (KDE 4.0.5)
KDE Daemon: $Id: kded.cpp 770025 2008-02-02 16:20:39Z dfaure $

Yuriy Kozlov (yuriy-kozlov) on 2008-06-22

Changed in kde4libs:
status:	Incomplete → Confirmed

Revision history for this message

Norbert (norbert-marchl) wrote on 2008-09-05:

#10

I start Package Manager, after a while it tell me here a updates, then come a crash information. At the same time opened a window for a incomplete language installation. I click on the button to repair this, but nothing happens. At the same time I write this comment, i become a crash information for Update Notifier closed unexpectedly. Can't say ist this one (or maybe three) bug(s). I close the crash information and the next information Desktop Effects closed unexpectedly appears.

Revision history for this message

Harald Sitter (apachelogger) wrote on 2008-09-09:

#11

Norbert, I rally can't follow, but it sounds mostly unrelated... anyway...

Someone please check if this still is an issue in 4.1.1. If so, please also try with a new user (or move your .kde4/.kde directory to somewhere else in order to reset your configuraitons).

Finally, if all this still leads to the described issue (or if you don't care about a new user/moving your configurations ;-):
1) Install kdebase-dbg kdebase-runtime-dbg kdebase-workspace-dbg
2) start the application kdebugdialog (via a terminal, this application is not visible in the menu)
3) click on the "Select all" button
4) click OK
5) open a terminal (e.g. konsole) and enter the following:
kquitapp kded; sleep10; kded4
6) this will make kded4 give super verbose debugging information in the terminal
7) try to trigger the issue
8) get a backtrace from the kcrash dialog and a the last few lines from the terminal attached to this report
9) start kdebugdialog again and deselect all again

The backtrace is most important since it hopefully gives us the possibility to find the crash location, the terminal output can help us find an appropriate solution. The sooner you can get the information the sooner we can fix the issue :)

Bug Triagers: This bug has to stay open until 2008-11-09!

Changed in kde4libs:
importance:	Undecided → High
status:	Confirmed → Incomplete

Revision history for this message

Jonathan Thomas (echidnaman) wrote on 2008-10-10:

#12

Closing as it's 2008-11-09 ;-)

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!