Bug 916996 - Folder selection drop-downs are blank
Summary: Folder selection drop-downs are blank
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gtk2
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-01 11:50 UTC by Theodore Lee
Modified: 2013-05-28 01:03 UTC (History)
2 users (show)

Fixed In Version: gtk2-2.24.18-1.fc18
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-05-28 01:03:31 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 691040 0 None None None Never

Description Theodore Lee 2013-03-01 11:50:10 UTC
Description of problem:
The drop-down folder selection box in gtk2 applications shows up blank. Using it to select a folder will result in it correctly displaying the selected folder, but once the application quits and is started again, it once again shows up blank.

Version-Release number of selected component (if applicable):
gtk2-2.24.16-1.fc18.x86_64

How reproducible:
Consistently reproducible with Deluge and Banshee (and probably other applications).

Steps to Reproduce:
1. Start deluge-gtk.
2. Go to Edit > Preferences.
3. Look at the Folders section under the Downloads category.
  
Actual results:
The folder selection drop-downs appear blank.

Expected results:
The folder selection drop-downs should display the currently selected folders.

Additional info:
This appears to be a regression in gtk2-2.24.16-1, as it is not reproducible with gtk2-2.24.13-1.

I am unsure if this bug has any effects beyond the visual glitches. Initially I believed it did not, but attempting to change download folders in Deluge does not appear to work. However, I'm unfamiliar with Deluge's config file structure (which I was using to check the actual selected folders), so I may just be missing something here.

This bug is also reproducible when selecting library locations in Banshee's preferences. With Banshee, it is not necessary to quit the application to blank the selection drop-downs again after picking a folder, simply exiting the preferences dialogue and opening it again is sufficient.

Note that Banshee is currently unusable due to a nasty bug involving gconf, dbus, and threading. In order to actually start Banshee and reproduce the bug there, a custom GConf2 build is probably needed. As both test machines I reproduced this bug on were running the aforementioned custom GConf2 build, I initially thought that might be the problem. However, I have since reproduced the issue using GConf2-3.2.5-3.fc18 from the repos.

For more information on the custom GConf2 build see:
https://bugzilla.redhat.com/show_bug.cgi?id=867133#c22

Comment 1 Michael Cronenworth 2013-03-01 13:41:35 UTC
It also effects Firefox if you print to a file. "Save in folder:" does not have a folder selected.

Comment 2 Michael Cronenworth 2013-03-06 16:52:46 UTC
The upstream bug now has a proposed patch to fix this.

https://bugzilla.gnome.org/show_bug.cgi?id=691040#c20

Comment 3 Fedora Update System 2013-05-26 00:08:11 UTC
gtk2-2.24.18-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/gtk2-2.24.18-1.fc18

Comment 4 Fedora Update System 2013-05-27 00:32:55 UTC
Package gtk2-2.24.18-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing gtk2-2.24.18-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-9336/gtk2-2.24.18-1.fc18
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2013-05-28 01:03:31 UTC
gtk2-2.24.18-1.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.