You're welcome. :KS
For what it's worth, to clarify, that .9 is related to how many times gcc had been updated specifically for Ubuntu 16.04 at that point. It has nothing to do with the...
Type: Posts; User: halogen2; Keyword(s):
You're welcome. :KS
For what it's worth, to clarify, that .9 is related to how many times gcc had been updated specifically for Ubuntu 16.04 at that point. It has nothing to do with the...
Yes, it is OK, if you install the System76 Driver in your new Kubuntu installation.
Also see this related thread.
Nice find, thank you 1fallen :KS Their summarizing various distros' responses was helpful and led to an answer: Following from there, the distros that resolved this by reverting to an older xz...
Thanks 1fallen for posting this.
Unfortunately my Arch Linux server VM picked up the compromised xz 5.6.0 during a big migration. Although this is a local testing server only accessible by the VM...
What "old Xenial" did you install? It looks like gcc-5 version 5.4.0-6ubuntu1~16.04.9 should be included in the Ubuntu 16.04.4 ISO from here
ClamAV is not the way to check whether a Linux system is compromised, especially if ClamAV is installed on the system you're scanning. That's a recipe for a false sense of security.
See this post...
I should have explained why I suggested trying it "as a test":
If graphics works, and Pop!_OS 22.04 meets OP's needs, it is the easiest way to get 6.8 kernel with a 22.04 base on non-System76...
Does it work to instead put that command at the end of .bashrc?
So as a test, does Pop!_OS 22.04 work? It is based on Ubuntu 22.04, currently uses 6.8 kernel, and has a Nvidia-specific ISO image.
Have you looked into Mullvad Browser, which is based on Firefox ESR and designed to limit fingerprinting?
Thanks again to all for the help and info! :KS Think this is finally good to go.
To summarize the solution:
Using the libvirt NAT network type worked after installing iptables-nft (from...
Although less than ideal, I decided to live with a 1440x900 GRUB for now, as 1440x900 is "close enough" to the desired resolution.
That link is the key to setting custom guest resolution in...
Thanks all for the clarifications :KS So a bridge will only forward packets between the interfaces that are explicitly connected to the bridge, so passing anything else to the bridge and its network...
:confused:
Could you please elaborate on this?
Based on attempting to read this (but don't currently have enough networking knowledge to get my head around everything written there), I thought...
If I manually create a bridge interface in nm-connection-editor, don't add any other interfaces to it, and set up VMs with Bridge networking to this interface, can I be sure this is a host-only...
Do you have the affected browsers installed as flatpaks? If so, you could try installing flatseal and explicitly adding Filesystem access to your download folder for each of the browsers.
Had partial success with this method: It works perfectly for TTYs, and the correct resolution is now an available option in xfce4 Display settings (which selecting that option does work, but only for...
Actually that does help on my Debian 11 / Trinity Desktop guest, where the custom GRUB resolution was already working, so I could go View > Resize to VM at the GRUB screen, then install spice-vdagent...
99% of the time I use a guest with open ports, I only want the host and/or specific other guests to be able to access the open ports. It's simpler, and potentially less attack surface, to use a...
In VirtualBox, it's possible to specify a custom video mode that could be used by GRUB and provide screen size hint for the login screen. I used this to make GRUB, TTYs, login screen, and graphical...
Well that was strange. Setting this up on the production host, the nftables table rename does completely solve the problem there, virt-manager is able to use iptables-nft no problem, and the VM can...
Ugh #-o That explains it, thanks. Unfortunately neither the test host nor the future production host are physically located where a wired Internet connection is available, and changing this isn't...
Unfortunately this doesn't work, virt-manager throws this error dialog -
Error creating virtual network: internal error: Failed to apply firewall rules /usr/sbin/iptables -w --table filter...
Ok, with host firewall completely disabled, the Open network appears to be working as host-only networking, solving one of the 3 issues. How can I prove this network is really isolated to host-only,...
The apparent iptables requirement is that virt-manager throws this error dialog when creating a virtual network, regardless of whether firewalld is installed and active -
Error creating virtual...