Re: [DNG] meta: list
On Wed, Aug 31, 2022 at 09:14:31AM +0200, marc wrote: > Hi > > Just a quick note that in the last week or so google seems > have ratcheted up its rejection of mail from independent MTAs > a notch or two. > > IF you check your logs, you might see 550 rejects with a message > such as > > Our system has detected that this message is likely > unsolicited mail. To reduce the amount of spam sent > to Gmail, this message has been blocked. Please visit > https://support.google.com/mail/?p=UnsolicitedMessageError > for more information. > > In this case this is for an IP+DNS combination that is known > to never have sent spam. And of course the supreme irony of > the matter is that google itself stands accused of injecting > spam into people's email - see noyb.eu > > The first reaction is to be a bit bleak about this, but > giving it some thought, there might be a silver lining to > this: This might be a significant step in the split into > "internet classic" the familiar favourite versus > the "hinternet.google", the free, convenient, but > also watered-down and shrinkflated version. > > Amusingly I think the DNG list here might have gotten > a headstart on this, with its unconfigured reverse > DNS entry - looking through the recent mails I see > next to no participants from gmail.com - presumably > because they haven't seen mail from here. I use gmail, and seem to be getting email from this list. I wonder if it is because I have it skip the inbox, and go straight into a different label. Mike Schmitz ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] gcc-doc
https://people.debian.org/~srivasta/Position_Statement.html On Wed, Sep 1, 2021, 07:19 Antonio A. Rendina via Dng wrote: > Hi, > > I remember that there was a discussion about this, but I'm no able to > find it anymore. The question is how do I install the gcc-doc package? > > For what I understand Debian put it on non-free, but on Devuan a have > non-free and contrib enabled and I still don't find it. > > Thanks > > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Rant: was fresh install of chimaera on an Ultrabook - no touchpad
On Fri, Jul 30, 2021 at 11:22:56PM +1000, terryc wrote: > On Fri, 30 Jul 2021 21:07:43 +0900 > Olaf Meeuwissen via Dng wrote: > > > Hi g4sra, > > > > g4sra via Dng writes: > > > > > <--snip--> > > > This is why Devuan's installer will ask\prompt you to insert > > > additional installation media such as a USB stick. There are just > > > too many Gigabytes of Drivers required to satisfy every corner > > > case, put the drivers your quirky hardware requires on a USB stick > > > and use it when prompted! I do not ever want to have to install an > > > OS from 31 removable media's ever again! (Windows NT > > > anybody?).___ > > I've done that once, but mostly it has been various versions of Novell > which thankfully are not that many as NT was. > > > > > Me waxes nostalgic and remembers installing Debian from 12 > > floppies ;-) -- > > Did it work? > > My installation didn't, so I then tried the Slackware floppies which > also didn't work. By the time I switched to Debian (.9x release), the ATA cdroms were working with the kernel without modification. Before that, I would drive to Pullman, WA, where a friend was going to school, with a large pack of 3.5" floppies and a blank CD, since it would take too long at 2400 baud to download from where I lived. I would spend the weekend there, downloading the install set of Slackware with enough packages to be able to rebuild the kernel, and put the rest of the packages I needed onto the CD. I would bring the whole mess back home, get the base system up, modify the source of the kernel to recognize my CDROM drive, and then build the kernel, so I could finish setting it up on my shiny new 386DX. Friends would be angry with me, since I would do all this with a 12pack of beer, and not remember how I did it the next day. (The installation was done drunk, not the rest of it...) > Aaah, those were the days. Indeed... signature.asc Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] more issues (RE: Beowulf Beta is here!)
On Sat, Apr 11, 2020 at 08:15:51PM -0700, Gregory Nowak wrote: > On Sat, Apr 11, 2020 at 02:47:27PM +, dal wrote: > > When I manually arrange networking and try to use > > > > deb http://deb.devuan.org/merged beowulf main > > deb http://deb.devuan.org/merged beowulf-updates main > > deb http://deb.devuan.org/merged beowulf-security main > > > > then the set of available packages seems to be quite short, lacking things > > like "less". > > > > What is wrong? > > Did you update the list of available packages with apt-get update? OOPS! sorry, I thought you were addressing me. Sorry for the noise. signature.asc Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] more issues (RE: Beowulf Beta is here!)
On Sat, Apr 11, 2020 at 08:15:51PM -0700, Gregory Nowak wrote: > On Sat, Apr 11, 2020 at 02:47:27PM +, dal wrote: > > When I manually arrange networking and try to use > > > > deb http://deb.devuan.org/merged beowulf main > > deb http://deb.devuan.org/merged beowulf-updates main > > deb http://deb.devuan.org/merged beowulf-security main > > > > then the set of available packages seems to be quite short, lacking things > > like "less". > > > > What is wrong? > > Did you update the list of available packages with apt-get update? yes. signature.asc Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] less ;-)
On Sat, Apr 11, 2020 at 10:52:48AM -0400, Hendrik Boom wrote: > On Sat, Apr 11, 2020 at 02:47:27PM +, dal wrote: > > > > > When I manually arrange networking and try to use > > > > deb http://deb.devuan.org/merged beowulf main > > deb http://deb.devuan.org/merged beowulf-updates main > > deb http://deb.devuan.org/merged beowulf-security main > > > > then the set of available packages seems to be quite short, lacking things > > like "less". > > Let me hope it isn't because Debian's "less" now requires systemd! looks ok from here: $ egrep "^deb " /etc/apt/sources.list && grep -l "Package: less" /var/lib/apt/lists/*Packages deb http://deb.devuan.org/merged beowulf main non-free contrib deb http://deb.devuan.org/merged beowulf-security main non-free contrib deb http://deb.devuan.org/merged beowulf-updates main non-free contrib deb http://deb.devuan.org/merged beowulf-backports main non-free contrib /var/lib/apt/lists/deb.devuan.org_merged_dists_beowulf-backports_main_binary-amd64_Packages /var/lib/apt/lists/deb.devuan.org_merged_dists_beowulf_main_binary-amd64_Packages signature.asc Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Beowulf Beta is here!
On Thu, Apr 09, 2020 at 11:23:24PM +, aitor_czr wrote: > Hi Didier, > > On 4/9/20 10:19 PM, aitor_czr wrote: > > Sorry for the typo. install *ifplugd* or an equivalent. > Another clarification: ifplugd depends on ifupdown and breaks with > ifupdown2. The > real culprit of the startup delay is ifupdown together with dhcp, and it's > not caused > by the time-out activation of the wired interface as you pointed out, but > rather by > the management ofany of the existent clauses for /etc/network/interfaces > with the > wrong version ofifupdown -better said-, regardless whether is a wired or > wireless > device. There was a fix on dev1galaxy, but I can't seem to get there right now. I think is this link: http://dev1galaxy.org/viewtopic.php?id=1688 it includes a patch for /etc/init.d/networking to back out some changes that they put in there for systemdon't signature.asc Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] libnetaid and simple-netaid-cdk released!
On Sun, Apr 05, 2020 at 02:04:37PM +, aitor_czr wrote: > Hi all, > > Today i uploaded the first releases of libnetaid and simple-netaid-cdk. > Here you are the packages: > > http://gnuinos.org/simple-netaid-cdk/simple-netaid.tar.gz > > Just install the packages appropriate to your architecture, add the > following > > lines to the /etc/network/interfaces files: > > iface eth0 inet dhcp > iface wlan0 inet dhcp > > and run *simple-netaid-cdk* in the command line. One thing I ran into right away, and took me a few tries before I figured it out; I needed to quote my passphrase, since it has spaces. It might be good to do that in your call to wpa-passphrase. It shouldn't have taken as many tries as it did, since I just went through it with a script I am working on (I am bulding a plugin for awesomewm to do this). It also doesn't seem to store the passphrase anywhere, so the user would still need to type it in every time. signature.asc Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Fonts in testing/unstable are some ugly.
On Tue, Oct 15, 2019 at 01:40:34AM +0700, Андрей via Dng wrote: > Приветствую. > > > В Tue, 8 Oct 2019 08:32:22 -0400, ты писал(а): > > > Long ago, in X, wasn't there a font explorer tool that you could use > > to fund different kinds of fonts and let you explore what they looked > > like in different resolutions? The problem it solved was that even > > when you found a nice font it wouldn't be available in all > > resolutions? > > > > I ask because I'm having trouble choosing a font size in xterm. > > I would dream of a tool that lets me know what font is in what package. > For there a lot of packages in repo, but i do not know what to choose, > and to try it all is a lot of effort. You might try font-manager. It doesn't help with the packages, but it will help to view installed (or even not installed) fonts. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Olimex Teres A64
I have an Olimex Teres A64 coming in on Thursday. I was wondering if anyone has gotten one of these working w/Devuan. The provide an Ubuntu image and an Android image for download from Olimex. Mike Schmitz signature.asc Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Call for testing: ConsoleKit2
On Wed, Jan 17, 2018 at 07:02:36PM +0300, Hleb Valoshka wrote: > Hi! > > ConsoleKit2 has been packaged for experimental (but it's also > installable in Ascii). > > This is an update for the old ConsoleKit and can be installed instead of it. > > Please help with its testing. What to test: PC stop/hibernate/etc, > mounting of usb drives and so on under DEs. > > === > deb http://packages.devuan.org/devuan/ experimental main > === it seems to want to install eudev. I am currently running vdev. Will it work together? signature.asc Description: Digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Bluetooth headset on Devuan?
On Tue, Nov 07, 2017 at 09:09:27AM -0600, dev wrote: > > > On 11/06/2017 11:04 AM, Mike Schmitz wrote: > <snip? > > > > I haven't had any problem with this. Well some choppiness when the > > computer/network is overworked doing something else... > > I'm wondering if it's due to buffer underruns. Are these buffer sizes > the same as yours:? > > ../../../src/asound/bluealsa-pcm.c:295: FIFO buffer size: 4096 > ../../../src/asound/bluealsa-pcm.c:301: Selected HW buffer: 6 periods x > 16000 bytes <= 96004 bytes ../../../src/asound/bluealsa-pcm.c:295: FIFO buffer size: 4096 ../../../src/asound/bluealsa-pcm.c:301: Selected HW buffer: 20 periods x 1920 bytes == 38400 bytes signature.asc Description: Digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Bluetooth headset on Devuan?
On Mon, Nov 06, 2017 at 08:46:03AM -0600, dev wrote: > > > On 11/01/2017 06:13 PM, Mike Schmitz wrote: > > > Ok, false alarm. I forgot to make certain it connected. > > You might want to check that too. It is flaky and doesn't always connect > > properly. > > > > I also wrote an init script (attached) that might work for you, when you > > get it working. > > Yes, getting things connected is a bit of a process. Having to set > amixer each time to lower the volume levels is a bit of an annyoance. > > Do you know how to make the bluetooth headset the output device for > Palemoon? I would assume it's a setting in ~/.asoundrc. setting it as the default alsa output should work. I typically use youtube-dl | mpv, so I haven't tested this. > Thanks for passing the script along! I've got it working now, but the > audio is quite choppy at times. Not sure why that is. If I set > "discoverable" and "scan" to "off" it gets better. Is your experience > about the same? I haven't had any problem with this. Well some choppiness when the computer/network is overworked doing something else... signature.asc Description: Digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Bluetooth headset on Devuan?
On Wed, Nov 01, 2017 at 02:14:27PM -0700, Mike Schmitz wrote: > On Wed, Nov 01, 2017 at 01:43:32PM -0700, Mike Schmitz wrote: > > On Wed, Nov 01, 2017 at 08:31:55AM -0500, dev wrote: > > > On 10/31/2017 12:42 PM, Mike Schmitz wrote: > > > > > > > > > > > Another project has picked up the ball and run with it, though. It works > > > > for me (SoundBot SB220) > > > > > > > > https://github.com/Arkq/bluez-alsa > > > > > > > > > > Nice! I've got it almost working. I'm stuck on "Couldn't get BlueALSA > > > transport: No such device" Any thoughts? From what I've googled so far, > > > solutions involve pulseaudio, or reference a pulseaudio conflict. I > > > have some libpulse scattieness installed[0] for apulse support, but > > > maybe I cannot have both? Perhaps I should remove those? > > > > > > So far, I've installed alsa and development libs[1] but had to add the > > > debian jessie repo[2] in order to get libfdk-aac-dev. Is there another > > > place for this? > > > > > > I cloned the bluez-alsa git repo and built per git page[3]. Configured > > > ~/.asoundrc for my bluetooth headset MAC[4]. The alsa-lib directory > > > installed to a location unknown to Devaun[5] so I sylinked[6] the new > > > libraries to a good location. I did 'echo /usr/lib/alsa-lib > > > > /etc/ld.so.conf.d/alsa-lib.conf' but this did not seem to help after > > > issuing ldconfig. > > > > > > The bluealsa "server" seems to start ok and generates no errors[7] when > > > trying to play a sound via aplay, however aplay does not seem to know[8] > > > yet how to use the headset. I did have an issue with permissions on[9] > > > on /var/run/bluealsa but I think I fixed those[9]. Right now, aplay > > > cannot "get BlueALSA transport"[10]. Any thoughts? > > > > > > Thank you! > > > > > > [0] > > > i apulse - PulseAudio emulation for ALSA > > > > > > i libpulse-mainloop-glib0 - PulseAudio client libraries (glib > > > support) > > > i libpulse0 - PulseAudio client libraries > > > > > > i libpulsedsp - PulseAudio OSS pre-load library > > > > > > i pulseaudio-utils- Command line tools for the > > > PulseAudio soun > > > i vlc-plugin-pulse- transitional dummy package for vlc > > > > > > > > > > > > [1] > > > aptitude install libalsaplayer-dev bluez bluez-tools libsbc-dev > > > libfdk-aac-dev alsa-tools alsaplayer-alsa libasound2-dev bluez-hcidump > > > checkinstall libusb-dev libbluetooth-dev libbluetooth-dev > > > libbluetooth3-dev > > > libglib2.0-dev > > > > > > [2] > > > Add debian jessie rep for libfdk-aac-dev > > > > > > libfdk-aac-dev required repo: > > >deb http://httpredir.debian.org/debian/ jessie main contrib non-free > > > > > > aptitude install libfdk-aac-dev > > > > > > [3] > > > git clone https://github.com/Arkq/bluez-alsa.git > > > cd bluez-alsa; mkdir build; autoreconf --install; cd build; ../configure > > > --enable-aac --enable-debug > > > make > > > make install > > > > > > > > > [4] > > > $ cat ~/.asoundrc > > > defaults.bluealsa.interface "hci0" > > > defaults.bluealsa.device "02:FC:9F:F8:13:94" > > > defaults.bluealsa.profile "a2dp" > > > > > > [5] > > > $ aplay -D bluealsa:HCI=hci0,DEV=02:FC:9F:F8:13:94,PROFILE=a2dp > > > /usr/share/sounds/purple/Windows\ Notify.wav > > > ALSA lib dlmisc.c:252:(snd1_dlobj_cache_get) Cannot open shared library > > > /usr/lib/x86_64-linux-gnu/alsa-lib/libasound_module_pcm_bluealsa.so > > > aplay: main:722: audio open error: No such device or address > > > > > > [6] > > > # ldconfig -v | grep alsa > > > > > > /usr/lib/alsa-lib: > > > libasound_module_ctl_bluealsa.so -> libasound_module_ctl_bluealsa.so > > > libasound_module_pcm_bluealsa.so -> libasound_module_pcm_bluealsa.so > > > > > > # ln -s /usr/lib/alsa-lib/libasound_module_* > > > /usr/lib/x86_64-linux-gnu/alsa-lib/ > > > > > > > > > [7] > > > $ bluealsa --disable-hfp > > > bluealsa: ../../src/ctl.c:489: Starting
Re: [DNG] Bluetooth headset on Devuan?
On Wed, Nov 01, 2017 at 01:43:32PM -0700, Mike Schmitz wrote: > On Wed, Nov 01, 2017 at 08:31:55AM -0500, dev wrote: > > On 10/31/2017 12:42 PM, Mike Schmitz wrote: > > > > > > > > Another project has picked up the ball and run with it, though. It works > > > for me (SoundBot SB220) > > > > > > https://github.com/Arkq/bluez-alsa > > > > > > > Nice! I've got it almost working. I'm stuck on "Couldn't get BlueALSA > > transport: No such device" Any thoughts? From what I've googled so far, > > solutions involve pulseaudio, or reference a pulseaudio conflict. I > > have some libpulse scattieness installed[0] for apulse support, but > > maybe I cannot have both? Perhaps I should remove those? > > > > So far, I've installed alsa and development libs[1] but had to add the > > debian jessie repo[2] in order to get libfdk-aac-dev. Is there another > > place for this? > > > > I cloned the bluez-alsa git repo and built per git page[3]. Configured > > ~/.asoundrc for my bluetooth headset MAC[4]. The alsa-lib directory > > installed to a location unknown to Devaun[5] so I sylinked[6] the new > > libraries to a good location. I did 'echo /usr/lib/alsa-lib > > > /etc/ld.so.conf.d/alsa-lib.conf' but this did not seem to help after > > issuing ldconfig. > > > > The bluealsa "server" seems to start ok and generates no errors[7] when > > trying to play a sound via aplay, however aplay does not seem to know[8] > > yet how to use the headset. I did have an issue with permissions on[9] > > on /var/run/bluealsa but I think I fixed those[9]. Right now, aplay > > cannot "get BlueALSA transport"[10]. Any thoughts? > > > > Thank you! > > > > [0] > > i apulse - PulseAudio emulation for ALSA > > > > i libpulse-mainloop-glib0 - PulseAudio client libraries (glib > > support) > > i libpulse0 - PulseAudio client libraries > > > > i libpulsedsp - PulseAudio OSS pre-load library > > > > i pulseaudio-utils- Command line tools for the > > PulseAudio soun > > i vlc-plugin-pulse- transitional dummy package for vlc > > > > > > > > [1] > > aptitude install libalsaplayer-dev bluez bluez-tools libsbc-dev > > libfdk-aac-dev alsa-tools alsaplayer-alsa libasound2-dev bluez-hcidump > > checkinstall libusb-dev libbluetooth-dev libbluetooth-dev > > libbluetooth3-dev > > libglib2.0-dev > > > > [2] > > Add debian jessie rep for libfdk-aac-dev > > > > libfdk-aac-dev required repo: > >deb http://httpredir.debian.org/debian/ jessie main contrib non-free > > > > aptitude install libfdk-aac-dev > > > > [3] > > git clone https://github.com/Arkq/bluez-alsa.git > > cd bluez-alsa; mkdir build; autoreconf --install; cd build; ../configure > > --enable-aac --enable-debug > > make > > make install > > > > > > [4] > > $ cat ~/.asoundrc > > defaults.bluealsa.interface "hci0" > > defaults.bluealsa.device "02:FC:9F:F8:13:94" > > defaults.bluealsa.profile "a2dp" > > > > [5] > > $ aplay -D bluealsa:HCI=hci0,DEV=02:FC:9F:F8:13:94,PROFILE=a2dp > > /usr/share/sounds/purple/Windows\ Notify.wav > > ALSA lib dlmisc.c:252:(snd1_dlobj_cache_get) Cannot open shared library > > /usr/lib/x86_64-linux-gnu/alsa-lib/libasound_module_pcm_bluealsa.so > > aplay: main:722: audio open error: No such device or address > > > > [6] > > # ldconfig -v | grep alsa > > > > /usr/lib/alsa-lib: > > libasound_module_ctl_bluealsa.so -> libasound_module_ctl_bluealsa.so > > libasound_module_pcm_bluealsa.so -> libasound_module_pcm_bluealsa.so > > > > # ln -s /usr/lib/alsa-lib/libasound_module_* > > /usr/lib/x86_64-linux-gnu/alsa-lib/ > > > > > > [7] > > $ bluealsa --disable-hfp > > bluealsa: ../../src/ctl.c:489: Starting controller loop > > bluealsa: ../../src/bluez.c:680: Registering endpoint: /A2DP/MPEG24/Source/1 > > bluealsa: ../../src/bluez.c:680: Registering endpoint: /A2DP/MPEG24/Sink/1 > > bluealsa: ../../src/bluez.c:680: Registering endpoint: /A2DP/SBC/Source/1 > > bluealsa: ../../src/bluez.c:680: Registering endpoint: /A2DP/SBC/Sink/1 > > bluealsa: ../../src/bluez.c:910: Registering profile: /HSP/Headset > > bluealsa: ../../src/bluez.c:910: Registering profile: /HSP/AudioGateway > > bluealsa: ../../src/main.c:225: Starting
Re: [DNG] Bluetooth headset on Devuan?
On Wed, Nov 01, 2017 at 08:31:55AM -0500, dev wrote: > On 10/31/2017 12:42 PM, Mike Schmitz wrote: > > > > > Another project has picked up the ball and run with it, though. It works > > for me (SoundBot SB220) > > > > https://github.com/Arkq/bluez-alsa > > > > Nice! I've got it almost working. I'm stuck on "Couldn't get BlueALSA > transport: No such device" Any thoughts? From what I've googled so far, > solutions involve pulseaudio, or reference a pulseaudio conflict. I > have some libpulse scattieness installed[0] for apulse support, but > maybe I cannot have both? Perhaps I should remove those? > > So far, I've installed alsa and development libs[1] but had to add the > debian jessie repo[2] in order to get libfdk-aac-dev. Is there another > place for this? > > I cloned the bluez-alsa git repo and built per git page[3]. Configured > ~/.asoundrc for my bluetooth headset MAC[4]. The alsa-lib directory > installed to a location unknown to Devaun[5] so I sylinked[6] the new > libraries to a good location. I did 'echo /usr/lib/alsa-lib > > /etc/ld.so.conf.d/alsa-lib.conf' but this did not seem to help after > issuing ldconfig. > > The bluealsa "server" seems to start ok and generates no errors[7] when > trying to play a sound via aplay, however aplay does not seem to know[8] > yet how to use the headset. I did have an issue with permissions on[9] > on /var/run/bluealsa but I think I fixed those[9]. Right now, aplay > cannot "get BlueALSA transport"[10]. Any thoughts? > > Thank you! > > [0] > i apulse - PulseAudio emulation for ALSA > > i libpulse-mainloop-glib0 - PulseAudio client libraries (glib > support) > i libpulse0 - PulseAudio client libraries > > i libpulsedsp - PulseAudio OSS pre-load library > > i pulseaudio-utils- Command line tools for the > PulseAudio soun > i vlc-plugin-pulse- transitional dummy package for vlc > > > > [1] > aptitude install libalsaplayer-dev bluez bluez-tools libsbc-dev > libfdk-aac-dev alsa-tools alsaplayer-alsa libasound2-dev bluez-hcidump > checkinstall libusb-dev libbluetooth-dev libbluetooth-dev > libbluetooth3-dev > libglib2.0-dev > > [2] > Add debian jessie rep for libfdk-aac-dev > > libfdk-aac-dev required repo: >deb http://httpredir.debian.org/debian/ jessie main contrib non-free > > aptitude install libfdk-aac-dev > > [3] > git clone https://github.com/Arkq/bluez-alsa.git > cd bluez-alsa; mkdir build; autoreconf --install; cd build; ../configure > --enable-aac --enable-debug > make > make install > > > [4] > $ cat ~/.asoundrc > defaults.bluealsa.interface "hci0" > defaults.bluealsa.device "02:FC:9F:F8:13:94" > defaults.bluealsa.profile "a2dp" > > [5] > $ aplay -D bluealsa:HCI=hci0,DEV=02:FC:9F:F8:13:94,PROFILE=a2dp > /usr/share/sounds/purple/Windows\ Notify.wav > ALSA lib dlmisc.c:252:(snd1_dlobj_cache_get) Cannot open shared library > /usr/lib/x86_64-linux-gnu/alsa-lib/libasound_module_pcm_bluealsa.so > aplay: main:722: audio open error: No such device or address > > [6] > # ldconfig -v | grep alsa > > /usr/lib/alsa-lib: > libasound_module_ctl_bluealsa.so -> libasound_module_ctl_bluealsa.so > libasound_module_pcm_bluealsa.so -> libasound_module_pcm_bluealsa.so > > # ln -s /usr/lib/alsa-lib/libasound_module_* > /usr/lib/x86_64-linux-gnu/alsa-lib/ > > > [7] > $ bluealsa --disable-hfp > bluealsa: ../../src/ctl.c:489: Starting controller loop > bluealsa: ../../src/bluez.c:680: Registering endpoint: /A2DP/MPEG24/Source/1 > bluealsa: ../../src/bluez.c:680: Registering endpoint: /A2DP/MPEG24/Sink/1 > bluealsa: ../../src/bluez.c:680: Registering endpoint: /A2DP/SBC/Source/1 > bluealsa: ../../src/bluez.c:680: Registering endpoint: /A2DP/SBC/Sink/1 > bluealsa: ../../src/bluez.c:910: Registering profile: /HSP/Headset > bluealsa: ../../src/bluez.c:910: Registering profile: /HSP/AudioGateway > bluealsa: ../../src/main.c:225: Starting main dispatching loop > bluealsa: ../../src/ctl.c:550: New client accepted: 8 > bluealsa: ../../src/ctl.c:571: +-+- > bluealsa: ../../src/ctl.c:571: +-+- > bluealsa: ../../src/ctl.c:521: Client closed connection: 8 > bluealsa: ../../src/ctl.c:571: +-+- > > > [8] > $ aplay -D bluealsa:HCI=hci0,DEV=02:FC:9F:F8:13:94,PROFILE=a2dp > /usr/share/sounds/purple/Windows\ Notify.wav > ../../../src/asound/../shared/ctl-client.c:102: Connecting to socket: > /var/run/bluealsa/hci0 > ALSA lib ../../../src/asound/bluealsa-pcm.c:645:(_snd_pcm_bluealsa_open) &
Re: [DNG] Bluetooth headset on Devuan?
On Tue, Oct 31, 2017 at 10:16:30AM -0500, dev wrote: > I'm trying to setup a bluetooth wireless headset under Devuan but not > able to get past the pairing. Started with the "blueman-applet" which > looked nice but after pairing and trusting, three icons would show up ( > which I think were related to signal level and volumes) and then they > would disappear. Alas, I dropped to the command line to produce the > output below via "bluetoothctl". > > This shows blueman-applet finding, pairing and connecting but ultimately > disconnecting from the headset. Any ideas why it will not stay connected? > > Headset is here: > https://www.amazon.com/Labvon-Bluetooth-Headphones-Sweatproof-Cancelling/dp/B075S6WXBH/ > > BT dongle is here: > https://www.amazon.com/Bluetooth-Ideapro-Transmitter-Raspberry-Compatible/dp/B00OH09OXS/ > > Thanks > > > [bluetooth]# info 02:FC:9F:F8:13:94 > Device 02:FC:9F:F8:13:94 > Name: S7 > Alias: S7 > Class: 0x240408 > Icon: audio-card > Paired: no > Trusted: no > Blocked: no > Connected: no > LegacyPairing: yes > [DEL] Device 02:FC:9F:F8:13:94 S7 > [NEW] Device 02:FC:9F:F8:13:94 S7 > [CHG] Device 02:FC:9F:F8:13:94 Connected: yes > [CHG] Device 02:FC:9F:F8:13:94 UUIDs: > 1101--1000-8000-00805f9b34fb > 110b--1000-8000-00805f9b34fb > 110c--1000-8000-00805f9b34fb > 110e--1000-8000-00805f9b34fb > 111e--1000-8000-00805f9b34fb > [CHG] Device 02:FC:9F:F8:13:94 Paired: yes > [bluetooth]# info 02:FC:9F:F8:13:94 > Device 02:FC:9F:F8:13:94 > Name: S7 > Alias: S7 > Class: 0x240408 > Icon: audio-card > Paired: yes > Trusted: no > Blocked: no > Connected: yes > LegacyPairing: yes > UUID: Serial Port (1101--1000-8000-00805f9b34fb) > UUID: Audio Sink(110b--1000-8000-00805f9b34fb) > UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) > UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) > UUID: Handsfree (111e--1000-8000-00805f9b34fb) > [CHG] Device 02:FC:9F:F8:13:94 Connected: no Bluetooth audio is usually done through pulseaudio. It was dropped from bluez/alsa in the version used in Jessie. Another project has picked up the ball and run with it, though. It works for me (SoundBot SB220) https://github.com/Arkq/bluez-alsa signature.asc Description: Digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] laptop lid switch
On Wed, Mar 23, 2016 at 06:46:41AM +0100, Jaromil wrote: > > dear Mike, > > thanks for your small reminder on the lid suspend! You're welcome > we'll try to collect such short howtos on the https://talk.devuan.org it really wasn't meant as a howto, just debugging info, as I it doesn't suspend on the activation of the lid switch. > website in the close future (while this list will stay for the general > discussion of the DNG community), so if you are not too web forum > adverse (which we can understand) please consider posting it there I am a bit web forum adverse, but I am willing to help, and will post it there (when things actually work). > somewhere. It will also nicely integrate in the new website... signature.asc Description: Digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] laptop lid switch
I think I remember this being discussed before on this list, but I couldn't find it in the archives. I apologize in advance if... I installed alpha4 on my AspireOne over the weekend. I got suspend working as a user with tweaks to polkit, and it shows up as an option in the XFCE Power Manager dialog. I told it to suspend when closing the lid. I also proved that acpi knows when the lid is closed using this script: #!/bin/sh cat /proc/acpi/button/lid/LID/state # state: open echo "Close lid now" sleep 2 cat /proc/acpi/button/lid/LID/state # state: closed systemd is not installed: dpkg -l | grep systemd ii libsystemd0:amd64 215-17+deb8u3amd64systemd utility library ii systemd-shim9-1 amd64shim for systemd I suspect some systemd vestige is causing this. signature.asc Description: Digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [Dng] Ста Деюс: As a russian, I have question for you.
On Wed, Mar 04, 2015 at 10:29:28PM +0100, Tom Collins wrote: Snowden ‘working exhaustively’ with US to secure terms of trial https://firstlook.org/theintercept/2015/03/04/snowden-wants-come-home-stories-case-study-media-deceit/ ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
