Version: unknown (using 4.2.2 (KDE 4.2.2), Debian packages) Compiler: cc OS: Linux (i686) release 2.6.28 creating a dbus-command shortcut seems incomprehensible: - no explanation, what remote application makes different from remote object and where to obtain that info - "launch dbus-browser" fails, because qdbusviewer is not installed -- and doing so pulls in a bunch of other dependencies (libqt4-dev{a} libqt4-opengl-dev{a} libqt4-scripttools{a} qt4-designer{a} qt4-dev-tools qt4-doc{a} qt4-qmake{a}, "Need to get 68,3MB of archives. After unpacking 106MB will be used.") and after that nothing really changes, since the qdbusviewer has not much more to offer, namely the application vs object question is not answered
Reassigning
still basically unusable. i try to setup a very simple example of using the play/pause button of my keyboard, but am immediately presenetd with still the same hardly usable interface. - hitting "launch dbus-browser" presents me with an even less useful interface - typing "amarok" in the search field just out of desperation presents me with three entries in the left section (which is, probably not to confuse me, doesn't have any lable at all): org.kde.amarok org.mpris.MediaPlayer2.amarok org.mpris.amarok - browsing the right section, which is at least labelled "Methods" unfolds an unsightly number of entries, whose unfold to even more entries - trying the most sensible looking "Method: PlayPause" inevitable returns an error (for each of the three left-side entries!) "Unable to find method PlayPause on path /Player in interface org.freedesktop.MediaPlayer" i really fail to grasp the whole idea behind this configuration. it has no usefull self-explaining interface, it sends the user into maze of incomprehensible options, and that doesn't even work.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!