[Bug 14357] gnome-session: unable to launch gnome due to bad group/owner on .ICEauthority

bugzilla-daemon at bugzilla.ubuntu.com bugzilla-daemon at bugzilla.ubuntu.com
Thu Sep 22 22:24:56 UTC 2005


Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=14357
Ubuntu | gnome-session





------- Additional Comments From debzilla at ubuntu.com  2005-09-22 23:24 UTC -------
Message-ID: <431454FA.2020106 at wanadoo.fr>
Date: Tue, 30 Aug 2005 14:45:46 +0200
From: Olivier Schwander <olivier.schwander at wanadoo.fr>
To: 325701 at bugs.debian.org
Subject: Re: Bug#325701: gnome-session: unable to launch gnome due to bad
	group/owner on .ICEauthority

Josselin Mouette a =E9crit :
> Le mardi 30 ao=FBt 2005 =E0 08:54 -0300, Gustavo Noronha Silva a =E9cri=
t :
>=20
>>Em Ter, 2005-08-30 =E0s 11:38 +0200, Olivier Schwander escreveu:
>>
>>>          ** (gnome-session:7151): WARNING **: Unable to read ICE auth=
ority
>>>file: /home/olivier/.ICEauthority
>>>
>>>A solution is to change owner/group of the file .ICEauthority from roo=
t:root
>>>to username:username.
>>>
>>>I think it is a problem in the preinst script.
>>
>>preinst scripts are not supposed to mess up with your home directory;
>>how did that .ICEauthority arrive at your home directory in the first
>>place?
>>
>>I bet it is not a problem in gnome-session, but some other thing that
>>messed up by writing that file there. Any ideas?
>=20
>=20
> It could be some GNOME program run as root with HOME=3D/home/olivier.

The problem appeared after an upgrade of gnome-session and a logout. But
  only one user is concerned: an .ICEauthority used by an other user
only with kde has a good owner.
I may have used Synaptic as root but I don't understand how it could
have bad $HOME. I tried with su and gksu but owner is preserved.
I know that I have not forced HOME=3D/home/olivier.






-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.




More information about the desktop-bugs mailing list