Bug 195823

Summary: Cannot save file with same basename as directory when the autoappend extension is enabled
Product: [Unmaintained] kdelibs Reporter: Ben Boeckel <bugzilla.kde>
Component: generalAssignee: kdelibs bugs <kdelibs-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: normal CC: andresbajotierra, ralph
Priority: NOR    
Version First Reported In: 4.2   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Unspecified   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Ben Boeckel 2009-06-09 22:48:40 UTC
Version:            (using KDE 4.2.3)
Installed from:    Fedora RPMs

When trying to save a file with KFileDialog that auto-appends the extension, if the basename is the same as a directory, when trying to get the dialog to save the file, it instead opens the directory (either by the button or the keyboard). In order to save it, the extension must be manually applied.
Comment 1 Dario Andres 2009-06-10 21:06:41 UTC
Are you entering an absolute path (like "/home/user/file.txt") in the location textfield ?
Thanks
Comment 2 Ben Boeckel 2009-06-16 17:39:43 UTC
No, I'm navigating through using the GUI. Say it auto-saves .bar and I try and save it as "foo.bar". I navigate to a directory that has a folder named "foo". Since .bar is auto-appended, I type "foo". Trying to save it causes the foo directory to be opened.
Comment 3 Dario Andres 2009-06-20 21:14:53 UTC
Thanks
Comment 4 Ralph Müller-Welt 2009-11-13 00:40:21 UTC
Duplicate of this
https://bugs.kde.org/show_bug.cgi?id=213679
Comment 5 Ralph Müller-Welt 2010-01-04 14:59:12 UTC
*** Bug 213679 has been marked as a duplicate of this bug. ***
Comment 6 Andrew Crouthamel 2018-11-02 22:57:22 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 7 Andrew Crouthamel 2018-11-16 05:22:26 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?

Thank you for helping us make KDE software even better for everyone!
Comment 8 Justin Zobel 2022-12-08 23:51:27 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 9 Bug Janitor Service 2022-12-23 05:22:45 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 10 Bug Janitor Service 2023-01-07 05:25:31 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!