Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #179661 > unrolled thread

Sound problems (mpd, mpv mainly)

Back to article view | Back to linux.debian.user

Contents

  Sound problems (mpd, mpv mainly) Sharon Kimble <boudiccas@skimble.plus.com> - 2017-03-31 21:00 +0200
    Re: Sound problems (mpd, mpv mainly) Sharon Kimble <boudiccas@skimble.plus.com> - 2017-04-01 11:50 +0200
      Re: Sound problems (mpd, mpv mainly) Dan Hitt <dan.hitt@gmail.com> - 2017-04-02 07:10 +0200
        Re: Sound problems (mpd, mpv mainly) Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2017-04-02 10:10 +0200
          Re: Sound problems (mpd, mpv mainly) Dan Hitt <dan.hitt@gmail.com> - 2017-04-02 19:20 +0200
            Re: Sound problems (mpd, mpv mainly) kamaraju kusumanchi <raju.mailinglists@gmail.com> - 2017-04-08 07:30 +0200
              Re: Sound problems (mpd, mpv mainly) Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2017-04-08 09:30 +0200
                Re: Sound problems (mpd, mpv mainly) Frank <zuiderduin@gmx.com> - 2017-04-08 10:50 +0200
                  Re: Sound problems (mpd, mpv mainly) Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2017-04-08 13:20 +0200
                    Re: Sound problems (mpd, mpv mainly) kamaraju kusumanchi <raju.mailinglists@gmail.com> - 2017-04-18 04:40 +0200
                      Re: Sound problems (mpd, mpv mainly) Henrique de Moraes Holschuh <hmh@debian.org> - 2017-04-18 16:40 +0200
              Re: Sound problems (mpd, mpv mainly) Dan Hitt <dan.hitt@gmail.com> - 2017-04-08 23:50 +0200
    Re: Sound problems (mpd, mpv mainly) Ric Moore <wayward4now@gmail.com> - 2017-04-05 17:10 +0200
      Re: Sound problems (mpd, mpv mainly) Martin Read <zen75502@zen.co.uk> - 2017-04-05 23:50 +0200
        Re: Sound problems (mpd, mpv mainly) Martin Read <zen75502@zen.co.uk> - 2017-04-06 12:20 +0200

#179661 — Sound problems (mpd, mpv mainly)

[Multipart message — attachments visible in raw view] — view raw

Since an upgrade on 2017-03-28 my debian Jessie system is continuously
dropping my soundcard such that mpd and mpv have no sound at all, but,
at this time qmmp and mplayer2 both have sound and work as they should.

My sound card is an on-board chip here -

--8<---------------cut here---------------start------------->8---
cat /proc/asound/cards
 0 [PCH            ]: HDA-Intel - HDA Intel PCH
                      HDA Intel PCH at 0xf7330000 irq 50
 1 [NVidia         ]: HDA-Intel - HDA NVidia
                      HDA NVidia at 0xf7080000 irq 17

--8<---------------cut here---------------end--------------->8---

When I start or reboot this computer I do 'sudo alsactl init' to get
sound working, and then run alsamixer, do 'F6' to choose my soundcard
and choose option 0 in above list. Then I run mpd and can listen to my
music and online radio. But, now the sound card is being dropped so I
get zero sound from mpd and/or mpv when I want to watch a saved TV
programme.

On the 28th these were the programmes that were upgraded and installed -

