Re: How to change lightdm background in bullseye? (additional: weird stat behaviour)

2022-06-17 Thread Christoph K.
Am Thu, 16 Jun 2022 23:26:38 +
schrieb Lee :

> > [greeter]
> > background=/usr/share/xfce4/backdrops/foo.png
> > user-background=/usr/share/xfce4/backdrops/foo.png
> 
> Do those files exist?  There's no /usr/share/xfce4/backdrops/ on my machine..

No, these files don't exist ;-)
I changed the name to foo.png in the email because the original name
contained information I didn't want to share.

But yes, the directory exists (initial install was Debian 8) and the files
referenced also exist.


> This works for me
> $ cat lightdm-gtk-greeter.conf
> [greeter]
> background = /usr/share/desktop-base/spacefun-theme/login/background.svg

My original file /etc/lightdm/lightdm-gtk-greeter.conf actually contained
a lot of lines with comments about the options. I copied only the relevant
stuff (what I _believed_ was relevant) into the email.


> Try installing lightdm-gtk-greeter-settings
> I get a lot of error messages but it did change the background for me.

It works.
The settings editor removed everything else from the file and now there's
only those two lines left.

I'm really curious to find out what in the original file caused problems.
I'll restore it from my backup and check that.

Thanks!

Christoph



Re: How to change lightdm background in bullseye? (additional: weird stat behaviour)

2022-06-17 Thread Eduardo M KALINOWSKI

On 16/06/2022 06:47, Christoph K. wrote:

Procedure:
1. touch test.txt
2. stat test.txt -> correct access time from touch
3. cat test.txt
4. stat test.txt -> access time changed due to cat - fine
5. cat test.txt
6. stat test.txt -> still the same access time as in step 4 - caching?
7. reboot
8. cat test.txt
9. stat test.txt -> STILL the same access time as in step 4 - WTF?

Expectations:
1) After a reboot there is no cache to read from.
2) The cat command accesses the file.
3) Stat shows the time of "cat" in the access time stamp.

But 3) does not happen. More precisely: It only happens sometimes.


Question 3:
Could someone please explain to me what's going on here with stat?


Looks like the relatime option, which has been the default for some 
time: 
https://www.linuxquestions.org/questions/linux-hardware-18/what-does-mount-option-relatime-4175575024/



--

Não tenha pressa, mas não perca tempo

--José Saramago

Eduardo M KALINOWSKI
edua...@kalinowski.com.br



Re: How to change lightdm background in bullseye? (additional: weird stat behaviour)

2022-06-16 Thread Lee
On 6/16/22, Christoph K. wrote:
> Hello,
>
>
> Part 1: lightdm background
>
> I've just upgraded to bullseye and would like to change the background of
> the lightdm greeter.
>
> According to ...
> https://wiki.debian.org/LightDM#Change_the_greeter.27s_background
> ... I'm supposed to edit ...
> /etc/lightdm/lightdm-gtk-greeter.conf
>
> ... which I've done ...
>
> [greeter]
> background=/usr/share/xfce4/backdrops/foo.png
> user-background=/usr/share/xfce4/backdrops/foo.png

Do those files exist?  There's no /usr/share/xfce4/backdrops/ on my machine..

This works for me
$ cat lightdm-gtk-greeter.conf
[greeter]
background = /usr/share/desktop-base/spacefun-theme/login/background.svg

  <.. snip ..>

> I'm suspecting my changes in lightdm-gtk-greeter.conf have no effect.

Try installing lightdm-gtk-greeter-settings
I get a lot of error messages but it did change the background for me.


> Part 2: weird stat behaviour (ext4 filesystem)
>
> I'm not too familiar with stat and access times, although I do believe to
> have some understanding of it. But the following confuses me:

Somebody with a lot more knowledge in that area needs to respond, but
wasn't there a setup question about enabling that or no?  .. along the
lines of updating access times requires a disk write every time a file
is accessed, so one can make things faster by not updating the access
time.

Regards,
Lee



How to change lightdm background in bullseye? (additional: weird stat behaviour)

2022-06-16 Thread Christoph K.
Hello,


Part 1: lightdm background

I've just upgraded to bullseye and would like to change the background of
the lightdm greeter.

According to ...
https://wiki.debian.org/LightDM#Change_the_greeter.27s_background
... I'm supposed to edit ...
/etc/lightdm/lightdm-gtk-greeter.conf

... which I've done ...

[greeter]
background=/usr/share/xfce4/backdrops/foo.png
user-background=/usr/share/xfce4/backdrops/foo.png

... with no success. Background sticks to dark blue image with debian
artwork.

Before, I had already tried to get a language selector in lightdm by
changing the indicators:

indicators=~host;~spacer;~session;~language;ally;~clock;~power

But lightdm doesn't show a language selector.

I'm suspecting my changes in lightdm-gtk-greeter.conf have no effect.


Question 1:
How do I properly change the lightdm background image?


Question 2:
Is lightdm-gtk-greeter.conf the right place to configure the lightdm
greeter in bullseye?



Part 2: weird stat behaviour (ext4 filesystem)

I'm not too familiar with stat and access times, although I do believe to
have some understanding of it. But the following confuses me:

The question related to lightdm was: Is the file
/etc/lightdm/lightdm-gtk-greeter.conf
actually read by lightdm?
To find out I edited the file and restartet lightdm. "stat" didn't show
any access to the file so I did a system reboot because I suspected the
missing access change was due to caching.

But after the reboot the file still had the old access time!
(I removed addional output of the stat command):

/etc/lightdm$ date
Do 16. Jun 11:11:05 CEST 2022
/etc/lightdm$ stat lightdm-gtk-greeter.conf 
 Datei: lightdm-gtk-greeter.conf
Zugriff: 2022-06-16 10:43:18.769291459 +0200

FYI: "Zugriff" is access time in german

Reboot was at 10:45,
access time is 10:43.

Is it correct to conclude that the file has not been read during bootup?
Or am I overlooking something?


To further elaborate I did another test on a test.txt file.
Procedure:
1. touch test.txt
2. stat test.txt -> correct access time from touch
3. cat test.txt
4. stat test.txt -> access time changed due to cat - fine
5. cat test.txt
6. stat test.txt -> still the same access time as in step 4 - caching?
7. reboot
8. cat test.txt
9. stat test.txt -> STILL the same access time as in step 4 - WTF?

Expectations:
1) After a reboot there is no cache to read from.
2) The cat command accesses the file.
3) Stat shows the time of "cat" in the access time stamp.

But 3) does not happen. More precisely: It only happens sometimes.


Question 3:
Could someone please explain to me what's going on here with stat?


Thanks,
Christoph