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
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To No-one
Architecture not specified
Severity Medium
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

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
Comment by Jan de Groot (JGC) - Tuesday, 24 October 2006, 06:21 GMT
I can't reproduce the dbus 0.6x dependency, the ksysguard binary I have on my system links to the testing version of dbus. About the avahi warning: do you have avahi running? if it isn't, then the warning is logical.
Comment by Tobias Powalowski (tpowa) - Tuesday, 24 October 2006, 07:01 GMT
[tobias@Wohnung ~]$ ldd /opt/kde/bin/ksysguard | grep dbus
libdbus-1.so.3 => /usr/lib/libdbus-1.so.3 (0xb69fb000)
so it seems ksysguard needs dbus
Comment by jos poortvliet (superstoned) - Tuesday, 24 October 2006, 09:31 GMT
well, i did have the avahi-daemon running, but only after starting the Avahi mDNS/DNS-SD DNS Server Configuration Daemon, the message disappears. as i have no idea what avahi is (and am way to lazy too look it up, as i wouldn't know what i need it for and have more to do), i guess that's solved.

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...
Comment by jos poortvliet (superstoned) - Wednesday, 01 November 2006, 11:32 GMT
this still doesn't work, tough KDE 3.5.5 is from extra packages now... not sure if there is any difference ;-)
anyway, still the connection question by the ksysguard panel applet, and no matter what i choose - it won't work.
Comment by Allan McRae (Allan) - Saturday, 08 September 2007, 15:58 GMT
Status?

Loading...