Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#7440 - Blender crash to SIGSEGV after change settings file paths

Attached to Project: Arch Linux
Opened by vladodriver (vladodriver) - Thursday, 14 June 2007, 10:33 GMT
Last edited by Tobias Kieslich (tobias) - Friday, 26 October 2007, 17:09 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Kieslich (tobias)
Architecture i686
Severity High
Priority Normal
Reported Version 2007.05 Duke
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:Blender crash if change File Paths


Additional info:
* package version(s) 2.44.1
* config and/or log f.iles etc.
(SIGSEGV)


Steps to reproduce: After change settings File Paths - e.g. python scripts, Blender crashed to SIGSEGV..
This task depends upon

Closed by  Tobias Kieslich (tobias)
Friday, 26 October 2007, 17:09 GMT
Reason for closing:  Won't fix
Additional comments about closing:  this is an upstream problem.
2.45 does not crash for me, it just reports an error
Comment by Michal Krenek (Mikos) - Thursday, 14 June 2007, 21:17 GMT
I can confirm it. After upgrade to blender-2.44-1 package, I can't even open my .blend files!
Comment by Jacek Poplawski (Jacek Poplawski) - Saturday, 16 June 2007, 12:07 GMT
Just a small info - original binary from blender.org works correctly, so problem is in the package, not in the Blender version (so we don't need to wait for next release, just fix something in the package).
Comment by Tobias Kieslich (tobias) - Saturday, 16 June 2007, 19:57 GMT
I tried all the things that you guys suggested but it works fine for me. I can't reproduce the SIGSEGV.
Do you see more of an error message when you start with blender -d from a terminal? It might have to have debugging symbols turned on though which it hasn't but it might be worth a try. The other option is you compile blender from abs (about 45 min on an Athlon+2400) and see if that helps...
Comment by Jacek Poplawski (Jacek Poplawski) - Saturday, 16 June 2007, 22:15 GMT
Here it is a backtrace from gdb:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1215047968 (LWP 14825)]
0x08197df4 in drawfilespace ()
(gdb) bt
#0 0x08197df4 in drawfilespace ()
#1 0x08243305 in scrarea_do_windraw ()
#2 0x08182cab in screenmain ()
#3 0x081454a7 in main ()
Comment by Jacek Poplawski (Jacek Poplawski) - Sunday, 17 June 2007, 22:53 GMT
According to thread on forum it is related to ~/.blender directory. Tobias, please remove it from your ${HOME} and run Blender, then save.
Comment by Tobias Kieslich (tobias) - Monday, 18 June 2007, 19:41 GMT
okay, I can confirm when I delete .blender it throws up. However when I copy /usr/share/blender to ~/.blender as suggested it works. A question to Jacek, What exactly did you do with the original binary from blender.org? Unzip it and run it from the directory? I can see how that will work because blender has a hardcoded behaviour to search for config files in the directory where it is located in. The second searchpath is the Home directory. I can't make it picking up /usr/share/blender as default, which sucks. And I can't put the files per default into /usr/bin where our binary is place as it would pollute that directory. So I'm open for suggestions. Copying from /usr/share/blender to ~/.blender is already in the post_install message ...
Comment by Jacek Poplawski (Jacek Poplawski) - Monday, 18 June 2007, 21:00 GMT
Yes, of course I ran it from the same directory. I haven't noticed post install message, probably like everyone else who had this bug :)
Comment by Tobias Kieslich (tobias) - Monday, 18 June 2007, 21:25 GMT
Well, I admit it is an issue, since the applications behavior out of the box is throwing errors. And 2.43 does not show the behavior.
Comment by Jacek Poplawski (Jacek Poplawski) - Monday, 18 June 2007, 21:29 GMT
In that case let's report a bug for Blender project.

Loading...