Default conky on MX-19 Beta 1

[Jerry3904]

It's very hard to find a conky that will work on every system, and we're hoping this one will work for most users. I'm looking for info on how it looks:

--on your screen (Quick System Info if not good)
--in your language (which one?)

If it doesn't work for you, use Conky Manager to select a different one or the Conky Toggle to just turn it off for the rest of the eternity.

Thanks.

[richb]

Alignment off. And text as expected small. But I revised it for my screen.

Code: Select all

System:    Host: mx Kernel: 4.19.0-5-amd64 x86_64 bits: 64 Desktop: Xfce 4.14.1 
           Distro: MX-19beta-1_x64 patito feo August 25  2019 
Machine:   Type: Desktop System: Gigabyte product: N/A v: N/A serial: <root required> 
           Mobo: Gigabyte model: F2A68HM-H v: x.x serial: <root required> UEFI: American Megatrends v: FB date: 04/22/2015 
CPU:       Topology: Quad Core model: AMD A8-7600 Radeon R7 10 Compute Cores 4C+6G bits: 64 type: MCP L2 cache: 2048 KiB 
           Speed: 1397 MHz min/max: 1400/3100 MHz Core speeds (MHz): 1: 1397 2: 1397 3: 1397 4: 1397 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Kaveri [Radeon R7 Graphics] driver: radeon v: kernel 
           Display: x11 server: X.Org 1.20.4 driver: ati,radeon unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz 
           OpenGL: renderer: AMD KAVERI (DRM 2.50.0 4.19.0-5-amd64 LLVM 7.0.1) v: 4.5 Mesa 18.3.6 
Audio:     Device-1: Advanced Micro Devices [AMD/ATI] Kaveri HDMI/DP Audio driver: snd_hda_intel 
           Device-2: Advanced Micro Devices [AMD] FCH Azalia driver: snd_hda_intel 
           Device-3: Logitech Webcam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo 
           Sound Server: ALSA v: k4.19.0-5-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 
           IF: eth0 state: down mac: 40:8d:5c:0d:62:1b 
           Device-2: Qualcomm Atheros AR93xx Wireless Network Adapter driver: ath9k 
           IF: wlan0 state: up mac: 60:e3:27:08:b6:6c 
Drives:    Local Storage: total: 755.94 GiB used: 5.79 GiB (0.8%) 
           ID-1: /dev/sda vendor: Samsung model: SSD 850 EVO 250GB size: 232.89 GiB 
           ID-2: /dev/sdb vendor: Samsung model: SSD 850 EVO 250GB size: 232.89 GiB 
           ID-3: /dev/sdc vendor: Samsung model: SSD 850 EVO 250GB size: 232.89 GiB 
           ID-4: /dev/sdd type: USB vendor: SanDisk model: Ultra size: 57.28 GiB 
Partition: ID-1: / size: 225.99 GiB used: 5.79 GiB (2.6%) fs: ext4 dev: /dev/sda2 
           ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda3 
Sensors:   System Temperatures: cpu: 9.6 C mobo: N/A gpu: radeon temp: 10 C 
           Fan Speeds (RPM): N/A 
Info:      Processes: 215 Uptime: 19m Memory: 14.63 GiB used: 1.43 GiB (9.8%) Shell: bash inxi: 3.0.33 

[JayM]

It looks OK but I question its color scheme of dark blue and green against that lighter blue portion of the default wallpaper. It's not that easy to see vs. if there was more color contrast. Colorblind people may have even more trouble trying to read it. I like its style though.

I didn't try playing with other languages to check its translations as I'm pretty much unilingual and didn't want to be unable to figure out how to change back to English. :)

Code: Select all

System:    Host: mx1 Kernel: 4.19.0-5-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           Desktop: Xfce 4.14.1 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-19beta-1_x64 patito feo August 25  2019 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Desktop Mobo: ASRock model: A780GM-LE serial: <filter> 
           BIOS: American Megatrends v: P1.50 date: 05/25/2010 
CPU:       Topology: Quad Core model: AMD Phenom II X4 925 bits: 64 type: MCP arch: K10 
           family: 10 (16) model-id: 4 stepping: 2 microcode: 10000DB L2 cache: 2048 KiB 
           flags: lm nx pae sse sse2 sse3 sse4a svm bogomips: 20755 
           Speed: 800 MHz min/max: 800/2600 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 1600 
           Vulnerabilities: Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass status: Not affected 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full AMD retpoline, STIBP: disabled, RSB filling 
Graphics:  Device-1: AMD RS780 [Radeon HD 3200] vendor: ASRock driver: radeon v: kernel 
           bus ID: 01:05.0 chip ID: 1002:9610 
           Display: x11 server: X.Org 1.20.4 driver: ati,radeon unloaded: fbdev,modesetting,vesa 
           resolution: 1280x1024~60Hz 
           OpenGL: renderer: AMD RS780 (DRM 2.50.0 / 4.19.0-5-amd64 LLVM 7.0.1) 
           v: 3.3 Mesa 18.3.6 compat-v: 3.0 direct render: Yes 
