I am running KDE 4.7.4-1 on Arch and am having various problems. I am new to KDE, Arch and Intel hardware. I am not completely new to Linux but I have only been using it for a few months.

I am having several issues in KDE. (Plasma seems to crash much too often for my liking and after I go through the bug report questions it always says there's insufficient information and the report is not worth sending.)

Top annoyance: primary click on the desktop background switches to virtual desktop 1. I found a hint somewhere which suggested switching to the "Desktop Icons" activity so I tried that but it made no difference.

I also tried configuring the primary click to do something else by secondary clicking on the desktop and using desktop settings to set "left click" to "standard menu". That meant that I had "left click" and "right click" set to "standard menu". However, primary click still switched to virtual desktop 1 which secondary click opened the menu.

I am assuming that KDE (confusingly) is insisting that "left click" is primary and "right click" is secondary since secondary click does get the standard menu.

How can I stop primary click snapping back to virtual desktop 1? This is something I tend to do a lot out of habit and it is driving me nuts.

In case it is relevant, other odd behaviour:
- cannot add a "default" panel - crashes plasma and did so before I'd configured virtually anything
- problematic behaviour of more than one panel - on reboot, second panel ignores all primary clicks or responds just by switching to virtual desktop 1 (I've now given up on the mutli-panel idea which is too bad as I'm used to having two).
- entirely non-responsive desktop toolbox (very occasionally randomly came to life but usually not) which I've for now managed to remove using ihatethecashew on the grounds that ihatethenonworkingcashew
- I could never move the desktop toolbox - it was one of the first things I tried to do
These are all things I can work around, though. I just mention them in case they cast light on the thing which is really driving me up the wall.

Please let me know if I've used KDE's terminology incorrectly or not supplied the right information - I feel a bit lost.

Thanks.

Something seems seriously wrong with your Plasma configuration given the behaviour you are seeing. If you try the following (which will erase your Plasma configuration) does anything change?

Code: Select all

killall plasma-desktop
mkdir ~/old-plasma-config/
mv $(kde4-config --localprefix)/share/config/plasma* ~/old-plasma-config/
plasma-desktop &

Thanks. OK. So I followed your instructions except that I moved my old config files to a different backup directory so I'd remember where I'd put them.

When I restarted plasma-desktop, I got these messages:

Code: Select all

Object::connect: No such signal QDBusAbstractInterface::Changed()
link XMLID_34_ hasn't been detected!
link XMLID_34_ hasn't been detected!
link XMLID_36_ hasn't been detected!
QGridLayoutEngine::addItem: Cell (0, 1) already taken
plasma-desktop(6492)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application


Right now I haven't changed anything. Primary click is not changing virtual desktops so that's very good. The desktop toolbox is now responsive. And I've just added a second default panel.

However, I then removed the original panel and plasma immediately crashed. I can, however, add and remove a further default panel without a crash.

I've now reconfigured a single customised panel more-or-less as before and moved the cashew to bottom right so the panel doesn't conflict. And still primary click isn't switching desktops.

Thanks! It is sometimes difficult when you are new to something to know if it is you, a "feature", a bug or something weird...

I was going to mark this "solved" but I'd like somebody to tell me whether the above output on restarting plasma is normal or not. (Assuming somebody knows.) Then I'll definitely mark it.

That output is normal from what I can tell. They are warnings of minor internal problems, but nothing you can solve, and they don't impair the operation of Plasma Desktop.

Hi, everyone. Today I met the very same problem, and after some inspecting inspired from this topic, I found my problem is caused by a failed attempt to add a Pager Plasmoid to my only panel this morning.

The Pager Plasmoid contains very large dimensions so cannot be displayed. But any click on the desktop will be considered as clicking on the Pager Plasmoid.

I remember my attempt to add the Pager was failed because either I didn't install some library, or I have only one virtual desktop at that time.

Hope that helps.