Desktop icons keep rearranging whenever I refresh the desktop or boot the system












2















Desktop icons keep rearranging whenever I refresh the desktop or boot the system.

When I arrange the icons by moving them with the mouse and refresh it, it'd be undone and rearranged by name. What's the solution?

I use Ubuntu 16.04.

I think this is a bug. How should I report it?










share|improve this question

























  • If you right-click on an empty part of the desktop it will open a menu. One of the options is 'Sort Desktop icons by Name'. Is that ticked? Try ticking the other option 'Align Desktop icons'. Does that stop this behaviour?

    – pHeLiOn
    Jun 1 '16 at 2:04











  • @pHeLiOn I can't tick it. It's not tickable.

    – Milad
    Jun 1 '16 at 3:42











  • I'm using Ubuntu 16.04 with the default Unity desktop & it's not rearranging them on reboot for me. If I select the 'Sort Desktop icons by Name' then it behaves like yours, but I have to select it - it doesn't just do it automatically. Did you do anything like install another desktop (Gnome, XFCE, LXDE etc)? Having multiple desktops installed can sometimes mess with the behaviour. Not sure why it's rearranging your icons automatically but you could try sudo apt-get install --reinstall ubuntu-desktop and see if it behaves better after that?

    – pHeLiOn
    Jun 1 '16 at 4:31











  • @pHeLiOn I had this problem in Ubuntu 15 too. But it didn't happened all the time. Just randomly when I refreshed the desktop. Until in Ubuntu 16 that was OK at first but eventually it became worse. Now it happens every time that I refresh the desktop.

    – Milad
    Jun 1 '16 at 8:00











  • Did you upgrade to 16.04? I'm curious as to whether a fresh installation of 16.04 will have the same behaviour. i.e it's possible that some sort of bug occurred during your 15.04/15.10 installation and then it has carried forward into your upgraded version. It's not really getting to the root of your problem, but in my 16.04 installation the desktop doesn't rearrange them like that, so if you don't get a better answer/suggestion from someone else then it might be worth trying.

    – pHeLiOn
    Jun 1 '16 at 16:37
















2















Desktop icons keep rearranging whenever I refresh the desktop or boot the system.

When I arrange the icons by moving them with the mouse and refresh it, it'd be undone and rearranged by name. What's the solution?

I use Ubuntu 16.04.

I think this is a bug. How should I report it?










share|improve this question

























  • If you right-click on an empty part of the desktop it will open a menu. One of the options is 'Sort Desktop icons by Name'. Is that ticked? Try ticking the other option 'Align Desktop icons'. Does that stop this behaviour?

    – pHeLiOn
    Jun 1 '16 at 2:04











  • @pHeLiOn I can't tick it. It's not tickable.

    – Milad
    Jun 1 '16 at 3:42











  • I'm using Ubuntu 16.04 with the default Unity desktop & it's not rearranging them on reboot for me. If I select the 'Sort Desktop icons by Name' then it behaves like yours, but I have to select it - it doesn't just do it automatically. Did you do anything like install another desktop (Gnome, XFCE, LXDE etc)? Having multiple desktops installed can sometimes mess with the behaviour. Not sure why it's rearranging your icons automatically but you could try sudo apt-get install --reinstall ubuntu-desktop and see if it behaves better after that?

    – pHeLiOn
    Jun 1 '16 at 4:31











  • @pHeLiOn I had this problem in Ubuntu 15 too. But it didn't happened all the time. Just randomly when I refreshed the desktop. Until in Ubuntu 16 that was OK at first but eventually it became worse. Now it happens every time that I refresh the desktop.

    – Milad
    Jun 1 '16 at 8:00











  • Did you upgrade to 16.04? I'm curious as to whether a fresh installation of 16.04 will have the same behaviour. i.e it's possible that some sort of bug occurred during your 15.04/15.10 installation and then it has carried forward into your upgraded version. It's not really getting to the root of your problem, but in my 16.04 installation the desktop doesn't rearrange them like that, so if you don't get a better answer/suggestion from someone else then it might be worth trying.

    – pHeLiOn
    Jun 1 '16 at 16:37














2












2








2


1






Desktop icons keep rearranging whenever I refresh the desktop or boot the system.

When I arrange the icons by moving them with the mouse and refresh it, it'd be undone and rearranged by name. What's the solution?

I use Ubuntu 16.04.

I think this is a bug. How should I report it?










share|improve this question
















Desktop icons keep rearranging whenever I refresh the desktop or boot the system.

When I arrange the icons by moving them with the mouse and refresh it, it'd be undone and rearranged by name. What's the solution?

I use Ubuntu 16.04.

I think this is a bug. How should I report it?







unity nautilus icons desktop-environments






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jun 7 '16 at 13:00







Milad

















asked May 31 '16 at 17:19









MiladMilad

142312




