Page 1 of 1

Porteus 5 Final MATE Caja Glitch on Changing Theme

Posted: 05 Jul 2022, 18:16
by POR5RC3-ID
Hello all,
I've been using porteus since version 3 I think, great distro, not easy to handle tho but yeah it will reward you once you get used to it. Yesterday I decided to create a youtube channel showcasing weekly tutorial on how to do things on porteus from a newbie prespective, I uploaded my first video yesterday, here

https://www.youtube.com/watch?v=37or7Dv9a1c

it's in Bahasa Indonesia, for Indonesian audience but I've put some effort to compile the English subtitle too, that video is using Porteus 5 RC3 and then at the same time I read that Porteus 5 Final has been released, o well ^^

I hope everything I've shown there still relevant with the final release

I've tried the Porteus 5 Final MATE and my autotheme script works with minor modification BUT I notice some kind of a gltch on the Caja window, the location entry background is dark, the text can not be read, I have to disable "always-use-location-entry" using the dconf editor to hide it, if any of you guys can point me to a guide that will fix that dark Caja background I would be grateful, here is the video showing what I'm talking about,

https://youtu.be/fVDgldheSeE

I might have to edit the GTK CSS on each theme to fix that but I'm not sure..

anyway, it's good to know that Porteus 5 Final has been released..

until next time :)

Porteus 5 Final MATE Caja Glitch on Changing Theme

Posted: 05 Jul 2022, 22:56
by ncmprhnsbl
unless i'm mistaken, this should fix itself on logout/in ... because caja needs to restart and because it's running the desktop, restarting the desktop is needed..

Porteus 5 Final MATE Caja Glitch on Changing Theme

Posted: 06 Jul 2022, 02:49
by POR5RC3-ID
ncmprhnsbl wrote:
05 Jul 2022, 22:56
unless i'm mistaken, this should fix itself on logout/in ... because caja needs to restart and because it's running the desktop, restarting the desktop is needed..
I don't use save file so relogin/restart is not an option BUT you're right mate, I got it fixed by restarting Caja with "caja --quit" command, so I don't have to relogin/restart
consider it's solved

thanks :)