Bug 204451

Summary: Clicking on URL in email in Kmail or Thunderbird messes up browser
Product: [Unmaintained] kdelibs Reporter: Maurice Batey <maurice>
Component: generalAssignee: kdelibs bugs <kdelibs-bugs>
Status: RESOLVED WORKSFORME    
Severity: normal CC: andrew.crouthamel, maurice, timon
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Mandriva RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Maurice Batey 2009-08-19 21:19:14 UTC 
Version:            (using KDE 4.2.4)
OS:                Linux
Installed from:    Mandriva RPMs

(N.B. This fault occurred both under KDE 4.2.2 and 4.2.4.)

The problem does *not* arise if - in Configure Desktop/Personal/Default Applications/Web Browser - the 2nd button of Default Component is selected (+ name of browser (e.g. Firefox, Opera).

If, however, the 1st button is selected (which seems to be the default) then - with certain URL's in an email (e.g. http://www.amipp.org.uk/phorum5) whether in KMail or Thunderbird- although the browser is called, the call fails as below.

(N.B. If I copy/paste it into Firefox (or Opera), it works fine.)

When I click on the URL, I get a Firefox/Opera failure window:

(with: "file:///home/mab/tmp/kdecache-mab/krun/14672.0.phorum5"
showing in FF's action bar)

"File Not Found

The file /home/mab/tmp/kdecache-mab/krun/header.htm cannot be found.
Please check the location and try again."

and also:

"The file /home/mab/tmp/kdecache-mab/krun/index.php cannot be found.
Please check the location and try again."

Although I do have a directory /home/mab/tmp/kdecache-mab/krun/, and there are files in there, the two files mentioned are not.
   BUT the file shown in FF's action bar (14672.0.phorum5 - see above) is there, and it contains references to the 2 missing files:

 "<frame name="header" scrolling="no" noresize target="main"
src="header.htm">
  <frame name="main" src="index.php">
  <noframes>
  <body>

 <p>This page uses frames, but your browser doesn't support them.</p>"

  (Guess the big clue is in that last line...)

In general, some URL's work, and others take me to only a
partly-formatted version of the web site. No problems with URL's elsewhere, e.g. in Pan newsgroup postings

The email URL that goes to a partially-formatted web page is:

http://www.readitswapit.co.uk/SwapStage2.aspx?SwapID=1175556

When copy/pasted into FF/Opera, it works normally, but when clicked on in the email FF/Opera shows a useless partially-formatted version of the web page.

The problems disappear if the Config..../Web browser 2nd button is selected, with browser name.

Also, the problem does not occur if the URL is copy/pasted into the Firefox (or Opera) action bar, instead of clicking on it.
Comment 1 Maurice Batey 2009-08-20 13:28:28 UTC 
It may just be a coincidence, but the two users (me using Kmail and the other using Thunderbird) had both recently tried Firefox 3.5, so I suppose there is a possibility that trying FF 3.5 has somehow fouled up some user setting that leads to the browser (Firefox or Opera) malfunction reported above.
Comment 2 Timon Zielonka 2014-01-24 22:54:37 UTC 
In a fresh installation of Kubuntu 13.10 after installing Firefox and Thunderbird clicking on an URL in an email in Thunderbird still does not open the URL in Firefox. After setting in Firefox "Edit -> Preferences -> Advanced -> General -> Make Firefox the default browser" opening an URL from Thunderbird works. So the suggestion is with the installation of Firefox it is set to the default browser.
Comment 3 Andrew Crouthamel 2018-11-11 04:36:01 UTC 
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Maurice Batey 2018-11-11 11:40:27 UTC 
This problem seems to have disappeared in the meantime so - as far as I am concerned - it can be closed.
Comment 5 Maurice Batey 2018-11-11 11:41:54 UTC 
This problem seems to have disappeared in the meantime so - as far as I am concerned - it can be closed.
Comment 6 Andrew Crouthamel 2018-11-12 03:08:38 UTC 
Thanks for the update!