Re: [arch-general] Arch Linux on MacBookPro13,3

[Christoph Gysin via arch-general]

I'm running arch on a MacbookPro13,1.

There used to be a really annoying bug with the NVMe controller, that
would delay bootup by up to 2 minutes. Luckily that has been fixed in
4.15.2 or so. The only feature I'm really missing is working
suspend/resume (wifi works on the 13,1). With kernel 4.16, bluetooth
will work out of the box on the 13,3 (13,1 still needs a small patch
currently).

For out-of-tree drivers, there are AUR packages:
webcam: https://aur.archlinux.org/packages/bcwc-pcie-git/
keyboard/touchpad: https://aur.archlinux.org/packages/macbook12-spi-driver-dkms/

Both are working on getting them into mainline.

On Thu, Mar 1, 2018 at 9:25 PM, Jeremy Brown  wrote:
> Hey Arch folks,
>
> I have a work-provided laptop which is a MacBookPro13,3; in other words a
> fairly recent MacBook Pro (one of the touch bar ones).  I've shrunk the root
> partition on it and would like to install Arch on a second partition and use
> that as my primary OS.  I've been able to do this with previous versions of
> MacBook Pros no problem.
>
> However, doing some research it appears as though installing Linux on this
> hardware is difficult and many of the components either require extensive
> customization (e.g. building your own drivers) or don't work at all:
>
>https://github.com/Dunedan/mbp-2016-linux
>https://gist.github.com/roadrunner2/1289542a748d9a104e7baec6a92f9cd7
>
> Assuming that page is correct audio, wifi, and suspend not working (or barely
> working) are going to be dealbreakers for me, I think.  I'm going to take a
> crack at it in the next few days but wondered if anyone in arch-general had 
> any
> success with similar hardware.  Is it livable, or is the driver support and
> such just not there yet?
>
> Cheers,
>
> Jeremy



-- 
echo mailto: NOSPAM !#$.'<*>'|sed 's. ..'|tr "<*> !#:2" org@fr33z3

[arch-general] linux-4.13: CONFIG_SPI removed?

[Christoph Gysin via arch-general]

I'm using a MacBookPro from late 2016, which features a keyboard and
touchpad that are attached via SPI (spi_pxa2xx_platform), using the
driver from [0].

It seems that with the upgrade to kernel 4.13. CONFIG_SPI has been removed [1].

Any idea what was the motivation behind this change? Was it intentional?

I'm totally capable of compiling my own kernel, but I'd rather spend
my time on other things :)

Could we have CONFIG_SPI back in the stock kernel?

[0] https://github.com/cb22/macbook12-spi-driver
[1] 
https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/linux=7648ebf0fa9b0190aa26a11acd46ac31f0593b69
-- 
echo mailto: NOSPAM !#$.'<*>'|sed 's. ..'|tr "<*> !#:2" org@fr33z3

Re: [arch-general] makepkg - any way to recompile only newly patched files in large packages?

[Christoph Gysin via arch-general]

On Mon, Aug 7, 2017 at 10:39 AM, David C. Rankin
 wrote:
> If it wasn't clear, I have already built the gtk2 package yesterday to
> --enable-debug=yes so I have all of the files in a state I could call
> --repackge on, except for the gtk/gtkrecentchooser.c file with the one line
> change. I was wondering if there was a way to avoid the full 15 minute rebuild
> of all of gtk2 and just compile gtkrecentchooserdefault.c to object and then
> --repackage?

Not the answer to your question, but you might consider configuring
/etc/makepkg.conf to use ccache to speed up rebuilds. Also set
MAKEFLAGS=-j4 or similar to make sure you are using all available
cores.

-- 
echo mailto: NOSPAM !#$.'<*>'|sed 's. ..'|tr "<*> !#:2" org@fr33z3

Re: [arch-general] Automatic login

[Christoph Gysin via arch-general]

Check also:

https://wiki.archlinux.org/index.php/Systemd/User#Automatic_login_into_Xorg_without_display_manager

On Wed, Jul 19, 2017 at 12:22 PM, Junayeed Ahnaf via arch-general
 wrote:
