When i log out/in takes long time and file is not updated?
Have searched forum there is simular topics but no solution
I saw about the same error message just after login today (this did not happened before).
My ~/.ICEauthority is root-only (??)
This was while login on a Gnome destop.
It’s even worst when login on a KDE desktop:
- VERY slow login process
- Error message about write access to ICEauthority
- impossible to start KDE, and back to the login screen.
(The second error message was from the X server and said something like “cannot start kmsserver”.)
This is the second time I reboot the computer, and I still cannot login to a KDE desktop.
Should I manually change the permission for ~/.ICEauthority ?
I’ve had that problem with past versions and just always deleted or renamed the file from the command line or another window manager like icewm or xfce.
The file var/lib/gdm/.ICEauthority does not exist
Its just not there so system cant write to it login /out
How do i add a file named .ICEauthority to the map var/lib/gdm
Secondary questions what do this file do?
Why is the file not there?
Seems to be many people having this matter.
So i try making a file on desktop simply copy it in to var/lib/gdm map gets the answer the file already exist but i can not se it??
i was watching the systemmonitor and i found an usr/lib/polkit-gnome/polkit-gnome-authentication-agent-1 process running containing some like 3 totaly. /home/user/x session-errors
Dont know what that is but it was the only process with something like authority in it.
Yes, or better just get back the ownership of the file.
Ex.: (as root)
chown <YourUserID> /home/<YourUserID>/.ICEauthority
Are you sure the file is not there ? (remember that files starting with a dot are hidden by default in Nautilus/Dolphin.)
Try: (as root)
ls -l /var/lib/gdm
You should see:
-rw------- 1 gdm gdm 318 mai 5 2009 /var/lib/gdm/.ICEauthority
(if not, then there is really a problem there 
)
If you have it, do not touch it. I believe the problem you have is due to .ICEauthority in your home directory.
Try:
ls -l /home/<YourUserID>/.ICEauthority
Is the owner root ? Change it back to <YourUserID> (see my previous post).
After some investigation, I discover that this ownership problem with .ICEauthority can happen after a ‘su’ command and starting a KDE application as root.
‘su’ gives you the root priviledges, but the environment variables are still the ones of the user. So $HOME is the home directory as USER. Some KDE apps need to replace/overwrite the .ICEauthority file. Althought root, the file is created in the user home dir instead of the root home dir; and the file gets the root ownership.
A good habit is to use ‘su -’ (note the dash) instead of ‘su’, so that you get the root priviledges AND the root env. variables.
For more about .ICEauthority, try:
man iceauth
I was using the the GConf-cleaner and now problem only appears login .
Ok your first
chown <YourUserID> /home/<YourUserID>/.ICEauthority
i get operand after chown <YourUserID> /home/<YourUserID>/.ICEauthority is missing see chown --help for more info done that but i can not see any other operand so??
Second
ls -l /home/<YourUserID>/.ICEauthority
I get ls:can not get it -: does not exist
Third
ls -l /home/<YourUserID>/.ICEauthority
Permission denied ls:can not get it :-does not exist
So i was looking in the systemlog this looks weird is it that??
Nov 20 19:45:55 c-90f570d5 gnome-session [3617]: WARNING: Application ‘gnome-wm.desktop’ failed to register before timeout
Nov 20 19:46:01 c-90f570d5 pulseaudio [3915]: pid.c: Daemon already running.
Nov 20 19:46:52 c-90f570d5 gnomesu-pam-backend: The gnome keyring socket is not owned with the same credentials as the user login: / tmp / keyring-aZuhwm / socket
Nov 20 19:46:52 c-90f570d5 gnomesu-pam-backend: gkr-pam: could not unlock ‘login’ keyring: 255
Nov 20 19:46:52 c-90f570d5 gnomesu-pam-backend: pam_env (gnomesu-pam: setcred): non-alphanumeric key ‘alias = padsp aumix aumix’ in / etc / environment ', ignoring
Nov 20 19:46:52 c-90f570d5 gnomesu-pam-backend: pam_env (gnomesu-pam: setcred): non-alphanumeric key ‘alias = padsp sox sox’ in / etc / environment ', ignoring
Nov 20 19:46:52 c-90f570d5 gnomesu-pam-backend: pam_env (gnomesu-pam: setcred): non-alphanumeric key ‘alias = timidity timidity-Oe’ in / etc / environment ', ignoring
Nov 20 19:47:37 c-90f570d5 seahorse-agent [3693]: GConf error: # 012 Failed to contact configuration server. Some possible reasons may be that you need to enable support for TCP / IP network in ORBit, or you have leftover NFS locks due to a system crash. See GConf configuration system for more information. (Details - 1: Failed to send message to the GConf daemon: Connection is closed)
Nov 20 19:47:37 c-90f570d5 seahorse-agent [3693]: GConf error: # 012 Failed to contact configuration server. Some possible reasons may be that you need to enable support for TCP / IP network in ORBit, or you have leftover NFS locks due to a system crash. See GConf configuration system for more information. (Details - 1: Failed to send message to the GConf daemon: Connection is closed)
FROM TODAY
Nov 21 21:17:00 c-11ff70d5 gnome-session[2031]: WARNING: Application ‘metacity.desktop’ failed to register before timeout
Nov 21 21:17:00 c-11ff70d5 gdm-simple-greeter[3434]: GLib-GObject-CRITICAL: g_param_spec_flags: assertion G_TYPE_IS_FLAGS (flags_type)' failed Nov 21 21:17:00 c-11ff70d5 gdm-simple-greeter[3434]: GLib-GObject-CRITICAL: g_object_class_install_property: assertion G_IS_PARAM_SPEC (pspec)’ failed
Nov 21 21:17:00 c-11ff70d5 pulseaudio[3442]: core-util.c: Home directory /var/lib/gdm not ours.
Nov 21 21:17:00 c-11ff70d5 pulseaudio[3442]: lock-autospawn.c: Cannot access autospawn lock.
Nov 21 21:17:00 c-11ff70d5 pulseaudio[3442]: main.c: Failed to acquire autospawn lock
Nov 21 21:17:00 c-11ff70d5 gdm-simple-greeter[3434]: WARNING: Unable to parse history: (null) 37#012
Nov 21 21:17:05 c-11ff70d5 gdm-session-worker[3439]: pam_env(gdm:setcred): non-alphanumeric key ‘alias aumix=padsp aumix’ in /etc/environment’, ignoring
Nov 21 21:17:05 c-11ff70d5 gdm-session-worker[3439]: pam_env(gdm:setcred): non-alphanumeric key ‘alias sox=padsp sox’ in /etc/environment’, ignoring
Nov 21 21:17:05 c-11ff70d5 gdm-session-worker[3439]: pam_env(gdm:setcred): non-alphanumeric key ‘alias timidity=timidity -Oe’ in /etc/environment’, ignoring
Nov 21 21:17:06 c-11ff70d5 checkproc: checkproc: can not get session id for process 3490!
Nov 21 21:17:06 c-11ff70d5 seahorse-agent[3558]: seahorse_agent_cache_init: assertion `GPG_IS_OK (err)’ failed
Nov 21 21:17:07 c-11ff70d5 gnome-session[3483]: WARNING: Could not parse desktop file /etc/xdg/autostart/ksmolt-autostart.desktop: Ogiltigt nyckelnamn: X-KDE-autostart-condition$e]
Nov 21 21:17:07 c-11ff70d5 gnome-session[3483]: WARNING: could not read /etc/xdg/autostart/ksmolt-autostart.desktop
Erm, just to be sure…
You have to replace the <YourUserID> by your real user id, the one you use when you login to the system.
Also, you have to run the chown command as root, otherwise you won’t be able to change the ownership of a file where the owner is root.
So first:
su (and enter the root password when prompted)
then (let’s say your user id is loggern):
chown loggern /home/loggern/.ICEauthority
finally:
exit (to return back to the normal user session)
If the file does really not exist in your home directory, that’s not a big problem. It will be recreated anyway after a successful login.
Same command again ? This time with a different result ??
If you meant to write:
ls -l /var/lib/gdm/.ICEauthority
then the “Permission denied” you got is because THAT .ICEauthority file is own (normally) by gdm, and you don’t have ran the ls command as root (as explained above).
This log is too technical for me, I can’t help here.
Can you check this:
env | grep ^HOME
If you get:
HOME=/var/lib/gdm
instead of:
HOME=/home/<YourUserID>
then you are really in a bad situation, as your installation is more in a mess than I thought.
HOME=/home/myuser i get then im trying with options here i still get the operand is missing when im trying to change owner here
chown user/home/user --from/.ICEauthority then i get the unknown flag for example and yes i am using my acc name where user is.
:\
Sorry second was ls -l /var/lib/gdm thats why the different result
chown user /.ICEauthority/root Then i get chown can not get “/.ICEauthority/root”: the file does not exist
and it seems not to be recreated because the error appers every time i login…
how can i add a gedit file named .ICEauthority in /var/lib/gdm map ??
:\
So I guess your user login ID is “myuser”. Am I right ?
If so, the right command should be (AS ROOT !):
chown myuser /home/myuser/.ICEauthority
If there are no errors, then reboot the computer.
??
No offence intended, but are you new to Linux ? Most of what you wrote is incoherent to me. Maybe it’s a language problem ? (English is not my native language either. I can try to help with French…)
First, the leading “/” is important. It makes the path to the file an ABSOLUTE one from the root directory (not to be confused with the root home dir.). Without it, the path is RELATIVE to $HOME. That is, if you try to chown user/home/user (as root), you are in fact trying to change the ownership of a file /root/user/home/user which does not exist (or /home/myuser/user/home/user if you sent the command as normal user).
Second, why the leading user/ ? Do you have any reason to have prepended it ?
Third, why the trailing user ? Do you have any “user” account on the system ?
(Please separate the command line from the comment, it helps to better read what you were trying to do.)
“chown user /.ICEautority/root” does not make any sense to me. What were you trying to do ?
You can create an empty file from Nautilus (Gnome) or from Dolphin (KDE). But that won’t help !
.ICEauthority in var/lib/gdm is created by the system ONLY !
with
chown user/.ICEauthority/root
i am trying to chance the ownership of the file
.ICEauthority
Because the way you where showing me (operand was missing)
This might be because my system was wrecked.
So i tried the repair system konsole on the dvd an it found the
/var/lib/rpm/filemd5s
to be missing,some modules from the
/etc/sysconfig/kernel
where missing to.
Wasnt able to login after the repair ,so i did a clean install.
But thank you for taking time (sorry for bad english)and we got a bit on the way there.Maybe nexttime ower knowledge is bigger and we will solve this matter…
THX
user=my account name it is not really important for you is it?
No, I don’t need to know it.
After reading what you wrote again, I think the misunderstanding comes from the fact that you forgot a space between arguments for the chown command.
The syntax should be:
chown user /home/user/.ICEauthority
(Note the spaces between “chown” and “user”, and between “user” and “/home/user/.ICEauthority”)
Yes it might have been so and i will think of the space when i need to use
chown
for some reason. I think the problem is from my install of the latest ATI driver here are some serius problems with opensuse.
In ubuntu you just download the latest driver from ATI homepage.
and
chmod +x ati-driver-installer-9-10-x86.x86_64.run
sudo sh ./ati-driver-installer-9-10-x86.x86_64.run
sudo aticonfig --initial --input=/etc/X11/xorg.conf
And you are done!!!
But in suse there is howtos all ower but not 1 is working!!
That is a big problem i think this was my case here i had the fglrx driver installed the wrong way for some reason.I have been trying with KDE 3 times this day but its even worse then Gnome.
I am back on gnome and i will not try for the fglrx because the xrandr works fine for my desktop i will stick to that for the time.
Again was fun here on this topic thx for taking time cheers
I have the same problem. And I’ve solved it with:
chown gdm:gdm -R /var/lib/gdm
.
I think the root:root owner of /var/lib/gdm is prevent gdm update .ICEauthority. When i changed it never show the message to me. Sorry my bad english, vietnamese is my native.