I upgraded to KDE 4.6 beta2, and my pre-existing panel icons work fine. But when I add a new one it doesn't do anything. Widgets all work fine; I'm talking about application icons here. When I click on it, it does not launch the program. I added a new user and the problem reproduces.

can confirm

posted bug report https://bugs.kde.org/show_bug.cgi?id=260596

If you mean the same icons I think you mean (i.e. the ones you can add by, for example, right-click on the program in question in Kickoff and select "Add to panel") they work fine here. True, I only have one such icon but since I re-created my entire plasma-setup upon upgrading I know it's not a "leftover" from my 4.5 setup. 4.5.86 is what I use (beta2 + some additional commits).

Kryten2X4B - the "add to panel" adds to the original panel, not to any additional ones

after testing "add to panel" any app launchers added to the original default panel is not working either, maybe recreating entire panel or starting with clean plasma config files resolves the bug (?)

google01103 wrote:Kryten2X4B - the "add to panel" adds to the original panel, not to any additional ones

after testing "add to panel" any app launchers added to the original default panel is not working either, maybe recreating entire panel or starting with clean plasma config files resolves the bug (?)

I tried it in my user account with new panel, problem persists.

google01103 wrote:Kryten2X4B - the "add to panel" adds to the original panel, not to any additional ones

Sort of. It adds it to whatever panel kickoff itself is running in which isn't necessarily the original one. Anyway, I've tried it in both my panels, both by using "add to panel" and drag-and-drop and I'm unable to reproduce this behavior.

So, I can see three possible reasons why it happens for you and the OP but not me:

1. The bug is circumvented on my system because I started with a clean-slate. Which is easy enough to check if one or both of you backs up your plasma* files and start with a clean-slate as well, even if just temporarily.
2. If you two run 4.5.85 rather than 4.5.86 like me, it could be that a bug has been fixed in between that causes this.
3. I don't know which Suse-repos you are using or if you compile KDE yourself, but I'm using the Unstable ones. It could be that those repos have additional patches used that Slackware and whatever packages you are using don't have.

Okay, 3 is grasping at straws really...but I certainly think mv'ing the plasma* files out of the way is worthwhile to rule out one potential source of the problem.

Kryten2X4B:

I'm using Factory 4.85.85

It appears the bug is circumvented on your system because you started with a clean-slate.

I have been using the same configuration file for Plasma for several months now, and can't reproduce this.

Code: Select all

ben@bianca:~> plasma-desktop --version
Qt: 4.7.2
KDE Development Platform: 4.5.86 (4.6 >= 20101210)
Plasma Desktop Shell: 0.4

Built less than 24 hours ago from SVN.

bcooksley - maybe fixed in 4.86 ?

Could be, yes. I do remember a period when my Opera launcher wouldn't work.

fixed in trunk https://bugs.kde.org/show_bug.cgi?id=260596#c3

google01103 wrote:fixed in trunk https://bugs.kde.org/show_bug.cgi?id=260596#c3

Great!

On kubuntu 10.10 (maverick) kde4.6 Bet2

I got this regardless if I started with a clean plasma or not.

I had to deactivate widgets, then the app. widgets worked.

Se What RC brings

I discovered that it works fine with the widgets locked.