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 779155 - user-accounts: Browse for more pictures doesn't work in 3.23.90
user-accounts: Browse for more pictures doesn't work in 3.23.90
Status: RESOLVED DUPLICATE of bug 779296
Product: gnome-control-center
Classification: Core
Component: User Accounts
3.23.x
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-02-24 00:32 UTC by Jeremy Bicha
Modified: 2017-02-28 02:13 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jeremy Bicha 2017-02-24 00:32:13 UTC
gnome-control-center 3.23.90
gtk+ 3.22.7
Ubuntu GNOME 17.04 Beta
Originally reported at https://launchpad.net/bugs/1667519

Open Settings
Click Users
Click the big picture then click Browse for more pictures
Try to select a picture
The Open button always stays inactive.
Comment 1 Ondrej Holy 2017-02-24 07:09:57 UTC
Thanks for your bug report, however, this is pretty weird. See Bug 778424 which seems like a duplicate of your issue, but the fix should be already part of 3.23.90. I can't reproduce this issue with 3.23.90 anymore...
Comment 2 Bastien Nocera 2017-02-24 11:04:41 UTC
You need both the latest gdk-pixbuf and the patch mentioned in bug 778424. Reopen if you indeed have both.

*** This bug has been marked as a duplicate of bug 778424 ***
Comment 3 Jeremy Bicha 2017-02-24 13:59:49 UTC
Reopening as requested.

This is with
gnome-control-center 3.23.90
gdk-pixbuf 2.36.5-1
gnome-desktop3 3.23.90-0ubuntu1

gnome-control-center 3.23.90 was built using that version of gdk-pixbuf and gnome-desktop3 too.

https://launchpad.net/ubuntu/+source/gnome-control-center/1:3.23.90-0ubuntu2
Comment 4 Jeremy Bicha 2017-02-28 02:13:20 UTC
This was a packaging bug.

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