Doh!

OK, my question is then whether posix mode should be switched off in xdm's Xsession as it is in kdm's Xsession?

chris

It may take some time to have the posix mode changed in the official xdm package's Xsession (if it happens at all). Of course individual users can modify their own installations. However I've also submitted an update to the SBo pulseaudio package which includes a patch to make its bash completion script more posix friendly so that an unchanged xdm will work as expected.

That changed pulseaudio package should appear in the next round of SBo updates - probably next weekend. If anyone wants to patch it themselves before then, the required patch is attached (with additional .txt suffix). Apply it by adding the line "patch -p0 $CWD/030_posix-completion.diff.txt" just after the existing patch in the pulseaudio.Slackware file.

chris

Attached Files

030_posix-completion.diff.txt (2.3 KB, 26 views)

Nice job. I didn't try it because I already removed pulseaudio and don't need it anymore. However, IMO the best solution would be to modify stock xdm/Xsession. In future we may see other packages that cause similar problems and patching all of them will become troublesome. I modified my xdm/Xsession to act the same as kdm/Xsession, that is to disable POSIX mode when $SHELL is bash. I attach the patch.

Attached Files

xdm-xsession-profile-source-patch.txt (1.8 KB, 46 views)

I'm not certain I fully understand what's happening here by "speakers volume on software level" or maybe wireless has some difference from hardwired of which I am unaware but my hardwired speaker system utilizing ALSA only (NO pulseaudio and Jack only on demand, usually off) will respond perfectly to volume changes even from the Volume control on my wireless Logitech keyboard. Perhaps this is useless info for you but I thought possibly it was worth knowing that at least someone has experienced zero limitations from not having pulseaudio.

The problem here is that my wireless Creative speakers Bluetooth dongle does not have any controls in alsamixer. I have this set: http://us.creative.com/p/speakers/inspire-s2-wireless and use this stock dongle: https://d287ku8w5owj51.cloudfront.ne...450&height=350. These speakers work perfectly with Android. On Slackware however I can pair my PC with speakers without installing any extra software using the dongle and play sound on them but I cannot manipulate volume level. Alsamixer says that "This sound device does not have any controls". In Youtube in Firefox I can use a volume slider to turn down a volume but I cannot increase the maximum volume anyway. What's worse is that for some reason even speaker hardware volume level button does not work on Slackware, I can't even turn the volume down using them. And what's worst is that AUX IN port is broken and after plugging in a jack I can only hear a loud mains hum, exactly like this: https://en.wikipedia.org/wiki/File:MainsBrum50Hz.ogg

Greetings
I'm not sure of the extent of what you mean by "the AUX IN port is broken" as in is it physically broken? I do know this - it is common in audio devices to have pre and post inputs and the fact that the hardware volume control does not work means that somehow the signal source is skipping the pre input and getting in post volume control. It is entirely common that jacks/ports separating preqmp and power amp have interrupt switches. Entirely hardware inputs have physical switches activated by the insertion of a jack.

To visualize this consider the purpose. Commonly one may wish to connect a preamp out to numerous power amp inputs in a playback system. It is very rare that more than one preamp be connected to a single power amp. This is why mixer consoles exist so commonly the toggle switch maintains the preamp connection when the port is used as an output (to an additional amp/spkr combination for added reinforcement) but disconnected when used as an input to that power section.

My conclusion is, since it appears this speaker system works in other environments but controls are not available in Slackware (any other distros?) is that either an additional or updated module is required in the kernel or some additional application is required to gain proper access to the proper port and controls.

You could try some LiveCDs or research what kernel module(s) are being used or are available or if some application might be available. FWIW in the FOSS world it is not at all uncommon that such apps are all but entirely chipset based and that even some other brand that employs the same chipset(s) may work. OTOH Creative does not have a history of playing nice with others or in Linux.

That said, Sennheiser uses a workaround to make the aptX codec functional in Linux and the other codec compatibility for your Creative hardware, SBC, has some availability in Linux through the Bluetooth Special Interest Group. see

SBC Codec

Good luck

BTW an "sbc" package script has been approved and will be available at SBo in the next update.

chris

Yes, I believe it's physically broken. As I said, I hear a loud annoying humming after plugging in a cable into AUX IN port. It's getting louder when then other end is connected to the computer or mobile phone. This is why I want to use Bluetooth. I would never consider using Bluetooth if AUX IN port worked.
I've been using Linux for several years, some hardware such as HP Pavilion card reader or Acer Aspire microphone didn't work out of the box and I spent a lot of time making it work. It's sad but it's true. I didn't try other LiveCDs, I might try some with a relatively new kernel.
Good news, I will give it a try.

Sounds like a classic earth loop.
https://www.soundonsound.com/sos/aug...s/qa0806_4.htm
http://www.epanorama.net/documents/groundloop/
https://en.wikipedia.org/wiki/Ground...electricity%29

It's probably easier to use Bluetooth than to solve an earth loop problem...

Note that humming is only there where a cable is plugged into AUX IN. Speakers are perfectly silent without any cable plugged in. I got a new power adapter, maybe it will help.