LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   KDE has been build without Zeroconf support (http://www.linuxquestions.org/questions/slackware-14/kde-has-been-build-without-zeroconf-support-823613/)

sjampoo 08-02-2010 02:39 PM

KDE has been build without Zeroconf support
 
What?

Correct.

@Work I've got 2 slackware 13.1 64 machines, and they work just fine: Basic installation, everything ' bog standard ' . When in Dolphin or Konqueror, I can ' click ' on Network Services and all the other MS Window machines pop-up.

@Home I've got 2 slackware 13.1 64 machines, they don't work fine. Basic installation, everything ' bog standard '. When in Dolphin or Konqueror, I can 'click' on Network Services and 'KDE has been build without Zeroconf support' pops up in Konqueror or is displayed in Dolpin..

Is it my netwerk @ Home (with an old Windows Server in it) or is something missing in the installation? Under MS windows (from within a virtualbox, brigded network) both machines can browse the network just perfectly: I even got a XP machine 'joined' in the domain on the windows server)..

Clueless since a google on the error + slackware give me Zero. Zeroconf in the slackware forum give me some midly related questions, but no answers for me.

sahko 08-02-2010 02:56 PM

Yeah, kdelibs has an optional dependency on avahi.
Since Slackware doesnt include it, KDE has indeed been built without zeroconf support.

sjampoo 08-02-2010 03:15 PM

how come it works on the slackware 13.1 machines that I recently installed at work?

Or better: how to solve?

damgar 08-02-2010 11:16 PM

Quote:

Originally Posted by sjampoo (Post 4052945)
how come it works on the slackware 13.1 machines that I recently installed at work?

Or better: how to solve?

Rebuild kdelibs with avahi?

sjampoo 08-03-2010 03:37 AM

and how whould I do that?

Alien Bob 08-03-2010 07:25 AM

Obviously the difference in behaviour between your work and home computers is not explained by using avahi or not - they're the same KDE packages, all compiled without the presence of avahi.
I would guess that your Windows network at home is configured differently than at work. My KDE at home sees all the WIndows computers (yes my family uses several) but perhaps that is helped by the fact that my server's SaMBa server is configured as a Windows Domain server?

If you want to rebuild portions of KDE, you can. First build an avahi package using the SlackBuild at slackbuilds.org, then rebuild the components that can make use of it.

In order to help you with this, I used my build log for KDE 4.4.5 and created a set of directions out of it: see http://slackware.com/~alien/kde-4.4.5-optionals.txt

Eric

sjampoo 08-03-2010 08:51 AM

Thanx!

Hmm come to think off it: I have had problems in the past with Windows computers joining the domain. Where @work I never had those problems, @home there must be something 'different': DHCP is conveniently handled by my Linksys cablemodem.

That must be it! Little differences can leave a man confused.

Quote:

If you want to rebuild portions of KDE, you can.
You sure I can? I'll give it a go.

Avahi needs libdaemon, both are installed as we speak. Will be looking into the link you provided to rebuild the KDE portions.

sjampoo 08-03-2010 05:13 PM

Done! :)

Thankx again Eric. I got the kdelibs rebuild, and upgraded. Zeroconf is no longer a problem ( started the daemon by /usr/sbin/avahi-daemon -D ) and now I know my network is borked :) :)

(as in: I no longer get an error, I can browse network services, but I see no networkgroups or shares. So probably right: reconfigure the network (domain aint working anyway)

mike_booth76 08-04-2010 12:33 AM

Quote:

Originally Posted by Alien Bob (Post 4053806)
Obviously the difference in behaviour between your work and home computers is not explained by using avahi or not - they're the same KDE packages, all compiled without the presence of avahi.
I would guess that your Windows network at home is configured differently than at work. My KDE at home sees all the WIndows computers (yes my family uses several) but perhaps that is helped by the fact that my server's SaMBa server is configured as a Windows Domain server?

If you want to rebuild portions of KDE, you can. First build an avahi package using the SlackBuild at slackbuilds.org, then rebuild the components that can make use of it.

In order to help you with this, I used my build log for KDE 4.4.5 and created a set of directions out of it: see http://slackware.com/~alien/kde-4.4.5-optionals.txt

Eric

How would you make this work for 4.4.95?

Mike

Alien Bob 08-04-2010 05:27 AM

Quote:

Originally Posted by mike_booth76 (Post 4054951)
How would you make this work for 4.4.95?

Mike

Well, the optional dependencies listed for KDE 4.4.5 are almost if not completely identical for KDE 4.5.0 (4.4.95 is the 4.5.0-RC3 of course) so you can still use that informational URL I posted.

Eric


All times are GMT -5. The time now is 12:24 AM.