Bug 1316522 - [control-center] daylight-dependent GNOME wallpaper appears twice in thumbnail list
Summary: [control-center] daylight-dependent GNOME wallpaper appears twice in thumbnai...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: control-center
Version: 24
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Control Center Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-10 11:59 UTC by Joachim Frieben
Modified: 2017-03-10 20:16 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-23 11:49:57 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 771876 0 None None None 2016-09-23 11:49:57 UTC

Description Joachim Frieben 2016-03-10 11:59:25 UTC 
Description of problem:
When choosing a background theme in GNOME control-center, the daylight-pendent GNOME wallpaper labeled "Changes throughout the day" appears twice: once in the first row and again in the fourth row.

Version-Release number of selected component (if applicable):
control-center-3.19.91-1.fc24

How reproducible:
Always

Steps to Reproduce:
1. Open "Change Background..." from desktop context menu.
2. Click thumbnail of current background and open thumbnail list "Wallpapers".

Actual results:
Daylight-pendent GNOME wallpaper is shown twice in the thumbnail list.

Expected results:
Daylight-pendent GNOME wallpaper is shown once in the thumbnail list.

Additional info:
Issue also affects current Fedora 23 including package control-center-3.18.2-1.fc23.
Comment 1 Bastien Nocera 2016-09-23 11:49:57 UTC 
It's a problem upstream as well:
https://bugzilla.gnome.org/show_bug.cgi?id=771876
Comment 2 Joachim Frieben 2017-03-10 20:16:47 UTC 
This issue affects both of GNOME 3.22.2 and 3.23.91 and is likely to make its way into GNOME 3.24 final.
Note You need to log in before you can comment on or make changes to this bug.