Totem and rhythmbox produce no sound since the gstreamer update that took place this week, where gst and several plugins got bumped. Also, when I try to open any sound-only file on totem, an error window pops up with title "An error ocurred" and text "Internal data flow error". If it's a video with an audio track, the video plays but with no sound and no error message. Totem also recognizes the audio track correctly in both cases, it just won't play it. From the command line, the error in totem is: $totem OIL: ERROR liboiltest.c 361: oil_test_check_impl(): illegal instruction in mmxCombineAddU ** Message: Error: Internal data flow error. gstbasesrc.c(2240): gst_base_src_loop (): /play/source: streaming task paused, reason not-linked (-1) In rhythmbox, the message is: $ rhythmbox OIL: ERROR liboiltest.c 361: oil_test_check_impl(): illegal instruction in mmxCombineAddU I'm not sure if the liboil message on both are relevant, even if it's the only message for rhythmbox, since I can't verify if they were there before. For totem this liboil message appears as soon as I start it, while the rest of the error messages appears only when I tell it to play the file. For rhythmbox the liboil message appears only when I tell it to play some music, but then it only appears for the first song I try. I am running an Athlon Thunderbird which does not have SSE instructions, perhaps this has to do with the liboil message... It might be relevant that the following plays the sound as expected: $gst-launch-0.10 -v filesrc location=sound.mp3 ! mad ! alsasink Hope you can help me :) &TxAnwy! Reproducible: Always
Created attachment 159195 [details] my emerge --info
A couple things : 1) drop the -O3, -O2 is the most we support 2) some glibc versions add the wrong assembly optimizations : try putting -mno-see in your CFLAGS Thanks
Well in this case it seems there is a problem with mmx optimizations. >> illegal instruction in mmxCombineAddU are you sure your processor really supports mmx ? you can check by using grep "mmx" /proc/cpuinfo.
I've committed liboil-0.3.15 (latest) to tree. Please test.
(In reply to comment #4) > I've committed liboil-0.3.15 (latest) to tree. Please test. > OK, this might fix some of the other comments we have in this bug.. But here is the real fix, to issue this bug is for. Other issues in new bug, thanks. +*gst-plugins-good-0.10.8-r1 (02 Jul 2008) + + 02 Jul 2008; Samuli Suominen <drac@gentoo.org> + +gst-plugins-good-0.10.8-r1.ebuild: + Pass --with-default-audiosink=autoaudiosink and + --with-default-visualizer=goom wrt upstream bug #532295, this fixes Gentoo + bug #230419.
And one more hint, I had to remove ~/.config/banshee* to get banshee in shape again after installing new -good-0.10.8-r1. Totem worked out of box after.
(In reply to comment #2) > 2) some glibc versions add the wrong assembly optimizations : try putting > -mno-see in your CFLAGS Just one thing about that, adding "-mno-sse" to CFLAGS is expected to break liboil compilation. Liboil is supposed to compile optimized code for several platforms and choose wich to use at runtime. Or at least that's what I learned when I filed bug #218592 , so one should not explicitly inclde -mno-sse in CFLAGS. Thanks!!
Hey!! Thanks everyone for being so helpful and responding so quickly :) So, about the present bug... Updating liboil to the new version clears the liboil related messages from both programs. However, even after updating gst-plugins-good, and after deleting any mention to 'totem' or 'Totem' in .config and .gnome2, my situation is exactly the same except for the liboil messages having vanished. :\ I will try some more things in the next hour or so, but if nothing helps I'd like to reopen this bug... Thanks again! ale ~~
Ok, so I have some news... After deleting ~/.gconf/apps/totem/ all the errors and warnings went away and I even got to see the pretty visualizations when playing audio files, but still no sound. Then I opened System -> Preferences -> Sound and noticed that the default setting for all actions was "Custom" instead of "Autodetect", and changing this returned sound playback to normal. For some reason, at least on my system, "Autodetect" was not the default. In the proccess of bugtracking I created a new account with no config files at all, and the same seemed to happen there, though I did not login on gnome, but started totem through a shell on my usual account's X session. So maybe someone should take a look on the global gconf files... Thanks everyone!! ale ~~
(In reply to comment #9) > So maybe someone should take a look on the global gconf files... More specifically, the keys: /system/gstreamer/0.10/default/musicaudiosink_description /system/gstreamer/0.10/default/audiosink_description /system/gstreamer/0.10/default/chataudiosink_description (curisouly, my system doesn't have default keys for gstreamer-0.10 in /etc/gconf, so I guess those above I see in my ~/.gconf/ were created by gnome/totem/?...)
The --default-audiosink=autoaudiosink should also be passed to the media-plugins/gst-plugins-gconf package... since we split it out of gst-p-good...
(In reply to comment #11) > The --default-audiosink=autoaudiosink should also be passed to the > media-plugins/gst-plugins-gconf package... since we split it out of > gst-p-good... > I didn't need this after updating from gst-plugins-good-0.10.6 DIRECTLY to 0.10.8-r1, maybe I didn't suffer this because I didn't installed buggy gst-plugins-good that was available in testing in the pass :-/
(In reply to comment #12) > I didn't need this after updating from gst-plugins-good-0.10.6 DIRECTLY to > 0.10.8-r1, maybe I didn't suffer this because I didn't installed buggy > gst-plugins-good that was available in testing in the pass :-/ Well, if you read the code, the only place these variables are used is in the gconf plugin.. I added gst-plugins-gconf-0.10.8-r1 with the fix
