#726 setting wallpaper to previously used file doesn't update

1.2
closed-fixed
pcmanfm (122)
6
2014-05-01
2013-05-18
Anonymous
No

If I set the wallpaper (either from the GUI or the command-line) to /path/to/file.png, and then I modify that image, and manually set the wallpaper again to the same file, the background fails to update.

Even if I change it to some /path/to/other/image.png, or remove the wallpaper (setting it to a color), and then change it bck to /path/to/file.png (after it has been changed), it reverts to the former image, rather than updating it with the new one.

Discussion

  • Lonely Stranger

    Lonely Stranger - 2013-05-18
    • assigned_to: nobody --> lstranger
    • priority: 5 --> 6
    • milestone: --> 1.2
     
  • Lonely Stranger

    Lonely Stranger - 2013-12-25
    • status: open --> closed-fixed
     
  • Lonely Stranger

    Lonely Stranger - 2013-12-25

    We hope this issue is completely fixed in the Git repository recently.
    Check it out when it's possible for you and if the bug still exists then reopen the report, please.
    Thank you very much.

     
  • Mr. Shady

    Mr. Shady - 2014-02-28

    I noticed a related problem. I wanted to update the wallpaper periodically with a webcam image and noticed that re-using the file name did not work. I therefor saved each image with a unique name to get the expected screen updates.

    However I have noticed that pcmanfm appears to allocate x-windows resources, but never releases them, for each image. Over time the Xorg process grows until memory is exhausted and something crashes.

    Killing and restarting pcmanfm releases all the x-windows memory.

    It would seem to be a related problem which this fix might also have addressed.

    I am using:

    ubuntu 13.04
    pcmanfm 1.1.0-0ubuntu2
    lxde 0.5.0-4ubuntu4

    command: pcmanfm --set-wallpaper=...ever-changing.jpg --wallpaper-mode=fit

    Thanks

     
    Last edit: Mr. Shady 2014-02-28
  • Lonely Stranger

    Lonely Stranger - 2014-05-01

    I hope that memory exhausting issue is completely fixed in the GIT sources now. Check it when possible. Thank you very much.

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks