'su lyx' changes file access privileges

[paolo m.]

Scott Kostyshak wrote:

> On Sun, Sep 27, 2020 at 04:31:24PM +0200, paolo m.  wrote:
>> Kornel Benko wrote:
>> 
>> > Am Sun, 27 Sep 2020 14:03:44 +0200
>> > schrieb "paolo m. " <paolo.pumilia at gmail.com>:
>> > 
>> >> Kornel Benko wrote:
>> >> 
>> >> > Am Sun, 27 Sep 2020 13:19:52 +0200
>> >> > schrieb "paolo m." <paolo.pumilia at gmail.com>:
>> >> >   
>> >> >> Sometimes, while  in user1 session, I find convenient launching lyx
>> >> >> as user2
>> >> >> (same group as user1)  to open a lyx file, through 'su'.
>> >> >> As user2 changes and save that file, access privileges are changed
>> >> >> as well. That does not happen when a text file is opened by kwrite,
>> >> >> so it should be something specific to lyx.
>> >> >>  
>> >> >> Before 'su' switch:
>> >> >> text file     x            -rw-rw-r--
>> >> >> lyx file     xx.lyx        -rw-rw-r--
>> >> >> 
>> >> >> Switching and modifying file x (by  kwrite)  and xx.lyx (by lyx):
>> >> >>               x          -rw-rw-r--
>> >> >>               xx.lyx     -rw-------
>> >> >> 
>> >> >> (Same results when  launching 'dolphin' file manager as user2 to
>> >> >> open a lyx file, through 'su'').
>> >> >>   
>> >> > 
>> >> > Have you checked the setting of 'umask' for both users?
>> >> > 
>> >> > Kornel
>> >> Yes, umask is set in /etc/zshenv;  kwrite complies with that
>> >> specification Maybe lyx reads a different umask setting?
>> >> 
>> >> thanks
>> >> 
>> >> p.
>> >> 
>> > 
>> > Hm, I meant the output of the command 'umask'.
>> > Maybe it is set be /etc/zshenv, but there may be different handling
>> > (like include of user specific file).
>> > 
>> >  Here it is for example
>> >  $ umask
>> > 22
>> > 
>> > Kornel
>> 
>> Umask is the same for both users:
>> % umask
>>  002
>>  
>> 
>> % grep -i umask /etc/zshenv
>>   umask u=rwx,g=rwx,o=rx
> 
> Is the following discussion related?
> 
> https://www.mail-archive.com/search?l=mid&q=ptceag%245s5%241%40blaine.gmane.org
> 
> Scott
Yes, that was me. 
That malfunction was fixed by Pavel Sanda

This seems to be a different issue.

p.