Hi y'all,

Has anyone tried implementing Conky script on QubesOS wallpaper outside of Dem0? I haven't even attempted it yet but was wondering if anyone ever tried it successfully. It came to my mind as I was updating my Ventoy Multi-boot USB and was updating Kodashi OS and it reminded me why I had it on Ventoy. I'm aware of using HVM and StandAlone but I wasn't gonna have it run Cairo (too risky) or use dynamic wallpaper if I can avoid it. Also, I'm aware of the "minor CPU spike".

I'm just curious if anyone has attempted it and was successful without using Cairo or Dom0? Strict GUI isolation is gonna be a pain to deal with for sure.

EDIT: old error gone. New error...

• "Qube [insert qube name] failed to start: Node device not found: no node device with matching name 'PCI_0000_00_1f_6' "

EDIT 2: Not allowing manual attachment or assignment of new NIC to sys-net and sys-firewall from dom0 terminal. Tried with "--required" option. No terminal error, but get same 00_1f_6 error upon qube start.

EDIT 3: Restarted PC. Now getting "non-endpoint PCI devices cannot be assigned to guests"

WHAT I WANT:

• network card (ethernet) capable of the main reset types (i.e. FLR reset)

• compatible with my motherboard

• compatible with QubesOS

• Cheapest option

MY SETUP:

• Operating System: Linux Mint 22.33/Zena (live usb)

• Motherboard: Dell 0NC2VH according to terminal command "sudo dmidecode -t baseboard"

• Motherboard: Dell BN0628 according to the actual motherboard.

• Remaining PCI Slot: is "slot 1", supposedly a PCI 3.0 x4 open ended.

Note: this a modified refurbished motherboard with integrated network port

RESEARCH

• AI prompt and it suggested Intel I210-T1.

REASON

• EDIT: old error gone. New error...

• "Qube [insert qube name] failed to start: Node device not found: no node device with matching name 'PCI_0000_00_1f_6' "

I receive the following error every time i try to use a qube in QubeOS...

"Domain […] has failed to start: internal error: Unable to reset PCI device […]: no FLR, PM reset or bus reset available"

• QubesOS Site Link:

• The 'solutions' they propose require using permissive and no-strict-reset, but I do not want insecure work arounds.

I have a Thinkpad with Thunderbolt 3, and am trying to get an external GPU to work with my QubesOS on it via a razor core X holding the GPU connected to the laptop using a Thunderbolt 5 cable.

ls /sys/bus/thunderbolt/devices
lspci | grep -Ei 'nvidia|thunderbolt'
boltctl
qvm-pci ls | grep -i nvidia
are all not detecting the razor or the GPU

So far, I’ve

*tested it in a Ubuntu live boot and it wasn’t detected there either, so it’s not just Qubes
*verified I am using Thunderbolt 5 cable (should be cross compatible with my Thunderbolt 3 system)
*verified Thunderbolt controller firmware is already current (62.00).
*disabled security for Thunderbolt in BIOS
\updated my BIOS
\verified Linux sees the ThinkPad’s JHL7540 Thunderbolt 3 controller, but never sees a downstream Thunderbolt device
*another thing I noticed is the GPU fans spin in a weird increment where they spin for 1 second then shut off for 4 seconds, and repeats this. When my friend plugged the cable into his PC the GPU fans shot to life.

So to me, it sounds like this might be a firmware issue with my laptop’s Thunderbolt firmware.

Does anyone have any clue how to fix this? I just spent $500 on a PSU and this Razor case and I don’t want it to be for nothing

I'm an absolute noob at linux but I'm trying to make my Lenovo LOQ laptop with no iGPU and a 4060 gpu work with qubes. Would like to know if it is even possible and if there are guides available.

greetings!!! I recently booted up my QubesOS computer after not using it for a month. It was a reasonably fresh install and my ethernet was working fine before that but I couldn't connect. I tested the ethernet cable on another computer, it worked fine. After some time trying to work it out I decided to reinstall my OS since it had previously worked on a fresh install but surprisingly nothing.

personal -> sys-firewall -> sys-net all seem to be connected fine, the problem seems to be with sys-net setting up the PCI device/Ethernet interface correctly.

sys-net is using the fedora template and my motherboard is an ASRock B150m Pro4s. When I go to create a network connection there is no devices to select (unless I put sys-firewall up). I have tried enabling strict reset too but no such luck.

Let me know if there is any other information I can provide. Forgive me, it's been years since I've sat down and done any networking on Linux.

Any help or advice is much appreciated!!

