After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 151639 - ctrl + s (saving) gives error messages and sometimes crashes the program
ctrl + s (saving) gives error messages and sometimes crashes the program
Status: RESOLVED DUPLICATE of bug 131210
Product: dia
Classification: Other
Component: win32
0.94
Other Windows
: Urgent critical
: ---
Assigned To: Steffen Macke
Dia maintainers
Depends on:
Blocks:
 
 
Reported: 2004-09-01 19:29 UTC by aggro
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description aggro 2004-09-01 19:29:53 UTC
This happened with Dia 0.94 on Windows 2000, SP4 Finnish version.

Create a .dia file. Move it into a folder which has character 'ä' in it's name,
now open it and press ctrl + s to save it, error messages appear.

Error messages come in pair, and they look like this:

"Failed to save file 'D:\fileä\Diagram1.dia'"

And
"Can't open output file D:\fileä\__diaa01288: No such file or directory"

The problem disappears if I rename the fileä folder to file, without the 'ä'
characters.

Once, after the error messages when I was closing the program, it crashed, don't
know if is related to this issue, because I couldn't repeat the crash, but I got
the error message from the crash, from the console, it looked like this:
---------------------------------
(dia.exe:480): GLib-GObject-CRITICAL **: file gobject.c: line 1579 (g_object_unr
ef): assertion `G_IS_OBJECT (object)' failed
---------------------------------

There is a workaround for the error messages, just only use folders that don't
have 'ä' in their name, but that really makes things hard, because Finnish
version of Windows has a folder called "Työpöytä" instead of the English
"Desktop". So basicly you can't work directly on your desktop which I like to do.

Please check that ä, ö and å and capital versions of them also work, since those
are also commonly used here were I live. Other non a-z characters might have the
same problem also. And also please look the crash error message, because it
might not have anything to do with this problem.
Comment 1 Steffen Macke 2004-09-01 19:55:51 UTC
What is the exact character? Could you give it's Unicode value (e.g. 
using the character map) 
 
Is it the space character? 
Comment 2 aggro 2004-09-01 20:29:07 UTC
ISO 8859-1:
http://encyclopedia.thefreedictionary.com/ISO%208859-1 

From that page you can find the character I mean, it is at place 0xE4 ( If you
don't know what that means, the example shows that character 'L' is at 0x4C )

I hope I answered the question, I'm not complitely familiar with characters maps
and unicode values.
Comment 3 aggro 2004-09-01 20:40:03 UTC
In previous post I just told what character I am talking about, but the
character map I might be using, could be Windows-1252 (CP1252), which seems to
be Windows default. But I'm not actually sure is it ISO 8859-1, or CP1252. The
character I'm talking about is at the same place in both of those character maps.

I took a little time, and studied this unicode, and the unicode value for that
character seems to be 00E4, found from here:
http://www.unicode.org/charts/PDF/U0080.pdf
Comment 4 Steffen Macke 2004-09-02 15:48:05 UTC
I have problems reproducing the bug. 
On windows (dia 0.94), the open/save dialog doesn't show 
folders containing the 0xe4 (ä - in German you can also write ae 
for it). How did you open the file? 
I was also unable to open a dia file copied to such a folder. 
On Linux, folder using this letter simply work. 
Comment 5 aggro 2004-09-02 18:48:09 UTC
> How did you open the file? 

I used the Windows Explorer to view the folder where the file was, then I just
double clicked it to open it. Tried now, and I was able to use File -> Open from
the menu to open file in folder containing the 0xE4. For me, it showed that
folder also in the dialog.

But if you are unable to even open the file, I assume that only verifies that
there is something wrong with such characters.
Comment 6 Hans Breuer 2004-11-07 10:06:06 UTC

*** This bug has been marked as a duplicate of 131210 ***