The KDE 4.6 beta 2 issues thread

I had a problem originally with widgets mysteriously moving about on the panel. I had locked them (or so I thought) a long time ago.

If you can see the goofy cashew-shaped thingy on the panel your widgets aren't locked. And yes, the widgets have a tendency to wander if not locked.

well good going this has never been an issue before. but hey I understand it now. It makes since for systems that run with different permissions or systems that have very little security. We know KDE runs on many systems.

I think I just figured it out: everybody who's having this problem, try locking your widgets and THEN launching the app from the panel icon.

Thanks 2handband been scratching my head reading the config's and rc files. Built beta2 from scratch today.

If someone is into webcam/microphone capturing, I just spotted this:

Casian Andrei's project "Phonon Capture API" involved implementing support for various capture devices (such as webcams or microphones) in Phonon. Currently,it works with Video4Linux devices for the Phonon VLC backend; ALSA capture should also work, but it is not well tested. Casian explains: "This means that multimedia applications that use Phonon will be able to access capture devices with ease. Eventually, the normal user will be able to use capture devices with KDE applications, but it will take a while until this happens. I plan to continue working on this until it is functional at a large scale."

I don't know if this made into 4.6 (I think it has been merged into the experimental phonon branch), btw that article (and the preceding) are nice showcases of possible future kde features

Originally Posted by Alien Bob Sounds like one of the programs you are running is buggy and creates lots of client connections. You can check with one of these commands which X clients are connected: xlsclients netstat -ap | grep X11 Eric

Thanks i have only had the error once since posting but unfortunately i did not have time to look into it. I will wait for it to happen again and see if i can work out what is causing it.

I had a problem about a month ago with slow booting. It resolved itself somehow. Now that I'm using the newest KDE, the slow boots are back. Originally, I could boot to a kde desktop in less than a minute. Now it takes about 2 1/2 minutes. That's still way better than the 5 minutes to get to a useful Vista desktop, but slower than It used to be. This is not a real problem, as I don't reboot that often - maybe once every two weeks. I was just wondering if anyone else is noticing slower boots.

I also have not done a clean install since x86_64 was first released. I've been rolling along with -current since.

The new KDE is faster, and it seem to take slightly less memory than 4.5. Good. However, after the first minutes, I can't start applications :S

Invoking the application from a terminal window outputs: "No protocol specified" a number of times, and finally "Cannot open display :0". Go figure...

Originally Posted by sombragris The new KDE is faster, and it seem to take slightly less memory than 4.5. Good. However, after the first minutes, I can't start applications :S Invoking the application from a terminal window outputs: "No protocol specified" a number of times, and finally "Cannot open display :0". Go figure...

Check if your hostname is set. I remember having such issues when *something* cleared my hostname. I haven't up to now figured out what actually did unset my hostname and it went away after a while so it's kinda hard for me now to trace it again, but what you describe sounds pretty similar to what I experienced.

When KDE starts it writes something about missing power-management back-end. Do I miss something? It pop-up and I do not have enough time to read it. I tried to check logs, but no sign is there. Battery widget shows on the panel but it seems that changing of brightness and etc doesn't seems to work.

EDIT: ok it seems that on kde-4.6-beta2, powermanagement doesn't work yet by default without HAL. It should be fixed in the newer beta(s) or rc(s). (On some forum I've seen that people reporting that if they log out from KDE session and log in again, it start to work. Didn't check it yet.).

EDIT2 (24.12.2010): upgrading to 4.5.90 solved this issue. Thanks, Eric. Merry Christmas en gelukige niew jaar!!!

Originally Posted by 2handband I think I just figured it out: everybody who's having this problem, try locking your widgets and THEN launching the app from the panel icon.

Seems to be fixed properly in RC1, anyone else tried?

Well, crapola. K3b complains it can't find an optical drive. Make sure hal is running. Hal is running. One to figure out later.

I'm feeling rather stupid by asking this, but does anyone know where is the policykit configuration tool? I can't seem to find it anywhere. The thing is that I need to see something about udisks, related to this thread: http://www.linuxquestions.org/questi...9/#post4202381

Did you looked at

system settings => system administration => global policy configuration

Kind regards

system settings => system administration => global policy configuration

From this point, there's nothing like you mentioned. Now I think I truly missed something.

EDIT: Sorry... solved it, really it was stupidity of mine - missed polkit-kde-agent-1-0.99.0-x86_64-1alien.txz and polkit-kde-kcmodules-1-20101202git-x86_64-1alien.txz

Originally Posted by mlangdn Well, crapola. K3b complains it can't find an optical drive. Make sure hal is running. Hal is running. One to figure out later.

I had this same problem and just discovered that all you need is to have a disk in an optical drive before you start k3b.