KDE 3.0.3 Released

The KDE Project is happy to announce the release of KDE 3.0.3,
an update for KDE 3.0 with further bugfixes and an important
security fix.
Read more in the announcement and on the
KDE 3.0.3 Info Page. Credits go to
Dirk Mueller for his tireless work as release coordinator. Thank you Dirk.

Dot Categories: 

Comments

hi,
i got the same problem with the locked screen but fixed it with the
tips below.

the other thing you mentioned appears here too.
every time i login, the clock moved to the left side of the screen.
the same happens with desktop chooser. and my icons on the left panel
(SuSE 8, packages from ftp.kde.org)

any fixes for that one???

thanks in advance.
matze

When you create a user in linux to ftp with, and that user password contains a "-" in it, then the password is rejected. You can get around this by doing the following :-

vi /etc/pam.d/ftp

and hash out the line with :-
"auth required /lib/security/pam_stack.so service=system-auth"

but then you lose all security. I have tested all symbols. And the only one it doesn't line is the minus sign '-'.

Pls let us know if anyone has a work around, other than a cheat..!
Thnx

i know this has nothing to do with your prob but im loking for a person by the name of talitha if you are her family please please let me know because she was very dear to me i was her best friend in florida my email [email protected]

by PEGGY L.SWANGO (not verified)

I NEED HELP

Hi.

I have exactly the same problem. Installed 3.0.3 for SuSE 7.3 from ftp.suse.com yesterday and noticed the problem after early morning coffee break.

Here is a better workaround than Ctrl Alt F1 an kill the session:
Login as yourself on the console and kill kdesktop_lock.

Martin.

Hi, yes, that may be the only way.. ;_;
but, i hate that, because, everytime i starting KDM or the other way, switching from KDM or a running KDE-Desktop to the simple Console with (Contr.+Alt+F1) , then it takes HOURS, ok, at least 15-20 Seconds till the switch is completed. I DON'T KNOW, what is the reason for that..
i have got a RivaTNT and of course the latest driver from Nvidia.com installed, (2960). with 2880 it is the same. Everything is just normal when
i use the standard 'nv' driver, but then, 'overlay'or fullscreen in some cases isn't supported. example Noatun: right mouse-click switches at once to real full-screen mode. i am running kernel 2.4.19, but everything is the same with 2.4.18, on my SuSE 8.0

i guess, that depends on the "nvidia" driver. but it is really nerving, waiting so long to get the login-screen or back to console. (;_;)
THANKS for all help..

(by the way, which newsgroup or mailing list is best for such problems ?) :)

Hi again, i tried "kill -9 kdesktop_lock", but that doesn't work..
i just get back to the KDM. But, switching to Console 1 was fast, but
the other way takes a long time..

An even better hint to deactive the lock is to do this

1. Switch to console (Ctrl+Alt+F1)
2. dcop kdesktop KScreensaverIface quit
3. Switch back to X...

This also means that if you just want to test if it works after you have tweeked the screensaver a bit you can do this

1. Start a konsole
2. sleep 15; dcop kdesktop KScreensaverIface quit

If you don't enter right password within 15 seconds dcop will quit the saver for you... :=)

/Perraw

FOR GOT MY PASSWORD ON ORUAM71

Cant unlock when u lock screen??????

Solution: run 'chown' with root for the kcheckpass utility.

by Kevin Haddock (not verified)

I have exactly the same problem with a Fujitsu Laptop running Mandrake 9.1. If I let the screen saver come on and the lock runs it won't let me back in even though I type the correct password. How do I rectify this (or just disable it -- I tried in config/kde/look and feel/screensaver to no avail)?

Thanks,

-Kevin

by Michael Granado (not verified)

Changing the suid bit on the file /usr/bin/kcheckpass seems to fix the problem:

chmod 4755 /usr/bin/kcheckpass

thanks, it's working now again.
don't know how, why... i tried with the hints above, but no change,
later, after shutdown, booting old (2.4.18) Kernel, (there lockscreen worked) then booted again 2.4.19, then worked, argh!
:)

I had the same problem (Suse 8),
but I remembered this from an earlier KDE upgrade,
The new KDE install puts /usr/opt/kde3/bin/kcheckpass in group root
ctrl alt F1 for a new console
login as root
cd /usr/opt/kde3/bin/
chown shadow kcheckpass

Fixed it for me

err... that will be chgrp not chown !doh !

by John (not verified)

> cd /usr/opt/kde3/bin/
> chgrp shadow kcheckpass

That fixed it for me too (SuSE 7.2) .. thanks.

by Lisa (not verified)

I had this problem also (SuSE 8.0). Your suggestion works and you don't seem to need kde3 or kscreensaver3 in /etc/pam.d either.

BTW, SuSE installs kde3 in /opt.

Thanks.

