SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
You may also need to rebuild your Blueman package to disable the Pulseaudio Plugin.
Just go to http://slackware.mirrors.tds.net/pub...e/xap/blueman/ download the build pack, rebuild Blueman, and reinstall it to see if it still requires it. Pulse is supposed to be completely optional as a package.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,095
Rep:
I'm not even running KDE, at the moment. Blueman just stopped working after installing yesterday's updates and upgrades. Either one of the updates or upgrades broke it or maybe Blueman needs to be updated?
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,095
Rep:
Fixed. Well, sort of...
Quote:
Wed Jun 27 04:38:25 UTC 2012
....
xap/blueman-r708-x86_64-2.txz: Reverted.
Switched back to r708, since the newer repo pull is requiring PulseAudio.
We'll consider what to do about this long term sometime down the road.
Thank you, Mr. Volkerding.
Last edited by cwizardone; 06-27-2012 at 01:15 AM.
It's probably because the source was geared towards Ubuntu which uses PulseAudio by default as it's main sound server. It can probably be patched out, but knowing what to do to patch it out will take some time.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.