> I actually have not thoguht about that. I'll take a look at it now :-)
>
>
> On 07/19/2017 06:16 AM, Maxwell Anselm via arch-general wrote:
>> If you're going to use automatic login, why not cut out the middle man and
>> ditch the display manager entirely?
>>
>> Relevant wiki articles/sections:
>> Getty#Automatic_login_to_virtual_console
>> Xinit#Autostart_X_at_login
>> KDE#Manual
>>
>> On Tue, Jul 18, 2017 at 10:08 AM, Junayeed Ahnaf via arch-general <
>> arch-general@archlinux.org> wrote:
>>
>>> On Tuesday, July 18, 2017 7:06:37 PM +06, Georg wrote:
 kcm is needed for that
>>> I did it . Steps :
>>>
>>> 1. Edit /etc/sddm.conf and added user and session under autologin
>>> 2. sudo systemctl --force enable sddm
>>> 3. cat /etc/systemd/system/display-manager.service to see if everything
>>> works
>>> 4. sudo reboot
>>>
>>> :-)
>>>
>>> Nirjhor
>>>
>



-- 
echo mailto: NOSPAM !#$.'<*>'|sed 's. ..'|tr "<*> !#:2" org@fr33z3

Re: [arch-general] pavucontrol depency question

[Christoph Gysin via arch-general]

pavucontrol works fine without pulseaudio, if you control another
machine's pulseaudio instance over the network:

   $ PULSE_SERVER=another-box pavucontrol

Not sure about xfce4 packages, don't use them.


On Mon, Mar 20, 2017 at 1:11 AM, Friedrich Strohmaier
 wrote:
> Hi all,
>
> some time ago xfce sorted out xfce4-mixer in favour of 
> xfce4-pulseaudio-plugin.
> - agreed removing xfce4-mixer
> - Installed xfce4-pulseaudio-plugin - no sound mixing available at all
> - Installed optional dependency pavucontrol - no sound mixing available - no
>   connection to pulseaudio server
> - Installed optional dependency pulsaudio - yay! sound mixing up an running.
>
> I don't understand much about dependency quirks but I wonder about the reason
> both dependencies beeing made optional.
> xfce4-pulsaudio-plugin is out of any functionality without working pavucontrol
> pavucontrol is out of any functionality without a running pulseaudio server.
>
> So what is the reason making both dependencies optional?
> --
> Friedrich



-- 
echo mailto: NOSPAM !#$.'<*>'|sed 's. ..'|tr "<*> !#:2" org@fr33z3

Re: [arch-general] Generating gdb debug logs for devs

[Christoph Gysin via arch-general]

On Fri, Feb 3, 2017 at 2:37 AM, Pekka Järvinen via arch-general
 wrote:
> This finally provided results!
>
> main (argc=, argv=) at lxrandr.c:783
> 783fixed = LVDS ? LVDS : monitors->data;

At this point, lxrandr has crashed and you are left at the gdb prompt.
Type "bt" to create a backtrace showing all functions and line numbers
of the current call stack. In your example, lxrandr is crashing in
main(), so there is only one stack frame.

Also, it might help the developers to print the values of relevant
variables. In the above example, it looks like LVDS evaluates to
false, and monitors is NULL, causing the segfault. You can confirm
this by printing those variables at the prompt, and include it in your
bug report:

(gdb) p LVDS
...
(gdb) p monitors
...

> I would suggest mentioning this manual compiling to the wiki page
> https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces so that others
> don't need to use hours/days figuring out this again.

Manual compiling is not the recommended way.

Chris
-- 
echo mailto: NOSPAM !#$.'<*>'|sed 's. ..'|tr "<*> !#:2" org@fr33z3

Re: [arch-general] Generating gdb debug logs for devs

[Christoph Gysin via arch-general]

On Thu, Feb 2, 2017 at 3:54 PM, Pekka Järvinen via arch-general
 wrote:
> % makepkg -sfi
> ...
> error: unresolvable package conflicts detected
> error: failed to prepare transaction (conflicting dependencies)
> :: lxrandr-gtk3 and lxrandr are in conflict

Ah, in this case -i won't work because the PKGBUILD builds two
conflicting versions, and -i tries to install them all.

