Problem happens with both Q4OS installed in a VM and it installed to bare metal (low spec Asus with an Atom N455). It is Q4OS running the trinity desktop or DE.
Start conky with
conky -d -c /pathtoscript
, it starts and displays as expected, but as soon as you click anyway on the desktop it disappears. It is still running - I can tell, output to the terminal complaining about no battery when running in the VM, and you can grep its PID. Starting the same conky in LM21 (cinnamon) - no issues, behaves.I suspect it is something in the config settings below. I will be playing at random with the various windows/desktop settings so anything to point me in the right direction would be useful:
Code: Select all
conky.config = {
background = false,
use_xft = true;
font = 'Sans:size=8',
xftalpha = 1,
update_interval = 2.0,
total_run_times = 0,
own_window = true,
own_window_class = 'Conky',
own_window_transparent = true,
own_window_argb_visual = true,
own_window_type = 'desktop',
own_window_hints = 'undecorated,below,sticky,skip_taskbar,skip_pager',
double_buffer = true,
minimum_height = 200,
maximum_width = 240,
draw_shades = false,
draw_outline = false,
draw_borders = false,
draw_graph_borders = false,
stippled_borders = 0,
default_color = 'white',
default_shade_color = 'grey',
default_outline_color = 'white',
alignment = 'top_right',
gap_x = 28,
gap_y = 34,
no_buffers = true,
uppercase = false,
cpu_avg_samples = 2,
override_utf8_locale = false,
color0 = 'white',
color1 = 'FCFF69',
color2 = 'CCE6FF',
color3 = 'DAFFB3',
color4 = 'CCFFCC',
color5 = 'FFFF66',
short_units = true,
}
-- end of conky config settings
I'm doing this for a friend (remote) so when trying to fix it on the Asus, I'm having to anydesk in.
Partial inxi on the Asus:
Code: Select all
System:
Host: q4os-desktop Kernel: 5.10.0-21-686-pae i686 bits: 32 compiler: gcc
v: 10.2.1 Desktop: Trinity R14.0.12 tk: Qt 3.5.0 info: kicker wm: Twin 3.0
dm: TDM Distro: Q4OS 4.11.1-n1 base: Debian GNU/Linux 11 (bullseye)
Machine:
Type: Laptop System: ASUSTeK product: 1011PX v: x.x serial: B8OAAS231822
Chassis: type: 10 v: x.x serial: N/A
Mobo: ASUSTeK model: 1015PE v: x.xx serial: EeePC-0123456789
BIOS: American Megatrends v: 1301 date: 05/06/2011
Battery:
ID-1: BAT0 charge: 20.7 Wh condition: 21.2/23.8 Wh (89%) volts: 12.4/10.8
model: ASUS 1015PE type: Li-ion serial: N/A status: Unknown
Memory:
RAM: total: 1.96 GiB used: 438.3 MiB (21.9%)
Array-1: capacity: 4 GiB slots: 2 EC: None max module size: 2 GiB
note: est.
Device-1: DIMM0 size: 2 GiB speed: 667 MT/s type: Other
detail: synchronous bus width: 64 bits total: 64 bits manufacturer: N/A
part-no: N/A serial: N/A
Device-2: DIMM1 size: No Module Installed
CPU:
Info: Single Core model: Intel Atom N455 bits: 64 type: MT arch: Bonnell
rev: A L1 cache: 24 KiB L2 cache: 512 KiB bogomips: 6665
Speed: 1000 MHz min/max: 1000/1667 MHz volts: 1.2 V ext-clock: 167 MHz
Core speeds (MHz): 1: 1000 2: 1000
Flags: acpi aperfmperf apic arch_perfmon bts clflush cmov constant_tsc
cpuid cx16 cx8 de ds_cpl dtes64 dtherm dts est fpu fxsr ht lahf_lm lm mca
mce mmx monitor movbe msr mtrr nx pae pat pbe pdcm pebs pge pni pse sep ss
sse sse2 ssse3 tm tm2 tsc vme xtpr
Graphics:
Device-1: Intel Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics
vendor: ASUSTeK Eee PC 1015PX driver: i915 v: kernel bus ID: 00:02.0
chip ID: 8086:a011 class ID: 0300
Device-2: IMC Networks USB 2.0 UVC VGA WebCam type: USB driver: uvcvideo
bus ID: 1-6:3 chip ID: 13d3:5711 class ID: 0e02 serial: 0x0001
Display: server: X.Org 1.20.11 driver: loaded: intel
unloaded: fbdev,modesetting,vesa resolution: 1024x600~60Hz s-dpi: 120
OpenGL: renderer: Mesa DRI Intel Pineview M x86/MMX/SSE2
v: 1.4 Mesa 20.3.5 direct render: Yes