list of recently opened files is not updated in v0.48.4

[Dominik Lenné]

action:

open a file. work on it. close it. close inkscape. reopen it.

expected result:

file worked on appears in list of recently opened files.

actual result:

file does not appear on list.

XP Pro SP3

[Alvin Penner (apenner)]

- not reproduced on Windows 7, Inkscape 0.48.4
- could you indicate which version of Inkscape?
- when you close it, are you using the File->Close menu item, which also automatically shuts down Inkscape.
- do you at any time have multiple instances of Inkscape running, which will happen if you do a File->Open or a File->New

[Alvin Penner (apenner)]

- sorry, now I see the 48.4, I did not read the comment carefully enough.

[Dominik Lenné (dlenne-n)]

Hi,
I just tested it again:
> file > open does not open a second instance, there is no second inkscape process indicated in the task manager.
> file > close (ctr w) and > file > quit (ctr q) both close inkscape without writing the file name into the recently-used-list.

Normally I work with a nonadmin account for security reasons.
So I tested running inkscape as admin:

> start inkscape via "run as" with admin account > create file > save

results in appearing the filename immediately after the saving action, without closing the program. After restart as admin the list contains the new filename. So running as admin, everyting is o.k.

When I check

C:\Dokumente und Einstellungen\myname\Lokale Einstellungen\Anwendungsdaten\recently-used.xbel

I find every file I modified neatly listed. So Inkscape writes properly but somehow does not read the file, when not operating as admin.

I had installed inkscape of course as admin.

HTH

[Alvin Penner (apenner)]

yes, I think that makes sense. In my case, on Windows 7, I had installed it as a non-admin, and I also run it as a non-admin, and I have not encountered any problems. Of course, the downside is that my preferences file gets stored in an unusual location like:
C:\Users\username\AppData\Roaming\inkscape\preferences.xml

and I have a redundant, duplicated, directory with the name:
C:\Users\username\AppData\Local\VirtualStore\Program Files\Inkscape\share\extensions\

but neither of these things affects the operation of Inkscape, so I don't care. I think the conclusion is that, if you install as an admin, then you must also run as an admin, and similarly for non-admin. (But then, I know nothing about security, and care even less, so that's just my 2 cents worth.)

[Dominik Lenné (dlenne-n)]

Hmm, to install a program as admin and use it as normal user is common with those old windowses.
Inkscape writes the correct data at the correct place as it is supposed to.
Only it does not use those data.

[Alvin Penner (apenner)]

yes, you are right, it does seem very unusual that this location would not work properly. I have 2 installations:

on Windows 7, the recently-used.xbel file is at: C:\Users\username\AppData\Local\
and on Windows XP, this file is at:
C:\Documents and Settings\username\Local Settings\Application Data\
and this is working well on my XP machine.

I think this location is consistent with your location, and I don't understand why it does not work, since it is in a user directory, not a system directory.

[Alvin Penner (apenner)]

possibly a wild ques, but is there any chance that your username has an accented e in it, as in Lenné.
sometimes these non-ascii characters can cause a problem.

[jazzynico (jazzynico)]

Duplicate of Bug #629608 "Recent files menu does not list files with non-Latin filenames (Windows)"?

@Dominik, could you please confirm the bug shows only when you have non-ascii characters in the file path?

[Dominik Lenné (dlenne-n)]

I cannot confirm neither rule out this, as my file path has no non-ascii characters in it.

But I today installed version 0.91 r13725 and cannot reproduce the bug anymore, repeating the steps given in my first report.

So I guess t h i s bug has become obsolete.

[Dominik Lenné (dlenne-n)]

I don't know exactly to which status to change this bug now.

[jazzynico (jazzynico)]

Thanks for reporting back!
Setting the bug status "Invalid". Don't hesitate to reopen if you run into the same issue with a recent Inkscape version.