Qubes OS Forum Forum

I don’t think so. This would make the category seem like it’s actually worthwhile for people to read. Right now it’s a dumping ground for paranoid topic and I feel like we do need a place like that.

parulin: GSoC 2026: remaining trusted file converter work · Issue #10940 · QubesOS/qubes-issues · GitHub also GitHub - freedomofpress/dangerzone at v0.11.0 · GitHub

In addition the mentioned qvm-convert-* tools, there is ongoing work to provide a tool capable of handling videos and other formats: github.com/QubesOS/qubes-issues GSoC 2026: remaining trusted file converter work opened 01:23PM - 23 Jun 26 UTC Jayant-kernel C: other P: default community dev S: in progress This issue tracked the GSoC 2026 work to generalise the Qubes PDF Converter for … additional trusted file types. The planned work for this project is now complete and the relevant changes have been merged into `qubes-app-linux-pdf-converter`. Completed: - The converter was extended with server-side renderer dispatch and the `qvm-convert-file` path. - LibreOffice-backed conversion was added for DOC, DOCX, ODT, XLSX, ODS, PPTX, and ODP files. - Initial video conversion was added in #60. Video data is transferred as raw RGB frames in chunks and audio is intentionally not included in this first version. - Desktop/file-manager integration, documentation, dependency checks, unit tests, integration tests, and CI coverage were added or updated. - The supported-format documentation was kept in sync with the implementation. Relevant merged pull requests include: - #60 — video conversion - #61 — PPTX presentation conversion - #62 — ODP presentation conversion - #64 — DOC document conversion Image conversion remains separate because `qvm-convert-img` already exists. Large OCR stress testing and further video/audio improvements are outside the completed scope and can be handled as separ

That’s not exactly what you’re asking for but have you taken a look at the following? Introducing the Qubes Admin API | Qubes OS How to create an AdminVM in R4.1? How to use the Qubes Admin Policies/API despite the lack of documentation - WIP

OvalZero: [1] You didn’t write this yourself? “Engineered this with Claude.” Its great really. Time to move with the times Man. You get what you want without the ego.

miroslav_vevoda: nice to have some eyes on it before I try it with my live system Please re-read and avoid the toxicity. Guess I won’t be asking you two to review code when you can’t even read, who knows maybe you can prove me wrong.

If it’s your code, you’re the one who breaks the system first because it’s your project; this isn’t a community of testers. Regards.

Or ‘weird stuff is going on in my qubes that I don’t understand’ Going through that category is mostly people observing some odd behavior, that they don’t understand or can diagnose, the paranoia kicks in to “Omg! I must have been hacked!”

Agreed, the console and Xterm make my eyes bleed with the microscopic font, the tiny size of the locked window, inability to copy / paste / scroll etc.. I was thinking of actually replacing xterm on esp. default-mgmt-dvm and all other templates with something a bit more flexible, easy on the eyes but also open to some hardening / tweaking.

I agree with this, thanks. Installing these things in dom0 is against the qubes security model. An ‘admin’ qube seems the way to go. That said, there are quite a few of guides like this out there (installed in dom0) but I don’t see any guides with similar capabilities on a qube like an admin qube. Perhaps a guide or some solutions to the issues the OP raised about the current limitations of executing these commands from an ‘admin qube’ would be very welcome and solve not just this but what seems to me to be a much broader class of issues.

I want to configure XTerm. X resources I want to set (click for more details) The well documented way is to create a custom .Xresources file (in the home directory). Then running xrdb -merge .Xresources and switching to a new terminal. When I load resources that way in a template, they don’t persist in any derived app qube. That’s why I now load them from /etc/X11/Xresources/x11-common , which does persist. I don’t know exactly why (probably by merging the resources file, it gets referenced in some startup script, which then loads the actual resources - that might also explain the need to open a new terminal). However, I am puzzled by the following behavior: If I open XTerm in an app qube using the Qubes “Run terminal” function, then the X resources of the underlying template are loaded (as shown by xrdb -query ), but only partly do what they are intended to do. The font settings work fine, but when I try to copy the clipboard to the global clipboard, I get a warning that it is empty - which implies the X resource XTerm.vt100.selectToClipboard is not in effect, i.e. the selected text does not land in the clipboard. All works as expected when using qvm-run (root or user) or the Qubes menu. It seems I have a major misunderstanding about what it means to “load” a X resource. Is there any difference between what xrdb -query shows and the actual setting? Might this be an X related bug?

Possible reason and workaround that I’ve found: It seems that something (still trying to figure out what exactly) is causing my gaming qube to not be able to process a gamepad that polls at 1000Hz. I’ve switched the gamepad (it has a button for it) to 125Hz (Nintento Switch compatibility) mode and the lag is gone, for now.