On Mon, Feb 17, 2014 at 09:02:56AM +0100, John Paul Adrian Glaubitz wrote:
> I don't know whether this is a good idea. What if I want to listen to
> something over my headphones which I don't others want to hear and
> I know about this "feature". I expect the sound to be over headphones
> only, yet
On Thu, Feb 06, 2014 at 11:59:11AM +, Ian Jackson wrote:
> Before you go too far down this path, I'd like to suggest that you do
> something which makes it possible to provide init system configuration
> for other than sysvinit, at the same time. And that you use an
> arrangement which uses a
Hi,
Ben Hutchings:
> So maybe the necessary change would be:
> - move the pulseaudio ALSA plugins and this config file into a new
> binary package
> - rename the config file so it's not just an example
> - make pulseaudio recommend that binary package
>
… except that when somebody does deinstal
On Mon, 2014-02-17 at 10:14 -0300, Niv Sardi wrote:
> actually, there is an on-going effort to port libav's features and
> bugfixes into the ffmpeg project.
Good to hear. So the remaining thing is to convince the libav folks to
contribute to ffmpeg again and change the ffmpeg community in ways th
❦ 18 février 2014 00:09 CET, Andrew Shadura :
>> > That's not true; Bluetooth headphones work flawlessly with plain
>> > ALSA (as I noted in my previous mail which somehow didn't reach the
>> > list).
>
>> Sure, you need to put the MAC address of your headset in your
>> ~/.asoundrc. That's prett
Hello,
On Mon, 17 Feb 2014 22:51:20 +0100
Vincent Bernat wrote:
> >> I do. You didn't get mine, which was that if you have a choice of
> >> (a) get PA working by at least filing a bug, or (b) get audio
> >> working by uninstalling pulseaudio, then me presenting you with a
> >> nice shiny set of
> The primary (and AFAIR only) cause of no sound with PulseAudio that I
> have encountered is that it doesnt know whether you want to hear sound
> over the HDMI output or over the jack. Both appear to the system as two
> different devices. So PA just selects one (I havent investigated how it
>
❦ 17 février 2014 15:50 CET, Andrew Shadura :
>> I do. You didn't get mine, which was that if you have a choice of
>> (a) get PA working by at least filing a bug, or (b) get audio working by
>> uninstalling pulseaudio, then me presenting you with a nice shiny set of
>> Bluetooth headphones will
On Mon, Feb 17, 2014 at 08:57:53AM +0100, John Paul Adrian Glaubitz wrote:
> On 02/17/2014 08:37 AM, Chow Loong Jin wrote:
> > It might just be that DDs/"computer experts" just have more customized
> > setups
> > that break in interesting ways when effort isn't spent porting the
> > configuration
Package: wnpp
Severity: wishlist
Owner: Sergio Schvezov
* Package name: golang-go-dbus
Version : 1~bzr20140217-1
Upstream Author : James Henstridge
* URL : https://launchpad.net/go-dbus
* License : MIT
Programming Lang: Go
Description : Go interface fo
]] Petter Reinholdtsen
> [Gergely Nagy]
> > No, it would be a terrible idea: First, to reliably support all of the
> > init systems, you'd have to target the dumbest one, and either not
> > support the features of the others, or emulate them to some extent
> > within generated code.
> >
> > Not
Control: reassign -1 wnpp
On Lu, 17 feb 14, 17:22:44, Jonathan Klee wrote:
> Package: ngp
> Severity: wishlist
>
> * Package name: ngp
> Version : 0.1
> Upstream Author : Jonathan Klee
> * URL : https://github.com/jonathanklee/ngp
> * License : GPL
> * Descript
On Mon, 2014-02-17 at 18:15 +0100, Jean-Christophe Dubacq wrote:
> Le 2014-02-17 16:00, Thomas Goirand a écrit :
> > On 02/17/2014 04:02 PM, John Paul Adrian Glaubitz wrote:
> >> Well. You can't blame PulseAudio if you have an .asoundrc in your
> >> home
> >> directory which configures your sound
[ pruning the recipient list a lot ]
On Sun, Feb 16, 2014 at 03:21:15PM +0200, Aigars Mahinovs wrote:
>
>I personally dislike systemd on a few technical and few social
>grounds, but I respect the decision of Debian TC and will do what I
>can to make systemd in Debian be the bast it can be and make
package: pulseaudio
severity: wishlist
x-debbugs-cc: debian-devel@lists.debian.org
Hi,
On Montag, 17. Februar 2014, Ben Hutchings wrote:
> On Mon, 2014-02-17 at 18:05 +0100, John Paul Adrian Glaubitz wrote:
> > On 02/17/2014 05:25 PM, Thomas Goirand wrote:
> > > On 02/17/2014 11:03 PM, John Paul
On Mon, 2014-02-17 at 18:05 +0100, John Paul Adrian Glaubitz wrote:
> On 02/17/2014 05:25 PM, Thomas Goirand wrote:
> > On 02/17/2014 11:03 PM, John Paul Adrian Glaubitz wrote:
> >> I don't see how I am rewriting things in a wrong way. Do you want to
> >> argue about the exact meaning of "broken" n
Le 2014-02-17 16:00, Thomas Goirand a écrit :
On 02/17/2014 04:02 PM, John Paul Adrian Glaubitz wrote:
Well. You can't blame PulseAudio if you have an .asoundrc in your
home
directory which configures your sound card incorrectly.
Oh !!!
Now I do remember why my pulseaudio system works. It's
On 02/17/2014 05:25 PM, Thomas Goirand wrote:
> On 02/17/2014 11:03 PM, John Paul Adrian Glaubitz wrote:
>> I don't see how I am rewriting things in a wrong way. Do you want to
>> argue about the exact meaning of "broken" now?
>
> Indeed, words are important. For me, when I read "broken" it means
Hi,
Gergely Nagy:
> > Oh except that some people didn't, which causes problems for the systemd
> > transition -- because init skript that are not skeleton-based don't know
> > how to redirect itself to systemd …
>
> Err, no. I have plenty of sysvinit scripts that work just fine with
> systemd, an
On 02/17/2014 11:03 PM, John Paul Adrian Glaubitz wrote:
> I don't see how I am rewriting things in a wrong way. Do you want to
> argue about the exact meaning of "broken" now?
Indeed, words are important. For me, when I read "broken" it means bugs
upstream, and I'm convince the problem is configu
Matthias Urlichs writes:
> Oh except that some people didn't, which causes problems for the systemd
> transition -- because init skript that are not skeleton-based don't know
> how to redirect itself to systemd …
Err, no. I have plenty of sysvinit scripts that work just fine with
systemd, and ar
On Mon, Feb 17, 2014 at 11:00:38PM +0800, Thomas Goirand wrote:
> On 02/17/2014 04:02 PM, John Paul Adrian Glaubitz wrote:
> > Well. You can't blame PulseAudio if you have an .asoundrc in your home
> > directory which configures your sound card incorrectly.
>
> Oh !!!
>
> Now I do remember why my
Hello,
On 17 February 2014 15:47, Matthias Urlichs wrote:
>> > Tried to use one of these with ALSA lately?
>> Man, don't you get the point?
> I do. You didn't get mine, which was that if you have a choice of
> (a) get PA working by at least filing a bug, or (b) get audio working by
> uninstalli
On 02/17/2014 04:02 PM, John Paul Adrian Glaubitz wrote:
> Well. You can't blame PulseAudio if you have an .asoundrc in your home
> directory which configures your sound card incorrectly.
Oh !!!
Now I do remember why my pulseaudio system works. It's because I
followed to the letter this howto:
ht
On 02/17/2014 03:47 PM, Thomas Goirand wrote:
> Your tendency to rewrite things that I write in a wrong way is annoying.
You wrote:
=
However, the fact that multiple DDs, which I do consider all as computer
experts, failed t
On 2014-02-17 14:55, Bjørn Mork wrote:
> John Paul Adrian Glaubitz writes:
[...]
>> If you want me to help you with your problem, you need to provide
>> something I can work on. Just claiming it doesn't work isn't helping
>> in this situation, I don't have a crystal ball I can consult in this
>> c
On 02/17/2014 03:57 PM, John Paul Adrian Glaubitz wrote:
> Exactly what I have been thinking all the time. And I find the argument
> "all DDs are computer experts, so if they can't get it working it
> must be broken" a particularly bad one.
No, that's not what I wrote. I wrote that it's too compli
Hi,
Norbert Preining:
> > Tried to use one of these with ALSA lately?
>
> Man, don't you get the point?
>
I do. You didn't get mine, which was that if you have a choice of
(a) get PA working by at least filing a bug, or (b) get audio working by
uninstalling pulseaudio, then me presenting you wi
Hi,
Gergely Nagy:
> If you want to properly support multiple init systems, write the init
> scripts / service files / etc for each of them.
The problem is that we all did that once already, and look where *that*
effort ended up: For sysv-rc, 1000 people copied (old versions of)
/etc/init.d/skelet
On Mon, Feb 17, 2014 at 13:18:11 +0100, John Paul Adrian Glaubitz wrote:
> On 02/17/2014 12:50 PM, Ansgar Burchardt wrote:
> > And ia64 is now gone from unstable and experimental since last Saturday.
>
> And isn't it going to become a port like all the other dropped
> architectures?
>
Not all dr
On Mo, 17 Feb 2014, Matthias Urlichs wrote:
> OK, I'll give every one of these people a Bluetooth headset instead.
> (No that does not mean I'll actually pay for them …)
>
> Tried to use one of these with ALSA lately?
Man, don't you get the point?
Yes, everyone here agrees that PA is in principl
[Gergely Nagy]
> No, it would be a terrible idea: First, to reliably support all of the
> init systems, you'd have to target the dumbest one, and either not
> support the features of the others, or emulate them to some extent
> within generated code.
>
> Not supporting features of modern init sys
Hi,
Bjørn Mork:
> The goal of most users will be "have sound", not "install pulseaudio".
Most users will have PA installed anyway, so the second "goal" is already
met. :-P
> A package which appear to be non-functional at install time is not
> likely to receive any bug reports at all. Feel free
John Paul Adrian Glaubitz writes:
> On 02/17/2014 01:37 PM, Norbert Preining wrote:
>> Why can you not simply say something like: "Well yes, there seem
>> to be some problems and we will try to fix them if we can get hold
>> of enough input. You DDs should be able to provide decent information
>>
+++ John Paul Adrian Glaubitz [2014-02-17 14:19 +0100]:
> On 02/17/2014 02:03 PM, Wookey wrote:
> > No it wasn't. He explicitly said 'I'll spare you my rants', and _didn't_
> > put in a big rant about how PA is a PITA. Yes it had some 'tone' due to
> > be filed just after being very annoyed by some
On Fri, Feb 14 2014, p...@debian.org wrote:
> On Sat, Feb 15, 2014 at 5:49 AM, Adrian Bunk wrote:
>
>> But how to make the decision whether libav or FFmpeg is better for jessie?
>
> Seems like getting the two upstreams to collaborate and merge the two
> forks is the way to go.
actually, there is
+++ Josselin Mouette [2014-02-17 11:06 +0100]:
> Le samedi 15 février 2014 à 22:12 +0100, Salvo Tomaselli a écrit :
> > Well I am now biased against pulseaudio. But let's look at the facts: it
> > comes
> > by default, in the last 3 desktop machines that I've installed, it
> > prevented
> > an
On 02/17/2014 02:03 PM, Wookey wrote:
> No it wasn't. He explicitly said 'I'll spare you my rants', and _didn't_
> put in a big rant about how PA is a PITA. Yes it had some 'tone' due to
> be filed just after being very annoyed by some problem. Sometimes that
> happens. As a maintiner you have to l
"Francesco P. Lovergine" writes:
> On Thu, Feb 06, 2014 at 11:59:11AM +, Ian Jackson wrote:
>>
>> I think the best approach would probably be to automate the generation
>> of init scripts in debhelper.
>>
>
> Seconded. Using an auto-generated skeleton starting from a simple template
> woul
+++ John Paul Adrian Glaubitz [2014-02-16 14:55 +0100]:
> On 02/16/2014 01:05 PM, Alessio Treglia wrote:
> > On Sun, Feb 16, 2014 at 12:50 AM, John Paul Adrian Glaubitz
> > wrote:
> >> Well, I'm sorry but I would have probably reacted the same. You were not
> >> reporting a bug, you were just rant
On 02/17/2014 01:37 PM, Norbert Preining wrote:
> Why can you not simply say something like: "Well yes, there seem
> to be some problems and we will try to fix them if we can get hold
> of enough input. You DDs should be able to provide decent information
> to help track the problems down."
Then w
On Thu, Feb 06, 2014 at 11:59:11AM +, Ian Jackson wrote:
>
> I think the best approach would probably be to automate the generation
> of init scripts in debhelper.
>
Seconded. Using an auto-generated skeleton starting from a simple template
would be more than enough to solve the main proble
On Mo, 17 Feb 2014, Michael Meskes wrote:
> I just fell into #690536 and found that it has been acknowledged and even a
> patch has been proposed some 18 months ago, but no upload has been made. Is
> anyone still working on it? Besides, this teams calls itself "Debian/Ubuntu
> ..." but the buntu pa
Hi Adrian,
On Mo, 17 Feb 2014, John Paul Adrian Glaubitz wrote:
> Exactly what I have been thinking all the time. And I find the argument
> "all DDs are computer experts, so if they can't get it working it
> must be broken" a particularly bad one.
Well, the amount of DDs mentioning that on their
I just fell into #690536 and found that it has been acknowledged and even a
patch has been proposed some 18 months ago, but no upload has been made. Is
anyone still working on it? Besides, this teams calls itself "Debian/Ubuntu
..." but the buntu packages were updated. So what's going on?
Michael
On 02/17/2014 12:50 PM, Ansgar Burchardt wrote:
> And ia64 is now gone from unstable and experimental since last Saturday.
And isn't it going to become a port like all the other dropped
architectures?
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.org
`.
Hi,
On 02/03/2014 10:13, Ansgar Burchardt wrote:
> Following the removal of ia64 from jessie, we intend to complete the
> process by removing it from unstable and experimental next weekend, that
> is 15th/16th Februrary 2014. If anyone has any objection to this,
> please let us know as soon as po
> Hi,
>
> Wouter Verhelst:
>> discussion. No, we should not depend on it for Debian; but we should
>> provide the interface for system administrators who wish to use it,
>> because it is not Debian's place to tell them that they cannot use that
>> interface.
>>
> It's not our place to tell people t
Le samedi 15 février 2014 à 22:12 +0100, Salvo Tomaselli a écrit :
> Well I am now biased against pulseaudio. But let's look at the facts: it
> comes
> by default, in the last 3 desktop machines that I've installed, it prevented
> any audio to be heard.
> Am I so unreasonable to think that sinc
Hi,
On Mon, Feb 17, 2014 at 09:02:56AM +0100, John Paul Adrian Glaubitz wrote:
>
> Well. You can't blame PulseAudio if you have an .asoundrc in your home
> directory which configures your sound card incorrectly.
I just want to confirm that I have no file ~/.asoundrc in my home dir
and I never ha
On 17 Feb 2014 19:33, "darkestkhan" wrote:
> It is also noteworthy that when most of average users getting this kind
> of problems would go back to Windows (hey, at least audio works there)
In my case, was the reverse. When Windows audio didn't work (incorrectly
says nothing connected to the port
[Petter Reinholdtsen]
> Have you consider the /lib/init/init-d-script approach now available
> in unstable when considering how hard it is to maintain init.d
> scripts? It allow package maintainers to only store the package
> specific parts in their init.d scripts, and offload the complete
> imple
On Mon, Feb 17, 2014 at 04:26:31PM +0800, Chow Loong Jin wrote:
On Mon, Feb 17, 2014 at 09:18:51AM +0100, Matthias Urlichs wrote:
> As an example, most users who use systemd probably still restart
> services using "/etc/init.d/ restart", just because it works.
It's simply less to type if you don
Hi,
Chow Loong Jin:
> > It's simply less to type if you don't otherwise like bash-autocomplete. :-P
>
> Really? I've been using "service restart" which autocompletes well
> too, and is even less to type. Works well with systemd, upstart, and sysvinit.
>
I intentionally disable bash autocomplete
On Mon, Feb 17, 2014 at 7:57 AM, John Paul Adrian Glaubitz
wrote:
> On 02/17/2014 08:37 AM, Chow Loong Jin wrote:
>> It might just be that DDs/"computer experts" just have more customized setups
>> that break in interesting ways when effort isn't spent porting the
>> configuration
>> changes to a
On Mon, Feb 17, 2014 at 09:18:51AM +0100, Matthias Urlichs wrote:
> Hi,
>
> John Paul Adrian Glaubitz:
> > As an example, most users who use systemd probably still restart
> > services using "/etc/init.d/ restart", just because it works.
> >
> It's simply less to type if you don't otherwise like
Hi,
John Paul Adrian Glaubitz:
> > Use all of them. Most of them most likely aren't connected to anything,
> > so sending a signal there is harmless.
>
> I don't know whether this is a good idea. What if I want to listen to
> something over my headphones which I don't others want to hear and
> I
Hi,
John Paul Adrian Glaubitz:
> As an example, most users who use systemd probably still restart
> services using "/etc/init.d/ restart", just because it works.
>
It's simply less to type if you don't otherwise like bash-autocomplete. :-P
> It's also noteworthy that complains about PulseAudio u
]] The Wanderer
> (And now I wait for someone to point out an obvious specialized format
> and/or tool that everyone uses that I've overlooked...)
.deb files? :-)
--
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are
--
To UNSUBSCRIBE, email to debian-devel-req
On 02/17/2014 08:44 AM, Tollef Fog Heen wrote:
> ]] John Paul Adrian Glaubitz
>
>> So, if your computer has several sounds cards - which is the case when
>> you have both a sound card and HDMI audio - how is PulseAudio supposed
>> to know which sound card to use? This is in no way different to pl
On 17 Feb 2014 06:54, "Andreas Tille" wrote:
> I have no idea whether this remark is helpful but this thread inspired
> me to give pulseaudio another chance on one of my boxes (I had
> deinstalled previously on all boxes where sound stoped working at some
> point in time randomly). Despite I gave
61 matches
Mail list logo