I had the same problem (Suse 8),
but I remembered this from an earlier KDE upgrade,
The new KDE install puts /usr/opt/kde3/bin/kcheckpass in group root
ctrl alt F1 for a new console
login as root
cd /usr/opt/kde3/bin/
chown shadow kcheckpass

Fixed it for me

by removed by request (not verified)

I've just upgraded to RH 8.0 with kernel 2.14-18 (I believe) and the associated KDE3. When I lock the screen and/or leave the laptop for an extended period, the screen goes black. I bring up the password entry but it is denied (with root logged in)! I am able to enter the password and gain access to kde if it is within a few minutes of locking the screen. Any ideas? Does the hard drive in sleep mode prohibit password access?

by dr_lha (not verified)

Odd problem: With the Redhat 7.3 packages Korn no longer seems to detect newly arrived email. I tried reconfiguring korn but to no avail.

by Jared (not verified)

Still showing the same xinerama bugs as kde 3.0.0 3.0.1 and 3.0.2.
KPersonalizer freezes
Kicker freezes whenever a button is pushed
KControl refuses to load
Konsole refuses to load

Is anyone else getting these errors? Because I have reported them several times and they still haven't been fixed. If it's just my system fine, but if it's affecting all xinerama users then when the next series of distributions comes out with kde3, guess how many people will be switching to gnome

by Sebastian (not verified)

Remove the font server in you XF86Config-4 font pathes.

by Jared (not verified)

eh? And replace it with what?
I need it to get my fonts.
What is it supposed to fix?

by Bryan Feeney (not verified)

Replace it with the paths to your fonts. Instead of

FontPath "unix/:-1"

Have

FontPath "/usr/X11R6/lib/X11/fonts/Type1"
FontPath "/usr/X11R6/lib/X11/fonts/TrueType"
FontPath "/usr/X11R6/lib/X11/fonts/TTF"
FontPath "/usr/X11R6/lib/X11/fonts/drakfont"
FontPath "/opt/ttfonts"
FontPath "/usr/share/fonts/default/Type1"

etc.,

Gotta admit though, this is a strange solution to the problem.

by BöNAS (not verified)

It works because you're telling XFree not to use the X Font Server (XFS.)

XFS is a daemon that serves fonts (either to your local X server or to remote machines.) As I understand it, older versions of X (< 4.0) required XFS for their fonts. However, the newer version 4 that most people use has its own built in font server.

Setting your FontPath to "unix/:-1" directs X to use XFT. Commenting that out means you have to specify where the system can find you fonts.

This has completely solved all my problems using Xinerama and KDE 3.1 (kicker, kcontrol, konsole freezing.) I guess XFS + KDE + Xinerama just doesn't work.

by Aaron Peterson (not verified)

partially works for me.

KDE comes up with xinerama... but as soon as I try to move a window between the two windows... choke, death, bye bye everything.

I think it might have something to do with Xauthority and xhost now that I've played with my sytem

xhost +localhost
might work...

I have recieved lots of MIT-magic cookie errors
(gentoo 1.4rc3 gaming-r1)
when trying to open programs (xinerama off)

also i've been wodering if:

Subsection "Display"
Depth 8
Modes "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
ViewPort has anything to do with it

by Aaron Peterson (not verified)

Grr... (sent before I wanted it to)

I attached my XF86config file
and I think I have both screens with ViewPort 0 0
on them...
I have no idea what that is... but it seems evil.

by halux (not verified)

Hi, I have also xinerama support enabled and two monitors.
Make sure you disabled antialiasing. Kde/QT/X uses hardware AA and the 2 head cards only support hardware accelerated things on the fist head.

The xinerama support is more than bad, but I think 3.1 will fix kicker.
I hope that the screensavers and the background will works with two screens in 3.2.

have fun
Felix

by Ravi (not verified)

Hi,
I am using Xinerama with two nVidia cards, and I have had no problems with any freezes, etc. Everything works except for the OpenGL screensavers. I have been running RH7.3 with all regular updates and also the KDE CVS tree 3.0.1. We have 4 machines with Xinerama in my lab with various video card combinations and we have no problems. I suspect your problem is due to misconfigured dual head setup or hardware issues (specifically certain motherboards which do not supply the proper rail voltage for PCI video cards). Please check if you can run sawfish over xinerama. If it does, kwin should not be a problem either.

Ravi

by Jared (not verified)

Curious. Well kde 2.2 works fine in xinerama mode, however it does not use OpenGL like kde 3 does. So the problem is either xinerama OpenGL or a specific problem with Mandrake 8.2's packages. I'm not sure what the purpose of running sawfish would be as opposed to any other window manager. I have been using xinerama under kde 2.2 for a very long time now and it is completely stable.

by Jason (not verified)

Ravi, how do I setup KDE in the inittab in order to use both monitors as one big screen? Right now with the way I have it setup, each screen is it's own virtual environment. I have RH 8.0 install ( KDE 3.0.3-8 ). I'm using 2 NVidia cards ( 3 [adp] and 2 [pci] ). The only way I can get the single "big" monitor to work, where windows can be dragged between monitors is by doing a "startx -- +xinerama"