--8<---------------cut here---------------start------------->8---
 Installed:
    gtg:all 0.3.1-1
    python-configobj:all 5.0.6-1
    python-glade2:amd64 2.24.0-4
    python-liblarch:all 2.1.0-2
    python-simplejson:amd64 3.6.5-1
    python-xdg:all 0.25-4
 
 Upgraded:
    chromium:amd64 56.0.2924.76-1~deb8u1 => 57.0.2987.98-1~deb8u1
    eject:amd64 2.1.5+deb1+cvs20081104-13.1 => 2.1.5+deb1+cvs20081104-13.1+deb8u1
    firefox-esr:amd64 45.7.0esr-1~deb8u1 => 45.8.0esr-1~deb8u1
    gir1.2-gst-plugins-base-1.0:amd64 1.4.4-2 => 1.4.4-2+deb8u1
    gir1.2-gstreamer-1.0:amd64 1.4.4-2 => 1.4.4-2+deb8u1
    gstreamer1.0-plugins-bad:amd64 1.4.4-2.1+deb8u1 => 1.4.4-2.1+deb8u2
    gstreamer1.0-plugins-base:amd64 1.4.4-2 => 1.4.4-2+deb8u1
    gstreamer1.0-plugins-good:amd64 1.4.4-2+deb8u2 => 1.4.4-2+deb8u3
    gstreamer1.0-plugins-ugly:amd64 1.4.4-2+b1 => 1.4.4-2+deb8u1
    gstreamer1.0-x:amd64 1.4.4-2 => 1.4.4-2+deb8u1
    iceweasel:all 45.7.0esr-1~deb8u1 => 45.8.0esr-1~deb8u1
    libaudiofile1:amd64 0.3.6-2+deb8u1 => 0.3.6-2+deb8u2
    libgstreamer-plugins-bad1.0-0:amd64 1.4.4-2.1+deb8u1 => 1.4.4-2.1+deb8u2
    libgstreamer-plugins-base1.0-0:amd64 1.4.4-2 => 1.4.4-2+deb8u1
    libgstreamer1.0-0:amd64 1.4.4-2 => 1.4.4-2+deb8u1
    libjbig2dec0:amd64 0.11+20120125-1 => 0.13-4~deb8u1
    libsmbclient:amd64 2:4.2.14+dfsg-0+deb8u2 => 2:4.2.14+dfsg-0+deb8u4
    libwbclient0:amd64 2:4.2.14+dfsg-0+deb8u2 => 2:4.2.14+dfsg-0+deb8u4
    samba-libs:amd64 2:4.2.14+dfsg-0+deb8u2 => 2:4.2.14+dfsg-0+deb8u4
    tzdata-java:all 2016j-0+deb8u1 => 2017a-0+deb8u1
    tzdata:all 2016j-0+deb8u1 => 2017a-0+deb8u1
    virtualbox-5.0:amd64 5.0.32-112930~Debian~jessie => 5.0.36-114008~Debian~jessie
    vivaldi-stable:amd64 1.7.735.46-1 => 1.8.770.50-1
--8<---------------cut here---------------end--------------->8---

I have since removed virtualbox and Vivaldi-stable thinking that they
were the cause of the problem, but its made no difference.

The only way I have found to regain the sound for mpd/mpv is to reboot,
but its now beginning to happen several times a day and its impractical
to keep rebooting.

How can I get sound continuously with mpd and mpv without the card being
seemingly dropped please?

Thanks
Sharon.
-- 
A taste of linux = http://www.sharons.org.uk
TGmeds = http://www.tgmeds.org.uk
DrugFacts = https://www.drugfacts.org.uk  
Debian 8.6, fluxbox 1.3.5-2, emacs 25.1.1.1

[toc] | [next] | [standalone]

#179677

[Multipart message — attachments visible in raw view] — view raw

Sharon Kimble <boudiccas@skimble.plus.com> writes:

