You are not logged in.

#1 2025-10-26 04:26:29

dainispolis
Member
Registered: 2025-10-26
Posts: 3

pcmanfm-qt rewrites config file after login

It is about persistent exclamation marks over desktop icons. I can set to trust any icon and exclamation mark lost. But after login , it shows again!  I was searching anywhere, but without success.
Why pcmanfm-qt config file - because ai says - you can disable trust checking by write TrustExecutables=true in config file. This also not helps , exactly because after another session config file is written as default.  Interesting is that on my desktop comp all is ok, but problem is on laptop.  All other is same, same lxqt, same archlinux,...  Please help!!!

Offline

#2 2025-10-26 08:59:59

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 73,680

Re: pcmanfm-qt rewrites config file after login

Generically because multiple processes (your desktop shell?) write back conflicting configs?
Log out of your GUI session, make sure no pcmanfm-qt process is running, log into a console, edit the config file there, restart pcmanfm-qt => profit?

Offline

#3 2025-10-27 05:14:38

dainispolis
Member
Registered: 2025-10-26
Posts: 3

Re: pcmanfm-qt rewrites config file after login

Ok.  New details: Your hint helps changes in  config file (in path ~/.config/pcman-qt/lxqt/settings.conf) , now TrustExecutables=true is persistent, but exclamation signs also persist and i can remove them by check "Trust this executable" in context menu, but after reloging signs again apears.  I'm confusing...

Offline

#4 2025-10-27 08:16:55

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 73,680

Re: pcmanfm-qt rewrites config file after login

Afaiu https://github.com/lxqt/pcmanfm-qt/issues/1519 and https://github.com/lxqt/pcmanfm-qt/issues/737 a list of per-file exceptions is kept around, have a look at that.

Offline

#5 2025-10-27 10:15:27

dainispolis
Member
Registered: 2025-10-26
Posts: 3

Re: pcmanfm-qt rewrites config file after login

Thanks seth!  In my case just after instaling package gvfs all works as needed!

Offline

#6 2025-10-27 13:20:12

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 73,680

Re: pcmanfm-qt rewrites config file after login

I had quite frankly not expected any of this to hinge on gvfs - does the problem re-appear when removing gvfs?

Either way, please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Offline

#7 2025-10-28 12:17:38

Valso
Member
Registered: 2021-04-22
Posts: 131

Re: pcmanfm-qt rewrites config file after login

dainispolis wrote:

Thanks seth!  In my case just after instaling package gvfs all works as needed!

I know your problem is solved but just out of curiousity bc I'm using the same file manager (only the gtk3 edition): if you ever encounter this problem again, try and see what will happen if you make the conf file immutable.

2 years ago I had a weird problem with ~/.bash_history and immutability solved the problem. smile


RESIST OS GTK3 (customized Arch), i7-12700F, RTX 3070 Ti 8GB, 64GB DDR5-4800 (OCed to 5200 MHz).

Offline

#8 2025-10-28 13:59:36

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 73,680

Re: pcmanfm-qt rewrites config file after login

This doesn't really solve problems so much as it downforces them - if you have something spamming random files you want to figure what that is and stop it from doing so.
Immuting a file can only be the last resort when you cannot stop the attack on it.

=> https://wiki.archlinux.org/title/Audit_ … ies_access

Offline

#9 2025-10-29 07:30:43

Valso
Member
Registered: 2021-04-22
Posts: 131

Re: pcmanfm-qt rewrites config file after login

seth wrote:

This doesn't really solve problems so much as it downforces them - if you have something spamming random files you want to figure what that is and stop it from doing so.
Immuting a file can only be the last resort when you cannot stop the attack on it.

=> https://wiki.archlinux.org/title/Audit_ … ies_access

Sometimes (depending on the problem) immutability is an easier fix. I've never used or needed .bash_history and since disabling .bash_history didn't help, it was easier to delete the file, touch it and immediately make it immutable before whatever was spamming it had the chance to reactivate.

It's pointless to discuss that now and here bc it was long ago, I solved the problem using the only way that actually worked and it seems to have disappeared at some point bc last night I lifted the immutability from it and nothing is spamming it anymore. A friend of mine suggested that it might have been a bug in xfsprogs bc the spamming of .bash_history started almost immediately after running the desktop of freshly installed vanilla Arch on XFS. And, IIRC, I updated xfsprogs several times since then (since 28th of July 2023).


RESIST OS GTK3 (customized Arch), i7-12700F, RTX 3070 Ti 8GB, 64GB DDR5-4800 (OCed to 5200 MHz).

Offline

Board footer

Powered by FluxBB