wine (and crossover) kill X on maverick box upgraded from lucid

[Shaya Potter]

Binary package hint: wine1.2

Trying to run powerpoint and I can load a presentation, but as soon as I switch slides, X is killed (as if it was zapped), and restarts itself on a new VT.

I see nothing any Xorg.0.log file indicating a crash (or anything really), nothing in ,xsession-errors.

tried with both metacity and compiz and no difference.

[Scott Ritchie (scottritchie)]

Logs aside, it is a crash in either X itself or the video driver, as killing X is not something Wine is supposed to be able to do. What kind of video card do you have?

[Shaya Potter (spotter)]

embedded intel 4500 (thinkpad W500)

[Shaya Potter (spotter)]

ran X by hand (startx)

instead of crashing it just hang (but not deadlocked, kill -9 worked via remote login). when it was hung, screen slowly went white

after I killed it, I saw output from startx (transcribed)

X: ../../uxa/uxa-glyphs.c:986: uxa_glyphs_via_mask: Assertion `uxa_pixmap_is_offscreen(src_pixmap)' failed

[Scott Ritchie (scottritchie)]

What does lspci list the video card as?

[Shaya Potter (spotter)]

00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)

[Shaya Potter (spotter)]

google seems to indicate similar behavior recently

http://www.google.com/search?q=uxa_glyphs_via_mask

[bugbot (bugbot)]

Hey Shaya,

Thanks for your interest in Ubuntu.

Thanks for testing maverick during its development period. Unfortunately it looks like this bug report didn't get attention during the maverick development period. But I see there's not been more comments on the bug since the release, which makes me wonder if this is still an issue for you?

If you've not seen this issue since maverick's release yourself, it may have been solved by kernel or X or other updates that occurred late in the release; if so, would you mind please closing the bug for us? Go to the URL mentioned in this bug report, click the yellow icon(s) in the status column and set to 'Fix Released'.

If you no longer have the hardware needed to reproduce the problem, or otherwise feel the bug no longer needs tracked in Launchpad, you can set the status to 'Invalid'.

If you are the original reporter and still have this issue, just reply to this email saying so. (Or set the bug status to Confirmed.) If you are able to re-test this against 11.04 Natty Narwhal (our current development focus) and find the issue still affects Natty, please also run 'apport-collect <bug-number>' while running natty, which will add fresh logs and debug data, and flag it for the Ubuntu-X development team to look at.

[bugbot (bugbot)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.