James, for whatever it's worth, I have a machine here that I upgraded from Fedora 10 -> 11 and then from Fedora 11 to Fedora 12 and sound was a nightmare and never worked right or at all with FlightGear after those upgrades. Then I finally blew everything away and installed Fedora 12 from scratch. It turns out (my best interpretation anyway) that the earlier version of Fedora used some random snapshot of openal. At some point Fedora switched over to openal-soft, but the upgrade never installed openal-soft because the package name is different and at least in this case, it just did it's best to find a newer version of the existing packages. So I had an old crappy openal on my system which didn't seem to work right or at all with FlightGear and Fedora 12. This got sorted out properly with a fresh install. Now going back I could have probably just removed the old openal, installed openal-soft and probably been happy, but it's too late for me to try that now.
Regards, Curt. On Sat, Jan 9, 2010 at 3:31 AM, James Sleeman wrote: > Is there a reason that --disable-sound doesn't totally disable sound? > Is there a way to totally disable sound? --help --verbose doesn't give > any further clue that I noticed. > > I am still having major problems getting FG to work with pulseaudio (and > I don't want to (nor really can) kill off pulseaudio). > > In summary: > Sometimes everything is perfect with the c172, sometimes it hangs > before the splash screen goes away, there is no rhyme nor reason, I > suspect there is a race condition of some description. > > I don't think I've successfully got any other aircraft to work, they > always hang before the splash goes away, again probably a race condition > I suspect which other aircraft trigger more readily than the 172. > > Even with --disable-sound, we get the same hang, the backtrace of > which follows, so I can't even fly soundless :-( > > Talk about frustrating, havn't been able to FG properly in ages, > withdrawl symptoms! > > Here is a --disable-sound backtrace which shoes that it's still trying > to use openal (and thus pulseaudio) even with no sound. > > Starting program: /usr/local/builds/fg-auto/install/fgfs/bin/fgfs > --fg-root=/usr/local/builds/fg-auto/install/fgfs/bin/../data/ > --aircraft=dc2 --disable-sound > [Thread debugging using libthread_db enabled] > [New Thread 0x7fffed970910 (LWP 5534)] > ^C ### I broke in here after it has hung ### > Program received signal SIGINT, Interrupt. > pthread_cond_wait@@GLIBC_2.3.2 () > at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:261 > 261 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S: No > such file or directory. > in ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S > Current language: auto > The current source language is "auto; currently asm". > (gdb) bt > #0 pthread_cond_wait@@GLIBC_2.3.2 () > at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:261 > #1 0x00007ffff107642b in pa_threaded_mainloop_wait () > from /usr/lib/libpulse.so.0 > #2 0x00007ffff5af12a9 in pulse_open (device=0xaf45d00, > device_name=0x7ffff5af6cf0 "PulseAudio Software") > at > /usr/local/builds/flightgear/openal-soft-1.10.622/Alc/pulseaudio.c:391 > #3 0x00007ffff5af2153 in pulse_open_playback (device=0xaf45d00, > device_name=0x7ffff5af6cf0 "PulseAudio Software") > at > /usr/local/builds/flightgear/openal-soft-1.10.622/Alc/pulseaudio.c:452 > #4 0x00007ffff5ad9200 in alcOpenDevice (deviceName=0x0) > at /usr/local/builds/flightgear/openal-soft-1.10.622/Alc/ALc.c:1587 > #5 0x00000000008e3653 in SGSoundMgr::init (this=0xe11540, > devname=<value optimized out>) at soundmgr_openal.cxx:105 > #6 0x0000000000448220 in fgInitSubsystems () at fg_init.cxx:1476 > #7 0x000000000042ccb4 in fgIdleFunction () at main.cxx:774 > #8 0x0000000000477ac2 in fgOSMainLoop () at fg_os_osgviewer.cxx:172 > #9 0x000000000042d509 in fgMainInit (argc=4, argv=0x7fffffffe7b8) > at main.cxx:920 > #10 0x000000000042b40e in main (argc=4, argv=0x7fffffffe7b8) > at bootstrap.cxx:229 > > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and > easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > -- Curtis Olson: http://baron.flightgear.org/~curt/
------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
