https://bugs.kde.org/show_bug.cgi?id=374402
Bug ID: 374402
Summary: startkde and qdbus-- logic in startkde make no sense
Product: plasmashell
Version: 5.8.4
Platform: Mageia RPMs
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: k...@davidedmundson.co.uk
Reporter: un...@physics.ubc.ca
CC: bhus...@gmail.com, plasma-b...@kde.org
Target Milestone: 1.0
If /usr/lib64/qt5.bin is not in pathe startx startkde produces
Cannot start D-Bus. Can you callqdbus
error message.
The problem is that starkde cannot find qdbus. It tries to run qtpaths
sometimes, but since that is in exactly the same directory as qdbus, if it
cannot find qdbus, it cannot find qtpaths either.
startkde looks to see if startkde was run with a full path or not. If it was
run with a full path, it adds that directory to the internal PATH. It then
tries to run qtpaths to add a full path to qdbus. But that makes no sense since
if qdbus cannot be found neither can qdbus. And whether or not startkde is
started with a full path is unrelated to whether qdbus can be fouund since
startde is not in the same directory as qdbus./lib64/qt5/bin
a) at least a link to qtpaths should be in /usr/bin, so qtpaths can allways be
found to be run.
b) qtpaths should always be run to create a call to qdbus which is independent
of whether or not startkde is started with a full path or not, and whether or
not /ust/lib64/qt5/bin is in the PATH or not.
c) Yhe error message should be changed to somethig usefull.The current
errormessage reads like a joke (what is qdbus)
I could make a suggestion as to how startkde should be changed if that would
be helpful.
--
You are receiving this mail because:
You are watching all bug changes.
