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 531566 - gnome-settings-daemon should work with unwritable user home directory
gnome-settings-daemon should work with unwritable user home directory
Status: RESOLVED DUPLICATE of bug 530975
Product: gnome-settings-daemon
Classification: Core
Component: general
2.22.x
Other All
: Normal enhancement
: ---
Assigned To: gnome-settings-daemon-maint
gnome-settings-daemon-maint
Depends on:
Blocks:
 
 
Reported: 2008-05-05 15:15 UTC by Xiurong Simon Zheng
Modified: 2008-05-05 15:29 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement


Attachments
A workaround to override home directory (4.04 KB, patch)
2008-05-05 15:25 UTC, Xiurong Simon Zheng
none Details | Review

Description Xiurong Simon Zheng 2008-05-05 15:15:23 UTC
In some cases, user home directory is possibly not writable.
- GDM login screen on Solaris is run by "gdm" account. Because of security by default on Solaris, his home directory is set as unwritable "/".
- When you install from CD, home directory is perhaps read-only.

But gnome-settings-daemon alwasys try to create ".gnome2" under user home directory. Also, some plugin like font-manager, sound, xrdb-manager will try to create its configuration file under "$HOME/.gnome2".

Would be better to let gnome-settings-daemon work correctly even if home directory isn't writable.
Comment 1 Michael Chudobiak 2008-05-05 15:17:30 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 530975 ***
Comment 2 Xiurong Simon Zheng 2008-05-05 15:25:29 UTC
Created attachment 110410 [details] [review]
A workaround to override home directory
Comment 3 Michael Chudobiak 2008-05-05 15:29:24 UTC
Please attach your patch to the original open bug, bug 530975.

- Mike