Audio:     Device-1: AMD SBx00 Azalia vendor: ASRock driver: snd_hda_intel v: kernel 
           bus ID: 00:14.2 chip ID: 1002:4383 
           Sound Server: ALSA v: k4.19.0-5-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASRock 
           driver: r8169 v: kernel port: e800 bus ID: 02:00.0 chip ID: 10ec:8168 
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 1.03 TiB used: 3.45 GiB (0.3%) 
           ID-1: /dev/sda vendor: Gigabyte model: GP-GSTFS31120GNTD size: 111.79 GiB block size: 
           physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 61.3 scheme: MBR 
           ID-2: /dev/sdb vendor: Seagate model: ST1000DM010-2EP102 size: 931.51 GiB block size: 
           physical: 4096 B logical: 512 B speed: 3.0 Gb/s rotation: 7200 rpm serial: <filter> 
           rev: CC43 
           ID-3: /dev/sdc type: USB vendor: Toshiba model: TransMemory size: 14.45 GiB 
           block size: physical: 512 B logical: 512 B serial: <filter> rev: 1.00 scheme: MBR 
Partition: ID-1: / raw size: N/A size: 7.81 GiB used: 41.4 MiB (0.5%) fs: overlay 
           source: ERR-102 
Sensors:   Message: No sensors data was found. Is sensors configured? 
Repos:     Active apt repos in: /etc/apt/sources.list.d/antix.list 
           1: deb http://iso.mxrepo.com/antix/buster buster main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian buster-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian buster main contrib non-free
           2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ buster main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 202 Uptime: 3m Memory: 7.55 GiB used: 510.0 MiB (6.6%) Init: SysVinit 
           v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 
           running in: quick-system-in inxi: 3.0.33 

[chrispop99]

I've tested on four different screen resolutions from 1024x768 and up. It looks fine with regard to the amount of screen estate it uses.

The HiDPI I tested on has a resolution of 3200x1800, and is just about readable at that resolution. It doesn't obey the x2 scaling sadly.

I don't think a predominately blue/green Conky looks great on a predominantly blue/green background; the blues and greens would need to be more closely matched for that to work. I realise that the Beta wallpaper is not necessarily the one Final will use, of course.

Conky Toggle is my first port of call on each new installation, so my aesthetic thoughts are academic at best.

Chris

[Gaer Boy]

Conky appears fine on my display. Something odd happens when I adjust the time to 24-hour. First, when I edit the widget it appears to have 24-hour selected but 12-hour is displayed.

Conky orig.png

Then, if I click Apply to set 24-hour, it does that but also changes the style and layout. Compare:

Conky 1.png

Conky 2.png

Finally, we need to get rid of the am/pm for the 24-hour display.

[fehlix]

Conky appears fine on my display. Something odd happens when I adjust the time to 24-hour. First, when I edit the widget it appears to have 24-hour selected but 12-hour is displayed.
Conky orig.png

Then, if I click Apply to set 24-hour, it does that but also changes the style and layout. Compare:
Conky 1.png
Conky 2.png
Finally, we need to get rid of the am/pm for the 24-hour display.

The 12/24 plus pm-display is solved with the conky itslef, by displaying the proper timeformat defined by your chosen locale. The 12/24 fix using conky-manager will destroy internal conky-pmfix, and will replace all %I (12h) with %H (24%).
So to say: Not the conky as to be fixed, which do already display the timeformat properly , but the "conky-manager fix" has to be fixed, by not touching the already pmfixed-conky lines. :lipsrsealed:

[Gaer Boy]

@fehlix - The conky as installed does not display the time format defined by my locale, or that selected on installation, which is 24-hour. All other displays of time are 24-hour, except the conky.

[fehlix]

@fehlix - The conky as installed does not display the time format defined by my locale, or that selected on installation, which is 24-hour. All other displays of time are 24-hour, except the conky.

What is your locale?

[Gaer Boy]

London. System clock set to display 24hr. I never use 12hr. I will reinstall (for the 7th time) tomorrow morning and check everything carefully but I don't expect to find a difference.

[fehlix]

London. System clock set to display 24hr. I never use 12hr. I will reinstall (for the 7th time) tomorrow morning and check everything carefully but I don't expect to find a difference.

London - that results in a time zone setting of Europe/London.
Show your locale setting:

Code: Select all

echo $LANG

EDIT:
OK, something with the conky:
On commadn line: this is correct:

Code: Select all

TZ=Europe/London LANG=en_GB.UTF-8 date +%c
Tue 27 Aug 2019 19:52:41 BST

But conky shows it wrongly:

conky-time.png

need to dig into this ...