Bug 359054 - Save attachment: always offering /usr/bin
Summary: Save attachment: always offering /usr/bin
Status: RESOLVED FIXED
Alias: None
Product: kmail2
Classification: Applications
Component: UI (show other bugs)
Version: 5.1
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-06 09:40 UTC by Martin Kostolný
Modified: 2016-04-22 16:07 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.1.2
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Kostolný 2016-02-06 09:40:22 UTC
When saving attachment incorrect directory path (/usr/bin) is suggested and I always need to select the proper one (which is for me always the same). The side effect of this suggestion is loading unnecessarily big contents of /usr/bin directory.

Reproducible: Always

Steps to Reproduce:
1. Click on an attachment in mail
2. In dialog click "Save as..."

Actual Results:  
Suggested path is /usr/bin

Expected Results:  
Suggested path should be home folder or last folder I used for saving an attachment.

I used to suffer from this bug: https://bugs.kde.org/show_bug.cgi?id=357557
...where the result of suggesting path file://home/user/ was showing also /usr/bin contents. But after some time it is directly showed /usr/bin.

I also tried to test with clean config (empty home directory) and the first suggestion when saving attachment was a proper home directory one. But maybe after a restart it was back to /usr/bin. Even when I select a home directory to save attachment, then save it and then try to save it again -> /usr/bin is suggested again.

I have Plasma 5.5.4, KF 5.18, KDE Apps 15.12.1, Qt 5.5.1, (KMail 5.1.1)
Comment 1 Laurent Montel 2016-02-06 13:16:36 UTC
I confirm it.
I will fix it soon
Comment 2 Martin Kostolný 2016-02-06 14:59:41 UTC
That was fast, thanks a lot!
Comment 3 jat255 2016-04-22 16:07:26 UTC
As of KMail 5.1.3, this is still an issue for me when attaching a file or attempting to save an attachment. Did the fix perhaps get reverted somehow?