Hi,
I use sys-usb as audio VM,
[user@dom0 ~]$ qvm-prefs video audiovm
sys-usb
and everything works fine.
Now i want to migrate from pulseaudio to pipewire:
[root@deb12-template]$ apt install pipewire-qubes pipewire-audio pipewire
wireplumber pipewire-alsa libspa-0.2-bluetooth
Now sound [still
Dear all,
My 13th gen intel raptor lake Dell laptop only supports one sleep mode:
s2idle a.k.a. S0ix, which drains the battery 7%/h -> empty over night.
I am not the only one with that problem
https://discussion.fedoraproject.org/t/please-improve-the-s0ix-experience-under-linux/79113/2
Install
-i vif+ -j ACCEPT
> ip route add local default dev lo table 100
> ip rule add fwmark 1 lookup 100
>
> sshuttle --dns -D --method tproxy --exclude REMOTE_SERVER --exclude
> 10.0.0.0/8 --disable-ipv6 --listen 0.0.0.0:0 -r REMOTE_SERVER 0/0
>
>
> All the best
>
>
> O
I need a sys-sshuttle qube to encapsulate traffic via sshuttle. Locally
(from sys-sshuttle) it works, but connected qubes get the previously
mentioned "no connection to host" message.
Played around with various nft ideas, but no success.
tcpdump on the vif shows requests (e.g. DNS, http, etc.)
Tried different solutions... no way.
/lib/modules is a qubes-specific mount (provided by dom0)
-> qubes team has to decide how to comply with debian's "merge /usr" dogma,
otherwise we can not upgrade.
On Wednesday, August 30, 2023 at 8:46:23 AM UTC+2 Peter Palensky wrot
This
https://wiki.debian.org/UsrMerge
did not help either...
Maybe we have to merge things manually?
On Tuesday, August 29, 2023 at 7:30:41 AM UTC+2 Peter Palensky wrote:
>
> When upgrading my Debian 11 template to 12 i get stuck at
>
> -- cut --
>
> Setting up usrmerge (35) .
When upgrading my Debian 11 template to 12 i get stuck at
-- cut --
Setting up usrmerge (35) ...
FATAL ERROR:
/lib/modules/ is a mount point.
Probably this system is using User Mode Linux.
To continue the conversion please:
- replace '/lib/modules/' with '/usr/lib/modules/' in /etc/fstab
- re
Update: I can use newer kernels if I remove device "Realtek Semiconductor
Co., Ltd. RTS525A PCI Express Card Reader" from sys-usb VM.
If it _is_ attached to that VM, the entire computer crashes upon sys-usb
start (when newer kernels are in use, it is fine with [very] old ones).
So I guess not h
Same here. Only 4.x and 5.4.175 kernel works for me (Dell hardware :-( ).
I am afraid of losing that when updating...
On Wednesday, July 6, 2022 at 9:19:21 AM UTC+2 haa...@web.de wrote:
>
> > Dear Qubes Community,
> >
> > Qubes OS 4.0 is scheduled to reach end-of-life (EOL) on 2022-08-04 --
> >
On Saturday, June 11, 2022 at 7:21:20 PM UTC+2 Demi Marie Obenour wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Sat, Jun 11, 2022 at 03:00:09AM -0700, Peter Palensky wrote:
> >
> > On Saturday, June 11, 2022 at 1:09:47 AM UTC+2 haa...@web.de wr
On Saturday, June 11, 2022 at 1:09:47 AM UTC+2 haa...@web.de wrote:
> > Which kernel version do you need to hold? You can update a subset of
> > packages by giving them as arguments to qubes-dom0-update, but I would
> > like to know what the forseeable problems are.
>
> The reason is simple: a
I use a video VM for MS Teams, Zoom, etc. and dom0 top shows >10% cpu load
for pulseaudio and pacat-simple-vchan (associated with that video VM).
Is that normal? It drains my battery (Dell XPS13, kernel 5.4.88-1, Qubes
4.0) really quickly.
--
You received this message because you are subscribe
On Wednesday, September 1, 2021 at 9:29:43 PM UTC+2 haa...@web.de wrote:
> On 9/1/21 7:44 PM, Mike Keehan wrote:
> > On 9/1/21 1:36 PM, Bernhard wrote:
> >> Hello, I wonder if some of you guys have the bad luck of an i915
> >> graphics card and found some solutions. For me, no >= 5.4 xen ker
On Monday, August 10, 2020 at 6:00:21 PM UTC+2 TheGardner wrote:
> I recently got some templates (bullseye, kali and Debian-11) installed on
> my system, but I can't get them updated. So speaking first about Denian-11,
> I always get the following message, when I try to update the qube via
>
I have several dom0 kernels installed (on a Dell XPS13) but only one works
fine:
5.11.8-1.fc25.qubes.x86_64 -> boot loop
5.11.4-1.fc25.qubes.x86_64 -> boot loop
5.10.8-1.qubes.x86_64 -> kernel panic
5.4.107-1.fc25.qubes.x86_64 -> does not wake up after suspend
5.4.98-1.fc25.qubes.x86_64 -> does
Cool. Even better! Works!
On Tuesday, July 14, 2020 at 2:30:43 PM UTC+2, GWeck wrote:
>
> There is a somewhat lengthy discussion in
> https://github.com/QubesOS/qubes-issues/issues/5863.
>
> For me, setting
>
> showframewindow=false
> in ~/snap/zoom-client/current/.config/zoomus.conf worked.
>
>
Oh. it works now!
I needed to share first, and then do the xdotool trick...
On Tuesday, July 14, 2020 at 2:12:23 PM UTC+2, peter@gmail.com wrote:
>
>
>
> On Sunday, May 10, 2020 at 8:00:57 PM UTC+2, Vít Šesták wrote:
>>
>> The problem with Zoom is probably that it opens a transparent overlay,
On Sunday, May 10, 2020 at 8:00:57 PM UTC+2, Vít Šesták wrote:
>
> The problem with Zoom is probably that it opens a transparent overlay,
> likely because of annotations. However, Qubes OS does not support
> transparency. There is a workaround that hides the overlay:
>
> xdotool selectwindow w
On Wednesday, May 8, 2019 at 8:41:42 AM UTC+2, awokd wrote:
> peter.palen...@gmail.com:
> > I have a Dell TB16 dock with Ethernet over USB, based on a Realtek 8152
> > chip.
> >
> > The device appears fine in sys-usb VM using r8152 driver and ehci/xhci. So
> > it works fine with direct PCI acces
A recurring topic since R3.2 and not yet solved:
Some tray icons (in my case nm-applet and evolution-alarm-notify) are
transparent (or invisible) in KDE. Hovering over or clicking them works.
They are, however, visible in XFCE, but i can not use that due to 4K display
issues (KDE does that much
I have a Dell TB16 dock with Ethernet over USB, based on a Realtek 8152 chip.
The device appears fine in sys-usb VM using r8152 driver and ehci/xhci. So it
works fine with direct PCI access to the device.
Connecting the usb device (via 'dom0$ qvm-usb attach...') to sys-net VM
triggers loading o
On Monday, October 15, 2018 at 11:17:48 AM UTC+2, fabr...@statebox.io wrote:
> On Friday, October 12, 2018 at 7:13:56 AM UTC+2, awokd wrote:
> > fabri...@statebox.io wrote on 10/11/18 9:40 AM:
> > > On Friday, May 4, 2018 at 5:05:45 PM UTC+1, gaxi...@gmail.com wrote:
> > >> The system tray device w
After working fine for weeks, my USB keyboard stopped working out of a sudden.
sys-usb qube dmesg says:
-- cut --
[ 3545.840080] usb 1-2: new low-speed USB device number 11 using xhci_hcd
[ 3545.973689] usb 1-2: New USB device found, idVendor=413c, idProduct=2107
[ 3545.973740] usb 1-2: New USB
On Friday, September 8, 2017 at 8:22:29 AM UTC+2, peter.p...@gmail.com wrote:
> On Friday, September 8, 2017 at 4:36:56 AM UTC+2, Drew White wrote:
> > Have you tried the Startup Wizard Fix under Windows 7 boot?
> >
> > On Wednesday, 6 September 2017 21:17:41 UTC+10, peter.p...@gmail.com wrote:
>
On Friday, September 8, 2017 at 4:36:56 AM UTC+2, Drew White wrote:
> Have you tried the Startup Wizard Fix under Windows 7 boot?
>
> On Wednesday, 6 September 2017 21:17:41 UTC+10, peter.p...@gmail.com wrote:
> > I try to use an existing win7 qemu qcow2 image with qubes os R3.2
> >
> > The imag
I try to use an existing win7 qemu qcow2 image with qubes os R3.2
The image does not boot. I tried various xml settings for the drive image
inspired by
https://wiki.libvirt.org/page/After_import_a_guest_from_an_existing_disk_image_using_virt-install,_the_guest_starting_stalls_with_%22No_boot_de
On Wednesday, March 8, 2017 at 3:09:10 PM UTC+1, Rusty Bird wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> peter.palen...@gmail.com:
> > On Saturday, October 12, 2013 at 3:51:51 AM UTC+2, Marek
> > Marczykowski-Górecki wrote:
> > > On 12.10.2013 03:22, Franz wrote:
> > > > I would
On Saturday, October 12, 2013 at 3:51:51 AM UTC+2, Marek Marczykowski-Górecki
wrote:
> On 12.10.2013 03:22, Franz wrote:
> > On Fri, Oct 11, 2013 at 11:40 AM, Axon wrote:
> >
> >> On 10/11/13 06:25, Индарил Шприц wrote:
> kmix, and Phonon
> >>>
> >>> also i tried pavucontrol in Dom0 from co
On Saturday, February 11, 2017 at 7:37:22 PM UTC+1, 01v3g4n10 wrote:
> On Saturday, February 11, 2017 at 3:23:38 PM UTC, peter.p...@gmail.com wrote:
> > I enabled "login at boot" during installation (3.2).
> > How can i disable it again?
> >
> > Thanks,
> > Peter.
>
> Make sure that any instances
I enabled "login at boot" during installation (3.2).
How can i disable it again?
Thanks,
Peter.
--
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+unsub
30 matches
Mail list logo
