background picture not cached

Bug #968898 reported by Sandra Farnedi
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-settings-daemon (Ubuntu)
Invalid
Low
Unassigned

Bug Description

gnome-settings-daemon:
  Installed: 3.4.0-0ubuntu2

I use a picture located in my destop directory to set my screen background. If I remove the picture from the desktop itself, I have no background at next reboot.
N.B. I did the same in ubuntu 11.10 environment and my background is kept on also if I remove the picture.

ProblemType: BugDistroRelease: Ubuntu 12.04
Package: casper 1.312
ProcVersionSignature: Ubuntu 3.2.0-20.33-generic-pae 3.2.12
Uname: Linux 3.2.0-20-generic-pae i686
ApportVersion: 1.95-0ubuntu1
Architecture: i386
CasperVersion: 1.312
Date: Fri Mar 30 08:20:30 2012LiveMediaBuild: Edubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120330)
ProcEnviron:
 TERM=xterm
 LANG=it_IT.UTF-8
 SHELL=/bin/bashSourcePackage: casper
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.casper.conf: 2012-03-30T10:19:36

Revision history for this message
Sandra Farnedi (sandra-farnedi-d) wrote :
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/968898

tags: added: iso-testing
Revision history for this message
Fabio Marconi (fabiomarconi) wrote : Re: screen background picture not cached (private triaging)

Great, this is reproducible on installed system too.
This mean that casper isn't the responsible of this issue, what do you think about ?
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

visibility: public → private
summary: - screen background picture not cached
+ screen background picture not cached (private triaging)
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

I confirm the issue

Changed in casper (Ubuntu):
status: New → Confirmed
Revision history for this message
Sandra Farnedi (sandra-farnedi-d) wrote :

The background picture is not saved into wallpapers pictures folder.

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Ok, it is /usr/share/backgrounds
To change the background we usually use System Settings - Appearance and in this way everythings works well, but we can also right-click on an image and select 'Use as background' (or something similar), in this case nautilus kick gnome-settings-daemon that copy the directory of the image and paste it in the background code but forget to copy the image into /usr/share/background too and to update the background pasted dir with the new generated /usr/share/background/copied+image.
Under this optic we cannot assign the bug to gnome-control-center that usually manage the settings for the background, but we have to blame gnome-settings-daemon.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

affects: casper (Ubuntu) → gnome-settings-daemon (Ubuntu)
summary: - screen background picture not cached (private triaging)
+ screen background picture not cached
summary: - screen background picture not cached
+ background picture not cached
visibility: private → public
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Hello Sebastien
I subscribe you for a better triage.
Thanks
Fabio
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

description: updated
Revision history for this message
Sandra Farnedi (sandra-farnedi-d) wrote :

The chosen picture background is saved in .cache/wallpaper directory but, at reboot time, the system looks for wallpapers in ~username/pictures folder and obviously doesn't find it out.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, that seems to not be a bug, the fact that g-s-d was copying local images before was a bug and creating issues (the image infos would look weird in the capplet, unity-greeter was not able to pick it because the image was made private without reason, etc) ... what is the usecase for that? if you use an image just put it somewhere and don't delete it while relying on "magic" to keep it for you, like you wouldn't delete files you are using an expect your work editor to still reload them by magic from its backup files (or only to avoid incident, not as a standard workflow)...

Changed in gnome-settings-daemon (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
Revision history for this message
Sandra Farnedi (sandra-farnedi-d) wrote :

Infact, if I do not delete the original picture the screen background is correctly kept, so I think we can consider the bug invalid.

Changed in gnome-settings-daemon (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.