KDE 3.2 Beta 2 "Dobra Voda" is Waiting For You

Our first KDE 3.2 Beta "Rudi" was a huge success and resulted in over 2000 resolved bugs. As the code still has some rough edges, we decided to go for another beta. So here it is: Dobra Voda. Please continue reporting problems you see with it, your testing is much appreciated. You can download Dobra Voda at http://download.kde.org/unstable/3.1.94. Currently we have binaries for Fedora, Slackware and SUSE, besides the sources.

Dot Categories: 


by stunji (not verified)

The only conflicts I saw were for libtag.so (apparently not included on SuSE 9 CDs) and a package called kdenetwork-SuSE. I just installed with --force --nodeps and things seem to work OK, just a few problems:

Suseplugger no longer manages my device icons
Konqueror segfaults in webbrowsing mode
Widgets sometimes flicker / comboboxes set their values randomly

I wouldn't recommend installing these packages at work, but for home they're fun to play with. Give it a shot. You might also want to move your .kde/ dir out of the way, this is probably causing some of my problems.

by Anonymous (not verified)

"--force --nodeps" is a good source for problems.

by Ojay (not verified)

Sure. It will work this way or it won't work at all. Most probably it will work because you install everything. If it does not work, then the packager made mistakes and produced really buggy binary packages. In this particular case the binaries should be considered to be useless. Don't use them....

by Roberto Alsina (not verified)

Or simply, the new version has a requirement the older one didn't have, and it's not provided by these RPMs. That is a perfectly reasonable problem, and it doesn't mean the binaries are in any way buggy.

Using --force --nodeps is only good if you know WHY you can ignore missing dependencies (for example, if you have a library built from source in some other path, and litle else)

by GeorgeM (not verified)

to stop Konqueror crashing in web browsing, Remove the application krpmview and its associated files which are supplied by SuSE as part of kdebase3-SuSE.

This has been logged as bug number 61042, details at http://bugs.kde.org/show_bug.cgi?id=61042

by Jeroen (not verified)

Aha so that was the problem. I saw a conflict between kdebase3 and kdebase-suse, so I removed kdebase-suse and it worked fine.



by John E. Martin (not verified)

Thank you! I've been frustrated for the past 4 days because the -only- problem I'm having with beta2 was konqueror segfaulting every so often. That has certainly cleared it up.

by Rich Jones (not verified)

Use Kpackage, and select all of the .rpm's.
Then, install marked.

by Kevin (not verified)

Running SuSE 9.0.

Does anyone else get this problem?:

Upon login of a new user (created after installing 3.1.94), I immediately get a dialog with TitleBar: "Sorry - KDesktop" with content: "KDEInit could not launch 'default_desktop_aligning': Could not find 'default_desktop_aligning' executable.


I also have a problem with fonts in the Konsole application. When I open a Konsole, or when I specifically choose the Linux font for the Konsole, I get an error dialog with TitleBar: "Error - Konsole" and content: "Font `-misc-console-medium-r-normal--16-160-72-72-c-80-iso10646-1' not found.
Check README.linux.console for help."


But I have no file README.linux.console anywhere on my filesystem. Any thoughts?

