MX-19 Feedback

[davemx]

Where can I get hold of a copy of the 43-bit version? Sounds interesting!

Because I made a mistake and left.them on the 43 bit iso.

Grr...

[Stevo]

yeah you're right.
I saw someone has reported the same virtualbox theming issue sometime around 2018 in manjaro forums. not sure if it's now fixed or not though.


EDIT: found the ticket > https://www.virtualbox.org/ticket/18258

I had the same virtualbox 6.X theme issue on my MX 19 with the a dark theme, but this setting fixes it for me (edit the menu item and use this for the command:)

VirtualBox -style fusion %U

-gtk and -qt styles don't work any longer, but maybe I'm missing a Qt package. If this solves it for everyone, we could add the fix to the wiki or the FAQs.

We also have an updated virtualbox 5.2.34 in the experimental repo that will follow the system theme, if you want to go that route.

thank you Stevo ! that solved the issue

Having installed qt-style-kvantum and configured it, and KDE to use it, I now find that it's also now a style option for Vbox in XFCE---so it's back to my preferred dark interface instead of glaring white.

[asqwerth]

Having installed qt-style-kvantum and configured it, and KDE to use it, I now find that it's also now a style option for Vbox in XFCE---so it's back to my preferred dark interface instead of glaring white.

So kvantum manager has a setting to sort out Vbox stying for users using XFCE?

[i_ri]

Hello Everyone
.* Temperature *. conky.

Code: Select all

-MX-APInfo/AP-info-debianUpdates-coloursMod-oldsyntx. "SYS TEMP:" method hwmon temp 1;empty print.
-MXBritPanel/conkyrc. "CPU Temperature:" method acpitemp; print 0 (zero. no help)  "HDD Temperature:" shows in the preview image but is nowhere in the script. 
-Clockrings/conkyrc. "temp:" is in the preview image but is nowhere in the script.  This one might mean weather outdoors and sunny.  
-MX-Conkypatch/conky.conf. thermometer icons method acpitemp; print 0 (zero. no help) 
-MX-CoreBlue/conkyrc2core. "Temp:" method acpitemp; print 0. (zero. no help) 
-MX-Flair/System-flair-Updated.  thermometer icon method acpitemp; print 0. (zero. no help.) 
-MX-Futuriste/conky-futuriste-6.  "TEMP" method hwmon temp 1; empty print.  
-MX-KoO/MX-Full. "CPU - " method sensors | grep 'Core 0' | cut -c18-24; print .0-C. CHANGING the cut parameters of 18-24 TO 15-22 WORKS. = method sensors | grep 'Core 0' | cut -c15-22 this works.  or use method sensors | awk '/Core 0/ {print $3}' this works.  
-MX-LSD/lsd2/conkyrc.  "Temperature:" no code present in script; empty. 
-MX-Manyroads/cpufile. "Temperature:"  method hwmon 1 temp 1; empty print.  
-MX-MyConky/MySysInfoConky.  "Temperature:" method hwmon 1 temp1; empty print.  
-MX-RelojPack/Bar/.conkyrc.  "CPU  -C" method hwmon 0 temp 1; empty print.  

In MX-19_64
Made a check into conky list with one thing of focus: temperature. Any where it said temperature on a conky the function is checked. checked live and installed.
Live usb with lean bootcodes I thought was the missing link; now after install starting all services is this check of display of hardware temperatures in conky.

In screenshots of other members is seen temperature values in the conky that are not working on this machine.To get these hardware temperatures readings functioning in MX-19 on this machine is it a process of adding a package? starting a service? or change the model of script?

[Eadwine Rose]

Please post the Quick system info from MX Tools, could be you need something extra to get your sensors seen.


Also, the output of

Code: Select all

sensors

[i_ri]

Hello Eadwine Rose
fresh MX-19_64 all upgraded install.
inxi shows temps, gkrellm shows temps, hardinfo shows temps, everything shows temps but not conky. conky is getting no meaning from acpitemp, hwmon, coretemp… hddtemp sda returns N/A
awk can grab from sensors in this simple case two values of field, but the conky options are not working? The correct script is?
This machine for cpu temps has two values: coretemp/temp2 and coretemp/temp4; that is sensors -u Core0: temp2_input and Core2: temp4_input.

Code: Select all

$ sensors
coretemp-isa-0000
Adapter: ISA adapter
Core 0:       +34.0°C  (high = +89.0°C, crit = +105.0°C)
Core 2:       +31.0°C  (high = +89.0°C, crit = +105.0°C)

f71858fg-isa-0a00
Adapter: ISA adapter
+3.3V:        +3.34 V  
3VSB:         +3.36 V  
Vbat:         +3.30 V  
fan1:         847 RPM
fan2:         901 RPM
fan3:           0 RPM  ALARM
temp1:        +33.8°C  (high = +70.0°C, hyst = +60.0°C)
temp2:        +14.8°C  (high = +100.0°C, hyst = +85.0°C)
temp3:        +38.5°C  (high = +100.0°C, hyst = +85.0°C)

hithere@WallEp6330f:~/Desktop
$ sensors | awk '/Core 0/ {print $3}'
+34.0°C
hithere@WallEp6330f:~/Desktop
$ inxi
CPU: Dual Core Intel Core i3 530 (-MT MCP-) speed/min/max: 1433/1200/2933 MHz 
Kernel: 4.19.0-6-amd64 x86_64 Up: 33m Mem: 535.7/7841.3 MiB (6.8%) Storage: 1.82 TiB (0.3% used) 
Procs: 204 Shell: bash 5.0.3 inxi: 3.0.36 
hithere@WallEp6330f:~/Desktop
$ inxi -s
Sensors:   System Temperatures: cpu: 33.8 C mobo: 14.6 C 
           Fan Speeds (RPM): cpu: 858 fan-2: 901 fan-3: 0 

[Eadwine Rose]

You'll likely have to fiddle and play with the different wordings in that conky to get your numbers to show up in it. So.. not coretemp but something else.


For instance I have to use Tdie to get my CPU temp to show. Sensors tells me that.

[i_ri]

Hello Eadwine Rose. Thank You. will bash. looks like inxi is grabbing the sensors temp3 in this case for single temperature reporting.
Wish to You Have a happy day.

[Eadwine Rose]

So then you have to change the code in conky so it also grabs temp3.

[Stevo]

Having installed qt-style-kvantum and configured it, and KDE to use it, I now find that it's also now a style option for Vbox in XFCE---so it's back to my preferred dark interface instead of glaring white.

So kvantum manager has a setting to sort out Vbox stying for users using XFCE?

Let me see what happens in a virtual machine without KDE installed. I know you can install SMPlayer or QMPlay2 and see what Qt styles are available in their appearance settings, but stay away from those "bb10" styles--they are evil. The Buster Kvantum also doesn't support Qt 4 apps, AFAIK, since it's being dropped upstream, but my backport of a newer version in the MX 19 test repo should.