So, does org.kde.Spectacle show up there, and does a Spectacle window open if you click on “Method: StartAgent” in org.kde.Spectacle?
- On the button of “Launch D-BUS Browser”
This button works in the fresh user profile although not in my current profile.
So you do have qdbusviewer installed, but you cannot run it in the standard user account it seems.
It may be the same with qdbus.
What error message do you get exactly if you type “qdbusviewer” or “qdbus” into Konsole?
Does “/usr/bin/qdbusviewer” or “/usr/bin/qdbus” work?
- On a new shortcut
I try to create a new global shortcut in System Settings -> Shortcuts -> Custom Shortcuts. I set it to be a “Command / URL” and set a hotkey for it. This works well although only being equivalent to what the old “PrtSc” can do.
Spectacle does accept command line arguments.
E.g. “spectacle -a” or “spectacle --activewindow” will take a snapshot of the active window.
See “spectacle --help” for all of them.
May be a workaround until we can fix the problem.
If I select “D-Bus Command” and fill the fields with the same as those in the entry of “Start Screenshot Tool”, this won’t work.
- on libqt4
I checked with zypper search and found that I have libqt4 installed from repo of openSUSE-Tumbleweed-Oss.
Ok, it should be there by default, and libqt4-x11 (i.e. qdbusviewer) too.
I just thought it got uninstalled because you wrote that you don’t have those commands.
But yeah, as I already mentioned, it would have been strange then that it would work on a fresh account…
- on the account
I merged my backed up account files into this new system. Maybe this merge caused the problem. And so, a fresh account does not have this problem.
Yes, it’s obviously some problem with your user account.
The question is what.
Do you think it is possible to regenerate all user profile (my current account) without damaging the user data, those not originally included in user profile, in it? Or just the part related to dbus?
There is no “part related to dbus” in the user profile.
Actually there’s not even much like a “user profile” either.
There are just config and data files that are located in your home directory.
And as I indicated already, I don’t really think this could be caused by some broken config file really.
Maybe some user startup script “corrupts” the command path?
What do you get if you enter “echo $PATH” into Konsole? And “which qdbus”?
My main suspicion here still is that “qdbus” cannot be run for some reason, just like apparently “qdbusviewer” cannot be run for some reason, though it works on the fresh account.