I powered on my spare test "server" and ran this update.
All went fine.
After the reboot I started the fully updated XOA (local installed) and ran it for a few minutes.
then I shut it down but it sat for a few minutes so I did a force shut down from xsconsole.
Rebooted the host again and started the XOA, shut it down and it worked fine
Tested one more time and it went OK.
Best posts made by ph7
-
RE: XCP-ng 8.3 betas and RCs feedback đ
-
RE: XCP-ng 8.3 betas and RCs feedback đ
Upgrade to RC2 worked fine so far with netinstall ISO in ventoy on a 8 gen i5 HP laptop. And a "full" ISO on its own USB on a Lenovo Thinkcentre Ryzen 5 2400GE
-
RE: Performance-Plugin is showing the wrong SR on resolution
@olivierlambert
I have reported a similar issue with the cpu report:
Lots of performance alerts after upgrading XO to commit aa490
https://xcp-ng.org/forum/topic/9658/lots-of-performance-alerts-after-upgrading-xo-to-commit-aa490/14#
-
RE: Need some advice on retention
I have a similar backup strategy
One backup job with 2 schedules
Works fine for me -
RE: XCP-ng 8.3 betas and RCs feedback đ
@ph7 said in XCP-ng 8.3 betas and RCs feedback :
Upgrade to RC2 worked fine so far with netinstall ISO in ventoy on a 8 gen i5 HP laptop. And a "full" ISO on its own USB on a Lenovo Thinkcentre Ryzen 5 2400GE
2 days ago I upgraded my fully patched Ryzen 5 RC1 to RC2 by ISO.
Unfortunately I also upgraded my XO to commit aa490.
All backup jobs since then has triggered CPU performance alerts on my backed up delta, offline VM, XCP-ng host and the VM running XO.
I will update the XO to latest commit today.
Are there any changes in RC2 that could cause this?
I have only received 1 alert on high memory earlier. -
RE: XCP-ng 8.3 betas and RCs feedback đ
@stormi
I ran yum update a few minutes ago and got this:
warning: %triggerin(sm-3.2.3-1.1.xcpng8.3.x86_64) scriptlet failed, exit status 1 Non-fatal <unknown> scriptlet failure in rpm package sm-3.2.3-1.1.xcpng8.3.x86_64
The server started and the VMs seems to be running.
I'm not running iSCSI so i hope its OK -
RE: XCP-ng 8.3 betas and RCs feedback đ
@stormi said in XCP-ng 8.3 beta :
@ph7 I did push a rebuilt netdata for Xen 4.17 yesterday, so it should have worked, but I admit I haven't tested the update process myself so maybe I've missed something.
Can you extract the error messages from the output of
yum history
?yum history
to get the list of operations, andyum history info NUMBER
for the details of a given call.[12:23 X3 ~]# yum history InlĂ€sta insticksmoduler: fastestmirror ID | Kommandorad | Datum och tid | Ă tgĂ€rd(er) | Ăndrade ------------------------------------------------------------------------------- 11 | update --disablerepo=* - | 2024-04-23 00:29 | I, U | 53 EE 10 | remove netdata-ui.x86_64 | 2024-04-23 00:26 | Erase | 2 9 | update --disablerepo=* - | 2024-04-18 18:11 | Update | 21 8 | update --disablerepo=* - | 2024-04-04 17:50 | Update | 1 7 | reinstall netdata.x86_64 | 2024-04-03 16:41 | Reinstall | 1 6 | reinstall netdata-ui | 2024-04-03 16:34 | Reinstall | 1 5 | --enablerepo=* install n | 2024-03-30 11:41 | Install | 1 4 | update --disablerepo=* - | 2024-03-29 14:13 | Update | 21 3 | install netdata-ui | 2024-03-23 13:59 | Install | 9 EE 2 | update --disablerepo=* - | 2024-03-01 16:00 | Update | 6 1 | update --disablerepo=* - | 2024-02-29 22:12 | I, UF, U | 63 history list --------------------------- [12:23 X3 ~]# yum history info NUMBER 10 InlĂ€sta insticksmoduler: fastestmirror Transaktions-ID: 10 Starttid : Tue Apr 23 00:26:27 2024 Start-rpmdb : 548:9dff1ffa674baaf209143925833d8346df54beac Sluttid : 00:27:27 2024 (60 sekunder) Slut-rpmdb : 546:17e105aef8586ef4615b3761b221b4051cc02275 AnvĂ€ndare : System <ej satt> Returkod : Lyckades Kommandoradsfel: remove netdata-ui.x86_64 netdata.x86_64 Transaktionen utförd med: Installerade rpm-4.11.3-32.el7.x86_64 @xcp:main/$releasever Installerade yum-3.4.3-158.el7.centos.noarch @xcp:main/$releasever Installerade yum-plugin-fastestmirror-1.1.31-46.el7_5.noarch @xcp:main/$releasever Ăndrade paket: Radering netdata-1.19.0-6.xcpng8.3.x86_64 @xcp-ng-base Radering netdata-ui-1.19.0-6.xcpng8.3.x86_64 @xcp-ng-base history info Excluding mirror: updates.xcp-ng.org * xcp-ng-updates: mirrors.xcp-ng.org Uppdaterade intel-ice-1.11.17.1-1.xcpng8.3.x86_64 @?xcp-ng-base Uppdatering 1.11.17.1-2.xcpng8.3.x86_64 @xcp-ng-base Uppdaterade intel-microcode-20231009-1.xcpng8.3.noarch @xcp-ng-base Uppdatering 20240130-1.xcpng8.3.noarch @xcp-ng-base Uppdaterade kernel-4.19.19-8.0.32.1.xcpng8.3.x86_64 @xcp-ng-base Uppdatering 4.19.19-8.0.33.1.xcpng8.3.x86_64 @xcp-ng-base Uppdaterade kexec-tools-1:2.0.15-18.xcpng8.3.x86_64 @?xcp-ng-base Uppdatering 1:2.0.15-19.xcpng8.3.x86_64 @xcp-ng-base Uppdaterade libcgroup-0.41-15.el7.x86_64 @?xcp-ng-base Uppdatering 0.41-21.el7.x86_64 @xcp-ng-base Uppdaterade libcgroup-tools-0.41-15.el7.x86_64 @?xcp-ng-base Uppdatering 0.41-21.el7.x86_64 @xcp-ng-base Uppdaterade message-switch-23.31.0-1.7.xcpng8.3.x86_64 @xcp-ng-base Uppdatering 24.11.0-1.2.xcpng8.3.x86_64 @xcp-ng-base Uppdaterade python2-xapi-storage-23.31.0-1.7.xcpng8.3.x86_64 @xcp-ng-base Uppdatering 24.11.0-1.2.xcpng8.3.x86_64 @xcp-ng-base Ber-inst python3-scapy-2.4.5-3.xcpng8.3.noarch @xcp-ng-base Uppdaterade qemu-2:4.2.1-5.2.4.xcpng8.3.x86_64 @xcp-ng-base Uppdatering 2:4.2.1-5.2.7.xcpng8.3.x86_64 @xcp-ng-base Uppdaterade qlogic-fastlinq-8.55.13.0-1.xcpng8.3.x86_64 @?xcp-ng-base Uppdatering 8.74.0.2-1.xcpng8.3.x86_64 @xcp-ng-base Uppdaterade rrdd-plugins-23.31.0-1.7.xcpng8.3.x86_64 @xcp-ng-base Uppdatering 24.11.0-1.2.xcpng8.3.x86_64 @xcp-ng-base Uppdaterade sm-3.0.12-6.2.xcpng8.3.x86_64 @xcp-ng-base Uppdatering 3.0.12-12.2.xcpng8.3.x86_64 @xcp-ng-base Uppdaterade sm-cli-23.31.0-1.7.xcpng8.3.x86_64 @xcp-ng-base Uppdatering 24.11.0-1.2.xcpng8.3.x86_64 @xcp-ng-base Uppdaterade squeezed-23.31.0-1.7.xcpng8.3.x86_64 @xcp-ng-base Uppdatering 24.11.0-1.2.xcpng8.3.x86_64 @xcp-ng-base Uppdaterade varstored-1.2.0-1.3.xcpng8.3.x86_64 @?xcp-ng-base Uppdatering 1.2.0-2.2.xcpng8.3.x86_64 @xcp-ng-base Uppdaterade varstored-guard-23.31.0-1.7.xcpng8.3.x86_64 @xcp-ng-base Uppdatering 24.11.0-1.2.xcpng8.3.x86_64 @xcp-ng-base Uppdaterade varstored-tools-1.2.0-1.3.xcpng8.3.x86_64 @?xcp-ng-base Uppdatering 1.2.0-2.2.xcpng8.3.x86_64 @xcp-ng-base Uppdaterade vcputune-2.0.1-5.xcpng8.3.noarch @?xcp-ng-base Uppdatering 2.0.2-1.xcpng8.3.noarch @xcp-ng-base Uppdaterade vhd-tool-23.31.0-1.7.xcpng8.3.x86_64 @xcp-ng-base Uppdatering 24.11.0-1.2.xcpng8.3.x86_64 @xcp-ng-base Uppdaterade vncterm-10.2.0-3.xcpng8.3.x86_64 @?xcp-ng-base Uppdatering 10.2.1-2.xcpng8.3.x86_64 @xcp-ng-base Uppdaterade wsproxy-23.31.0-1.7.xcpng8.3.x86_64 @xcp-ng-base Uppdatering 24.11.0-1.2.xcpng8.3.x86_64 @xcp-ng-base Uppdaterade xapi-core-23.31.0-1.7.xcpng8.3.x86_64 @xcp-ng-base Uppdatering 24.11.0-1.2.xcpng8.3.x86_64 @xcp-ng-base Uppdaterade xapi-nbd-23.31.0-1.7.xcpng8.3.x86_64 @xcp-ng-base Uppdatering 24.11.0-1.2.xcpng8.3.x86_64 @xcp-ng-base Uppdaterade xapi-rrd2csv-23.31.0-1.7.xcpng8.3.x86_64 @xcp-ng-base Uppdatering 24.11.0-1.2.xcpng8.3.x86_64 @xcp-ng-base Uppdaterade xapi-storage-script-23.31.0-1.7.xcpng8.3.x86_64 @xcp-ng-base Uppdatering 24.11.0-1.2.xcpng8.3.x86_64 @xcp-ng-base Uppdaterade xapi-tests-23.31.0-1.7.xcpng8.3.x86_64 @xcp-ng-base Uppdatering 24.11.0-1.2.xcpng8.3.x86_64 @xcp-ng-base Uppdaterade xapi-xe-23.31.0-1.7.xcpng8.3.x86_64 @xcp-ng-base Uppdatering 24.11.0-1.2.xcpng8.3.x86_64 @xcp-ng-base Uppdaterade xcp-clipboardd-1.0.3-7.xcpng8.3.x86_64 @?xcp-ng-base Uppdatering 1.0.3-8.xcpng8.3.x86_64 @xcp-ng-base Uppdaterade xcp-featured-1.1.6-3.xcpng8.3.x86_64 @xcp-ng-base Uppdatering 1.1.6-4.xcpng8.3.x86_64 @xcp-ng-base Uppdaterade xcp-networkd-23.31.0-1.7.xcpng8.3.x86_64 @xcp-ng-base Uppdatering 24.11.0-1.2.xcpng8.3.x86_64 @xcp-ng-base Uppdaterade xcp-ng-release-8.3.0-18.x86_64 @xcp-ng-base Uppdatering 8.3.0-19.x86_64 @xcp-ng-base Uppdaterade xcp-ng-release-config-8.3.0-18.x86_64 @xcp-ng-base Uppdatering 8.3.0-19.x86_64 @xcp-ng-base Uppdaterade xcp-ng-release-presets-8.3.0-18.x86_64 @xcp-ng-base Uppdatering 8.3.0-19.x86_64 @xcp-ng-base Uppdaterade xcp-rrdd-23.31.0-1.7.xcpng8.3.x86_64 @xcp-ng-base Uppdatering 24.11.0-1.2.xcpng8.3.x86_64 @xcp-ng-base Uppdaterade xen-crashdump-analyser-2.5.6-1.xcpng8.3.x86_64 @?xcp-ng-base Uppdatering 2.6.1-1.xcpng8.3.x86_64 @xcp-ng-base Uppdaterade xen-dom0-libs-4.13.5-10.58.xcpng8.3.x86_64 @xcp-ng-base Uppdatering 4.17.3-4.xcpng8.3.x86_64 @xcp-ng-base Uppdaterade xen-dom0-tools-4.13.5-10.58.xcpng8.3.x86_64 @xcp-ng-base Uppdatering 4.17.3-4.xcpng8.3.x86_64 @xcp-ng-base Uppdaterade xen-hypervisor-4.13.5-10.58.xcpng8.3.x86_64 @xcp-ng-base Uppdatering 4.17.3-4.xcpng8.3.x86_64 @xcp-ng-base Uppdaterade xen-libs-4.13.5-10.58.xcpng8.3.x86_64 @xcp-ng-base Uppdatering 4.17.3-4.xcpng8.3.x86_64 @xcp-ng-base Uppdaterade xen-tools-4.13.5-10.58.xcpng8.3.x86_64 @xcp-ng-base Uppdatering 4.17.3-4.xcpng8.3.x86_64 @xcp-ng-base Uppdaterade xenopsd-23.31.0-1.7.xcpng8.3.x86_64 @xcp-ng-base Uppdatering 24.11.0-1.2.xcpng8.3.x86_64 @xcp-ng-base Uppdaterade xenopsd-cli-23.31.0-1.7.xcpng8.3.x86_64 @xcp-ng-base Uppdatering 24.11.0-1.2.xcpng8.3.x86_64 @xcp-ng-base Uppdaterade xenopsd-xc-23.31.0-1.7.xcpng8.3.x86_64 @xcp-ng-base Uppdatering 24.11.0-1.2.xcpng8.3.x86_64 @xcp-ng-base Uppdaterade xenserver-status-report-1.3.14-1.xcpng8.3.noarch @xcp-ng-base Uppdatering 2.0.3-1.xcpng8.3.noarch @xcp-ng-base Skriptutdata: 1 warning: /etc/sysconfig/xencommons saved as /etc/sysconfig/xencommons.rpmsave history info -------------------------- [12:25 X3 ~]# yum history info NUMBER 11 InlĂ€sta insticksmoduler: fastestmirror Transaktions-ID: 11 Starttid : Tue Apr 23 00:29:47 2024 Start-rpmdb : 546:17e105aef8586ef4615b3761b221b4051cc02275 Sluttid : 00:31:19 2024 (92 sekunder) Slut-rpmdb : 547:ab22718930a5c79c4616bc82131af44e4ed6cb50 AnvĂ€ndare : System <ej satt> Returkod : Lyckades Kommandoradsfel: update --disablerepo=* --enablerepo=xcp-ng-base,xcp-ng-updates -y Transaktionen utförd med: Installerade rpm-4.11.3-32.el7.x86_64 @xcp:main/$releasever Installerade yum-3.4.3-158.el7.centos.noarch @xcp:main/$releasever Installerade yum-plugin-fastestmirror-1.1.31-46.el7_5.noarch @xcp:main/$releasever Ăndrade paket: Uppdaterade blktap-3.54.6-2.1.xcpng8.3.x86_64 @xcp-ng-base Uppdatering 3.54.6-3.1.xcpng8.3.x86_64 @xcp-ng-base Uppdaterade edk2-20220801-1.7.3.2.xcpng8.3.x86_64 @xcp-ng-base Uppdatering 20220801-1.7.4.1.xcpng8.3.x86_64 @xcp-ng-base Uppdaterade forkexecd-23.31.0-1.7.xcpng8.3.x86_64 @xcp-ng-base Uppdatering 24.11.0-1.2.xcpng8.3.x86_64 @xcp-ng-base Uppdaterade gpumon-0.25.0-6.1.xcpng8.3.x86_64 @xcp-ng-base Uppdatering 0.25.0-14.1.xcpng8.3.x86_64 @xcp-ng-base Uppdaterade guest-templates-json-2.0.6-1.1.xcpng8.3.noarch @xcp-ng-base Uppdatering 2.0.9-1.1.xcpng8.3.noarch @xcp-ng-base Uppdaterade guest-templates-json-data-linux-2.0.6-1.1.xcpng8.3.noarch @xcp-ng-base Uppdatering 2.0.9-1.1.xcpng8.3.noarch @xcp-ng-base Uppdaterade guest-templates-json-data-other-2.0.6-1.1.xcpng8.3.noarch @xcp-ng-base Uppdatering 2.0.9-1.1.xcpng8.3.noarch @xcp-ng-base Uppdaterade guest-templates-json-data-windows-2.0.6-1.1.xcpng8.3.noarch @xcp-ng-base Uppdatering 2.0.9-1.1.xcpng8.3.noarch @xcp-ng-base Loading mirror speeds from cached hostfile Excluding mirror: updates.xcp-ng.org * xcp-ng-base: mirrors.xcp-ng.org --------------------------- I also got the result from my update when I discovered net netdata issue: yum update --disablerepo=* --enablerepo=xcp-ng-base,xcp-ng-updates -y ....... Fel: Paket: netdata-1.19.0-6.xcpng8.3.x86_64 (@xcp-ng-base) Behöver: libxenlight.so.4.13()(64bit) Tar bort: xen-dom0-libs-4.13.5-10.58.xcpng8.3.x86_64 (@xcp-ng-base) libxenlight.so.4.13()(64bit) Uppdaterat av: xen-dom0-libs-4.17.3-4.xcpng8.3.x86_64 (xcp-ng-base) ~libxenlight.so.4.17()(64bit) TillgĂ€ngliga: xen-dom0-libs-4.13.4-10.27.xcpng8.3.x86_64 (xcp-ng-base) libxenlight.so.4.13()(64bit) TillgĂ€ngliga: xen-dom0-libs-4.13.4-10.35.xcpng8.3.x86_64 (xcp-ng-base) libxenlight.so.4.13()(64bit) TillgĂ€ngliga: xen-dom0-libs-4.13.4-10.36.xcpng8.3.x86_64 (xcp-ng-base) libxenlight.so.4.13()(64bit) TillgĂ€ngliga: xen-dom0-libs-4.13.5-10.40.xcpng8.3.x86_64 (xcp-ng-base) libxenlight.so.4.13()(64bit) TillgĂ€ngliga: xen-dom0-libs-4.13.5-10.42.xcpng8.3.x86_64 (xcp-ng-base) libxenlight.so.4.13()(64bit) TillgĂ€ngliga: xen-dom0-libs-4.13.5-10.42.1.xcpng8.3.x86_64 (xcp-ng-base) libxenlight.so.4.13()(64bit) TillgĂ€ngliga: xen-dom0-libs-4.13.5-10.42.3.xcpng8.3.x86_64 (xcp-ng-base) libxenlight.so.4.13()(64bit) TillgĂ€ngliga: xen-dom0-libs-4.13.5-10.51.xcpng8.3.x86_64 (xcp-ng-base) libxenlight.so.4.13()(64bit) Fel: Paket: netdata-1.19.0-6.xcpng8.3.x86_64 (@xcp-ng-base) Behöver: libxenstat.so.4.13()(64bit) Tar bort: xen-dom0-libs-4.13.5-10.58.xcpng8.3.x86_64 (@xcp-ng-base) libxenstat.so.4.13()(64bit) Uppdaterat av: xen-dom0-libs-4.17.3-4.xcpng8.3.x86_64 (xcp-ng-base) ~libxenstat.so.4.17()(64bit) TillgĂ€ngliga: xen-dom0-libs-4.13.4-10.27.xcpng8.3.x86_64 (xcp-ng-base) libxenstat.so.4.13()(64bit) TillgĂ€ngliga: xen-dom0-libs-4.13.4-10.35.xcpng8.3.x86_64 (xcp-ng-base) libxenstat.so.4.13()(64bit) TillgĂ€ngliga: xen-dom0-libs-4.13.4-10.36.xcpng8.3.x86_64 (xcp-ng-base) libxenstat.so.4.13()(64bit) TillgĂ€ngliga: xen-dom0-libs-4.13.5-10.40.xcpng8.3.x86_64 (xcp-ng-base) libxenstat.so.4.13()(64bit) TillgĂ€ngliga: xen-dom0-libs-4.13.5-10.42.xcpng8.3.x86_64 (xcp-ng-base) libxenstat.so.4.13()(64bit) TillgĂ€ngliga: xen-dom0-libs-4.13.5-10.42.1.xcpng8.3.x86_64 (xcp-ng-base) libxenstat.so.4.13()(64bit) TillgĂ€ngliga: xen-dom0-libs-4.13.5-10.42.3.xcpng8.3.x86_64 (xcp-ng-base) libxenstat.so.4.13()(64bit) TillgĂ€ngliga: xen-dom0-libs-4.13.5-10.51.xcpng8.3.x86_64 (xcp-ng-base) libxenstat.so.4.13()(64bit) Du kan försöka anvĂ€nda --skip-broken för att gĂ„ runt problemet Du kan försöka köra: rpm -Va --nofiles --nodigest
Sorry for the Swedish languish and the long text
Do You need a translation ???? -
RE: XCP-ng 8.3 betas and RCs feedback đ
@stormi
No stats in XO-lite v0.1.7 (0d127) , as you probably already know
Latest posts made by ph7
-
RE: Bug?? Tree view XO v6
@Danp
Yes of course You are correct
I moved it to local storage a few weeks ago
My bad -
Bug?? Tree view XO v6
Hi
Just updated XO (from docs non script) to commit ff118
And also updated v6
$ /root/xen-orchestra/node_modules/.bin/turbo run build --filter @xen-orchestra/web
I see a strange behavior in the tree view
The XOA is not in line with the other halted VMs
-
RE: Lots of performance alerts after upgrading XO to commit aa490
@ph7 said in Lots of performance alerts after upgrading XO to commit aa490:
@olivierlambert
One strange note when I get the alarms on e-mail during a full backup of my running XOAlert: vm cpu usage > 65%, XO 67,8%
End of alert: vm cpu usage > 65% SyncMate 0,3%
End of alert is the wrong VM, should be XO.
In Dashboard/Health it's OK, it says XO in both alert and end of alert ??Not a big deal for me, but I thought might as well report it
I added a new VM and put it in a backup job (which had a concurrency of 2) and got these new alerts:
ALERT: VM CPU usage > 80% XO5: 80.4%
End of alert: vm cpu usage > 80% HomeAssistant: 6,7%
It seems like the reporting has changed and is reporting the latest VM.The host alert is reporting in the same way
ALERT: host memory usage > 90% X2 đ: 92.7% used
END OF ALERT: host memory usage > 90% X1: 11.3%
I have changed all jobs to concurrency 1 and I have not got any SR alert
-
RE: Lots of performance alerts after upgrading XO to commit aa490
@MathieuRA
Yes, All running hosts and all running VMs -
Failed unmounting remotes at XO/XOA shutdown
Hi
This has been going on for several month i think.Every now and then the XO and XOA can not umount the remotes at powerdown/reboot but they will shut down after a time out of 2-3 minutes
I have 2 remotes, NFS with option hard on a QNAP and SMB on a TrueNAS scale. Seems like both fail the umount.
Same on XOA 5.99.1 and XO latest ba375 from source (docs not script).If I
ls
a mount point, I get this
ph7@XO:/run/xo-server/mounts/0927f4dc-4476-4ac3-959a-bc37e85956df$ ls xo-config-backups xo-pool-metadata-backups xo-vm-backups
If I do als -a
, I also get a lot of .nfs00000000 and .keeper_ files, all 0 bytes and some are older than the existing backups. In an attempt to fix this, I manually deleted some old empty backups, so I guess the old ones origin from them.I am running a Lenovo Thinkcentre mini PC with Ryzen 5 2400GE 16GB, XCP-ng 8.3 latest, upgraded from RC2 by ISO
The issue was also in RC2 and maybe RC1, I donÂŽt remember.Anybody got any idea where to look ?
Is there a way to change the SMB BR to NFS ??
Perhaps create a new NFS BR, copy all files, Connect to new NFS BR and forget the SMB BR. Is that possible ??? -
RE: XCP-ng firewall
@Byte0
Hi
There was a time this summer or spring when NUT-server was unavailable from the repo.
I decided to follow the "don't fiddle with dom0"
I let a mini server control theUPS
and remotely activate a script on the host at power failure.
edit: changed USB > UPS -
RE: Performance-Plugin is showing the wrong SR on resolution
@olivierlambert
I have reported a similar issue with the cpu report:
Lots of performance alerts after upgrading XO to commit aa490
https://xcp-ng.org/forum/topic/9658/lots-of-performance-alerts-after-upgrading-xo-to-commit-aa490/14#
-
RE: Understanding delta backups with different schedules
@stephane-m-dev
In the schedule You can selectforce full backup
-
RE: Wrong colours in dashboard
More screenshots
This is from my Lenovo host:
And lightmode:
Here they are black and purple.
I swithed back to dark mode but stilldark
barsAnd from the old HP:
I think the
light
colour is light purple and thedark
is black or dark blue. -
RE: Wrong colours in dashboard
@john-c
I'm on a Dell laptop with debian + cinnamon noting done with the display.
I tested from a HP laptop with w10 but this time the LMDE was light:
Hosts
X2dark
VMs
LMDElight
HAlight