Inserted CD1, su'd to root and did "emerge ut2003" Followed the instructions (ie changing CD's) and placed cd key in twice as asked, no apperance of an error up to this time. Looked in at the KDE menu and there is a shortcut called "ut2003" (no icon for it), I tried to add an icon but it didn't want to update it in the menu (strange). I tried the shortcut but "nothing happened" (ie no splash screen, no cd activity, no error). If I jump onto the console and type "ut2003" I get the error "bash: ut2003: command not found". I cd to /opt/ut2003/ and run "./ut2003" as user (yes I'm a member of the group "games" ), the splash screen appears for a moment and then I get this error: bash-2.05b$ cd /opt/ut2003/ bash-2.05b$ ./ut2003 Can't find file for package 'WinDrv' History: Exiting due to error I have emerge umerge ut2003 plus removed /opt/ut2003 twice and reinstalled three times. It is the same every time. Reproducible: Always Steps to Reproduce: 1.pop cd in drive, mount it, "emerge ut2003", follow instructions about other CD's and CD key. 2.pop CD1 back into drive, type "cd /opt/ut2003" 3.type ./ut2003 Actual Results: Splash screen loads for a moment. bash-2.05b$ ./ut2003 Can't find file for package 'WinDrv' History: Exiting due to error Expected Results: Started the game up... Any help required from me please e-mail me ( senectus TA westnet TOD com TOD au ). I live in Western Australia so my hours are a little different to yours at a guess.. :-) There is also another person with the same issue's in the forum : http://forums.gentoo.org/viewtopic.php?t=73918 Thanks guy..
I'm looking into this issue. It appears to be a problem with the Default.ini installed with the Windows installer versus the one installed with the Linux installer.
Fixed in CVS emerge sync emerge ut2003 emerge clean
The bug is still there!! I'm using 1.5 ebuild but that message appears in my term. Yes, I'm on the games group too. *.ini problems? I don't know. Thanks.
Actually, the bug is still present because you still have an invalid UT2003.ini in your ~/.ut2003 directory. Delete the entire directory and run ut2003 again.
I just submitted a new UT2003 ebuild which solves this problem along with another. I was unable to reproduce the problem again myself, but the fix for another bug seemed to solve this one also.
