After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 772888 - Size of VC console window is reset to invisibly small after restart with maximized meld window
Size of VC console window is reset to invisibly small after restart with maxi...
Status: RESOLVED OBSOLETE
Product: meld
Classification: Other
Component: version
git master
Other All
: Normal normal
: ---
Assigned To: meld-maint
meld-maint
Depends on:
Blocks:
 
 
Reported: 2016-10-13 20:11 UTC by Vasily Galkin
Modified: 2017-12-13 19:20 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Vasily Galkin 2016-10-13 20:11:19 UTC
Problem: after restarting maximized meld window several times the vc console "disappears".

Steps to reproduce:
Launch meld like "bin/meld ." in it own git checkout
Maximize meld window
Ensure that vc console window is visible (enable it in the menu, then drag the separator to the middle of the window height)
Close meld
Open meld like "bin/meld ." 
Close meld again
Open meld again like "bin/meld ." 

Result: console window is enabled in the menu, but is not visible. 
Really it present but has near-1-pixel height, so it requires dragging from the bottom of the window to make it visible.

The bug is quite strange, but reproduces both on debian with gtk3.20 and windows with gtk3.18.

Possibly it is related to the fact that I have both meld 3.17 master and meld 3.16 installed and runed, so they share some of gsettings data...

According to dconf-editor the value of vc-console-pane-position is saved correctly but is hugely increased in the moment of starting new meld instance. Also I'm not sure by now that bug doesn't affect meld 3.16, but it looks that it's behaviour has some differences.
Comment 1 Kai Willadsen 2016-10-15 21:12:24 UTC
So I can't reproduce this exact behaviour at all. I *can* reproduce some things that look vaguely related:

 * If I'm running with client-side decorations enabled (GTK_CSD=1) then the size for the pane stored in dconf *decreases* on startup.
 * On GTK+ 3.20, when maximised (and only then) the pane height *increases* every restart, by about 9% of the stored pane height. This is accompanied by a GTK+ allocation warning for a toolitem (i.e., nothing Meld-specific), which doesn't happen when not maximised and is thus very suspicious.

I've just pushed a change to master that seems to help the second case slightly. The pane should no longer shrink to an invisible height. In my testing it changed the increase behaviour so that instead of increasing by ~9% every invocation, it increased by one pixel.

Clearly none of this makes any sense, so I'd be keen for better reproductions. At this point, I strongly suspect that this is a GTK+ bug.
Comment 2 Vasily Galkin 2016-11-11 15:49:16 UTC
I compared behavior in current master and to a version just before 
a2695ec vcview.ui: Don't allow the console window to shrink to invisible

It definetly makes situation better on debian with gtk 3.22.

Before change the console disappears after restart, and after change restarting meld leads to resetting console position to some useful default size (splitted like 2:1). Formally not remembering position is a bug, but it is another problem and has much-much less effect on usability, so from a user point of view this bug can be closed.

(on windows platform problem disappears even with original version - it is not reliably reproduced).
Comment 3 GNOME Infrastructure Team 2017-12-13 19:20:26 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/meld/issues/115.