APR
4
2002

KDE 3.0: A New Era In Desktop Choice

Today the KDE Project proudly announces the release of KDE 3.0 (fully mirrored below), a release which marks a new era of choice on the desktop. Every advance opens the door to a group of new adopters, and KDE 3 is set to tear the doors asunder. In celebration of the release, the KDE League has posted the text KDE: The Complete Enterprise Desktop Solution, a work-in-progress but already something useful to show those who are considering the migration to freedom. Enough talk, time to download.

 


[Full Announcement Available Here]

Comments

The issue of split infinitives is not clear-cut. Grammarians are divided over it. The two errors he pointed out, however, are completely uncontroversial.


By Jérôme Loisel at Thu, 2002/04/04 - 6:00am

"...school that a sentance begins..."

I think you mean "sentence".... and I stopped reading then.

Glass houses and throwing stones comes to mind.


By Corba the Geek at Thu, 2002/04/04 - 6:00am

I've generally got better response to bugs posted here than to bugs.kde.org, so I don't usually bother with the latter any more.


By cbcbcb at Thu, 2002/04/04 - 6:00am

tre bonega novajxo :))


By Capit Igloo at Thu, 2002/04/04 - 6:00am

‚ ã! â® ¢®®¡é¥ á㯥à! ‘ ¬ë© ª« áá­ë© ¤¥áªâ®¯! ‘ª®à® ¤®«¦­  ¢ë©â¨ è ¯ª  - ¢®â ¨ ¯®á¬®âਬ, çâ® §  èâ㪠 â ª ï!


By ᯥ«« 祪¥à at Thu, 2002/04/04 - 6:00am

Time to look forward to KDE 3.1, see what's planned: http://developer.kde.org/development-versions/kde-3.1-features.html


By Jan at Thu, 2002/04/04 - 6:00am

"Tabbed browsing support (David Faure & Doug Hanley)"

woohoo! I can give up Mozilla for ever! :-D


By danrees at Fri, 2002/04/05 - 6:00am

I was running rc3 - and it was great! Now I installed the final (SuSE 7.3 packages), after removing the rc3 from my box, and it won't start. throws me out with some dcop error:

There was an error setting up inter-process communications for KDE. The message returned by the system was:

could not read network connection list.
/root/.DCOPserver_boreas__0

Please check that the "dcopserver" program is running!

Now, this box used to run rc3 just fine, and the same thing happend to a clean install of KDE3 over KDE2 on another box.

any idea's?

cheers,

Martijn


By Martijn Dekkers at Thu, 2002/04/04 - 6:00am

The same thing happened to me with the suse 7.3 packages.
Haven't really time to check now as I'm at work now but I'll look deeper into it tonight.


By thomas at Thu, 2002/04/04 - 6:00am

insert

"export KDEDIR=/opt/kde3"

in the /opt/kde3/bin/startkde script


By brat at Thu, 2002/04/04 - 6:00am

I had some dcop problems, here. The above solution fixed the problem !
No problems found during the last RC version, hopefully this is fixed in a more general way soon.

Peter


By Peter at Thu, 2002/04/04 - 6:00am

Thanx for your hint. This solved the problem when i start kde as root. But it doesn't work for non-root users (something like dcop-connections rejected). I'm using Suse 7.3 with XFree86 4.2. Anyone has an idea?


By Daniel at Thu, 2002/04/04 - 6:00am

Check the values of PATH, KDEDIR and KDEDIRS, maybe it gets set differently for non-root users somehow?

Cheers,
Waldo


By Waldo Bastian at Fri, 2002/04/05 - 6:00am

Hi Waldo
Thank you for your suggestion. I looked at the values of PATH, KDEDIR and KDEDIRS and couldn't see a difference. The only thing i noticed is that /opt/kde2/bin is in the path but not /opt/kde3/bin, the same for root and non-root.

Here the detailed log of what happens when i start as non-root user (as said before, running as root goes well)

