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 553505 - gnome-vfs should work if user has no writable $HOME directory
gnome-vfs should work if user has no writable $HOME directory
Status: RESOLVED FIXED
Product: gnome-vfs
Classification: Deprecated
Component: Other
2.24.x
Other All
: Normal normal
: ---
Assigned To: gnome-vfs maintainers
gnome-vfs maintainers
Depends on:
Blocks:
 
 
Reported: 2008-09-24 02:08 UTC by Brian Cameron
Modified: 2010-05-13 04:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24

Attachments
patch fixing problem (651 bytes, patch)
2008-09-24 02:09 UTC, Brian Cameron 		none Details | Review
updated patch (651 bytes, patch)
2008-10-22 07:45 UTC, Brian Cameron 		none Details | Review

Description Brian Cameron 2008-09-24 02:08:58 UTC 
A recent change in gnome-vfs enforces that the user have a writable $HOME directory.  However, this causes problems for running programs like GOK from GDM if the "gdm" user doesn't have a writable $HOME directory. 

The attached patch to check if the user has a writable $HOME directory, and avoid creating the directory if it is not writable seems to fix GOK so it runs okay from GDM.  Can this go upstream?
Comment 1 Brian Cameron 2008-09-24 02:09:20 UTC 
Created attachment 119268 [details] [review]
patch fixing problem
Comment 2 Brian Cameron 2008-10-22 07:45:32 UTC 
Created attachment 121092 [details] [review]
updated patch


After doing additional testing, I found that I reversed the if-test in the first patch and it didn't work properly.  Here is a correct patch that does work.

Can this go upstream?
Comment 3 Brian Cameron 2010-05-03 18:10:57 UTC 
This seems a straightforward patch?  Can it go upstream?
Comment 4 Brian Cameron 2010-05-13 04:03:26 UTC 
Fixed in master.