Bug 310698 - attempting to open remote archive / tar embedded in konqueror fails
Summary: attempting to open remote archive / tar embedded in konqueror fails
Status: RESOLVED WORKSFORME
Alias: None
Product: konqueror
Classification: Applications
Component: konq-e (show other bugs)
Version: 4.9.3
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror/Embedded Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-26 09:49 UTC by Diggory Hardy
Modified: 2023-01-20 05:09 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Diggory Hardy 2012-11-26 09:49:22 UTC
By default, using konqueror as a web-browser downloads and opens remote archives in ark. Because konqueror can handle archives better than ark (which is buggy and AFAIK unmaintained) I'm trying to use konqueror instead. With local archives they open fine in konqueror, but not with remote ones. The following is what happens with Ark uninstalled and konqueror set to handle archives in the KDE file associations.

Reproducible: Always

Actual Results:  
Clicking an archive link or pasting the remote URL (any http URL for example) brings up a box asking whether to save or open (this can be skipped by changing associated setting in file associations, but that's not important).

The action on clicking 'open' depends on whether konqueror is associated with the file type or no application is (in which case an app selector is shown). In either case, choosing to open with konqueror only brings up another copy of the same dialog box. In certain configurations (when no application is associated with the file type and ...) this box is also shown when pressing escape/close and the only way to escape the endless boxes is to kill konqueror.

Expected Results:  
What I'd like to happen is that konqueror would open remote archives directly (downloading a temporary copy or not). I have a feeling some hard-coded behaviour is preventing this.
Comment 1 Andrew Crouthamel 2018-11-09 00:57:44 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 2 Andrew Crouthamel 2018-11-18 03:33:04 UTC
Dear Bug Submitter,

This is a reminder that 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? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Justin Zobel 2022-12-21 23:58:22 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 4 Bug Janitor Service 2023-01-05 05:26:07 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 5 Bug Janitor Service 2023-01-20 05:09:20 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now 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

Thank you for helping us make KDE software even better for everyone!