MAR
17
2005

KDE 3.4 is Out

KDE 3.4 has been released today. "After more than a half year of development the KDE Project is happy to be able to announce a new major release of the award-winning K Desktop Environment. Among the many new features that have been incorporated, the improvements in accessibility are most remarkable." Read the full announcement for an overview of the many changes. You can download source and binary packages from download.kde.org or use the Konstruct automatic build tool.

Lars Stetten from the accessibility user group Linaccess said about the release: "The new accessibility features in KDE 3.4 are an important step for the future, to enable disabled people to get to know the KDE desktop and to join its community."

As well as the new accessiblity features major improvements have been made to KPDF, groupware server support for Kontact and Kopete, HAL support for detection of removable media and the inclusion of Akregator RSS feed reader. In total 6,500 bugs have been fixed and more than 1,700 wishlist items fulfilled.

Many thanks to all of KDE's hard working developers, translators and helpers.

Comments

I will certainly take a step back but I do expect to remain involved with KDE, just not in a development role. Keeping up to date of what's happening and what's hot within the developers/contributors world is part of the new job though ;-)


By Waldo Bastian at Fri, 2005/03/18 - 6:00am

Wow. Well thank you Waldo for your contributions. They have been immensely appreciated. Good luck at your new job.


By Leo Spalteholz at Fri, 2005/03/18 - 6:00am

Glad to hear you will at least keep following all the developments (hopefully including giving input when requeted). I consider most of Kiosk and its utilities & documentation as your claim to fame, so it would be a shame if that all goes downhill after your leaving.


By ac at Fri, 2005/03/18 - 6:00am

Your development skills will be surely missed! Hope you will have fun at your new job.


By Christian Loose at Fri, 2005/03/18 - 6:00am

Waldo, good luck for the future - KDE is going to miss you for sure.


By David Ankers at Sat, 2005/03/19 - 6:00am

Konstruct is a handy build utility, but it failed first time through because I had a space in my Konstruct install path.

Congratulations to the KDE team on another excellent release.

Long may KDE prosper!


By Robert Knight at Thu, 2005/03/17 - 6:00am

I've been using KDE on Solaris10... I'm using KDE 3.3 'cos only 3.3 binaries are available for solaris10. But I find KDE 3.4 Solaris 9 binaries under "3.4/contrib/Solaris/GCC/9"
Will that work on solaris 10?


By Mathi at Thu, 2005/03/17 - 6:00am

Since there was no RC2, how is this different from RC1? Judging by the size of the packages this obviously isn't RC1, but where can RC1 users learn about the differences or at least get a figure of how much this changed since?

By the way, I am in great debt with the KDE team, I absolutely love this project! Thanks so much!


By Pilaf at Thu, 2005/03/17 - 6:00am

> Since there was no RC2, how is this different from RC1?

Showstopper and security fixes.


By Anonymous at Fri, 2005/03/18 - 6:00am

In my opinion a little thing is missing in the Announcement:
A list of all programs that ship with the release.
This should be mentioned on the info page IMHO.

Nevertheless: Congratulations to the KDE-Team!

Peter


By PJ at Thu, 2005/03/17 - 6:00am

I'm building it with konstruct. But I'm getting this compilation error in the kdepim component:

