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 613990 - GTK_WIDGET_IS_SENSITIVE deprecated in 2.19.7
GTK_WIDGET_IS_SENSITIVE deprecated in 2.19.7
Status: RESOLVED DUPLICATE of bug 612493
Product: nautilus-sendto
Classification: Applications
Component: general
unspecified
Other All
: Normal major
: ---
Assigned To: nautilus-sendto-maint
nautilus-sendto-maint
Depends on:
Blocks:
 
 
Reported: 2010-03-26 09:42 UTC by Halton Huo
Modified: 2010-06-08 17:35 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Halton Huo 2010-03-26 09:42:05 UTC 
On OpenSolaris and Ubuntu 10.04, the GTK version is updated to 2.19.7. According http://git.gnome.org/browse/gtk+/tree/gtk/gtkwidget.h#n301, GTK_WIDGET_IS_SENSITIVE seems be deprecated. This cause nautilus-sendto is not builtble on it.

/opt/SunStudioExpress/bin/cc -g -o nautilus-sendto nautilus-sendto-command.o  -L/lib ./.libs/libnstplugin.a -lgtk-x11-2.0 -lsecdb -ltsol -lgdk-x11-2.0 -latk-1.0 -lpangoft2-1.0 -lgdk_pixbuf-2.0 -lm -lpangocairo-1.0 -lgio-2.0 -lXext -lXrender -lXinerama -lXi -lXrandr -lXcursor -lXcomposite -lXdamage -lXfixes -lcairo -lX11 -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lpthread -lthread -lgconf-2 -lglib-2.0 -R/usr/lib -R/lib
Undefined                       first referenced
 symbol                             in file
GTK_WIDGET_IS_SENSITIVE             nautilus-sendto-command.o

Two ways to fix this issue:
1. Update GTK depend to 2.19.0 and make a code change.
2. Just remove $(DISABLE_DEPRECATED) in src/Makefile.am

Which way do you prefer?
Comment 1 Bastien Nocera 2010-06-08 17:35:26 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 612493 ***