Bug 166158 - .ICEauthority problems can prevent KDE start, etc.
Summary: .ICEauthority problems can prevent KDE start, etc.
Status: RESOLVED UNMAINTAINED
Alias: None
Product: dcop
Classification: Frameworks and Libraries
Component: dcopserver (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
: 307403 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-07-09 18:48 UTC by David Baron
Modified: 2018-09-02 22:15 UTC (History)
10 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Baron 2008-07-09 18:48:44 UTC
Version:           unknown (using 4.00.85 (KDE 4.0.85 (KDE 4.1 >= 20080703)), Debian packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.23-rt1-davidb

Often enough, after normal KDE shutdown or control/back restart, .ICEauthority has been changed to root:root!!!
and the lock files may still be around as well.

1. KDE3 or KDE4 will now not start because it has no write-permission.
2. dcopserver, if needed, will not start, because of permissions or the lock files.
Comment 1 David Baron 2008-07-10 22:09:40 UTC
Since it would take a root privileged process to do this--the only culprit can be ksensors which is run sudo to get disk temperature measurements. Realizing this, I put a sleep before the sudo ksensors so that other older applets such as knemo, kalsamix or such would start dcop first. This had been OK, but ...

Since I cannot prevent kmix from coming up and I can get everything on its mixer pane as kalsamix, I am not starting that. knemo, apparently does not use dcop (in a way effect this). Kboincspy is for whatever reason not coming up usually and to start it manually after the ksensors, I have to change the permissions on the .ICEauthority. The dcopserver is running as root (and with root privileges does not really care about who owns .ICEauthority).

I wish KDE stuff would not change permissions of files. I had this before with kmail when trying to let another login look at my mail. If I set them wrong, this is my problem. If I set them sensibly, changing them is a bug which I cited a long time ago :)
Comment 2 Jordi Polo 2008-11-30 13:06:33 UTC
Move this to dcopserver. 
Comment 3 K.-Michael Aye 2009-01-05 16:06:54 UTC
I have this happening as well on Kubuntu 08.10.
It did appear before and after upgrade to KDE 4.2 beta (was hoping this bug was removed).
As well: A very clean close everything and reboot and the login manager comes with a 
No write access to '/home/user/.ICEauthority'

Comment 4 lamont 2009-01-07 06:19:58 UTC
I am having the same issue unable to access desktop. Tried changing permission to file with no success please notify me with a fix
Comment 5 xeno6696 2009-04-25 05:33:09 UTC
After upgrading today to 9.04 I have this issue but I have no clue how to fix it.  I'm pretty new to Linux/KDE and simply do not know what to do because I can't get into the gui and don't know enough about where permissions are stored.  I always change them by the right-click menu-->properties

The issue doesn't happen in the live cd.  The only resolution I can think of is to nuke my /home disk but uh... I got linux to skip doing crap like that.
Comment 6 martin.jkb 2009-05-09 22:47:56 UTC
I installed Kubuntu 9.04 right after the release in April 09.  No problems occurred until yesterday when I was playing around with Kdevelop (launched from the console via sudo Kdevelop). 

Of course, I also used the commands under the menu "build" (clean project and dist clean). Next time I could not start a kde session because of the above mentioned problem ("could not write to .ICEauthority" "could not start ksmserver. Check your installation"). 
 So I went to the console login and changed permissions of .ICAauthority via sudo chmod a+rw. After next reboot launching of kde was as usual. Strange enough, the file looks empty. 

Regards
Martin
Comment 7 Dieter Drewanz 2010-03-22 20:39:48 UTC
using sidux:  Nov 2009  Linux 2.6.31-6.slh.2-sidux-686 #1 SMP PREEMPT Sun Nov 15 13:56:52 UTC 2009 i686 GNU/Linux

last apt-get update March 2010
last apt-get upgrade End of February 2010
For two weeks was netbook not rebootet because of using pm_suspend.

Stopping at third dot displayed of five while starting kde. Kde does not start.
After 5 to 10 minutes a window pops up with following text:

The following installation problem was detected while trying to start KDE:
No write access to '/home/username/.ICEauthority'.
KDE is unable to start.
(button for pressing ok)

checked in a terminal with
ls -la
-rw------- 1 root root 0 Mar 10 00:58 .ICEauthority

button ok pressed
A window pops up:
Could not start ksmserver. Check your Installation.
button okay pressed

back to login-screen

How to solve:

Changed with midnight commander (chmod, chown, chusr)

-rw-rw-r-- 1 root users 0 Mar 10 00:58 /home/username/.ICEauthority
 
Now it works again. Strange - file did not change date.   

Another thing - when i stopped kde with "init 1" and in a root terminal i type "start x" kde hungs up with a screen for config of kde3 to kde4.
Comment 8 lamont 2010-03-23 05:01:22 UTC
good information thanks alot

On Mon, Mar 22, 2010 at 2:41 PM, Dieter Drewanz <dieterd2005@yahoo.com>wrote:

> https://bugs.kde.org/show_bug.cgi?id=166158
>
>
> Dieter Drewanz <dieterd2005@yahoo.com> changed:
>
>           What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>                 CC|                            |dieterd2005@yahoo.com
>
>
>
>
> --- Comment #7 from Dieter Drewanz <dieterd2005 yahoo com>  2010-03-22
> 20:39:48 ---
> using sidux:  Nov 2009  Linux 2.6.31-6.slh.2-sidux-686 #1 SMP PREEMPT Sun
> Nov
> 15 13:56:52 UTC 2009 i686 GNU/Linux
>
> last apt-get update March 2010
> last apt-get upgrade End of February 2010
> For two weeks was netbook not rebootet because of using pm_suspend.
>
> Stopping at third dot displayed of five while starting kde. Kde does not
> start.
> After 5 to 10 minutes a window pops up with following text:
>
> The following installation problem was detected while trying to start KDE:
> No write access to '/home/username/.ICEauthority'.
> KDE is unable to start.
> (button for pressing ok)
>
> checked in a terminal with
> ls -la
> -rw------- 1 root root 0 Mar 10 00:58 .ICEauthority
>
> button ok pressed
> A window pops up:
> Could not start ksmserver. Check your Installation.
> button okay pressed
>
> back to login-screen
>
> How to solve:
>
> Changed with midnight commander (chmod, chown, chusr)
>
> -rw-rw-r-- 1 root users 0 Mar 10 00:58 /home/username/.ICEauthority
>
> Now it works again. Strange - file did not change date.
>
> Another thing - when i stopped kde with "init 1" and in a root terminal i
> type
> "start x" kde hungs up with a screen for config of kde3 to kde4.
>
> --
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug.
>
Comment 9 Christoph Feck 2011-06-08 14:55:21 UTC
What is the status of this bug? Does it still happen with recent distributions and KDE versions? Who exactly is responsible for creating .ICEauthority?
Comment 10 David Baron 2011-06-08 22:58:12 UTC
On Wednesday 06 Sivan 5771 15:55:24 Christoph Feck wrote:
> https://bugs.kde.org/show_bug.cgi?id=166158
> 
> 
> Christoph Feck <christoph@maxiom.de> changed:
> 
>            What    |Removed                     |Added
> ---------------------------------------------------------------------------
> - CC|                            |christoph@maxiom.de
> 
> 
> 
> 
> --- Comment #9 from Christoph Feck <christoph maxiom de>  2011-06-08
> 14:55:21 --- What is the status of this bug? Does it still happen with
> recent distributions and KDE versions? Who exactly is responsible for
> creating .ICEauthority?

The .ICEauthority problem came from running a KDE3 utility as root. This was 
kensors displaying disk temperatures which required root privileges. Probably, 
the dcop did this.

I have stopped using this so no more problem. However, the principle remains.

My startkde scripts started out by resetting those permissions, at least for 
my loging since I am sudoer. This was a hack.
Comment 11 Christoph Feck 2012-09-25 19:48:54 UTC
*** Bug 307403 has been marked as a duplicate of this bug. ***
Comment 12 Andrew Crouthamel 2018-09-02 22:15:20 UTC
Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years and I will be closing this bug.