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 607775 - canvas not displayed on startup
canvas not displayed on startup
Status: RESOLVED FIXED
Product: dasher
Classification: Applications
Component: gtk
unspecified
Other Linux
: Urgent critical
: ---
Assigned To: Patrick Welche
Patrick Welche
: 617998 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2010-01-22 15:30 UTC by Patrick Welche
Modified: 2010-05-07 13:23 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
fix (1.50 KB, patch)
2010-01-27 17:14 UTC, Patrick Welche
none Details | Review

Description Patrick Welche 2010-01-22 15:30:42 UTC
Normally, when you start dasher, you see a toolbar, text box, and a canvas with an alphabet and colourful rectangles. With gtk 2.18, you see a default grey area where the canvas should be.

If you configure dasher --without-cairo, the canvas is correctly drawn on startup using gdk instead of cairo. The only file which is affected by WITH_CAIRO is

http://git.gnome.org/browse/dasher/tree/Src/Gtk2/Canvas.cpp
(and Canvas.h - CanvasExperimental isn't used by default)

So at this point, it seems that
- events are handled correctly otherwise the gdk version wouldn't work
- must be a cairo problem

But now for the surprise.

To repeat:
grab a copy of dasher e.g.,
wget http://www.inference.phy.cam.ac.uk/prlw1/dasher/dasher-cairo.tar.bz2
tar xjvf dasher-cairo.tar.bz2
cd dasher-4.10.1
./configure --without-gnome --disable-a11y --disable-nls
(to minimise the number of dependencies (toupper(a11y) = A11Y))
make
Src/dasher

If you see a grey square instead of the alphabet in colourful boxes, you see the bug.

So, the surprise is that I don't see the bug on:
- ubuntu 8.04.3 i686 with gtk 2.12.9, cairo 1.6.0, glib 2.16.6
- ubuntu 9.04 x86_64 with gtk 2.16.1, cairo 1.8.6, glib 2.20.1
- NetBSD-5.99.23/amd64 with gtk 2.16.6, cairo 1.8.8, glib 2.20.5

I do see the bug on:
- ubuntu 9.10 i686 with gtk 2.18.3, cairo 1.8.8, glib 2.22.3
- NetBSD-5.99.23/i386 with gtk 2.18.5, cairo 1.8.8, glib 2.22.3

So, it doesn't seem to be a cairo problem, as NetBSD/amd64 works with cairo 1.8.8.

It looks like a gtk 2.18 vs 2.16 problem (or glib?!) - so what changed?
Comment 1 Patrick Welche 2010-01-25 19:24:22 UTC
Upgrading to NetBSD-5.99.24/i386 with gtk 2.18.6, cairo 1.8.8, glib 2.22.4 didn't help.
Comment 2 Patrick Welche 2010-01-27 17:14:53 UTC
Created attachment 152432 [details] [review]
fix

Seems to fix it - will check on ubuntu 9.10 soon
Comment 3 Patrick Welche 2010-02-04 18:03:31 UTC
Fixed with http://git.gnome.org/browse/dasher/commit/?id=3c71ead76d5650868eead6576a56baf7c5be95d0

Tested on ubuntu 9.10 (as well as NetBSD)
Comment 4 Patrick Welche 2010-05-07 13:23:57 UTC
*** Bug 617998 has been marked as a duplicate of this bug. ***