-> Announced in the Changelog.

-A

yes...i updated into current.
but after that i cannot login into my user, but using root i can login.
what happen with my slackware?

I upgraded to KDE 4.4.5 on my AAO netbook using slackpkg without issue this morning. Since I usually hibernate instead of shutdown I rebooted the netbook just in case. My previous KDE settings appear to remain in tact so no surprises yet.

Updated my -current boxes without issue. Many thanks to Eric Hameleers for his excellent work.

Hi, How did you updated it?

* Edit: I updated mine via slackpkg and took care of:
/etc/kde/kdm/kdmrc.new
/etc/kde/kdm/backgroundrc.new

No issues here, thank you Eric, Pat and the Slackware team.

The changelog mentions k3b being upgraded to version 2.0.0, but in fact the previous version still exists in the tree (both are currently present). Is there any reason to keep the old version around? Furthermore, both are present in /slackware64/kde/, which is a bit weird.

There is a new KDM group that you have to be a member of to login via kdm. Eric had a patch to prevent that in his packages, but I don't know who built the packages in current. I would think that if you can't login, either your /home/YOURUSER directory's permissions went goofy or somehow the patch didn't take, maybe from an incomplete upgrade, but that's just a guess.

with slackpkg upgrade-all

and after that, there's a question appear:
are u want to overwrite the older files... then i select overwrite.

after that, i can't login to my user in every WM. but with root i can.

why?

What happens from runlevl 3 if you do as your user?

I did exactly the same thing with the 2 files I mentioned in my previous post, launched KDE, then fluxbox and had no problem at all, did you overwrite another file? Maybe try as root: find /etc/ -name "*.new" just to make sure. Also try damgar's advice. I can't think of anything else, hopefully somebody else does.
Good luck

I can think of another cause for the "root can start X but normal accounts can not" issue.

An X session can not start if it can not write to /tmp . This can happen when:

(1) the partition which holds directory /tmp is full. A root user can still write to a ext2/ext3/ext4 partition after it has filled up for normal users.

(2) the permissions for the /tmp directory have changed so that normal users no longer can write there. When you run "ls -la /" then the output line for the /tmp directory should start with "drwxrwxrwt". If not, then the permissions for /tmp can be repaired with this command: Eric

1 members found this post helpful.

thx eric...my problem solved...

Because 13.1 is still "fresh", can I update all these KDE related packages being that they are -current?

The only thing so far that doesn't work properly is within system settings, where the Desktop effects say that compositing is not supported, so the enable desktop effects tickbox is greyed out, yet it also says that compositing is active, and my normal wobbly windows etc are working correctly. A bug or a feature? who knows.

Works fine here, and the new QT has resolved some graphics glitches I was seeing, so pretty happy with it now.