I did the following in upgrading:
1. dl suse ix86 rpms for 9.0
2. init 3
3. login as root
4. rpm -Fvh (or -Uvh) kde3.....rpm (one at a time, in such a manner as to resolve all dependency problems before successful install---thus, very few times did I need to use --force --nodeps and only where it seemed clear that some other package would be providing the necessary requirements)
4a. As a part of this step, I also had to first do some rpm --erase packageX.rpm where there were conflicts (in some cases, my SuSE 9.0 insisted on =3.1.4 package versions rather than >=3.1.4 versions)
5. Ran YaST from the console, looked at the summary of dependency problems (many were reported, but only one that I hadn't noticed forcing from the command line), found one for libtag, therefore, I did:
6. rpm -Uvh taglib-0.95-5.i586.rpm
7. Used console YaST to create a new user (thinking to get an entirely new .kde directory upon first KDE startup and not risk damage to some existing user's .kde directory)
8. init 5 (I got a different kdm background from before, but it still looks nice---noticed 2 or 3 system users (privoxy, some others) listed in the kdm user list as well as regular users)
9. Logged in as the new user and got the Error Dialog listed above.

Just about everything else seems to work fine. I did find the Konqueror bug and fixed it (or rather, did the workaround listed in the bug report), but of course that removes the handly konqueror plugin for looking at rpm package contents---hopefully this will be fixed soon.

I had few or none of the other problems mentioned here and in similar threads. I thought there might have been an issue with my suseplugger, (my CD-ROM and DVD-ROM don't show up on the new user's desktop), but that really seems to be related to the error dialog listed above. If I do any clicking on the desktop surface itself, the error dialog is brought to the front and the focus is assigned there. When I ran suseplugger by hand, it let me integrate the optical drives (though I didn't get links on the desktop).

FWIW, this whole setup is with a Matrox Millenium G450 and running X in dual-head mode with one monitor at 1600x1200 and the other at 1024x768 with xinerama---not a trivial arrangement, but KDE 3.2 Beta 2 seemed to do ok with it. My sound works, panel works, I'm posting this in konqueror, xmms works, quanta 3.2 beta 2 starts up, kdevelop 3.0.0b2 starts up (though SuSE YaST reports many dependency problems with it, I'm guessing that the dependency problems reported are more problems with packaging than actual lacks of some requirement---else, would it start up so nicely?), kommander starts up. Not sure what else to test.

Oh... one last question. I find no link in menu for kcontrol. I have to run it from the command line (though when I do, it seems to work fine).

Many thanks to the KDE developers! Nice work!


by Craig (not verified)

I fixed the "default_desktop_aligning" problem by extracting it from the original SuSE 9 kdebase package:

cp [path to /suse/i586/kdebase3-3.1.4-52.i586.rpm] into a temp directory-not into your /opt/kde3!
cd into to the temp dir and:
rpm2cpio kdebase3-3.1.4-52.i586.rpm | cpio -i --make-directories
Next, delve to opt/kde3/bin in your new set of kdebase directories and cp default_desktop_aligning to /opt/kde3/bin

delete the temp dir. Logout and login.

The konsole font problem, I just picked Normal, then Save as default and the message stopped. Problem with font aliasing??


by Lolaine (not verified)

the fix is:
rm /opt/kde3/share/apps/khtml/kpartplugins/krpmview.rc

well ... you won't see rpms in konqueror ... but its a fix :D

by Ojay (not verified)

Wow. I tried the 3.2beta1 release before and I found always the same annoying bugs I also found before in 3.1.x. To my large surprise up to now all these annoying bugs (plus the additional ones introduced in the first beta) are gone. For me it looks like as if 3.2beta2 is even better than 3.1.4! Good work!

Even more remarkable for me is the speed of the second beta (it feels at least 30% faster) compared to both 3.1.4 and 3.2beta1. Where does this really large speed momentum come from?

by JC (not verified)

If you still have bugs, you can fill a report on bugs.kde.org :)

by joe p (not verified)

well, he said that the bugs are actually GONE!

good to hear all this positive advancements!

by wygiwyg (not verified)

'Where does this really large speed momentum come from?'

Fresh install :)

by Ojay (not verified)

Okay. After one more day giving it a try I have to say that my first impressions were the right ones. Ah and by the way I am using the SUSE 8.2 binaries.

Nevertheless, I found two severe bugs that were also present in the first beta:
- after entering and highlighting some text in webforms, pressed keys no longer get accepted. After some mouse actions on the highlighted text it might be that keys pressed on the keyboard get accepted again.
- KNode tries to receive new messages from a newsserver but refuses to do so showing the error message: "Connection not possible. Work in progress." This seems to indicate incompleted work.

by Jord (not verified)

Had the same knode bug you were suffering from.

