Ubuntu

flickering 3d models in wine 1.3.23 ?

Asked by JJ Master on 2011-07-09

Hi, all

When i update Wine package form version 1.3.22 to 1.3.23 lot of applications and games using wine running with errors in graphics and flickering 3d models. Performance is good it's affects only visual graphics.

I've tested it on 3 computers (Laptop Intel graphics, AMD based desktop computer GF 9800 card and old computer pentium 3 based with radeon graphic card)

Tested on Ubuntu 10.10 maverick, 10.04 LTS and 11.04 versions (gnome and xfce).

Problem always persist.

The question is: How to report this bug when it's present in many versions of Ubuntu, many types of programs and hardware ?

BTW: I'm solved it reverting wine package form 1.3.23 (official) to 1.3.22(previous) for now.

Thanks in advise.

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu wine1.3 Edit question
Assignee:
No assignee Edit question
Last query:
2011-07-09
Last reply:
2011-07-10

First carefully read https://help.ubuntu.com/community/ReportingBugs carefully. Then pick any of the systems on which to report the bug (just make sure it's a currently-supported version of Ubuntu...which all the systems you listed are). Of the systems that you try, the latest system that is affected is probably best. If you are willing to attempt to reproduce this bug on an Oneiric system, that might be even better, but it is not necessary for you as the original reporter to test it on Oneiric in order to report the bug.

After searching to see if the bug has already been reported (the ReportingBugs page explains how to do this), produce the bug and, while wine is running, invoke ubuntu-bug with the PID of the running wine process (the ReportingBugs page explains that too). This will automatically attach important information. In your bug report, make sure to include a detailed description of the problem, and make sure to list the systems on which you have produced the problem, what version of Ubuntu and wine they have, and what their hardware is (specify the CPU architecture, the video card, and, if applicable, the make and model of the computer). Also make sure to specify which of the systems you are reporting the bug on (so that it's clear which of the systems the information that is automatically attached by Apport corresponds to). In your bug report, you should also specify what Windows program you were running when you produced the bug (and, if possible, give examples of additional Windows applications that can be used to produce this bug, especially if the Windows application you used to produce it is proprietary payware and thus not readily available to all developers). You should include or attach the output of "sudo lshw -C display" (run in the Terminal, without the quotes) for at least the system on which you are reporting the bug, as that provides detailed information about your graphics hardware and drivers.

You can add tags to the submitted bug report to make it more clear that it affects a wider variety of systems. For example, if you report it on the Natty system, the Apport reporting process will have automatically tagged the bug with the natty tag, so you can manually add the maverick and lucid tags. (Lucid Lynx is the codename for Ubuntu 10.04 LTS). Though it is less important to do so, you can also add architecture tags. For example, if you report the bug on an amd64 system (i.e., a PC or Mac with a 64-bit Intel or AMD desktop processor) then the Apport reporting process will automatically tag it with the amd64 tag; if you have also produced the bug on and i386 system (i.e., a PC or Mac with a 32-bit Intel, AMD, or compatible processor), you could manually add the i386 tag.

After reporting the bug, you can (and should) link this bug and this question to each other with the "Link existing bug" link on this question page. However, your bug report should be complete and self-contained--it should not be necessary for the developers to refer to this question page in order to fully understand and appreciate your bug report.

Finally, I recommend searching to see if there is an upstream bug filed at http://bugs.winehq.org for this problem. (It is also OK to do this earlier in the process, if you like.) If there is, you can link the upstream (Wine project) bug with the downstream (Ubuntu) bug using the blue "Also affects project" link on the Launchpad bug page (you should provide the upstream bug URL in the appropriate text box). If there is no upstream bug report and you are willing to make the effort of trying to produce the bug on a non-Ubuntu system (preferably, on a non-Debian system running a distribution based neither on Debian nor Ubuntu), and you are able to produce it on such a system, you could file an upstream bug report (and then link it to the downstream Launchpad report). If you don't produce it on a non-Ubuntu system, you could still file an upstream bug report, though you may be better of waiting until the downstream bug has been marked Confirmed in Ubuntu and/or Ubuntu developers indicate that it should be reported upstream, as they may ask for additional information to be provided.

If you report an upstream bug, please make sure to first read the documentation at http://bugs.winehq.org first so you know how to do so properly. Different bug trackers and projects have different guidelines for bug reporting, even though many of the elements of their guidelines tend to be similar.

Can you help with this problem?

Provide an answer of your own, or ask JJ Master for more information if necessary.

To post a message you must log in.