Hi, this is all from R4.3. I’ll start with the most important things:
1 Sys-whonix has extreme CPU usage before internet connection, and also some time after losing internet connection
To fix: Debug sys-whonix.
I spent 1-2 hours doing experiments and writing down notes.. until I realized the problem is sys-whonix. It eats 60% CPU like an american eats hamburgers when it’s disconnected from the the internet. The fans blow like crazy and laptop heats up, until I shut down the qube. It seems a little inconsistent; one time I restarted the PC and left whonix on. The CPU usage stopped after 70 seconds. Typically it just stays at 60% CPU forever, until I shut down
2 Fully charging battery permanently stops charging capability
To fix: I’m willing to do further tests if given instructions, as this may be a problem with my laptop only. To replicate: Let the battery fully charge (while PC is off/in suspend), until charging turns off.
Either the PC was off or it was in suspend mode. Either way, I left the charger attached over night, and afterwards, it wouldn’t load. I had to manually open laptop to disconnect, start pc, on charger, then turn off pc/unplug charger and reconnect battery. Then it worked again fine. When you turn the laptop on and it won’t turn on, either re-attach the laptop lid or press the “power switch” button on your motherboard (is pressed down by laptop lid.
3 Attaching mouse to a qube is buggy: The mouse’s cursor is invisible
To fix: Debug. To replicate: Attach a mouse to any qube. The mouse’s cursor inside a qube isn’t visible, though clicking and scrolling works fine. Also, when I attach a mouse, it only asks to connect it to dom0.
I want to attach my mouse the qubes instead of dom0, because I’m afraid of it buying evil and installing malware on my dom0 system. But the cursor for the mouse is invisible on the cube. Clicking and scrolling works fine.
MORE BUGS!
4 Right-click Menus + Desktop Swapping is bugged.
Todo: Debug. To replicate, right click inside any Qubes App (e.g. Thunar) to open a right-click menu. Then switch the desktop.
2 Bugs happen:
A: The right-click menu follows to the next desktop.
B: Clicking outside the right-click menu, e.g. the dom0 desktop, won’t close the menu. If you switch back to the original desktop where it was opened, this works again again.
Note: Does this also happen with two monitors? Open context in screen one, click on desktop in screen two to try and close.
5 Dom0 task manager and most cli tools (top, vmstat, cat /proc/meminfo), show incorrect RAM/CPU (only shows that of dom0)
To fix: Debug task manager in dom0, and/or whatever cli tools the task amanger uses, see full system RAM/CPU usage.
Explanation: Confuse the hell out of me, spent some time on this. The task manager showed 15% CPU while my fans were crazy from sys-whonix. The task manager also showed that I had “3.8 GB”. Since I have 2x4 GB sticks, so I thought that 1 of them wasn’t recognized. Eventually, I realized that the Qubes icon on the desktop bar shows how much RAM and CPU each qube has.
6 Screenshots don’t save to clipboard
To fix: Debug code. To replicate, press PrintScr and select “copy to clipboard”. It won’t get pasted, the clipboard says is empty.
7 Qubes dom0 XFCE uses BIOS beeps instead speakers
To fix: Is this intentional? To replicate: Go to any menu in dom0 with input box, e.g. Alt+F3 Program Finder. Press backspace in the entry field. It makes BIOS beep.
8 Nevermind, this one works again..
9 Dom0 desktop bar, symbols in top right don’t increase in size with DPI settings
To fix: Debug code. To replicate: Open Settings Manger (dom0), then after Appeareance, lastly Fonts. Change the “DPI” setting. Everything in the UI will increase in size, except for the top-right symbols. On a big screen, these are hard to click on.
10 Dom0 desktop bar, top right corner is missing “keyboard language” selection + shortcut to change language is missing my default
To fix: Add them. It’s standard on windows and good to have, to quickly change language with mouse. Maybe I misremember, but I think the shortcut to switch language was empty and I needed to set it up.
11 Update for standalone qube failed, but no option to update after
To fix: Debug code. To replicate: Update a standalone qube while the qube is running. Let the error happen “qube is already running”. Then close the qube and open update again. This time, the qube won’t appear as an option on the list of things to update. Everything else updated successfully btw.