On Monday, July 29th, 2024 at 08:28, colony.three via qubes-users
wrote:
>
>
> > My recommendation is:
>
> > 1. Create a trusted VM to run WireGuard or a key-protected onion
> > service.
> > 2. Allow that VM (and only that VM) to connect to sshd in dom
hole OS.
On one machine I don't want to install all my server software in template
debian, just to spin off qubes from it. Do I have to clone template debian for
each individual service?
I've tried to understand this but it doesn't address my questions:
https://dev.qubes-os.org/proje
On Saturday, July 27th, 2024 at 12:53, Demi Marie Obenour
wrote:
>
>
> On Thu, Jul 25, 2024 at 02:09:02PM +0000, Qubes OS Users Mailing List wrote:
>
> > The server is a headless lights-out deal, and actually what I'd like to do
> > is connect x2go to dom0.
as user where user refers to the first dom0 user in qubes group and
with corresponding dom0 password
This is indecipherable.
Running sudo qubesctl --all state.highstate took a long time, until the first
stage timed out as unable to reach the network. No wonder, /etc/resolv.conf
symlinks
On Mon, Jun 17, 2024 at 12:02:25PM +0200, 'Rune Philosof' via qubes-users wrote:
> 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 swit
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 <
qu
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
AppVM Firefox,
it works like a breeze.
It seems that it could be an issue with the Whonix. Are there any
limitations in the Whonix design that prevent the beast from connecting
to the VPN over Tor? I remember that the 1.4.4 in the Qubes 4.1 it was
working.
Any workarounds?
'taran1s' via qubes
That seems promising.
Does it mean that the whole procedure is still the same just instead of
unzipping the 1.4.4 one downloads the replace-iptables-with-nftables and
it should work as the original 1.4.4 on Qubes 4.1.
Will it work as a VPN over Tor including the Tor browser?
Chris Bensch
> Do you have any recommendation how to solve that?
I just use a simplified version of
https://privsec.dev/posts/qubes/using-mullvad-vpn-on-qubes-os/
to run the Mullvad GUI directly. Going by the time stamp on my note
file, it has been working very reliably for most of a year
Does anyone have the VPN running through the srcipt from tasket? Were
there any changes in the 4.2 that can prevent it to run?
https://github.com/tasket/Qubes-vpn-support/tree/v1.4.4
I can get the VPN running from within the vpn proxy (I know it is not
recommended) and firefox shows it exits
s 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-u
as the original media qube.
I add MimeType=video/x-matroska to the desktop file and re-run the xdg-mime
command.
I still get the same error.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving e
ing
used, before running xdg-mime, to get it to work.
> And there it is: xdg-open wrongly detects gnome3 which is not
> installed. Then I checked:
>
> $ printenv | grep XDG_CURRENT_DESKTOP
> XDG_CURRENT_DESKTOP=X-QUBES ## NOT XFCE, which is the correct value
XDG_CURRENT_DESKTOP
with qvm-copy works.
Opening the copied files with xdg-open or qubes-open works in the dvm.
Opening media files in mplayer in the disposable qube with qvm-open-in-dvm used
to work.
It stopped working after I switched the media qube's template from
debian-11-minimal to debian-12-minimal.
I used qubesctl
I have a simple question, around "things that you have" (like sec.
tokens, etc).
Many "fido tokens" (yubi, nitro, google) allow NFC communication, most
computers as well, but i do not find anything in my qubes (maybe the
chips acts as USB client and my US
rror. Is it possible to
> > designate an appVM to behave similarly so it won't get shutdown
> > accidentally?
>
> Not as a user-facing feature AFAIK. But you could use the qubes.ext
> Python entry point
>
> https://github.com/QubesOS/qubes-core-admin/blob/v4.2.21/qubes/ext
ate an appVM to behave similarly so it won't get shutdown
> accidentally?
Not as a user-facing feature AFAIK. But you could use the qubes.ext
Python entry point
https://github.com/QubesOS/qubes-core-admin/blob/v4.2.21/qubes/ext/__init__.py#L57-L59
to add another "domain-pre-shutdown
On 2024-03-26 23:05, 'జిందం వాఐి' via qubes-users wrote:
On 2024-03-26 22:18, Andrew David Wong wrote:
On 3/25/24 11:25 AM, 'జిందం వాఐి' via qubes-users wrote:
As you can see, only Intel processors are listed. I'm not personally
aware of any changes since then, but when it comes to Qubes
On 2024-03-26 22:18, Andrew David Wong wrote:
On 3/25/24 11:25 AM, 'జిందం వాఐి' via qubes-users wrote:
As you can see, only Intel processors are listed. I'm not personally
aware of any changes since then, but when it comes to Qubes-certified
hardware, you should always consult the vendor's
* i see an option to purchase
laptop for amd also on their
website
* is this certified with only
intel?
--
regards,
జిందం వాఐి [ jindam, vani ]
web_ jindam.neocities.org
[matrix]_ @jindam:oikei.net
--
You received this message because you are subscribed to the Google Groups
"qubes-users&q
Sorry, i discuss in the Qubes Communityfaster responses, better
systemthen google groups
Bapak Ireng schrieb am Montag, 25. März 2024 um 16:32:33 UTC+1:
> i tried sudo /usr/libexec/initial-setup/initial-setup-graphical
>
> and the following is the output / result:
>
>
i tried sudo /usr/libexec/initial-setup/initial-setup-graphical
and the following is the output / result:
i tried to sent pictures, but google did not let me sent them. Sh
--
You received this message because you are subscribed to the Google Groups
"qubes-users&q
Hi, after successfully installing Qubes 4.2 i am left all alone to
configure network (internet) Access.
I appreciate it very much if somebody could guide me to the right options.
The question is so vague, no one can reasonably answer it.
Does sys-net start on boot?
Does it have access
Hi, after successfully installing Qubes 4.2 i am left all alone to
configure network (internet) Access.
I appreciate it very much if somebody could guide me to the right options.
Best regards, Bapak Hitam
--
You received this message because you are subscribed to the Google Groups
"
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
Without seeing the screenshot, I think I know the issue.
They are from the same repository.
qvm-template lists *all* the template in the repo, whereas
qvm-template-gui filters to only show the most recent supported
versions.
--
I never presume to speak for the Qubes team.
When I comment
ound. 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 Thursda
Hi one7two99,
I have Qubes and Linux already installed in different partitions in legacy
mode and both work fine. Now I need to install windows 10 (to run Fusion
360 for personal use). I don't want to install it as a qube as my hardware
is not very powerful. I don't need Bitlocker. Could you
Suspend works
On Monday, March 4th, 2024 at 2:33 PM, 'bozoslivehere' via qubes-users
wrote:
> ---layout:
> 'hcl'
> type:
> 'Mini PC'
> hvm:
> 'yes'
> iommu:
> 'yes'
> slat:
> 'yes'
> tpm:
> '2.0'
> remap:
> 'yes'
> brand: |
> AZW
Ethernet Controller [10ec:8168] (rev 15)
Intel Corporation Wi-Fi 6 AX200 [8086:2723] (rev 1a)
memory: |
29618
scsi: |
usb: |
4
certified:
'no'
versions:
- works:
'FIXME:yes|no|partial'
qubes: |
R4.2.0
xen: |
4.17.2
kernel: |
6.1.62-1
remark
an you run `sudo journalctl -b ` in sys-net and look for
any entries relating to networking devices.
It may be that you need specific drivers for the NIC, so knowing what it
is would be a help.
--
I never presume to speak for the Qubes team.
When I comment in the mailing lists I speak for myself
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 s
best, Bernhard
--
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://group
```bash
#!/bin/bash --
exec qvm-run-vm @dispvm /bin/firefox -- "'${1//\'/\'\\\'\'}'"
```
[/quote]
I believe this is a script improvement. The URL is not trusted data and
these safeguards do not have an impact on valid inputs.
--
You received this message because you are subscribed to
ly used in in policy files, but I assume
that it will work here too so long as you are running 4.1 or newer. So
the new file would look like this:
```bash
#!/bin/bash
qvm-run-vm '@dispvm' /bin/firefox "'$1'"
```
--
You received this message because you are subscribed to the Google Groups
"qube
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:
>>>
>>>&
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.
>
>Fo
?
--
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.c
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
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
c38
>
> brcmfmac-firmware 202312111.fc38 -> 202401152.fc38
>
> intel-gpu-firmware 202312111.fc38 -> 202401152.fc38
>
> mt7xxx-firmware 202312111.fc38 -> 202401152.fc38
>
> nvidia-gpu-firmware 202312111.fc38 -> 202401152.fc38
>
> realtek-firmware 2023
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
-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
> >
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
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,
> >
> >
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
-to-Berlin-time
clock displays 10:42 which is 1h and 3min wrong. If it was 1h exactly,
I'd guess a user-malconfig, but 3min ??
do you have some hints on that?
Thank you, Bernhard
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubs
:8168] (rev 07)
memory: |
65410
scsi: |
Samsung SSD 870 Rev: 1B6Q
usb: |
1
certified:
'no'
versions:
- works:
'yes'
qubes: |
R4.2.0
xen: |
4.17.2
kernel: |
6.1.62-1
remark: |
Everything seems fine
credit: |
code9n
link: | FIXLINK
.cpio attached.
Thanks for 4.2
On Sunday, January 21st, 2024 at 09:45
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
AX201 [8086:a0f0] (rev 20)
memory: |
16073
scsi: |
usb: |
3
certified:
'no'
versions:
- works:
'FIXME:yes|no|partial'
qubes: |
R4.2.0
xen: |
4.17.2
kernel: |
6.1.62-1
remark: |
FIXME
credit: |
FIXAUTHOR
link: |
FIXLINK
--
You
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
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 00
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
Major issue is that the touchpad does not work.Suspend/wake does work fine.Have not tested much beyond the above.Thanks.
--
You received this message because you are subscribed to the Google Groups "qubes-users" group.
To unsubscribe from this group and stop receiving emails fro
Most features works flawlessly.
I did not test suspend / sleep.
--
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.co
I actually had a similar issue. It ended up being a BIOS that refused to
detect rc3 is ISO format. Mounting the ISO and copying the files over to
a FAT formatted USB got around the boot issue but the qubes installer
doesn't see it's root partition then.
The working solution was to insert both
Works out of the box:
- networking (usb2lan)
- keyboard backlight
- build-in bluetooth
- sound
Works after tweaking:
- sceen is flickering unless adding "i915.enable_psr=0" in
/boot/efi/EFI/qubes/xen.cfg, more details:
https://wiki.archlinux.org/title/inte
successes while running the command.
I tried to remove i3lock in case of conflict, but i3-settings-qubes depends on
it.
I tried to compile slock without any patches, same error when running that.
I managed to get it to run with the PAM_auth patch, which replaces the use of
shadow, but I couldn't unlock
Corporation Ethernet Connection (2) I219-LM (rev 31)
Intel Corporation Wireless 8265 / 8275 (rev 78)
memory: |
16035
scsi: |
SAMSUNG MZ7LN256 Rev: 1H3Q
usb: |
1
versions:
- works:
'FIXME:yes|no|partial'
qubes: |
R4.1
xen: |
4.14.6
kernel: |
6.4.7-1
remark: |
FIXME
credit: |
FIXAUTHOR
link: |
FIXLINK
On Fri, Sep 08, 2023 at 08:10:44AM +0200, haaber wrote:
> I tried to configure split-ssh according to the tutorial on qubes pages,
> in its simple version (just agent, but no keepass integration). But now
> ssh offers *all* my private keys to *all* servers, which is odd, but
> m
+1
Same problem here.
--
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 vi
;, " ~
> grains['osfullname'] ~ ", " ~ grains['os_family'] }}
>
> returns
> grains['os']=Fedora, grains['os']=dom0, grains['osfullname']=Qubes,
> grains['osfamily']=RedHat
>
> Any ideas why this happens? How to branch correctly in a state file depending
> on
, 2:02 PM, 'Gandalfen' via qubes-users - qubes-users at
googlegroups.com wrote:
> ---
> layout:
> 'hcl'
> type:
> 'notebook'
> hvm:
> 'yes'
> iommu:
> 'yes'
> slat:
> 'yes'
> tpm:
> 'unknown'
> remap:
> 'yes'
> brand: |
> ASUSTeK COMPUTER INC.
>
Device [8086:4641] (rev 02)
chipset-short: |
Intel [8086:4641] (rev 02)
gpu: |
Intel Corporation Device [8086:46a6] (rev 0c) (prog-if 00 [VGA controller])
gpu-short: |
Intel Iris Xe Graphics
network: |
MEDIATEK Corp. Device 7961
memory: |
16076
scsi: |
usb: |
1
versions:
- works:
'partial'
qubes
install time untick the 'sysusb' creation, and then create sysusb by
hand and attach just 1 USB controller at a time (following the
instructions here
https://www.qubes-os.org/doc/usb-qubes/#how-to-create-a-usb-qube-for-use-with-a-usb-keyboard)
Another way to find out which device is causing the system
On Wed, 2023-08-09 at 20:53 +0100, Edwin Török wrote:
> On Mon, 2023-08-07 at 21:45 +0100, 'Edwin Török' via qubes-users
> wrote:
> >
> > Must NOT use a USB qube. Using a USB qube results in an
> > instant
> > host reboot as soon as the USB qube is booted
On Mon, 2023-08-07 at 21:45 +0100, 'Edwin Török' via qubes-users wrote:
>
> Must NOT use a USB qube. Using a USB qube results in an instant
> host reboot as soon as the USB qube is booted (same issue happen on
> KVM
> when attempting to pass through any USB c
: Not affected
Tsx async abort: Not affected
edwin ~ [4.14.1] ❯ cat /mnt/home/edwin/Qubes-HCL-
Gigabyte_Technology_Co___Ltd_-B650E_AORUS_MASTER-20230807-162029.yml
---
layout:
'hcl'
type:
'Desktop'
hvm:
'yes'
iommu:
'yes'
slat:
'yes'
tpm:
'2.0'
remap:
'yes'
brand
In my desktop Qubes system the mainboard died. So I bought a new one.
Unfortunately I didn't make a backup for some days.
After building the new hardware system my Qubes installation from the old ssd
doesn't start there.
(Somehow the system freezes or at least the keyboard is being switched off
ncoming
```
I dont think the chown calls are needed, but I put them in , and have
not removed them.
Works as you would expect.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails fro
-add -L
You seem to be running the "ssh-agent.service" in your work qube. This
is not part of the linked setup guide. There only one agent is running
and that is in the vault qube.
The "clients" (e.g. work qube) only redirect the communication via
socat, qubes RPC and the
On Tue, Jun 06, 2023 at 01:24:18PM -0500, Leo28C wrote:
> I managed to set up a pi-hole qube and make it my network's DNS
> filtering/caching server. Ironically, it works flawlessly across my network
> EXCEPT it completely breaks DNS for all other qubes in the same system. On
> Debian
C 12 (NUC12WSHv5). QubesOS with the "kernel latest" option runs
> great. Most importantly, it is a dream to work on a fanless computer that
> still runs completely silent under heavy load despite various Qubes running
> in parallel including several standalone machines.
Here is my HCL report for the motherboard MSI MEG x670e ACE.
Booting even the installer works only with the x2apic=false flag set in
both xen and linux lines in grub. Automatic creation of networking related
qubes (sys-firewall and sys-net) during first configuration after install
crashes the pc
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/c50703f7-a6ae-b659-a618-cb
Qubes wrote:
Qubes wrote:
I am just trying my luck here with an issue that i have been unable to
resolve on my Qubes system for a long time now. I have been looking
into this problem quite a bit but i cannot seem to find a solution
anywhere. Perhaps someone on this list has experienced
Qubes wrote:
I am just trying my luck here with an issue that i have been unable to
resolve on my Qubes system for a long time now. I have been looking into
this problem quite a bit but i cannot seem to find a solution anywhere.
Perhaps someone on this list has experienced the same and has
I am just trying my luck here with an issue that i have been unable to
resolve on my Qubes system for a long time now. I have been looking into
this problem quite a bit but i cannot seem to find a solution anywhere.
Perhaps someone on this list has experienced the same and has found a
solution
--- Original Message ---
On Friday, May 26th, 2023 at 4:24 AM, 'Stuart Perkins' via qubes-users
wrote:
> Bottom post is the standard on this list. See my response at the bottom... :)
>
> On Thu, 25 May 2023 19:02:23 +
> "'sonnenfinsternis' via qubes-u
Bottom post is the standard on this list. See my response at the bottom... :)
On Thu, 25 May 2023 19:02:23 +
"'sonnenfinsternis' via qubes-users" wrote:
>Sounds helpful, I'll try it when I get a chance, thanks :) After reading this
>[1], I can now even use my USB mous
with this great community :)
1: https://www.qubes-os.org/doc/usb-qubes/#usb-mice
--- Original Message ---
On Thursday, May 25th, 2023 at 8:39 AM, haaber wrote:
> Hi
>
> > 5) The question about autocomplete in the terminal has been resolved. This
> > was indeed
uot; option runs
> great. Most importantly, it is a dream to work on a fanless computer that
> still runs completely silent under heavy load despite various Qubes running
> in parallel including several standalone machines.
>
> Best regards :-)
> Eichennarr
>
> ---
>
Here's my review of the cirrus7 nimbini v3, which is largely based on the Intel
NUC 12 (NUC12WSHv5). QubesOS with the "kernel latest" option runs great. Most
importantly, it is a dream to work on a fanless computer that still runs
completely silent under heavy load despite var
/v1/by-fingerprint/DA5975C9ABC40C833B2F620B2A632C537D744BC7
>
> --
> 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...@googlegr
usage in Qubes. Unfortunately I haven't found
anything yet -_-.
2) I'll just stick with the existing ready-made templates for Linux then. If
there is a clickable solution at some point, I would still be very interested
in it though!
3) Too bad, but could have been. Then we just stick to opening
Qubes wrote:
Qubes wrote:
Qubes wrote:
Qubes wrote:
Qubes wrote:
I have noticed than when my computer wakes up from sleep the dom0
date and time updates as soon as my computer gets net connectivity,
but my appVMs can take a loong time before their date and time
also update
The documentation on [how to backup, restore and
migrate](https://www.qubes-os.org/doc/how-to-back-up-restore-and-migrate/)
says,
"When backing up dom0 using the Qubes backup tool (explained below),
only the home directory is backed up. Therefore, if there are files
outside of the
'unman' via qubes-users wrote:
On Tue, Jul 19, 2022 at 01:26:13PM +0200, Qubes wrote:
Qubes wrote:
'unman' via qubes-users wrote:
On Tue, Jul 19, 2022 at 08:41:40AM +0200, Qubes wrote:
The procedure to install KDE in 4.1 doesn't seem to work, is
that expected
behavior?
Yes, the group isn't
Demi Marie Obenour:
On Sat, May 13, 2023 at 10:57:00AM +, Qubes OS Users Mailing List wrote:
Andrew David Wong:
On 5/12/23 4:31 AM, 'taran1s' via qubes-users wrote:
If anon-whonix AppVM is set to use mullvad-VPN that is connected to sys-whonix
it doesn't connect to internet. If one
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/58dbf781-0be6-aae5-75ca-6b
Andrew David Wong:
On 5/12/23 4:31 AM, 'taran1s' via qubes-users wrote:
If anon-whonix AppVM is set to use mullvad-VPN that is connected to sys-whonix
it doesn't connect to internet. If one uses Debian or Fedora based AppVM and
runs vanilla Firefox, it works like a breeze.
Any ideas how
On Thu, 11 May 2023 15:20:17 -0700
Andrew David Wong wrote:
>Dear Qubes Community,
>
>The Fedora Project has
>[announced](https://lists.fedoraproject.org/archives/list/annou...@lists.fedoraproject.org/thread/4GXBZJSGQ2PEKIBM2APCTLXBS6IDKSOP/)
> that Fedora 36 will reach EOL
or Fedora
based AppVM and runs vanilla Firefox, it works like a breeze.
Any ideas how to solve this?
Leo28C:
I followed this guide: https://micahflee.com/2019/11/using-mullvad-in-qubes/
(works with others too not just Mullvad)
On Wed, May 10, 2023 at 9:51 AM 'taran1s' via qubes-users <
qubes-us
Hi,
What is the best practice for setting up a VPN proxy in Qubes these days
(for Mullvad, VPN over Tor)?
I found two versions for setup of VPN proxy in Qubes:
The first one is from tasket called Qubes-vpn-support. The last version
is dated Dec 2020: https://github.com/tasket/Qubes-vpn
Qube as a standalone VM. The integration works fine thanks
to qubes-windows-tools. But is there something similar for standalone Linux
VMs? Assuming there is a LinuxMint in a standalone qube: What is the best way
to exchange files or pass the clipboard to other "normal" Qubes? Via a
Here is my report on the TUXEDO InfinityBook S 15 Gen7. Great laptop, but
honestly it is quite annoying in the long run that the fan blows so loud when
you work in many Qubes in parallel :-(
Greetings!
Eichennarr
---
layout:
'hcl'
type:
'notebook'
hvm:
'yes'
iommu:
'yes'
slat:
'yes
Qubes wrote:
Qubes wrote:
Qubes wrote:
Qubes wrote:
I have noticed than when my computer wakes up from sleep the dom0
date and time updates as soon as my computer gets net connectivity,
but my appVMs can take a loong time before their date and time
also update. Is there any explanation
Qubes wrote:
Is this normal/expected behavior?
As has been discussed in this thread, making changes in `/etc/skel` in a
template of an existing VM does not propagate to the VM. However, if you
change the VMs template to a different template it seems like
`/etc/skel` is copied to `/home/user
Qubes wrote:
Vít Šesták wrote:
Perhaps my search terms are just out of whack, but I have had a good
look around and I cannot find a system wide location for
`~/.config/qt5ct/qt5ct.conf` that controls the Style and Icon
Theme for
example.
It's easy to find.
1. Me: Do you know
1 - 100 of 4398 matches
Mail list logo
