Seg Fault on start of new map in Ubuntu Natty with current 0.4.dev
-
- Member
- Posts: 12
- Joined: Thu Jun 07, 2012 20:47
- Location: lockhart
Seg Fault on start of new map in Ubuntu Natty with current 0.4.dev
Well, I ran into this after installing the most recent dev snapshot from ppa.
At the "Updating textures and meshes in item definitions" stage it gives me a SEGMENTATION FAULT.
Probably a setting that I am just missing, however, I have ran various versions on several different computers and not seen this.
Computer is an Acer Aspire One running Ubuntu Natty with most current version off of the ppa repository. After first encountering the error I purged the program, removed all lingering files, and reinstalled fresh, still yielding the same error.
Thanks in advance
At the "Updating textures and meshes in item definitions" stage it gives me a SEGMENTATION FAULT.
Probably a setting that I am just missing, however, I have ran various versions on several different computers and not seen this.
Computer is an Acer Aspire One running Ubuntu Natty with most current version off of the ppa repository. After first encountering the error I purged the program, removed all lingering files, and reinstalled fresh, still yielding the same error.
Thanks in advance
Why not compile it yourself, instead of using ppa/launchpad? Go to minetest.net, click on GitHub, scroll the page down to the readme.txt and follow the instructions under "Compiling on GNU/Linux:". Just copy the lines and paste them in your terminal (probably you have to type "Sudo" before the 1 paste).
-
- Member
- Posts: 12
- Joined: Thu Jun 07, 2012 20:47
- Location: lockhart
Ideally, that would be the solution, or at least a step in troubleshooting, however, I only installed from ppa because of an issue in pulling in the proper versions the requirements to compile the code, most cases being that the dev versions of the requirements would roll programs back to previous versions. This causes the install of the dev versions to fail due to the depends of the depends cannot be resolved. I have yet to try and compile it against the newer version that I already have (I haven't had time to check the code to see if it builds against the specific version or against any better than that version).
In the mean time, maybe someone has another idea (I may try compiling against the newer libraries tomorrow).
In the mean time, maybe someone has another idea (I may try compiling against the newer libraries tomorrow).
I see you have far more knowledge of Linux than I do. It's hard for me to follow even the core of your reply :-/
So rests me only to wish you good luck solving the problem.
So rests me only to wish you good luck solving the problem.
Last edited by Topywo on Fri Jun 08, 2012 15:28, edited 1 time in total.
-
- Member
- Posts: 12
- Joined: Thu Jun 07, 2012 20:47
- Location: lockhart
-
- Member
- Posts: 12
- Joined: Thu Jun 07, 2012 20:47
- Location: lockhart
-
- Member
- Posts: 12
- Joined: Thu Jun 07, 2012 20:47
- Location: lockhart
Yes, I have ran both 0.1 and 0.2 on it at various times. I have not ran 0.3 (rather opting to put it on the desktop). After my earlier posts, I compiled 0.3.1 and it shows the same issues that the minetest-delta fork have. Namely, any block that extends beyond the edge of the screen does not render. Other than that speed is good, there is no lagging or other problems apparent.
I have a few more things that I can try on my end, including updating Ubuntu to the next release (I usually run a bit behind for stability). I am just trying to make sure that I did not miss a setting somewhere.
I have a few more things that I can try on my end, including updating Ubuntu to the next release (I usually run a bit behind for stability). I am just trying to make sure that I did not miss a setting somewhere.
-
- Member
- Posts: 12
- Joined: Thu Jun 07, 2012 20:47
- Location: lockhart
- LolManKuba
- Member
- Posts: 939
- Joined: Fri Feb 10, 2012 22:36
- Location: Ontario, Canada
- Contact:
-
- Member
- Posts: 12
- Joined: Thu Jun 07, 2012 20:47
- Location: lockhart
As noted above, FPS originally was ZERO, openGL would segfault when rendering mesh, null would fail with a floating point exception, direct3d is not an option with Linux, and software rendering would render (around 15FPS) but would not render any block that was not entirely on the screen.
In the end, it took both adding the openGL ES libraries and Burningsvideo to get everything to render (other rendering options still give their previous errors without the libraries and burningsvideo does not render for me without them).
In the end, it took both adding the openGL ES libraries and Burningsvideo to get everything to render (other rendering options still give their previous errors without the libraries and burningsvideo does not render for me without them).
-
- Member
- Posts: 12
- Joined: Thu Jun 07, 2012 20:47
- Location: lockhart
Who is online
Users browsing this forum: No registered users and 25 guests