This is what my inittab is doing:

x:5:respawn:/etc/X11/prefdm +xinerama -nodaemon

The xinerama makes absolutely no diff.

Thanks,

*Email correspondence may get bounced as I haven't updated my DNS due to a new IP address*

by Jason (not verified)

Nevermind, figured it out.

In /etc/XF86Config, in ServerLayout, needed to add:

Option "Xinerama" "on"

by John Bell (not verified)

FWIW, there's a note in the nVidia driver documentation that they do not support OpenGL on both screens with xinerama. Wish they did, but they don't.

by Andrew (not verified)

Hi,

I have exactly the same problem with KDE 3.03 on Mandrake 9.0b4.

Using Xinerama with nv (AGP) and s3 virge (PCI) cards.

Konsole loads sometimes, and Kcontrol always refuses to load.

Rgds,

Andrew

by me (not verified)

Looks like a lot of people are having problem with 3.0.3.
I'll wait for something with less problems.

Something else now. Nobody is saying anything about the new gcc release.
This should improve the boot speed as the developers were claiming when the KDE 2 series appeared.
They told the gcc guys to solve it and they have done it.
Now will we have finally a konqui booting JUST AFTER the mouse click as it should be in a file manager? Will KDE boot in 2-3 seconds?
I hope so :-)
RedHat is pushing for the desktop and KDE will have to look behind. This is going to be challenging. I hope both projects (GNOME+KDE) will improve from that situation.

by fredan (not verified)

Nobody is saying anything about the new gcc release.

I can say something. Yesterday I compiled 3.0.3 with gcc 3.1.1 with options like -march=athlon -mmmx -md3now and they have also enabled objprelink again, so it's fast!

by Delete (not verified)

Thanks for your suggestions.

Recently upgraded to gcc-3.2, and just compiled KDE with objprelink again & athlon flags.

Wow! A huge performance increase, and no compilation problems.

Seems like gcc-3.2 + kde-3.0.x is a very nice combination :)

by Mononoke (not verified)

Hi, how/where exactly is the performance increase ? :)
have got a dual board, 2x PIII 450MHz, 512MB. but KDE is starting up a bit slow.. the 2cd Symbol in the Ksplash remains a long time (it's about 'System services will be initialized' (don't know the exact english message).
of course konqueror-startup takes around 3 seconds too, so i think, faster would be better, at least to introduce a beautiful and fast desktop to XP-users :)
i still use gcc 2.95.1 (like that) but your review about 3.2 is sounds really nice, will that be standard in the next (for example) SuSE 8.x edition ?

greets

by John (not verified)

I just updated from 3.0.1 to 3.0.3 using the SuSE 7.2 rpm's. Now I can't get any Wallpapers to display. Even in the Control Center I can't get the screen image to display anything.

Anyone else seen this?

by John (not verified)

Bugger! The problem seems to be that I can't display any jpg files. Pixie is horribly broken, and kview gives me the following message on the command line.

QPixmap::convertFromImage: Cannot convert a null image

Kicker now wants to left justify all my Applets everytime I logout :-(

by Mike (not verified)

Hello.

I have the same problem. I updated from 3.0.2 to 3.0.3 using the SuSE 7.2 rpm's. There isn't possible to choose any wallpaper in JPG or PNG format. Wallpapers in BMP are working!

I have also problem with wrong password when I lock screen and also problem with moving of applets in the kicker as was written by Mononoke.

by John (not verified)

Is this a general problem with the quality of the 3.0.3 release, or are we looking at a kit build and packaging problem from SuSE?

by mr. nuba (not verified)

same problem here with suse7.3
no pixie no wallpapers.

bye
m.n.

by mr. nuba (not verified)

you have to edit your ~/.qt/qtrc and change the library path to
the correct qt-path (qt-3.0.5).

No probs with wallpapers or pixie or the like.

bye
mr n.

by John (not verified)

> you have to edit your ~/.qt/qtrc and change the library path to
> the correct qt-path (qt-3.0.5).

Thanks mr n. Thas fixed it for my account, but not for root. So I went looking and found a system wide /etc/X11/qtrc. Made the same change there and now root and the KDE login screen are behaving as they should.

You heard anything about a fix for kicker yet?

by mr. nuba (not verified)

Haven't found any official fixed package nor statement from suse.

There's a private patch published in de.comp.os.unix.apps.kde, the message id
is .

The bad news is, that you have to recompile kdebase for yourself after patching.

good luck

mr. n.

by John (not verified)

Think I'll wait for a new rpm from SuSE. Mixing installation methods is only going to cause me headaches later on.

by Hywel Mallett (not verified)

For those who want them, source diffs of the main packages are at http://www.hmallett.co.uk