--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: linux-image-2.6.30-1-amd64: media players sometimes fail to open audio device
- From: Michal Suchanek <hramrach@centrum.cz>
- Date: Mon, 17 Aug 2009 23:46:48 +0200
- Message-id: <20090817214648.22238.9670.reportbug@heretic.burning-in-hell>
Package: linux-image-2.6.30-1-amd64
Version: 2.6.30-3.local
Severity: normal
Media players sometimes fail to open the audio device saying that the
device is busy.
Since re-running the player (or skipping to the next item in playlist)
resolves the problem I don't think this is really the case.
I am running a rebuild of 2.6.30-3 because I needed the vmlinux image.
-- System Information:
Debian Release: 5.0.2
APT prefers stable
APT policy: (900, 'stable'), (500, 'testing'), (300, 'unstable'), (290, 'stable-i386'), (280, 'testing-i386'), (270, 'unstable-i386'), (1, 'experimental-i386'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.30-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages linux-image-2.6.30-1-amd64 depends on:
ii coreutils 6.10-6 The GNU core utilities
ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy
ii initramfs-tools [linux-initra 0.92o tools for generating an initramfs
linux-image-2.6.30-1-amd64 recommends no packages.
Versions of packages linux-image-2.6.30-1-amd64 suggests:
pn fdutils <none> (no description available)
ii grub-pc [grub] 1.96+20080724-16 GRand Unified Bootloader, version
pn ksymoops <none> (no description available)
pn linux-doc-2.6.30-1-amd6 <none> (no description available)
-- debconf information excluded
--- End Message ---
--- Begin Message ---
- To: 542116-done@bugs.debian.org
- Cc: Ben Hutchings <ben@decadent.org.uk>
- Subject: Re: Bug#542116: linux-image-2.6.30-1-amd64: media players sometimes fail to open audio device
- From: maximilian attems <max@stro.at>
- Date: Sat, 13 Feb 2010 12:37:08 +0100
- Message-id: <20100213113708.GZ2821@stro.at>
- In-reply-to: <a5d587fb0909072325g13a50a14sd7ad73b1539f7f8d@mail.gmail.com>
- References: <20090817214648.22238.9670.reportbug@heretic.burning-in-hell> <1250552222.16001.16.camel@localhost> <a5d587fb0908172333yf804016w2c966b8603d8db5e@mail.gmail.com> <1251037430.16001.238.camel@localhost> <a5d587fb0908240123m6a3d11faoc17f1daf761a7eda@mail.gmail.com> <1252377903.5607.113.camel@localhost> <a5d587fb0909072325g13a50a14sd7ad73b1539f7f8d@mail.gmail.com>
On Tue, 08 Sep 2009, Michal Suchanek wrote:
>
> I don't think there's any message. It does not happen always, only
> once in ~10 attempts to reopen the device
> I will try to reproduce this and see if there is anything in the recent log.
closing as no follow up since, assumed fixed in newer 2.6.32 images.
thanks for your report.
--- End Message ---