FS#5654 - ksysguard doesn't play nice with dbus and avahi
Attached to Project:
Arch Linux
Opened by jos poortvliet (superstoned) - Monday, 23 October 2006, 23:18 GMT
Last edited by Aaron Griffin (phrakture) - Friday, 14 December 2007, 18:51 GMT
Opened by jos poortvliet (superstoned) - Monday, 23 October 2006, 23:18 GMT
Last edited by Aaron Griffin (phrakture) - Friday, 14 December 2007, 18:51 GMT
|
Details
currently, if one runs kde 3.5.5 from testing, ksysguard
doesn't start until you create a symlink from
/usr/lib/libdbus-1.so to /usr/lib/libdbus-1.so.2 while it
should work (my guess) with /usr/lib/libdbus-1.so.3.
when you make the symlink, ksysguard complains about avahi: ksysguard: WARNING: Failed to create avahi client third, the ksysguard kicker plugin doesn't work anymore. it asks, when logging in, about where to connect to, and no matter what you choose, you end up with a non-working applet, which only shows a 'can't connect' icon. |
This task depends upon
Closed by Aaron Griffin (phrakture)
Friday, 14 December 2007, 18:51 GMT
Reason for closing: None
Additional comments about closing: no response to status request
Friday, 14 December 2007, 18:51 GMT
Reason for closing: None
Additional comments about closing: no response to status request
libdbus-1.so.3 => /usr/lib/libdbus-1.so.3 (0xb69fb000)
so it seems ksysguard needs dbus
but still, when starting the kicker, i get the annoying 'connect to host' dialog, where i must choose between ssh, rsh, daemon, or custom command. none of these seem to work, and i can't get my ksysguard kicker applet to work. It should work, did in 3.5.4 and even in my local kde4 build it works fine...
anyway, still the connection question by the ksysguard panel applet, and no matter what i choose - it won't work.