Re: [qubes-users] Unable to boot appvm due to qubes-relabel-rw
Also, if this was a rarely used appvm, then I might not have noticed that the problem started due to a template vm upgrade. I also might not have the old template vm present on my system to switch back to for cleaning up the bind dir. So it would be nice with another solution for this. The simplest to implement is probably to remove the time out, and have the user kill the vm if it takes too long. But that might be problematic in the case of service vms that start at boot? If so, the time out could be conditional. On Mon, Jun 17, 2024 at 11:23 AM 'Rune Philosof' via qubes-users < qubes-users@googlegroups.com> wrote: > After updating from `fedora-38` to `fedora-39`, I have some AppVMs that I > am unable to boot because `qubes-relabel-rw` takes more than 60s. > > The VMs have large `/rw/bind-dirs/var/lib/docker`. > > I can clean my docker state before making the template switch, but it > would be nice to avoid having to recreate the state. > > It would be good with a more user friendly process for this, both for > explaining the problem and the solution. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "qubes-users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/qubes-users/HejWPZX102Q/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > qubes-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/qubes-users/8c63b924-605f-4bbe-8ead-7236abc7764en%40googlegroups.com > <https://groups.google.com/d/msgid/qubes-users/8c63b924-605f-4bbe-8ead-7236abc7764en%40googlegroups.com?utm_medium=email_source=footer> > . > -- Med venlig hilsen / Best regards Rune Philosof Software developer +45 28 45 64 08 r...@abtion.com Vesterbrogade 15, 3 1620 København V Sverigesgade 18 5000 Odense C https://abtion.com -- 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 https://groups.google.com/d/msgid/qubes-users/CAL8J5gbRb-LhKJpP9GXgko1N-KoHbzEeSXFHFxrq7kqY2nMPFA%40mail.gmail.com.
[qubes-users] Unable to boot appvm due to qubes-relabel-rw
After updating from `fedora-38` to `fedora-39`, I have some AppVMs that I am unable to boot because `qubes-relabel-rw` takes more than 60s. The VMs have large `/rw/bind-dirs/var/lib/docker`. I can clean my docker state before making the template switch, but it would be nice to avoid having to recreate the state. It would be good with a more user friendly process for this, both for explaining the problem and the solution. -- 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 https://groups.google.com/d/msgid/qubes-users/8c63b924-605f-4bbe-8ead-7236abc7764en%40googlegroups.com.
Re: [qubes-users] Re: Qubes 4.2: Attach usb audio device to appvm
It was not fixed... Apparently just an example of how random it is. It was working for an hour or so. Now it is back to mic not working, just sending out that beep beep sound. On Wed, Mar 20, 2024 at 9:16 AM 'Rune Philosof' via qubes-users < qubes-users@googlegroups.com> wrote: > Installing a new template fixed it. > I installed fedora-39 and switched to it. > > The old template had been upgraded in-place several times, back from > fedora-36, I think. > Maybe something is missing in the upgrade from 4.1 to 4.2, or in the > instructions on how to upgrade existing templates to 4.2. > > > On Wednesday, March 20, 2024 at 8:17:25 AM UTC+1 Rune Philosof wrote: > >> Now it is more consistent in how it is not working. >> Audio output is connected properly. >> But microphone is still not working. It does not capture any sound from >> the microphone, but it does repeat a ticking sound. I have attached a 3 >> second recording of the ticking sound. >> >> I have not changed any audio settings. >> I have tested with two different usb soundcards. >> It worked in Qubes 4.1. >> >> I wonder what has changed in the audio setup from Qubes 4.1 to 4.2. >> >> On Thursday, February 29, 2024 at 12:23:30 PM UTC+1 Rune Philosof wrote: >> >>> After upgrading to 4.2 my audio device does not work. >>> >>> I plug in a usb audio device, then attach that usb device to an appvm >>> and try to use it in e.g. meet.google.com. >>> For some reason it only works for the audio microphone or the speaker, >>> not both. >>> Example: >>> 1. I attach the usb device to the appvm. >>> 2. meet.google.com automatically switches to the new microphone, but I >>> cannot hear anything and the speaker list does not show the usb device. >>> 3. I then detach from the appvm and reattach the usb device to the same >>> appvm. >>> 4. meet.google.com does not show the usb device in the list of >>> microphones. but somehow the "default" speaker now outputs through the usb >>> device. >>> >>> In 4.1 it would either work for both mic and speaker or for none. >>> >> -- > You received this message because you are subscribed to a topic in the > Google Groups "qubes-users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/qubes-users/NDRrrYrLkpQ/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > qubes-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/qubes-users/f66bbd6a-ad20-4c30-a005-32bad82c8282n%40googlegroups.com > <https://groups.google.com/d/msgid/qubes-users/f66bbd6a-ad20-4c30-a005-32bad82c8282n%40googlegroups.com?utm_medium=email_source=footer> > . > -- Med venlig hilsen / Best regards Rune Philosof Software developer +45 28 45 64 08 r...@abtion.com Vesterbrogade 15, 3 1620 København V Sverigesgade 18 5000 Odense C https://abtion.com -- 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 https://groups.google.com/d/msgid/qubes-users/CAL8J5gaHuuvugFkwSEOTc6n2VnfzE0U-1yngaFu3zxqBAn2aZg%40mail.gmail.com.
[qubes-users] Re: Qubes 4.2: Attach usb audio device to appvm
Installing a new template fixed it. I installed fedora-39 and switched to it. The old template had been upgraded in-place several times, back from fedora-36, I think. Maybe something is missing in the upgrade from 4.1 to 4.2, or in the instructions on how to upgrade existing templates to 4.2. On Wednesday, March 20, 2024 at 8:17:25 AM UTC+1 Rune Philosof wrote: > Now it is more consistent in how it is not working. > Audio output is connected properly. > But microphone is still not working. It does not capture any sound from > the microphone, but it does repeat a ticking sound. I have attached a 3 > second recording of the ticking sound. > > I have not changed any audio settings. > I have tested with two different usb soundcards. > It worked in Qubes 4.1. > > I wonder what has changed in the audio setup from Qubes 4.1 to 4.2. > > On Thursday, February 29, 2024 at 12:23:30 PM UTC+1 Rune Philosof wrote: > >> After upgrading to 4.2 my audio device does not work. >> >> I plug in a usb audio device, then attach that usb device to an appvm and >> try to use it in e.g. meet.google.com. >> For some reason it only works for the audio microphone or the speaker, >> not both. >> Example: >> 1. I attach the usb device to the appvm. >> 2. meet.google.com automatically switches to the new microphone, but I >> cannot hear anything and the speaker list does not show the usb device. >> 3. I then detach from the appvm and reattach the usb device to the same >> appvm. >> 4. meet.google.com does not show the usb device in the list of >> microphones. but somehow the "default" speaker now outputs through the usb >> device. >> >> In 4.1 it would either work for both mic and speaker or for none. >> > -- 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 https://groups.google.com/d/msgid/qubes-users/f66bbd6a-ad20-4c30-a005-32bad82c8282n%40googlegroups.com.
[qubes-users] Qubes 4.2: Attach usb audio device to appvm
After upgrading to 4.2 my audio device does not work. I plug in a usb audio device, then attach that usb device to an appvm and try to use it in e.g. meet.google.com. For some reason it only works for the audio microphone or the speaker, not both. Example: 1. I attach the usb device to the appvm. 2. meet.google.com automatically switches to the new microphone, but I cannot hear anything and the speaker list does not show the usb device. 3. I then detach from the appvm and reattach the usb device to the same appvm. 4. meet.google.com does not show the usb device in the list of microphones. but somehow the "default" speaker now outputs through the usb device. In 4.1 it would either work for both mic and speaker or for none. -- 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 https://groups.google.com/d/msgid/qubes-users/bff4746d-a10d-482a-a913-dc82cf5e1ab6n%40googlegroups.com.
[qubes-users] Temporary failure in name resolution
After upgrading the following, I lost dns functionality in sys-firewall and all vms using sys-firewall. Using tcpdump on sys-net, it does not seem to receive the dns query. When I run `systemctl stop systemd-resolved` in an appvm, dns works again. (I removed some clearly uninteresting packages) ``` PackageArch Version Repo Size Upgrading: babl x86_64 0.1.92-1.fc35 updates 533 k dhcp-clientx86_64 12:4.4.3-2.fc35 updates 799 k dhcp-commonnoarch 12:4.4.3-2.fc35 updates 126 k evolution-data-server x86_64 3.42.4-2.fc35 updates 2.2 M evolution-data-server-langpacksnoarch 3.42.4-2.fc35 updates 1.3 M gegl04 x86_64 0.4.36-1.fc35 updates 3.0 M havegedx86_64 1.9.18-1.fc35 updates 74 k libsolvx86_64 0.7.22-1.fc35 updates 403 k nspr x86_64 4.32.0-6.fc35 updates 137 k nssx86_64 3.77.0-1.fc35 updates 691 k nss-softoknx86_64 3.77.0-1.fc35 updates 376 k nss-softokn-freebl x86_64 3.77.0-1.fc35 updates 323 k nss-sysinitx86_64 3.77.0-1.fc35 updates 20 k nss-util x86_64 3.77.0-1.fc35 updates 88 k ostree x86_64 2022.2-1.fc35 updates 229 k ostree-libsx86_64 2022.2-1.fc35 updates 424 k perl-CPAN noarch 2.33-1.fc35 updates 557 k pipewire x86_64 0.3.50-1.fc35 updates 39 k pipewire-alsa x86_64 0.3.50-1.fc35 updates 62 k pipewire-jack-audio-connection-kit x86_64 0.3.50-1.fc35 updates 135 k pipewire-libs x86_64 0.3.50-1.fc35 updates 1.5 M python3-tqdm noarch 4.64.0-1.fc35 updates 132 k rsync x86_64 3.2.3-9.fc35 updates 388 k systemdx86_64 249.11-1.fc35 updates 4.1 M systemd-libs x86_64 249.11-1.fc35 updates 603 k systemd-networkd x86_64 249.11-1.fc35 updates 523 k systemd-pamx86_64 249.11-1.fc35 updates 323 k systemd-resolved x86_64 249.11-1.fc35 updates 266 k systemd-udev x86_64 249.11-1.fc35 updates 1.8 M tzdata noarch 2022a-2.fc35 updates 432 k xorg-x11-xinit x86_64 1.4.0-14.fc35 updates 55 k Installing dependencies: botan2 x86_64 2.18.2-1.fc35 updates 1.9 M minizipx86_64 3.0.2-4.fc35 fedora 70 k perl-Digest-SHA1 x86_64 2.13-34.fc35 fedora 52 k perl-Module-Signature noarch 0.87-5.fc35 fedora 82 k ``` -- 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 https://groups.google.com/d/msgid/qubes-users/1c069029-e43a-4327-80e0-a5059cf9e4b7n%40googlegroups.com.
Re: [qubes-users] 4.1: Unlock screen -> no qube windows
What scripts are run when you log in? I have searched in vain for the script that connects already running windows to the session I just created. It would be nice to be able to reconnect the windows without having to log out and in again. Also it might help me understand what the problem is. On Mon, Jan 17, 2022 at 1:51 PM 'Rune Philosof' via qubes-users < qubes-users@googlegroups.com> wrote: > Some times when I unlock my screen my desktop is completely empty, except > for dom0 windows. > The qubes still run, for instance I can still chat in an active Google > Meet, just can't see the window. > The windows are completely gone, as in not visible in the panel, taskbar, > or workspace_switcher. > If I then log out and in again, the windows reappear. > > Felt a bit odd to stay in a meeting while logging out and back in again. :) > > -- > You received this message because you are subscribed to a topic in the > Google Groups "qubes-users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/qubes-users/D0I_Boj2Seo/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > qubes-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/qubes-users/90a68260-3318-4364-b888-d0d7d7519da5n%40googlegroups.com > <https://groups.google.com/d/msgid/qubes-users/90a68260-3318-4364-b888-d0d7d7519da5n%40googlegroups.com?utm_medium=email_source=footer> > . > -- Med venlig hilsen / Best regards Rune Philosof Software developer +45 28 45 64 08 r...@abtion.com Vesterbrogade 15, 3 1620 København V Sverigesgade 18 5000 Odense C abtion.com -- 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 https://groups.google.com/d/msgid/qubes-users/CAL8J5gbnFffFpSvdKwwGruPssUzAe2EYcmqHQi_rs7VYtXHuMA%40mail.gmail.com.
[qubes-users] Re: Google Maps producing a very high CPU usage
> . I wish Google allowed my graphics card to work instrad of my CPU. p.s. and yes, I also have 100% CPU load often. Same with YouTube. Google, come on, let graphics cards do the job! In Qubes the graphics card hardware acceleration is not exposed to the vms for security reasons (https://www.qubes-os.org/faq/#can-i-run-applications-like-games-which-require-hardware-acceleration). So it is incorrect to blame Google for this. On Sunday, April 5, 2020 at 8:20:29 PM UTC+2 inya...@gmail.com wrote: > https://groups.google.com/d/msg/qubes-users/m_3EEWedJjk/YdaExR-wAgAJ > > Unfortunatelly when I turn off WebGL, everything starts to look pixelated > and the image quality sucks. I wish Google allowed my graphics card to work > instrad of my CPU. p.s. and yes, I also have 100% CPU load often. Same with > YouTube. Google, come on, let graphics cards do the job! > -- 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 https://groups.google.com/d/msgid/qubes-users/6c33dd3f-3dee-4b22-a016-5a06954e86ebn%40googlegroups.com.
Re: [qubes-users] Why is dom0 so long behind in versions?
On Tue, Jan 18, 2022 at 5:49 PM Floyd wrote: > On 1/18/22 7:09 AM, 'Rune Philosof' via qubes-users wrote: > > On Tue, Jan 18, 2022 at 1:24 PM 'awokd' via qubes-users < > qubes-users@googlegroups.com> wrote: > >> 'Rune Philosof' via qubes-users: >> > Why not use fedora 35 for dom0? >> > Wouldn't it make it easier to maintain, while also getting better >> hardware >> > support? >> > >> https://www.qubes-os.org/faq/#why-is-dom0-so-old >> > > Security is the core of Qubes, not convenience or bells and whistles. > There are, generally speaking, fewer surprises with mature versions. > > There was a saying in IT of which I often reminded my employees and > colleagues - I don't mind being on the bleeding edge, as long as it's not > the client's blood. Update that to today's reality - I don't mind being on > the bleeding edge, as long as it's not my blood. > Those are good arguments. However, I am testing out 4.1 and looking a bit into the cause of the bugs I see (loading the coredumps in gdb). I find my motivation for using time on getting to the bottom of the errors dropping because there is a chance that the errors are already fixed in newer versions. How hard it would be for me to test it out on newer versions, I wonder. It would be nice if Qubes was something you could add to an existing installation. -- 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 https://groups.google.com/d/msgid/qubes-users/CAL8J5gaxndr1MqGNBmNKaSUjeJYmVxKi6k_zekka65geEaKbbg%40mail.gmail.com.
Re: [qubes-users] Why is dom0 so long behind in versions?
On Tue, Jan 18, 2022 at 1:24 PM 'awokd' via qubes-users < qubes-users@googlegroups.com> wrote: > 'Rune Philosof' via qubes-users: > > Why not use fedora 35 for dom0? > > Wouldn't it make it easier to maintain, while also getting better > hardware > > support? > > > https://www.qubes-os.org/faq/#why-is-dom0-so-old > Thanks. But that does not answer any of the questions. It only says why it is not necessary to run a newer one. -- Med venlig hilsen / Best regards Rune Philosof Software developer +45 28 45 64 08 r...@abtion.com Vesterbrogade 15, 3 1620 København V Sverigesgade 18 5000 Odense C abtion.com -- 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 https://groups.google.com/d/msgid/qubes-users/CAL8J5gahDwsBLH54Luf_7i%3DvDC-D2fWbz3ez1N9751Q6BS5_Dw%40mail.gmail.com.
[qubes-users] Why is dom0 so long behind in versions?
Why not use fedora 35 for dom0? Wouldn't it make it easier to maintain, while also getting better hardware support? -- 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 https://groups.google.com/d/msgid/qubes-users/ec21c40c-e35d-4004-972f-e3273690e511n%40googlegroups.com.
[qubes-users] 4.1: Unlock screen -> no qube windows
Some times when I unlock my screen my desktop is completely empty, except for dom0 windows. The qubes still run, for instance I can still chat in an active Google Meet, just can't see the window. The windows are completely gone, as in not visible in the panel, taskbar, or workspace_switcher. If I then log out and in again, the windows reappear. Felt a bit odd to stay in a meeting while logging out and back in again. :) -- 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 https://groups.google.com/d/msgid/qubes-users/90a68260-3318-4364-b888-d0d7d7519da5n%40googlegroups.com.
[qubes-users] xrandr often coredumps
I am running Qubes 4.1rc3 on a Librem 14 and I see a lot of ``` Process 30303 (xrandr) of user 1000 dumped core ``` in my journalctl. This morning I have ten within a minute. I just resumed the computer from sleep and connected a usb-c monitor. Are anyone else seeing similar issues? -- 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 https://groups.google.com/d/msgid/qubes-users/a2a38830-20b9-4f02-93cd-afbbce3e8757n%40googlegroups.com.
[qubes-users] sys-net dispVM forgetting wifi passwords
I have installed 4.1rc2 and chose a disposable sys-net, because I could think of a reason not to. But now that I have to type in the wifi password again and again, I know a reason to not choose dispVM for sys-net. Maybe it should be mentioned in the installation process what consequences it will have to choose disposable for sys-net? -- 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 https://groups.google.com/d/msgid/qubes-users/6abdd98f-b3d1-46d6-967b-5ad480ddc584n%40googlegroups.com.
[qubes-users] Verifying signatures
When I follow the guide on https://www.qubes-os.org/security/verifying-signatures/ I get the following result ``` [vagrant@fedora ~]$ gpg2 --check-signatures "Qubes Master Signing Key" pub rsa4096 2010-04-01 [SC] 427F11FD0FAA4B080123F01CDDFA1A3E36879494 uid [ultimate] Qubes Master Signing Key sig!3DDFA1A3E36879494 2010-04-01 Qubes Master Signing Key gpg: 1 good signature [vagrant@fedora ~]$ gpg2 --check-signatures "Qubes OS Release 4 Signing Key" pub rsa4096 2017-03-06 [SC] 5817A43B283DE5A9181A522E1848792F9E2795E9 uid [ unknown] Qubes OS Release 4 Signing Key sig!31848792F9E2795E9 2017-03-06 Qubes OS Release 4 Signing Key gpg: Note: third-party key signatures using the SHA1 algorithm are rejected gpg: (use option "--allow-weak-key-signatures" to override) sig% DDFA1A3E36879494 2017-03-08 [Invalid digest algorithm] gpg: 1 good signature gpg: 1 signature not checked due to an error ``` Is it because the master key is old and the old defaults are now considering too weak? If so, why not distribute a new one? -- 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 https://groups.google.com/d/msgid/qubes-users/5a43c954-21a7-4aaf-8589-218dc1f911acn%40googlegroups.com.
