3 ms·

thank you... but did you try that in practice? For my system it still ocntinues to leak into a new created writable version of that file! calling truecrypt wil

thank you... but did you try that in practice? For my system it still ocntinues to leak into a new created writable version of that file! calling truecrypt will results in this: (truecrypt:29720): Gtk-WARNING : Attempting to store changes into `/home/tverrbjelke/.local/share/recently-used.xbel', but failed: Failed to rename file '/home/tverrbjelke/.local/share/recently-used.xbel.I2I27W' to '/home/tverrbjelke/.local/share/recently-used.xbel': g_rename() failed: The operation is not permitted (truecrypt:29720): Gtk-WARNING : Attempting to set the permissions of `/home/tverrbjelke/.local/share/recently-used.xbel', but failed: The operation is not permitted (truecrypt:29720): Gtk-WARNING : Attempting to store changes into `/home/tverrbjelke/.local/share/recently-used.xbel', but failed: Failed to rename file '/home/tverrbjelke/.local/share/recently-used.xbel.QVH27W' to '/home/tverrbjelke/.local/share/recently-used.xbel': g_rename() failed: The operation is not permitted (truecrypt:29720): Gtk-WARNING : Attempting to set the permissions of `/home/tverrbjelke/.local/share/recently-used.xbel', but failed: The operation is not permitted tverrbjelke@espen:~/.local/share$ ls -l recently-used.xbel -rw------- 1 tverrbjelke tverrbjelke 0 Dez 14 14:38 recently-used.xbel please more help!!!

deleted 13y ago
[deleted]
slashdotaccount 13y ago
> but did you try that in practice? Not with TrueCrypt. You can just ignore the warnings (if it doesn't cause a crash). "chattr +i" makes a file really read-only (you can undo it with "chattr -i"). GTK library wants to write recently accessed files there, and fails, emits the warnings. It's safe to ignore them.
- tverr_bjelke 13y ago
  OK I did that and the result was the above output. And then still in same truecrypt session I saw my recently used file - while the bookmarking file still was empty. So closing truecrypt reopening the recently used files list was empty. So that seems to work. thx Question for me is, how the hell can a normal process trigger root-owned read only filed to becom overwritten and chowned to normal user? What is GTK magic doing there?? I dont understand the above session! maybe someone can explai that to me?

deleted 13y ago

[deleted]

slashdotaccount 13y ago

> but did you try that in practice? Not with TrueCrypt. You can just ignore the warnings (if it doesn't cause a crash). "chattr +i" makes a file really read-only (you can undo it with "chattr -i"). GTK library wants to write recently accessed files there, and fails, emits the warnings. It's safe to ignore them.

tverr_bjelke 13y ago
OK I did that and the result was the above output. And then still in same truecrypt session I saw my recently used file - while the bookmarking file still was empty. So closing truecrypt reopening the recently used files list was empty. So that seems to work. thx Question for me is, how the hell can a normal process trigger root-owned read only filed to becom overwritten and chowned to normal user? What is GTK magic doing there?? I dont understand the above session! maybe someone can explai that to me?