Bug 344649

Summary:	Clicking link to open external browser opens browser, but fails to load link
Product:	[Applications] akregator	Reporter:	melanes <kadjette>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description melanes 2015-02-28 03:56:26 UTC

When viewing the chosen article in the preview pane, right clicking on the "Complete Story" link, and selecting "Open Link in External Browser," the browser opens but fails to load the link in the browser. Instead a new browser window opens to my default home page with no further action. The same behavior occurs when right clicking on the article title and selecting "Open Link in External Browser". Same results from multiple articles.

My default browser is Firefox. I wonder if a recent Firefox update broke this functionality.

Clicking on the link and opening the article in the internal browser appears to work for most articles.

Reproducible: Always

Steps to Reproduce:
1. Right click on "Complete story" link on article preview or Right click on article title
2. Select "Open in External Browser"
3.

Actual Results:  
Akregator opens default browser to default home page but does not pass the link to the browser. A new browser window is opened at each attempt. An already open browser is ignored.

Expected Results:  
Akregator should pass the link to the browser in a new tab if the browser is already open or open a new browser window and load the link.

Firefox version 36.0
Akregator 4.13.3
Xubuntu 14.04 (trusty)
Kernel 3.13.0-46-generic

Comment 1 Denis Kurz 2016-09-24 19:45:32 UTC

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of akregator (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.

Comment 2 Denis Kurz 2017-01-07 22:32:49 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.