Red Hat Bugzilla – Bug 971923
blender crashes switching viewport Abrt does nothing
Last modified: 2013-08-27 04:34:02 EDT
Description of problem:
Any attempt to use the number pad to change viewport angle causes blender to crash without warning Abrt does not pick up the crash but a 'blender.crash.txt' file is written to tmp.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.open a blend file or start a new scene use the number pad to any view.
Application closes instantly
I am using KDE but tried Mate - same thing.
radeon driver ATI RV730/M96
This issue is not limited to fedora's blender build I have tried versions 2.66a and 2.67a from blender.org with the same results
running blender in fc19 on virtualbox does not have the problem -- must be an X related problem.
I have pushed blender-2.67b-1.fc19 to updates-testing. It may be nice, if
anyone can try out this package.
I have tried it with the same result.
I believe the problem is in mesa or the radeon driver.
xsession-errors is full of complaints but it doesn't seem to pick up the crash.
I just did a major update that included xorg and mesa packages now it seems to be fine.
No it is not fine. Same problem. I have no idea how to locate the cause. From the console there is no more information than this:
"read blend: /home/josh/Documents/14ethel-deck-rail_City_MV.blend
Warning: edge 88 - 89 appears twice, correcting
+ Segmentation fault ./blender"
@Joshua: could you please try launching blender this way:
and reproduce the problem?
If it works fine, we have a mesa problem.
If it still crashes, please report this bug to the Blender project.
Their bug tracker is at https://projects.blender.org/tracker/?group_id=9&atid=498
Please include whatever's needed to reproduce the bug.
I'm not sure where the problem was but as of June 17th updates the problem went away. I suspect radeon driver - I can check the yum logs.
Now the only problem is material view in cycles - there is no crash but only selected objects are visible and without mapped materials.
Starting blender "LIBGL_ALWAYS_SOFTWARE=1 blender &" and now material view works with cycles. I guess I could add it to the launcher.
@Joshua: yes, I suspect a mesa-libGL update fixed your problem. Switching component to mesa.
Could you please open a new bug, against mesa, explaining the difference in behaviour between:
$ LIBGL_ALWAYS_SOFTWARE=1 blender
hopefully with screenshots and how to reproduce things.