GnuCash
Contact   Instructions
Bug 796968 - Screen display gets corrupted in some circumstances when multiple windows stacked on top of each other
Summary: Screen display gets corrupted in some circumstances when multiple windows sta...
Status: RESOLVED OBSOLETE
Alias: None
Product: GnuCash
Classification: Unclassified
Component: Windows (show other bugs)
Version: 3.3
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: windows
QA Contact: windows
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-04 19:52 EST by Steve Lelievre
Modified: 2019-01-04 19:28 EST (History)
4 users (show)

See Also:


Attachments
Screenshot of problem (37.38 KB, image/png)
2018-12-04 19:52 EST, Steve Lelievre
no flags Details

Description Steve Lelievre 2018-12-04 19:52:40 EST
Created attachment 373073 [details]
Screenshot of problem

GnuCash 3.3 on Windows 10 Home (64 bit) on a Dell Inspiron.

I am getting a kind of display corruption when editing currency prices. I have the currency price database open, on top of the main GnuCash window, and am editing an individual currency so there is another little editor window on top of the price database window. The top window is displayed wrong - like parts of it are transparent so I see the information from the price database window behind it. When I move the mouse around, the parts that are affected change. Sometimes after I have changed a price value, the window grays but doesn't go away.

I have attached a partial screen shot showing the screen as I'm seeing it. Notice how the blue bar and some text from the database window behind is showing in the little edit window.

I am getting the same (or very similar) problem when I am importing transactions and want to change the account that GnuCash guesses a transaction should be assigned to. I have the importer window open, and also another window open on on top of it for editing the individual transaction. Parts of the importer window shows through.

I don't get problems like this in other applications, so I'm assuming my PC itself is set up OK...

I'm filing this as a Windows Port bug, because that's what I'm on, but I don't know for sure that the problem is in the Windows port. I checked the existing bug list but did not notice a match for this problem.
Comment 1 John Ralls 2018-12-11 17:02:33 EST
I can't reproduce this.
Comment 2 Steve Lelievre 2018-12-11 17:39:53 EST
(In reply to John Ralls from comment #1)
> I can't reproduce this.

Humm. I just tried the price editor and the transaction importer again on my system - and today I can't reproduce my problem either.

I hadn't realized that it is an intermittent problem (but then again I only use the price editor once or twice a year, and the I only use the transaction importer once a month).

My recollection from previous occasions is that the problem persists if I close and immediately reopen the application - but I can't say that for sure (and I don't think I've ever tried rebooting the PC as well).

Any thoughts on diagnostic measures, other than keeping an eye on it and trying to figure out what triggers it?
Comment 3 John Ralls 2018-12-11 19:01:05 EST
Not really. From the screen shot it looks more like parts of the dialog box failed to draw rather than a transparency setting got munged. I think it's got to be an upstream--either Gtk or Cairo--problem, but I have to be able to reproduce it before I can pass it up to them.
Comment 4 Steve Lelievre 2019-01-04 19:20:56 EST
Since I first reported it, I upgraded GnuCash the new release, 3.4. As well, various automatic Windows updates have come along too. 

I do not know if either change is a cure; however, I did not see the problem bug when I did my latest monthly accounts.

I think we might as well close this report, and I can re-open if the problem recurs. I would mark it closed myself, but am not sure what category to use.

I like the new release by the way, it seems to run a bit smoother and faster.
Comment 5 John Ralls 2019-01-04 19:28:03 EST
Gtk was blocked from updating, but Cairo probably did. I'll mark it obsolete because I we didn't do anything overt to change it.

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