Bug 16404 - Creating new folding before saving a download file, renames the file
Summary: Creating new folding before saving a download file, renames the file
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: i586 Linux
Priority: Normal minor
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-18 10:42 CEST by Koos Uys
Modified: 2016-04-24 19:39 CEST (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Koos Uys 2015-07-18 10:42:31 CEST
Description of problem:

When one needs to save a file downloaded from a web browser and wants to create a new folder, the file name for some reason is changed to - it seems like - the last file that was saved in a previous download.


Version-Release number of selected component (if applicable):


How reproducible:

Works every time.

Steps to Reproduce:
1. Select any file to download.
2. The dialog should open now.
3. Check the file name
3. Navigate to any folder and create a new folding within that folder.
4. Go to the new folder.
5. You will now see the file name have changed, postfix included.


Reproducible: 

Steps to Reproduce:
Comment 1 Rémi Verschelde 2015-07-18 10:46:15 CEST
With which browser(s) and desktop environment(s) do you experience this issue?

Component: Release (media or process) => RPM Packages

Comment 2 Koos Uys 2015-07-18 11:12:22 CEST
Using KDE and Chrome and...

I just tried to reproduce on Chrome and other browsers but no luck. That after lived with quirk since Mageia 3 and it did not bother me too much. :)

I did an update this morning though. Don't know if that fixed it by chance.
Comment 3 Marja Van Waes 2016-04-24 19:39:56 CEST
(In reply to Koos Uys from comment #2)
> Using KDE and Chrome and...
> 
> I just tried to reproduce on Chrome and other browsers but no luck. That
> after lived with quirk since Mageia 3 and it did not bother me too much. :)
> 
> I did an update this morning though. Don't know if that fixed it by chance.

Closing as fixed, then. Feel free to reopen if needed.

Status: NEW => RESOLVED
CC: (none) => marja11
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.