[SOLVED] Blender 2.63 only runs if I type /opt/blender/blender in cmdline
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Blender 2.63 only runs if I type /opt/blender/blender in cmdline
Built blender from slackbuilds, but only way to run it is through cmdline.
Code:
/opt/blender/blender
Code:
slackuser@slackmachine:/var/log$ /opt/blender/blender
connect failed: No such file or directory
ndof: spacenavd not found
found bundled python: /opt/blender/2.63/python
It still launches, but I just want to run blender without doing this all the time.
No shortcuts created or anything, can't even run it if I try to type 'blender' in the run field in lxde.. So what gives?
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,541
Rep:
When you installed blender, there should be a file in /etc/profile.d (actually two files), blender.sh and blender.csh. Look to see if /etc/profile.d/blender.sh is executable; if not, as root (or su -)
Now if only it would put entries in automatically.
Quote:
Originally Posted by tronayne
When you installed blender, there should be a file in /etc/profile.d (actually two files), blender.sh and blender.csh. Look to see if /etc/profile.d/blender.sh is executable; if not, as root (or su -)
That was it! Thank you. Maybe the slackbuild needs to be modified to have that step. Considered matter 'solved', but now just a few minor details:
Not that it really matters but after launching blender I expected some kind of .blender directory in my home folder and found none, also no entries in any of these categories... Hmmmmm
It doesn't work the way you want it to because /opt/blender isn't in your PATH environment variable. That' all that the blender.sh and blender.csh basically does (puts it in your PATH).
It doesn't work the way you want it to because /opt/blender isn't in your PATH environment variable. That' all that the blender.sh and blender.csh basically does (puts it in your PATH).
Oh... I found an icon setup in /usr/share/applications and I copied that to to the desktop and works that way... Hmm, so it seems to be that the slackbuild is not quite complete.
Should obviously be there when the script installs the program, and it doesn't automatically place entries anywhere for you to launch, you have to hunt for it yourself.
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,541
Rep:
Um, I did go to SlackBuilds.org, downloaded the source package and the SlackBuild (blender-2.63a-linux-glibc27-x86_64.tar.bz2 and blender.tar.gz) and did
Code:
cd /usr/local/packages/src/graphics
tar xzvf blender.tar.gz
<said file was not in gzip format, so...>
tar xvf blender.tar.gz
<success!>
<wrote a note to Robby Workman about that>
cd blender
mv blender-2.63a-linux-glibc27-x86_64.tar.bz2 .
blender.SlackBuild
<wait a while>
mv /tmp/blender-2.63a-x86_64-1_SBo.tgz .
installpkg blender-2.63a-x86_64-1_SBo.tgz
log out -- shuts down Xfce
log out -- exit from the console
log in -- log back in to the console
startx -- start Xfce
blender
and viola! there it was.
So, the SlackeBuild did install blender.sh and blender.csh in /etc/profile.d and there were executable (I sneaked a look) and what /etc/profile.d/blender.sh does, when you log in, is
Now, I don't know if it's exactly set up correctly; I get the following when I exit from it:
Code:
connect failed: No such file or directory
ndof: spacenavd not found
found bundled python: /opt/blender/2.63/python
Blender quit
but it appears to work initially and there might be some set up stuff I've missed (and I've never used it and haven't a clue what to do with it but does seem to work).
Weird... The files ARE there yes, but the script didn't make .csh and .sh files executable, I had to do that manually on my end. I don't know what I did differently than you, just unpacked the slackbuild and ran it.. But just for kicks I also ran it in cmdline and got the same thing you did...
Code:
slackuser@slackmachine:~$ blender
connect failed: No such file or directory
ndof: spacenavd not found
found bundled python: /opt/blender/2.63/python
Blender quit
slackuser@slackmachine:~$
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.