Had to do some re-emerge under gentoo since some gcc, it didn't accept one of my use variables. However after the re-emerge knode works perfectly (even in kontact).

What I'm saying, it might be a compile bug in the binaries, it doesn't have to be in the source.

by JLP (not verified)

Did anyone try to run KDE 3.2 Beta 2 and XFree86 4.4.0 RC1 together. I installed them here but KDE just doesn't want to start :(. GNOME works fine though.

are you using binary packages ?
if so, I guess that there are linked to the old XFree libraries. You might want to recompile everything.

Yup binaries for both. Is there so much difference in 4.4.0 that everything needs to be recompiled? Ah well it looks like I will have to wait on this machine :(

by Anonymous Coward (not verified)

Try compiling only kdebase and kdelibs against your new X, and install the rest as binaries. Might work.

by Lubos Lunak (not verified)

Xlibs should be backwards-compatible, so there should be no need to recompile apps using older Xlibs in order to run with newer ones. This looks like a bug, but it's hard to say where and whose without knowing details.

Yeah sounds logical. Then we would have to compile everything just because of upgrading XFree86. And considering that all other WMs work just fine then I guess KDE should also work fine. I guess I will have to file a bug, Would it be best to report it here, at XFree86 or maybe even both?

i'm using beta2 with xfree8t rc1 of 4.4.0

everything is working ok, the only problem is, if i use the kde-option: "restore previous session" my kde hangs after restarting, cpu time is up to 99%. after a few minutes, my xserver freezes. i think it could easily be a bug, but i'm not shure yet if it's successional with the new xfree86.

the only solution i found until now is to remove the directory KDEHOME/share/config/session. if i do so, my kde starts up fine, without any components of the last session, shurely.

oh yes, and top said the 99% of cpu time comes from tree or four kdeinit processes wich uses each about 30%.


This is what I get when I try to run KDE:

startkde: Starting up...
Loading required GL library /usr/lib/libGL.so.1
kdeinit: Launched DCOPServer, pid = 3684 result = 0
DCOP: register 'anonymous-3684' -> number of clients is now 1
DCOP: unregister 'anonymous-3684'
kdeinit: Launched KLauncher, pid = 3688 result = 0
DCOP: register 'klauncher' -> number of clients is now 1
DCOP: unregister 'klauncher'
DCOP: register 'klauncher' -> number of clients is now 1
QPixmap: Cannot create a QPixmap when no GUI is being used
QPixmap: Cannot create a QPixmap when no GUI is being used
DCOP: new daemon klauncher
kdeinit: Launched KRandrInitHack, pid = 3689 result = 0
kdeinit: Launched KDED, pid = 3690 result = 0
DCOP: register 'kded' -> number of clients is now 1
DCOP: unregister 'kded'
DCOP: register 'kded' -> number of clients is now 1
Loading required GL library /usr/lib/libGL.so.1
DCOP: register 'anonymous-3690' -> number of clients is now 2
DCOP aborting call from 'anonymous-3690' to 'kded'
DCOP: unregister 'kded'
kded: ERROR: Communication problem with kded, it probably crashed.
DCOP: unregister 'anonymous-3690'
kdeinit: PID 3690 terminated.
kdeinit: opened connection to :0.0
kdeinit: Launched 'kcminit', pid = 3692 result = 0
Loading required GL library /usr/lib/libGL.so.1
kdeinit: PID 3692 terminated.
kdeinit: Launched 'knotify', pid = 3693 result = 0
DCOP: register 'knotify' -> number of clients is now 1
Loading required GL library /usr/lib/libGL.so.1
DCOP: register 'anonymous-3693' -> number of clients is now 2
DCOP aborting call from 'anonymous-3693' to 'knotify'
DCOP: unregister 'knotify'
ERROR: Communication problem with knotify, it probably crashed.
DCOP: unregister 'anonymous-3693'
kdeinit: PID 3693 terminated.
kdeinit: Got KWRAPPER 'ksmserver' from socket.
WARNING: NAME not specified in initial startup message
kdeinit: PID 3696 terminated.
Loading required GL library /usr/lib/libGL.so.1
startkde: Shutting down...
kdeinit: terminate KDE.
klauncher: Exiting on signal 1
DCOP: unregister 'klauncher'
startkde: Running shutdown scripts...
startkde: Done.

by Waldo Bastian (not verified)

Analysis of log:
Both kded and knotify crash and probably ksmserver as well.

The "Loading required GL library /usr/lib/libGL.so.1" looks suspicious, GL tends to cause heaps of problems.

You *might* want to clean out all your old DCOP sockets and ICE files.

I had similar problems when I upgraded X once with one of the 3.0 series of KDE -- on my system the .DCOP files in the ${HOME} directory and the .ICE files appeared to be tied to something specific in X. ...
It cause the KDE startup to hang for a while and then die horribly .. leaving X hung.

-- Just a possibility to be explored.

I have kde cvs from yesterday running on X-
running on a radeon 9200se , really good.

by Robert Inglis (not verified)

Not RC1 but I just installed RC2 last night over 4.3.0. It seems that by default 4.4.0 installs its base xinitrc-overwriting my existing xinitrc link.

Kde would start right up after making a minor adjustment by (re)moving the base xinitrc installed by 4.4.0 and creating a new xinitrc link to point to my initrc.kdm script. Before that, X would use XDM.


by Lars Westergren (not verified)

I have the same problem. I have had some problems with my Intel i845 graphics card at work. If I leave the computer alone for 5 min X crashes, so I decided to try to upgrade X to 4.4.0 RC2. After installing the binaries, it started the fwm window manager. After lynxing around on the net I finally learned that I had to change the .xinitrc file to exec startkde
X starts, but then quits with the following messages on screen:

XFree86 Version (4.4.0 RC 2)
Release Date: 18 December 2003
X Protocol Version 11, Revision 0, Release 6.6
Build Operating System: Linux 2.4.18-14 i686 [ELF]
Current Operating System: Linux xxx 2.4.22-10mdk #1 Thu Sep 18 12:30:58 CEST 2003 i686
Build Date: 20 December 2003
Changelog Date: 19 December 2003
Before reporting problems, check http://www.XFree86.Org/
to make sure that you have the latest version.
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 Jan 9 16:05:04 2004
(==) Using config file: "/etc/X11/XF86Config-4"
Symbol ShadowFBInit from module /usr/X11R6/lib/modules/drivers/i810_drv.o is unresolved!
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list!
startkde: Starting up...
Loading required GL library /usr/lib/libGL.so.1
Loading required GL library /usr/lib/libGL.so.1
DCOP aborting call from 'anonymous-3380' to 'kded'
ERROR: Communication problem with kded, it probably crashed.
Loading required GL library /usr/lib/libGL.so.1
Loading required GL library /usr/lib/libGL.so.1
DCOP aborting call from 'anonymous-3383' to 'knotify'
ERROR: Communication problem with knotify, it probably crashed.
Loading required GL library /usr/lib/libGL.so.1
startkde: Shutting down...
KLauncher: Exiting on signal 1
startkde: Running shutdown scripts...
startkde: Done.

waiting for X server to shut down

My .xsession-errors file gives the following information:

startkde: Starting up...
Loading required GL library /usr/X11R6/lib/libGL.so.1.2
Loading required GL library /usr/X11R6/lib/libGL.so.1.2
kbuildsycoca running...
Loading required GL library /usr/X11R6/lib/libGL.so.1.2
Loading required GL library /usr/X11R6/lib/libGL.so.1.2
mcop warning: user defined signal handler found for SIG_PIPE, overriding
Loading required GL library /usr/X11R6/lib/libGL.so.1.2
Loading required GL library /usr/X11R6/lib/libGL.so.1.2
Loading required GL library /usr/X11R6/lib/libGL.so.1.2
mcop warning: user defined signal handler found for SIG_PIPE, overriding
Loading required GL library /usr/X11R6/lib/libGL.so.1.2
Loading required GL library /usr/X11R6/lib/libGL.so.1.2
Loading required GL library /usr/X11R6/lib/libGL.so.1.2
Loading required GL library /usr/X11R6/lib/libGL.so.1.2
Loading required GL library /usr/X11R6/lib/libGL.so.1.2
konsole: cannot chown /dev/pts/0.
Reason: Operation not permitted
konsole_grantpty: determined a strange device name `/dev/ptmx'.
konsole: chownpty failed for device /dev/pts/0::/dev/pts/0.
: This means the session can be eavesdroped.
: Make sure konsole_grantpty is installed in
: /usr/bin/ and setuid root.
WARNING: KDE detected X Error: BadDrawable (invalid Pixmap or Window parameter)\ \x09
Major opcode: \x0e
konsole_grantpty: determined a strange device name `/dev/ptmx'.
QClipboard::setData: Cannot set X11 selection owner for PRIMARY
startkde: Shutting down...
KLauncher: Exiting on signal 1
startkde: Running shutdown scripts...
startkde: Done.

I was looking through all the startup scripts (there are quite a lot of them in different places...) until I realised I could try startgnome instead, and lo and behold, it starts fine.

I'm currently looking for the initrc.kdm file another poster mentioned, so I can get KDE to work again, but no luck finding it yet. Also, I'm now pretty sure that its the graphics card drivers that caused my original problems, its the procedure LpWaitRing() in the driver which causes the crash after 5 min with the following message in the logs:
Dec 9 15:16:08 lars kernel: [drm:i830_wait_ring] *ERROR* space: 131048 wanted 131064
Dec 9 15:16:08 lars kernel: [drm:i830_wait_ring] *ERROR* lockup

by Martin (not verified)

I've got the same problem with Intel845/855
Did you find answer??

by Aberhatschi (not verified)

I have the same Problem, too
Acer Travelmate 243LC


Title says it all. I'd appreciate the response.

I tried on an up to date RH 9 system. Got the following errors/dependency problems:

error: Failed dependencies:
libdb_cxx-4.1.so is needed by kdeaddons-3.1.94-0.2
kdeaddons = %{epoch}:3.1.94-0.2 is needed by kdeaddons-atlantikdesigner-3.1.94-0.2
libsensors.so.2 is needed by kdebase-3.1.94-0.2
libsmbclient.so.0 is needed by kdebase-3.1.94-0.2
libieee1284.so.3 is needed by kdegraphics-3.1.94-0.1
libiw.so.26 is needed by kdenetwork-3.1.94-0.1
libdb-4.1.so is needed by kdesdk-3.1.94-0.1
libdb-4.1.so is needed by kdevelop-3.0.0b2-0.2
libMagick-5.5.6-Q16.so.0 is needed by koffice-1.2.94-0.2
libqassistantclient.so.1 is needed by (installed) PyQt-3.5-5

They work flawlessly here. Just satisfy the dependencies and it flies like an angel!

I tried:

rpm -i kdebase-3.1.94-0.2.i386.rpm kdelibs-3.1.94-0.2.i386.rpm arts-1.1.94-0.1.i386.rpm qt-3.2.3-0.2.i386.rpm redhat-artwork-0.88-2.i386.rpm

I got:

libsensors.so.2 is needed by kdebase-3.1.94-0.2
libsmbclient.so.0 is needed by kdebase-3.1.94-0.2

I have lm_sensors installed which provides libsensors.so.1 only, and I don't know where to find the libsmbclient - it is not in the samba-client package.



try using rpmfind.net. Here is waht I got, when i searched for: "libsmbclient.so.0":


I would try to use the packages for "iRed Hat Beta Workstation taroon for i386"

here's the link to the package:



Tell us how you satisfied the dependencies and like what I have done. At the beginning there were a lot of dependencies missing and start thinking and tried a lot of ways and it kind resolved one but poped out others. So I went to upgrade my sistem using the apt-get upgrade (this is redhat9). I used these two repository

# Red Hat Linux 9
rpm http://ayo.freshrpms.net redhat/9/i386 os updates freshrpms
#rpm-src http://ayo.freshrpms.net redhat/9/i386 os updates freshrpms

# Dag Apt Repository for Red Hat 9
rpm http://apt.sw.be redhat/9/en/i386 dag

Could be some other repository but I couldn't locate. The dag one took a lot of the work and this are the last one that couldn't been done

libdb_cxx-4.1.so is needed by kdeaddons-3.2.0-0.1
libsensors.so.2 is needed by kdebase-3.2.0-0.1
libsmbclient.so.0 is needed by kdebase-3.2.0-0.1
libieee1284.so.3 is needed by kdegraphics-3.2.0-0.1
libdb-4.1.so is needed by kdesdk-3.2.0-0.1
libmysqlclient.so.10 is needed by qt-MySQL-3.2.3-0.2

Lets us know how could this dependencies be satisfy.

Thank you for sharing.

Rosendo from Todos Santos, Guatemala

by Michael Kairys (not verified)

I (as well) am trying to install KDE 3.2 on RedHat 9. There is no such package (understandably, since RedHat 9 is "dead"). I tried the Fedora packages and found they depend on later versions of some system libraries, specifically
libsensors.so.2 and libsmbclient.so.0 are needed by kdebase-3.2.0-0.1

libsmbclient was pointed to in this thread. libsensors is found by rpmfind but only for a Mandrake distribution (and will that work???)

But by now I'm getting a "should I be doing this" feeling. Let me rephrase the question: should Fedora packages be used on RedHat 9? Is there a better alternative (SuSE 9 packages perhaps) for getting KDE 3.2 on RedHat 9?

And is it reasonable to assume that RedHat 9 packages will not be forthcoming?

Thanks for any wisdom or anything close ;-)