142312













  • If you right-click on an empty part of the desktop it will open a menu. One of the options is 'Sort Desktop icons by Name'. Is that ticked? Try ticking the other option 'Align Desktop icons'. Does that stop this behaviour?

    – pHeLiOn
    Jun 1 '16 at 2:04











  • @pHeLiOn I can't tick it. It's not tickable.

    – Milad
    Jun 1 '16 at 3:42











  • I'm using Ubuntu 16.04 with the default Unity desktop & it's not rearranging them on reboot for me. If I select the 'Sort Desktop icons by Name' then it behaves like yours, but I have to select it - it doesn't just do it automatically. Did you do anything like install another desktop (Gnome, XFCE, LXDE etc)? Having multiple desktops installed can sometimes mess with the behaviour. Not sure why it's rearranging your icons automatically but you could try sudo apt-get install --reinstall ubuntu-desktop and see if it behaves better after that?

    – pHeLiOn
    Jun 1 '16 at 4:31











  • @pHeLiOn I had this problem in Ubuntu 15 too. But it didn't happened all the time. Just randomly when I refreshed the desktop. Until in Ubuntu 16 that was OK at first but eventually it became worse. Now it happens every time that I refresh the desktop.

    – Milad
    Jun 1 '16 at 8:00











  • Did you upgrade to 16.04? I'm curious as to whether a fresh installation of 16.04 will have the same behaviour. i.e it's possible that some sort of bug occurred during your 15.04/15.10 installation and then it has carried forward into your upgraded version. It's not really getting to the root of your problem, but in my 16.04 installation the desktop doesn't rearrange them like that, so if you don't get a better answer/suggestion from someone else then it might be worth trying.

    – pHeLiOn
    Jun 1 '16 at 16:37



















  • If you right-click on an empty part of the desktop it will open a menu. One of the options is 'Sort Desktop icons by Name'. Is that ticked? Try ticking the other option 'Align Desktop icons'. Does that stop this behaviour?

    – pHeLiOn
    Jun 1 '16 at 2:04











  • @pHeLiOn I can't tick it. It's not tickable.

    – Milad
    Jun 1 '16 at 3:42











  • I'm using Ubuntu 16.04 with the default Unity desktop & it's not rearranging them on reboot for me. If I select the 'Sort Desktop icons by Name' then it behaves like yours, but I have to select it - it doesn't just do it automatically. Did you do anything like install another desktop (Gnome, XFCE, LXDE etc)? Having multiple desktops installed can sometimes mess with the behaviour. Not sure why it's rearranging your icons automatically but you could try sudo apt-get install --reinstall ubuntu-desktop and see if it behaves better after that?

    – pHeLiOn
    Jun 1 '16 at 4:31











  • @pHeLiOn I had this problem in Ubuntu 15 too. But it didn't happened all the time. Just randomly when I refreshed the desktop. Until in Ubuntu 16 that was OK at first but eventually it became worse. Now it happens every time that I refresh the desktop.

    – Milad
    Jun 1 '16 at 8:00











  • Did you upgrade to 16.04? I'm curious as to whether a fresh installation of 16.04 will have the same behaviour. i.e it's possible that some sort of bug occurred during your 15.04/15.10 installation and then it has carried forward into your upgraded version. It's not really getting to the root of your problem, but in my 16.04 installation the desktop doesn't rearrange them like that, so if you don't get a better answer/suggestion from someone else then it might be worth trying.

    – pHeLiOn
    Jun 1 '16 at 16:37

















If you right-click on an empty part of the desktop it will open a menu. One of the options is 'Sort Desktop icons by Name'. Is that ticked? Try ticking the other option 'Align Desktop icons'. Does that stop this behaviour?

– pHeLiOn
Jun 1 '16 at 2:04





If you right-click on an empty part of the desktop it will open a menu. One of the options is 'Sort Desktop icons by Name'. Is that ticked? Try ticking the other option 'Align Desktop icons'. Does that stop this behaviour?

– pHeLiOn
Jun 1 '16 at 2:04













@pHeLiOn I can't tick it. It's not tickable.

– Milad
Jun 1 '16 at 3:42





@pHeLiOn I can't tick it. It's not tickable.

– Milad
Jun 1 '16 at 3:42













I'm using Ubuntu 16.04 with the default Unity desktop & it's not rearranging them on reboot for me. If I select the 'Sort Desktop icons by Name' then it behaves like yours, but I have to select it - it doesn't just do it automatically. Did you do anything like install another desktop (Gnome, XFCE, LXDE etc)? Having multiple desktops installed can sometimes mess with the behaviour. Not sure why it's rearranging your icons automatically but you could try sudo apt-get install --reinstall ubuntu-desktop and see if it behaves better after that?

– pHeLiOn
Jun 1 '16 at 4:31





I'm using Ubuntu 16.04 with the default Unity desktop & it's not rearranging them on reboot for me. If I select the 'Sort Desktop icons by Name' then it behaves like yours, but I have to select it - it doesn't just do it automatically. Did you do anything like install another desktop (Gnome, XFCE, LXDE etc)? Having multiple desktops installed can sometimes mess with the behaviour. Not sure why it's rearranging your icons automatically but you could try sudo apt-get install --reinstall ubuntu-desktop and see if it behaves better after that?

– pHeLiOn
Jun 1 '16 at 4:31













@pHeLiOn I had this problem in Ubuntu 15 too. But it didn't happened all the time. Just randomly when I refreshed the desktop. Until in Ubuntu 16 that was OK at first but eventually it became worse. Now it happens every time that I refresh the desktop.

– Milad
Jun 1 '16 at 8:00





@pHeLiOn I had this problem in Ubuntu 15 too. But it didn't happened all the time. Just randomly when I refreshed the desktop. Until in Ubuntu 16 that was OK at first but eventually it became worse. Now it happens every time that I refresh the desktop.

– Milad
Jun 1 '16 at 8:00













Did you upgrade to 16.04? I'm curious as to whether a fresh installation of 16.04 will have the same behaviour. i.e it's possible that some sort of bug occurred during your 15.04/15.10 installation and then it has carried forward into your upgraded version. It's not really getting to the root of your problem, but in my 16.04 installation the desktop doesn't rearrange them like that, so if you don't get a better answer/suggestion from someone else then it might be worth trying.

– pHeLiOn
Jun 1 '16 at 16:37





Did you upgrade to 16.04? I'm curious as to whether a fresh installation of 16.04 will have the same behaviour. i.e it's possible that some sort of bug occurred during your 15.04/15.10 installation and then it has carried forward into your upgraded version. It's not really getting to the root of your problem, but in my 16.04 installation the desktop doesn't rearrange them like that, so if you don't get a better answer/suggestion from someone else then it might be worth trying.

– pHeLiOn
Jun 1 '16 at 16:37










4 Answers
4






active

oldest

votes


















1














A better way might be:
Open a terminal from the desktop then enter the following commands:



cd ~/local/share/gvfs-metadata

sudo chown $USER home

chmod 755 home



This allows your desktop software to change/save the icon configuration.

(Thanks to the community for correcting spelling and syntax errors.)