> Ok, let's try with pacman:
>
> % sudo pacman -U lxrandr-0.3.1-1-x86_64.pkg.tar.xz
> ...
> Packages (1) lxrandr-0.3.1-1
>
> Total Installed Size:  0.22 MiB
> Net Upgrade Size:  0.01 MiB

This seems too small to contain the debug symbols. Something went
wrong during your build. Try to clean the build dir and try again,
using the upstream PKGBUILD and simply adding:

options+=(debug)

Building it should result in packages lxrandr-0.3.1-1 and
lxrandr-debug-0.3.1-1. Installing both should get you proper
backtraces.

> % gdb lxrandr
> ...
> Reading symbols from lxrandr...(no debugging symbols found)...done.

This indicates that you have no debug symbols for lxrandr.

Chris
-- 
echo mailto: NOSPAM !#$.'<*>'|sed 's. ..'|tr "<*> !#:2" org@fr33z3

Re: [arch-general] Generating gdb debug logs for devs

[Christoph Gysin via arch-general]

> I've installed ABS, modified PKGBUILD and made my own /etc/makepkg-dev.conf

No need to change both makepkg.conf and the PKGBUILD. Either will do.

> makepkg -sf --config /etc/makepkg-dev.conf generates the executable.

This will only build the package. Make sure to install it, or use
'makepkg -sfi' to install it automatically.

> Still gdb gives very little info after running
> cd lxrandr/pkg/lxrandr/usr/bin
> gdb -ex "set logging file debug.log" -ex "set logging overwrite on" -ex
> "thread apply all bt full" -ex "set logging on" -ex "run" -ex "backtrace"
> -ex "frame 0" -ex "kill" -ex "quit" ./lxrandr
>
> I'm guessing because I need to add debugging to libraries which lxrandr is
> using too.

You should see symbols for the stackframes in lxrandr, but stackframes
inside libraries might not resolve until you also build debug versions
for them.

> In the wiki there's
> --- snip ---
> Note: It is insufficient to simply install the newly compiled debug
> package, because the debugger will check that the file containing the debug
> symbols is from the same build as the associated library and executable.
> You must install both of the recompiled packages. In Arch, the debug
> symbols files are installed under /usr/lib/debug. See the GDB documentation
> for more information about debug packages.
> --- snip ---

This is referring to using split debug packages. When using
option=(debug) without !split, makepkg will create a separate package
with debug symbols. If using this approach, you must install both,
simply installing the symbols won't work because they have to match
the binary they were built for.

> But as a non c/c++ dev this doesn't say anything. What do I need to
> install/run and where?

You most likely need to install debug symbols for the libraries used
when lxrandr crashes.

Chris

Re: [arch-general] GNU Privacy Assistant window sizing problem?

[Christoph Gysin via arch-general]

This seems to be a bug in GPA. Nevertheless, you should be able to
move/resize the window to see the hidden options and buttons. I don't
use gnome, but I believe the default shortcuts are holding down the
Meta/Super/Windows/Apple key, then click and drag with
left/right/middle? mouse button to resize/move the window.

Chris

On Sat, Sep 17, 2016 at 6:10 AM, Francis Gerund via arch-general
 wrote:
> Hello.
>
> Running Arch x86-64, Gnome 3, Linux 4.7.4-1-ARCH #1 SMP PREEMPT Thu Sep 15
> 15:24:29 CEST 2016 x86_64 GNU/Linux.  Screeen is 15" 1366 x 768, 60 Hz.
>
> In GNU Privacy Assistant, when I open the "backend preferences" window, it
> opens with the "basic" options selected, correctly sized.  But when I then
> select either the "advanced" or "options", the window expands well below
> the lower screen edge.  Some of the options are then hidden, and I can not
> seem to find a way to resize the "backend preferences" window.
>
> Since the bottom row of buttons is completely hidden, I can not even change
> the setting that are visible, except the "basic" options.  I have searched
> the forum, wiki, and online, without success.
>
> Has anyone else seen this problem, and if so, found a solution?



-- 
echo mailto: NOSPAM !#$.'<*>'|sed 's. ..'|tr "<*> !#:2" org@fr33z3

Re: [arch-general] Virtualization accross hardware border

