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 725330 - GUI mostly broken after startup
GUI mostly broken after startup
Status: RESOLVED DUPLICATE of bug 706519
Product: gnome-sudoku
Classification: Applications
Component: general
3.8.x
Other Linux
: Normal critical
: ---
Assigned To: gnome-sudoku-maint
gnome-sudoku-maint
Depends on:
Blocks:
 
 
Reported: 2014-02-27 15:35 UTC by BenWiederhake.GitHub
Modified: 2014-02-28 03:22 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
GUI after startup ("New game" interface is barely visible) (10.14 KB, image/png)
2014-02-27 15:35 UTC, BenWiederhake.GitHub
Details
Scrolling down, the rest of the "new game" interface is visible and functional. Scrolling works only by mouse wheel. (11.33 KB, image/png)
2014-02-27 15:36 UTC, BenWiederhake.GitHub
Details
The rest of the game renders/displays as it should. (45.44 KB, image/png)
2014-02-27 15:37 UTC, BenWiederhake.GitHub
Details

Description BenWiederhake.GitHub 2014-02-27 15:35:56 UTC
Created attachment 270486 [details]
GUI after startup ("New game" interface is barely visible)

After a recent system update (Debian testing), I couldn't see most of the GUI anymore (erroneously making me believe that no sudokus are available, due to correlation with actually running out of them and an actual error message)

Eventually I noticed that the GUI actually still is "visible", just barely (see attachment), but actually usable.

From here on I'm just guessing, but because it happened after I updated my system (including certain gtk libs, see below), and I think gnome-sudoku is using gtk, I just assumed there was some kind of break/misuse/whatever concerning the part of gtk that's responsible for the scrolling area.

libgtk-3-0:amd64 3.8.6-1 -> 3.10.7-1
libgtk-3-bin:amd64 3.8.6-1 -> 3.10.7-1
libgtk-3-common:amd64 3.8.6-1 -> 3.10.7-1
Again, I'm only guessing (= "I'm not sure") whether this has to do anything with gtk.

Flagged as critical since it makes the game unplayable when the user doesn't realize the problem.

Custom workaround: Hover mouse over "New game" (part of the rectangle that is probably supposed to be the scrolling area), scroll down (using the mouse wheel), and click whatever you want. From here on, the interface looks and works as always.

Using Debian testing, gnome-sudoku 3.8.1 (the newest in the Debian testing repo), X (I mean: not knowingly wayland), Xfce, gtk 3.10.7-1 (unless I'm mistaking things)

Xfce provides the session-option to "load GNOME runtime environment on startup".
This bug is exhibited both when using that option and when not.
Comment 1 BenWiederhake.GitHub 2014-02-27 15:36:55 UTC
Created attachment 270487 [details]
Scrolling down, the rest of the "new game" interface is visible and functional. Scrolling works only by mouse wheel.
Comment 2 BenWiederhake.GitHub 2014-02-27 15:37:28 UTC
Created attachment 270488 [details]
The rest of the game renders/displays as it should.
Comment 3 Michael Catanzaro 2014-02-28 03:13:53 UTC
Can you please file a bug in Debian's bugtracker? Shipping GNOME 3.8 applications with GTK+ 3.10 is a bad idea due to a significant behavior change in GtkBox. Ideally Debian would upgrade to 3.10 (there are very few changes), but there's a patch in Bug #706519.

* The behavior of GtkBox::expand has been changed to never propagate
  up. Previously, this was happening inconsistently. If you want the
  expand to propagate, use the GtkWidget h/v expand properties.
  If you experience sizing problems with widgets in ported code,
  carefully check the expand and fill flags of your boxes.

*** This bug has been marked as a duplicate of bug 706519 ***
Comment 4 Michael Catanzaro 2014-02-28 03:22:43 UTC
Looking at [1], it seems Debian testing is half GNOME 3.10, half GNOME 3.8. Debian should seriously reconsider this version-mixing. The GtkBox::expand change has been an issue for so many GNOME apps that I've lost track. If an entire app isn't broken, a particular view or dialog may well be....

[1] https://packages.debian.org/jessie/gnome/