share|improve this answer

































    0














    EDIT (August 30th, 2017):

    Before trying the solution below and if the other answers didn't work, try this:




    $ sudo chown -R (UserName) /home/(UserName)/.local/




    For some reason, I have had this issue again after updating Ubuntu 17.04, so I've considered and tried the other answers and they actually didn't work (not because they forgot the "." in "~/.local/..."(again, I'm using 17.04) but because changing the mode and ownership of "./local/share/gvfs-metadata/home" didn't work, most likely it wasn't the right file.) I put this here instead of editing their answer because it may be different on the earlier versions of Ubuntu, and unfortunately, I am not yet allowed to comment. I have decided to chown and chmod all of the "~/.config" directory to no avail, then, after considering the other answers and comments, I tried to chown and chmod the whole "~/.local" directory, testing the result after each step, and I noticed it worked immediately just as I chowned it. No chmod necessary. It could just be my weird setup, but try it anyway because if it works, you're not weakening your security or altering your whole home directory, and it'll fix whatever other configuration files are needed by the desktop client, if any. I hope this helps.
    ==END OF EDIT.==






    I did this,



    $ sudo chown -R (UserName) /home/(UserName)
    $ sudo chmod -R 766 /home/(UserName)


    The first command ensures that the mentioned username (in this case, you) owns all the files in the /home/(UserName) directory.

    The second command ensures you, the owner, have full permissions (read, write, execute) on those files, and everyone else has read and write, which allows the desktop program to write to the configuration file. It doesn't have to be 777, or 766 (read the edit at the bottom). It can be 666 if you want it that way, 766 just gives you execute permissions, just to make sure the configuration files can be overwritten and read.



    The reason this works is because the desktop program runs as whatever user you log in as, not root. If that user doesn't own the configuration files or have write access to them, then every time you refresh the desktop or reboot, because the old files couldn't be overwritten, it reloads the old configuration (like the desktop settings, location of the desktop icons, etc.). By running these commands, you give yourself ownership and complete control over those files, and because the desktop program runs as your user, it will also be able to overwrite, do what it needs to do with those files.



    Also these commands gives the user's home directory (/home/(UserName)) and all the subdirectories write/create privileges also, enabling the user and the desktop program to create those files should they not exist. If those files don't exist and aren't created, the desktop program will generate a new layout every time it is refreshed or restarted. These commands should ensure you full access to all the subdirectories and the desktop program should now be able to create these files and save your layout.



    Edit: When you use the chmod command, you don't have to make them world readable/writable/executable (777), infact, you really shouldn't unless you have to, especially if you have a multi-user machine. It was my mistake for originally suggesting 777, and therefore, I have edited my answer to read 766, not 777. You can use whatever you wish, but you only need to ensure you can write to and read any and all of your configuration files needed for the desktop program and any other software to work.



    Something to remember... Security and convenience (or functionality) usually don't mix.






    share|improve this answer


























    • Hello, It seems like your answer does not answer the question. Could you give more details why it would work

      – ankit7540
      Feb 21 '17 at 5:15






    • 1





      This worked for me because the desktop program runs as whatever user you log in as. If that user doesn't own the configuration file or have write access to it, then every time you refresh the desktop or reboot, because the old file couldn't be overwritten, it reloads the old configuration. By running those commands, you give yourself ownership and complete control over the file, and because the desktop program runs as your user, not root, it will also be able to overwrite, do what it needs to do with that file. And if I'm not mistaken, there's more than 1 config file, so this gets all of them.

      – Thomas Bodrey
      Feb 21 '17 at 5:33











    • Please elaborate your answer to include this information.

      – ankit7540
      Feb 21 '17 at 5:34






    • 1





      Also if it can't write to the directory and that file doesn't exist, you may notice a randomly generated desktop with all the icons reorganized, because there is no configuration file to load from... This was my issue because all my icons were moving around, all sorted in alphabetical order and such. Giving ownership and write privileges to your home directory and sub directories for your user ensures the desktop program can create that file and save your desktop. At least it worked for me anyways.

      – Thomas Bodrey
      Feb 21 '17 at 5:39






    • 2





      You just made every file and directory under /home/username world-writeable, world-readable and world-executable. Why? This is like using a tank to open your front door. While it will probably let you enter the house, it will also let anyone else come in and rearrange your furniture.

      – terdon
      May 18 '17 at 12:31



















    0














    For users who would prefer a GUI (graphical) way of dealing with the OP, this may be useful to you.



    Procedure: open Nautilus (Files) as root then change the file called ‘ home ‘ to be USER Read/Writable



    Launch Terminal => sudo nautilus
    Nautilus ( Files ) > Home > /.local > /share > /gvfs-metadata
    Right click on file called " home " select “ Properties “ and change “ Permissions “


    Note that the file called " home " likely was set to " root " privilege (it probably had a small lock symbol on the icon) which means that the user (you) could not alter it.



    Rationale:



    The problem is difficult to reproduce but it seems that Ubuntu 16.04 will lose the ability to ‘remember’ desktop icon placement locations when folders that are located on the desktop have their permissions altered. This seems to happen when the application ' Nautilus ( icon name is “Files” ) ' is simultaneously open in multiple permission states. When Nautilus (Files) is launched using the Unity launcher, the control level is that of a “ user “. When Nautilus (Files) is started from the terminal (CLI) using sudo, it is opened with all the permissions of “ root “. In addition to changing the permission of a folder located on the desktop, Ubuntu will also change the permission of the file that retains the desktop configuration information.
    Unfortunately this does not happen on a regular basis so it is difficult to confirm this theory.






    share|improve this answer



















    • 1





      I think generally root is both the owner and group of /home. Mine, for example shows drwxr-xr-x 7 root root 4096 Dec 15 13:52 home. Perhaps you meant the users directory, which on my system looks like drwxrwxr-x 65 chick chick 4096 Feb 9 16:19 /home/chick

      – Charles Green
      Feb 10 at 2:05



















    -1














    Non-anorak luck:
    Hi-I am not a computer nerd+ not really interested, am refugee to Xubuntu 16.04 from Windows XP.
    But,for what it's worth,I had same annoying problem for 2 years+ this appeared to solve it for me.
    On Settings (or the top LH corner list,I don't know its techy name)click on Desktop>Icons Tab +at Icon Size I reduced the size of desktop icons to 50+Bingo! I've never had the problem since (prob. 2 months with multiple computer re-starts).
    Hope this is of help to other people.
    Computer technical details: desktop ,second hand re-furbished.And it's black.
    Good luck.






    share|improve this answer























      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "89"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: true,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: 10,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f779995%2fdesktop-icons-keep-rearranging-whenever-i-refresh-the-desktop-or-boot-the-system%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      4 Answers
      4






      active

      oldest

      votes








      4 Answers
      4






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      1














      A better way might be:
      Open a terminal from the desktop then enter the following commands:



      cd ~/local/share/gvfs-metadata

      sudo chown $USER home

      chmod 755 home



      This allows your desktop software to change/save the icon configuration.

      (Thanks to the community for correcting spelling and syntax errors.)






      share|improve this answer






























        1














        A better way might be:
        Open a terminal from the desktop then enter the following commands:



        cd ~/local/share/gvfs-metadata

        sudo chown $USER home

        chmod 755 home



        This allows your desktop software to change/save the icon configuration.

        (Thanks to the community for correcting spelling and syntax errors.)






        share|improve this answer




























          1












          1








          1







          A better way might be:
          Open a terminal from the desktop then enter the following commands:



          cd ~/local/share/gvfs-metadata

          sudo chown $USER home

          chmod 755 home



          This allows your desktop software to change/save the icon configuration.

          (Thanks to the community for correcting spelling and syntax errors.)






          share|improve this answer















          A better way might be:
          Open a terminal from the desktop then enter the following commands:



          cd ~/local/share/gvfs-metadata

          sudo chown $USER home

          chmod 755 home



          This allows your desktop software to change/save the icon configuration.

          (Thanks to the community for correcting spelling and syntax errors.)







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Jun 4 '17 at 22:49

























          answered May 31 '17 at 22:01









          UoPTucsonUoPTucson

          464




          464

























              0














              EDIT (August 30th, 2017):

              Before trying the solution below and if the other answers didn't work, try this:




              $ sudo chown -R (UserName) /home/(UserName)/.local/




              For some reason, I have had this issue again after updating Ubuntu 17.04, so I've considered and tried the other answers and they actually didn't work (not because they forgot the "." in "~/.local/..."(again, I'm using 17.04) but because changing the mode and ownership of "./local/share/gvfs-metadata/home" didn't work, most likely it wasn't the right file.) I put this here instead of editing their answer because it may be different on the earlier versions of Ubuntu, and unfortunately, I am not yet allowed to comment. I have decided to chown and chmod all of the "~/.config" directory to no avail, then, after considering the other answers and comments, I tried to chown and chmod the whole "~/.local" directory, testing the result after each step, and I noticed it worked immediately just as I chowned it. No chmod necessary. It could just be my weird setup, but try it anyway because if it works, you're not weakening your security or altering your whole home directory, and it'll fix whatever other configuration files are needed by the desktop client, if any. I hope this helps.
              ==END OF EDIT.==






              I did this,



              $ sudo chown -R (UserName) /home/(UserName)
              $ sudo chmod -R 766 /home/(UserName)


              The first command ensures that the mentioned username (in this case, you) owns all the files in the /home/(UserName) directory.

              The second command ensures you, the owner, have full permissions (read, write, execute) on those files, and everyone else has read and write, which allows the desktop program to write to the configuration file. It doesn't have to be 777, or 766 (read the edit at the bottom). It can be 666 if you want it that way, 766 just gives you execute permissions, just to make sure the configuration files can be overwritten and read.



              The reason this works is because the desktop program runs as whatever user you log in as, not root. If that user doesn't own the configuration files or have write access to them, then every time you refresh the desktop or reboot, because the old files couldn't be overwritten, it reloads the old configuration (like the desktop settings, location of the desktop icons, etc.). By running these commands, you give yourself ownership and complete control over those files, and because the desktop program runs as your user, it will also be able to overwrite, do what it needs to do with those files.



              Also these commands gives the user's home directory (/home/(UserName)) and all the subdirectories write/create privileges also, enabling the user and the desktop program to create those files should they not exist. If those files don't exist and aren't created, the desktop program will generate a new layout every time it is refreshed or restarted. These commands should ensure you full access to all the subdirectories and the desktop program should now be able to create these files and save your layout.



              Edit: When you use the chmod command, you don't have to make them world readable/writable/executable (777), infact, you really shouldn't unless you have to, especially if you have a multi-user machine. It was my mistake for originally suggesting 777, and therefore, I have edited my answer to read 766, not 777. You can use whatever you wish, but you only need to ensure you can write to and read any and all of your configuration files needed for the desktop program and any other software to work.



              Something to remember... Security and convenience (or functionality) usually don't mix.






              share|improve this answer


























              • Hello, It seems like your answer does not answer the question. Could you give more details why it would work

                – ankit7540
                Feb 21 '17 at 5:15






              • 1





                This worked for me because the desktop program runs as whatever user you log in as. If that user doesn't own the configuration file or have write access to it, then every time you refresh the desktop or reboot, because the old file couldn't be overwritten, it reloads the old configuration. By running those commands, you give yourself ownership and complete control over the file, and because the desktop program runs as your user, not root, it will also be able to overwrite, do what it needs to do with that file. And if I'm not mistaken, there's more than 1 config file, so this gets all of them.

                – Thomas Bodrey
                Feb 21 '17 at 5:33











              • Please elaborate your answer to include this information.

                – ankit7540
                Feb 21 '17 at 5:34






              • 1





                Also if it can't write to the directory and that file doesn't exist, you may notice a randomly generated desktop with all the icons reorganized, because there is no configuration file to load from... This was my issue because all my icons were moving around, all sorted in alphabetical order and such. Giving ownership and write privileges to your home directory and sub directories for your user ensures the desktop program can create that file and save your desktop. At least it worked for me anyways.

                – Thomas Bodrey
                Feb 21 '17 at 5:39






              • 2





                You just made every file and directory under /home/username world-writeable, world-readable and world-executable. Why? This is like using a tank to open your front door. While it will probably let you enter the house, it will also let anyone else come in and rearrange your furniture.

                – terdon
                May 18 '17 at 12:31
















              0














              EDIT (August 30th, 2017):

              Before trying the solution below and if the other answers didn't work, try this:




              $ sudo chown -R (UserName) /home/(UserName)/.local/




              For some reason, I have had this issue again after updating Ubuntu 17.04, so I've considered and tried the other answers and they actually didn't work (not because they forgot the "." in "~/.local/..."(again, I'm using 17.04) but because changing the mode and ownership of "./local/share/gvfs-metadata/home" didn't work, most likely it wasn't the right file.) I put this here instead of editing their answer because it may be different on the earlier versions of Ubuntu, and unfortunately, I am not yet allowed to comment. I have decided to chown and chmod all of the "~/.config" directory to no avail, then, after considering the other answers and comments, I tried to chown and chmod the whole "~/.local" directory, testing the result after each step, and I noticed it worked immediately just as I chowned it. No chmod necessary. It could just be my weird setup, but try it anyway because if it works, you're not weakening your security or altering your whole home directory, and it'll fix whatever other configuration files are needed by the desktop client, if any. I hope this helps.
              ==END OF EDIT.==






              I did this,



              $ sudo chown -R (UserName) /home/(UserName)
              $ sudo chmod -R 766 /home/(UserName)


              The first command ensures that the mentioned username (in this case, you) owns all the files in the /home/(UserName) directory.

              The second command ensures you, the owner, have full permissions (read, write, execute) on those files, and everyone else has read and write, which allows the desktop program to write to the configuration file. It doesn't have to be 777, or 766 (read the edit at the bottom). It can be 666 if you want it that way, 766 just gives you execute permissions, just to make sure the configuration files can be overwritten and read.



              The reason this works is because the desktop program runs as whatever user you log in as, not root. If that user doesn't own the configuration files or have write access to them, then every time you refresh the desktop or reboot, because the old files couldn't be overwritten, it reloads the old configuration (like the desktop settings, location of the desktop icons, etc.). By running these commands, you give yourself ownership and complete control over those files, and because the desktop program runs as your user, it will also be able to overwrite, do what it needs to do with those files.



              Also these commands gives the user's home directory (/home/(UserName)) and all the subdirectories write/create privileges also, enabling the user and the desktop program to create those files should they not exist. If those files don't exist and aren't created, the desktop program will generate a new layout every time it is refreshed or restarted. These commands should ensure you full access to all the subdirectories and the desktop program should now be able to create these files and save your layout.



              Edit: When you use the chmod command, you don't have to make them world readable/writable/executable (777), infact, you really shouldn't unless you have to, especially if you have a multi-user machine. It was my mistake for originally suggesting 777, and therefore, I have edited my answer to read 766, not 777. You can use whatever you wish, but you only need to ensure you can write to and read any and all of your configuration files needed for the desktop program and any other software to work.



              Something to remember... Security and convenience (or functionality) usually don't mix.






              share|improve this answer


























              • Hello, It seems like your answer does not answer the question. Could you give more details why it would work

                – ankit7540
                Feb 21 '17 at 5:15






              • 1





                This worked for me because the desktop program runs as whatever user you log in as. If that user doesn't own the configuration file or have write access to it, then every time you refresh the desktop or reboot, because the old file couldn't be overwritten, it reloads the old configuration. By running those commands, you give yourself ownership and complete control over the file, and because the desktop program runs as your user, not root, it will also be able to overwrite, do what it needs to do with that file. And if I'm not mistaken, there's more than 1 config file, so this gets all of them.

                – Thomas Bodrey
                Feb 21 '17 at 5:33











              • Please elaborate your answer to include this information.

                – ankit7540
                Feb 21 '17 at 5:34






              • 1





                Also if it can't write to the directory and that file doesn't exist, you may notice a randomly generated desktop with all the icons reorganized, because there is no configuration file to load from... This was my issue because all my icons were moving around, all sorted in alphabetical order and such. Giving ownership and write privileges to your home directory and sub directories for your user ensures the desktop program can create that file and save your desktop. At least it worked for me anyways.

                – Thomas Bodrey
                Feb 21 '17 at 5:39






              • 2





                You just made every file and directory under /home/username world-writeable, world-readable and world-executable. Why? This is like using a tank to open your front door. While it will probably let you enter the house, it will also let anyone else come in and rearrange your furniture.

                – terdon
                May 18 '17 at 12:31














              0












              0








              0







              EDIT (August 30th, 2017):

              Before trying the solution below and if the other answers didn't work, try this:




              $ sudo chown -R (UserName) /home/(UserName)/.local/




              For some reason, I have had this issue again after updating Ubuntu 17.04, so I've considered and tried the other answers and they actually didn't work (not because they forgot the "." in "~/.local/..."(again, I'm using 17.04) but because changing the mode and ownership of "./local/share/gvfs-metadata/home" didn't work, most likely it wasn't the right file.) I put this here instead of editing their answer because it may be different on the earlier versions of Ubuntu, and unfortunately, I am not yet allowed to comment. I have decided to chown and chmod all of the "~/.config" directory to no avail, then, after considering the other answers and comments, I tried to chown and chmod the whole "~/.local" directory, testing the result after each step, and I noticed it worked immediately just as I chowned it. No chmod necessary. It could just be my weird setup, but try it anyway because if it works, you're not weakening your security or altering your whole home directory, and it'll fix whatever other configuration files are needed by the desktop client, if any. I hope this helps.
              ==END OF EDIT.==






              I did this,



              $ sudo chown -R (UserName) /home/(UserName)
              $ sudo chmod -R 766 /home/(UserName)


              The first command ensures that the mentioned username (in this case, you) owns all the files in the /home/(UserName) directory.

              The second command ensures you, the owner, have full permissions (read, write, execute) on those files, and everyone else has read and write, which allows the desktop program to write to the configuration file. It doesn't have to be 777, or 766 (read the edit at the bottom). It can be 666 if you want it that way, 766 just gives you execute permissions, just to make sure the configuration files can be overwritten and read.



              The reason this works is because the desktop program runs as whatever user you log in as, not root. If that user doesn't own the configuration files or have write access to them, then every time you refresh the desktop or reboot, because the old files couldn't be overwritten, it reloads the old configuration (like the desktop settings, location of the desktop icons, etc.). By running these commands, you give yourself ownership and complete control over those files, and because the desktop program runs as your user, it will also be able to overwrite, do what it needs to do with those files.



              Also these commands gives the user's home directory (/home/(UserName)) and all the subdirectories write/create privileges also, enabling the user and the desktop program to create those files should they not exist. If those files don't exist and aren't created, the desktop program will generate a new layout every time it is refreshed or restarted. These commands should ensure you full access to all the subdirectories and the desktop program should now be able to create these files and save your layout.



              Edit: When you use the chmod command, you don't have to make them world readable/writable/executable (777), infact, you really shouldn't unless you have to, especially if you have a multi-user machine. It was my mistake for originally suggesting 777, and therefore, I have edited my answer to read 766, not 777. You can use whatever you wish, but you only need to ensure you can write to and read any and all of your configuration files needed for the desktop program and any other software to work.



              Something to remember... Security and convenience (or functionality) usually don't mix.






              share|improve this answer















              EDIT (August 30th, 2017):

              Before trying the solution below and if the other answers didn't work, try this:




              $ sudo chown -R (UserName) /home/(UserName)/.local/




              For some reason, I have had this issue again after updating Ubuntu 17.04, so I've considered and tried the other answers and they actually didn't work (not because they forgot the "." in "~/.local/..."(again, I'm using 17.04) but because changing the mode and ownership of "./local/share/gvfs-metadata/home" didn't work, most likely it wasn't the right file.) I put this here instead of editing their answer because it may be different on the earlier versions of Ubuntu, and unfortunately, I am not yet allowed to comment. I have decided to chown and chmod all of the "~/.config" directory to no avail, then, after considering the other answers and comments, I tried to chown and chmod the whole "~/.local" directory, testing the result after each step, and I noticed it worked immediately just as I chowned it. No chmod necessary. It could just be my weird setup, but try it anyway because if it works, you're not weakening your security or altering your whole home directory, and it'll fix whatever other configuration files are needed by the desktop client, if any. I hope this helps.
              ==END OF EDIT.==






              I did this,



              $ sudo chown -R (UserName) /home/(UserName)
              $ sudo chmod -R 766 /home/(UserName)


              The first command ensures that the mentioned username (in this case, you) owns all the files in the /home/(UserName) directory.

              The second command ensures you, the owner, have full permissions (read, write, execute) on those files, and everyone else has read and write, which allows the desktop program to write to the configuration file. It doesn't have to be 777, or 766 (read the edit at the bottom). It can be 666 if you want it that way, 766 just gives you execute permissions, just to make sure the configuration files can be overwritten and read.



              The reason this works is because the desktop program runs as whatever user you log in as, not root. If that user doesn't own the configuration files or have write access to them, then every time you refresh the desktop or reboot, because the old files couldn't be overwritten, it reloads the old configuration (like the desktop settings, location of the desktop icons, etc.). By running these commands, you give yourself ownership and complete control over those files, and because the desktop program runs as your user, it will also be able to overwrite, do what it needs to do with those files.



              Also these commands gives the user's home directory (/home/(UserName)) and all the subdirectories write/create privileges also, enabling the user and the desktop program to create those files should they not exist. If those files don't exist and aren't created, the desktop program will generate a new layout every time it is refreshed or restarted. These commands should ensure you full access to all the subdirectories and the desktop program should now be able to create these files and save your layout.



              Edit: When you use the chmod command, you don't have to make them world readable/writable/executable (777), infact, you really shouldn't unless you have to, especially if you have a multi-user machine. It was my mistake for originally suggesting 777, and therefore, I have edited my answer to read 766, not 777. You can use whatever you wish, but you only need to ensure you can write to and read any and all of your configuration files needed for the desktop program and any other software to work.



              Something to remember... Security and convenience (or functionality) usually don't mix.







              share|improve this answer














              share|improve this answer



              share|improve this answer








              edited Aug 30 '17 at 6:49

























              answered Feb 21 '17 at 4:46









              Thomas BodreyThomas Bodrey

              153




              153













              • Hello, It seems like your answer does not answer the question. Could you give more details why it would work

                – ankit7540
                Feb 21 '17 at 5:15






              • 1





                This worked for me because the desktop program runs as whatever user you log in as. If that user doesn't own the configuration file or have write access to it, then every time you refresh the desktop or reboot, because the old file couldn't be overwritten, it reloads the old configuration. By running those commands, you give yourself ownership and complete control over the file, and because the desktop program runs as your user, not root, it will also be able to overwrite, do what it needs to do with that file. And if I'm not mistaken, there's more than 1 config file, so this gets all of them.

                – Thomas Bodrey
                Feb 21 '17 at 5:33











              • Please elaborate your answer to include this information.

                – ankit7540
                Feb 21 '17 at 5:34






              • 1





                Also if it can't write to the directory and that file doesn't exist, you may notice a randomly generated desktop with all the icons reorganized, because there is no configuration file to load from... This was my issue because all my icons were moving around, all sorted in alphabetical order and such. Giving ownership and write privileges to your home directory and sub directories for your user ensures the desktop program can create that file and save your desktop. At least it worked for me anyways.

                – Thomas Bodrey
                Feb 21 '17 at 5:39






              • 2





                You just made every file and directory under /home/username world-writeable, world-readable and world-executable. Why? This is like using a tank to open your front door. While it will probably let you enter the house, it will also let anyone else come in and rearrange your furniture.

                – terdon
                May 18 '17 at 12:31



















              • Hello, It seems like your answer does not answer the question. Could you give more details why it would work

                – ankit7540
                Feb 21 '17 at 5:15






              • 1





                This worked for me because the desktop program runs as whatever user you log in as. If that user doesn't own the configuration file or have write access to it, then every time you refresh the desktop or reboot, because the old file couldn't be overwritten, it reloads the old configuration. By running those commands, you give yourself ownership and complete control over the file, and because the desktop program runs as your user, not root, it will also be able to overwrite, do what it needs to do with that file. And if I'm not mistaken, there's more than 1 config file, so this gets all of them.

                – Thomas Bodrey
                Feb 21 '17 at 5:33











              • Please elaborate your answer to include this information.

                – ankit7540
                Feb 21 '17 at 5:34






              • 1





                Also if it can't write to the directory and that file doesn't exist, you may notice a randomly generated desktop with all the icons reorganized, because there is no configuration file to load from... This was my issue because all my icons were moving around, all sorted in alphabetical order and such. Giving ownership and write privileges to your home directory and sub directories for your user ensures the desktop program can create that file and save your desktop. At least it worked for me anyways.

                – Thomas Bodrey
                Feb 21 '17 at 5:39






              • 2





                You just made every file and directory under /home/username world-writeable, world-readable and world-executable. Why? This is like using a tank to open your front door. While it will probably let you enter the house, it will also let anyone else come in and rearrange your furniture.

                – terdon
                May 18 '17 at 12:31

















              Hello, It seems like your answer does not answer the question. Could you give more details why it would work

              – ankit7540
              Feb 21 '17 at 5:15





              Hello, It seems like your answer does not answer the question. Could you give more details why it would work

              – ankit7540
              Feb 21 '17 at 5:15




              1




              1





              This worked for me because the desktop program runs as whatever user you log in as. If that user doesn't own the configuration file or have write access to it, then every time you refresh the desktop or reboot, because the old file couldn't be overwritten, it reloads the old configuration. By running those commands, you give yourself ownership and complete control over the file, and because the desktop program runs as your user, not root, it will also be able to overwrite, do what it needs to do with that file. And if I'm not mistaken, there's more than 1 config file, so this gets all of them.

              – Thomas Bodrey
              Feb 21 '17 at 5:33





              This worked for me because the desktop program runs as whatever user you log in as. If that user doesn't own the configuration file or have write access to it, then every time you refresh the desktop or reboot, because the old file couldn't be overwritten, it reloads the old configuration. By running those commands, you give yourself ownership and complete control over the file, and because the desktop program runs as your user, not root, it will also be able to overwrite, do what it needs to do with that file. And if I'm not mistaken, there's more than 1 config file, so this gets all of them.

              – Thomas Bodrey
              Feb 21 '17 at 5:33













              Please elaborate your answer to include this information.

              – ankit7540
              Feb 21 '17 at 5:34





              Please elaborate your answer to include this information.

              – ankit7540
              Feb 21 '17 at 5:34




              1




              1





              Also if it can't write to the directory and that file doesn't exist, you may notice a randomly generated desktop with all the icons reorganized, because there is no configuration file to load from... This was my issue because all my icons were moving around, all sorted in alphabetical order and such. Giving ownership and write privileges to your home directory and sub directories for your user ensures the desktop program can create that file and save your desktop. At least it worked for me anyways.

              – Thomas Bodrey
              Feb 21 '17 at 5:39





              Also if it can't write to the directory and that file doesn't exist, you may notice a randomly generated desktop with all the icons reorganized, because there is no configuration file to load from... This was my issue because all my icons were moving around, all sorted in alphabetical order and such. Giving ownership and write privileges to your home directory and sub directories for your user ensures the desktop program can create that file and save your desktop. At least it worked for me anyways.

              – Thomas Bodrey
              Feb 21 '17 at 5:39




              2




              2





              You just made every file and directory under /home/username world-writeable, world-readable and world-executable. Why? This is like using a tank to open your front door. While it will probably let you enter the house, it will also let anyone else come in and rearrange your furniture.

              – terdon
              May 18 '17 at 12:31





              You just made every file and directory under /home/username world-writeable, world-readable and world-executable. Why? This is like using a tank to open your front door. While it will probably let you enter the house, it will also let anyone else come in and rearrange your furniture.

              – terdon
              May 18 '17 at 12:31











              0














              For users who would prefer a GUI (graphical) way of dealing with the OP, this may be useful to you.



              Procedure: open Nautilus (Files) as root then change the file called ‘ home ‘ to be USER Read/Writable



              Launch Terminal => sudo nautilus
              Nautilus ( Files ) > Home > /.local > /share > /gvfs-metadata
              Right click on file called " home " select “ Properties “ and change “ Permissions “


              Note that the file called " home " likely was set to " root " privilege (it probably had a small lock symbol on the icon) which means that the user (you) could not alter it.



              Rationale:



              The problem is difficult to reproduce but it seems that Ubuntu 16.04 will lose the ability to ‘remember’ desktop icon placement locations when folders that are located on the desktop have their permissions altered. This seems to happen when the application ' Nautilus ( icon name is “Files” ) ' is simultaneously open in multiple permission states. When Nautilus (Files) is launched using the Unity launcher, the control level is that of a “ user “. When Nautilus (Files) is started from the terminal (CLI) using sudo, it is opened with all the permissions of “ root “. In addition to changing the permission of a folder located on the desktop, Ubuntu will also change the permission of the file that retains the desktop configuration information.
              Unfortunately this does not happen on a regular basis so it is difficult to confirm this theory.






              share|improve this answer



















              • 1





                I think generally root is both the owner and group of /home. Mine, for example shows drwxr-xr-x 7 root root 4096 Dec 15 13:52 home. Perhaps you meant the users directory, which on my system looks like drwxrwxr-x 65 chick chick 4096 Feb 9 16:19 /home/chick

                – Charles Green
                Feb 10 at 2:05
















              0














              For users who would prefer a GUI (graphical) way of dealing with the OP, this may be useful to you.



              Procedure: open Nautilus (Files) as root then change the file called ‘ home ‘ to be USER Read/Writable



              Launch Terminal => sudo nautilus
              Nautilus ( Files ) > Home > /.local > /share > /gvfs-metadata
              Right click on file called " home " select “ Properties “ and change “ Permissions “


              Note that the file called " home " likely was set to " root " privilege (it probably had a small lock symbol on the icon) which means that the user (you) could not alter it.



              Rationale:



              The problem is difficult to reproduce but it seems that Ubuntu 16.04 will lose the ability to ‘remember’ desktop icon placement locations when folders that are located on the desktop have their permissions altered. This seems to happen when the application ' Nautilus ( icon name is “Files” ) ' is simultaneously open in multiple permission states. When Nautilus (Files) is launched using the Unity launcher, the control level is that of a “ user “. When Nautilus (Files) is started from the terminal (CLI) using sudo, it is opened with all the permissions of “ root “. In addition to changing the permission of a folder located on the desktop, Ubuntu will also change the permission of the file that retains the desktop configuration information.
              Unfortunately this does not happen on a regular basis so it is difficult to confirm this theory.






              share|improve this answer



















              • 1





                I think generally root is both the owner and group of /home. Mine, for example shows drwxr-xr-x 7 root root 4096 Dec 15 13:52 home. Perhaps you meant the users directory, which on my system looks like drwxrwxr-x 65 chick chick 4096 Feb 9 16:19 /home/chick

                – Charles Green
                Feb 10 at 2:05














              0












              0








              0







              For users who would prefer a GUI (graphical) way of dealing with the OP, this may be useful to you.



              Procedure: open Nautilus (Files) as root then change the file called ‘ home ‘ to be USER Read/Writable



              Launch Terminal => sudo nautilus
              Nautilus ( Files ) > Home > /.local > /share > /gvfs-metadata
              Right click on file called " home " select “ Properties “ and change “ Permissions “


              Note that the file called " home " likely was set to " root " privilege (it probably had a small lock symbol on the icon) which means that the user (you) could not alter it.



              Rationale:



              The problem is difficult to reproduce but it seems that Ubuntu 16.04 will lose the ability to ‘remember’ desktop icon placement locations when folders that are located on the desktop have their permissions altered. This seems to happen when the application ' Nautilus ( icon name is “Files” ) ' is simultaneously open in multiple permission states. When Nautilus (Files) is launched using the Unity launcher, the control level is that of a “ user “. When Nautilus (Files) is started from the terminal (CLI) using sudo, it is opened with all the permissions of “ root “. In addition to changing the permission of a folder located on the desktop, Ubuntu will also change the permission of the file that retains the desktop configuration information.
              Unfortunately this does not happen on a regular basis so it is difficult to confirm this theory.






              share|improve this answer













              For users who would prefer a GUI (graphical) way of dealing with the OP, this may be useful to you.



              Procedure: open Nautilus (Files) as root then change the file called ‘ home ‘ to be USER Read/Writable



              Launch Terminal => sudo nautilus
              Nautilus ( Files ) > Home > /.local > /share > /gvfs-metadata
              Right click on file called " home " select “ Properties “ and change “ Permissions “


              Note that the file called " home " likely was set to " root " privilege (it probably had a small lock symbol on the icon) which means that the user (you) could not alter it.



              Rationale:



              The problem is difficult to reproduce but it seems that Ubuntu 16.04 will lose the ability to ‘remember’ desktop icon placement locations when folders that are located on the desktop have their permissions altered. This seems to happen when the application ' Nautilus ( icon name is “Files” ) ' is simultaneously open in multiple permission states. When Nautilus (Files) is launched using the Unity launcher, the control level is that of a “ user “. When Nautilus (Files) is started from the terminal (CLI) using sudo, it is opened with all the permissions of “ root “. In addition to changing the permission of a folder located on the desktop, Ubuntu will also change the permission of the file that retains the desktop configuration information.
              Unfortunately this does not happen on a regular basis so it is difficult to confirm this theory.







              share|improve this answer












              share|improve this answer



              share|improve this answer










              answered Feb 9 at 23:52









              NewUserNewUser

              165




              165








              • 1





                I think generally root is both the owner and group of /home. Mine, for example shows drwxr-xr-x 7 root root 4096 Dec 15 13:52 home. Perhaps you meant the users directory, which on my system looks like drwxrwxr-x 65 chick chick 4096 Feb 9 16:19 /home/chick

                – Charles Green
                Feb 10 at 2:05














              • 1





                I think generally root is both the owner and group of /home. Mine, for example shows drwxr-xr-x 7 root root 4096 Dec 15 13:52 home. Perhaps you meant the users directory, which on my system looks like drwxrwxr-x 65 chick chick 4096 Feb 9 16:19 /home/chick

                – Charles Green
                Feb 10 at 2:05








              1




              1





              I think generally root is both the owner and group of /home. Mine, for example shows drwxr-xr-x 7 root root 4096 Dec 15 13:52 home. Perhaps you meant the users directory, which on my system looks like drwxrwxr-x 65 chick chick 4096 Feb 9 16:19 /home/chick

              – Charles Green
              Feb 10 at 2:05





              I think generally root is both the owner and group of /home. Mine, for example shows drwxr-xr-x 7 root root 4096 Dec 15 13:52 home. Perhaps you meant the users directory, which on my system looks like drwxrwxr-x 65 chick chick 4096 Feb 9 16:19 /home/chick

              – Charles Green
              Feb 10 at 2:05











              -1














              Non-anorak luck:
              Hi-I am not a computer nerd+ not really interested, am refugee to Xubuntu 16.04 from Windows XP.
              But,for what it's worth,I had same annoying problem for 2 years+ this appeared to solve it for me.
              On Settings (or the top LH corner list,I don't know its techy name)click on Desktop>Icons Tab +at Icon Size I reduced the size of desktop icons to 50+Bingo! I've never had the problem since (prob. 2 months with multiple computer re-starts).
              Hope this is of help to other people.
              Computer technical details: desktop ,second hand re-furbished.And it's black.
              Good luck.






              share|improve this answer




























                -1














                Non-anorak luck:
                Hi-I am not a computer nerd+ not really interested, am refugee to Xubuntu 16.04 from Windows XP.
                But,for what it's worth,I had same annoying problem for 2 years+ this appeared to solve it for me.
                On Settings (or the top LH corner list,I don't know its techy name)click on Desktop>Icons Tab +at Icon Size I reduced the size of desktop icons to 50+Bingo! I've never had the problem since (prob. 2 months with multiple computer re-starts).
                Hope this is of help to other people.
                Computer technical details: desktop ,second hand re-furbished.And it's black.
                Good luck.






                share|improve this answer


























                  -1












                  -1








                  -1







                  Non-anorak luck:
                  Hi-I am not a computer nerd+ not really interested, am refugee to Xubuntu 16.04 from Windows XP.
                  But,for what it's worth,I had same annoying problem for 2 years+ this appeared to solve it for me.
                  On Settings (or the top LH corner list,I don't know its techy name)click on Desktop>Icons Tab +at Icon Size I reduced the size of desktop icons to 50+Bingo! I've never had the problem since (prob. 2 months with multiple computer re-starts).
                  Hope this is of help to other people.
                  Computer technical details: desktop ,second hand re-furbished.And it's black.
                  Good luck.






                  share|improve this answer













                  Non-anorak luck:
                  Hi-I am not a computer nerd+ not really interested, am refugee to Xubuntu 16.04 from Windows XP.
                  But,for what it's worth,I had same annoying problem for 2 years+ this appeared to solve it for me.
                  On Settings (or the top LH corner list,I don't know its techy name)click on Desktop>Icons Tab +at Icon Size I reduced the size of desktop icons to 50+Bingo! I've never had the problem since (prob. 2 months with multiple computer re-starts).
                  Hope this is of help to other people.
                  Computer technical details: desktop ,second hand re-furbished.And it's black.
                  Good luck.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Jan 24 at 4:47









                  D.M.MillerD.M.Miller

                  1




                  1






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Ask Ubuntu!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f779995%2fdesktop-icons-keep-rearranging-whenever-i-refresh-the-desktop-or-boot-the-system%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      How to send String Array data to Server using php in android

                      Title Spacing in Bjornstrup Chapter, Removing Chapter Number From Contents

                      Is anime1.com a legal site for watching anime?