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 317766 - cannot create files with gnomevfs
cannot create files with gnomevfs
Status: RESOLVED FIXED
Product: libgsf
Classification: Core
Component: GNOME
1.12.x
Other Linux
: Normal normal
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2005-10-02 20:03 UTC by Sven Herzberg
Modified: 2005-10-03 19:43 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
patch (1.08 KB, patch)
2005-10-02 20:19 UTC, Sven Herzberg 		none Details | Review
path with fixed permissions (1.08 KB, patch)
2005-10-03 19:00 UTC, Sven Herzberg 		none Details | Review

Description Sven Herzberg 2005-10-02 20:03:45 UTC 
Version details: 1.12.3-3ubuntu1

take a recent criawips and try to save a presentation.

the GnomeVFS-error which comes from broken API usage is "File not found" (which
is normal when saving files to a new file).
Comment 1 Sven Herzberg 2005-10-02 20:19:34 UTC 
Created attachment 52945 [details] [review]
patch

please apply quickly, this breaks creating new files with libgsf since quite
some time
Comment 2 Sven Herzberg 2005-10-02 20:24:34 UTC 
the thing happens like this:

1. perms gets set to -1 initially
2. gnome_vfs_uri_exists() returns false, so perms will never be set to something
different
3. when the check for perms == -1 comes it enters the first block
4. it tries to open and not to create a file
Comment 3 Sven Herzberg 2005-10-03 19:00:07 UTC 
Created attachment 52994 [details] [review]
path with fixed permissions

this one sets correct permissions (0644) instead of still using -1
Comment 4 Sven Herzberg 2005-10-03 19:43:35 UTC 
2005-10-03  Sven Herzberg  <herzi@gnome-de.org>

        Got okay from Morten for this:

        * gsf-gnome/gsf-output-gnomevfs.c: create the file if necessary; fixes
        bug 317766