Blender was running fine (or not, but that’s unrelated) until a few days ago it consistently crashes upon startup. Run straight from the command line, it says:
connect failed: No such file or directory
then writes a crash text file in /tmp, which contains:
Program received signal SIGSEGV, Segmentation fault.
__strstr_sse2 (haystack_start=0x0, needle_start=0x405e696 “ATI”) at …/string/strstr.c:63
63 …/string/strstr.c: No such file or directory.
(gdb)
Is Blender or GDB looking for a source file? Just what is strstr_sse2, and why is segfaulting?
This is on Ubuntu Linux, 64-bit with 16GB RAM. I don’t know of anything I changed, on purpose or accidentally, to cause Blender to act different.
Hi
“connect failed: No such file or directory” this text appear when Blender is compiled with NDOF - devices support (Spacenavigator etc.) by default in builds from blender.org.
Which verssion you have.
Do you upgraded system, or libs???
Try some builds from graphicall.org
This is my output when i start blender 2.70 from blender.org
“connect failed: No such file or directory
Read new prefs: /home/blendermaniac/BLENDERY/blender-2.70-linux-glibc211-x86_64/2.70/config/userpref.blend”
Which dont appear when i’m build blender from source with NDOF=OFF
I have Xubuntu x64 4GB RAM and i have nvidia graphic card. -
Mayby try to delete the config folder (make copy first)
I’m not a programer, or it tech… Just trying to help…
Regards
Moving .blender out of the way had no effect. I haven’t tried building Blender from source in a long time. Last time was a mess, but then I was new to Blender. Right now I’ve got a huge physics software build going, but will try making Blender from source soon.
A new clue: When I close the Chromium browser, Blender now starts up. Not starts up fine, but starts up, at least.
Another problem has been haunting me for a while, before this startup crash, which is that for 2.69, 2.70 clicking Viewport Shading to Rendered causes an instant lock-up, that even ctrl-C on the command line can’t kill. So I use 2.68. Except half the times I run it, many of the buttons such as in Properties, are just black squares. There’s plenty of RAM. These could be some sort of OpenGL-related troubles.
So maybe I will have to power down this machine sometime this year and update all software, drivers, etc.
I’ve wiped my disk to install a fresh Arch Linux. No Chromium. It is blacklisted forever So far, all versions of Blender run fine, even the Viewport Shading Rendered. I have yet to run Youtube or Flash a lot to see if they have any detrimental effect. Or to use Blender on something complex with plenty of fancy nodes, animation and compositing.
As the absent-minded parachutist said when half-way down, “so far so good…”