Re: [qubes-users] issue with URL handler in Thunderbird: started VM receives truncated URL

I have this you can use: https://github.com/Rudd-O/qvm-open-in-another-vm After building the package and installing it in the template, you can shut off the template, restart the qube where you want to configure link clicks to launch in another qube, and follow these instructions:

Re: [qubes-users] Qubes 4.2 error: Failed to remove old efi boot entry.

On 2024-02-24 16:02, ales...@magenta.de wrote: > In my fresh install of 4.2 this error appeared. > > > The following error occurred while installing the boot loader. The system > will not be bootable. > > Would you like to ignore this and continue with installation? > > Failed to remove old efi

[qubes-users] Screen sleep doesn't disable backlight

On Qubes 4,2, when the screen goes to sleep after idle time or when I lock the screen, the screen is black but the backlight is still on. Only when the system goes to Suspend is the backlight turned off. How can I fix this? -- You received this message because you are subscribed to the Google

[qubes-users] Qubes 4.2 error: Failed to remove old efi boot entry.

In my fresh install of 4.2 this error appeared. > The following error occurred while installing the boot loader. The system will not be bootable. > Would you like to ignore this and continue with installation? > Failed to remove old efi boot entry. This is most likely a kernel or firmware

[qubes-users] Installation Guide needs to be updated

I followed the Installation Guide when I made my fresh install of 4.2. Some of it is not accurate any more. Actually it has not been accurate since a long time now I think. a) In the section Software: Debian and Whonix are not options there any more. This choice has been moved to later in the

Re: [qubes-users] issue with URL handler in Thunderbird: started VM receives truncated URL

[quote="Ulrich_Windl1, post:8, topic:24602"] I kind of disagree: When passing the URL as "$1", it is passed as one single parameter. The user cannot be expected to know to how much more levels of shell script the parameter will be passed to, so any deeper layers have to keep the single

Re: [qubes-users] issue with URL handler in Thunderbird: started VM receives truncated URL

Hi! I kind of disagree: When passing the URL as "$1", it is passed as one single parameter. The user cannot be expected to know to how much more levels of shell script the parameter will be passed to, so any deeper layers have to keep the single parameter. That is: Every layer of shell script

Re: [qubes-users] issue with URL handler in Thunderbird: started VM receives truncated URL

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Fri, Feb 23, 2024 at 02:34:27AM +, Qubes OS Users Mailing List wrote: > Just realized I sent this as "reply" instead of "reply all". Sorry for > the spam, Ulrich, but I want to make sure this is visible to others who > might have a similar

Re: [qubes-users] issue with URL handler in Thunderbird: started VM receives truncated URL

Just realized I sent this as "reply" instead of "reply all". Sorry for the spam, Ulrich, but I want to make sure this is visible to others who might have a similar problem. I think the problem is that the URL doesn't end up getting quoted on the other end. When this is sent:

Re: [qubes-users] issue with URL handler in Thunderbird: started VM receives truncated URL

On Thu, 22 Feb 2024 22:19:21 +0100 Ulrich Windl wrote: >On 2/22/24 22:15, Ulrich Windl wrote: >> On 2/22/24 21:54, 'Stuart Perkins' via qubes-users wrote: >>> >>> On Thu, 22 Feb 2024 21:25:18 +0100 >>> Ulrich Windl wrote: >>> Hi! I managed to configure Thunderbird to

Re: [qubes-users] issue with URL handler in Thunderbird: started VM receives truncated URL

On 2/22/24 22:15, Ulrich Windl wrote: On 2/22/24 21:54, 'Stuart Perkins' via qubes-users wrote: On Thu, 22 Feb 2024 21:25:18 +0100 Ulrich Windl wrote: Hi! I managed to configure Thunderbird to run any links via a DVM. However today I realized that URLs with parameters are truncated

Re: [qubes-users] issue with URL handler in Thunderbird: started VM receives truncated URL

On 2/22/24 21:54, 'Stuart Perkins' via qubes-users wrote: On Thu, 22 Feb 2024 21:25:18 +0100 Ulrich Windl wrote: Hi! I managed to configure Thunderbird to run any links via a DVM. However today I realized that URLs with parameters are truncated (Qubes-OS 4.2) after the first parameter it

Re: [qubes-users] issue with URL handler in Thunderbird: started VM receives truncated URL

On Thu, 22 Feb 2024 21:25:18 +0100 Ulrich Windl wrote: >Hi! > > >I managed to configure Thunderbird to run any links via a DVM. However >today I realized that URLs with parameters are truncated (Qubes-OS 4.2) >after the first parameter it seem. > >For example I have the URL

