On Tue, May 20, 2008 at 07:27:01PM +0200, Josip Rodin wrote: > reopen 439072 > thanks > > On Tue, May 20, 2008 at 07:08:59PM +0200, Josip Rodin wrote: > > On Tue, May 20, 2008 at 04:54:06PM +0000, Debian Bug Tracking System wrote: > > > closing as according to upstream not a driver issue. > > > marked as resolved thus closing. > > > > I would appreciate it if you could first answer the question which I asked > > in August last year (which was the reason I didn't close the bug myself): > > > > > Can someone tell me the proper steps to test the default value to see if > > > the bug was really just some local mishap? > > > > It's a bit annoying to see people ignore you for nine months, > > and then close the bug report rather than answering it. > > I almost forgot - that's disregarding the simple fact that even if > the driver made no mistake with this, this 2ch vs 4ch issue is not documented > anywhere, neither in kernel (linux-2.6/Documentation/sound/alsa/?) nor in > userland (alsamixer(1), arecord(1), ...?), so if anyone else sees this > behaviour, whether due to one's own change or a possible bad default, > there is no recourse. > > Closing bugs just like that may well be acceptable elsewhere, but I thought > we had a bit higher standards in Debian. :|
great. firstly this is *not* a kernel bug. secondly this i not the way you'll get alsa userland support thirdly your message did mention that you even *tried* current 2.6.25 candidate to closure unless you provide info that is is a kernel bug. thanks -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
