hello,
thanks for your generous help!
maybe i am behind a vpn as yesterday i did install test-wise the protonvpn and connected it;
did think that it does not auto-connect upon reboot, but am not so sure about it anymore.
maybe this has caused an issue?

On Devuan Beowulf this error is still persistent (with XFCE4).

after installing "gvfs*" network places  would show up, but afterwards, when clicking a folder on my network drive,

an "open with" dialogue comes up and asks me with which program i want to open "unknown" file ...

thank you very much!

this led me to reconfigure reportbug and entering a gmail adress.

the next reportbug was also rejected with updated error

Saving a backup of the report at /tmp/reportbug-xfce4-power-manager-backup-20200304-3439-lul_qn4s
Connecting to mx.devuan.org via SMTP...
SMTP send failure: {'submit@bugs.devuan.org': (450, b'4.7.25 Client host
rejected: cannot find your hostname, [151.62.1.237]')}. Do you want to retry
(or else save the report and exit)? [Y|n|q|?]? 

It seems that i have alsa-utils already installed

this could mean that something is not functioning on the cmus alsa-backend side?

can you confirm that your alsa is functioing also when pulseaudio is shut-off?

i don't know,

when i changed the above line to

set output_plugin=alsa

an error came up; when i tried to install alsa package, there was the message "package not found" or similar, that got me thinking this is not installed.

the exact error that comes up with alsa is

Error: opening audio device: No such file or directory

I am using Debian since Wheezy/Squeeze, and Alsa was always default package.

well, in the meantime i downgraded to jessie devuan (where wifi worked ootb) and then upgraded from there to ascii; now the wifi is there.
don't know if previously i made an error or the wifi was just not there or just hidden.

(solution)
works for me.
thanks alot

I reverted back to Devuan Jessie, and there the Wifi + Bluetooth are recognized and installed out of the box (with WIFI hardware-switch set ON).

Probably never saw so many connections WIFI available on my computer at once; a bit scary.

The problem now is with Bluetooth as i am trying to access my MacMiniServer via NAP (Network Access Point - PAN)

on Gnome this function is available and functions well, albeit slow with the Bluetooth 2.1 card (surfing with around 100kb/s)

to achieve this i am trying to install all available packages as i did on gnome, but it would complain

sudo apt-get install bluez*
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Note, selecting 'bluespike' for regex 'bluez*'
Note, selecting 'compass-blueprint-plugin' for regex 'bluez*'
Note, selecting 'jquery-jplayer-bluemonday' for regex 'bluez*'
Note, selecting 'bluefish-unstable' for regex 'bluez*'
Note, selecting 'python2.7-lightblue' for regex 'bluez*'
Note, selecting 'bluedevil' for regex 'bluez*'
Note, selecting 'pulseaudio-module-bluetooth-dbg' for regex 'bluez*'
Note, selecting 'ruby-bluefeather' for regex 'bluez*'
Note, selecting 'bluefish-unstable-data' for regex 'bluez*'
Note, selecting 'python-bluetooth' for regex 'bluez*'
Note, selecting 'bluetooth' for regex 'bluez*'
Note, selecting 'bluez-network' for regex 'bluez*'
Note, selecting 'bluefish' for regex 'bluez*'
Note, selecting 'bluez-firmware' for regex 'bluez*'
Note, selecting 'blueproximity' for regex 'bluez*'
Note, selecting 'bluez-test-scripts' for regex 'bluez*'
Note, selecting 'python-bluez' for regex 'bluez*'
Note, selecting 'blueman' for regex 'bluez*'
Note, selecting 'libbluetooth3' for regex 'bluez*'
Note, selecting 'bluez-cups' for regex 'bluez*'
Note, selecting 'libgnome-bluetooth13' for regex 'bluez*'
Note, selecting 'libnet-bluetooth-perl' for regex 'bluez*'
Note, selecting 'libbluetooth3-dbg' for regex 'bluez*'
Note, selecting 'bluez-utils' for regex 'bluez*'
Note, selecting 'bluez-pan' for regex 'bluez*'
Note, selecting 'bluez-alsa' for regex 'bluez*'
Note, selecting 'bluefish-plugins' for regex 'bluez*'
Note, selecting 'libbluetooth3-dev' for regex 'bluez*'
Note, selecting 'libbluetooth-dev' for regex 'bluez*'
Note, selecting 'python2.7-bluez' for regex 'bluez*'
Note, selecting 'qtdeclarative5-qtbluetooth-plugin' for regex 'bluez*'
Note, selecting 'bluez-obexd' for regex 'bluez*'
Note, selecting 'libpam-blue' for regex 'bluez*'
Note, selecting 'bluez' for regex 'bluez*'
Note, selecting 'bluez-gnome' for regex 'bluez*'
Note, selecting 'bluefish-data' for regex 'bluez*'
Note, selecting 'bluemindo' for regex 'bluez*'
Note, selecting 'libbluedevil2' for regex 'bluez*'
Note, selecting 'bluemon' for regex 'bluez*'
Note, selecting 'bluez-tools' for regex 'bluez*'
Note, selecting 'libqt5bluetooth5' for regex 'bluez*'
Note, selecting 'pulseaudio-module-bluetooth' for regex 'bluez*'
Note, selecting 'libbluedevil-dev' for regex 'bluez*'
Note, selecting 'libgnome-bluetooth-dev' for regex 'bluez*'
Note, selecting 'gnome-bluetooth' for regex 'bluez*'
Note, selecting 'gir1.2-gnomebluetooth-1.0' for regex 'bluez*'
Note, selecting 'libgnome-bluetooth8' for regex 'bluez*'
Note, selecting 'kdebluetooth' for regex 'bluez*'
Note, selecting 'bluez-serial' for regex 'bluez*'
Note, selecting 'bluez-dbg' for regex 'bluez*'
Note, selecting 'qml-module-qtbluetooth' for regex 'bluez*'
Note, selecting 'bluez-audio' for regex 'bluez*'
Note, selecting 'python-lightblue' for regex 'bluez*'
Note, selecting 'bluez-hcidump' for regex 'bluez*'
Note, selecting 'bluefish-dbg' for regex 'bluez*'
Note, selecting 'bluez-input' for regex 'bluez*'
Note, selecting 'ruby-bluecloth' for regex 'bluez*'
Note, selecting 'libbluetooth-dev' instead of 'libbluetooth3-dev'
Note, selecting 'python-bluez' instead of 'python-bluetooth'
Note, selecting 'python-bluez' instead of 'python2.7-bluez'
Note, selecting 'python-lightblue' instead of 'python2.7-lightblue'
blueman is already the newest version.
bluetooth is already the newest version.
bluetooth set to manually installed.
bluez is already the newest version.
libbluetooth3 is already the newest version.
libbluetooth3 set to manually installed.
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
gnome-bluetooth : Depends: libpam-systemd but it is not installable
                   Recommends: gnome-control-center but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

any idea on how to overcome this=?

Thanks

I tried to do this today (have several computer running Debian Wheezy 64Bit or Powerpc) with a quite fresh installation on Gnome3 + plus some packages installed

The error when going directly from Wheezy to Devuan Jessie would be

sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Failed
The following packages have unmet dependencies:
 gir1.2-gnomebluetooth-1.0 : Breaks: gnome-bluetooth (< 3.8) but 3.4.2-1 is to be installed
 gnome-bluetooth : Depends: gir1.2-gnomebluetooth-1.0 (= 3.4.2-1) but 3.14.0-2 is to be installed
                   Depends: obexd-client but it is not going to be installed
 gnome-settings-daemon : Depends: libgnome-desktop-3-2 (>= 3.4.0) but it is not going to be installed
                         Depends: libpackagekit-glib2-14 but it is not going to be installed
 gsettings-desktop-schemas : Breaks: gnome-settings-daemon (< 3.10.0) but 3.4.2+git20121218.7c1322-3+deb7u3 is to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

So it seems more intelligent to update to Debian Jessie first, or to remove Gnome3 altogether and then upgrade directly to Devuan Jessie (and skipping Debian Jessie altogether)?