MX-21 beta 2 feedback thread (xfce)
- Eadwine Rose
- Administrator
- Posts: 14478
- Joined: Wed Jul 12, 2006 2:10 am
Re: MX-21 beta 2 feedback thread (xfce)
There is something wonky, window manager theme (the old way), theme not changing when I select different themes. However if I go through.. what is it.. tweak? I find myself in a whole different window layout with them all next to each other (window theme font icon theme, a new way that I haven't seen before) and when I change the theme there from say greybird to adawaita, or whatever that is called, you can see things changing.
However not on all the applications. I had libreoffice open, that had a light theme, gthumb is dark.
Something is wonky there. Might the two places (the old and the new) be conflicting?
Also.. where does one adjust the visible time of the mx updater?
It used to be by editing in this folder
/usr/lib/apt-notifier/pkexec-wrappers/
in this file
file mx-updater-reload.sh
changing the 6 to a 1(or whatever) in the sleep line
That is no longer there.
However not on all the applications. I had libreoffice open, that had a light theme, gthumb is dark.
Something is wonky there. Might the two places (the old and the new) be conflicting?
Also.. where does one adjust the visible time of the mx updater?
It used to be by editing in this folder
/usr/lib/apt-notifier/pkexec-wrappers/
in this file
file mx-updater-reload.sh
changing the 6 to a 1(or whatever) in the sleep line
That is no longer there.
MX-23.6_x64 July 31 2023 * 6.1.0-34amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.216.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.216.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
- dolphin_oracle
- Developer
- Posts: 22110
- Joined: Sun Dec 16, 2007 12:17 pm
Re: MX-21 beta 2 feedback thread (xfce)
you might can adjust timeout in ~/.config/apt-notifierrcEadwine Rose wrote: Wed Sep 08, 2021 3:05 pm There is something wonky, window manager theme (the old way), theme not changing when I select different themes. However if I go through.. what is it.. tweak? I find myself in a whole different window layout with them all next to each other (window theme font icon theme, a new way that I haven't seen before) and when I change the theme there from say greybird to adawaita, or whatever that is called, you can see things changing.
However not on all the applications. I had libreoffice open, that had a light theme, gthumb is dark.
Something is wonky there. Might the two places (the old and the new) be conflicting?
Also.. where does one adjust the visible time of the mx updater?
It used to be by editing in this folder
/usr/lib/apt-notifier/pkexec-wrappers/
in this file
file mx-updater-reload.sh
changing the 6 to a 1(or whatever) in the sleep line
That is no longer there.
gthumb is always dark, although if you watch close you will see the color change some between adwaita and arc for instance. but gthumb is generally dark.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
- Eadwine Rose
- Administrator
- Posts: 14478
- Joined: Wed Jul 12, 2006 2:10 am
Re: MX-21 beta 2 feedback thread (xfce)
Ah ok, that explains that, thanks on both :)
But still remains that when in the "old" adjuster (window manager), changing the theme there does nothing.
I can click about, but no changes to be seen.
Also.. Daloa, the one I always use, is in there. However that one is not there in the new one.
I need to recheck this tomorrow and confirm, for now I am seeing cross-eyed haha.
The panel tooltip issue is also a hairpuller
When I change the size to 29 it is ok, but I don't want a maximized window to go behind the panel, so I have to set the leave space on borders, or what is it called, accordingly. But when I do that the tooltips go back to being silly.
But still remains that when in the "old" adjuster (window manager), changing the theme there does nothing.

Also.. Daloa, the one I always use, is in there. However that one is not there in the new one.

I need to recheck this tomorrow and confirm, for now I am seeing cross-eyed haha.
The panel tooltip issue is also a hairpuller

When I change the size to 29 it is ok, but I don't want a maximized window to go behind the panel, so I have to set the leave space on borders, or what is it called, accordingly. But when I do that the tooltips go back to being silly.
MX-23.6_x64 July 31 2023 * 6.1.0-34amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.216.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.216.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
- chrispop99
- Global Moderator
- Posts: 3338
- Joined: Tue Jan 27, 2009 2:07 pm
Re: MX-21 beta 2 feedback thread (xfce)
That's one reason why I won't use it, and why I think we shouldn't include it.dolphin_oracle wrote: Wed Sep 08, 2021 3:29 pm
gthumb is always dark, although if you watch close you will see the color change some between adwaita and arc for instance. but gthumb is generally dark.
My 75 year old eyes can't cope with dark themes; it gives me a headache.
Chris
MX Facebook Group Administrator.
Home-built desktop - Core i5 9400, 970 EVO Plus, 8GB
DELL XPS 15
Lots of test machines
Home-built desktop - Core i5 9400, 970 EVO Plus, 8GB
DELL XPS 15
Lots of test machines
- dolphin_oracle
- Developer
- Posts: 22110
- Joined: Sun Dec 16, 2007 12:17 pm
Re: MX-21 beta 2 feedback thread (xfce)
@Eadwine Rose you will need to watch close. Not all apps use window manager themes including the window manager theme app.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
- Eadwine Rose
- Administrator
- Posts: 14478
- Joined: Wed Jul 12, 2006 2:10 am
Re: MX-21 beta 2 feedback thread (xfce)
Apparently. I had the same apps open when I tried the one and then the other. They didn't work with the one, but did with the other.
I will give this a good and proper whirl sometime tomorrow.
I will give this a good and proper whirl sometime tomorrow.
MX-23.6_x64 July 31 2023 * 6.1.0-34amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.216.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.216.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Re: MX-21 beta 2 feedback thread (xfce)
Yes, that's a general config item, which can be changed globaly for all users,Eadwine Rose wrote: Wed Sep 08, 2021 3:05 pm Also.. where does one adjust the visible time of the mx updater?
It used to be by editing in this folder
/usr/lib/apt-notifier/pkexec-wrappers/
in this file
file mx-updater-reload.sh
changing the 6 to a 1(or whatever) in the sleep line
That is no longer there.
Or in addition on user level by creating such a file
within users home/.config sub-folder "MX-Linux" folder:
$HOME/.config/MX-Linux/apt-notifier.conf
Code: Select all
[MX]
# auto close timeouts
reload_auto_close_timeout = 6
upgrade_auto_close_timeout = 10
- Eadwine Rose
- Administrator
- Posts: 14478
- Joined: Wed Jul 12, 2006 2:10 am
Re: MX-21 beta 2 feedback thread (xfce)
Not in that location as I cannot find it there anymore.fehlix wrote: Wed Sep 08, 2021 4:26 pm Yes, that's a general config item, which can be changed globaly for all users,
Oh I need to create one. Errr no, not me

I will check the above and ~/.config/apt-notifierrc that DO gave me.Or in addition on user level by creating such a file
within users home/.config sub-folder "MX-Linux" folder:
$HOME/.config/MX-Linux/apt-notifier.confCode: Select all
[MX] # auto close timeouts reload_auto_close_timeout = 6 upgrade_auto_close_timeout = 10
MX-23.6_x64 July 31 2023 * 6.1.0-34amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.216.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.216.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Re: MX-21 beta 2 feedback thread (xfce)
So if we are running Beta 1 and everything is fine, we can just keep going as is and eventually be updated via Apt to MX-21 stable?
Or do we need to re-install to Beta 2 first to update eventually to stable?
Sorry, never done a Beta before and just confused as to how the beta to stable release process works.
Or do we need to re-install to Beta 2 first to update eventually to stable?
Sorry, never done a Beta before and just confused as to how the beta to stable release process works.
- entropyfoe
- Posts: 615
- Joined: Thu Apr 19, 2007 11:42 am
Re: MX-21 beta 2 feedback thread (xfce)
My un-official practice is to not roll a beta over.
Better to start with a real fully configured tested starting iso.
Most reliable. Betas are for testing.
Now there will probably be at least one RC -release candidate, rarely two.
These can easily be rolled to a final, as often no changes are made, except a name.
So you really have the final.
Better to start with a real fully configured tested starting iso.
Most reliable. Betas are for testing.
Now there will probably be at least one RC -release candidate, rarely two.
These can easily be rolled to a final, as often no changes are made, except a name.
So you really have the final.

MX 23.5 on Asus PRIME X470-PRO
AMD Ryzen 3600X (12 threads @ 3.8 GHz)
32 Gig DDR4 3600 (Crucial CL 16)
Nvidia GeForce GT 710
Samsung 970 NVMe nvme0n1 P1-3=MX-23.5, P4=testing
Samsung 980 NVMe =1TB Data, plus 2TB WD =backups
on-board ethernet & sound
AMD Ryzen 3600X (12 threads @ 3.8 GHz)
32 Gig DDR4 3600 (Crucial CL 16)
Nvidia GeForce GT 710
Samsung 970 NVMe nvme0n1 P1-3=MX-23.5, P4=testing
Samsung 980 NVMe =1TB Data, plus 2TB WD =backups
on-board ethernet & sound