> Since an upgrade on 2017-03-28 my debian Jessie system is continuously
> dropping my soundcard such that mpd and mpv have no sound at all, but,
> at this time qmmp and mplayer2 both have sound and work as they should.
>
> My sound card is an on-board chip here -
>
> cat /proc/asound/cards
>  0 [PCH            ]: HDA-Intel - HDA Intel PCH
>                       HDA Intel PCH at 0xf7330000 irq 50
>  1 [NVidia         ]: HDA-Intel - HDA NVidia
>                       HDA NVidia at 0xf7080000 irq 17
>
>
> When I start or reboot this computer I do 'sudo alsactl init' to get
> sound working, and then run alsamixer, do 'F6' to choose my soundcard
> and choose option 0 in above list. Then I run mpd and can listen to my
> music and online radio. But, now the sound card is being dropped so I
> get zero sound from mpd and/or mpv when I want to watch a saved TV
> programme.
>
> On the 28th these were the programmes that were upgraded and installed -
>
>  Installed:
>     gtg:all 0.3.1-1
>     python-configobj:all 5.0.6-1
>     python-glade2:amd64 2.24.0-4
>     python-liblarch:all 2.1.0-2
>     python-simplejson:amd64 3.6.5-1
>     python-xdg:all 0.25-4
>  
>  Upgraded:
>     chromium:amd64 56.0.2924.76-1~deb8u1 => 57.0.2987.98-1~deb8u1
>     eject:amd64 2.1.5+deb1+cvs20081104-13.1 => 2.1.5+deb1+cvs20081104-13.1+deb8u1
>     firefox-esr:amd64 45.7.0esr-1~deb8u1 => 45.8.0esr-1~deb8u1
>     gir1.2-gst-plugins-base-1.0:amd64 1.4.4-2 => 1.4.4-2+deb8u1
>     gir1.2-gstreamer-1.0:amd64 1.4.4-2 => 1.4.4-2+deb8u1
>     gstreamer1.0-plugins-bad:amd64 1.4.4-2.1+deb8u1 => 1.4.4-2.1+deb8u2
>     gstreamer1.0-plugins-base:amd64 1.4.4-2 => 1.4.4-2+deb8u1
>     gstreamer1.0-plugins-good:amd64 1.4.4-2+deb8u2 => 1.4.4-2+deb8u3
>     gstreamer1.0-plugins-ugly:amd64 1.4.4-2+b1 => 1.4.4-2+deb8u1
>     gstreamer1.0-x:amd64 1.4.4-2 => 1.4.4-2+deb8u1
>     iceweasel:all 45.7.0esr-1~deb8u1 => 45.8.0esr-1~deb8u1
>     libaudiofile1:amd64 0.3.6-2+deb8u1 => 0.3.6-2+deb8u2
>     libgstreamer-plugins-bad1.0-0:amd64 1.4.4-2.1+deb8u1 => 1.4.4-2.1+deb8u2
>     libgstreamer-plugins-base1.0-0:amd64 1.4.4-2 => 1.4.4-2+deb8u1
>     libgstreamer1.0-0:amd64 1.4.4-2 => 1.4.4-2+deb8u1
>     libjbig2dec0:amd64 0.11+20120125-1 => 0.13-4~deb8u1
>     libsmbclient:amd64 2:4.2.14+dfsg-0+deb8u2 => 2:4.2.14+dfsg-0+deb8u4
>     libwbclient0:amd64 2:4.2.14+dfsg-0+deb8u2 => 2:4.2.14+dfsg-0+deb8u4
>     samba-libs:amd64 2:4.2.14+dfsg-0+deb8u2 => 2:4.2.14+dfsg-0+deb8u4
>     tzdata-java:all 2016j-0+deb8u1 => 2017a-0+deb8u1
>     tzdata:all 2016j-0+deb8u1 => 2017a-0+deb8u1
>     virtualbox-5.0:amd64 5.0.32-112930~Debian~jessie => 5.0.36-114008~Debian~jessie
>     vivaldi-stable:amd64 1.7.735.46-1 => 1.8.770.50-1
>
> I have since removed virtualbox and Vivaldi-stable thinking that they
> were the cause of the problem, but its made no difference.
>
> The only way I have found to regain the sound for mpd/mpv is to reboot,
> but its now beginning to happen several times a day and its impractical
> to keep rebooting.
>
> How can I get sound continuously with mpd and mpv without the card being
> seemingly dropped please?
>

And the missing link that got it all working nicely again was
'pavucontrol'. Installing and using that regained sound again.

Sharon.
-- 
A taste of linux = http://www.sharons.org.uk
TGmeds = http://www.tgmeds.org.uk
DrugFacts = https://www.drugfacts.org.uk  
Debian 8.6, fluxbox 1.3.5-2, emacs 25.1.1.1

[toc] | [prev] | [next] | [standalone]

#179706

Hi Sharon,

Glad you found a solution in pavucontrol.

