Running Rhythmbox 0.6.1. Normally sounds great. If I run the wmbattery docapp in Windowmaker, it produces a periodic clicking noise (approximately every second or so). It is not a simple lack of resources problem, since I can complile and do other heavyduty stuff without a single stutter in rhythmbox. Also, xmms will play fine with wmbattery running. I am guessing that for some reason, when wmbattery checks the battery life, it causes a problem. This is obviously not a big deal, since I can just kill wmbattery when I want to listen to music. Reproducible: Always Steps to Reproduce: Portage 2.0.50-r1 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r9, 2.6.3-gentoo-r1) ================================================================= System uname: 2.6.3-gentoo-r1 i686 Mobile Intel(R) Pentium(R) 4 - M CPU 1.70GHz Gentoo Base System version 1.4.3.13 Autoconf: sys-devel/autoconf-2.58-r1 Automake: sys-devel/automake-1.8.2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=pentium4 -funroll-loops -fprefetch-loop-arrays -pipe" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.1/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=pentium4 -funroll-loops -fprefetch-loop-arrays -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="ftp://ftp.ussg.iu.edu/pub/linux/gentoo rsync://mirrors.tds.net/gentoo ftp://gentoo.noved.org/ rsync://gentoo.seren.com/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X alsa apm arts avi berkdb crypt cups encode esd foomaticdb gdbm gif gnome gpm gtk gtk2 guile imlib java jpeg kde libg++ libwww mad mikmod motif mozilla mpeg ncurses nls oggvorbis opengl oss pam pdflib perl png ppds python qt quicktime readline sdl slang spell ssl svga tcltk tcpd tetex truetype usb x86 xml2 xmms xv zlib"
Is this fixed in 0.6.8?
Same problem in 0.6.8. I would try 0.7.1, but it needs gstreamer 0.7.4.
can you please try rhythmbox 0.8.0
Upgraded to 0.8.0Well, no more skipping. And no more music at all. I now get this error whenever I try and play any mp3: "There is no element present to handle the stream's mime type application/x-id3." and on the command line, it prints: "GStreamer-WARNING **: inconsistent state information, fix threading please" I can't see anything obviously wrong with what I have emerged - any suggestions?
My apologies - gst-plugins-mad doesn't automatically get updated to 0.8.0, and the new version seems to be necessary to play mp3s. After upgrading that, I have sound back again. Still the same problem with wmbattery though. Upgrading to a new version of wmbattery also makes no difference.
turning this over to foser as he's requested to handle all the rb related bugs.
what backend are you using (gstreamer is default) ? Assuming you use gstreamer, what sound output are you using ? Assuming you use the default, it's probably the oss plugin. Does any music playback software using oss directly exhibit the same behaviour ? The clicking sound together with a battery check makes me think hardware related interference might be involved.
I use the gstreamer backend. I didn't specify anything special (besides USE="alsa", so I am assuming that by default sink is osssink. I don't know how to find out for sure though. I did some investigation - here are my results: 1) running: gst-launch filesrc location="07_-_colorblind_128_lame_abr.mp3" ! osssink gives the exact same problem. 2) running: gst-launch filesrc location="07_-_colorblind_128_lame_abr.mp3" ! spider ! alsasink gives RUNNING pipeline ... gst-launch-0.8: pcm_plug.c:882: snd_pcm_plug_hw_params: Assertion `err >= 0' failed. Aborted I am not sure if that is supposed to work, but I have gst-plugins-alsa installed. 3) I can run xmms with either the alsa or the oss output. By default, neither displays the problem. However, if I use the alsa output, and set "Period Time" to 1 (from the default of 50), xmms has a similar problem. No amount of messing with thse settings in the oss output seems to produce this result.
gst-launch should no try to run a 0.8 pipeline ? Did you use bmg stuff ? You need to try something that uses oss directly (eg. cat a raw sound file to the sound device), without settings.. it is likely xmms does some caching itself to prevent problems. It is unlikely that alsa is the direct problem, cause alsa wasn't working in gstreamer 0.6 . Or it must've been trough the alsa oss emulation maybe. I think it's just your hardware and without some sounddate caching the batterycheck is too interruptive to go unnoticed.
i believe the upcoming gst release contains some oss fixes that might help here. keep an eye on it.
Unfortunately, I spilled water on my laptop, so I have been unable to try anything. In another week, I will have a new computer, but I don't know whether I will be able to reproduce the bug. If you want, you can close this bug, and I will reopen it if the problem reoccurs on the new computer.
closing
