With enabled dolphin integration libs are built to show the sync status as overlay on files/folders. Also it is possible to share files/folders with right click on them. The problem is that the libs are in wrong place, which leads to this dolphin output: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Keine Berechtigung Error loading plugin "ownclouddolphinactionplugin" "The shared library was not found." Plugin search paths are ("/usr/lib64/qt5/plugins", "/usr/bin", "/usr/lib64/kde4/plugins") The mentioned file is in /usr/lib64/plugins/ownclouddolphinactionplugin.so (installed via ebuild 2.1.1). To solve this I had to manually add the following links: /usr/lib64/qt5/plugins/ownclouddolphinactionplugin.so -> /usr/lib64/plugins/ownclouddolphinactionplugin.so /usr/lib64/kde4/plugins/kf5 -> /usr/lib64/plugins/kf5 /usr/lib64/kde4/plugins/ownclouddolphinactionplugin.so -> /usr/lib64/plugins/ownclouddolphinactionplugin.so Unfortunately I am not good at writing ebuilds, but I can test/try your suggestions. Thank you
Crossreference: https://github.com/owncloud/client/issues/4570
Thanks for the report and upstream bug! I do not use KDE myself but I hope to fix this before bumping owncloud-client to 2.2.0 (it probably misses some configuration parameters from a KDE eclass) Looking into it
If you need help testing, please let me know.
CC'ing kde folks for ideas here: the paths can be specified to use proper places instead of the default paths. However, I did not find helpers in our current eclasses or a way to check on the live system (and what about binary builds in that case?) to specify these paths. Also I guess dolphin support should only be allowed on qt5 builds for owncloud-client (and from them KDE5 only)? The current dependencies are: dolphin? ( >=kde-frameworks/kcoreaddons-5.16:5 >=kde-frameworks/kio-5.16:5 ) But it is strange as Tobias's workaround points to kde4 paths?
From kde5.eclass: kde5_src_configure phase function # install mkspecs in the same directory as qt stuff cmakeargs+=(-DKDE_INSTALL_USE_QT_SYS_PATHS=ON) I
Passing -DKDE_INSTALL_USE_QT_SYS_PATHS=ON should indeed fix the issue, but note this is now the default behaviour as of kde-frameworks/extra-cmake-modules-5.22.0. (In reply to Bernard Cafarelli from comment #4) > Also I guess dolphin support should only be allowed on qt5 builds for > owncloud-client (and from them KDE5 only)? The current dependencies are: > dolphin? ( > >=kde-frameworks/kcoreaddons-5.16:5 > >=kde-frameworks/kio-5.16:5 ) > Yep, this dolphin plugin definitely requires qt5. If it's loaded against a qt4 owncloud library, it will almost certainly crash. > But it is strange as Tobias's workaround points to kde4 paths? I'm not sure why it's in the search path, but being in just the qt5 one should be fine.
With 2.2.0 and Framework-5.22.0 both files in question are: /usr/lib64/qt5/plugins/kf5/overlayicon/ownclouddolphinoverlayplugin.so /usr/lib64/qt5/plugins/ownclouddolphinactionplugin.so So they seem to be in the right folder and the integration of owncloud in dolphin is working just like expected. Thank you!
Add us back when more infos needed.
Created attachment 435924 [details] Updated 2.2.0 ebuild Things are looking good then! Tobias, as a last test, can you confirm that the attached ebuild works fine for you? It only changes: * force build dependency on new enough extra-cmake-modules * make doplhin USE-flag depend on qt5 one It should be fine, but I'd prefer some confirmation before committing the ebuild
It works fine. Great :)
Thanks, 2.2.0-r1 is in tree then!
