Bug 79255 - FILESAVE: "Save as" doesn't follow the file location
Summary: FILESAVE: "Save as" doesn't follow the file location
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
4.2.4.2 release
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2014-05-26 10:33 UTC by Alexander
Modified: 2018-11-08 14:07 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander 2014-05-26 10:33:17 UTC
Problem description: 

Steps to reproduce:
1. Open a file
2. Menu File -> Save As...
3. File save dialog is opened

Current behavior:
It offers me my home directory regardless the place where the file was opened from

Expected behavior:
It must offer me the location of the file being saved as
              
Operating System: Windows 8
Version: 4.2.4.2 release
Comment 1 Marina Latini (SUSE) 2014-05-26 11:05:07 UTC
Can't reproduce on GNU/Linux with LibreOffice installed with fresh user profile:

* Version: 4.2.4.2
* Build ID: 63150712c6d317d27ce2db16eb94c2f3d7b699f8

* Version: 4.3.0.0.beta1
* Build ID: 2e39c7e59c8fc8b16a54c3d981dceef27fb0c07f

* OS: Ubuntu 13.10 x86_64
with Italian helppack and langpack installed.
Comment 2 Kevin Suo 2014-05-27 01:43:17 UTC
I am sure I could reproduce this in ubuntu before, but now I could not find the steps. 
For the cases when I was able to reproduce, it seems that LibreOffice was offering the last used directory for "save as".
Comment 3 Alexander 2014-05-27 08:03:06 UTC
Hm... today tried it again with Impress, Writer and Calc - it worked correctly! I.e. they initially offered me the locations (different ones each time) where the files were opened from. 

Operating System: Windows 8
Version: 4.2.4.2 release
Comment 4 ign_christian 2014-06-10 04:29:00 UTC
I can't also reproduce with 4.0.6.2 (Win7 x86)
Perhaps that problem arise with particular LO setting / configuration. 

Change status to WFM temporarily, please reopen if you find exact ways to reproduce.