The export tool not remember the export path/filename

Please add information about OS/platform and Inkscape version (see Inkscape menu 'Help > About Inkscape') to the bug description.

In case you use Inkscape on Windows, please also provide details about the installer used (32bit|64bit, exe|msi|7z|paf.exe).

To allow further investigation of the reported problem, it would be helpful if you could also attach a test case (an Inkscape SVG file created with the previous version of Inkscape (presumeably 0.48.5)), and provide a detailed list of steps to reproduce based on the attached test case.

My distribution is xubuntu 14.04
The Inkscape version is 0.91

- reproduced on Windows 7, Inkscape 0.91 r13725 (Jan 30 2015), 32 bit installed from .exe
- reproduced on Windows XP, Inkscape 0.91+devel r13919 (Feb 13 2015)

- start Inkscape, draw obect
- click on File->EXport PNG
- note that the export path is C:\Users\username\ as expected
- click on Export As, and navigate to the folder C:\Windows\Temp\
- click on Export and confirm that the png file was actually saved to this location
- close Inkscape and reopen Inkscape
- note that the Export PNG dialog shows the folder C:\Users\username\, the same as it did initially

in both cases the pathname in the saved preferences file appears to be empty, section attached here:

    <group
       id="export"
       default=""
       append_extension="1"
       path=""
       x="507"
       y="0"
       w="348"
       h="397"
       panel_size="1"
       panel_ratio="100"
       panel_mode="1"
       panel_wrap="0"
       panel_border="0"
       visible="0"
       state="1"
       placement="1">
      <group
         id="exportarea"
         value="drawing" />
      <group
         id="defaultxdpi"
         value="114.4" />
    </group>

Possibly the same as already tracked in:
- Bug #1153829 “Export selection - won't remember last used file name.”
  https://bugs.launchpad.net/inkscape/+bug/1153829

On 2015-02-15 22:53 (+0100), Alvin Penner wrote:
> in both cases the pathname in the saved preferences file appears to be
> empty, section attached here:

To the best of my knowledge, the export path and file name is stored in the export hints inside the SVG file, not in the global preferences?

I have been able to confirm that the dpi is stored in the svg file, as part of the path element, excerpt shown below. This same information is also stored in the preferences file. However I can't find any reference to the save path, either in the file or in the preferences.

.......................................

    <path
       style="color:#000000;display:inline;overflow:visible;visibility:visible;fill:none;fill-rule:evenodd;stroke:#000000;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1;marker:none;marker-start:none;marker-mid:none;marker-end:none;enable-background:accumulate"
       d="M 137.14286,300.93363 305.71429,178.07649"
       id="path3336"
       inkscape:connector-curvature="0"
       inkscape:export-xdpi="114.4"
       inkscape:export-ydpi="114.4" />

That's right, the export path belongs to the SVG file. I have hundreds of svg files with its own export customs settings. This error exists only since the last version 0.91 and affects all my files

I can also add that this happens with open svg document. With the previous version, saving the path worked live, if hiding a layer with the exported object, and then was returning to show the saved path was there. But now with version 0.91 so not true, because if hidden layer with the exported object, and again show the pre-existing path reappears despite having been replaced.

In which details does this report differ from bug #1153829? (see comment #5)

I have studied bug # 1153829 and apparently is the same case. The only difference between my case and the case mentioned in bug # 1153829 is that my files already had their export svg path previously saved which i can not replace more, but represents the same problem. So tell me, how I should proceed with this report?

Status changed to 'Confirmed' because the bug affects multiple users.

Hum please importance should raise from low ;)

Thanks. This bug affects production environments and is very annoying.

Linking as duplicate to bug #1153829 - the regression AFAICT effects both
a) objects which had not been exported before (no export hints stored at all),as well as
b) objects which already have an export-filename stored (which does not get updated as expected with 0.91)

Feel free to add a comment here (bug #1422131) and to revert the duplicate status if you disagree.