Bug 971923 - blender crashes switching viewport Abrt does nothing
Summary: blender crashes switching viewport Abrt does nothing
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: mesa
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-07 15:19 UTC by Joshua
Modified: 2013-08-27 08:34 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-08-27 08:34:02 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Joshua 2013-06-07 15:19:53 UTC
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):
blender-2.67a-3.fc19.x86_64

How reproducible:
100%


Steps to Reproduce:
1.open a blend file or start a new scene use the number pad to any view.
2.
3.

Actual results:
Application closes instantly

Expected results:


Additional info:
I am using KDE but tried Mate - same thing.
radeon driver ATI RV730/M96

Comment 1 Joshua 2013-06-07 16:23:26 UTC
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

Comment 2 Joshua 2013-06-07 18:36:55 UTC
running blender in fc19 on virtualbox does not have the problem -- must be an X related problem.

Comment 3 Jochen Schmitt 2013-06-08 16:45:44 UTC
I have pushed blender-2.67b-1.fc19 to updates-testing. It may be nice, if
anyone can try out this package.

Comment 4 Joshua 2013-06-08 19:23:45 UTC
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.

Comment 5 Joshua 2013-06-11 03:22:19 UTC
I just did a major update that included xorg and mesa packages now it seems to be fine.

Comment 6 Joshua 2013-06-11 14:00:27 UTC
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
Writing: /tmp/14ethel-deck-rail_City_MV_01.crash.txt

[1]+  Segmentation fault      ./blender"

Comment 7 François Cami 2013-08-26 22:06:59 UTC
@Joshua: could you please try launching blender this way:

LIBGL_ALWAYS_SOFTWARE=1 blender

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.

Comment 8 Joshua 2013-08-26 23:30:30 UTC
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.

Comment 9 François Cami 2013-08-27 08:34:02 UTC
@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:
$ blender
$ LIBGL_ALWAYS_SOFTWARE=1 blender
hopefully with screenshots and how to reproduce things.

Closing.


Note You need to log in before you can comment on or make changes to this bug.