[Christoph Gysin]

> For my needs, I want to run "usual" software, specifically R, the statistics
> language. Utlimately, I want to bind several physical hosts together to
> appear as one host on OS level, such that e.g. htop would show the total
> number of cores accross all bound boxes.

There are often optimized distributed solutions for specific tasks. So
if your goal is to run R across multiple machines, check out something
like http://www.distributedr.org

Chris
-- 
echo mailto: NOSPAM !#$.'<*>'|sed 's. ..'|tr "<*> !#:2" org@fr33z3

Re: [arch-general] Alsa Softvol and MOC

[Christoph Gysin]

Alsa itself has a pulseaudio plugin. So applications using alsa will
be routed through pulseaudio.

I tried to find the source for that plugin, but couldn't find it.
Maybe it was removed from alsa-plugins upstream? Or merged into
another plugin?

What is preventing speakup from using pulseaudio?

On Sat, Sep 26, 2015 at 4:09 PM, Storm Dragon <stormdragon2...@gmail.com> wrote:
> Howdy,
> No, I don't have pulseaudio installed. I actually can't use it because it
> will not allow me to use speakup in the console.  Interestingly enough, I
> read something that said moc doesn't have support for pulseaudio. So, I must
> have found outdated info.
> Still, I wonder if we are missing a plugin in alsa itself?
> thanks
> Storm
>
> On Sat, Sep 26, 2015 at 03:09:38PM +0300, Christoph Gysin wrote:
>>
>> Are you using pulseaudio? This works out of the box for me with
>> pulseaudio. moc controls the volume of whatever was the default sink
>> when it was started.
>>
>> On Fri, Sep 25, 2015 at 10:06 PM, Storm Dragon
>> <stormdragon2...@gmail.com> wrote:
>>>
>>> Howdy,
>>> I have installed extra/moc 1:2.5.0-3. Reading through the docs, and
>>> things
>>> on the net, I found a way to set up a softvol control for it in alsa, so
>>> when I adjust its volume, it only changes the volume for moc. Everything
>>> went well, except, I can't adjust the volume from within the moc app,
>>> which
>>> should be possible because you can set the alsa device and mixer in the
>>> ~/.moc/config file.
>>> It is using the right device, and amixer sset Mocmaster 50% sets the
>>> volume.
>>> It's just the in program controls that fail. When moc starts, it gives
>>> this
>>> error:
>>> ALSA lib dlmisc.c:254:(snd1_dlobj_cache_get) Cannot open shared library
>>> /usr/lib/alsa-lib/libasound_module_ctl_softvol.so
>>> This makes me think that either a plugin is missing from alsa-plugins, or
>>> maybe moc is using an outdated way to change its volume. However, if the
>>> alsa controls are set to their defaults, the volume works fine, but it
>>> lowers the volume on the whole system.
>>> I did a pacman search for alsa softvol but it didn't return anything. Is
>>> there anything I can install to fix this?
>>> Thanks for any help
>>> Storm
>>> --
>>> Powered by Arch Linux! I am registered Linux user number 508465:
>>> https://linuxcounter.net/user/508465.html
>>> My blog, Thoughts of a Dragon: http://www.stormdragon.tk/
>>> get my public PGP key: gpg --keyserver wwwkeys.pgp.net --recv-key
>>> 43DDC193
>>> Twitter and Facebook are so ... yesteryear. Get your 2MB Social account
>>> TODAY! http://2mb.social/main/register
>>> My Blackberry is Broken: http://is.gd/my_blackberry_is_broken
>>> "I am your soul insane"
>>> Slayer - Gemini
>>
>>
>>
>>
>> --
>> echo mailto: NOSPAM !#$.'<*>'|sed 's. ..'|tr "<*> !#:2" org@fr33z3
>
>
> --
> Powered by Arch Linux! I am registered Linux user number 508465:
> https://linuxcounter.net/user/508465.html
> My blog, Thoughts of a Dragon: http://www.stormdragon.tk/
> get my public PGP key: gpg --keyserver wwwkeys.pgp.net --recv-key 43DDC193
> Twitter and Facebook are so ... yesteryear. Get your 2MB Social account
> TODAY! http://2mb.social/main/register
> Follow me on GNU Social: https://social.stormdragon.tk/storm
> "Fell in a river of illusion and apathy"
> Godsmack - Realign



