On Tuesday, June 07, 2022 02:11:36 PM Dave Parker wrote: > thanks, but that didn't fix it :'( > > On Tue, Jun 7, 2022 at 12:08 PM Alain Aupeix <[email protected]>
> > Perhaps changing owner of .run/user/1000/geany > > > > sudo chown -R $user:$user .run/user/1000/geany What command did you actually run, or what is the owner and group of that file now? A number of comments, which may be rather "elementary" (or may sound condescending) depending on the level of expertise of Dave: * on my Debian Wheezy system, it is $USER to get the username * I understand that on newer (Debian?) systems the behavior of sudo has changed somehow, specifically with respect to what environment it uses (that of the user or that of root), you may have to do something like add a - (like "sudo -"), but I have not paid careful attention to discussions about that. * where is file .run/user/1000/geany? I assume (I know) that it is in the user's home directory (i.e., /home/<username>/.run/user/1000/geany I prefer to write commands like that, especially in an email to a (to me) unknown user, more like: # chown -R <username>.<groupname> /home/<user>.run/user/1000/geany (the pound prompt implies being run as root) or some variation that, I hope, a user will recognize what needs to be done. BTW, is that /home/<user>.run/user/1000/geany a file or a directory -- if a file, the -R (for recursive) is not necessary There are possible alternates, like $ sudo <-??> <username>.<groupname> /home/<user>.run/user/1000/geany Note: if the - (dash) is required in the sudo command, I'm about 95% sure a separating space is required. (the pound prompt implies being run as the user) Running ls -al /home/<user>.run/user/1000/geany would let you know if the desired change was accomplished (if that is a directory, appending a /* would be helpful) -- you can post the results here if you have any doubts. _______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected]
