MX-23 alpha2 feedback thread
- Eadwine Rose
- Administrator
- Posts: 14485
- Joined: Wed Jul 12, 2006 2:10 am
Re: MX-23 alpha2 feedback thread
When you use a big panel (say 44), the only way to make things look uniform is to set the system tray to huge icons.
Or make a really small (to me that is really small) panel, which makes the weather item kinda useless in my case.
Is there no way to get those icons, pulseaudio and power manager I think they were, to adjust sizes?
Or make a really small (to me that is really small) panel, which makes the weather item kinda useless in my case.
Is there no way to get those icons, pulseaudio and power manager I think they were, to adjust sizes?
MX-23.6_x64 July 31 2023 * 6.1.0-35amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.247.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.247.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Re: MX-23 alpha2 feedback thread
Previously, @Jerry3904 had posted a gtk hack for scaling the pulseaudio icon to your chosen size. It was from the xfce forum.
You need to add one line of css theming "code" to the gtk.css file (currently empty) in the $HOME/.config/gtk-3.0/ folder. And the actual scale ratio used will be different for everyone depending on the monitor display. resolution,panel size, they use.
xfce4-panel -r
after you make a change.
Perhaps there is a similar thing you can do for power-manager.
You need to add one line of css theming "code" to the gtk.css file (currently empty) in the $HOME/.config/gtk-3.0/ folder. And the actual scale ratio used will be different for everyone depending on the monitor display. resolution,panel size, they use.
Restart the panel with#pulseaudio-button * {
-gtk-icon-transform: scale(.55);
}
xfce4-panel -r
after you make a change.
Perhaps there is a similar thing you can do for power-manager.
Desktop: Intel i5-4460, 16GB RAM, Intel integrated graphics
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400
Re: MX-23 alpha2 feedback thread
Good find. Sure don't remember doing that, but ToZ is always coming up with great css solutions
BTW1: the gtk.css file on my Acer Aspire One 722 testing (Live) machine is not empty but contains a line to import the whisker-tweak file in the same folder
BTW2: @dolphin_oracle above said
BTW1: the gtk.css file on my Acer Aspire One 722 testing (Live) machine is not empty but contains a line to import the whisker-tweak file in the same folder
BTW2: @dolphin_oracle above said
so that may follow the dodoalso, the power manager systray icon appears to work again, so we could take that particular plugin off the panel
Production: 5.10, MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB
Personal: Lenovo X1 Carbon with MX-23 Fluxbox
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Personal: Lenovo X1 Carbon with MX-23 Fluxbox
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Re: MX-23 alpha2 feedback thread
On that test laptop, I see that in Power Manager > System tab, "On Battery" : System sleep mode is set to "hibernate." That seems a potential source of trouble to me since the individual machine's specs vary so much.
Production: 5.10, MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB
Personal: Lenovo X1 Carbon with MX-23 Fluxbox
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Personal: Lenovo X1 Carbon with MX-23 Fluxbox
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Re: MX-23 alpha2 feedback thread
I could have sworn my Home gtk.css file was empty in the alpha2 when I added the hack.Jerry3904 wrote: Wed Apr 12, 2023 5:18 am Good find. Sure don't remember doing that, but ToZ is always coming up with great css solutions
BTW1: the gtk.css file on my Acer Aspire One 722 testing (Live) machine is not empty but contains a line to import the whisker-tweak file in the same folder
...
It's the mx-comfort theme's css file that has the whisker menu addition.
Desktop: Intel i5-4460, 16GB RAM, Intel integrated graphics
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400
- Eadwine Rose
- Administrator
- Posts: 14485
- Joined: Wed Jul 12, 2006 2:10 am
Re: MX-23 alpha2 feedback thread
Just checked, all that is in mine is:asqwerth wrote: Wed Apr 12, 2023 5:44 am I could have sworn my Home gtk.css file was empty in the alpha2 when I added the hack.
Code: Select all
/*set custom gtk3/css code below */
Oh, now that I have it open (in 21 at the mo) I can add that code in.
MX-23.6_x64 July 31 2023 * 6.1.0-35amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.247.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.247.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Re: MX-23 alpha2 feedback thread
The line in mine may have come from implementing touchpad-indicator or something else
Switched to using the Power Manager icon in the systray > very large, so tried this css codeNo effect
Switched to using the Power Manager icon in the systray > very large, so tried this css code
Code: Select all
#power-manager-button * {
-gtk-icon-transform: scale(.55);
}
Production: 5.10, MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB
Personal: Lenovo X1 Carbon with MX-23 Fluxbox
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Personal: Lenovo X1 Carbon with MX-23 Fluxbox
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Re: MX-23 alpha2 feedback thread
HI every one
Here are some suggestions for the MX23
Security issues
1. in the file /etc/adduser the sudo group is enabled for all users,
this is a breach security. I mean any user can execute any command
using his sudo.
2. In the same file the DIR_MODE=0755 should be 0750 ( I notice in the MX23 it is 700)
but why that 700 ? I think group should be enabled
The boot by default uses initV, The largely most used is systemd,
why not switch to systemd by default?
Now in my version MX21:
The command lsblk gives always RO=0, even if the device is read only
see the following output iso image is mount of course as RO
/opt/iso/finnix-125.iso on /root/t type iso9660
(ro,relatime,nojoliet,check=s,map=n,blocksize=2048,iocharset=utf8)
#lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 489M 0 loop /root/t
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 579M 0 part /media/mnt1
Regards
Here are some suggestions for the MX23
Security issues
1. in the file /etc/adduser the sudo group is enabled for all users,
this is a breach security. I mean any user can execute any command
using his sudo.
2. In the same file the DIR_MODE=0755 should be 0750 ( I notice in the MX23 it is 700)
but why that 700 ? I think group should be enabled
The boot by default uses initV, The largely most used is systemd,
why not switch to systemd by default?
Now in my version MX21:
The command lsblk gives always RO=0, even if the device is read only
see the following output iso image is mount of course as RO
/opt/iso/finnix-125.iso on /root/t type iso9660
(ro,relatime,nojoliet,check=s,map=n,blocksize=2048,iocharset=utf8)
#lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 489M 0 loop /root/t
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 579M 0 part /media/mnt1
Regards
Re: MX-23 alpha2 feedback thread
From the Home page:The boot by default uses initV, The largely most used is systemd,
why not switch to systemd by default?
Our Positions
Systemd
Because the use of systemd as a system and service manager has been controversial, we want to be clear about its function in MX Linux. Systemd is included by default but not enabled. You can scan your MX system and discover files bearing systemd* names, but those simply provide a compatibility hook/entrypoint when needed.
MX Linux uses systemd-shim, which emulates the systemd functions that are required to run the helpers without actually using the init service. This means that SvsVinit remains the default init yet MX Linux can use crucial Debian packages that have systemd dependencies such as CUPS and Network Manager. This approach also allows the user to retain the ability to choose his/her preferred init on the boot screen (GRUB). For details, see the MX/antiX Wiki.
Production: 5.10, MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB
Personal: Lenovo X1 Carbon with MX-23 Fluxbox
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Personal: Lenovo X1 Carbon with MX-23 Fluxbox
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
- Eadwine Rose
- Administrator
- Posts: 14485
- Joined: Wed Jul 12, 2006 2:10 am
Re: MX-23 alpha2 feedback thread
Power manager icon scaling code that does work in that file:
Code: Select all
#xfce4-power-manager-plugin * {
-gtk-icon-transform: scale(0.6);
}
MX-23.6_x64 July 31 2023 * 6.1.0-35amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.247.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.247.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030