maemo.org Bugzilla – Bug 6494
Can't change desktop Background
Last modified: 2010-03-15 20:54:11 UTC
You need to
before you can comment on or make changes to this bug.
(Settings > General > About product)
EXACT STEPS LEADING TO PROBLEM:
(Explain in detail what you do (e.g. tap on OK) and what you see (e.g. message
Connection Failed appears))
1. Click on area of homescreen that is empty so that Settings (spanner) icon
appears in Status bar.
2. Click on settings icon and then Change background
3. Attempt to change background
List of Themes comes up then browser for images folder then choose image.
Homescreen refreshes with some widget loss (so far Ovi Widget disappears).
Change Background option does nothing UNLESS USB CABLE IS CONNECTED TO DEVICE.
(always unless USB cable is connected to Device & PC)
EXTRA SOFTWARE INSTALLED:
This seems to be affecting some people & not others.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:188.8.131.52)
Gecko/20091102 Firefox/3.5.5 (.NET CLR 3.5.30729)
Here's what I''ve found out.
This only occurs when you add a new .desktop file to the .images folder.
When I don't add a .desktop file to the .images file & add just the images, I
can pick the images up fine but not the image set.
Critical bug as desktop background changes seem not to work and this is an
integral part of the marketing of the device.
We are working on this.
(In reply to comment #2)
> We are working on this.
Urho, do you know an internal ID for this to set in the Alias field here
The image files in the .desktop file need to be absolute paths currently
(without the upcoming fix).
(In reply to comment #3)
> Urho, do you know an internal ID for this to set in the Alias field here
(In reply to comment #4)
> The image files in the .desktop file need to be absolute paths currently
> (without the upcoming fix).
And they should not contain trailing spaces.
This has been fixed in package
which is part of the internal build version
(Note: 2009 is the year, and the number after is the week.)
A future public update released with the year/week later than this internal
build version will include the fix. (This is not always already the next public
Please verify that this new version fixes the bug by marking this bug report as
VERIFIED after the public update has been released and if you have some time.
To answer popular followup questions:
* Nokia does not announce release dates of public updates in advance.
* There is currently no access to these internal, non-public build versions.
A Brainstorm proposal to change this exists at
*** Bug 7538 has been marked as a duplicate of this bug. ***
*** Bug 8274 has been marked as a duplicate of this bug. ***
Setting explicit PR1.2 milestone (so it's clearer in which public release the
fix will be available to users).
Sorry for the bugmail noise (you can filter on this message).