XFree86 Version 4.2.0 / X Window System
(protocol Version 11, revision 0, vendor release 6600)
Release Date: 23 January 2002
If the server is older than 6-12 months, or if your card is
newer than the above date, look for a newer version before
reporting problems. (See http://www.XFree86.Org/)
Build Operating System: SuSE Linux [ELF] SuSE
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/XFree86.0.log", Time: Fri Apr 5 10:55:35 2002
(==) Using config file: "/etc/X11/XF86Config"
DCOPServer up and running.
DCOP aborting call from 'anonymous-1841' to 'kded'
ERROR: KUniqueApplication: DCOP communication error!
DCOP aborting call from 'anonymous-1845' to 'knotify'
ERROR: KUniqueApplication: DCOP communication error!
kdeinit: Fatal IO error: client killed
kdeinit: sending SIGHUP to children.
KLauncher: Exiting on signal 1

waiting for X server to shut down

kdeinit: sending SIGTERM to children.
kdeinit: Exit.


By Daniel at Fri, 2002/04/05 - 6:00am

just checked - it can't be the PATH, added /opt/kde3/bin, removed /opt/kde2/bin and still get the same error runnung non-root. once it failed, a simple
> su
in the same directory does it: retyping
> startx
brings up the beautiful KDE 3.0. so it seems to be some strange user-priv stuff, but i can't figure for which file/directory


By Daniel at Fri, 2002/04/05 - 6:00am

I'm having these problems as well. I had issues with upgrading to kde2.0 back in the day but a little fussing around got it working, but this time I can't figure it out. here's my setup:
distro: slack 8.0
install method: packages
where: /opt/kde

actually, kde2.0 is in /opt/kde2
kde3.0 is in /opt/kde3
/opt/kde is a symlink to /opt/kde3. it used to be a symlink to /opt/kde2 before i did the install so all I really did was remove the symlink, install, move kde to kde3, and install the symlink. I've gone through the tmp folder and remove ANYTHING that looked like it might give me problems, including files starting with a . I also removed my .kde folder, and other .ICE and .DCOP files in my home directory. I've tried this as both root and a normal user and cannot get kdeinit to start up due to dcop issues. the weird thing is switching back to kde2.0 is painless (just change the symlink). when trying to get kde3.0 up I see teh splash screen, but dcop cannot be used and I get the same errors mentioned above. any ideas?:(


By Will Stokes at Mon, 2002/04/08 - 5:00am

I've had the same problem after I compliled the 3.1rc6 binaries, KDE would work for root, and under VNC. After removing the user's .xftconfig file it started right up... It's something to try. Good luck


By Tony at Thu, 2003/01/09 - 6:00am

Hi all I had this frustrating problem for quite some time, it involved iceauth and I keeped on getting an error message refering to sh: line1: iceauth: command not found, or somthing similar.

My soloution was to find out which package iceauth came in, and install it. in this case it was simply xbase-clients

goodluck
aaron


By aaron at Sun, 2003/02/23 - 6:00am

I also had an annoying problem with this. The 'iceauth' file is part of the XFree86 package which comes with Redhat. If the dcopserver program can't find iceauth, you need to first check that iceauth exists on your machine (in /usr/X11R6/bin/ normally) then set your search PATH to include this directory so dcopserver knows where to look (ie. export PATH=/usr/X11R6/bin/). That worked for me. Good Luck....
Bruce


By Bruce at Fri, 2003/03/21 - 6:00am

I got the same errors, I found out it was because my /home partition was FULL.


By jonny at Fri, 2007/02/09 - 6:00am

I had this exact problem before with Redhat when updating to 2.2.x.
I solved this problem buy download "ALL PACKAGES" including QT3.0.x as
well as other packages, not just KDE packages. The problem solved.
:)


By Tom at Thu, 2002/04/04 - 6:00am

I had that problem for all users (root and non-root). I have tried all the suggestions which were posted here but non worked. The only solution I have found was to sym-link /opt/kde3 to /opt/kde2. This was needed despite that only /opt/kde3/libs was listed in /etc/ld.so.conf and only /opt/kde/bin was addedd to the $PATH in /etc/profile. But hey, it works so I'm happy ;-)


By JoeFromTheBush at Fri, 2002/04/05 - 6:00am

I had that problem for all users (root and non-root). I have tried all the suggestions which were posted here but non worked. The only solution I have found was to sym-link /opt/kde3 to /opt/kde2. This was needed despite that only /opt/kde3/libs was listed in /etc/ld.so.conf and only /opt/kde/bin was addedd to the $PATH in /etc/profile. But hey, it works so I'm happy ;-)


By JoeFromTheBush at Fri, 2002/04/05 - 6:00am

Try installing xbase-client

if it isn't already, that was my problem.


By aaron at Sun, 2003/02/23 - 6:00am

I have this same error with SuSE 8.0 clean install. Sort of frusterating with a clean install!

Trying the suggestions above...


By Mattfago at Tue, 2002/04/30 - 5:00am

Hey... guys.. you need to install lib_fam. Not hard.. do a google search for libfam site:oss.gsi.com and you'll come up with it...

untar it, cd to dir, ./configure, make, make install and vuala.

hope it helps.


By feeshbar at Mon, 2002/06/17 - 5:00am

Hey... guys.. you need to install lib_fam. Not hard.. do a google search for libfam site:oss.gsi.com and you'll come up with it...

untar it, cd to dir, ./configure, make, make install and vuala.

hope it helps.


By feeshbar at Mon, 2002/06/17 - 5:00am

A google search doesn't find the oss site you specified. Is there somewhere else?


By David Reinhart at Tue, 2002/11/19 - 6:00am

I was running rc3 - and it was great! Now I installed the final (SuSE 7.3 packages), after removing the rc3 from my box, and it won't start. throws me out with some dcop error:

There was an error setting up inter-process communications for KDE. The message returned by the system was:

could not read network connection list.
/root/.DCOPserver_boreas__0

Please check that the "dcopserver" program is running!

Now, this box used to run rc3 just fine, and the same thing happend to a clean install of KDE3 over KDE2 on another box.

any idea's?

cheers,

Martijn


By Martijn Dekkers at Thu, 2002/04/04 - 6:00am

I am having the exact same problems.

Unfortunately, the error message doen't indicate where to look for the problem. I have change the libICE.so.6 but that didn't fix it.

Any help would be very much appreciated.
Thanks


By JoeFromTheBush at Thu, 2002/04/04 - 6:00am

On the KDE mailing list (lists.kde.org) there is a mail:

in /opt/kde3/bin/startkde change:

unset KDEDIRS to unset KDEDIR

works for me :-)