In file included from conduit_notepad_la.all_cc.cc:2:
notepad-conduit.cc: In member function `int
NotepadActionThread::unpackNotePad(NotePad*, unsigned char*, int)':
notepad-conduit.cc:235: `struct body_t' has no member named `dataType'
make[6]: *** [conduit_notepad_la.all_cc.lo] Error 1
make[6]: Leaving directory `/usr/local/src/kde/kde3.4/konstruct/kde/kdepim/work/kdepim-3.4.0/kpilot/conduits/notepadconduit'
make[5]: *** [all-recursive] Error 1

Can anyone help? I'm using Redhat 9.0 with gcc 3.2.2.

Another thing I noticed is that konstruct is missing a Makefile under konstruct/apps, how do I build the apps then, without doing make in each individual app?


By ac at Thu, 2005/03/17 - 6:00am

Not sure, but it built fine for us to provide rpms.

Could be a problem with using --enable-final (we usually omit that now).


By Rex Dieter at Fri, 2005/03/18 - 6:00am

I found the error, RedHat 9.0's pilot-link is at version 0.11.5, the kdepim conduit plugin requires 0.11.8, an included struct has a new field.

The konstruct build target is fine, the apps target are included in meta/everything.

I got another compile error in kdeaddons about a missing krb5.h, a Google search found that this is another RedHat peculiarity, which places the kerberos headers in /usr/include/kerberos.

I know what people might say about me using RH, but this is my work machine and I have no control over which OS is used. I run SUSE at home.


By ac at Fri, 2005/03/18 - 6:00am

Feel free to use our RPMS from http://kde-redhat.sourceforge.net/

IMHO, a lot easier than building it all by-hand or via-konstruct.


By Rex Dieter at Fri, 2005/03/18 - 6:00am

same problem here


By Nabegh at Thu, 2005/03/31 - 6:00am

Even I am facing the same problem.

Any solution to get it working. I am specifically interested in KMail. Hence I am upgrading the KDEPim package using construct. Following is the terminal window snapshot...
In file included from conduit_notepad_la.all_cc.cc:2:
notepad-conduit.cc: In member function `int
NotepadActionThread::unpackNotePad(NotePad*, unsigned char*, int)':
notepad-conduit.cc:235: `struct body_t' has no member named `dataType'
make[6]: *** [conduit_notepad_la.all_cc.lo] Error 1
make[6]: Leaving directory `/home/admin/rohit/installers/kde/konstruct/kde/kdepim/work/kdepim-3.4.0/kpilot/conduits/notepadconduit'
make[5]: *** [all-recursive] Error 1
make[5]: Leaving directory `/home/admin/rohit/installers/kde/konstruct/kde/kdepim/work/kdepim-3.4.0/kpilot/conduits'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory `/home/admin/rohit/installers/kde/konstruct/kde/kdepim/work/kdepim-3.4.0/kpilot'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/home/admin/rohit/installers/kde/konstruct/kde/kdepim/work/kdepim-3.4.0'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/home/admin/rohit/installers/kde/konstruct/kde/kdepim/work/kdepim-3.4.0'
make[1]: *** [build-work/kdepim-3.4.0/Makefile] Error 2
make[1]: Leaving directory `/home/admin/rohit/installers/kde/konstruct/kde/kdepim'
make: *** [dep-../../kde/kdepim] Error 2

Thanks in advance

Rohit


By Rohit Bhosale at Tue, 2005/04/19 - 5:00am

Is it just me, or does kpdf handle fonts significantly worse than xpdf (and acrobat reader)?

I've attached a snapshot of both kpdf and xpdf rendering the same PDF file. The top is kpdf, the bottom xpdf. Both are at 100%.

Anyone else seeing such a discrepancy?


By KDE User at Fri, 2005/03/18 - 6:00am

It's always helpful to say what version you're using.
KPDF 3.4 isn't comparable at all to the old version.


By ac at Fri, 2005/03/18 - 6:00am

Since this was a KDE 3.4 topic, I assumed that it would be clear I'm using KDE 3.4. If not, well... This is with KDE 3.4.


By KDE User at Fri, 2005/03/18 - 6:00am

Yeah, you're right. I was just very surprised because the font quality of KPDF in the KDE 3.4 version vastly improved for me. I haven't had any problems since I switched.

I'm sure the KPDF developers a really interested in a bug report for this. Especially when you're able to attach the PDF.


By ac at Sat, 2005/03/19 - 6:00am

Yes, I have the same problems. I have been anxiously waiting for KDE 3.4 hoping that things would be solved. Alas, this problem was not fixed.
There is a bug report on the KDE database, but it was closed for some reason.


By Elad at Fri, 2005/03/18 - 6:00am

Maybe hinting? The screenshot shows that KPDF uses hinting, while xpdf does not. Maybe you could change this behaviour in the font-tab in the control center.


By Hans Chen at Sun, 2005/03/20 - 6:00am

I have had trouble with KMail since the rc1 release,and I thought it was just something that would be ironed out. Somehow, I cannot send email at all! At the release of the 3.4, the same problem is still present., even after telline KMail to check what my ISP's server supports! I googled and came across advice that I should install everything cyrus-sasl*. This I did and I am now able to send email. Question is: Why don't the developers somehow get this cyrus* stuff bundled in such a way that it gets installed?


By charles at Fri, 2005/03/18 - 6:00am

I had the exact same problem. Read an old posting about installing cyrus. Checked and I did have cyrus installed; but only the 1st package. Installed all of the packages and now everything works as it should. Was surprised that it wasn't caught by Yast as an issue.....


By IronMan at Fri, 2005/03/18 - 6:00am

How come Cyrus wasn't needed before, but KMail still supported authentication? Was there built-in auth code that was removed?


By AC at Fri, 2005/03/18 - 6:00am

In order to add support for new authetication methods (NTLM (Microsoft Windows) and GSSAPI (Kerberos)) we switched to using the cyrus-sasl library which supports all those authentication methods.


By Ingo Klöcker at Fri, 2005/03/18 - 6:00am

Oh. Maybe the old auth code could be used for people without Cyrus?


By AC at Fri, 2005/03/18 - 6:00am

It's not cyrus. It's just cyrus-sasl.

Cyrus-sasl is a whole 45388 bytes, plus 790K of libanonymous and libsasldb.
Since it is the first library that fixes the pathetic mess client-side auth is in unixland, and that pretty much every modern application shares it, and that it makes the world safer (since centralized auth library means less code to audit, and easier updates in case of trouble), trust me, it's the best 20 cents worth of disk-space you have.


By Roberto Alsina at Fri, 2005/03/18 - 6:00am

Okay, point taken. :-)


By AC at Sat, 2005/03/19 - 6:00am

It can be compiled without SASL, and was in the past. For 3.4 it is compiled with SASL support, but the first SUSE rpms did not include cyrus-sasl-* in their dependencies list, so you could install the rpms, but kmail would miss SASL at runtime. The next rpms will have that fixed.


By Will Stephenson at Fri, 2005/03/18 - 6:00am

I've installed kde 3.4 on mandrake 10.1 and I have same problem, there is also problem with konqueror that cannot connect to sites with user authentication. I've installed all cyrus* packages
available ( include cyrus-sasl ) but it does not help. Any idea how to solve problem? thanks


By Pini at Wed, 2005/03/30 - 6:00am

I still find Konq to be too slow in opening a directory onto my drive. I have a SATA 200Gb drive hooked up to 1Gb of memory and an AMD64 3200.


By Mike at Fri, 2005/03/18 - 6:00am

Good for you!


By Troll-o at Thu, 2005/03/24 - 6:00am

I upgraded Suse 9.1 to KDE 3.4 via Yast. Everything went well; but as with the last upgrade to 3.3.2 (...and the version or two before, if I remember right), I found that system sounds did not work at all. Previously, I found it was because of the arts build. At that time, someone else built arts on their end from the source and posted it, which fixed my problem (...and that of many others with the same issue). Not sure of why this seems to be the norm or if it can be fixed by KDE or Suse this time around. Other than that, so far I'm VERY happy with the upgrade. Thanks go out to the KDE Team - Your efforts are very much appreciated.


By IronMan at Fri, 2005/03/18 - 6:00am

I had the same problem. I downloaded the arts source rpm from Suse and rebuilt it and now everything works fine.


By Flitcraft at Fri, 2005/03/18 - 6:00am

I'm running Suse 9.1 Personal - Installing RPMs is fine, but building them is another matter. Any assistance or direction that anyone can give would be appreciated.


By IronMan at Fri, 2005/03/18 - 6:00am

Here's what I did:

Download this file:
ftp://ftp.suse.com/suse/i386/supplementary/KDE/update_for_9.1/source/art...

Open a konsole, cd to the directory where you saved the file and run (as root):
rpmbuild --rebuild arts-1.4.0-8.src.rpm

This will most probably give you some failed dependencies. The missing packages must be installed from the Suse disks. When you have installed everything needed, run the command again.

If all goes well three new rpm files (arts, arts-devel, arts-gmcop) will be present in /usr/src/packages/RPMS/i586 (or in the directory corresponding to your arch). Install them with:
rpm -Uhv --replacefiles --force /usr/src/packages/RPMS/i586/arts*

Hope that helps.


By Flitcraft at Fri, 2005/03/18 - 6:00am

THANK YOU!

Yes, it helped.... :-) I did as instructed: Had to install 30+ RPMs to cover dependencies, then did Online Update to update those, then finally a couple of updates from the Supplementary to bring it all up-to-date before it all built correctly the first time and installed without a hitch.

It's been a while since I did any compiling/building.... In fact, hadn't done so since upgrading to Suse 9.1 Personal when it first came out. Thanks for the reminder.... ;-)


By IronMan at Sat, 2005/03/19 - 6:00am

Hi,

i get following error after i upgraded Suse 9.2 to KDE 3.4:

Could not start process Unable to create io-slave: klauncher said: Unknownn protocol 'file'.

Also i dont have any shortcuts on panel and i have empty main panel menu.

Did anyone experienced this?

Regards,

Marek


By MK at Fri, 2005/03/18 - 6:00am

When i run for example kcontrol i get this:

krejza@ares:~> kcontrol
kio (KSycoca): WARNING: Found version 75, expecting version 79 or higher.
kio (KSycoca): WARNING: Outdated database found
kio (KSycoca): ERROR: No database available!
kcontrol: WARNING: No K menu group with X-KDE-BaseGroup=settings found !
Defaulting to Settings/
kio (KSycoca): WARNING: Found version 75, expecting version 79 or higher.
kio (KSycoca): WARNING: Outdated database found
kio (KSycoca): WARNING: Found version 75, expecting version 79 or higher.
kio (KSycoca): WARNING: Outdated database found
krejza@ares:~> kio (KSycoca): WARNING: Found version 75, expecting version
79 or higher.
kio (KSycoca): WARNING: Outdated database found
kcontrol: ERROR: : couldn't create slave : Unable to create io-slave:
klauncher said: Unknown protocol 'file'.
kcontrol:
kcontrol: ERROR: : couldn't create slave : Unable to create io-slave:
klauncher said: Unknown protocol 'file'.
kcontrol:

krejza@ares:~>


By MK at Fri, 2005/03/18 - 6:00am

Ok i got fix for this: :)

rm /var/tmp/kdecache-$USER/ksycoca*


By MK at Fri, 2005/03/18 - 6:00am

finnish the install (if you're not ready yet) and log out - and in again. should fix it.


By superstoned at Fri, 2005/03/18 - 6:00am

Just hang there with no response in my case.
Anyone else experience this?


By idlecat at Fri, 2005/03/18 - 6:00am

Hi! Yes, you are right. As I also seen, Kopete don't know how to work with proxy. I am using a proxy to have access to internet, and I can't configure Kopette to use that proxy.


By Daniel C at Sun, 2005/07/24 - 5:00am

I still have this problem with kopete
Qt: 3.3.1
KDE: 3.2.1
Kopete: 0.8.1

Still no solution???


By Steve at Wed, 2005/07/27 - 5:00am

Tried a current Kopete version?


By Anonymous at Wed, 2005/07/27 - 5:00am

try 0.12 versions


By bhaki at Mon, 2006/11/20 - 6:00am

Excellent release!

There's just one thing I want to know: how can the multiple To: lines in KMail's composer window be disabled?


By Flitcraft at Fri, 2005/03/18 - 6:00am

There is no sane reason why you'd want to disable these. So, what is your reason? ;)


By Max Howell at Fri, 2005/03/18 - 6:00am

Not all reasons have to be sane. Transparent menus aren't the pinnacle of sanity, or are they?

I just don't like it. On first glance I thought it was a bug. Inserting half a dozen recipient addresses makes the window look silly.

Just my opinion.


By Flitcraft at Fri, 2005/03/18 - 6:00am

Pages