App running under Wine does not refresh the screen

[spiceisland]

Binary package hint: wine

I have installed Source Insight, v3.50.0058 (http://www.sourceinsight.com), under Wine (0.9.58-0ubuntu2) under Hardy Beta.

Source Insight is a code editor and browser. You can install a time-limited copy if you want.

Anyway, having used this under Wine under Ubuntu for 18 months, with only a couple of niggly problems, I decided to upgrade (by doing a wipe + fresh install) to Hardy Beta. Since then, Source Insight has exhibited major problems.

These all centre around NOT refreshing the screen after things happen:

(1) Opening a new source-file window and moving it. Also resizing an existing window.

(2) Minimising and then maximising the Source Insight window itself.

In both cases, the screen inside the Source Insight window does not refresh. Moving the window around the screen does nothing (except get a nice swirly pattern of a repeating window title-bar inside the window itself.

The only way I have found to cure the problem and make the window refresh itself is to switch to the second workspace, wait a few seconds (until the window with the "Go to left workspace ..." pops up) and then switch back. THEN the window refreshes. Sometimes. If it does not, switch to the other workspace again and wait longer before switching back.

This is on a Dell D620 with an nVidia "G72M [Quadro NVS 110M/GeForce Go 7300]" and a second Dell 2007FP display attached. I'm running the graphics in TwinView mode (which means a manually configured xorg.conf, attached).

Going to System -> Preferences -> Appearance -> Visual Effects shows that "None" is currently active.

[spiceisland (graham-hudspith)]

Binary package hint: wine

I have installed Source Insight, v3.50.0058 (http://www.sourceinsight.com), under Wine (0.9.58-0ubuntu2) under Hardy Beta.

Source Insight is a code editor and browser. You can install a time-limited copy if you want.

Anyway, having used this under Wine under Ubuntu for 18 months, with only a couple of niggly problems, I decided to upgrade (by doing a wipe + fresh install) to Hardy Beta. Since then, Source Insight has exhibited major problems.

These all centre around NOT refreshing the screen after things happen:

(1) Opening a new source-file window and moving it. Also resizing an existing window.

(2) Minimising and then maximising the Source Insight window itself.

In both cases, the screen inside the Source Insight window does not refresh. Moving the window around the screen does nothing (except get a nice swirly pattern of a repeating window title-bar inside the window itself.

The only way I have found to cure the problem and make the window refresh itself is to switch to the second workspace, wait a few seconds (until the window with the "Go to left workspace ..." pops up) and then switch back. THEN the window refreshes. Sometimes. If it does not, switch to the other workspace again and wait longer before switching back.

This is on a Dell D620 with an nVidia "G72M [Quadro NVS 110M/GeForce Go 7300]" and a second Dell 2007FP display attached. I'm running the graphics in TwinView mode (which means a manually configured xorg.conf, attached).

Going to System -> Preferences -> Appearance -> Visual Effects shows that "None" is currently active.

[spiceisland (graham-hudspith)]

The problem seems a LOT worse when running with the two displays and with the Source Insight window on the second (non-laptop) display.

When running in single-display mode (i.e. at home instead of work), the "new source file window" problem does not seem to occur so much. The "minimising/maximising" problem occurs all the time, whatever the display being used.

[Scott Ritchie (scottritchie)]

So the last version of Wine this worked with was the one included in Gutsy? (0.9.46)

[spiceisland (graham-hudspith)]

Yep, everything worked fine under Gutsy.

I guess the thing to do would be to build and try 0.9.46 under Hardy. And then try 0.9.48 under Gutsy.

I'll try and do this in the next few days.

My gut(sy) feeling is that this is down to the new versions of Gnome and/or X, but time will tell.

[spiceisland (graham-hudspith)]

Sigh! Change that last comment to:

... then try 0.9.58 under Gutsy.

[spiceisland (graham-hudspith)]

Scott, my gut feeling was wrong, which is why I'm not a wine/gnome/x developer!

I downloaded, configured and built 0.9.46 under Hardy and Souce Insight works fine.

So, I've just been doing a binary-search of download, build and test of all versions between 0.9.46 and 0.9.58 and have found that ...

Source Insight works on versions upto (and including) 0.9.56 and fails on versions 0.9.57 and later.

NOTE - this is just on checking case (2), above. I won't be able to able to test it under dual-monitor mode until tomorrow, but I suspect that the results will be the same ...

At least I can carry on using 0.9.56 until the problem is solved!

When I've tested 56 and 57 under dual-monitor mode tomorrow, I'll add a comment to that winehq ticket you have created "upstream".

BTW - I've been configuring to build and install into /usr/local/wine-0.9.5x and all works fine apart from the minimise/maximise/close icons on the windows all missing. Will these reappear if I configure and build to install under /usr instead? Or do I have to apply your special, ubuntu-package-source "diff" file to get my copy of wine to integrate into the O/S properly too?

[Scott Ritchie (scottritchie)]

Further narrowing it down, the regression appeared some time between 0.9.56 and 0.9.57.

[Scott Ritchie (scottritchie)]

No, other than removing the package, source-installs of Wine should work fine in /usr/local

Upstream would love it if you could do a proper regression test, that way the exact patch that broke it could be determined. Thank you so much for your help.

[spiceisland (graham-hudspith)]

Well, I can confirm that the "minimising and maximising" problem (number 2, above) was broken in the move from 0.9.56 to 0.9.57.

Unfortunately, the "sub-window visual artefacts corruption" problem (number 1, above) is still present in 0.9.56. So I'll have to perform some more building of previous versions to see where that problem was introduced.

0.9.46 is still a star release, though!

[spiceisland (graham-hudspith)]

Scott - I can confirm that the latest release of wine, 0.9.59, seems to fix the "minimising and maximising" problem (number 2, above).

However, it still does not fix doing the same operations on sub-windows within Source-Insight. Of course, this may be down to bugs in Source-Insight itself, but suspect the developers of Source-Insight would argue that "it works fine when run under Windows!" :-(

I have made a flash movie demonstrating the problem:

(1) Here I have created a project containing the source code for SQLite.

(2) I open up one source-file (journal.c) and then another (complete.c).

(3) I maximise the second source-file sub-window => screen corruption.

(4) I unmaximise this => still get screen corruption.

(5) I then move the second source-file sub-window around a bit => still get screen corruption.

[spiceisland (graham-hudspith)]

Sigh! Can't attach more than one file at a time!

Anyway, here is an html file to "drive" the flash file attached above.

[Spiceisland (g-w-hudspith)]

Just to bring you up-to-date w.r.t. the downstream Ubuntu bug report, I can verify that "Minimising and then maximising the Source Insight window itself" (aka "Problem (2)") has been fixed in 0.9.59.

However, the other "Opening a new source-file window and moving it. Also resizing an existing window" problem (aka "Problem (1)") is still present.

Going back through the previous versions, the problem disappear when I get to 0.9.53 and reappears if I move forward to 0.9.54.

I've attached a flash video demonstrating the problem happening to the downstream Ubuntu problem report if you fancy a demo ...

[spiceisland (graham-hudspith)]

Okay, been playing with old versions for a few days now, so here is the latest update.

The original "Minimising and then maximising the Source Insight window itself" (aka "Problem (2)") seems to have been fixed in the move from 0.9.58 to 0.9.59, and I see that Hardy has been updated to that release of Wine.

The other problem (aka "Opening a new source-file window and moving it. Also resizing an existing window" or "Problem (1)") is still present in 0.9.59 and can be "seen in action" via that wine-refresh.swf attachment.

I've been slowly going back through the previous releases of Wine and have landed on 0.9.53 as the LAST good Wine release that does not exhibit "Problem (1)". Moving to 0.9.54 brings the problem back again.

[Scott Ritchie (scottritchie)]

If you want to be really helpful, you could run a regression test: http://wiki.winehq.org/RegressionTesting

[Spiceisland (g-w-hudspith)]

Ah! That's what you meant by a "proper regression test" (see https://bugs.edge.launchpad.net/ubuntu/+source/wine/+bug/208853/comments/7) !

Right, I'll get onto it this week. It may take a few days (testing for the absense of a bug ...).

In the meantime, I can confirm that this has NOT been fixed in the latest 0.9.60 releases :-(

[Spiceisland (g-w-hudspith)]

STILL doing the regression test (sigh!). Down now to four deltas remaining, so not long to go, hopefully.

In the meantime, I can confirm that this has NOT been fixed in the latest 0.9.61 release.

[Spiceisland (g-w-hudspith)]

Phew. Regression test completed!

# git bisect good
390ae9cc2845fe002bc2e68c14d104d927af68b1 is first bad commit
commit 390ae9cc2845fe002bc2e68c14d104d927af68b1
Author: Alexandre Julliard <email address hidden>
Date: Tue Jan 22 10:16:19 2008 +0100

    winex11.drv: Fix handling of strange window sizes in CreateWindow, with tests.

:040000 040000 7f4af3fece218b6b14a34926975259a14a4e4cc7 42ed599dea2db32f69df6b10a7748456570fddc2 M dlls

[Scott Ritchie (scottritchie)]

Wow, thank you.

[Spiceisland (g-w-hudspith)]

FYI - problem still exists in v1.0rc2

[Bruce Webber (brucewebber)]

I was seeing a similar problem running Picture Window Pro 3.0 under Wine on Ubuntu Hardy, and I just updated Wine via the package manager to version wine-1.0. I'm happy to report that the problem is no longer occurring in Picture Window.

Thanks!

[Spiceisland (g-w-hudspith)]

Thanks for caring, Bruce!

Sadly, I still encounter this problem when using Wine v1.0 :-(

I've switched over to the winehq.com ubuntu repository, in the vain hope that one of the Wine developers will pick on this ticket and fix it ...

At the moment, having taken the effort to use git to narrow down to the code delta which broke things, I have "re-wound" to the delta beforehand and have compiled/installed/stuck with that, working, version.

Maybe Source Insight will migrate to .NET and I can then run the excellent product under Mono under Linux :-)

[Andre_H (nerv-dawncrow)]

cant confirm this bug in wine 1.1.11
Source Insight 3.50.0054 (Trial)
Ubuntu 8.10 64-Bit

[Austin English (austinenglish)]

Scott, can you retest?

[Scott Ritchie (scottritchie)]

Think Graham is the one who should retest, I don't have it ;)

[Spiceisland (g-w-hudspith)]

Created an attachment (id=18516)
Nice hmtl file to play the (also attached) .swf file

[Spiceisland (g-w-hudspith)]

Created an attachment (id=18517)
Nice swf file showing my reproducing the problem

[Spiceisland (g-w-hudspith)]

Well, I can still reproduce the problem with Wine 1.1.12 using Source Insight 3.50.0063 under Ubuntu 8.10.

I've attached two files. One is a .swf showing me reproducing the problem. The other is an html file that replay the .swf in a browser. Although I can now download the .swf I've just attached, I can't find an easy way to re-download the attached .html as .html, so I'll leave that as an exercise to the developers who use this lovely bug reporting system :-)

Anyway, the steps followed in reproducing the problem were:

* start up Source Insight

* open a source file (this project is for sqlite)

* maximise the source file

* open some more source files

* do an "About ... Wine" to get a nice pop-up for you

* close the source files in the reverse order I opened them

* observe the screen corruption :-(

As mentioned earlier on in this ticket. If I go back to a version I built from the git repository using the snapshot BEFORE the bad delta I have identified, the problem does not occur.

Need anything else, don't hesitate to ask!

[Spiceisland (g-w-hudspith)]

It's a shame that the developer identified as the delta-adder (i.e. Alexandre Julliard) is on the auto-exclude list for comments added to this ticket :-(

[Scott Ritchie (scottritchie)]

Upstream is reporting that they can't confirm this bug in the latest Wine.

Could you please test the Wine beta packages here: http://winehq.org/download/deb and tell me if they work? Thanks.

[spiceisland (graham-hudspith)]

Scott,

I've reproduced the problem against Wine 1.1.12 under Ubuntu 8.10 and added comments and attachments to the Wine bug report (http://bugs.winehq.org/show_bug.cgi?id=12283).

[Andre_H (nerv-dawncrow)]

OK, no i can confirm this bug in wine 1.1.11
Source Insight 3.50.0054 (Trial)
Ubuntu 8.10 64-Bit

Your really have to open at least 5 Files.

[Spiceisland (g-w-hudspith)]

Just to show I haven't forgotten about this, I can confirm that the problem still exists in v1.1.25 :-(

[mr.larch (bunglehead)]

Running wine-1.1.44-290-g7d3cb53 I can't say it doesn't refresh a window. Yes, there's a glitch with resizing child window - navigation listbox doesn't refresh properly in rare cases, but it's a really minor problem.

Scott, retest with current Wine please.

[Spiceisland (g-w-hudspith)]

Well, I can confirm that the problem still occurs with the latest Ubuntu development builds of Wine (thanks, Scott!).

This is with the latest Source Insight under Ubuntu 10.04.

I'll try and reproduce the problem again when I get into work, tomorrow, and provide some version numbers. And maybe another swf showing the problem.

When the problem occurs, the left-half of the screen is corrupted. I have to close all open source-editing sub-windows (without actually leaving Source Insight itself) for the screen corruption to go away. I can then start opening source files again.

As mentioned earlier in the ticket, I had followed Wine's procedures for isolating the code-repository changes where the problem was reproduced and for a couple of years I ran my own build of a snapshot of Wine with these changes backed out.

However, with the introduction of 10.04, the old Wine binary would not run anymore, and I haven't found the time to rebuild it yet, so I'm running with Scott's Ubuntu 10.04 development build and putting up with the frequent screen corruptions for now.

Sigh.

[Spiceisland (g-w-hudspith)]

Version of Source Insight now at 3.50.0064

Version of Wine now at 1.1.44-0ubuntu1~lucidppa1

Using the method I documented in comment #16, I can still provoke the screen corruption.

De-maximising the individual source-file sub-windows has no effect, the corruption continues in the de-maximised sub-window. Re-maximising the sub-window similarily has no effect.

However, iconifying the complete Wine+SourceInsight window and de-iconifying it DOES clear the screen corruption, which is nice.

[Spiceisland (g-w-hudspith)]

Created an attachment (id=28080)
Example of the screen corruption

[Alexandre Julliard (julliard)]

Please test if d815e582cf327dca33cf84c3cc27701c2eef98ba makes any difference.

[Andre_H (nerv-dawncrow)]

As far as i can tell it looks a bit better

[Spiceisland (g-w-hudspith)]

Dunno which build "d815e582cf327dca33cf84c3cc27701c2eef98ba" has appeared in (or, even, if it has at all), but the problem seems just as bad in wine-1.2-rc5 ...

[rusivi2 (rusivi2-deactivatedaccount)]

Does this issue occur in newest WINE?

[rusivi2 (rusivi2-deactivatedaccount)]

Thank you for reporting this bug.

Does this issue occur in newest WINE?

[Spiceisland (g-w-hudspith)]

Yep, problem still there under Ubuntu 10.04 with Wine 1.2-1ubuntu1~lucidppa1

[Spiceisland (g-w-hudspith)]

Yep, problem still there under Ubuntu 10.04 with Wine 1.2-1ubuntu1~lucidppa1

[rusivi2 (rusivi2-deactivatedaccount)]

In Maverick Meerkat, regarding Bug Description:
during install, did not do a backup.
Once install completed choose .NET only.

(1) could open and resize new and existing source file and move it no problem.
(2) Opened a new source-file windows moved it, minimized and maximized no problem.

Toshiba Satellite L305D-S5934 no second display attached.

System -> Preferences -> Appearance -> Visual Effects "Normal".

lsb_release -rd
Description: Ubuntu maverick (development branch)
Release: 10.10
name@name-laptop:/usr/local/src$ apt-cache policy wine1.3
wine1.3:
  Installed: 1.3.3-0ubuntu1~maverickppa1
  Candidate: 1.3.3-0ubuntu1~maverickppa1
  Version table:
 *** 1.3.3-0ubuntu1~maverickppa1 0
        500 http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu/ maverick/main i386 Packages
        100 /var/lib/dpkg/status

[Spiceisland (g-w-hudspith)]

rusivi1, thanks for taking an interest in this very old bug report.

Sadly, I'm stuck in Lucid until Maverick is released, so bear with me until the end of next month when I can test whether the problem really has been fixed. Also, I'm stuck on wine 1.2, dunno why lucidppa for wine has not moved to 1.3.3, but hey ho.

Could you please have a look at the bug report I raised at WineHQ (http://bugs.winehq.org/show_bug.cgi?id=12283#c16) and see if you can (not) reproduce the problem using the method detailed there?

P. S. I can see that you've already commented in that bug report (comment #27).

[Spiceisland (g-w-hudspith)]

rusivil - I've upgraded to 1.3.3-0ubuntu1~lucidppa1 (so, same version of wine as you, just for Lucid instead of Maverick) and, following the steps I detailed in http://bugs.winehq.org/show_bug.cgi?id=12283#c16, I can confirm that the problem still exists.

[Spiceisland (g-w-hudspith)]

rusivil - re-reading your comment again, I thought that I'd better add that I'm still using a second display screen and that my Visual Effects are set to "None".

[Spiceisland (g-w-hudspith)]

Well, I bit the bullet and installed-from-fresh Maverick beta following by 1.3.3-0ubuntu1~maverickppa1 followed by Source Insight.

The problem still occurs :-(

Using nvidia driver with a second display and visual effects set to "none".

[Jeremielapuree (jeremielapuree)]

Version v3.50.0058 is no more available. And in the new version, no problem occurs. So, this bug could be closed as ABANDONED.

[Scott Ritchie (scottritchie)]

All right, I'm abandoning the bug then.

[Scott Ritchie (scottritchie)]

Upstream is unable to verify the bug anymore: the reported version is no longer available, and the newer versions don't show the bug in modern Wine. I'll mark this as fixed here.

[Austin English (austinenglish)]

Closing.