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:
> I
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.
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
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
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
> Me
> . 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
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 u
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?
>
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
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 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
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
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
13 matches
Mail list logo
