Yes and no. I went through the setup and compile again and checked some packages in the requirement list. There were a couple in that list that had broken dependencies on my machine. This is mostly due to a couple edgy updates that have broken several packages. So I successfully got those installed and the depends fixed.
I did the compile with no detected errors. In fact it seemed to go smooth the whole way. It was only at the point where I tried to run winecfg or wine itself that I got the Segmentation Fault. I'm not really sure what is causing this or what the memory problem is. The only thing I can figure is that you are running Dapper and the libraries at that version work right for this compile. I am thinking that Edgy has one or more of those libraries at different versions and that it breaks because of that.
I can't really nuke the OS until Thanksgiving (US) holiday or maybe even the beginning of Christmas holidays for me.
I hadn't ever intended on returning to Dapper because there are so many cool things about Edgy, but if I can run GW in Dapper but not Edgy then I will revert.
Bookmarks