Bug 131242 - Cannot add png||jpg desktop background using gnome-background-properties
Summary: Cannot add png||jpg desktop background using gnome-background-properties
Alias: None
Product: Fedora
Classification: Fedora
Component: control-center
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Jonathan Blandford
QA Contact: David Lawrence
Depends On:
Blocks: FC3Target
TreeView+ depends on / blocked
Reported: 2004-08-30 12:55 UTC by James Laska
Modified: 2013-09-02 05:59 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2004-09-01 13:59:32 UTC

Attachments (Terms of Use)

Description James Laska 2004-08-30 12:55:50 UTC
# TREE rawhide-20040830
# RPMS control-center-2.7.1-1

Steps to reproduce:
 1) right click on desktop and select "Change Desktop Background"
 2) select "Add Wallpaper"
 3) navigate to png or jpg and select that image

Actual Results:
 - The selected image does not show up in the above file display

Expected Results:
 - The selected image should appear in the background file display and
should be selected as the current background.

I should note that I can open up the image in epiphany and right click
"Set as background" and that works correctly.  I believe this bug is
related to bug#131113.  I can remove an image that is already in my
background list, and re-add it.  Shown below are the results of `file`
on the image that I removed/then added again (existing.jpg), and one
of many new images that won't add to the list (new.jpg).

(~/Desktop/Documents/Images)> file existing.jpg
existing.jpg: JPEG image data, EXIF standard 2.2

(~/Desktop/Documents/Images)> file new.jpg
new.jpg: JPEG image data, EXIF standard 2.2

I am attaching `strace` output from an attempt to add a background to
my list.

Comment 1 James Laska 2004-08-30 13:03:55 UTC
For a full strace (1.4M) of the above scenario (attempting to add a
new image "Big Sur Sunset.jpg") see ...


Comment 2 James Laska 2004-09-01 13:59:32 UTC
Closed not a bug ... adding the gamin package seems to have resolved
the issue.

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