This situation existed long before my recently-reported system clobbering.
[root@small ron]# kpackage
_KDE_IceTransmkdir: Owner of /tmp/.ICE-unix should be set to root
DCOPServer up and running.
kio (KService*): WARNING: Invalid Service : Networking/WWW/Mozilla.mail.desktop
error stat'ing fd 3: Bad file descriptor
[here kpackage was exited. No entry followed the following prompt]
[root@small ron]# Mutex destroy failure: Device or resource busy
kdeinit: Fatal IO error: client killed
kdeinit: sending SIGHUP to children.
kdeinit: sending SIGTERM to children.
kdeinit: Exit.
[hang. Here a ^C was necessary].
[root@small ron]#
Re:
_KDE_IceTransmkdir: Owner of /tmp/.ICE-unix should be set to root
Setting the owner as per above does not stop the message.
What service is invalid? What said so? *.desktop is not a service.
What file had a bad file descriptor? According to what?
What device or resource was busy? Who said so? What was it busy doing?
What client was killed?
The information that answers these questions was immediately available
when the message is being prepared and was deliberately omitted. Why?
This is a sick form of agression by the developer against his users.
In this parlous state, is 9.0 a viable product?
--
Ron [Melbourne, Australia]
"The problems that we have created as a result of the level of thinking
that we have done thus far cannot be solved at the same level of
thinking at which we created them." - Albert Einstein.
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
