https://bugs.kde.org/show_bug.cgi?id=370384
--- Comment #16 from Vishal Rao <vishal...@gmail.com> --- I have built dummy backend also as part of kpmcore and noted both the default partitionmanager binary and my built one both try to load the backends from /usr/lib/x86.../qt5/plugins folder, so I tried replacing the original with my built ones and only the default partitionmanager binary from /usr/bin crashed and not my built one. One other difference I see is that when I run the default /usr/bin/partitionmanager it seems to trigger KDE-SU UI while my binary triggers/picks up gksudo... see different console output below during early run: vishal@skybird:/usr/bin$ ./partitionmanager org.kde.kdesu: Daemon not safe (not sgid), not using it. -------- vishal@skybird:~/SRC/partitionmanager-2.2.1+p16.04+git20160920.0957/build/src$ ./partitionmanager (gksudo:2327): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita", (gksudo:2327): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita", -- You are receiving this mail because: You are watching all bug changes.