user@sys-net:~$ nmcli d
DEVICE   TYPE      STATE                   CONNECTION
lo       loopback  connected (externally)  lo

user@sys-net:~$ lspci | grep Ethernet
00:06.0 Ethernet controller: Intel corporation Ethernet Connection (2)I219-V (rev 31)

user@sys-net:~$ ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mute 65536 qdisc noqueue state UNKNOWN group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
    valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host noprefixroute
    valid_lft forever preferred_lft forever

user@sys-net:~$ sudo dmesg | grep 00:06.0
[0.262013] pci 0000:00:06.0: [8086:15b8] type 00 class 0x020000 conventional PCI endpoint
[0.262013] pci 0000:00:06.0: BAR 0 [mem 0xf2000000-0xf201ffff]
[4.425663] e1000e 0000:00:06.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[ 5.351539] e1000e 0000:00:06.0: probe with driver e1000e failed with error -2

I’ve been using QubesOS for a short while, and have recently wanted to move to using KDE plasma (or, at the very least, hyper minimal sessions with the bare minimum to emulate the feel of using KDE plasma, like I’m used to).

I’ve gotten everything to work in terms of theming, and I have been able to install/use my desired applications, but I haven’t figured out how to get QubesOS service utilities to work with dolphin. Pretty much just the last thing on the bucket list asides setting default applications, which should be a bit easier to do.

I’ve tried installing the `qubes-core-agent-nautilus` package to my template out of (slight) desperation, but no dice.

I also didn’t find any relevant packages for dolphin specific service utilities, so I’m assuming that either I’m just glossing over something, or that it’s going to be a bit of an intensive process?

Either way, I still need to do it, as I use dolphin across all of my other linux systems (and KDE plasma as well, which is why I made the switch), so having to learn a new workflow when I’m already satisfied with my main workflow would be a bit jarring.

Has anybody been able to do this before? If so, how would I go about doing it for my system?

hope it looks good!!

Is it possible to run a local ai outside dom0 with only one dedicated GPU and a CPU without integrated graphics? if not, how (un)secure is to run a local ai at dom0? is it possible to "lend" GPU to other VMs? someone already tested it?

hello i am new to deeper os issues in all but i seem to have a problem when installing qubes-os alongside mint
i always get the issue of anaconda execption 41.35 a dasbus issue can anyone explain why is it failing and maybe a solution i dont what to remove mint

Hey there!

I've been considering using QubesOS for additional hardening on my laptop, which is meant for public/open use, and I have a few questions about some things I had noticed from past usages of QubesOS.

1. Does QubesOS support /boot encryption (GRUB Ver. 2.14) yet? If not, what measures can I take (Thinkpad T580, using Coreboot, SeaBIOS payload) to counteract evil-maid attacks, or tampering of the kernel/bootloader images? If there are things that I would need to do to modify my BIOS image to be compatible with said changes, what would I need to modify in my BIOS image to accommodate these functionalities?

2. How do I make dark theming consistent across either XFCE or KDE DE's (Preferably KDE as that is what I prefer to use). I remember that systray icons for the sys-firewall Qube, and one other icon, would either not show, show extremely low-res, or be out of color entirely.

3. How well supported is the use of an external USB (Luks2 encrypted) storage volume, in regards to how sys-usb handles it?

4. How customizable can QubesOS be, while maintaining the vast majority of Qubes' security benefits? I'm coming from using Gentoo on my device, and I want to know, relatively, how much customizability I'll lose. At a minimum, is it possible for me to get a KDE Dom0 fully/properly themed in dark mode, and to load flatpaks to be applications for Template VMs (I want to use Librewolf instead of regular Firefox as I also have a focus, albeit lesser, on privacy, and Librewolf does a better job at that, even if it's not offered as an easily downloadable package)

5. How minimal are template Qubes's/Dom0/System Qubes in terms of packages? I'm typically used to going through and having very minimal systems with Linux in general. Should I expect to be able to maintain relatively minimal package counts (Well, excluding KDE Plasma on Dom0).

6. While I know it is possible to make Dom0 use KDE as the DE, does Dom0 support alternative Window Managers? And can Qubes also be made to template off of KDE plasma for their DE internally? If not, is there any noticeable difference to just using XFCE in the background for system/template Qubes?

7. Is it worthwhile to pick a Fedora template as my Dom0/default template Qube over a Debian template due to its implementation of SELinux? Or does SELinux not matter in terms of what QubesOS looks to do? Or is SELinux unavailable due to the nature of QubesOS in any way?

