Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 84342

Summary:	gnome-terminal spews warnings
Product:	[Retired] Red Hat Linux	Reporter:	Chris Ricker <chris.ricker>
Component:	libgnomeui	Assignee:	Havoc Pennington <hp>
Status:	CLOSED RAWHIDE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	9	Keywords:	Triaged
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2003-10-17 21:35:09 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	79579, 100644

Description Chris Ricker 2003-02-14 17:58:35 UTC

[cricker@winsucks cricker]$ gnome-terminal 

(gnome-terminal:27344): GnomeUI-WARNING **: gnome_icon_entry_gnome_entry
deprecated, use changed signal!

(gnome-terminal:27344): GnomeUI-WARNING **: gnome_icon_entry_gnome_entry
deprecated, use changed signal!


This is with gnome-terminal-2.2.0-2 on a pre-beta5 system

Comment 1 Havoc Pennington 2003-02-18 19:54:03 UTC

The bug here is in libgnomeui/glade/glade-gnome.c

Comment 2 Elliot Lee 2003-02-21 20:41:52 UTC

So glade-gnome.c is using deprecated routines because the person who deprecated
the routines hadn't thought some of the side effects through. They wrote "this
is deprecated in favour of the above" (gnome-icon-entry.h) to indicate that
people should use the gnome_icon_entry_* routines instead of retrieving the
GnomeEntry and calling the gnome_entry on it. The problem is that there is no
gnome_icon_entry_ do what glade-gnome.c wants to do.

Either glade-gnome.c needs to be fixed to not export the features of
GnomeIconEntry that require accessing the contained GnomeEntry, or
gnome-icon-entry needs to provide wrappers for all the GnomeEntry features, or
gnome-icon-entry needs to stop spewing warnings (and be made non-deprecated).
The latter is the least intrusive.

Comment 3 Havoc Pennington 2003-02-21 20:45:47 UTC

My preferred fix for this release would be to just remove the warning.

Comment 4 Chris Ricker 2003-10-17 21:35:09 UTC

I don't see this in severn