-- 
echo mailto: NOSPAM !#$.'<*>'|sed 's. ..'|tr "<*> !#:2" org@fr33z3

Re: [arch-general] Alsa Softvol and MOC

[Christoph Gysin]

Are you using pulseaudio? This works out of the box for me with
pulseaudio. moc controls the volume of whatever was the default sink
when it was started.

On Fri, Sep 25, 2015 at 10:06 PM, Storm Dragon
 wrote:
> Howdy,
> I have installed extra/moc 1:2.5.0-3. Reading through the docs, and things
> on the net, I found a way to set up a softvol control for it in alsa, so
> when I adjust its volume, it only changes the volume for moc. Everything
> went well, except, I can't adjust the volume from within the moc app, which
> should be possible because you can set the alsa device and mixer in the
> ~/.moc/config file.
> It is using the right device, and amixer sset Mocmaster 50% sets the volume.
> It's just the in program controls that fail. When moc starts, it gives this
> error:
> ALSA lib dlmisc.c:254:(snd1_dlobj_cache_get) Cannot open shared library
> /usr/lib/alsa-lib/libasound_module_ctl_softvol.so
> This makes me think that either a plugin is missing from alsa-plugins, or
> maybe moc is using an outdated way to change its volume. However, if the
> alsa controls are set to their defaults, the volume works fine, but it
> lowers the volume on the whole system.
> I did a pacman search for alsa softvol but it didn't return anything. Is
> there anything I can install to fix this?
> Thanks for any help
> Storm
> --
> Powered by Arch Linux! I am registered Linux user number 508465:
> https://linuxcounter.net/user/508465.html
> My blog, Thoughts of a Dragon: http://www.stormdragon.tk/
> get my public PGP key: gpg --keyserver wwwkeys.pgp.net --recv-key 43DDC193
> Twitter and Facebook are so ... yesteryear. Get your 2MB Social account
> TODAY! http://2mb.social/main/register
> My Blackberry is Broken: http://is.gd/my_blackberry_is_broken
> "I am your soul insane"
> Slayer - Gemini



-- 
echo mailto: NOSPAM !#$.'<*>'|sed 's. ..'|tr "<*> !#:2" org@fr33z3

Re: [arch-general] Alsa Softvol and MOC

[Christoph Gysin]

The performance impact is hardly an issue on any modern machine you
will be running it.

The main concerns are regarding security.

http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/SystemWide/http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/WhatIsWrongWithSystemWide/