When i saw your first post i was interested, because i had a similar
problem (mpv abruptly went silent) and no clue as to how to fix it,
and it arose at just about the same time as yours.

It affected mpv, but not firefox.

Although i don't know what i did to trigger the problem, in the case
of mpv you can give it an option to tell it explicitly what output
device to use for audio.

The command is something like:
   mpv --audio-device=my-device  name_of_file.mp4

So in my case, the command was
   mpv --audio-device=alsa mane_of_file.mp4

If you have no idea what name to use (and i certainly didn't), mpv
will list them for you, if you run this command:
   mpv --audio-device=help

Posting here just in case anybody is searching around for mpv silence
and hits this thread.

dan


On Sat, Apr 1, 2017 at 2:44 AM, Sharon Kimble
<boudiccas@skimble.plus.com> wrote:
> Sharon Kimble <boudiccas@skimble.plus.com> writes:
>
>> Since an upgrade on 2017-03-28 my debian Jessie system is continuously
>> dropping my soundcard such that mpd and mpv have no sound at all, but,
>> at this time qmmp and mplayer2 both have sound and work as they should.
>>
>> My sound card is an on-board chip here -
>>
>> cat /proc/asound/cards
>>  0 [PCH            ]: HDA-Intel - HDA Intel PCH
>>                       HDA Intel PCH at 0xf7330000 irq 50
>>  1 [NVidia         ]: HDA-Intel - HDA NVidia
>>                       HDA NVidia at 0xf7080000 irq 17
>>
>>
>> When I start or reboot this computer I do 'sudo alsactl init' to get
>> sound working, and then run alsamixer, do 'F6' to choose my soundcard
>> and choose option 0 in above list. Then I run mpd and can listen to my
>> music and online radio. But, now the sound card is being dropped so I
>> get zero sound from mpd and/or mpv when I want to watch a saved TV
>> programme.
>>
>> On the 28th these were the programmes that were upgraded and installed -
>>
>>  Installed:
>>     gtg:all 0.3.1-1
>>     python-configobj:all 5.0.6-1
>>     python-glade2:amd64 2.24.0-4
>>     python-liblarch:all 2.1.0-2
>>     python-simplejson:amd64 3.6.5-1
>>     python-xdg:all 0.25-4
>>
>>  Upgraded:
>>     chromium:amd64 56.0.2924.76-1~deb8u1 => 57.0.2987.98-1~deb8u1
>>     eject:amd64 2.1.5+deb1+cvs20081104-13.1 => 2.1.5+deb1+cvs20081104-13.1+deb8u1
>>     firefox-esr:amd64 45.7.0esr-1~deb8u1 => 45.8.0esr-1~deb8u1
>>     gir1.2-gst-plugins-base-1.0:amd64 1.4.4-2 => 1.4.4-2+deb8u1
>>     gir1.2-gstreamer-1.0:amd64 1.4.4-2 => 1.4.4-2+deb8u1
>>     gstreamer1.0-plugins-bad:amd64 1.4.4-2.1+deb8u1 => 1.4.4-2.1+deb8u2
>>     gstreamer1.0-plugins-base:amd64 1.4.4-2 => 1.4.4-2+deb8u1
>>     gstreamer1.0-plugins-good:amd64 1.4.4-2+deb8u2 => 1.4.4-2+deb8u3
>>     gstreamer1.0-plugins-ugly:amd64 1.4.4-2+b1 => 1.4.4-2+deb8u1
>>     gstreamer1.0-x:amd64 1.4.4-2 => 1.4.4-2+deb8u1
>>     iceweasel:all 45.7.0esr-1~deb8u1 => 45.8.0esr-1~deb8u1
>>     libaudiofile1:amd64 0.3.6-2+deb8u1 => 0.3.6-2+deb8u2
>>     libgstreamer-plugins-bad1.0-0:amd64 1.4.4-2.1+deb8u1 => 1.4.4-2.1+deb8u2
>>     libgstreamer-plugins-base1.0-0:amd64 1.4.4-2 => 1.4.4-2+deb8u1
>>     libgstreamer1.0-0:amd64 1.4.4-2 => 1.4.4-2+deb8u1
>>     libjbig2dec0:amd64 0.11+20120125-1 => 0.13-4~deb8u1
>>     libsmbclient:amd64 2:4.2.14+dfsg-0+deb8u2 => 2:4.2.14+dfsg-0+deb8u4
>>     libwbclient0:amd64 2:4.2.14+dfsg-0+deb8u2 => 2:4.2.14+dfsg-0+deb8u4
>>     samba-libs:amd64 2:4.2.14+dfsg-0+deb8u2 => 2:4.2.14+dfsg-0+deb8u4
>>     tzdata-java:all 2016j-0+deb8u1 => 2017a-0+deb8u1
>>     tzdata:all 2016j-0+deb8u1 => 2017a-0+deb8u1
>>     virtualbox-5.0:amd64 5.0.32-112930~Debian~jessie => 5.0.36-114008~Debian~jessie
>>     vivaldi-stable:amd64 1.7.735.46-1 => 1.8.770.50-1
>>
>> I have since removed virtualbox and Vivaldi-stable thinking that they
>> were the cause of the problem, but its made no difference.
>>
>> The only way I have found to regain the sound for mpd/mpv is to reboot,
>> but its now beginning to happen several times a day and its impractical
>> to keep rebooting.
>>
>> How can I get sound continuously with mpd and mpv without the card being
>> seemingly dropped please?
>>
>
> And the missing link that got it all working nicely again was
> 'pavucontrol'. Installing and using that regained sound again.
>
> Sharon.
> --
> A taste of linux = http://www.sharons.org.uk
> TGmeds = http://www.tgmeds.org.uk
> DrugFacts = https://www.drugfacts.org.uk
> Debian 8.6, fluxbox 1.3.5-2, emacs 25.1.1.1

[toc] | [prev] | [next] | [standalone]

#179707

On Sat, 1 Apr 2017, Dan Hitt wrote:

> . . .
> If you have no idea what name to use (and i certainly didn't), mpv
> will list them for you, if you run this command:
>   mpv --audio-device=help
> . . .

hi Dan
what is your mpv version?
For mine, the --audio-device is unknown.
I am on Jessie, with mpv version "0.6.2 (C) 2000-2014 mpv/MPlayer/mplayer2 projects"

best regards,
-- 
Pierre Frenkiel

[toc] | [prev] | [next] | [standalone]

#179714

Hi Pierre,

When i do:
/usr/bin/mpv --version

it responds with:
mpv 0.23.0 (C) 2000-2016 mpv/MPlayer/mplayer2 projects
 built on UNKNOWN
ffmpeg library versions:
   libavutil       55.34.100
   libavcodec      57.64.101
   libavformat     57.56.100
   libswscale      4.2.100
   libavfilter     6.65.100
   libswresample   2.3.100
ffmpeg version: 3.2.2-2

I did not install ffmpeg explicitly, but when i installed mpv it
picked up a bunch of other packages.

(For reference, i did install some other sound packages centered
around sox and sndfile, but i'm guessing these are irrelevant.)

Everything is via apt-get, nothing home-compiled (yet).

/etc/debian_version says '9.0' for me, and i think it is called
'stretch' (it is not in the list of debian versions in the wikipedia,
which stops at 8, 'jessie').

I put debian on a fresh partition (i.e., this is not an upgrade) in
early February this year to get access to some newer and totally
unrelated packages.

The mpv website recommends building your own or using a 3rd party
builds instead of relying on a package.  ("Distributions usually
package outdated, unmaintained, and unsupported versions of mpv. This
is especially true for popular distros like Debian and Ubuntu. You are
recommended to use mpv-build or 3rd party packages instead.")  That's
all in https://mpv.io/installation/

However, despite using both debian and ubuntu, i've never had to do
that yet.  knock on wood! :)

But if you do install something from mpv.io, and it works better for
jessie, please post and tia!

dan

On Sun, Apr 2, 2017 at 1:02 AM, Pierre Frenkiel
<pierre.frenkiel@gmail.com> wrote:
> On Sat, 1 Apr 2017, Dan Hitt wrote:
>
>> . . .
>> If you have no idea what name to use (and i certainly didn't), mpv
>> will list them for you, if you run this command:
>>   mpv --audio-device=help
>> . . .
>
>
> hi Dan
> what is your mpv version?
> For mine, the --audio-device is unknown.
> I am on Jessie, with mpv version "0.6.2 (C) 2000-2014 mpv/MPlayer/mplayer2
> projects"
>
> best regards,
> --
> Pierre Frenkiel
>

[toc] | [prev] | [next] | [standalone]

#179891

On Sun, Apr 2, 2017 at 1:14 PM, Dan Hitt <dan.hitt@gmail.com> wrote:
> /etc/debian_version says '9.0' for me, and i think it is called
> 'stretch' (it is not in the list of debian versions in the wikipedia,
> which stops at 8, 'jessie').

FWIW, you can get this information even without going to wikipedia.

 % sudo apt-get install distro-info-data

 % cat /usr/share/distro-info/debian.csv
version,codename,series,created,release,eol
1.1,Buzz,buzz,1993-08-16,1996-06-17,1997-06-05
1.2,Rex,rex,1996-06-17,1996-12-12,1998-06-05
1.3,Bo,bo,1996-12-12,1997-06-05,1999-03-09
2.0,Hamm,hamm,1997-06-05,1998-07-24,2000-03-09
2.1,Slink,slink,1998-07-24,1999-03-09,2000-10-30
2.2,Potato,potato,1999-03-09,2000-08-15,2003-07-30
3.0,Woody,woody,2000-08-15,2002-07-19,2006-06-30
3.1,Sarge,sarge,2002-07-19,2005-06-06,2008-03-30
4.0,Etch,etch,2005-06-06,2007-04-08,2010-02-15
5.0,Lenny,lenny,2007-04-08,2009-02-14,2012-02-06
6.0,Squeeze,squeeze,2009-02-14,2011-02-06,2014-05-31
7,Wheezy,wheezy,2011-02-06,2013-05-04
8,Jessie,jessie,2013-05-04,2015-04-25
9,Stretch,stretch,2015-04-25
10,Buster,buster,2018-07-01
11,Bullseye,bullseye,2020-11-05
,Sid,sid,1993-08-16
,Experimental,experimental,1993-08-16



-- 
Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog

[toc] | [prev] | [next] | [standalone]

#179893

On Sat, 8 Apr 2017, kamaraju kusumanchi wrote:

> . . .
> % cat /usr/share/distro-info/debian.csv
> . . .
> 11,Bullseye,bullseye,2020-11-05

   hi,
   can you explain why I don't have this line?
   I am on Jessie, but that should not matter.

best regards,
-- 
Pierre Frenkiel

[toc] | [prev] | [next] | [standalone]

#179894

Op 08-04-17 om 09:23 schreef Pierre Frenkiel:
> On Sat, 8 Apr 2017, kamaraju kusumanchi wrote:
>
>> . . .
>> % cat /usr/share/distro-info/debian.csv
>> . . .
>> 11,Bullseye,bullseye,2020-11-05
>
>   hi,
>   can you explain why I don't have this line?
>   I am on Jessie, but that should not matter.

What makes you think it shouldn't matter? Jessie has version 0.26 of the 
distro-info-data package. That line must have been added in a later 
version. Stretch has 0.33 and jessie-backports 0.32~bpo8+1.

Regards,
Frank

[toc] | [prev] | [next] | [standalone]

#179899

On Sat, 8 Apr 2017, Frank wrote:

> What makes you think it shouldn't matter? Jessie has version 0.26 of the 
> distro-info-data package. That line must have been added in a later version. 
> Stretch has 0.33 and jessie-backports 0.32~bpo8+1.

   you are right: installing version .33 actually gives the line
   with version 11. Nevertheless, I don't see why this package is not
   upgraded in Jessie: it just gives a list, and have then no dependency
   problem.

best regards,
-- 
Pierre Frenkiel

[toc] | [prev] | [next] | [standalone]

#180237

On Sat, Apr 8, 2017 at 7:09 AM, Pierre Frenkiel
<pierre.frenkiel@gmail.com> wrote:
>   Nevertheless, I don't see why this package is not
>   upgraded in Jessie: it just gives a list, and have then no dependency
>   problem.

Packages in Debian Stable are upgraded only when it fixes a security
related issue. I agree that the change is very small in this case. But
it does not qualify for an update.

raju
-- 
Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog

[toc] | [prev] | [next] | [standalone]

#180241

On Mon, 17 Apr 2017, kamaraju kusumanchi wrote:
> On Sat, Apr 8, 2017 at 7:09 AM, Pierre Frenkiel
> <pierre.frenkiel@gmail.com> wrote:
> >   Nevertheless, I don't see why this package is not
> >   upgraded in Jessie: it just gives a list, and have then no dependency
> >   problem.
> 
> Packages in Debian Stable are upgraded only when it fixes a security
> related issue. I agree that the change is very small in this case. But

This is incorrect.  Usability issues, as long as they are important
enough, can also be fixed through stable updates, especially when it is
the case of a leaf package, that has less risk of causing regressions on
other packages.

What *does* matter is that the change can be fully understood, and that
the change *is* heavily tested so there are no regressions.

> it does not qualify for an update.

It could, as long as it is very heavily tested.  You will only know if
you do the aforementioned testing, and write a *proper* request (through
reportbug) for the stable release managers asking about it.  Note that
doing this properly is important.  No shortcuts.  No halfbaked reports
missing information.

If it is _not_ worth the trouble, then you know it is not important
enough to deserve a stable update :-)

-- 
  Henrique Holschuh

[toc] | [prev] | [next] | [standalone]

#179909

Thanks Kamaraju, that looks awesome.

So extrapolating from the pattern of the dates, i would guess that
'stretch' should be actually released on the creation date of
'buster', 2018-07-01.

(And i should note, just for the record, that indeed the wikipedia
article on debian versions had more information than i realized; i was
just looking at the infobox at top.  Thanks Pierre for reading more
carefully than me!!)

dan

On Fri, Apr 7, 2017 at 10:19 PM, kamaraju kusumanchi
<raju.mailinglists@gmail.com> wrote:
> On Sun, Apr 2, 2017 at 1:14 PM, Dan Hitt <dan.hitt@gmail.com> wrote:
>> /etc/debian_version says '9.0' for me, and i think it is called
>> 'stretch' (it is not in the list of debian versions in the wikipedia,
>> which stops at 8, 'jessie').
>
> FWIW, you can get this information even without going to wikipedia.
>
>  % sudo apt-get install distro-info-data
>
>  % cat /usr/share/distro-info/debian.csv
> version,codename,series,created,release,eol
> 1.1,Buzz,buzz,1993-08-16,1996-06-17,1997-06-05
> 1.2,Rex,rex,1996-06-17,1996-12-12,1998-06-05
> 1.3,Bo,bo,1996-12-12,1997-06-05,1999-03-09
> 2.0,Hamm,hamm,1997-06-05,1998-07-24,2000-03-09
> 2.1,Slink,slink,1998-07-24,1999-03-09,2000-10-30
> 2.2,Potato,potato,1999-03-09,2000-08-15,2003-07-30
> 3.0,Woody,woody,2000-08-15,2002-07-19,2006-06-30
> 3.1,Sarge,sarge,2002-07-19,2005-06-06,2008-03-30
> 4.0,Etch,etch,2005-06-06,2007-04-08,2010-02-15
> 5.0,Lenny,lenny,2007-04-08,2009-02-14,2012-02-06
> 6.0,Squeeze,squeeze,2009-02-14,2011-02-06,2014-05-31
> 7,Wheezy,wheezy,2011-02-06,2013-05-04
> 8,Jessie,jessie,2013-05-04,2015-04-25
> 9,Stretch,stretch,2015-04-25
> 10,Buster,buster,2018-07-01
> 11,Bullseye,bullseye,2020-11-05
> ,Sid,sid,1993-08-16
> ,Experimental,experimental,1993-08-16
>
>
>
> --
> Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog

[toc] | [prev] | [next] | [standalone]

#179810

On 04/01/2017 05:41 AM, Sharon Kimble wrote:
> Ric Moore <wayward4now@gmail.com> writes:
>
>> On 03/31/2017 02:56 PM, Sharon Kimble wrote:
>>
>>> How can I get sound continuously with mpd and mpv without the card being
>>> seemingly dropped please?
>>
>> Are you using pulseaudio and have you installed pavucontrol?? Run alsamixer, make sure your
>> soundcard is not muted and the sound level up to 80% or better. What are you using to provide
>> speakers? Switched on/plugged in?? Desktop or Laptop? Speakers external (powered or not powered) or
>> internal? Unless you have some speaker-out/audio-out issue, where it doesn't sense/switch correctly
>> when you have only one audio jack. you >should< have audio. If we can't get it fixed, get a USB
>> sound device. But, let's try to fix first. Ric
>
> Thanks for replying Ric.
>
> And thank you, thank you, thank you! I hadn't got 'pavucontrol'
> installed, soon remedied, but I've now got sound back through it!
>
> I'd always thought that I was using ALSA, but apparently not. But
> 'pavucontrol' is the missing link in my sound setup.
>
> But to answer your general questions, *all* sound goes through my
> headphones, and its a desktop machine, even though the machine is
> actually sitting under my desk :). And the only speakers are my
> headphones.

Great! The deal is that pulse sits on top of alsa. If alsa not workie, 
pulse is dead in the water. So, as a general rule, use alsamixer first 
to see if something is muted. If so, unmute it and set sound to about 80%.
THEN use pavucontrol to finish your sound setup. That was all you 
needed. What blows my mind is why this happens so frequently and 
pavucontrol is not a "depend" on pulseaudio. Your problem occurs 
frequently without pavucontrol being automagically installed to use. 
Glad to be of assistance! Ric


-- 
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html

[toc] | [prev] | [next] | [standalone]

#179830

On 05/04/17 16:02, Ric Moore wrote:
> What blows my mind is why this happens so frequently and
> pavucontrol is not a "depend" on pulseaudio. Your problem occurs
> frequently without pavucontrol being automagically installed to use.
> Glad to be of assistance! Ric

pulseaudio currently Suggests: pavucontrol.

One could reasonably argue that pulseaudio ought to Recommends: 
pavucontrol, since pavucontrol makes pulseaudio much more convenient to 
use for desktop users.

One cannot, however, argue within the bounds of Debian policy that 
pulseaudio should Depends: pavucontrol, because pulseaudio as built in 
Debian *can* be run without it.

[toc] | [prev] | [next] | [standalone]

#179848

On 06/04/17 07:45, Ric Moore wrote privately to me with a question about 
how my previous remarks made sense.

Here's my public answer.

First, the dependency bill could be considerably more than 111kB, 
because while pavucontrol is itself only 111kB, it also requires the 
Pango font handling library, the Cairo drawing library, the GTK+ 
windowing library, the GLib utility library, the Canberra event sounds 
library, and the ATK accessibility interface library, none of which are 
dependencies of pulseaudio.

The average GUI user wouldn't be bothered by that, since they've 
probably got all of those libraries dragged in by application software, 
but not all use cases for pulseaudio require a GUI in the first place (I 
might be running it on my headless home media server), and some GUI 
users treat their GUI as just a way to have lots of xterms on screen at 
once.

Second, pulseaudio Depends: pulseaudio-utils, meaning that any Debian 
system with pulseaudio installed will have pacmd (an interactive 
terminal-oriented program for submitting commands to a pulseaudio 
server) and pactl (a non-interactive program for submitting commands to 
a pulseaudio server) available. These are inconvenient for your 
particular use case, but they are sufficient to make pulseaudio functional.

Thus, suggesting that "pulseaudio Suggests: pavucontrol" should become 
"pulseaudio Recommends: pavucontrol" would be entirely reasonable, since 
a very common set of pulseaudio use cases are vastly more convenient 
with pavucontrol installed, but suggesting that it should become 
"pulseaudio Depends: pavucontrol" would not.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web