Description of problem: flighgear has numerous error messages and gets stuck looping when opening a file until maximum number of open file limit is reached. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. clean beta3 install + updates, reboot, urpmi flightgear. 2. click up a terminal 3. export FG_ROOT=/usr/share/games/flightgear 4. exportFG_HOME=/usr/share/games/flightgear 5. exportFG_SCENERY=/usr/share/games/flightgear/Scenery 6. fgfs --aircraft=C172p I have added myself to games, vidio and audio groups.
Created attachment 2064 [details] snippet of errors
Summary: 2_b3: flighgear has numerous error messages and loops opening a file => 2_b3: flightgear has numerous error messages and loops opening a file
Assignee: bugsquad => lists.jjorge
I can't reproduce here : it starts nicely, after eating 1500MB of RAM. - why do you export FG* ? - do you have enough memory? Today, flightgear needs at least 2GB, and of course good GPU.
Status: NEW => UNCONFIRMEDEver confirmed: 1 => 0
(In reply to comment #2) > I can't reproduce here : it starts nicely, after eating 1500MB of RAM. > - why do you export FG* ? Silly me, I read http://mapserver.flightgear.org/getstart/ Getting rid of the exports cleaned up the looping errors. > - do you have enough memory? I think so. $ free -m total used free shared buffers cached Mem: 3706 813 2892 0 45 312 -/+ buffers/cache: 456 3249 Swap: 3812 0 3812 It is something in my user account. I have deleted .fgfs and .fltk sub-directories, ran fgrun again and I can not get it to work correctly using --aircraft=CitationX Running in another user account does not show the same problems. My account attempts to show hud and cannot see the controls. Other account shows controls and no hud. In either account, fgrun does not show all the aircraft found in /usr/share/games/flightgear/Aircraft I'll mark this resolved and open a new bug when I can localize the problem.
Status: UNCONFIRMED => RESOLVEDResolution: (none) => FIXED