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 615394 - Does not compile with -DGSEAL_ENABLE
Does not compile with -DGSEAL_ENABLE
Status: RESOLVED FIXED
Product: deskbar-applet
Classification: Deprecated
Component: general
2.30.x
Other Linux
: Normal normal
: ---
Assigned To: Deskbar Applet Maintainer(s)
Deskbar Applet Maintainer(s)
Depends on:
Blocks: 585391
 
 
Reported: 2010-04-10 20:27 UTC by André Klapper
Modified: 2010-04-16 13:31 UTC
See Also:
GNOME target: ---
GNOME version: 2.29/2.30



Description André Klapper 2010-04-10 20:27:40 UTC
This module does not build with -DGSEAL_ENABLE.
See http://live.gnome.org/GnomeGoals/UseGseal .

Note that maybe this report cannot be fixed yet, as GTK+ still misses some accessor functions (see bug 588389, bug 597610) needed for sealing.
Also see http://live.gnome.org/GTK%2B/3.0/PendingSealings for current status.
For Epiphany see https://bugzilla.gnome.org/show_bug.cgi?id=595791 .

The jhbuild output posted here of course only lists the very first error when trying to compile.

make[5]: Entering directory `/home/andre/svn-gnome/deskbar-applet/deskbar/ui/iconentry'
  CC     _iconentrymodule.lo
  CC     ephy-icon-entry.lo
ephy-icon-entry.c: In function ‘ephy_icon_entry_get_borders’:
ephy-icon-entry.c:68: error: ‘GtkWidget’ has no member named ‘style’
ephy-icon-entry.c:75: error: ‘GtkWidget’ has no member named ‘style’
ephy-icon-entry.c:76: error: ‘GtkWidget’ has no member named ‘style’
ephy-icon-entry.c: In function ‘ephy_icon_entry_paint’:
ephy-icon-entry.c:99: error: ‘GtkWidget’ has no member named ‘window’
ephy-icon-entry.c:101: error: ‘GtkObject’ has no member named ‘flags’
ephy-icon-entry.c:109: error: ‘GtkWidget’ has no member named ‘style’
ephy-icon-entry.c:109: error: ‘GtkWidget’ has no member named ‘window’
ephy-icon-entry.c:110: error: ‘GtkWidget’ has no member named ‘state’
ephy-icon-entry.c:115: error: ‘GtkWidget’ has no member named ‘style’
ephy-icon-entry.c:115: error: ‘GtkWidget’ has no member named ‘window’
ephy-icon-entry.c:120: error: ‘GtkObject’ has no member named ‘flags’
ephy-icon-entry.c:127: error: ‘GtkWidget’ has no member named ‘style’
ephy-icon-entry.c:127: error: ‘GtkWidget’ has no member named ‘window’
ephy-icon-entry.c:128: error: ‘GtkWidget’ has no member named ‘state’
ephy-icon-entry.c: In function ‘ephy_icon_entry_init’:
ephy-icon-entry.c:145: error: ‘GtkObject’ has no member named ‘flags’
ephy-icon-entry.c: In function ‘ephy_icon_entry_realize’:
ephy-icon-entry.c:172: error: ‘GtkObject’ has no member named ‘flags’
ephy-icon-entry.c:174: error: ‘GtkContainer’ has no member named ‘border_width’
ephy-icon-entry.c:176: error: ‘GtkWidget’ has no member named ‘allocation’
ephy-icon-entry.c:177: error: ‘GtkWidget’ has no member named ‘allocation’
ephy-icon-entry.c:178: error: ‘GtkWidget’ has no member named ‘allocation’
ephy-icon-entry.c:179: error: ‘GtkWidget’ has no member named ‘allocation’
ephy-icon-entry.c:189: error: ‘GtkWidget’ has no member named ‘window’
ephy-icon-entry.c:191: error: ‘GtkWidget’ has no member named ‘window’
ephy-icon-entry.c:193: error: ‘GtkWidget’ has no member named ‘style’
ephy-icon-entry.c:193: error: ‘GtkWidget’ has no member named ‘style’
ephy-icon-entry.c:193: error: ‘GtkWidget’ has no member named ‘window’
ephy-icon-entry.c:195: error: ‘GtkWidget’ has no member named ‘style’
ephy-icon-entry.c:195: error: ‘GtkWidget’ has no member named ‘window’
ephy-icon-entry.c: In function ‘ephy_icon_entry_size_request’:
ephy-icon-entry.c:207: error: ‘GtkContainer’ has no member named ‘border_width’
ephy-icon-entry.c:212: error: ‘GtkBin’ has no member named ‘child’
ephy-icon-entry.c:216: error: ‘GtkBin’ has no member named ‘child’
ephy-icon-entry.c: In function ‘ephy_icon_entry_size_allocate’:
ephy-icon-entry.c:236: error: ‘GtkWidget’ has no member named ‘allocation’
ephy-icon-entry.c:240: error: ‘GtkObject’ has no member named ‘flags’
ephy-icon-entry.c:242: error: ‘GtkContainer’ has no member named ‘border_width’
ephy-icon-entry.c:243: error: ‘GtkContainer’ has no member named ‘border_width’
ephy-icon-entry.c:244: error: ‘GtkContainer’ has no member named ‘border_width’
ephy-icon-entry.c:244: error: ‘GtkContainer’ has no member named ‘border_width’
ephy-icon-entry.c:245: error: ‘GtkContainer’ has no member named ‘border_width’
ephy-icon-entry.c:245: error: ‘GtkContainer’ has no member named ‘border_width’
ephy-icon-entry.c:247: error: ‘GtkWidget’ has no member named ‘window’
ephy-icon-entry.c:256: error: ‘GtkContainer’ has no member named ‘border_width’
ephy-icon-entry.c:257: error: ‘GtkContainer’ has no member named ‘border_width’
ephy-icon-entry.c:258: error: ‘GtkWidget’ has no member named ‘allocation’
ephy-icon-entry.c:259: error: ‘GtkContainer’ has no member named ‘border_width’
ephy-icon-entry.c:259: error: ‘GtkContainer’ has no member named ‘border_width’
ephy-icon-entry.c:260: error: ‘GtkContainer’ has no member named ‘border_width’
ephy-icon-entry.c:260: error: ‘GtkContainer’ has no member named ‘border_width’
ephy-icon-entry.c:270: error: ‘GtkBin’ has no member named ‘child’
ephy-icon-entry.c: In function ‘ephy_icon_entry_expose’:
ephy-icon-entry.c:277: error: ‘GtkObject’ has no member named ‘flags’
ephy-icon-entry.c:277: error: ‘GtkObject’ has no member named ‘flags’
ephy-icon-entry.c:278: error: ‘GtkWidget’ has no member named ‘window’
make[5]: *** [ephy-icon-entry.lo] Error 1
make[5]: Leaving directory `/home/andre/svn-gnome/deskbar-applet/deskbar/ui/iconentry'
Comment 1 Stéphane Maniaci 2010-04-13 09:44:24 UTC
Tried to do so in #615555. Why are there two bugs reports actually ?
Comment 2 André Klapper 2010-04-13 10:00:41 UTC
Because deprecated gtk symbols and sealing is not necessarily the same issue, but it can happen that one codefix fixes both issues.
Comment 3 Sebastian Pölsterl 2010-04-16 13:22:56 UTC
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.
Comment 4 André Klapper 2010-04-16 13:31:12 UTC
Sebastian, thanks a lot for the quick review!