Bug 269216

Summary: Akregator doesn't honor system wide default browser settings, but uses its own "external browsing" configuration
Product: [Applications] akregator Reporter: Sönke Hahn <shahn>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: wishlist CC: osterfeld
Priority: NOR    
Version: 1.6.5   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:

Description Sönke Hahn 2011-03-23 11:43:38 UTC 
Version:           1.6.5 (using KDE 4.6.1) 
OS:                Linux

You can globally configure which web browser you want to use in the kde system settings (section "Default Applications" -> "Web Browser"). Akregator doesn't care for that and has its own browser settings (called "External Browsing"). Akregator should use kde's global settings.

Reproducible: Always

Steps to Reproduce:
1. Set your global web browser setting to browser A via "System Settings" -> "Default Applications" -> "Web Browser"
2. Set your akregator browser to browser B via "Settings" -> "Browser" -> "External Browsing" -> "Use this command"
3. click a link in a feed entry. Browser B will be used.
Comment 1 Frank Osterfeld 2011-03-23 12:22:12 UTC 
Yes, that's because you configured a custom browser to be used. Then Akregator will of course do exactly that.
If you choose the default option "Use default web browser" it will use the default browser.
Comment 2 Sönke Hahn 2011-03-24 19:38:31 UTC 
(In reply to comment #1)
> Yes, that's because you configured a custom browser to be used. Then Akregator
> will of course do exactly that.

Yes, of course, my fault.

> If you choose the default option "Use default web browser" it will use the
> default browser.

It will do so on one of my computers. On the other, akregator chooses to open the link with arora, which is not my default browser. That was what I wanted to report :(. In the meantime I saw, that this is already reported. Will mark as duplicate.
Comment 3 Sönke Hahn 2011-03-24 19:39:09 UTC 

*** This bug has been marked as a duplicate of bug 238671 ***