Bug 167526 - Right click on an image and "save image as..." shouldn't start KGet.
Summary: Right click on an image and "save image as..." shouldn't start KGet.
Status: RESOLVED NOT A BUG
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: 4.0.98
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-27 11:49 UTC by Peter Lewis
Modified: 2011-12-29 06:50 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Lewis 2008-07-27 11:49:59 UTC 
Version:           4.00.98 (using KDE 4.0.98)
Installed from:    Ubuntu Packages

In Konqueror (web-browsing mode), right clicking an image and selecting "save image as..." opens a file dialog box to select where to save to. So far, so good. But once the location to save to has been selected, KGet is started and it saves it to KGet's default location (and using the image's original name) regardless of what was entered in the "save image as..." dialog box.

Note that there's already a "download using KGet" option in the right-mouse-button context menu, so using KGet for "save image as..." is not required.

Thanks.
Comment 1 Paul Eggleton 2008-08-02 17:45:30 UTC 
Possibly related to (or same issue as) bug 157543
Comment 2 Peter Lewis 2008-08-04 12:12:30 UTC 
I agree - seems to be related at least if not a dupe.
Comment 3 FiNeX 2010-08-23 22:56:09 UTC 
still valid: the "action->download with kget" is visible even if the kget/konqui integration is enabled (moreover "action->download with kget" save the file with a wrong file name).
Comment 4 Dawit Alemayehu 2011-12-29 06:50:04 UTC 
Disable konqueror integration in KGet and that won't happen. The action "download with kget" is simply a service menu that is provided with KGet and does not require the konqueror integration to be activated in KGet for it to work. The problem with the service menu is dealt with in bug# 157543 so I won't repeat it here.