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
.
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 s
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
Hi
søndag den 28. juni 2020 kl. 23.23.39 UTC+2 skrev Dave C:
>
> A) Is it safe to remove qubes-core-agent-dom0-updates and
> qubes-vm-recommended from a debian template?
> I've noticed that installing qubes-vm-recommended brings yum and yum-utils
> along with it. This leaves me wondering, is
On Wed, May 6, 2020 at 3:44 PM Rune Philosof
wrote:
> Also discovered an alternative solution. Switch to HVM for the appVM and
> use podman instead.
>
It would be even nicer if the switch to HVM wasn't necessary.
But that would require at least kernel 5.2 (
https://github.com/torva
mandag den 13. april 2020 kl. 10.05.00 UTC+2 skrev Frédéric Pierret:
>
> qvm-prefs --set work-docker kernelopts 'nopat
> systemd.unified_cgroup_hierarchy=0'
>
>
I wish I had been able to find this using duckduckgo.com when I searched
for "qubes fedora 31 docker".
But I eventually
søn. 10. feb. 2019 20.34 skrev Dupéron Georges :
> I don't know if editing in virsh is supported.
>
> I use this to change settings from the command-line:
>
> qvm-prefs myvm vcpus 1
>
Well, the problem is that I wanted to add network to the booting options.
I want to PXE boot the VM.
> Le jeu.
When I edit domains in virsh I get the message
```
error: XML document failed to validate against schema: Unable to validate doc
against /usr/share/libvirt/schemas/domain.rng
Extra element os in interleave
Element domain failed to validate content
```
This happens even if I only change the
On Monday, January 8, 2018 at 10:06:29 AM UTC+1, Rune Philosof wrote:
> On Wednesday, March 12, 2014 at 4:40:16 PM UTC-6, danf...@gmail.com wrote:
> > Any update regarding this?
>
> I have chosen to do this, it is a terrible downgrade of security from a
> normal Qubes s
On Saturday, June 25, 2016 at 7:49:39 PM UTC+2, cubit wrote:
> To use the Windows Key, it is `Mod4`
>
>
> "Mod4-c"
> "Mod4-v"
How did you figure that out?
I haven't been able to find documentation with a list available modifier names.
I tried using the names from `xev`'s output with no luck.
On Wednesday, March 12, 2014 at 4:40:16 PM UTC-6, danf...@gmail.com wrote:
> Any update regarding this?
I have chosen to do this, it is a terrible downgrade of security from a normal
Qubes system, but I think it is better than the alternative of using Ubuntu.
In my case I am also not using the
On Mon, Jul 10, 2017 at 4:20 PM, Unman <un...@thirdeyesecurity.org> wrote:
> On Mon, Jul 10, 2017 at 10:03:09AM +0200, Rune Philosof wrote:
> > I get an error in Fedora 23 Chromium, that I don't get in Firefox or in
> > Chromium on Debian 8.
>
> This is a well known bu
Hi
I get an error in Fedora 23 Chromium, that I don't get in Firefox or in
Chromium on Debian 8.
I am wondering what is different in the setup of Qubes Fedora 23 that makes
this error appear. I guess it is just a matter of using a different version
of Chromium (54.0.2840.90 in Fedora and
23 matches
Mail list logo
