I doubt we will change the message for dapper, that's a detail and not
really worth breaking the string freeze. Feel free to open a bug
upstream and a new launchpad bug pointing to it though
--
GDM cannot write to authorisation file
https://launchpad.net/bugs/33132
--
desktop-bugs mailing list
d
Ideally, there should be two different messages for either the user's home
drive permissions, or the .dmrc file permissions.
For Dapper, can that message be changed to
"Either your home directory or the .dmrc file (a hidden file) in it is set to
be writable by other users. This is insecure. T
if you want a setting for that better to open an another bug (better if
upstream since that's the right place), that's not the same issue
what is not verbose enough about the warning? It explains the possible reasons
for that dialog clearly ...
--
GDM cannot write to authorisation file
https:/
If someone choses to make their home folder writable to another user, shouldn't
there be a way to dissable this warning?
Should the warning be a little bit more verbose, too? It kills two birds with
one stone and leads one to beleive that the system is broken.
--
GDM cannot write to authorisa
closing the bug, that's not a gdm issue but user or an another
application changing the permission. Feel free to reopen if you get the
issue again and figure how gdmrc gets the wrong permission
** Changed in: gdm (Ubuntu)
Status: Needs Info => Rejected
--
GDM cannot write to authorisation
I changed the permissions of my home directory so that groups could not have
write access and the problem went away.
Possibly, my young kids may have clicked around and changed the permissions of
folders. The error message is however cryptic and not intuitive.
"User's $HOME directory must be o
I get this:
User's $HOME /.dmrc file is being ignored. This prevents the default session
and language from being saved. Fle should be owned by user and have 644
permissions. User's $HOME directory must be owned by user and not writable by
other users"
I tried installing childsplay and gcompris
Ok, that might have been the wrong transcript above:
"GDM could not write to your authorisation file. THis could mean you are out of
disk space or that your home directory could not be opened for writing. In any
case it is not possible to login. Please contact your system administrator."
Now th
I no longer have the problem, but the exact wording is still on a piece of
paper here on my desk ;)
"User's $HOME /.dmrc file is being ignored. This prevents the default session
and language from being saved. Fle should be owned by user and have 644
permissions. User's $HOME directory must be
Andrew, Melissa what message do you get exactly?
--
GDM cannot write to authorisation file
https://launchpad.net/malone/bugs/33132
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Running flight 6, I just started getting this. I think the last few things I
did was to install childsplay and gcompris. I also set up gdm to autologin my
user at boot.
drwxrwxrwx 3 root root 4096 2006-03-29 14:06 home
[EMAIL PROTECTED]:~$ ls -l /home
total 4
drwxrwxr-- 22 emma emma 4096
11 matches
Mail list logo
