Version: (using KDE 4.2.96) OS: Linux Installed from: Ubuntu Packages I have just upgraded to KDE 4.2.96 (KDE 4.3 RC2) and now no tasks are appearing on my Task Manager. I have tried adding another panel and adding a new Task Manager to it, but it shows nothing.
Weird... could you try creating a new user account just to test with a clean configuration ? - Have you tried to remove the current taskbar and then add a new one ? Thanks
(In reply to comment #1) > Weird... could you try creating a new user account just to test with a clean > configuration ? ok, done this, and still no applications showing on the bar. > - Have you tried to remove the current taskbar and then add a new one ? > Thanks Done, still no application showing on the bar.
That is really weird indeed. Do you use Compiz, or any other non-KDE application ? If you use Alt+Tab, do the windows appear there ? Thanks
(In reply to comment #3) > That is really weird indeed. > Do you use Compiz, or any other non-KDE application ? No Compiz, I'm not entirely sure about other non KDE applications. > If you use Alt+Tab, do the windows appear there ? Yes, Alt+Tab is good. > Thanks
I can confirm this behavior using Kubuntu Jaunty + KDE 4.3 RC2.
Another Kubuntu user showing this behaviour.. Let see if we get another non-Kubuntu one.
Still happening on RC3 ? I wonder why nobody else reported this...
This may have just been a Kubuntu packaging fluke. I was having this problem on two systems both were running Kubuntu Jaunty and were updated to KDE 4.3 RC2 from RC1. When I updated both systems to RC3 I had dependency problems relating to conflicting files in kdebase-runtime and kdebase-workspace. I battled this out with apt-get and dpkg for a while and now have RC3 fully installed with the task bar working. I noticed at one point that I saw KDE packages installed from 4.2.98, 4.2.96, and 4.2.90. Everything on my system is now up to 4.2.98 only. There could have just been some left over packages conflicting with the ones in RC2 which caused this problem. I don't fully understand how this was allowed by the package manager but this is what I made of it.
Did anyone else experienced this "package mess" ?.
we'd be hearing about this from a lot of people it had persisted. given that there is no feedback from original reporters, marking as a downstream packaging issue.