Bug 425713 - "Open http/https URLs based on content" still using old settings
Summary: "Open http/https URLs based on content" still using old settings
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (other bugs)
Version First Reported In: 5.19.4
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-08-23 14:27 UTC by kde
Modified: 2020-12-25 11:55 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kde 2020-08-23 14:27:36 UTC
I made this post in the forums a while ago
https://forum.kde.org/viewtopic.php?f=289&t=167118

Apparently the new behavior of always opening the browser is intentional:
https://bugs.kde.org/show_bug.cgi?id=423401

I had set it to open links based on content before, but now there is no way to remove that setting.

It seems that plasmashell is still following the old configuration, despite it not being configurable anymore.

1. How can I remove this config so it opens links in the browser, as is the new default?
2. I think plasmashell should ignore this config if someone had it set before, since the user can't change it from System Settings anymore.


SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20200819
KDE Plasma Version: 5.19.4
KDE Frameworks Version: 5.73.0
Qt Version: 5.15.0
Kernel Version: 5.8.0-1-default
OS Type: 64-bit
Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: Radeon RX 570 Series
Comment 1 kde 2020-12-25 11:55:45 UTC
I fixed it by editing ~/.config/kdeglobals

old:
BrowserApplication[$d]

new:
BrowserApplication=firefox.desktop

The "[$d]" is probably the deprecated "open based on contentes" logic that still lingered in the config after an update.

It can also be fixed by changing the browser in Systemsettings and then changing it back, so it forces a config file write.

I'm not sure how KDE should deal with deprecated settings lingering in config files, so I'll mark it as resolved but ask Nate for his opinion, since he also responded to the other bug.