On Sat, Sep 26, 2015 at 4:45 PM, Michał Zegan
<webczat_...@poczta.onet.pl> wrote:
> It is not recommended for, I believe, a good reason, including severe
> performance impact.
>
> W dniu 26.09.2015 o 15:39, Christoph Gysin pisze:
>
>> While it's generally not recommended, you *can* run pulseaudio also as
>> a system-wide instance.
>>
>> On Sat, Sep 26, 2015 at 4:35 PM, Michał Zegan
>> <webczat_...@poczta.onet.pl> wrote:
>>>
>>> this is very well known to me, and also quite logical. pulseaudio is a
>>> session process, espeakup is a system process. that whole thing actually
>>> means it will have exactly those problems.
>>>
>>> W dniu 26.09.2015 o 15:32, Storm Dragon pisze:
>>>
>>>> Howdy,
>>>> No one has any clue what is stopping it. People have contacted the pulse
>>>> developers who say it's something with espeakup, but then some think it
>>>> may
>>>> be speech-dispatcher's crappy pulse implimentation, which may be the
>>>> case,
>>>> cause I think it will work if a dekstop infironment isn't loaded with
>>>> orca.
>>>> No one has any clue how, or even what, to fix lol. So, I just avoid
>>>> pulse.
>>>> Thanks
>>>> Storm
>>>> On Sat, Sep 26, 2015 at 04:26:40PM +0300, Christoph Gysin wrote:
>>>>>
>>>>> Alsa itself has a pulseaudio plugin. So applications using alsa will
>>>>> be routed through pulseaudio.
>>>>>
>>>>> I tried to find the source for that plugin, but couldn't find it.
>>>>> Maybe it was removed from alsa-plugins upstream? Or merged into
>>>>> another plugin?
>>>>>
>>>>> What is preventing speakup from using pulseaudio?
>>>>>
>>>>> On Sat, Sep 26, 2015 at 4:09 PM, Storm Dragon
>>>>> <stormdragon2...@gmail.com>
>>>>> wrote:
>>>>>>
>>>>>> Howdy,
>>>>>> No, I don't have pulseaudio installed. I actually can't use it because
>>>>>> it
>>>>>> will not allow me to use speakup in the console. Interestingly enough,
>>>>>> I
>>>>>> read something that said moc doesn't have support for pulseaudio. So,
>>>>>> I
>>>>>> must
>>>>>> have found outdated info.
>>>>>> Still, I wonder if we are missing a plugin in alsa itself?
>>>>>> thanks
>>>>>> Storm
>>>>>>
>>>>>> On Sat, Sep 26, 2015 at 03:09:38PM +0300, Christoph Gysin wrote:
>>>>>>>
>>>>>>>
>>>>>>> Are you using pulseaudio? This works out of the box for me with
>>>>>>> pulseaudio. moc controls the volume of whatever was the default sink
>>>>>>> when it was started.
>>>>>>>
>>>>>>> On Fri, Sep 25, 2015 at 10:06 PM, Storm Dragon
>>>>>>> <stormdragon2...@gmail.com> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>> Howdy,
>>>>>>>> I have installed extra/moc 1:2.5.0-3. Reading through the docs, and
>>>>>>>> things
>>>>>>>> on the net, I found a way to set up a softvol control for it in
>>>>>>>> alsa,
>>>>>>>> so
>>>>>>>> when I adjust its volume, it only changes the volume for moc.
>>>>>>>> Everything
>>>>>>>> went well, except, I can't adjust the volume from within the moc
>>>>>>>> app,
>>>>>>>> which
>>>>>>>> should be possible because you can set the alsa device and mixer in
>>>>>>>> the
>>>>>>>> ~/.moc/config file.
>>>>>>>> It is using the right device, and amixer sset Mocmaster 50% sets the
>>>>>>>> volume.
>>>>>>>> It's just the in program controls that fail. When moc starts, it
>>>>>>>> gives
>>>>>>>> this
>>>>>>>> error:
>>>>

Re: [arch-general] Alsa Softvol and MOC

[Christoph Gysin]

While it's generally not recommended, you *can* run pulseaudio also as
a system-wide instance.

