Bug 814665
Summary: | blender 2.62 crashes on startup | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jakub Steiner <jsteiner> | ||||
Component: | blender | Assignee: | Jochen Schmitt <jochen> | ||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 17 | CC: | danielbelton, hobbes1069, jochen, kwizart, promac | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2012-05-26 07:29:40 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Jakub Steiner
2012-04-20 11:12:11 UTC
I emailed the person responsible for setting up the SpaceNavigator software in Blender and it's supposed to happily keep working even if it can't connect to spacenavd which I think is why he assumes it's a SELinux issue. Now that I think about it. Let's try a little test if you don't mind. Even if you don't have a space pilot or other 3D input device you can still install spancenavd. I'm just curious if installing it will fix the problem. yum install spacenavd systemctl start spacenavd.service Actually, try just installing it first and see if Blender still crashes. If it does, try starting the service and running Blender again. What's strange is I run my own package of Blender (newer than what's in the repos) and while I do have spacenavd installed (I'm the maintainer) I don't have it running and Blender has never crashed on me like that. It may be nice, if you can install the debuginfo packages for libspnav and retry to reproduced the reported crash. Without the xymbols the backtrace is useless for me. *** Bug 814262 has been marked as a duplicate of this bug. *** Created attachment 580168 [details]
patch for blender ndof system
Here's the svn diff for the patch applied by upstream in case it's useful.
blender-2.62-6.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/blender-2.62-6.fc17 This update appears to fix this issue. I stopped and disabled the spacenavd service, and completely removed spacenavd using yum. Then installed this blender update, and tested it out. This appears to have fixed the spacenavd issue. What I get now when running blender: ======= [Me@tower20 ~]$ blender connect failed: No such file or directory ndof: spacenavd not found Error: Not freed memory blocks: 2 IDProperty group len: 128 0x53de838 uiAfterFunc len: 720 0x5385a48 Blender quit ======= I didn't get those other errors and warnings on the previous version, though. Here is what I got when running the previous version (with spacenavd loaded): ====== [Me@tower20 ~]$ blender ndof: unknown Logitech product c52b ndof: unknown Logitech product c308 Blender quit ====== Package blender-2.62-6.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing blender-2.62-6.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-6647/blender-2.62-6.fc17 then log in and leave karma (feedback). the luxrender-blender package needs to be rebuilt as well. Today's update to luxrender-blender has a dependency on a specific version (2.61) of blender. 12:09:32 : ERROR: Dependency resolving completed with errors 12:09:32 : ERROR: Package: LuxRender-blender-0.8.0-13.fc17.x86_64 (fedora) Requires: blender(ABI) = 2.61 Installed: 1:blender-2.62-6.fc17.x86_64 (@/blender-2.62-6.fc17.x86_64) blender(ABI) = 2.62 Installed: 1:blenderplayer-2.62-6.fc17.x86_64 (@/blenderplayer-2.62-6.fc17.x86_64) blender(ABI) = 2.62 Available: 1:blender-2.62-2.fc17.x86_64 (fedora) blender(ABI) = 2.62 Available: 1:blenderplayer-2.62-2.fc17.x86_64 (fedora) blender(ABI) = 2.62 This is known, and will be done along with a LuxRender RC1 compatible update. Thanks. I thought about it after writing the comment that I should really have opened a new bug report for it, but since it is already known and being taken care of, there isn't much need in doing so. blender-2.63a-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/blender-2.63a-1.fc17 Still getting a crash with http://kojipkgs.fedoraproject.org/packages/blender/2.63a/1.fc17/x86_64/blender-2.63a-1.fc17.x86_64.rpm It works if I enable the spacenavd.service as has been suggested. I completely removed the spacenavd package and it works fine here. Does it give you a crash if the spacenavd package isn't installed at all? Or is it crashing if spacenavd is installed but not enabled? Or both? Darn, I can't reproduce the crash at all today. blender-2.63a-1.fc17.x86_64 is able to run with the spacenavd service running or not, or the package uninstalled completely. Sorry for the noise. blender-2.63a-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. |