LeslieM
Tue Jun 23, 2020 4:03:38 am
How do I stop this from happening?
LeslieM
Tue Jun 23, 2020 4:03:38 am
Aravisian
Tue Jun 23, 2020 5:00:28 am
sudo chown -R <YOUR-USER-NAME>/home/<YOUR-USER-NAME>/.local/
smhardesty
Tue Jun 23, 2020 8:28:50 pm
Aravisian
Tue Jun 23, 2020 10:44:29 pm
smhardesty wrote:I have the same problem as LeslieM. I tried using your command but I keep getting this error. I must be missing something.
chown: missing operand after ‘steve-Lenovo-G50-45/home/steve-Lenovo-G50-45/.local/’
sudo chown -R /home/$USER/.local/
smhardesty
Wed Jun 24, 2020 12:25:16 am
steve@steve-Lenovo-G50-45:~$ sudo chown -R /home/steve-Lenovo-G50-45/.local/
[sudo] password for steve:
chown: missing operand after ‘/home/steve-Lenovo-G50-45/.local/’
Try 'chown --help' for more information.
steve@steve-Lenovo-G50-45:~$ chown --help
Usage: chown [OPTION]... [OWNER][:[GROUP]] FILE...
or: chown [OPTION]... --reference=RFILE FILE...
Change the owner and/or group of each FILE to OWNER and/or GROUP.
With --reference, change the owner and group of each FILE to those of RFILE.
-c, --changes like verbose but report only when a change is made
-f, --silent, --quiet suppress most error messages
-v, --verbose output a diagnostic for every file processed
--dereference affect the referent of each symbolic link (this is
the default), rather than the symbolic link itself
-h, --no-dereference affect symbolic links instead of any referenced file
(useful only on systems that can change the
ownership of a symlink)
--from=CURRENT_OWNER:CURRENT_GROUP
change the owner and/or group of each file only if
its current owner and/or group match those specified
here. Either may be omitted, in which case a match
is not required for the omitted attribute
--no-preserve-root do not treat '/' specially (the default)
--preserve-root fail to operate recursively on '/'
--reference=RFILE use RFILE's owner and group rather than
specifying OWNER:GROUP values
-R, --recursive operate on files and directories recursively
The following options modify how a hierarchy is traversed when the -R
option is also specified. If more than one is specified, only the final
one takes effect.
-H if a command line argument is a symbolic link
to a directory, traverse it
-L traverse every symbolic link to a directory
encountered
-P do not traverse any symbolic links (default)
--help display this help and exit
--version output version information and exit
Owner is unchanged if missing. Group is unchanged if missing, but changed
to login group if implied by a ':' following a symbolic OWNER.
OWNER and GROUP may be numeric as well as symbolic.
Examples:
chown root /u Change the owner of /u to "root".
chown root:staff /u Likewise, but also change its group to "staff".
chown -hR root /u Change the owner of /u and subfiles to "root".
GNU coreutils online help: <http://www.gnu.org/software/coreutils/>
Full documentation at: <http://www.gnu.org/software/coreutils/chown>
or available locally via: info '(coreutils) chown invocation'
Aravisian
Wed Jun 24, 2020 1:29:39 am
smhardesty
Wed Jun 24, 2020 4:38:34 am
Aravisian
Wed Jun 24, 2020 9:19:09 am
smhardesty
Wed Jun 24, 2020 10:00:46 am
Swarfendor437
Wed Jun 24, 2020 4:49:01 pm
smhardesty
Wed Jun 24, 2020 8:10:55 pm
Aravisian
Wed Jun 24, 2020 8:19:11 pm
smhardesty
Wed Jun 24, 2020 8:45:44 pm
Aravisian
Wed Jun 24, 2020 8:54:16 pm
smhardesty wrote:I have two .rc files. One is icons.screen.latest.rc and the other is icons.screen0-1350x711.rc. I checked and they appear to be identical in their content. My screen resolution is set to 1366x768. Before I remove anything I'd like to confirm which to remove.
Uh-oh. I just took a look at the Sessions and Startup info. There is no check in Automatically Save Session On Logout. Is that my problem?
smhardesty
Wed Jun 24, 2020 10:37:50 pm
smhardesty
Thu Jun 25, 2020 7:35:14 am
Aravisian
Thu Jun 25, 2020 4:45:59 pm
smhardesty wrote:Well, that didn't seem to work. On the first reboot it totally scrambled my desktop icons. Not only that, I just checked on those .rc files and the system recreated the icons.screen0-1350x711.rc file. For whatever reason, the system believes it needs that file. Go figure.
smhardesty
Thu Jun 25, 2020 7:00:38 pm
You know...I may have been wrong - that resolution may be accounting for the Panel size.
Aravisian
Thu Jun 25, 2020 7:32:35 pm
smhardesty wrote:It seems that both the .rc files I have on my laptop are necessary. I don't begin to understand why, but it sure looks that way.
smhardesty
Thu Jun 25, 2020 9:17:15 pm
Aravisian
Thu Jun 25, 2020 9:47:06 pm
smhardesty wrote:.
HAH! You''l find this really funny. Back when I was doing the MS thing, my desktops were spotless. I had NOTHING on any Windows desktop I had. I left only the bare minimum icons on the desktops of PCs I worked on for customers. When I switched to Linux I started using the desktop to put my most used files and folders on.
As for the scrambling of icons, I don't view it as a real problem. I consider it a somewhat strange annoyance. Rearranging icons isn't a big deal, especially since it only happens occasionally. If there are already several bug reports in, it'll probably be handled in some future update.
Also, I did try deleting just the generic icons.screen.latest.rc file and rebooting. It came right back so apparently both of those files are necessary.
.
smhardesty
Fri Jun 26, 2020 9:31:05 pm
Swarfendor437
Fri Jun 26, 2020 10:56:58 pm
smhardesty
Sat Jun 27, 2020 1:05:09 am
smhardesty
Sat Jun 27, 2020 9:20:33 pm