KDE apps fail start due to socket connect error
Beeblebrox
zaphod at berentweb.com
Thu Jul 13 10:40:09 UTC 2017
Hello, thanks for the answer.
> Just to be sure, is the dbus service running?
Yes dbus is running but not HAL. ps shows:
66343 - I 0:00.00 dbus-launch --autolaunch .........
66344 - Is 0:00.26 /usr/local/bin/dbus-daemon --fork --print-pid ........
Additionally, Konqueror was segfaulting & gdb showed
"then: then/endif not found."
To be able to further analyse it w/ gdb, I re-compiled baseapps using "WITH_DEBUG_PORT" setting. Now both dolphin & Konq start, terminal output attached, but gdb not giving much info (gdb may be the wrong tool for KDE apps perhaps).
deskutils/silence for example still has same problem
Regards
--
HardenedBSD_amd64_12-Current_RadeonKMS
Please CC my email when responding, mail from list is not delivered.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dolphin-start.log
Type: text/x-log
Size: 2600 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-freebsd/attachments/20170713/d1813337/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: konq-start.log
Type: text/x-log
Size: 414 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-freebsd/attachments/20170713/d1813337/attachment-0001.bin>
More information about the kde-freebsd
mailing list