[gentoo-user] another strange alsa problem

2006-12-07 Thread Matthias Langer
I'm using alsa for years now and it has always been fine; especially it
has always been possible without any problems to have multiple apps
running that access the sound card. For example i could start audacious
to play some music and to totem and watch a movie _with_ sound; or play
some music and start a game etc.  Yesterday, i noticed, that this is
no longer possible: For example, if i try to play a mp3 in gmplayer
while running audacious i get:

alsa-init: using device default
alsa-lib: pcm_dmix.c:914:(snd_pcm_dmix_open) unable to open slave
alsa-init: playback open error: Invalid argument
Could not open/initialize audio device - no sound.

Now the funny thing is, that the same works as root; so i guess that
some permissions are not set correctly (note that my everyday user is in
the audio group) and perhaps, but this is only one possible explanation,
this is because i've upgraded to sys-fs/udev-103 recently ...

any ideas ?

btw, this is my sound-card: Creative Labs SB Live! EMU10k1

Portage 2.1.1-r2 (default-linux/x86/2006.1/desktop, gcc-4.1.1,
glibc-2.4-r4, 2.6.18-gentoo-r3 i686)
=
System uname: 2.6.18-gentoo-r3 i686 AMD Athlon(tm) XP 2400+
Gentoo Base System version 1.12.6
Last Sync: Thu, 07 Dec 2006 01:20:01 +
distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632)
[disabled]
app-admin/eselect-compiler: [Not Present]
dev-java/java-config: 1.3.7, 2.0.30
dev-lang/python: 2.4.3-r4
dev-python/pycrypto: 2.0.1-r5
dev-util/ccache: [Not Present]
dev-util/confcache:  [Not Present]
sys-apps/sandbox:1.2.17
sys-devel/autoconf:  2.13, 2.60
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2
sys-devel/binutils:  2.16.1-r3
sys-devel/gcc-config: 1.3.13-r4
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.17-r2
ACCEPT_KEYWORDS=x86
AUTOCLEAN=yes
CBUILD=i686-pc-linux-gnu
CFLAGS=-march=athlon-xp -O2 -pipe
CHOST=i686-pc-linux-gnu
CONFIG_PROTECT=/etc /usr/kde/3.5/env /usr/kde/3.5/share/config 
/usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config
CONFIG_PROTECT_MASK=/etc/env.d /etc/env.d/java/ /etc/gconf 
/etc/java-config/vms/ /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c
CXXFLAGS=-march=athlon-xp -O2 -pipe
DISTDIR=/usr/portage/distfiles
FEATURES=autoconfig collision-protect distlocks metadata-transfer
sandbox sfperms strict
GENTOO_MIRRORS=ftp://ftp.sh.cvut.cz/MIRRORS/gentoo/gentoo 
LANG=en_US.utf8
LC_ALL=en_US.utf8
LINGUAS=en de
MAKEOPTS=-j2
PKGDIR=/usr/portage/packages
PORTAGE_RSYNC_OPTS=--recursive --links --safe-links --perms --times
--compress --force --whole-file --delete --delete-after --stats
--timeout=180 --exclude='/distfiles' --exclude='/local'
--exclude='/packages'
PORTAGE_TMPDIR=/var/tmp
PORTDIR=/usr/portage
PORTDIR_OVERLAY=/usr/local/portage
SYNC=rsync://192.168.0.1/gentoo-portage
USE=x86 3dnow 3dnowext X a52 aac acpi aiglx alsa audiofile avahi beagle
berkdb bitmap-fonts bzip2 cairo cdr cli cracklib crypt css cups dbus
dlloader dri dvd dvdr dvdread eds elibc_glibc emboss encode evo exif fam
fbcon ffmpeg firefox flac fortran gdbm gif ginac gmp gnome gphoto2 gpm
gstreamer gtk gtk2 hal iconv icq input_devices_keyboard
input_devices_mouse ipv6 isdnlog java javascript jpeg jpeg2k
kernel_linux lcms ldap libg++ linguas_de linguas_en mad mikmod mime mmx
mmxext mono mozsvg mp3 mpeg msn nautilus ncurses nfs nls nptl nptlonly
nsplugin nvidia offensive ogg oggvorbis opengl pam pcre pdf perl
plotutils png posix ppds pppd python qt3 qt4 quicktime readline real
reflection ruby sdl session sockets spell spl sqlite3 sse ssl subtitles
svg tcpd tetex theora threads tiff truetype truetype-fonts type1-fonts
udev unicode usb userland_GNU vcd video_cards_nvidia vorbis win32codecs
wma xine xml xorg xv xvid zlib
Unset:  CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LDFLAGS,
PORTAGE_RSYNC_EXTRA_OPTS

-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] another strange alsa problem [SOLVED]

2006-12-07 Thread Matthias Langer
On Thu, 2006-12-07 at 13:18 +0100, Matthias Langer wrote:
 I'm using alsa for years now and it has always been fine; especially it
 has always been possible without any problems to have multiple apps
 running that access the sound card. For example i could start audacious
 to play some music and to totem and watch a movie _with_ sound; or play
 some music and start a game etc.  Yesterday, i noticed, that this is
 no longer possible: For example, if i try to play a mp3 in gmplayer
 while running audacious i get:
 
 alsa-init: using device default
 alsa-lib: pcm_dmix.c:914:(snd_pcm_dmix_open) unable to open slave
 alsa-init: playback open error: Invalid argument
 Could not open/initialize audio device - no sound.
 

well, it finally turned out that this problems where related to an
~/.asoundrc that has been created by some strange program. removing that
file made alsa happy again ...

-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] another strange alsa problem [SOLVED]

2006-12-07 Thread Matthias Langer
On Thu, 2006-12-07 at 11:24 -0700, Richard Fish wrote:
 On 12/7/06, Matthias Langer [EMAIL PROTECTED] wrote:
  alsa-init: using device default
  alsa-lib: pcm_dmix.c:914:(snd_pcm_dmix_open) unable to open slave
  alsa-init: playback open error: Invalid argument
  Could not open/initialize audio device - no sound.
 
 This indicates a configuration error.  The default device is
 apparently the dmix plugin, but it is misconfigured to open a slave
 device that doesn't exist.
 
  Now the funny thing is, that the same works as root; so i guess that
  some permissions are not set correctly
 
 Maybe root doesn't have a ~/.asoundrc, and your regular user account does?
 
 -Richard

thanks for your answer that would have been very, very helpful if i
hadn't already fixed this problem [1] ;-)

Matthias

[1]: http://news.gmane.org/gmane.linux.gentoo.user/cutoff=175354

-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] another strange alsa problem [SOLVED]

2006-12-07 Thread Richard Fish

On 12/7/06, Matthias Langer [EMAIL PROTECTED] wrote:

On Thu, 2006-12-07 at 11:24 -0700, Richard Fish wrote:
thanks for your answer that would have been very, very helpful if i
hadn't already fixed this problem [1] ;-)


Yeah I saw that, but only after I responded.  I blame both gmail, for
treating messages with different subjects as different threads (so
adding SOLVED caused a different thread to appear in my inbox, that
I didn't read until later), and myself, for using gmail. :-P

-Richard
--
gentoo-user@gentoo.org mailing list