Summary: | games-rpg/nwn 1.67-r1 (and 1.68) sementation faults on startup | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Bill C. Riemers <docbill+bugzilla> |
Component: | Current packages | Assignee: | Gentoo Games <games> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | gent_bz |
Priority: | High | ||
Version: | 2006.1 | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
strace of crash in 1.67-r1
Strace of 1.68 crashing Output from "equery depgraph nwn" Suggested patch for the nwn client Suggested update to resolve the language problem suggested update to resolve the language problem |
Description
Bill C. Riemers
2006-09-23 09:09:35 UTC
Created attachment 97864 [details]
strace of crash in 1.67-r1
Created attachment 97865 [details]
Strace of 1.68 crashing
Are you sure all files that nwn needs is installed in their respective directories since there are many "no such file or directory" in those straces (In reply to comment #3) > Are you sure all files that nwn needs is installed in their respective > directories since there are many "no such file or directory" in those straces > I would expect the package dependancies would take of installing all neccessary files. An "emerge --update -deep world" finds no missing dependancies. Neither does revdep-rebuild. docbill@docbill003 ~ $ emerge --search nwn Searching... [ Results for search key : nwn ] [ Applications found : 4 ] * games-rpg/nwn Latest version available: 1.68 Latest version installed: 1.68 Size of files: 2,022,233 kB Homepage: http://nwn.bioware.com/downloads/linuxclient.html Description: Neverwinter Nights License: NWN-EULA * games-rpg/nwn-cep Latest version available: 1.52 Latest version installed: [ Not Installed ] Size of files: 246,401 kB Homepage: http://nwn.bioware.com/players/cep.html Description: The Community Expansion Pack is a high quality custom content addon for Neverwinter Nights License: as-is * games-rpg/nwn-data Latest version available: 1.29 Latest version installed: 1.29 Size of files: 1,919,252 kB Homepage: http://nwn.bioware.com/downloads/linuxclient.html Description: Neverwinter Nights Data Files License: NWN-EULA * games-server/nwn-ded [ Masked ] Latest version available: 1.67 Latest version installed: [ Not Installed ] Size of files: 325,420 kB Homepage: http://nwn.bioware.com/downloads/standaloneserver.html Description: Neverwinter Nights Dedicated server License: NWN-EULA Created attachment 97879 [details]
Output from "equery depgraph nwn"
Created attachment 97885 [details, diff]
Suggested patch for the nwn client
It seems the problem is some important steps from nwn-data are quickly scrolled past when emerging nwn. The best solution is to test if these instructions have been followed and if not prompt them again Changing the nwn script in nwclient129.tar.gz should do this...
Now that I have followed those steps the main problem I have is NWN is in French, even though my current locale is English.
Bill
So the problem is that you didn't complete the directions? As for the French thing... we haven't decided on a proper way to determine which language is default (within the ebuild, that is) and which to select. The simplest method is for you to do: mkdir -p /etc/portage echo "games-rpg/nwn-data -linguas_fr" >> /etc/portage/package.use echo "games-rpg/nwn -linguas_fr" >> /etc/portage/package.use emerge --oneshot nwn-data nwn Properly designed software should not segmentation fault under any condition. Given than NWN is a commercial product, that is obviously beyond your control. However, it is within control to wrap the excutable to protect from obvious errors. That aside it is definitely a flaw in ANY build to expect users to see the directions and follow them. Like most people when building a system, several hundred packages are merged at once. Any important message will have long since scrolled off the screen, and even if I did capture a log file, I am not likely to review the hundreds of thousands of lines of text without having a month of vacation and nothing to do. Even then, if someone does simply do "emerge nwn", the nwn-data will be automatically merged as a dependancy and the messages will have long since scrolled off the screen. There are several ways to try and communicate to the user the important instructions. A segmentation fault is not one of them. It just makes the whole system appear unstable. My solution of modifing the nwn script to report the instructions is NOT the best solution because the instructions still won't appear when someone tries the KDE link. However, it is definitely better than the segmentation fault. At least the end user is likely to notice the problem when they try and debug the problem. In regards to language, it looks like what happens is all three languages I have configured as LINGUAS in make.conf are installed ontop of eachother in the order listed. As a workaround I did: LINGUAS="en" emerge nwn However, this is not a good solution. I have three languages configured because my wife will normally use French, and my son Spanish. Right now there is no possible way to do this with NWN other than re-emerging it each time one of them wants to use it. Since it looks like NWN only supports one language at a time, the correct thing to do would be to install NWN in locale specific directories with the common files symlinked. i.e. /opt/nwn/en, /opt/nwn/fr, /opt/nwn/es ... Note: Most programs use "en" as the default, so in this senario /opt/nwn/en might be a symlink to /opt/nwn. The "nwn" would need to determine which directory to use. I believe that the "LANG" environmental variable should work. ie "/opt/nwn/$LANG/nwn" I have no intentions of fixing the broken behavior of upstream. Unless either you or Bioware are willing to pay me to the contrary, this is WONTFIX. While this might not be the answer that you are looking to receive, WONTFIX is quite simple. It means that I will not fix it. Reopening a bug is not going to change the fact that I am not going to "fix" it, so please save us both some time. As I said, there's no real way to actually fix the language problem other than to force the package to only install the first language. I definitely am not going to spend the time trying to do as you suggested with the symlinks as it seems overly complex, and again. I am not paid by Bioware. If you're willing to do the work and file it to a bug, then I'll verify it and patch it, but if this is left to me, it is a WONTFIX. Have a look at PORTAGE_ELOG and friends in /etc/make.conf.example as a better (general) solution to seeing the messages an ebuild has for you. I haven't tried to change ebuild's before, but I am perfectly willing to try. When/if I have a comprehensive patch to attach, do you wish me to change the status of this bug? Bill (In reply to comment #10) > Have a look at PORTAGE_ELOG and friends in /etc/make.conf.example as a better > (general) solution to seeing the messages an ebuild has for you. > Thanks. Unforunately nwn-data did not log its important messages to e-log, rather it just sent the messages to standard out. Bill Bill, if you have a patch to resolve the language issue, then yes, I would definitely accept it. Either a patch to only use the first available language from LINGUAS, or a patch to allow all of them (perhaps with compatibility scripts like nwn-es, nwn-en, nwn-fr, etc.) to be used would be fine. As I said, it isn't so much that I don't think it is a good idea as much as I think it is a *lot* of work and in my opinion, not a valuable use of my rather limited time. I would love to see a patch for it, though, so if you're willing to put in the work, I'd definitely commit it. I am changing all of the einfo messages to elog as we speak, so that should resolve that issue. Created attachment 99168 [details]
Suggested update to resolve the language problem
This update allows multiple languages to be installed at once and each user to have their own saved games.
Bill
(In reply to comment #13) > Bill, if you have a patch to resolve the language issue, then yes, I would > definitely accept it. > > Either a patch to only use the first available language from LINGUAS, or a > patch to allow all of them (perhaps with compatibility scripts like nwn-es, > nwn-en, nwn-fr, etc.) to be used would be fine. As I said, it isn't so much > that I don't think it is a good idea as much as I think it is a *lot* of work > and in my opinion, not a valuable use of my rather limited time. I would love > to see a patch for it, though, so if you're willing to put in the work, I'd > definitely commit it. > > I am changing all of the einfo messages to elog as we speak, so that should > resolve that issue. > I am sorry it took me awhile to get to this. I just uploaded an updated set of ebuilds for you to verify. I was surprised just how load the download is with the nowin option, I had to resize some of my partitions to test the ebuild script with that option, but everything seems to work as expected. Bill Bill Created attachment 99178 [details]
suggested update to resolve the language problem
Opps. I notice that digest files where being unpacked multiple times, and the .metadata directory in the nwn package where not being installed. I've corrected those two problems.
Cool... it'll take me a while to get this implemented, since I'm making some other changes at the same time (nwn takes 1+ hours to digest/commit, so I try to make all my changes at once) Perhaps I should mention I already build the digests for the updates to nwn-data and nwn. The install is also quicker, because unnecessary components are not downloaded with the updated version. (The original version downloaded language files for nwn-data even when they weren't needed.) Bill The digests and such don't help me, as #1. I'm required to redo them myself, and #2. the Manifest changes due to CVS filling certain keywords, like the header, automatically Regarding the segmentation fault, installing with USE="-nowin" fixed the problem for me. OK. I'm marking this as FIXED since it works with USE="-nowin" and I've tested USE="cdinstall" and USE="nowin" now (there was a bug in nowin). |