On Sat, Sep 26, 2015 at 4:35 PM, Michał Zegan
<webczat_...@poczta.onet.pl> wrote:
> this is very well known to me, and also quite logical. pulseaudio is a
> session process, espeakup is a system process. that whole thing actually
> means it will have exactly those problems.
>
> W dniu 26.09.2015 o 15:32, Storm Dragon pisze:
>
>> Howdy,
>> No one has any clue what is stopping it. People have contacted the pulse
>> developers who say it's something with espeakup, but then some think it may
>> be speech-dispatcher's crappy pulse implimentation, which may be the case,
>> cause I think it will work if a dekstop infironment isn't loaded with orca.
>> No one has any clue how, or even what, to fix lol. So, I just avoid pulse.
>> Thanks
>> Storm
>> On Sat, Sep 26, 2015 at 04:26:40PM +0300, Christoph Gysin wrote:
>>>
>>> Alsa itself has a pulseaudio plugin. So applications using alsa will
>>> be routed through pulseaudio.
>>>
>>> I tried to find the source for that plugin, but couldn't find it.
>>> Maybe it was removed from alsa-plugins upstream? Or merged into
>>> another plugin?
>>>
>>> What is preventing speakup from using pulseaudio?
>>>
>>> On Sat, Sep 26, 2015 at 4:09 PM, Storm Dragon <stormdragon2...@gmail.com>
>>> wrote:
>>>>
>>>> Howdy,
>>>> No, I don't have pulseaudio installed. I actually can't use it because
>>>> it
>>>> will not allow me to use speakup in the console. Interestingly enough, I
>>>> read something that said moc doesn't have support for pulseaudio. So, I
>>>> must
>>>> have found outdated info.
>>>> Still, I wonder if we are missing a plugin in alsa itself?
>>>> thanks
>>>> Storm
>>>>
>>>> On Sat, Sep 26, 2015 at 03:09:38PM +0300, Christoph Gysin wrote:
>>>>>
>>>>>
>>>>> Are you using pulseaudio? This works out of the box for me with
>>>>> pulseaudio. moc controls the volume of whatever was the default sink
>>>>> when it was started.
>>>>>
>>>>> On Fri, Sep 25, 2015 at 10:06 PM, Storm Dragon
>>>>> <stormdragon2...@gmail.com> wrote:
>>>>>>
>>>>>>
>>>>>> Howdy,
>>>>>> I have installed extra/moc 1:2.5.0-3. Reading through the docs, and
>>>>>> things
>>>>>> on the net, I found a way to set up a softvol control for it in alsa,
>>>>>> so
>>>>>> when I adjust its volume, it only changes the volume for moc.
>>>>>> Everything
>>>>>> went well, except, I can't adjust the volume from within the moc app,
>>>>>> which
>>>>>> should be possible because you can set the alsa device and mixer in
>>>>>> the
>>>>>> ~/.moc/config file.
>>>>>> It is using the right device, and amixer sset Mocmaster 50% sets the
>>>>>> volume.
>>>>>> It's just the in program controls that fail. When moc starts, it gives
>>>>>> this
>>>>>> error:
>>>>>> ALSA lib dlmisc.c:254:(snd1_dlobj_cache_get) Cannot open shared
>>>>>> library
>>>>>> /usr/lib/alsa-lib/libasound_module_ctl_softvol.so
>>>>>> This makes me think that either a plugin is missing from alsa-plugins,
>>>>>> or
>>>>>> maybe moc is using an outdated way to change its volume. However, if
>>>>>> the
>>>>>> alsa controls are set to their defaults, the volume works fine, but it
>>>>>> lowers the volume on the whole system.
>>>>>> I did a pacman search for alsa softvol but it didn't return anything.
>>>>>> Is
>>>>>> there anything I can install to fix this?
>>>>>> Thanks for any help
>>>>>> Storm
>>>>>> --
>>>>>> Powered by Arch Linux! I am registered Linux user number 508465:
>>>>>> https://linuxcounter.net/user/508465.html
>>>>>> My blog, Thoughts of a Dragon: http://www.stormdragon.tk/
>>>>>> get my public PGP key: gpg --keyserver wwwkeys.pgp.net --recv-key
>>>>>> 43DDC193
>>>>>> Twitter and Facebook are so ... yesteryear. Get your 2MB Social
>>>>>> account
>>>>>> TODAY! http://2mb.social/main/register
>>>>>> My Blackberry is Broken: http://is.gd/my_blackberry_is_broken
>>>>>> "I am your soul insane"
>>>>>> Slayer - Gemini
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> echo mailto: NOSPAM !#$.'<*>'|sed 's. ..'|tr "<*> !#:2" org@fr33z3
>>>>
>>>>
>>>>
>>>> --
>>>> Powered by Arch Linux! I am registered Linux user number 508465:
>>>> https://linuxcounter.net/user/508465.html
>>>> My blog, Thoughts of a Dragon: http://www.stormdragon.tk/
>>>> get my public PGP key: gpg --keyserver wwwkeys.pgp.net --recv-key
>>>> 43DDC193
>>>> Twitter and Facebook are so ... yesteryear. Get your 2MB Social account
>>>> TODAY! http://2mb.social/main/register
>>>> Follow me on GNU Social: https://social.stormdragon.tk/storm
>>>> "Fell in a river of illusion and apathy"
>>>> Godsmack - Realign
>>>
>>>
>>>
>>>
>>> --
>>> echo mailto: NOSPAM !#$.'<*>'|sed 's. ..'|tr "<*> !#:2" org@fr33z3
>>
>>
>



-- 
echo mailto: NOSPAM !#$.'<*>'|sed 's. ..'|tr "<*> !#:2" org@fr33z3