konqueror looses connection to klauncher

Bug #295329 reported by Klaus S. Madsen
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
KDE Base
Fix Released
Medium
kdebase (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: konqueror

I'm using Kubuntu 8.10, and I see a problem where konqueror looses the connection to klauncher. The first part of the konqueror error message is:

"The requested operation could not be completed
Cannot Initiate the about Protocol
Technical Reason: Unable to Launch Process
Details of the Request:
URL: about:blank
Protocol: about
Date and Time: Friday 07 November 2008 21:40
Additional Information: Cannot talk to klauncher: Connection is closed"

I've enabled "Open as tab in existing Konqueror when URL is called externally".

To reproduce the problem, I have a konqueror running on desktop 4 only. Then I change to desktop 1, and right click on an URL in a konsole window, and select "Open Link". I then get a message telling me that the previous konqueror crashed, and allowing me to choose between restoring the session or ignoring the crash data. No matter which of the choices I make, I get a new konqueror window on desktop 1. And after this the konqueror on desktop 4 is no longer capable of connecting to the klauncher, rendering it useless.

Revision history for this message
Jeremy Kerr (jk-ozlabs) wrote :

Same problem here. Another sympton is that konqueror keeps prompting to restore a crash session.

These problems have been reported in kde bugs 167667 and 164307.

Looks like this has been fixed in KDE SVN, commit r870787. Could the kubuntu team backport this change to the kdebase package?

Thanks,

Jeremy

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Thanks for the heads-up. This would make an excellent candidate for cherry-picking.
Relevant websvn link: http://websvn.kde.org/?view=rev&revision=870787

Changed in kdebase:
milestone: none → intrepid-updates
status: New → Triaged
Changed in kdebase:
status: Unknown → Fix Released
Revision history for this message
Jeremy Kerr (jk-ozlabs) wrote :

Looks to be fixed in 4:4.1.3-0ubuntu1~intrepid1 due to the new upstream version.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Yeah, now that 4.1.3 is in recommended updates this is fixed.

Changed in kdebase:
status: Triaged → Fix Released
Changed in kdebase:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.