Why does Bledner 2.79b keep crash after a few clicks or key presses during a saved project?
- Inicie sesión ou rexístrese para enviar comentarios
Hi,
I don't really have much info to share atm cause I don't even know where to begin. I have solved the issue with the OS crash after opening up specific images (see solution in here: https://trisquel.info/en/forum/why-does-trisquel-11-crash-whenever-i-open-image-file )
I thought that would've solved this same problem too, unfortunately it hasn't; the same problem persists.
Bare in mind, this is an older version of the official blender that has been downloaded from their archives and has received a successful checksum. It had been extracted and removed from it's tar file and has currently been placed in my home folder in it's own directory.
Like I said, I don't know where to begin here and I could really use some help.
I know I've been "whiney" as of late, and I wish I could give as much back into this community, but I would really appreciate any question, advice and directions given to me.
Thank you
Bare in mind, this is an older version of the official blender that has been downloaded from their archives and has received a successful checksum.
Can't you use the version in Trisquel's repository?
I'm afraid not. It's to do with my graphics card not being able to accept OpenGL drivers higher than 2.1. Which is why I had to roll back and use the "Latest" version that my machine can take.
I've mentioned in here and found a solution for an earlier version of Trisquel.
https://trisquel.info/en/forum/anyone-else-having-trouble-getting-blender-and-running
I had tried other version of 2.79, 2.79a and 2.79b, but to no avail.
Maybe you could rebuild 2.79.b from source, and that could fix stability issues, if possible at all.
Pre-compiled binaries are build using the current library set at each release,
- aramo > 3.0.1+dfsg-7
- nabia > 2.82.a+dfsg-1
- etiona > 2.79.b+dfsg0-1
So 2.79.b binaries could be linked to libraries that doesn't exist at trisquel 11, Aramo.
That could explain why it crashes frequently.
Upd: BTW, etiona is no longer supported.
I see. So know I have to figure out a way to rebuild the 2.79b version from source and I'm home free.
Is there any guidelines anywhere on the internet to do such a thing; cause I'm not sure where to begin and I'm afraid things might get a bit too technical?
https://wiki.blender.org/wiki/Building_Blender/Linux/Ubuntu but use the older source code instead of the one on git.
Please, read the complete post before copy-pasting commands.
The simplest debian-like OS way to rebuild a package could be,
apt build-dep blender
apt source blender
cd blender-*
dpkg-buildpackage -us -uc
Now by default it will download the current source version of blender at aramo, so you need to add the etiona deb-src for it at sources.list
when having different versions of the same package it will by default pull the latest one, so in order to choose a specific version you can use "=", so I guess it should be something like,
apt source blender=2.79.b+dfsg0-1
That will download the source for 2.7, if you have previously added the necessary sources repos.
Final suggestion is that maybe you want to use a Trisquel 11 VM or some development environment, as apt build-dep will install several development dependencies that you might only use for that particular purpose.
With enough luck you'll get it built, and it will be proven to be easy, if not, well then it will get "technical" pretty quick.
Regards.
BTW, by using the method above, I was only capable to rebuild blender 2.79.b+dfsg0-1, under an etiona environment.
Hope you had better luck.
Afraid not. I got up to 'apt source blender=2.79.b+dfsg0-1' and I received this instead.
USER@DEVICE:~ $ sudo apt source blender=2.79.b+dfsg0-1
Reading package lists... Done
E: Can not find version '2.79.b+dfsg0-1' of package 'blender'
E: Unable to find a source package for blender
The is the package name right?
Okay, this is strange. Instead of running the app as a stand alone executable file, I installed in on my laptop to run as a full fledged application.
The intent was to try to run it through 3D Emulation to see how it would respond, but when trying it out natively, it no longer crashes. Somehow installing it properly appeared to have fixed the issue. (more found here: (3D Emulation: https://trisquel.info/en/forum/anyone-else-having-trouble-getting-blender-and-running#comment-168164 ) (Installing the Tar file: https://trisquel.info/en/forum/anyone-else-having-trouble-getting-blender-and-running#comment-168172 ))
I also used 'sudo apt-mark hold blender' to prevent this version from getting an update.
Bare in mind...it hasn't crashed yet, but so far so good.
I'll report back here if it does crash again.
Okay, what do you know, it started crashing again after a few clicks.
Now I run it through 3D emulation by entering the appropriate folder with:
Me@MyComputer:~$ cd /opt/blender-2.79b-linux-glibc219-x86_64
(that's my software version I'm using)
...then run the following command:
Me@MyComputer:~$ LIBGL_ALWAYS_SOFTWARE=1 ./blender
It basically runs it without acceleration.
Testing it out now and seems to be functioning well so far, but then again I said that before.
Will keep testing and report back my findings. Hopefully, this will be the solution I need.
Alright, so I've been testing out this approach and it works flawlessly. It appears to have solved all of my issues.
Now I just need to see if there is a way to launch it from the menu using this same approach.
I know using gedit or nano to access/edit file:
'~/.local/share/applications/blender.desktop'
reveals:
[Desktop Entry]
Name=Blender
Exec=/opt/blender-2.79b-linux-glibc219-x86_64/blender %u
Terminal=false
Icon=/opt/blender-2.79b-linux-glibc219-x86_64/blender.svg
Type=Application
Categories=Application;Graphics;X-Developer;
I can see the Executable command is:
'Exec=/opt/blender-2.79b-linux-glibc219-x86_64/blender %u
Terminal=false'
Now if only I am able to somehow execute this, editing and using this command:
'LIBGL_ALWAYS_SOFTWARE=1 ./blender'
?
SOLUTION FOUND!!!!
Edit the desktop file with
'nano /opt/[blender-folder-name]/blender.desktop'
Then add this into the text file:
'/opt/[blender-folder-name]/pipenv LIBGL_ALWAYS_SOFTWARE=1 blender %f'
env (or pipenv in my case) is used to print environment variables. It is also used to run a utility or command in a custom environment.
'pipenv' was the one that worked for me, which is a variation of the 'env' command.
If this doesn't work for anyone, you can just replace 'pipenv' with these one's instead:
env venv pyvenv pyenv virtualenv virtualenvwrapper pipenv
Now we can use almost any program on an older graphics drive.
- Inicie sesión ou rexístrese para enviar comentarios