[qubes-users] issue with URL handler in Thunderbird: started VM receives truncated URL

Hi! I managed to configure Thunderbird to run any links via a DVM. However today I realized that URLs with parameters are truncated (Qubes-OS 4.2) after the first parameter it seem. For example I have the URL .../viewtopic.php?f=21=196913=1023049=1023049 When I view it in Firefox, the

[qubes-users] Re: help: errors in fedora-39-minimal upgrade

Some useful information at https://github.com/QubesOS/qubes-issues/issues/8806 On Saturday, February 17, 2024 at 9:08:44 PM UTC-8 Boryeu Mao wrote: > I attempted to upgrade the fedora-39-minimal template as follows: > > sudo qubesctl --show-output --skip-dom0 >

[qubes-users] Qubes OS 4.2: no more access to local ports?

I have for years done my development work using dedicated AppVMs that run podman (https://podman.io/) containers based on images from bioconductor (https://bioconductor.org/help/docker/) for project isolation and reproducibility - images are pushed on a per project basis into the registry of

[qubes-users] HCL Dell Precision 7730 with Qubes 4.2

HCL: --- layout: 'hcl' type: 'Notebook' hvm: 'yes' iommu: 'yes' slat: 'yes' tpm: '2.0' remap: 'yes' brand: | Dell Inc. model: | Precision 7730 bios: | 1.31.0 cpu: | Intel(R) Xeon(R) E-2176M CPU @ 2.70GHz cpu-short: | FIXME chipset: | Intel Corporation 8th Gen Core

[qubes-users] [Q4.2] Minor display resolution issue with KVM

I have more computers than keyboards so I use a KVM. I have this Debian computer that always switches back to 1024x768 whenever the KVM returns control to it. Ever since I updated my Qubes computer to 4.2, it has been doing the same thing. I keep finding myself wondering why everything looks so

Re: [qubes-users] Need help after a failed in-place upgrade attempt

Hello 'Haaber', Am Di., 20. Feb. 2024 um 11:10 Uhr schrieb 'haaber' via qubes-users < qubes-users@googlegroups.com>: > ... > > all updates go via tor network (sys-whonix) by default. You could click on > the blue qube widget -> sys-wonix -> run terminal and see if sys-whonix has > network. But I

Re: [qubes-users] Need help after a failed in-place upgrade attempt

Hi Am Sa., 17. Feb. 2024 um 08:10 Uhr schrieb 'haaber' via qubes-users : Hi > I tried to upgrade my Qubes OS system from 4.1.2 to 4.2.0 using the > "qubes-dist-upgrade" script. ... > OK, I am not an expert on THIS question. Some

Re: [qubes-users] Need help after a failed in-place upgrade attempt

Hello community, Am Sa., 17. Feb. 2024 um 08:10 Uhr schrieb 'haaber' via qubes-users < > qubes-users@googlegroups.com>: > >> Hi >> > I tried to upgrade my Qubes OS system from 4.1.2 to 4.2.0 using the >> > "qubes-dist-upgrade" script. >> ... >> > >> OK, I am not an expert on THIS question. Some

[qubes-users] help: errors in fedora-39-minimal upgrade

I attempted to upgrade the fedora-39-minimal template as follows: sudo qubesctl --show-output --skip-dom0 --targets=fedora-39-minimal-clone-1 state.sls update.qubes-vm But the process results in errors (see attached file qubesctl-f39). This is for R4.2. Please help. Thank you. -- You

Re: [qubes-users] Need help after a failed in-place upgrade attempt

Hello 'Haaber', Am Sa., 17. Feb. 2024 um 08:10 Uhr schrieb 'haaber' via qubes-users < qubes-users@googlegroups.com>: > Hi > > I tried to upgrade my Qubes OS system from 4.1.2 to 4.2.0 using the > > "qubes-dist-upgrade" script. > > > > The upgrade failed - and - now the system is in a 'weird'

Re: [qubes-users] Need help after a failed in-place upgrade attempt

Hi I tried to upgrade my Qubes OS system from 4.1.2 to 4.2.0 using the "qubes-dist-upgrade" script. The upgrade failed - and - now the system is in a 'weird' state. None of the Fedora- or Debian-based VM have 'external / public' network access anymore. The 'anon-whonix' VM however still does

Re: [qubes-users] Updating fedora-38: "b'warning: runaway fork() in Lua script\n'"

On Friday, February 16th, 2024 at 6:32 PM, Ulrich Windl wrote: > > > Hi! > > > I saw these messages when upading fedora-38 today. I didn't run QuebesOS > for a while, so there were a lot of updates, but "runaway fork()" > worries me a bit... I've seen these messages too, during

[qubes-users] Updating fedora-38: "b'warning: runaway fork() in Lua script\n'"

Hi! I saw these messages when upading fedora-38 today. I didn't run QuebesOS for a while, so there were a lot of updates, but "runaway fork()" worries me a bit... Kind regards, Ulrich --- Updating fedora-38 b'warning: runaway fork() in Lua script\n' b'warning: runaway fork() in Lua

Re: [qubes-users] Where do I verify the gpg key? Do the docs need updating?

On 2/16/24 12:38 PM, Allen Schultz wrote: > Hi, > > I''m trying to verify the key I downloaded from the Qubes Download page > . According to the documentation on > the Verfying Signatures > , it looks

[qubes-users] Where do I verify the gpg key? Do the docs need updating?

Hi, I''m trying to verify the key I downloaded from the Qubes Download page . According to the documentation on the Verfying Signatures , it looks like there may be a discrepancy between the two.

[qubes-users] Need help after a failed in-place upgrade attempt

Hello community, I tried to upgrade my Qubes OS system from 4.1.2 to 4.2.0 using the "qubes-dist-upgrade" script. The upgrade failed - and - now the system is in a 'weird' state. None of the Fedora- or Debian-based VM have 'external / public' network access anymore. The 'anon-whonix' VM

[qubes-users] Re: Fedora 39 templates available; Fedora 38 approaching EOL

On 2/13/24 4:17 AM, Andrew David Wong wrote: > Dear Qubes Community, > > New Fedora 39 templates are now available in standard, > [minimal](https://www.qubes-os.org/doc/templates/minimal/), and > [Xfce](https://www.qubes-os.org/doc/templates/xfce/) varieties. In addition, > Fedora 38 is

Re: [qubes-users] time sync dysfunctional

Dear unman & qubes -community, I am still on Q4.1 (no time to do a full install now). Since a few days, my time ran large out of sync, despite the swdate displaying normal functioning. I rebooted, I restarted swdate. Its log says:   [INFO] date output: 10:44:44 (which is London time, but

Re: [qubes-users] Re: question on 'service-name' for the new (R4.2) qrexec policy

Thanks very much -- the details helped a lot. Case closed. On Tuesday, February 13, 2024 at 5:21:05 AM UTC-8 Rusty Bird wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Boryeu Mao: > > > For R4.1.2 I had some RPC calls with + and - characters in the file > > > name. These are

Re: [qubes-users] Re: question on 'service-name' for the new (R4.2) qrexec policy

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Boryeu Mao: > > For R4.1.2 I had some RPC calls with + and - characters in the file > > name. These are considered as invalid characters to be part of service > > names in the new qrexec policy format (e.g. in > >

[qubes-users] Fedora 39 templates available; Fedora 38 approaching EOL

Dear Qubes Community, New Fedora 39 templates are now available in standard, [minimal](https://www.qubes-os.org/doc/templates/minimal/), and [Xfce](https://www.qubes-os.org/doc/templates/xfce/) varieties. In addition, Fedora 38 is currently

Re: [qubes-users] The Star Labs StarBook is Qubes-certified!

Looking to get myself a new laptop...I have been using the Carbon X1 (Gen. 5) for about 6-7 years. It has treated me well but fear it is about to crash (I recently saw a Fan error). I don't know if I have the energy to make a laptop from a refub again, thinking a new laptop with Qubes

[qubes-users] Re: question on 'service-name' for the new (R4.2) qrexec policy

Correction - only + is considered as invalid character. On Monday, February 12, 2024 at 4:56:27 PM UTC-8 Boryeu Mao wrote: > For R4.1.2 I had some RPC calls with + and - characters in the file > name. These are considered as invalid characters to be part of service > names in the new qrexec

[qubes-users] question on 'service-name' for the new (R4.2) qrexec policy

For R4.1.2 I had some RPC calls with + and - characters in the file name. These are considered as invalid characters to be part of service names in the new qrexec policy format (e.g. in /etc/qubes/policy.d/30-user.policy). Using wild card * works, but I wonder if there is any way to keep these

[qubes-users] Re: looking for qubes package(s) to install in debian-12-minimal

Upon a bit of searching, the main package needed is pinentry-gnome3, with four additional packages: gcr libgcr-base-3-1 libgcr-ui-3-1 libgck-1-0 for my AppVM. On Friday, February 9, 2024 at 4:47:28 PM UTC-8 Boryeu Mao wrote: > PS. The AppVM sends the gpg passphrase request to dom0 when the

[qubes-users] Ich suche eine Lesesoftware und eine Diktat-Software für QubesOS / Debian/Fedora.

Ich suche eine Lesesoftware und eine Diktat-Software für QubesOS / Debian/Fedora. Wo finde ich das? Oder gibt es eine andere Lösung? Ich benutze LibreOffice als Textverarbeitungsprogramm. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To

[qubes-users] Re: looking for qubes package(s) to install in debian-12-minimal

PS. The AppVM sends the gpg passphrase request to dom0 when the following command is run in dom0: qvm-run --pass-io AppVM 'gpg --quiet -d some-file' On Friday, February 9, 2024 at 1:05:16 PM UTC-8 Boryeu Mao wrote: > I have a debian-12 based AppVM that forwards gpg passphrase

[qubes-users] looking for qubes package(s) to install in debian-12-minimal

I have a debian-12 based AppVM that forwards gpg passphrase request to dom0 in a pop-up dialog window. When the template is changed to debian-12-minimal, the pop-up request no longer shows up in dom0, presumably because some qubes package(s) need to be installed? Any configuration changes

Re: [qubes-users] time sync dysfunctional

Hi Unman I reply inline below. On 2/6/24 11:45, 'haaber' via qubes-users wrote: Hi, I am still on Q4.1 (no time to do a full install now). Since a few days, my time ran large out of sync, despite the swdate displaying normal functioning. I rebooted, I restarted swdate. Its log says:  

Re: [qubes-users] time sync dysfunctional

On Tue, Feb 06, 2024 at 01:08:09PM +0100, 'haaber' via qubes-users wrote: > addendum: if I run "date" in a client VM it will give the right > timezone, but still has 3min of delay.. > > On 2/6/24 11:45, 'haaber' via qubes-users wrote: > > Hi, > > > > I am still on Q4.1 (no time to do a full

Re: [qubes-users] time sync dysfunctional

addendum: if I run "date" in a client VM it will give the right timezone, but still has 3min of delay.. On 2/6/24 11:45, 'haaber' via qubes-users wrote: Hi, I am still on Q4.1 (no time to do a full install now). Since a few days, my time ran large out of sync, despite the swdate displaying

[qubes-users] time sync dysfunctional

Hi, I am still on Q4.1 (no time to do a full install now). Since a few days, my time ran large out of sync, despite the swdate displaying normal functioning. I rebooted, I restarted swdate. Its log says:   [INFO] date output: 10:44:44 (which is London time, but otherwise correct), my

[qubes-users] Whonix 17 templates available for Qubes OS 4.1

Dear Qubes Community, Until now, Whonix 17 has been available only on Qubes OS 4.2. Since [Whonix 16 reached EOL (end-of-life) on 2024-01-18](https://www.qubes-os.org/news/2023/12/22/whonix-16-approaching-eol/), this left users still on Qubes OS 4.1 without a supported way to use Whonix. In

[qubes-users] XSAs released on 2024-01-30

Dear Qubes Community, The [Xen Project](https://xenproject.org/) has released one or more [Xen security advisories (XSAs)](https://xenbits.xen.org/xsa/). The security of Qubes OS *is affected*. ## XSAs that DO affect the security of Qubes OS The following XSAs *do affect* the security of Qubes

[qubes-users] XSAs released on 2024-01-22

Dear Qubes Community, The [Xen Project](https://xenproject.org/) has released one or more [Xen security advisories (XSAs)](https://xenbits.xen.org/xsa/). The security of Qubes OS *is not affected*. ## XSAs that DO affect the security of Qubes OS The following XSAs *do affect* the security of

Re: [qubes-users] librem14 sleep on qubes 4.2

Follow up: The installation of librem-ec-acpi-dkms solved it. Regards, Vit On 2/1/24 22:44, Vitali Andrusevich wrote: Hi Just made a fresh install of qubes 4.2 to my Librem14 So far everything is running smoothly except sleep mode. The first time when i close the lid - it goes to sleep

[qubes-users] librem14 sleep on qubes 4.2

Hi Just made a fresh install of qubes 4.2 to my Librem14 So far everything is running smoothly except sleep mode. The first time when i close the lid - it goes to sleep like a charm. When i open the lid i have to press power button to wake it up. It wakes up normally, but the next time i close

[qubes-users] HVM standalone: no mouse after suspend-to-ram

Dear group, I am having issues with the mouse not coming back after standby. I am running Qubes 4.1.2 (R4.1), kernel 5.15.52-1.fc32.qubes.x86_64 The VM is a HVM standalone, running Tails OS, kernel 6.1.0-13-amd64 (Debian 6.1.55-1). After I wake Qubes from suspend-to-ram, the mouse doesn't work

[qubes-users] [qubes-announce] QSB-100: Incorrect handling of PCI devices with phantom functions (XSA-449)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear Qubes Community, We have published [Qubes Security Bulletin 100: Incorrect handling of PCI devices with phantom functions (XSA-449)](https://github.com/QubesOS/qubes-secpack/blob/main/QSBs/qsb-100-2024.txt). The text of this QSB and its

[qubes-users] HCL Purism Librem mini V2 with Qubes 4.2

Hi, HCL: --- layout: 'hcl' type: 'Desktop' hvm: 'yes' iommu: 'yes' slat: 'yes' tpm: 'no' remap: 'yes' brand: | Purism model: | librem_mini_v2 bios: | PureBoot-Release-20 cpu: | Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz cpu-short: | FIXME chipset: | Intel Corporation Comet Lake-U v1 4c Host

[qubes-users] LUKS and Yubikey in 4.2?

Can a librem key or yubikey be used to unlock a LUKS filesystem at boot in 4.2? Wasn’t the issue previously related to dom0 being too old? Thanks -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving

[qubes-users] Re: problem with 4.2 rc5 installation source

Thank you to everyone who has helped me in the last mails. I have finally decided to buy a NovaCustomes Laptop that is Qubes certified and as expected, that works very well with Qubes 4.2. All the best Kai On Wednesday 20 December 2023 at 16:50:12 UTC Catacombs wrote: > hi, sorry if it was

[qubes-users] 4.2 issue with pam_sss.so

Hi! I just noticed these messages (in my upgraded Qubes OS): Jan 20 01:22:39 dom0 sudo[25013]: PAM unable to dlopen(/usr/lib64/security/pam_sss.so): /usr/lib64/security/pam_sss.so: cannot open shared object file: No such file or directory Jan 20 01:22:39 dom0 sudo[25013]: PAM adding faulty

[qubes-users] Re: Some issues during / after upgrading to 4.2.0

On 1/5/24 00:20, Ulrich Windl wrote: Hi! As I had some time, I performed the upgrade to Qubes OS 4.2.0. Unfortunately there were a few unexpected findings: * my debian-12-dvm template no longer offers Firefox: Qubes settings say: "Application missing in template (firefox-esr.desktop)",

[qubes-users] Minor bugs in qubes manager's "Global Config"

Hi! I just discovered the "Global Config" in Quebes manager. I found some minor bugs: In "Split GPG" the "learn more" hyperlink is displayed as text. I found no way to copy that text. The link in "URL Handling" is a link, but it leads to a very generic documentation page that says nothing

[qubes-users] HCM report

Hi! Just in case: There is a HCL report for an old system. Everything works. Brand: ASUS Model: All Series CPU: Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz Chipset: Intel Corporation 4th Gen Core Processor DRAM Controller [8086:0c00] (rev 06) Graphics: Advanced Micro Devices, Inc. [AMD/ATI]

[qubes-users] QSB-099: Qrexec policy leak via policy.RegisterArgument service

Dear Qubes Community, We have published [Qubes Security Bulletin 099: Qrexec policy leak via policy.RegisterArgument service](https://github.com/QubesOS/qubes-secpack/blob/main/QSBs/qsb-099-2024.txt). The text of this QSB and its accompanying cryptographic signatures are reproduced below. For

[qubes-users] The Star Labs StarBook is Qubes-certified!

I had a look and was surprised: A German keyboard layout would cost almost 400€ extra (while 16 GB more RAM cost only about 80€). Also the CPUs seem rather slow (1.2 GHz), and no option for recent AMD CPUs. The configuration interesting for me would have been around 1700€ with s weak CPU and

[qubes-users] HCL - ASUS Expertbook B9400CEA

--- layout:   'hcl' type:   'Notebook' hvm:   'yes' iommu:   'yes' slat:   'yes' tpm:   '2.0' remap:   'yes' brand: |   ASUSTeK COMPUTER INC. model: |   ASUS EXPERTBOOK B9400CEA_B9400CEA bios: |   B9400CEA.311 cpu: |   11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz cpu-short: |   FIXME chipset: |

[qubes-users] The Star Labs StarBook is Qubes-certified!

Dear Qubes Community, It is our pleasure to announce that the [Star Labs StarBook](https://starlabs.systems/pages/starbook) is [officially certified](https://www.qubes-os.org/doc/certified-hardware/) for Qubes OS Release 4! ## The Star Labs StarBook The [Star Labs

Re: [qubes-users] Some issues during / after upgrading to 4.2.0

On 1/9/24 2:11 PM, Ulrich Windl (Google) wrote: > Hi! > > Sorry for the delay, but attached is what I see. > > Kind regards, > Ulrich > Thank you for your report. This is a known bug: https://github.com/QubesOS/qubes-issues/issues/8725 > 06.01.2024 04:10:29 Andrew David Wong : > >> On

Re: [qubes-users] Re: Qubes 4.2: qubes-tunnel not working after upgrade (cannot resolve hostname)

Hi, Part of the answer may be that Q4.2 switched from iptables to nftables and qubes-tunnel has not been adapted for this (However I am not sure whether this holds for fedora38 templates that were in-place upgrades from 4.1 to 4.2 or only for "native" 4.2 templates obtained from the server.):

Re: [qubes-users] Re: Qubes 4.2: qubes-tunnel not working after upgrade (cannot resolve hostname)

Hi, The forum post does not use qubes-tunnel and I do not use wireguard (but openVPN) - so I do not see how this post solves my issue?! On 1/6/24 12:06, code9n wrote: Hi,   This is on the Forum: https://forum.qubes-os.org/t/wireguard-vpn-setup/19141 cheers, On Saturday 6 January 2024 at

[qubes-users] Re: Qubes 4.2: qubes-tunnel not working after upgrade (cannot resolve hostname)

Hi, This is on the Forum: https://forum.qubes-os.org/t/wireguard-vpn-setup/19141 cheers, On Saturday 6 January 2024 at 00:16:40 UTC r.wie...@web.de wrote: > Hi there, > > vpnVM and netVM both in-place upgrades from Q4.1 (and worked fine > there). Template is fedora 38. > NetVM is online,

Re: [qubes-users] Some issues during / after upgrading to 4.2.0

On 1/4/24 3:20 PM, Ulrich Windl wrote: > * fedora-38 is obsolete already? I thought fedora-37 is??? > No, Fedora 38 has not reached EOL: https://docs.fedoraproject.org/en-US/releases/eol/ -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To

[qubes-users] Qubes 4.2: qubes-tunnel not working after upgrade (cannot resolve hostname)

Hi there, vpnVM and netVM both in-place upgrades from Q4.1 (and worked fine there). Template is fedora 38. NetVM is online, ping of vpn server hostname is fine within netVM. Ping and dig do not work within vpnVM, but afair that is intended (leak prevention of qubes-tunnel) I tried to restart

[qubes-users] Whonix/dom0 broken

System Qubes(R4.0) My whonix 16 randomly stopped working. I tried clicking on the apps but they won’t open. My attempts to fix it 1. Update through qubes manger= failed and I can’t open any whonix 16 app including the terminal 2. Install whonix 17= “qvm-template command not found” yes I

[qubes-users] USB issue in 4.2.0?

Hi! It seems there is an issue with USB devices in Qubes OS 4.2: When shutting down s VM that has an USB device mounted, thst USB device is not returned to the list of available devices. I had to unplug/replug it to be able to reuse. Kind regards, Ulrich -- You received this message because

[qubes-users] Some issues during / after upgrading to 4.2.0

Hi! As I had some time, I performed the upgrade to Qubes OS 4.2.0. Unfortunately there were a few unexpected findings: * fedora-38 is obsolete already? I thought fedora-37 is??? * my debian-12-dvm template no longer offers Firefox: Qubes settings say: "Application missing in template

[qubes-users] Whonix 16 approaching EOL

Dear Qubes Community, Whonix 16 is currently [scheduled](https://www.whonix.org/wiki/About#Qubes_Hosts) to reach EOL (end-of-life) on 2024-01-18. We strongly recommend that all Whonix users upgrade to Whonix 17 before then. For more information, see [Upgrading to avoid

[qubes-users] Re: problem with 4.2 rc5 installation source

hi, sorry if it was wrong, but I sent your home email from a proton account. It might have gone to spam. The Qubes OS group just released Qubes 4.2 Final, which might accomplish install more ---directly. I usually haunt the Qubes Forum.https://forum.qubes-os.org/, where you might get more

[qubes-users] Re: External camera, microphone, wlan and Bluetooth via usb under qubes

OK, while I was not really able to find this information online, e.g. the official documents at qubes-os.org are rather silent on this topic and the stuff i find on reddit is rather outdated, i have (who provides a mind blowing support, btw) been confirmed that it is indeed possible to run a

Re: [qubes-users] Qubes OS 4.2.0 has been released!

I'm gonna make it a fun day project to upgrade my Qubes system. Long live Qubes!! On Mon, Dec 18, 2023 at 7:13 PM Andrew David Wong wrote: > Dear Qubes Community, > > Qubes OS 4.2.0 brings a host of new features, major improvements, and > numerous bug fixes. The ISO and associated [verification

[qubes-users] External camera, microphone, wlan and Bluetooth via usb under qubes

Greetings! Today is a phantastic day as qubes 4.2 came out and do I am configuring a laptop to order for it today. >From a security point of view, it seems best to me to have webcam, microphone, wlan and (optional) Bluetooth all via external usb devices, so that they do not need to be blobs in

Re: [qubes-users] Virtualbox in Linux qubes?

Hi, On 12/19/23 02:14, Kai wrote: Can you please confirm that one can use virtualbox in a Linux qube? Yes and no. Qubes uses Xen as hypervisor. Since only one hypervisor can utilize the hardware virtualization support at a time, you need VirtualBox with software virtualization. VirtualBox

[qubes-users] Virtualbox in Linux qubes?

Greetings! Can you please confirm that one can use virtualbox in a Linux qube? I am using at the moment Linux mint as I do not get qubes to install but I will buy a notebook with preinstalked qubes when version 4.2 is out. I use currently a virtual box with windows for those use cases that

[qubes-users] Qubes OS 4.2.0 has been released!

Dear Qubes Community, Qubes OS 4.2.0 brings a host of new features, major improvements, and numerous bug fixes. The ISO and associated [verification files](https://www.qubes-os.org/security/verifying-signatures/) are available on the [downloads](https://www.qubes-os.org/downloads/) page. ##

Re: [qubes-users] Re: Introducing Qubes 3.0 LiveUSB (alpha)

On 12/17/23 3:24 PM, leore...@gmail.com wrote: > Hello Joanna there is any iso more recent? > The "LiveUSB" version of Qubes is discontinued. However, you can install Qubes OS onto a USB drive and run it from there. Please see the installation guide for details:

[qubes-users] Re: Introducing Qubes 3.0 LiveUSB (alpha)

Hello Joanna there is any iso more recent? On Monday, August 10, 2015 at 5:24:23 PM UTC+2 Joanna Rutkowska wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hello, > > We have built and uploaded the first ever working Qubes Live USB image! :) > > It's based on the recently released

[qubes-users] QSB-098: CPU microcode updates not loaded with dom0 kernel version 6.6.x

Dear Qubes Community, We have published [Qubes Security Bulletin 098: CPU microcode updates not loaded with dom0 kernel version 6.6.x](https://github.com/QubesOS/qubes-secpack/blob/main/QSBs/qsb-098-2023.txt). The text of this QSB and its accompanying cryptographic signatures are reproduced

[qubes-users] XSAs released on 2023-12-12

Dear Qubes Community, The [Xen Project](https://xenproject.org/) has released one or more [Xen security advisories (XSAs)](https://xenbits.xen.org/xsa/). The security of Qubes OS *is not affected*. ## XSAs that DO affect the security of Qubes OS The following XSAs *do affect* the security of

[qubes-users] Qubes Canary 037

Dear Qubes Community, We have published [Qubes Canary 037](https://github.com/QubesOS/qubes-secpack/blob/main/canaries/canary-037-2023.txt). The text of this canary and its accompanying cryptographic signatures are reproduced below. For an explanation of this announcement and instructions for

[qubes-users] Re: HCL X570 Aorus Extreme v1.1 Ryzen 5950X R4.2-rc5

Sorry about the Typos, "I turned off SMT"* which fixed some R4.1 installer issues but not all. The installer fails to finish boot. On Saturday, December 9, 2023 at 9:01:36 AM UTC-5 Richard Horan wrote: > Hi, > > I could not post to the forum.qubes-os.org becuse I am a new user, so I > am

[qubes-users] HCL - Samsung Expert X41

Installation was done with legacy boot. UEFI does not work out of the box but the troubleshooting steps for unrecognized boot device would probably fix it (they are also required on every Linux distro). Everything else works well. --- layout:   'hcl' type:   'notebook' hvm:   'yes' iommu:  

[qubes-users] HCL X570 Aorus Extreme v1.1 Ryzen 5950X R4.2-rc5

Hi, I could not post to the forum.qubes-os.org becuse I am a new user, so I am posting here. I could not get R4.1 to work so it forced me to install the rc5. I tried the R4.2 latest kernel but had network errors after updating, which is an issue on GitHub. This is install is with the default

[qubes-users] QUbes HCL AMD ryzen

Here is an new HCL I will udpate what is working and what is not when i will test thing. For now i need to fix an issue : i only have connection to internet into template (by sudo apt update) i cannot surf on the internet on dvm or personnal template tho -- You received this message because

[qubes-users] Re: problem with 4.2 rc5 installation source

I believe the problems with the auto detection option while installing the recent release candidates has to do with the fact, that the installer seems to look for a device with a certain qubes label. However, as I am using https://www.ventoy.net/en/index.html To create my boot usb by copying the

[qubes-users] Re: Install failure, HP Z420, both 4.1.2 and 4.2.0rc5

After much fiddling around ... I have an LSI 1.6TB NVMe PCIe storage device that works just fine with Ubuntu and I think it even behaved with Proxmox 7.4 in an experiment earlier this year. I also have a couple cheap NVMe PCIe carriers and some no-name 120GB SSDs left over from a caching

[qubes-users] HCL ASUS ROG GU503GL

-- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit

[qubes-users] Install failure, HP Z420, both 4.1.2 and 4.2.0rc5

Today I have been trying to install Qubes on an HP Z420 workstation and it's been an exercise in frustration. The system had been a Proxmox host for the last eight months and it had no trouble doing that. I have two small USB sticks, one for each ISO, and I'm using Ventoy. The onboard

[qubes-users] problem with 4.2 rc5 installation source

Greetings! in qubes-os 4.2 rc4, autodetect of the installation source would no longer work, but I could successfully choose in the second option the installation source by choosing the drive and then from that drive the directory and iso file. In qubes-os 4.2 rc5, autodetect still doesn’t work,

[qubes-users] Qubes OS 4.2.0-rc5 is available for testing

Dear Qubes Community, We're pleased to announce that the fifth [release candidate (RC)](#what-is-a-release-candidate) for Qubes OS 4.2.0 is now available for [testing](https://www.qubes-os.org/doc/testing/). The ISO and associated [verification

[qubes-users] QSB-097: "Reptar" Intel redundant prefix vulnerability

Dear Qubes Community, We have published [Qubes Security Bulletin 097: "Reptar" Intel redundant prefix vulnerability](https://github.com/QubesOS/qubes-secpack/blob/main/QSBs/qsb-097-2023.txt). The text of this QSB and its accompanying cryptographic signatures are reproduced below. For an

[qubes-users] XSAs released on 2023-11-14

Dear Qubes Community, The [Xen Project](https://xenproject.org/) has released one or more [Xen security advisories (XSAs)](https://xenbits.xen.org/xsa/). The security of Qubes OS *is affected* by at least one of these XSAs. ## XSAs that DO affect the security of Qubes OS The following XSAs *do

[qubes-users] QSB-096: BTC/SRSO fixes not fully effective (XSA-446)

Dear Qubes Community, We have published [Qubes Security Bulletin 096: BTC/SRSO fixes not fully effective (XSA-446)](https://github.com/QubesOS/qubes-secpack/blob/main/QSBs/qsb-096-2023.txt). The text of this QSB and its accompanying cryptographic signatures are reproduced below. For an

[qubes-users] Re: Motherboard change

I've found a related thread on Qubes OS forum: https://forum.qubes-os.org/t/if-i-change-my-motherboard/11346 On Thursday, November 9, 2023 at 4:48:45 PM UTC+1 Vít Šesták wrote: > Hello, > I'd like to change my motherboard (for a different model), while keeping > other computer parts. What

[qubes-users] Motherboard change

Hello, I'd like to change my motherboard (for a different model), while keeping other computer parts. What should I be careful about. I am aware just about one issue: PCI devices will probably have different numbers, which causes some troubles. There is a workaround, as long as I think about

<    1   2   3   4   5   6   7   8   9   10   >