Bug 47796 - Powerpoint 2010 Viewer crashes with Wine and the Nouveau driver: "Unhandled exception: assertion failed"
Summary: Powerpoint 2010 Viewer crashes with Wine and the Nouveau driver: "Unhandled e...
Status: RESOLVED DUPLICATE of bug 49148
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: git
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Nouveau Project
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-24 02:14 UTC by alister.hood
Modified: 2013-08-21 05:53 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
kernel log (36.90 KB, text/plain)
2012-03-24 02:14 UTC, alister.hood 		no flags Details
backtrace from Wine (19.47 KB, text/plain)
2012-03-24 02:16 UTC, alister.hood 		no flags Details
output of lspci -vvv (10.26 KB, text/plain)
2012-03-24 02:17 UTC, alister.hood 		no flags Details
View All

Description alister.hood 2012-03-24 02:14:38 UTC 
Created attachment 58959 [details]
kernel log

I have an Nvidia MX440 graphics card and am running Arch Linux.  When I run MS Powerpoint Viewer 2010 (using Wine), a file select dialog opens for me to
select a powerpoint file, but then it crashes a second or so after the dialog
opens.
On the Wine tracker I was told that it was a problem with the nouveau driver, not Wine:

> > This is an assertion in nouveau driver, so you have to try to update it or use
> > proprietary one.
> To add to that, the backtrace is missing function names and line numbers, but
> this is probably the assert in get_rt_format() in nv10_state_fb.c. It gets
> triggered because during wined3d startup we try to attach a GL_RGB5_A1 texture
> (among various others) to an FBO. The driver should probably fail the FBO
> completeness test for formats it doesn't know how to handle instead of
> asserting.

I am running current GIT, but this issue is longstanding.
Comment 1 alister.hood 2012-03-24 02:16:17 UTC 
Created attachment 58960 [details]
backtrace from Wine
Comment 2 alister.hood 2012-03-24 02:17:02 UTC 
Created attachment 58961 [details]
output of lspci -vvv
Comment 3 Trek 2013-01-12 23:45:00 UTC 
I think to have the same bug. I filed a complete report at:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697913

The error message is:

nv10_state_fb.c:50: get_rt_format: Assertion `0' failed.

The installed drivers are:

libdrm-nouveau1a 2.4.33-3 i386
libgl1-mesa-dri 8.0.5-3 i386
libgl1-mesa-glx 8.0.5-3 i386
linux-image-3.2.0-4-686-pae 3.2.35-2 i386
xserver-xorg-video-nouveau 1:1.0.1-4 i386

The video card is:

NVIDIA Corporation NV11 [GeForce2 MX/MX 400] (rev a1)


It seems to me that this bug can be merged with:

https://bugs.freedesktop.org/show_bug.cgi?id=49148

that contains also a patch.


This bug seems to affect some user, that filed these bug reports:

https://bugs.launchpad.net/ubuntu/+source/stellarium/+bug/1079011
https://bugzilla.redhat.com/show_bug.cgi?id=834329


I hope to have the time to setup a build environment to test the patch on my hardware, but in the meantime I wanted you to know about the situation.

Ciao
Comment 4 Trek 2013-01-13 01:08:41 UTC 
After doing some search, I found another patch that could address this bug:

http://lists.freedesktop.org/archives/nouveau/2012-July/010706.html

I am sorry but my limited knowledge about the mesa code do not let me to know what issue is related to this bug.
Comment 5 Ilia Mirkin 2013-08-21 05:53:15 UTC 
I downloaded the latest powerpoint viewer and was not able to recreate the crash on a NV18 card. There's another very similar bug (which is a tad newer than this one, but I've already commented on that one, sorry) that I'm going to mark this as a duplicate of. The upshot is that I don't see how that assert can happen with the current mesa code.

Please re-check with the latest mesa if this is still an issue, and add steps on how to reproduce if it still occurs. (And let us know if it doesn't occur anymore too.)

*** This bug has been marked as a duplicate of bug 49148 ***

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.