Yes I did. There was no other way to get that thing transparent.JayM wrote: Mon Oct 07, 2019 3:24 amSee my edit 2 above. You probably selected a solid panel background color (with transparency, it looks like,)Eadwine Rose wrote: Mon Oct 07, 2019 3:18 am Hmm.. how then is it possible that it is transparent for me?
This is from beta2.1:
snapshot.png
MX-19 Beta 3 Feedback
- Eadwine Rose
- Administrator
- Posts: 14471
- Joined: Wed Jul 12, 2006 2:10 am
Re: MX-19 Beta 3 Feedback
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-19 Beta 3 Feedback
BTW I just tested it with a panel background image and it uses a slightly lighter version of that image for its background. If I set both the enter and leave opacity to 50 I have the regular image as Orage's background with no translucency. So the "onliest" way to have a truly transparent background in Orage is to use a solid color in your panel.
Please read the Forum Rules, How To Ask For Help, How to Break Your System and Don't Break Debian. Always include your full Quick System Info (QSI) with each and every new help request.
- Eadwine Rose
- Administrator
- Posts: 14471
- Joined: Wed Jul 12, 2006 2:10 am
Re: MX-19 Beta 3 Feedback
Back in 18.3 I just matched the background color to the wallpaper and had the regular transparency going on. Since that transparency option is now gone the only way to get that is with the solid color thing.
It would be nice to get that transparency sorted though.. but yeah.. it's not a major thing.
It would be nice to get that transparency sorted though.. but yeah.. it's not a major thing.
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-19 Beta 3 Feedback
The only way is to set the enter and leave opacity to the same setting, if you don't want to change to a solid color. That sort of works, except of course for the Orage clock, and the fact that it also affects all panel icons.
Please read the Forum Rules, How To Ask For Help, How to Break Your System and Don't Break Debian. Always include your full Quick System Info (QSI) with each and every new help request.
- Eadwine Rose
- Administrator
- Posts: 14471
- Joined: Wed Jul 12, 2006 2:10 am
Re: MX-19 Beta 3 Feedback
That only makes it semi transparent I think.. and affects EVERYTHING in the panel indeed.. also the window buttons and all that.
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-19 Beta 3 Feedback
Hello,
During live session and before installing Mx Linux 19.3 beta, I notice that my bluetooth dock and headphones cannot be paired. They don't appear during the first step of the process.
It worked properly on previous MX Linux versions without any special manipulation.
I hope this problem will be solved.
So sorry if my post is not at the right place...
Best regards.
During live session and before installing Mx Linux 19.3 beta, I notice that my bluetooth dock and headphones cannot be paired. They don't appear during the first step of the process.
It worked properly on previous MX Linux versions without any special manipulation.
I hope this problem will be solved.
So sorry if my post is not at the right place...

