user-interface: unclear which background image is selected

[Sam_]

Due to investigating bug 918934 found when having identical images there is no indication which one is selected. (screenshot)
Expected:
Highlight selected image.
Display complete path of image.
Would make it unnessecary of basically opening another application to find out.

Use-case.
Have two folders which content the identical image.
One in standard 'pictures' and one in a created custom folder e.g. 'images'.
Go to user-interface and try to select the preferred one from 'pictures-folder' in drop-down menu.

## In order to test which image is displayed in unity-greeter, I had to guess which one is the one in 'pictures', assumed the second one, since I've added it later and using the one from 'images' before, which didn't display in unity-greeter.
Anyway, two remember after a few weeks or more which one is the one in 'pictures' or in 'images' may make it necessary to find out by removing either one of them.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: gnome-control-center 1:3.2.2-2ubuntu5
ProcVersionSignature: Ubuntu 3.2.0-12.20-generic 3.2.2
Uname: Linux 3.2.0-12-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Sun Jan 29 15:12:10 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111129.1)
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_gnome-control-center:
 gnome-bluetooth 3.2.1-1ubuntu4
 indicator-datetime 0.3.1-0ubuntu5

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

[Sam_ (and-sam)]

I've just set new upstream url since my report was a dupe, for this I had to rm affects g-c-c and readd back, sorry, couldn't find how to do this better.

[Sebastien Bacher (seb128)]

you can click on the small ">" at the start of the "gnome-control-center" line and edit the bug number or just edit the watch in the bottom left corner of the page

[Sam_ (and-sam)]

Thank you Sebastien.

[Sam_ (and-sam)]

No change with an upgraded 12.04 to 14.04.
Both are installed and appearance UIs the same.
gnome-control-center 1:3.6.3-0ubuntu56.1
unity-control-center 14.04.3+14.04.20140604-

Terminal outputs from appearance.
:~$ gnome-control-center

(unity-control-center:10130): Gtk-CRITICAL **: gtk_radio_button_set_group: assertion '!g_slist_find (group, radio_button)' failed

(unity-control-center:10130): Gtk-CRITICAL **: gtk_radio_button_set_group: assertion '!g_slist_find (group, radio_button)' failed

(unity-control-center:10130): Gtk-CRITICAL **: gtk_radio_button_set_group: assertion '!g_slist_find (group, radio_button)' failed

(unity-control-center:10130): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
*** BUG ***
In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on '_pixman_log_error' to debug

:~$ unity-control-center

(unity-control-center:10038): Gtk-CRITICAL **: gtk_radio_button_set_group: assertion '!g_slist_find (group, radio_button)' failed

(unity-control-center:10038): Gtk-CRITICAL **: gtk_radio_button_set_group: assertion '!g_slist_find (group, radio_button)' failed

(unity-control-center:10038): Gtk-CRITICAL **: gtk_radio_button_set_group: assertion '!g_slist_find (group, radio_button)' failed

(unity-control-center:10038): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
*** BUG ***
In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on '_pixman_log_error' to debug

[Sebastien Bacher (seb128)]

The interface was rewritten since and the new one doesn't have that issue