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.
...It would of made a lot more sense to just remove bluez in a sign of protest of their poor development decisions and let any users that really need it to solve the problem themselves, this is slackware after all. You're supposed to be able to fend for yourself, but instead we will get pulseaudio which predictably can only cause more problems than it will solve...
I second that!
I would have prefered BlueZ on slackbuilds.org, left over there for people to consider.
After all, it's not the first time Slackware has dropped softwares.
I prefer to have BlueZ in Slackware directly. Whose right should be respected?
Then maybe 14.3 drops PA and BlueZ, we'll see.
--
Best regards,
Andrzej Telszewski
I believe that there Isn't much rights to consider here, at least not for the people who aren't involved with the making of Slackware, just some requests and wishes.
I fully understand that, nonetheless if BlueZ was dropped and placed in slackbuilds.org, It would have been a win-win.
Those who want it could have installed it easily along PulseAudio and those who aren't fond of the idea of having PulseAudio didn't have to deal with it.
Now one side wins, the other loses.
There is no win-win possibility here. Up to now, folks who wanted to have the fully PA enabled system, had to compile software on their own. Now folks who don't want to have PA, have to re-compile on their own.
I believe that there Isn't much rights to consider here, at least not for the people who aren't involved with the making of Slackware, just some requests and wishes.
I fully understand that, nonetheless if BlueZ was dropped and placed in slackbuilds.org, It would have been a win-win.
Those who want it could have installed it easily along PulseAudio and those who aren't fond of the idea of having PulseAudio didn't have to deal with it.
Now one side wins, the other loses.
Assigning BlueZ to SBo means out-of-the-box Slackware wouldn't have a Bluetooth manager which would limit and cripple users. Yes, you'd have the kernel Bluetooth driver, but you'd lack the server to control it. BlueZ is the Bluetooth server as Pulse is an audio and sound server just like X is a video and graphics server. Having Pulse doesn't hurt Slackware as Patrick has chosen to implement Pulse in Slackware with options. Crippling support is a lose-lose, not a win-win.
You should be getting support through the modesetting driver now for older DRI1 based graphics cards and chipsets. You can still use the older drivers, but modesetting should work also.
You should be getting support through the modesetting driver now for older DRI1 based graphics cards and chipsets. You can still use the older drivers, but modesetting should work also.
Yes, but the segfault has nothing to do with DRI1 or modesetting. Someone added support for new hardware and it's triggering a bug on old hardware.
in a current from 29 december of 2015, slackware64:
there is again no xfce4-xkb-plugin package!
xfce4 is almost useless without that package, because there are no current language indicator for keyboard layouts! please include that package in slackware current, and in further releases too!
My main desktop system has only HDMI audio. I have been playing with current a little bit (btrfs subvol root makes that easy) and so far to get good quality sound output, without crackles and pops, I still need my /etc/asound.conf with its dmix + rate convert + buffering and route plugins. Some stuff in wine still seems unhappy without a null device behind the route plugin to fake a recording device.
I am happy that the decision to include pulse was made, it seems more and more software is looking for the libs to be present. I think this will generally make life on Slackware easier. I am not yet sure if I might just go with the dumbpipe to alsa pulse config some have suggested on these boards. I say this given I still seem to need a somewhat exotic ALSA setup for things to work well and I have a lot of stuff I might not recompile to use pulse just yet too. I don't know what folks might need on the KDE side or if it would be even possible but for people who may not be quite ready to go whole hog on pulse audio and use XFCE, these two packages would still be useful.
They are not hard to build, but considering how much angst there still seems to be out there maybe this would help some folks?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
