HipMaestro wrote...
What is the version/update number of python that fixed the problem for your configuration?
It wasn't python that fixed the problem. It was a dependency of the package python2-xy. It went something like this:
1: python2-xy required another package, which in turn required [some alternate version of mesa]
2: In order to install [some alternate version of mesa], standard mesa had to be uninstalled.
3: [some alternate version of mesa] broke NWN.
4: a new update to python2-xy no longer required [some alternate version of mesa], so that was uninstalled and replaced by standard mesa.
5: NWN started working again as soon as [some alternate version of mesa] was gone.
So what really fixed my problem wasn't a new version of python, it was the fact that the dependencies for Python(x,y) changed away from a version of mesa which broke NWN to a version which allowed NWN to work.
Skildron wrote...
Glad to hear you got it sorted out.
Thanks! In this case, all it took was a combination of luck and patience.
Skildron wrote...
Meanwhile, I did some testing with ubuntu 12.10 and 13.04. beta and both distros run NWN just fine after installing some packages not in the base config. So NWN still ist compatible to up to date Linux versions.
Good to know.
Skildron wrote...
BTW, I read "The Arch Way" and I am really intrigued. It seems to me like "back to good old times" when configuring a PC did not need more than a keyboard, a black and white display and a text editor (MS-DOS worked like that too, for those who remember) - and of course, a "little" bit of know-how. If I can get hands on a spare system, I'm going to try Arch Linux.
It's worth trying, even if you don't make it your main distro. Going through the process of installing and configuring Arch will force you to learn (or re-learn) a lot of stuff about Linux.
It's true that Arch emphasises the CLI and text editors, but not that's more of a means than an end. It's about having true simplicity instead of just a facade of simplicity. As Linux has grown, config files have become larger and more complex. Many distros responded by hiding that complexity behind GUIs. Unfortunately, there is then even less incentive to make the config files understandable, and the process tends to snowball. The Arch philosophy says that if you make the config files simple enough (and document them well enough), then people can edit their own config files instead of relying on GUIs to do it for them.