Michael Kairys
SL Corporation

On IRC chat #kde (Freenode) someone was advocating using yum to get the proper packages for resolving this problem. YMMV

I found a source for libsmbclient.so.0 at http://samba.org/~jerry/RPMS/samba/RedHat/RPMS/i386/9.0/ and that seems to work. As for the other dependencies, I'm still working on it. Some day, I will be able to run Apollon!

by cl (not verified)

i tested the beta1 release on my suse 8.2 installation, and it was impressive.
now i can't wait to test the beta2 for suse 9. :)

by anonymous (not verified)

kde.org says, that Gideon/Kdevelop is released too?

by Søren Holm (not verified)

right here ... it is not included in the KDE-sources


by teatime (not verified)

The mirror I looked at has it. Try another?

by Brian Kendig (not verified)

The beta 2 release appears to only have a few rpm's in it, far fewer than the beta 1 -- I assume that to install beta 2, I have to have beta 1 already installed?

I hit a bunch of dependency problems when I tried to install either beta by downloading all the rpm's and running 'rpm -Fvh *.rpm' as the readme says. It's missing libartsbuilder.so.0, libartsgui.so.0, libartsmidi_idl.so.0, kdelibs3, libvcard.so.0, libgnokii.so.0, etc. etc. Some of these are supposed to be provided by some of the beta rpm's themselves, and others should be installed already in SuSE 9.0, so I don't understand why they can't be found.

>far fewer than the beta 1
nope, as many packages as beta 1 (leave out the debug-rpms)
you don't need to have beta 1 installed.

>'rpm -Fvh *.rpm'
try without the -F option. i installed _all_ packages available for my arch
(suse 9.0 / ix86), after that i installed the noarch pkg. works for me at least...
good luck!

by TuxCane (not verified)

some of the mirrors don't have all the files ... try the KDE FTP =(

by Mathi (not verified)

Even I don't find the artsbuilder package... for SuSE 9.0

by DiCkE (not verified)

A good thing is to look in the supplementary directory on any ftp that has the SuSE distribution.

And dont use --nodeps!! Solve the conflicts, otherwise U end up with a broken dist!