Bug 401978

Summary: Opening link redirect to login page
Product: [Frameworks and Libraries] frameworks-kio Reporter: jb.ducharme
Component: generalAssignee: David Faure <faure>
Status: RESOLVED FIXED    
Severity: normal CC: kdelibs-bugs, nate
Priority: NOR Keywords: triaged
Version: 5.53.0   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In: 5.54
Sentry Crash Report:
Attachments: Default web browser

Description jb.ducharme 2018-12-10 21:11:22 UTC
SUMMARY
I recently converted from gdm3 to kde on ubuntu 18.04 and the behavior of opening a link in the console has changed. It now redirects me to the login page instead of sending me to the correct page. 

I would assume the redirect engine tries to check if the link is valid before sending me, but since it's behind a mandatory login, it fails and sends me to the login page instead.

A little of context for the steps to reproduce : the bug occurs when I'm push a git branch to our internal gitlab and I then ctrl+click on the link to do a merge request.

STEPS TO REPRODUCE
1. modify file + commit
2. git push origin master
3. ctrl+click link

OBSERVED RESULT
Chrome opens a new tab, displaying my projects with a mention at the top "You are already logged in"


EXPECTED RESULT
Chrome opens a new tab showing the merge request


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 18.04
KDE Plasma Version: 5.12.6
KDE Frameworks Version: 5.44.0
Qt Version: 5.9.5

ADDITIONAL INFORMATION
The url looks like this https://gitlab.foobar.com/internal/foobar.com/merge_requests/1899

My coworkers can't reproduce the problem, which is why I think it's related to either konsole or kde. One is running Ubuntu 16.04 unity and the other 18.04 gdm3
Comment 1 jb.ducharme 2018-12-10 21:22:35 UTC
ADDITIONAL INFORMATION
I openned the link using gnome-terminal and it works perfectly. Only when I try to open the link throught Konsole do I get the bad behavior.
Comment 2 Nate Graham 2018-12-11 18:18:51 UTC
Cannot reproduce with Konsole 18.08, the upcoming 18.12, or git master.

Can you share a screenshot of what System Settings > Applications > Default Applications > Web Browser looks like on your system?
Comment 3 Bug Janitor Service 2018-12-26 03:44:18 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 jb.ducharme 2019-01-02 13:59:24 UTC
Created attachment 117237 [details]
Default web browser

Here is the requested screenshot
Comment 5 Nate Graham 2019-01-02 14:34:53 UTC
Two more questions for you:
1. What does `grep "x-scheme-handler/http" ~/.config/mimeapps.list` show?
2. Does the problem go away if you click on "In the following application" and make sure "Google Chrome" is selected?
Comment 6 jb.ducharme 2019-01-02 15:01:31 UTC
1. Here is the result

x-scheme-handler/http=google-chrome.desktop
x-scheme-handler/https=google-chrome.desktop

2. No the problem remains
Comment 7 Nate Graham 2019-01-02 15:03:18 UTC
For 2, did you remember to click Apply? If so, does the problem happen if you install Firefox and make it your default browser?
Comment 8 jb.ducharme 2019-01-02 15:09:28 UTC
Hot damn! It works just fine now. 

Thanks for your help!

I'm 98% certain that I had clicked apply the first time I tried the setting, but it wasn't checked. The default suggested application was firefox now ( it was already installed, so that hasn't changed ). I selected it again and now it works. I reloaded the settings to make sure it stuck this time.

Do you have any idea as to why it behaved like that? Just a curiousity on my part.
Comment 9 Nate Graham 2019-01-02 15:13:34 UTC
Yep. Due to a bug I just fixed. :)