Best regards.
- Eadwine Rose
- Administrator
- Posts: 14471
- Joined: Wed Jul 12, 2006 2:10 am
Re: MX-19 Beta 3 Feedback
Please post quick system info, thank you.
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-19 Beta 3 Feedback
You know what the problem is? Most users install mx19b3 on a VM - just to try it out. I guess very few ppl would risk installing a beta on their "main" PC/Laptop.
I've had a few glitches installing 19 b2.1 on 2 bare-metal Thinkpads, 1 NUC and 1 Latitude - both frech installs and snapshot cloning.
Lenovo's BIOS is the worst - totally geared towards Windows UFI and "scure boot".
With 19b2.1 I managed to ignore the "incorrect settings in minstall.conf" error and finish the install.
Now with 19b3 the installation process is completely broken. Even with "custom install" (after manually creating xt4 and fat32 partitions with Gparted) - I can only progress as far as Grub where it fails.
I'm a professional tester, I know this is a major bug Sev-1 which needs to be fixed urgently. Who cares about the transparency/color of the panel if the install doesn't work?
May I suggest the MX Devs grab a spare Lenovo and try to install on an empty NVMe - hope they get as frustrated as dozens of potential MX users this stupid bug is turning away from otherwise excellent distro!
I've had a few glitches installing 19 b2.1 on 2 bare-metal Thinkpads, 1 NUC and 1 Latitude - both frech installs and snapshot cloning.
Lenovo's BIOS is the worst - totally geared towards Windows UFI and "scure boot".
With 19b2.1 I managed to ignore the "incorrect settings in minstall.conf" error and finish the install.
Now with 19b3 the installation process is completely broken. Even with "custom install" (after manually creating xt4 and fat32 partitions with Gparted) - I can only progress as far as Grub where it fails.
I'm a professional tester, I know this is a major bug Sev-1 which needs to be fixed urgently. Who cares about the transparency/color of the panel if the install doesn't work?
May I suggest the MX Devs grab a spare Lenovo and try to install on an empty NVMe - hope they get as frustrated as dozens of potential MX users this stupid bug is turning away from otherwise excellent distro!
Re: MX-19 Beta 3 Feedback
Please post quick system info, thank you.
edit :Please run MX Tools/Quick System Info, then edit your post above with its pencil icon and paste. (Quick System Info automatically copies the information to your clipboard, already formatted properly for pasting into the forum so all you have to do is a right-click/ paste, not a copy/paste.) Thanks.
Code: Select all
System: Host: zen Kernel: 4.19.0-5-686-pae i686 bits: 32 compiler: gcc v: 6.3.0
Desktop: Xfce 4.12.3 Distro: MX-18.3_386 Continuum May 26 2019
base: Debian GNU/Linux 9 (stretch)
Machine: Type: Laptop System: ASUSTeK product: 1000H v: x.x serial: <filter>
Mobo: ASUSTeK model: 1000H v: x.xx serial: <filter> BIOS: American Megatrends v: 2102
date: 07/21/2009
Battery: ID-1: BAT0 charge: 17.2 Wh condition: 44.5/55.3 Wh (81%) model: ASUS 1000H
status: Charging
CPU: Topology: Single Core model: Intel Atom N270 bits: 32 type: MT arch: Bonnell rev: 2
L2 cache: 512 KiB
flags: nx pae sse sse2 sse3 ssse3 bogomips: 6383
Speed: 868 MHz min/max: 800/1600 MHz Core speeds (MHz): 1: 1116 2: 816
Graphics: Device-1: Intel Mobile 945GSE Express Integrated Graphics vendor: ASUSTeK
driver: i915 v: kernel bus ID: 00:02.0
Display: x11 server: X.Org 1.19.2 driver: intel unloaded: fbdev,modesetting,vesa
resolution: 1024x600~60Hz
OpenGL: renderer: Mesa DRI Intel 945GME x86/MMX/SSE2 v: 1.4 Mesa 18.2.6
direct render: Yes
Audio: Device-1: Intel NM10/ICH7 Family High Definition Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel bus ID: 00:1b.0
Sound Server: ALSA v: k4.19.0-5-686-pae
Network: Device-1: Ralink RT2790 Wireless 802.11n 1T/2R PCIe driver: rt2800pci v: 2.3.0
port: ffa0 bus ID: 01:00.0
IF: wlan0 state: up mac: <filter>
Device-2: Qualcomm Atheros AR8121/AR8113/AR8114 Gigabit or Fast Ethernet
vendor: ASUSTeK driver: ATL1E v: N/A port: ec00 bus ID: 03:00.0
IF: eth0 state: down mac: <filter>
Drives: Local Storage: total: 178.35 GiB used: 4.97 GiB (2.8%)
ID-1: /dev/sda vendor: Seagate model: ST9160827AS size: 149.05 GiB
ID-2: /dev/sdb type: USB vendor: Generic model: Flash Disk size: 29.30 GiB
Partition: ID-1: / size: 67.41 GiB used: 4.97 GiB (7.4%) fs: ext4 dev: /dev/sda2
Sensors: System Temperatures: cpu: 23.0 C mobo: N/A
Fan Speeds (RPM): cpu: 770
Repos: Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http://iso.mxrepo.com/antix/stretch stretch main
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://ftp.fr.debian.org/debian/ stretch-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://ftp.fr.debian.org/debian/ stretch main contrib non-free
2: deb http://security.debian.org/ stretch/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mirror.ibcp.fr/pub/mxlinux/workspace/mx/repo/ stretch main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 168 Uptime: 2m Memory: 1.90 GiB used: 322.6 MiB (16.6%) Init: SysVinit
runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 inxi: 3.0.36
Last edited by Zuul on Mon Oct 07, 2019 5:34 am, edited 5 times in total.
Re: MX-19 Beta 3 Feedback
Please run MX Tools/Quick System Info, then edit your post above with its pencil icon and paste. (Quick System Info automatically copies the information to your clipboard, already formatted properly for pasting into the forum so all you have to do is a right-click/ paste, not a copy/paste.) Thanks.
Please read the Forum Rules, How To Ask For Help, How to Break Your System and Don't Break Debian. Always include your full Quick System Info (QSI) with each and every new help request.