As it is RHEL-6.5-candidate, change to version to 6.5

(In reply to CongDong from comment #0)
> 
> Actual results:
> step 2:

> (virt-viewer:3883): virt-viewer-DEBUG: Guest rhel6.3 has a spice display
> virt-viewer: symbol lookup error: /usr/lib64/libspice-client-glib-2.0.so.8:
> undefined symbol: g_proxy_get_type
> 

This symbol comes with the glib2 2.26 rebase, you need  https://brewweb.devel.redhat.com/buildinfo?buildID=279312 for example.
It would be worth explicitly requiring this version in the spice-gtk build.

(In reply to CongDong from comment #0)
> 
> Step 3:
> virt-viewer: symbol lookup error: virt-viewer: undefined symbol:
> gtk_widget_get_mapped
> 

Similarly to the previous comment, you need to get the rebased 6.5 gtk2 package to avoid this issue, for example https://brewweb.devel.redhat.com/buildinfo?buildID=277007
And virt-viewer should get a require for a new enough gtk2 version to avoid such issues.

I am not sure we need to explicitely bump the requirement in the spec. Those bugs quite clearly indicate that the update or the compose is not in sync with the build environment. It's not really the spec fault.

this is a distro/release error, and the problem is solved by a correct update, so lower severity/blocker.

I can reproduce this bug with virt-viewer-0.5.6-1.el6.x86_64.
Steps:
As the steps in description.

result:
# virt-viewer test
(virt-viewer:26240): virt-viewer-DEBUG: Couldn't load configuration: File is empty
virt-viewer: symbol lookup error: virt-viewer: undefined symbol: g_object_bind_property



Verify:
I install the new virt-viewer, version:0.5.6-3.el6

Steps:
# virt-viewer test

result:
# virt-viewer test
(virt-viewer:26345): virt-viewer-DEBUG: Couldn't load configuration: File is empty
virt-viewer: symbol lookup error: virt-viewer: undefined symbol: g_object_bind_property

As the result, I think the problem is still there, so change to ASSIGNED.
The steps is right? Or I should update the gtk2 and glib2 manually.

Ah, the change was done in the BuildRequires while what we need is Requires with explicit versioning, something like:

diff --git a/virt-viewer.spec b/virt-viewer.spec
index 0da6939..e0b1b7b 100644
--- a/virt-viewer.spec
+++ b/virt-viewer.spec
@@ -78,10 +78,12 @@ BuildRequires: gettext-devel
 BuildRequires: libtool
 %endif

+Requires: glib2 >= 2.26
 %if %{with_gtk3}
 BuildRequires: gtk3-devel >= 3.0.0
 %else
 BuildRequires: gtk2-devel >= 2.20
+Requires: gtk2 >= 2.20
 %endif
 BuildRequires: libvirt-devel >= 0.9.7
 BuildRequires: libxml2-devel

(In reply to Christophe Fergeau from comment #10)
> Ah, the change was done in the BuildRequires while what we need is Requires
> with explicit versioning, something like:
> 
> diff --git a/virt-viewer.spec b/virt-viewer.spec
> index 0da6939..e0b1b7b 100644
> --- a/virt-viewer.spec
> +++ b/virt-viewer.spec
> @@ -78,10 +78,12 @@ BuildRequires: gettext-devel
>  BuildRequires: libtool
>  %endif
> 
> +Requires: glib2 >= 2.26
>  %if %{with_gtk3}
>  BuildRequires: gtk3-devel >= 3.0.0
>  %else
>  BuildRequires: gtk2-devel >= 2.20
> +Requires: gtk2 >= 2.20
>  %endif
>  BuildRequires: libvirt-devel >= 0.9.7
>  BuildRequires: libxml2-devel


So I think virt-viewer should popup a message like:

Requires: gtk2 >= 2.20

not:

(virt-viewer:26345): virt-viewer-DEBUG: Couldn't load configuration: File is empty
virt-viewer: symbol lookup error: virt-viewer: undefined symbol: g_object_bind_property

Should be good with latest build

I tried with the virt-viewer-0.5.6-5.el6.
If I didn't update the gtk2, the error message when I install virt-viewer is:

Error: Package: virt-viewer-0.5.6-6.el6.x86_64 (/virt-viewer-0.5.6-6.el6.x86_64)
           Requires: gtk2 >= 2.20
           Installed: gtk2-2.18.9-12.el6.x86_64 (@anaconda-RedHatEnterpriseLinux-201301301459.x86_64/6.4)
               gtk2 = 2.18.9-12.el6
Error: Package: virt-viewer-0.5.6-6.el6.x86_64 (/virt-viewer-0.5.6-6.el6.x86_64)
           Requires: glib2 >= 2.26
           Installed: glib2-2.22.5-7.el6.x86_64 (@anaconda-RedHatEnterpriseLinux-201301301459.x86_64/6.4)
               glib2 = 2.22.5-7.el6
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

As the result, set VERIFIED

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1578.html