When launching Blender from GNOME Shell, nothing happens (i.e. it is not launched). When launching from the command line, I get the following: $ blender connect failed: No such file or directory Instruction non permise (core dumped) So I try running it in gdb: (gdb) r Starting program: /usr/bin/blender [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/libthread_db.so.1". [New Thread 0xb73ffb40 (LWP 4463)] connect failed: No such file or directory Program received signal SIGILL, Illegal instruction. 0x0906c206 in RNA_def_property_range () (gdb) thread apply all bt Thread 2 (Thread 0xb73ffb40 (LWP 4463)): #0 0xb7fff424 in __kernel_vsyscall () #1 0x4803ca95 in sem_wait@@GLIBC_2.1 () at ../nptl/sysdeps/unix/sysv/linux/i386/i486/sem_wait.S:79 #2 0x488715df in IlmThread::Semaphore::wait() () from /lib/libIlmThread.so.6 #3 0x48870922 in IlmThread::(anonymous namespace)::WorkerThread::run() () from /lib/libIlmThread.so.6 #4 0x48871250 in IlmThread::(anonymous namespace)::threadLoop(void*) () from /lib/libIlmThread.so.6 #5 0x48036d8a in start_thread (arg=0xb73ffb40) at pthread_create.c:309 #6 0x47f60a0e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:129 Thread 1 (Thread 0xb7fcb7c0 (LWP 4459)): #0 0x0906c206 in RNA_def_property_range () #1 0x090703e5 in RNA_def_int () #2 0x084b7c17 in WM_OT_userpref_autoexec_path_remove () #3 0x084bbb47 in WM_operatortype_append () #4 0x084c08ac in wm_operatortype_init () #5 0x084b2a09 in WM_init () #6 0x0848a1ed in main () This is on Fedora 20 with blender.i686 1:2.69-5.fc20 (latest available from @updates). Let me know if there's anything more I can do.
At firt tahk you that you have take the time to create this bug report. It may be nice, if you can tell me which graphics adapter do you use. In addtional the output of the lspci -vv and glxinfo comands may be helpful.
Created attachment 866771 [details] Output of lspci -vv
Created attachment 866772 [details] Output of glxinfo
I have an ATI Radeon 9800 graphics card.
Thank you for your responds. Can you tell me which driver do you use for your graphics adaper, because I Assum that your issue depends on the drvier of your graphics adapter.
As the attached lspci output says: Kernel driver in use: radeon
@Jochen: this doesn't look like a Mesa bug to me, but I could be wrong. @Alexandre: could you please attach the output of: $ cat /proc/cpuinfo I'm pretty sure you're running an Athlon (circa 2001 or so?). Tbh I haven't tested our 32-bit Blender for a long, long while, and I'm wondering if we're including instructions (through optimizations) that that particular CPU can't handle.
I'm currently at work on another machine. The issue happens on my machine at home which is indeed an Athlon 2600+ (32-bit). I'll provide the cpuinfo this evening when I get back home.
Created attachment 867118 [details] Output of cat /proc/cpuinfo
(In reply to François Cami from comment #7) > I'm pretty sure you're running an Athlon (circa 2001 or so?). Late 2003 actually according to Wikipedia. ;-) > I'm wondering if we're > including instructions (through optimizations) that that particular CPU > can't handle. For my culture, I'm interested in an explanation of how you'll check that.
This CPU does not seem to support SSE2. The log for the build of blender mentions "SSE2 Support: detected." and blender seems to be compiled with SSE2 support after that as the CFLAGS have -D__SSE2__ I don't know what is the minimal set of feature we expect from 32 bit machines running fedora these days. One way of checking which instruction triggered the SIGILL would be to use 'disass' in gdb after breaking in RNA_def_property_range
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.