"jdd" == jdd@dodin org <jdd@dodin.org> writes: Hi Jdd,
jdd> linking *this* in /usr/share/kservices5/ServiceMenus/ServiceMenus jdd> kim_compressandresize.desktop kim_convertandrotate.desktop jdd> kim_publication.desktop mediainfo-gui.desktop jdd> to /usr/share/kio/servicemenus Strange, in the package that I am using, the kim files in /usr/share/kservices5/ServiceMenus/ServiceMenus are just symlinks from /usr/share/kde4/services/ServiceMenus. So why symlinking them from /usr/share/kservices5/ServiceMenus/ServiceMenus works for you, where as symlinking them from /usr/share/kde4/services/ServiceMenus didn't, is beyond me. jdd> makes kim utilities to show in context menu and at least partially jdd> works. I say "partially" because a notice on the bug report say some jdd> may not work and I only test the resize and web options (that worked) qdbus can be found in the "libqt4" package. I have libqt4-4.8.7-1699.458.pm.35.x86_64 from Packman. However, there is a qdbus6 in qt6-tools-qdbus. Looking at the command line syntax it should be as easy as changing "qdbus" to "qdbus6" and "--address" to "--bus". ,----[ Output of qdbus --help ] | Usage: qdbus [--system | --address ADDRESS] [--literal] [servicename] [path] [method] [args] | | servicename the service to connect to (e.g., org.freedesktop.DBus) | path the path to the object (e.g., /) | method the method to call, with or without the interface | args arguments to pass to the call | With 0 arguments, qdbus will list the services available on the bus | With just the servicename, qdbus will list the object paths available on the service | With service name and object path, qdbus will list the methods, signals and properties available on the object | | Options: | --system connect to the system bus | --address ADDRESS connect to the given bus | --literal print replies literally `---- ,----[ Output of qdbus6 --help ] | Usage: qdbus [--system] [--bus busaddress] [--literal] [servicename] [path] [method] [args] | | servicename the service to connect to (e.g., org.freedesktop.DBus) | path the path to the object (e.g., /) | method the method to call, with or without the interface | args arguments to pass to the call | With 0 arguments, qdbus will list the services available on the bus | With just the servicename, qdbus will list the object paths available on the service | With service name and object path, qdbus will list the methods, signals and properties available on the object | | | Options: | --system connect to the system bus | --bus busaddress connect to a custom bus | --literal print replies literally `---- Anywhere, I now know why it works a lot better for me than you, since I use Krusader. I still have a minimal install of Plasma5 and several self-compiled Plasma5 programs (for their Kpart) to make Krusader work fully. Krusader was still a Plasma5 application until today- I just receive a message that it has been ported to Plasma6. Charles -- When you say "I wrote a program that crashed Windows", people just stare at you blankly and say "Hey, I got those with the system, *for free*". -- Linus Torvalds