By Martijn Dekkers at Thu, 2002/04/04 - 6:00am

Over on usenet we're seeing the same problem - unset KDEDIR didn't work for me, and I've tried manually setting KDEDIR KDEDIRS and PATH correctly, and it still won't run. I had RC3 installed, and did a -Uvh.

Any ideas? (I'd poke around more, but I have business deadlines, and right now I need to work, not play with a desktop. Above anything else, KDE is a functional environment for me. :)

--
Evan


By Evan "JabberWok... at Fri, 2002/04/05 - 6:00am

I have exactly the same problem with KDE 3.0.1 on SPARC Solaris 9 box, none of the above solution works for me.

But, when I log into failsafe mode (one of Solaris' DT login mode to start basic X), then run startkde manually, the KDE starts!

Very strange. Any idea?


By Yale Yu at Wed, 2002/07/10 - 5:00am

I have exactly the same problem with KDE 3.0.1 on SPARC Solaris 2.6 box
, none of the above solution works for me.

But, when I log into failsafe mode (one of Solaris' DT login mode to start basic X), then run startkde manually, the KDE starts!


By Girisha at Sun, 2002/10/06 - 5:00am

I too ran into the DCOP message

"could not read connection list"

running KDE 2.1.2 on SuSE. I had moved /tmp to a new partition and had forgotten to set the "sticky bit" on /tmp.


By Clem Dickey at Sun, 2002/11/10 - 6:00am

(sigh) Although the sticky bit *was* missing, DCOP was probably more unhappy with the lack of "go+w" permissions on /tmp. It's late.


By Clem Dickey at Sun, 2002/11/10 - 6:00am

The answer to your problem is a known issue with Solaris and the /tmp/.ICE-unix directory used by DCOP. If you ran kde as root initially, /tmp/.ICE-unix is not writable by anyone else. Do a chmod 777 on it before logging out. Then it should work fine when you log back in as anyone else. :)

Have found that logging into KDE as root at any time will reset and cause this problem again. Write a script or avoid logging into KDE as root. :)

Mike W.


By Mike W at Thu, 2003/01/30 - 6:00am

Hi,

I had exactly the same problem after I was moving with my linux
to another location. I got a new UID (500), but kept the same user name.

Thats why KDE could not create files with my user name in /tmp,
because they were already there, but with the old UID (503).

Everything worked fine for me after I removed the the old files
like this (503 was my old UID):
find /tmp -uid 503 -exec rm -rf "{}" \;

Good luck.
Abrax


By abrax at Sat, 2003/06/28 - 5:00am

I found the following issues that resolved the .DCOPserver_??__# problem.
In the directory of the user under .kde/ you'll find these files:
~socket_servername
~tmp_servername

I deleted these two files and restart kde and everything began to work as it should.


By Dale Arey at Wed, 2003/07/09 - 5:00am

I had a similar problem after having to reboot a Mandrake 9.2 machine (KDE 3.1.3) and I fixed it by renaming the dirs /tmp/ksocket-(username) and /tmp/kde-(username) to different names. Seems that perhaps this issue is sometimes caused by DCOPserver terminating in an ungraceful fashion.


By Michael Barrett at Wed, 2003/12/17 - 6:00am

It worked perfectly, a new /tmp/ksocket-fernando was created and now everything runs fine. The problem aroused when I closed KDE with Crtl-Alt-Bksp what probably terminated the processes ungracefully.


By Fernando Gerdt at Sat, 2004/05/15 - 5:00am

I'm using RH9.0. I found the same error

could not read network connection list.
/home/my_user/.DCOPmyserver__0

Please check that the "dcopserver" program is running!

after a reboot!

I followed instructions 'by Dale Arey on Wednesday 09/Jul/2003, @18:02 '
above, and that solved the problem.

thanks a lot!


By M. C. Tripp at Fri, 2004/03/26 - 6:00am

I tried changing the names of the above mentioned /tmp/ and /$user/ files with no success.

Realised eventually that what Mike W said 30 Jan 03 is true in my case. Checking permissions (ls -l -a) in $user/ showed that .ICEauthority was owned by root and belonged to group root, so as a user I had no say over it's rwx. Instead of changing the permissions so that every man and his dog can write to it, I changed the user and group (chown [username].[username] .ICEauthority). Now works fine!

Mandrake 10.0 Official
intel PC


By Brad Milne at Thu, 2004/05/06 - 5:00am

i had the same problem and the problem was i had my /etc/sysconfig/network parameters badly configured


By polrus at Fri, 2004/11/26 - 6:00am

hi, I have encountered the similar problem when try to login KDE.
But have to clarify the point before explain the phenomenon,
that is: I have set the default shell as "tcsh" for my users and root.
default shell in REDHAT-7.3 is "bash".
in order to start kde, the only way for me is setting default shell back.
then problem is gone.
actually, I am used to work with tcsh,not familiar with bash.
For the more depth reason, should be solved by linux-developer.
hope help.


By temp-join at Tue, 2006/04/11 - 5:00am

I solved the problem by running fsck --rebuild-tree on my disk with my home directory...


By burner at Wed, 2006/04/19 - 5:00am

The problem is related to a mismatch between the PID number you'll see in the task-manager for dcopserver and the number you'll see in line 2 in both the /root/.DCOPserver_boreas__0 -files, and the two similar files in your and maybe other users HOME-dir. These files can safely be deleted as dcopserver creates them at boot time if they doesn't exist, and thus fixes the problem for you. - Delete the files and reboot!


By Svein Liby at Fri, 2006/08/25 - 5:00am

Nice article in every way, but I wonder how you know that it's the "leading" desktop. Hard to estimate, I would think. Otherwise, brilliant article and KDE 3 looks very good.


By Joe at Thu, 2002/04/04 - 6:00am

do you know of anything similar on linux/unix/bsd that has the capabilities of kde ? oh please dont come up with gnome now.


By dr. schiwago at Thu, 2002/04/04 - 6:00am

So in other words you're guessing that KDE is "leading". A guess is something different than a fact. I'm not saying KDE is bad, but for the sake of credibility I think you need to avoid statements you can't prove. Just a suggestion.


By Joe at Thu, 2002/04/04 - 6:00am

Pages