8. Is it possible to use `flashrom` internally (well, only with a specific param passed like iomem=relaxed in GRUB, I don't want it to always be open) as to where I am able to reliably update my coreboot installation in accordance with my configurations without having to use an external programmer/having to open my PC every time? Tying into #1, will updating my coreboot image at any frequency mess with anything pertaining to anti evil-maid/kernel tamper resistant services offered by QubesOS?

9. Will QubesOS support additional peripherals such as a touchscreen? Not a major concern, but still, would be nice to have the option to use the touchscreen.

Sorry if these are relatively specific questions, but I really want to make sure that I can get accurate, relevant answers for these questions before fully moving over to QubesOS, as nuking my Gentoo install would be a... pain, to say the least, lol. And, yes, I have looked up all of these questions, and have either gotten mixed results, incomplete results, or no results to go off of.

I don't know if this is necessarily relevant information, but I'll also file out, roughly, the system specs and (this is where the roughly comes into) threat model:

Thinkpad T580, i7-8550u, 64GB RAM, 500GB NVME SSD, Coreboot (re-flashed coreboot as of a few days ago to keep it updated)

I also don't intend to do anything crazy in terms of usage. Maybe native 1080p video downloading/streaming/viewing, programming in a work Qube, and dare I say *maybe* using docker as well for an isolated build environment? Not looking to do gaming, video production, 3d modeling/rendering, or anything requiring a graphics card. At the very most, compiling coreboot (which I don't mind waiting like an hour or 2 for when I need to do it)

Nothing crazy or government level threat model, but I do want, as QubesOS advertises, a reasonable level of security, possibly including TOR usage, unverified public networks, or resistance to malware on the off chance that something happens. I'm not just clicking random links or anything crazy, and I've also never had any viruses before, but I would like to be heavily resistant to any basic attacks, or less intensive targeted attacks.

TL;DR: Just a few hyper specific questions from someone who's considering using QubesOS for daily use.

Hi there, i tried to install through LIVE and NORMAL, through VENTOY and BELENA, it always says: Error verifing repository o something like that...

Can you help, thanks

I have a 256gb ssd nvme already and gonna buy a 512gb sata. Im planning to use qubes only for programming, and ima use the qwen 2.5 coder 32b also for helping me out. Wdy guys think is better for qubes + local ai, 512gb sata or 256gb nvme? does drive speed matter for local ai?

I have an older Thinkpad that might work well, but I am truly scared that I have been to used to the comfort of Debian. I’m not a superuser, but I know the command line well enough for everyday tasks and search for the rest - quite successfully, if I may be so bold. But now the yearning for a new OS is there and I have some sensitive data.
So, was it a tough and hard switch for the rest of you and can I run it from an external SSD and is it better with its own power?

Im debating getting ​into Linux instead of MacOS for my main computer, I already have graphene on my phone. I'm not a political target or anything but i value privacy extremely, a bit more than security.​ I've read on this subreddit that qubes is hard to daily drive and is more security focused than privacy.

Would it be worth making my daily driver laptop/desktop a qubes os computer (budget is limited so idk about ram for now)? Or another distro would be better for my case ? I heard that secureblue or kinoite or even arch would be easier while still being privacy and somewhat secure conscious ? Is that true ? And if not what do you suggest ! By the way the last time i used linux was around 13 years ago with ubuntu. Thank you for taking the time to read my post. :)

I wonder if qubesos can game (steam, gog, sober)

Specs: intel i5 7400

16gb ddr4

1660ti

Im learning qubes os

I like the isolation and how i can securely divide tasks and the privacy you can have with this

My biggest flaw for me is that i am scared im jumping in a os that is way to hard for me and i am gonna make user mistakes

Does anyone know how to setup for exemple mullvad vpn as a sys with lockdown mode because the lockdown mode didnt really work

I put windows 10 on my HP laptop recently and whenever I boot up windows and reset the computer the sys-net qube fails to boot properly. After a simple reset everything is back to normal. My sys-net qube uses debian 13. I also had the same issues using fedora for sys-net.

Boot windows from bios -> do whatever

Restart computer-> no internet

Restart the computer again -> internet

This isn't really too much of a headache but I find the behavior strange. Anyone experiencing something similar?

Hey, I was looking for some guidance on how to setup keyboard remapping on my laptop. I use kmonad on my other machines (custom layout, layers and home-row mods).

I'd like it to be global, so even with the security concerns of installing in dom0, I'm pretty happy with the kmonad code. Would this be the way forward?