Re: [qubes-users] Salt: Jinja Error in templates but NOT dom0!?

[Frédéric Pierret]

Hello,

Just writing what I'm thinking (not Salt expert at all!), you are probably 
missing default value in the .get(): .get('kernelrelease', SOMETHING_DEFAULT)

Le 5/3/22 à 11:01, 'Johannes Graumann' via qubes-users a écrit :

I have the following `*.sls` in my `salt`setup:

{% if salt['pkg.version_cmp'](salt['grains'].get('kernelrealease'), '5.12') < 0 
%}
move broken AX260 wifi blob out of the way:
   file.rename:
     - name: /usr/lib/firmware/iwlwifi-ty-a0-gf-ao.pnvm.xz.bak
     - source: /usr/lib/firmware/iwlwifi-ty-a0-gf-ao.pnvm.xz
     - force: True
     - runas: root
{% endif %}

This is supposed to automate moving `linux` firmware out of the way that 
interferes with my wifi card's operation under certain non-cutting edge kernel 
versions (as present in `QubesOS`).

I can run this `*.sls`fine on `dom0` (where it doesn't make much sense, 
respectively the change isn't necessary), but if I target the templates (and 
particularly the one `sys-net` is based on), `salt` balks on the first line. 
There's a lot of traceback, but the most readable message appears to be along 
the lines of

`Jinja error: get() missing 1 required positional argument: 'default'`

Does anyone have any pointers as to what may be going on here, how to better debug 
(error output from `dom0`--> Email VM?) and how to fix?

Thanks in advance.

Joh




Best,
Frédéric

--
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/5a81c61a-a62e-fd60-691f-53fb0e11ae6f%40qubes-os.org.


OpenPGP_signature
Description: OpenPGP digital signature

[qubes-users] Qubes OS hardware costs

[Frédéric Pierret]

Dear all,

I would like to share with you all the list of hardware that I have allocated 
for the Qubes OS Project's infrastructure: continuous integration, daily and 
weekly builds, and reproducible builds.

# CI/CD runners (all Qubes OS repositories)
HP DL360 Gen8:
  - Operating system: Debian
  - 2 * Intel(R) Xeon(R) CPU E5-2670 @ 2.60GHz
  - 128GB ECC RDIMM DDR3
  - 8 * 146GB HDD (SAS)

# CI/CD runners (Weekly ISO builds and Gentoo repositories (build and serve))
# Reproducible builds runners (see https://beta.tests.reproducible-builds.org/)
# Remark: only allocated at half of the global resources; the other half is my 
work machine.
DELL PowerEdge R730:
  - Operating system: Qubes OS
  - 2 * Intel(R) Xeon(R) CPU E5-2690 v4 @ 2.60GHz
  - 128GB ECC LDIMM DDR4
  - 8 * 300GB HDD (SAS)
  - 8 * 256GB SSD

# CI/CD runner for next generation Qubes builder
Custom Computer:
  - Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz
  - 16 GB Non-ECC DIMM DDR3
  - 2 * 256GB SSD

# openQA runners
HP DL360 Gen8:
  - Operating system: openSUSE
  - 2 * Intel(R) Xeon(R) CPU E5-2670 @ 2.60GHz
  - 128GB ECC RDIMM DDR3
  - 8 * 146GB SAS HDD

# openQA runners
HP DL360 Gen7:
  - 2 * Intel(R) Xeon(R) CPU X5650 @ 2.67GHz
  - 64GB ECC RDIMM DDR3
  - 8 * 146GB SAS HDD

# Reproducible builds snapshot.notset.fr service (key for rebuilding Debian)
HP DL380e Gen8:
  - Operating system: openSUSE
  - 2 * Intel(R) Xeon(R) CPU E5-2430L v2 @ 2.40GHz
  - 32GB ECC RDIMM DDR3
  - 8 * 4TB HDD (SATA)

This is hardware I've paid for out of my own pocket over the past four years 
and that I run at home in a controlled environment. I've recently finished 
optimizing the on-demand startup and auto-shutdown of the GitLab and openQA 
machines.

All of this was and continues to be a non-negligible cost (several thousand 
euros over the years) for me in terms of energy and hardware. As this is 
refurbished hardware, from time to time I need to replace some drives and 
failing memory modules. To give you an idea, as of today and since the middle 
of January 2022, all of this hardware (including auxiliary networking and 
firewall hardware) has consumed 2023 KWh (according to my watt-meter and with a 
daily average rate of ~20-25 KWh).

If any of you could possibly be financial or hardware sponsors, I would greatly 
appreciate your generosity and support. Please don't hesitate to contact me or 
Marek if you can help with this. We already have some machines in the cloud 
that were generously offered by the Qubes OS community. (Marek can provide 
details about the hardware.) In general, renting similar machine specs in the 
cloud as what I can run at home is very expensive, and we cannot afford that. 
This is why I prefer to invest in hardware that we control, especially when 
part of it is used to deliver content like the Qubes OS weekly ISO builds.

Best regards,
Frédéric

--
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/25d24f3f-ac60-d29d-e4ed-6c4fedb0ad04%40qubes-os.org.


OpenPGP_signature
Description: OpenPGP digital signature

Re: [qubes-users] XSAs released on 2021-11-23

[Frédéric Pierret]

Le 11/28/21 à 10:10, Qubes a écrit :

'awokd' via qubes-users wrote:

Qubes:


Are you currently running it, can you give any feedback?


Yes, running 4.1. Haven't tried gui or audio domains yet, but so far everything 
works fine. Think a couple people have run into no QWT being available for 4.1, 
but it's not something I need.



A couple of things I am not sure of doing a backup, fresh install of 4.1 rc2, 
and then restoring, is for example current templates, like Debian 10 as well as 
all the clones of this template for example and the customizations done to 
each. Is it possible to directly 'transfer' Templates via backup/restore method 
to 4.1 rc2. Does one need to perhaps install new qubes-specific-packages for 
new features/integration/or-the-like things to work. Or should everything 
pretty much work out the 'box'?



It does not work out of the box. Migrating your template from R4.0 to R4.1 need manual 
steps like adding Qubes R4.1 repositories and upgrade your templates. As you will not be 
able to have GUI once your template from R4.0 are restored into R4.1, you will need to 
use "virsh console" into dom0 to access your templates.

Best regards,
Frédéric

--
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/9c98cb56-173b-14e9-7018-d05350b958ec%40qubes-os.org.


OpenPGP_signature
Description: OpenPGP digital signature

Re: [qubes-users] Qubes OS 4.1.0-rc1: No match for argument: qubes-windows-tools

[Frédéric Pierret]

Le 10/17/21 à 15:26, 'fossdd' via qubes-users a écrit :

By installing `qubes-windows-tools` in dom0 it says that this package
does not exist.

How can I install it?



You can't. We have not build it for R4.1.

Check several threads on the forum talking about the community support for 
Windows in Qubes 4.1.

Best,
Frédéric

--
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/8d55ed66-9a0a-6a78-94f6-8a988f5123a3%40qubes-os.org.


OpenPGP_signature
Description: OpenPGP digital signature

[qubes-users] Re: QubesOS weekly builds

[Frédéric Pierret]

Hi,

Le 3/21/21 à 11:33 PM, Frédéric Pierret a écrit :

Hi,
As some of you may know, months(years?) ago, I've setup a pipeline that is 
automatically PR latest kernels for Qubes OS and more recently, pulseaudio 
headers too. This is done every week.

At some point, I added the build of ISO including kernel-latest for users who 
were having issues with latest hardware. I stopped it quickly because we were 
merging more and more kernel versions thank to the help of automatic PR and 
Qubes point releases.

Due to recent troubles with kernels 5.4.X and 5.10.X, I've decided to add again 
to this weekly pipeline, the build of a fresh Qubes R4.1 ISO. I don't build any 
package or any template. It uses only Qubes OS repositories. The qubes-builder 
conf is: 
https://github.com/QubesOS/qubes-release-configs/blob/master/R4.1/qubes-os-iso-full-online.conf
 and the kickstart can be found here: 
https://github.com/QubesOS/qubes-installer-qubes-os/blob/master/conf/iso-full-online.ks.

Please note that, contrary to my first attempt, I don't include kernel-latest kernels. 
It's a standard R4.1 ISO as if Marek would release one. It is built in a dedicated AppVM 
together with Split GPG. The ISOs are signed by "fepitre-bot" 
1C8714D640F30457EC953050656946BA873DDEC1. Some of you already download latest R4.1 devel 
ISOs in openQA but they are not signed and not necessary built in a safe environment 
because it's only for CI purposes. That's a solution between CI ISOs and R4.1 alpha 
release.

That said, the ISO(s) can be found on my self hosted server: 
https://qubes.notset.fr/iso/.

Best regards,
Frédéric



I've added support to qubes-builder the possibility to build an ISO having the 
installer running kernel-latest and the installed QubesOS too. For 
documentation: 
https://github.com/QubesOS/qubes-builder/blob/master/doc/Configuration.md#iso_use_kernel_latest
 (pretty simple, isn't it?)

I'm pleased to announce you that I've added that to my weekly build pipeline where I will 
still build both versions: the standard and the one with kernel-latest embedded. Same as 
previously, you can find signed ISOs here https://qubes.notset.fr/iso/ and also result of 
openQA tests too (see openqa.qubes-os.org with build tag having -kernel-latest. For 
example: 
https://openqa.qubes-os.org/tests/overview?build=20210610-kernel-latest-4.1&distri=qubesos&version=4.1&groupid=1).

The goal is still the same: providing testing QubesOS images built in a sane 
environment for latest drivers support by Linux until LTS kernels would have 
enough backports for very recent hardware.

A final remark like on the Discourse thread, I do recurrent cleaning for space 
consideration. I keep only ISOs for the current month now.

Best regards,
Frédéric

--
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/5068b322-bda1-f92b-cbed-023a9f925692%40qubes-os.org.


OpenPGP_signature
Description: OpenPGP digital signature

Re: [qubes-users] Re: [qubes-devel] QubesOS weekly builds

[Frédéric Pierret]

Hi Holger,

Le 3/31/21 à 12:29 AM, Holger Levsen a écrit :

Hi Frédéric,

On Sun, Mar 21, 2021 at 11:33:05PM +0100, Frédéric Pierret wrote:

Due to recent troubles with kernels 5.4.X and 5.10.X, I've decided to add
again to this weekly pipeline, the build of a fresh Qubes R4.1 ISO. I don't
build any package or any template. It uses only Qubes OS repositories.


yay, that's very nice and useful! thank you!


You are welcome.


Please note that, contrary to my first attempt, I don't include kernel-latest 
kernels.


So do they have 5.4.x or 5.10.x?


R4.1 has switched to 5.10.X as default LTS that's a very good point for new 
hardware.


The ISOs are signed by "fepitre-bot" 1C8714D640F30457EC953050656946BA873DDEC1.


nice!


That said, the ISO(s) can be found on my self hosted server: 
https://qubes.notset.fr/iso/.


I'll give them a try in the next days on some new hardware which doesn't
work with the iso from December but should be working now...

I guess you have ran diffoscope on two builds, how is the result? Do you
already have this in CI too? (this is for testing for reproducible builds...)



Not yet but I've discussed few days ago with Marek on how to do the build 
integration in order to reproduce the ISO. I'm finishing few Fedora related 
reproducible things then I guess I would do this, depending on what Marek has 
in mind for the schedule.

Additionally, I've added few days ago the automatic openQA trigger for each ISO I build: 
https://openqa.qubes-os.org/group_overview/1. It's jobs corresponding to 
"BUILD20XXYYZZ-4.1" where in the settings, for example this one: 
https://openqa.qubes-os.org/tests/16829#settings, it downloads from my hosting repository 
the built ISO.

Best regards,
Frédéric


--
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/dbc4136b-ecf3-0583-a579-0a60d673672c%40qubes-os.org.


OpenPGP_signature
Description: OpenPGP digital signature

Re: [qubes-users] Custom LAN Network with dhcpd

[Frédéric Pierret]

Hi,

Le 3/15/21 à 12:40 PM, 'Nyx' via qubes-users a écrit :

Hello,

I am trying to implement an internal Qubes LAN with HVMs that receive dhcp from 
a netvm using dhcpd. A classical network layout sort of speak. Reading Xen 
Networking makes it look possible but Qubes auto configuring the VM networking 
is being a bit troublesome for what I am trying to setup. Note that the entire 
network will be on Qubes only with no internet access.

The reason I am trying to set this up is I have some HVMs that are not getting 
an ip through dhcp and I cannot access them to set ip manually (they are 
vulnhub vms). I was thinking of just running an hvm with virtualbox but the 
limits of emulation only wont work. I read that qubes can be recompiled to 
enable nested virtualization to get that working but if there is a way to 
create a custom network that would be preferred.

Is there a way to allow a set of HVMs to get ip from a netvm running dhcp and 
communicate like a classic network?

--


You might be interested in such thing: 
https://github.com/fepitre/qubes-mgmt-salt-qubes-server/blob/devel-140320/qubes-server.png

I'm currently working on several adjustment recently (not pushed) but for you case, you 
might want to start by using usual "bridge" for which we have support of this 
in QubesOS-contrib:

dom0 component: 
https://github.com/QubesOS-contrib/qubes-core-admin-addon-bridge-device
vm component: 
https://github.com/QubesOS-contrib/qubes-core-agent-linux-addon-bridge-device

When this installed, in a given AppVM named for example "lan-net", with NetworkManager you can create a bridge interface named for example 
"br0" that will be made available as bridge device to be attached. Then, in dom0, running "qvm-device bridge" will show you the 
bridge created in "lan-net". At this point, this is exactly like USB, BLOCK or MIC devices. You can attach an AppVM named for example 
"personal" to this bridge (meaning it will have an interface that is linked into the bridge): "qvm-device bridge attach personal 
lan-net:br0". You can do that for multiple VMs, and then, you would have local classical network between several VMs. Even more, you can attach 
a physical interface into "br0" and link external network with other machines.

Notes:
 - It supports options like: "qvm-device bridge attach personal lan-net:br0 
--option=ip=192.168.0.1 --option=netmask=255.255.255.0 
--option=gateway=192.168.0.254"
 - Be careful that using standard bridge network model is NOT the Qubes model 
using NAT and based on isolation of each component.
 - You would need to probably adjust iptables if your "lan-net" has a NetVM.

I plan to make proper README and documentation describing this and also related 
Qubes-server formula soon. In the mean time I can help here or on discourse.

Best,
Frédéric

--
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/187fb4d0-a475-0a95-8c9f-a9b9ce3aa441%40qubes-os.org.


OpenPGP_signature
Description: OpenPGP digital signature

Re: [qubes-users] Re: QubesOS weekly builds

[Frédéric Pierret]

Le 3/22/21 à 2:03 AM, Beto HydroxyButyrate a écrit :

Trying to use the info provided to kick off my own ISO build.
This posted links to does not use the `QubesBuilder` approach, as it references 
stuff apparently checked out to ~/qubes-src, rather than 
~/qubes-builder/qubes-src.

Is this different approach to building documented?  What else should  check out to 
~/qubes-src?  How does this fit into the "Development Workflow"?

Per those docs:

/Qubes is split into a bunch of git repos. This are *_all _*contained in the 
qubes-src directory under qubes-builder. Subdirectories there are separate 
components, stored in separate git repositories./
/
/
Just making ~/qubes-src a symbolic link to ~/qubes-builder/qubes-src does not 
fix things as, despite the claim that /this are all contained/  in 
~/qubes-builder/qubes-src, the two new git repos referenced are not contained 
there.



I forgot to mention also that the reference used in builder.conf for 
INSTALLER_KICKSTART=ZZZ is a path under the build chroot and not to your local 
qubes-builder. The build chroot has sources from qubes-builder/qubes-src copied 
to chroot-dom0-fcXX/home/user/qubes-src. The value for the kickstart is then 
used when build is ran under the chroot. That probably deserves a note in the 
doc if it's not the case.

Frédéric

--
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/e5620fdb-2379-f1ec-c85b-4ba44bd1d3fb%40qubes-os.org.


OpenPGP_signature
Description: OpenPGP digital signature

Re: [qubes-users] Re: QubesOS weekly builds

[Frédéric Pierret]

Le 3/22/21 à 2:03 AM, Beto HydroxyButyrate a écrit :

Trying to use the info provided to kick off my own ISO build.
This posted links to does not use the `QubesBuilder` approach, as it references 
stuff apparently checked out to ~/qubes-src, rather than 
~/qubes-builder/qubes-src.

Is this different approach to building documented?  What else should  check out to 
~/qubes-src?  How does this fit into the "Development Workflow"?




Due to recent troubles with kernels 5.4.X and 5.10.X, I've decided to add again to this 
weekly pipeline, the build of a fresh Qubes R4.1 ISO. I don't build any package or any 
template. It uses only Qubes OS repositories. The qubes-builder conf is: 
https://github.com/QubesOS/qubes-release-configs/blob/master/R4.1/qubes-os-iso-full-online.conf
 

 and the kickstart can be found here: 
https://github.com/QubesOS/qubes-installer-qubes-os/blob/master/conf/iso-full-online.ks 
.


It's written "qubes-builder" conf. So use this as builder.conf and that's all: 
make iso. The kickstart reference provided is the one used by this conf: 
https://github.com/QubesOS/qubes-release-configs/blob/master/R4.1/qubes-os-iso-full-online.conf#L24.
 Meaning the installer will use the file in installer-qubes-os sources: 
https://github.com/QubesOS/qubes-installer-qubes-os/blob/master/conf/iso-full-online.ks

Frédéric

--
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/95429f87-1632-15d3-a7e1-8285407eec56%40qubes-os.org.


OpenPGP_signature
Description: OpenPGP digital signature

[qubes-users] QubesOS weekly builds

[Frédéric Pierret]

Hi,
As some of you may know, months(years?) ago, I've setup a pipeline that is 
automatically PR latest kernels for Qubes OS and more recently, pulseaudio 
headers too. This is done every week.

At some point, I added the build of ISO including kernel-latest for users who 
were having issues with latest hardware. I stopped it quickly because we were 
merging more and more kernel versions thank to the help of automatic PR and 
Qubes point releases.

Due to recent troubles with kernels 5.4.X and 5.10.X, I've decided to add again 
to this weekly pipeline, the build of a fresh Qubes R4.1 ISO. I don't build any 
package or any template. It uses only Qubes OS repositories. The qubes-builder 
conf is: 
https://github.com/QubesOS/qubes-release-configs/blob/master/R4.1/qubes-os-iso-full-online.conf
 and the kickstart can be found here: 
https://github.com/QubesOS/qubes-installer-qubes-os/blob/master/conf/iso-full-online.ks.

Please note that, contrary to my first attempt, I don't include kernel-latest kernels. 
It's a standard R4.1 ISO as if Marek would release one. It is built in a dedicated AppVM 
together with Split GPG. The ISOs are signed by "fepitre-bot" 
1C8714D640F30457EC953050656946BA873DDEC1. Some of you already download latest R4.1 devel 
ISOs in openQA but they are not signed and not necessary built in a safe environment 
because it's only for CI purposes. That's a solution between CI ISOs and R4.1 alpha 
release.

That said, the ISO(s) can be found on my self hosted server: 
https://qubes.notset.fr/iso/.

Best regards,
Frédéric

--
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/802aed98-8415-a791-875b-d5cd9dade2b6%40qubes-os.org.


OpenPGP_signature
Description: OpenPGP digital signature

Re: [qubes-users] gentoo template missing

[Frédéric Pierret]

On 2/17/21 12:08 PM, yoge 67855 wrote:
> i cant install gentoo template using:
> sudo qubes-dom0-update --enablerepo=qubes-templates-community
> qubes-template-gentoo
>
> or
>
> sudo qubes-dom0-update --enablerepo=qubes-templates-community-testing
> qubes-template-gentoo
>
>
> how do i fix it ?


Gentoo template is only available for Qubes R4.1 in current alpha stage.

-- 
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/56080d2f-6d40-608e-d7d2-0be77f2fc193%40qubes-os.org.

[qubes-users] TemplateVM/StandaloneVM with python3.9

[Frédéric Pierret]

Hi,

For you information, in order to update all your TemplateVM/StandaloneVM having 
python3.9 like latest bullseye, Fedora 33, Gentoo, etc. with Salt or the Qubes 
Update widget, the mgmt-dvm needs to be switched to Fedora 33 template.

The technical reason can be found in 
https://github.com/saltstack/salt/pull/58518.

Best regards,
Frédéric

--
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/6e0c2cd2-9de4-75b9-dbb7-d7349372ebea%40qubes-os.org.


OpenPGP_signature
Description: OpenPGP digital signature

Re: [qubes-users] Installing Rofi on dom0 via contributed packages?

[Frédéric Pierret]

Le 12/16/20 à 7:42 PM, Stumpy a écrit :

On 12/16/20 1:26 PM, Rusty Bird wrote:

Stumpy:

[bob@dom0 ~]$ sudo qubes-dom0-update qubes-rofi

[...]

No Match for argument qubes-rofi


The package is called just "rofi":
https://contrib.qubes-os.org/yum/r4.0/current/dom0/fc25/rpm/


which seems to be similar to an error i get when i try to
install qubes-tunnel in a fed32 minimal template?


Looks like qubes-tunnel is in Fedora 32 current-testing, but hasn't
been uploaded to current yet:

https://contrib.qubes-os.org/yum/r4.0/current-testing/vm/fc32/rpm/
https://contrib.qubes-os.org/yum/r4.0/current/vm/fc32/rpm/
https://github.com/QubesOS-contrib/updates-status/issues?q=tunnel+r4.0+fc32

Rusty

 >
 >
Oi. That was too simple, can't belive I didnt try just "rofi" thanks for that.

As for fed32/tunnel, thanks I will follow those git status for it.

Much appreciated!!



Fedora 32 version for qubes-tunnel is currently uploading to stable. Sorry for 
the delay :)

Best,
Frédéric

--
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/807ce67b-3459-7b8f-0a81-3189a63204ee%40qubes-os.org.


OpenPGP_0x484010B5CDC576E2.asc
Description: application/pgp-keys


OpenPGP_signature
Description: OpenPGP digital signature

Re: [qubes-users] Q: Remove fedora-30 template

[Frédéric Pierret]

Le 11/28/20 à 7:25 PM, Ulrich Windl a écrit :

On 11/28/20 6:12 PM, Frédéric Pierret wrote:



Le 11/28/20 à 5:28 PM, Ulrich Windl a écrit :

Hi!

I've upgraded all my fedora-30 VMs to fedora-31, and before going to fedora-32 
I wanted to get rid of one fedora-30 template that is unused.
However when I try to delete the qube from the Qubes Manager, I get this error: "VM 
installed by package manager: fedora-30"

I have no idea what to do. Did I miss something?

Regardfs,
Ulrich



Hi,

In dom0:

 sudo dnf -y remove qubes-template-fedora-30


Thanks a lot:
Dependencies resolved.

  Package Arch     
Version Repository    Size

Removing:
  qubes-template-fedora-30    noarch     
4.0.1-201912252234    @anaconda 
   4.5 G

Transaction Summary

Remove  1 Package

Installed size: 4.5 G
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
   Erasing : qubes-template-fedora-30-4.0.1-201912252234.noarch
   1/1
warning: file /var/lib/qubes/vm-templates/fedora-30/whitelisted-appmenus.list: 
remove failed: No such file or directory
warning: file 
/var/lib/qubes/vm-templates/fedora-30/vm-whitelisted-appmenus.list: remove 
failed: No such file or directory
warning: file /var/lib/qubes/vm-templates/fedora-30/root.img.part.04: remove 
failed: No such file or directory
warning: file /var/lib/qubes/vm-templates/fedora-30/root.img.part.03: remove 
failed: No such file or directory
warning: file /var/lib/qubes/vm-templates/fedora-30/root.img.part.02: remove 
failed: No such file or directory
warning: file /var/lib/qubes/vm-templates/fedora-30/root.img.part.01: remove 
failed: No such file or directory
warning: file /var/lib/qubes/vm-templates/fedora-30/root.img.part.00: remove 
failed: No such file or directory
warning: file 
/var/lib/qubes/vm-templates/fedora-30/netvm-whitelisted-appmenus.list: remove 
failed: No such file or directory
warning: file /var/lib/qubes/vm-templates/fedora-30/icon.png: remove failed: No 
such file or directory
warning: file /var/lib/qubes/vm-templates/fedora-30/clean-volatile.img.tar: 
remove failed: No such file or directory
warning: file /var/lib/qubes/vm-templates/fedora-30/apps.templates: remove 
failed: No such file or directory
warning: file /var/lib/qubes/vm-templates/fedora-30/apps.tempicons: remove 
failed: No such file or directory
warning: file /var/lib/qubes/vm-templates/fedora-30/apps: remove failed: No 
such file or directory
warning: file /var/lib/qubes/vm-templates/fedora-30: remove failed: No such 
file or directory
   Verifying   : qubes-template-fedora-30-4.0.1-201912252234.noarch
   1/1

Removed:
   qubes-template-fedora-30.noarch 4.0.1-201912252234


Complete!

It's gone in qube manager, but I still see a stale fedora-30-dvm-vm in the 
Qubes Menu. I got no idea how it was added, but there doesn't exist a Qube with 
a name like that (any more).

Regards,
Ulrich




Best,
Frédéric



I would suggest you to change fedora-30-dvm template to fedora 31+ and simply 
rename it. Else, the previous warnings are harmless.

Best,
Frédéric

--
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/f92fab40-e223-92ab-4ce9-771b5ea88ea7%40qubes-os.org.


OpenPGP_0x484010B5CDC576E2.asc
Description: application/pgp-keys


OpenPGP_signature
Description: OpenPGP digital signature

Re: [qubes-users] Q: Remove fedora-30 template

[Frédéric Pierret]

Le 11/28/20 à 5:28 PM, Ulrich Windl a écrit :

Hi!

I've upgraded all my fedora-30 VMs to fedora-31, and before going to fedora-32 
I wanted to get rid of one fedora-30 template that is unused.
However when I try to delete the qube from the Qubes Manager, I get this error: "VM 
installed by package manager: fedora-30"

I have no idea what to do. Did I miss something?

Regardfs,
Ulrich



Hi,

In dom0:

sudo dnf -y remove qubes-template-fedora-30

Best,
Frédéric

--
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/d521dbd4-ee73-b67c-9f18-afd3e899745e%40qubes-os.org.


OpenPGP_0x484010B5CDC576E2.asc
Description: application/pgp-keys


OpenPGP_signature
Description: OpenPGP digital signature

Re: [qubes-users] Announcement: "Qubes OS contributed packages are now available" by Marek Marczykowski-Górecki

[Frédéric Pierret]

Le 11/4/20 à 12:35 PM, Stumpy a écrit :

On 11/4/20 6:18 AM, Frédéric Pierret wrote:



Le 11/4/20 à 11:39 AM, Stumpy a écrit :

On 11/3/20 6:00 PM, Andrew David Wong wrote:

On 11/3/20 7:48 AM, Stumpy wrote:

On 10/5/20 9:00 PM, Andrew David Wong wrote:

Dear Qubes Community,

Marek has just published the following announcement:

https://www.qubes-os.org/news/2020/10/05/qubes-os-contributed-packages/

[...]


So do I understand this currently is only available for Fed31? and not 32?


I don't recall hearing that anywhere, and I can think of no reason why it would 
be true.


That was mentioned in one of the chat rooms but if true, and Fed31 is reaching 
EOL is there and ETA on when the contributed-packages will be available for 
Fed32?


As far as I know, the repos should already work on Fedora 32.

For the compatibility of the packages themselves, you'll have to check the 
package details, but I imagine that most, if not all, should be compatible.

P.S. -- Please don't reply to multiple lists.



Thank you, I will give it a try again. I just asked because I was able to get it to 
work with Fed31 but not Fed32 (tried Fed32 when the com packages were first made 
available".

Regarding the replies, my apologies, I just mindlessly clicked "reply all".



Packages should be available (or almost) for Fedora 32.

Please note this is a community effort. Authors of contribution package are 
kindly asked to help into maintaining or fixing build issues. Any package 
normally has a Github issue. I'm currently referencing all packages with extras 
info into a JSON here: 
https://github.com/QubesOS-contrib/qubes-contrib-configs/blob/master/packages.json.

Regards,
Frédéric



Please dont mistake my questions for ingratitude, I very very much appreciate 
the community effort!


Sure no problem, don't worry I did not take it as is. I was answering that to 
make precise the original announcement how we ask for help for this part.


A quick general question, you mentioned "almost", so does that mean that this 
community packages is distro ver dependent? Also, is there a way for users to be able to 
tell if a package is available yet for whichever template? (I am quite looking forward to 
trying rofi on my qubes4.0 setup!)


In a general manner, when we trigger build for a component, it launches build for every 
dist and versions. "Almost" here means possible build failure to be solved.


Regardless, I was in *awe* of how easy it was to setup the vpn proxy using the 
community qubes-tunnel package, albeit on fed31 (which is totally fine with me 
for now). Thank you all for this as I literally spent hours on previous 
installs trying to figure, and re-figure out how to do it!


I recently added Fedora 32 to distribution to be built into contrib (sorry for 
the late) and I'm triggering build (and fixing some issues) for every 
components since few days. I've launched the one for `qubes-tunnel` and Fedora 
32 just now.

Regards,
Frédéric

--
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/deaa250b-174a-fba3-efb0-42e76ef452aa%40qubes-os.org.


OpenPGP_0x484010B5CDC576E2.asc
Description: application/pgp-keys


OpenPGP_signature
Description: OpenPGP digital signature

Re: [qubes-users] Announcement: "Qubes OS contributed packages are now available" by Marek Marczykowski-Górecki

[Frédéric Pierret]

Le 11/4/20 à 11:39 AM, Stumpy a écrit :

On 11/3/20 6:00 PM, Andrew David Wong wrote:

On 11/3/20 7:48 AM, Stumpy wrote:

On 10/5/20 9:00 PM, Andrew David Wong wrote:

Dear Qubes Community,

Marek has just published the following announcement:

https://www.qubes-os.org/news/2020/10/05/qubes-os-contributed-packages/

[...]


So do I understand this currently is only available for Fed31? and not 32?


I don't recall hearing that anywhere, and I can think of no reason why it would 
be true.


That was mentioned in one of the chat rooms but if true, and Fed31 is reaching 
EOL is there and ETA on when the contributed-packages will be available for 
Fed32?


As far as I know, the repos should already work on Fedora 32.

For the compatibility of the packages themselves, you'll have to check the 
package details, but I imagine that most, if not all, should be compatible.

P.S. -- Please don't reply to multiple lists.



Thank you, I will give it a try again. I just asked because I was able to get it to 
work with Fed31 but not Fed32 (tried Fed32 when the com packages were first made 
available".

Regarding the replies, my apologies, I just mindlessly clicked "reply all".



Packages should be available (or almost) for Fedora 32.

Please note this is a community effort. Authors of contribution package are 
kindly asked to help into maintaining or fixing build issues. Any package 
normally has a Github issue. I'm currently referencing all packages with extras 
info into a JSON here: 
https://github.com/QubesOS-contrib/qubes-contrib-configs/blob/master/packages.json.

Regards,
Frédéric

--
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/b2221736-1606-8913-13ff-518951889d46%40qubes-os.org.


OpenPGP_0x484010B5CDC576E2.asc
Description: application/pgp-keys


OpenPGP_signature
Description: OpenPGP digital signature

[qubes-users] Re: Fw: qubes arch template

[Frédéric Pierret]

Le 10/31/20 à 6:15 PM, fargubz a écrit :

I have a large 4k monitor. How do I split the screen into 4 virtual screens and 
or work spaces?

‐‐‐ Original Message ‐‐‐
On Thursday, July 16, 2020 3:16 PM, Frédéric Pierret 
 wrote:


On 2020-07-16 16:51, fargubz wrote:


Hi Frederic,
Having the https://github.com/QubesOS/qubes-issues/issues/5503 issue.


Hi, please don't ask directly to any member of the Qubes OS project (including 
me :)). Ask to the list directly for which I CC it.



Hi,

I've already asked you to don't request help directly please. I've forwarded 
your previous email to the appropriate list. Please see: 
https://www.qubes-os.org/support/

Regards.

--
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/0aed498f-ed42-185c-f2de-95886914d717%40qubes-os.org.


OpenPGP_0x484010B5CDC576E2.asc
Description: application/pgp-keys


OpenPGP_signature
Description: OpenPGP digital signature

Re: [qubes-users] [unofficial] Qubes security advisory

[Frédéric Pierret]

Le 10/26/20 à 3:24 AM, 'J.M. Porup' via qubes-users a écrit :

#This email represents my analysis of the events of the last few weeks.
#It does not reflect the views of the Qubes Project or Qubes developers
#in any way.

My Qubes laptop got hacked by Five Eyes because they thought I was a
terrorist, when in fact I was only making clown videos.

That is surely one of the strangest sentences I have ever had to write,
so let me establish my bona fides. I'm a cybersecurity reporter [0],
and have covered cybersecurity and national security since 2013. I have
a masters degree in cybersecurity from Berkeley, and am currently working
on my OSCP. I've been using Qubes as my daily laptop since 2014. I'm not
a Qubes developer, but I would consider myself an advanced user.

I'm also a clown. (I gave a talk at Hackers on Planet Earth this year
called "Cybersecurity and Clown" [1]). In fact, when Covid hit I was in
France studying clown with Philippe Gaulier, the same clown master who
trained Sacha Baron Cohen. I'm a standup comedian and comic actor as well.

So when I made these incredibly silly clown videos [2], I didn't expect to find
myself under intense physical surveillance for several weeks. I mean, intense.
I've been under physical surveillance before for national security reporting
I've done (like this article [3]), but this was the closest I've ever seen the
security services here in Canada swing their elbows.

Knowing that physical surveillance is always accompanied by electronic
surveillance, I kept an eye on my devices. My phone got popped first. Zero-click
iPhone RCE. Two missed calls from a non-existent number right when the physical
surveillance started.

But would they risk a Qubes 0-day to go after me--for being a literal fscking 
clown?

They did, and per their new "flyswatter policy" left a JTRIG-style goodbye
present when they finally realized I'm just a journalist, and a clown.

One morning last week, I launched a disposable Debian 10 template with my preset
defaults of no netvm and a blank page preset--but instead a default page of
"https://www.youtube.com/"; appeared. It only happened once, but it was enough.

Does this rise to the standard of journalist proof I'm accustomed to? Of course
not. Would I risk my reputation by writing this email to the qubes-users list
if I was not confident in my assessment? What do you think?

So why am I writing this message? First, and most importantly, there is clearly
a great Qubes 0-day floating around that needs to be found and squashed. But 
also,
if Five Eyes are prepared to risk a Qubes 0-day on a clown, who would they *not*
risk it on? There must be dozens, if not hundreds, of active Qubes implants out
there right now.



Hi,
Sorry for what happened to you but before stating there "existing clearly a zero day" in 
default provided Qubes vs my "current customized Qubes seems compromised", further 
proof/investigation would be needed.

If from what what I read you go to this conclusion because your browser has 
unexpected homepage, there is so many ways for having a template compromised. I 
would say to be *really* careful to what to put into a template too. Here I 
mean mostly third party apps not coming from the underlying distribution. Don't 
hesitate to create scripts or using salt to recreate customized template and to 
reinstall template. Even better, don't hesitate to build template directly.

Best,
Frédéric

--
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/a2df2882-7ca1-837a-05df-c551abacb6cd%40qubes-os.org.


OpenPGP_0x484010B5CDC576E2.asc
Description: application/pgp-keys


OpenPGP_signature
Description: OpenPGP digital signature

[qubes-users] Re: Problème et panne sur mon ordi sous QubesOs

[Frédéric Pierret]

Le 10/22/20 à 9:00 PM, Yanis Ihaddaden a écrit :

Bonjour Monsieur Pierret,

Je suis un utilisateur de QubesOs depuis quelques mois,

Récemment depuis maintenant près de 20 jours j'ai un soucis avec son 
utilisation, sachant que je n'utilise que cette os sur ma machine, cela me pose 
problème.

Je m'adresse à vous, car je ne sais pas à qui m'adresser et ou dois je aller.

J'ai vu qu'il y avait des plateforme Freenode IRC  pour pouvoir communiquer 
avec d'autres utilisateurs, je n'ai pas su enregistrer mon nickname dessus , il 
y a aussi je pense discord, et github là ou j'ai trouvé votre adresse mail.

Le problème rencontré avec mon os:

Xen_version : 4.8.5-23.fc25

Linux 4.19.147-1.pvops.qubes.x86_64

Qubes os release 4.0 (R4.0)


Est tout simplement que j'ai perdu ma barre de fenetres la ou il y a la croix 
pour fermer et les 3 icones( réduire, agrandir, fermer ) de toutes les fenêtres 
, j'aurai cru a une mauvaise manipulation de ma part, ou que la résolution de 
l'un de mes 2 écrans déconnait, mais j'ai remarqué un autre problème le 
raccourcis pour basculer entre des fenetres, (Alt + Tab ) ne fonctionne pas.

Ce qui fait que je ne peux utiliser qu'une seule fenêtre, puis la fermer pour 
faire autre chose.

Voila j'ajoute une info, parfois le pointeur de la souris n'est pas précis, 
faut que je clique un peu plus loins que le bouton pour que cela marche, 
parfois et lors d'autres démarrage et allumage il fonctionne bien.

Je suis près a restaurer dom0 ou la totalité du système si je dois en arriver 
là, j'ai chercher a le faire, mais je n'ai pas de backup.


Je vous remercie j'espère ne pas vous  déranger avec mon mail.

---
Hello Mr. Pierret,

  I have been a QubesOs user for a few months,

  Recently for almost 20 days now I have had a problem with its use, knowing 
that I only use this bone on my machine, it causes me a problem.

  I am speaking to you because I do not know who to address and where I should 
go.

  I saw that there was Freenode IRC platform to be able to communicate with 
other users, I did not know how to register my nickname on it, there is also I 
think discord, and github there where I found your  mail address.

  The problem I encountered with my bone:

  Xen_version: 4.8.5-23.fc25

  Linux 4.19.147-1.pvops.qubes.x86_64

  Qubes os release 4.0 (R4.0)


  Is quite simply that I lost my window bar where there is the cross to close 
and the 3 icons (reduce, enlarge, close) of all the windows, I would have 
believed in a bad handling on my part, or  that the resolution of one of my 2 
screens was messing up, but I noticed another problem the shortcut to switch 
between windows, (Alt + Tab) does not work.

  So I can only use one window and then close it to do something else.

  Here I add an info, sometimes the mouse pointer is not precise, I have to 
click a little further than the button for it to work, sometimes and during 
other startup and ignition it works well.

  I am ready to restore dom0 or the whole system if I have to get there, I 
tried to do it, but I don't have a backup.


  Thank you I hope you do not disturb you with my mail.

Salutation




Hello,
I'll answer in English and not in French because I'm transferring your issue to the user mailing 
list where the community could help you. You can find more information about how to have support: 
https://www.qubes-os.org/support/. More recently it's not a "discord" but a 
"discourse" forum https://qubes-os.discourse.group/ where you can post your request too.

Looking briefly to your issue, it seems that your dom0 (XFCE?) window manager might has 
its config broken. As a first attempt, I would try to clean the XFCE configuration by 
deleting/moving the folder in your dom0 user ~/.conf/xfce4. I would also ensure having 
latest updates: "[XXX@dom0 ~]$ sudo qubes-dom0-update"

Best regards,
Frédéric

--
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/0f1d1079-da5e-237e-7c0a-43b0539d6e7c%40qubes-os.org.


OpenPGP_0x484010B5CDC576E2.asc
Description: application/pgp-keys


OpenPGP_signature
Description: OpenPGP digital signature

[qubes-users] Re: Thunderbird 78.2.1

[Frédéric Pierret]

Le 2020-09-10 à 09:09, Frédéric Pierret a écrit :
> Hi,
> Just a little update to let you know that I've built Thunderbird 78.2.1 for 
> Fedora 31 and 32 (33 soon I need to debug a failing build): 
> https://copr.fedorainfracloud.org/coprs/fepitre/thunderbird-78/build/1654837/
> 
> If someone wants to try it (**don't upgrade your template** or do it at your 
> own risk):
> 
> $ sudo dnf copr enable -y fepitre/thunderbird-78
> $ sudo dnf update thunderbird
> 
> As we are currently implementing tests 
> (https://github.com/fepitre/qubes-app-linux-split-gpg/tree/tb78) for 
> Thunderbird 78 and their PGP implementation, until Fedora and other distros 
> have upgraded their version, we plan to use my COPR repo for validating the 
> Qubes Slit GPG mechanism.
> 
> Best regards,
> Frédéric
> 

Hi,

Following my previous email, Fedora is now building and testing Thunderbird 
78.3.1 for rawhide (https://src.fedoraproject.org/rpms/thunderbird). They will 
certainly upgrade current stable versions soon. We have made a specific 
documentation for Thunderbird 78 and higher for configuring Split GPG without 
Enigmail. Please have a look here: 
https://www.qubes-os.org/doc/split-gpg/#thunderbird-78-and-higher. You can 
already try to configure and test yourself by using builds I've made for Fedora 
31 and 32 on my COPR repository.

Best regards,
Frédéric

-- 
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/de72f17f-a589-5632-6bed-460566d4bf0b%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Re: [TemplateVM error] could not resolve host: github.com #2

[Frédéric Pierret]

On 2020-09-25 14:58, lik...@gmx.de wrote:
> On 2020-09-25 06:19, setemeraude-VwIFZPTo/vqstnjn9+b...@public.gmane.org 
> wrote:
>>
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA512
>>
>> Hello there,
>>
>> I was following the instructions listed here
>> (https://www.qubes-os.org/doc/pentesting/kali/#katoolin4_0) to create a
>> kali template vm and ran into the following error for Qubes 4.0
>>
> 
> I recently came across this blog which uses salt to setup a kali machine. I 
> haven't tried this, but you might find it useful:
> https://alan-mushi.github.io/asap/2020/01/18/qubes-os-salt-kali-template.html
> 

We do have already Kali template. Only issue with missing DNF in bullseye 
prevent to build a full kali build. See notably 
https://github.com/QubesOS/qubes-issues/issues/6030#issuecomment-698667814 or 
other issues related to kali and bullseye.

-- 
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/75c95443-504d-9989-30f2-2782ee36da7e%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Install Google Chrome in Fedora 32 Template

[Frédéric Pierret]

Hi,

On 2020-09-09 09:51, 799 wrote:
> Hello Frederic,
> 
> I found a much easier approach by enabling network connectivity during 
> template customization and using Google's package repository.
> This is fine for me, because my multimedia-AppVM will be declared as 
> untrusted and is only used for specific "rich-media-tasks".

At which step do you need to set netvm to your template?
 
Depending on requirements, maybe that can be adapted.

Best regards,
Frédéric

-- 
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/13dee2ce-25f8-6daa-eabb-5f3bd5bd7ccb%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Install Google Chrome in Fedora 32 Template

[Frédéric Pierret]

On 2020-09-04 16:33, 799 wrote:
> Hello,
> 
> I am trying to setup a multimedia AppVM based on a fedora-32-minimal template 
> and want to install Chrome in the template VM.
> Unfortunately I am unable to resolve dependencies to install the 
> chrome.rpm-package.
> I need to install libappindicator3.so.1()(64bit) and I am unable to find a 
> way to install it from the default repo's.
> https://rpmfind.net/linux/rpm2html/search.php?query=libappindicator3&submit=Search+...&system=&arch=
> 
> Any ideas how to do so?


$ dnf search libappindicator

Copr repo for fedy owned by kwizart 



   6.0 
kB/s | 4.3 kB 00:00
Copr repo for PyCharm owned by phracek  



82 
kB/s |  71 kB 00:00
Fedora 32 openh264 (From Cisco) - x86_64



   3.1 
kB/s | 5.1 kB 00:01
Fedora Modular 32 - x86_64  



   1.2 
MB/s | 4.9 MB 00:04
Fedora Modular 32 - x86_64 - Updates



   2.0 
MB/s | 3.7 MB 00:01
Fedora 32 - x86_64 - Updates



   4.7 
MB/s |  22 MB 00:04
Fedora 32 - x86_64  



12 
MB/s |  70 MB 00:05
Qubes OS Repository for VM (updates)



   135 
kB/s | 108 kB 00:00
==
 Name Exactly Matched: libappindicator 
==
libappindicator.i686 : Application indicators library
libappindicator.x86_64 : Application indicators library
=
 Name & Summary Matched: libappindicator 
=
libappindicator-deve

Re: [qubes-users] Witch one is the best?

[Frédéric Pierret]

On 2020-08-25 23:51, Mélissa Ch. wrote:
> 
>> Silitech
>>
>> Intel(R) Core(TM) i5-3450 CPU @ 3.10 GHz 3.10GHz
>>
>> Mémoire 16.0 Go ram
>>
>> Système d’exploitation 64 bits
>>
>> Windows 7 Familiale Premium
>>
>> Carte graphique ADM Radeon HD 7470
> 
> This one is the better Qubes candidate because of the AMD video card and
> 16GB RAM. Be aware Qubes can sometimes be more challenging to install
> than Windows, so might need troubleshooting.
> 
> 
> Thank you! 
> 
> And another question. 
> How to veryfie the key. I mean, i have donwload the file and verify the key 
> on the web. But i can't fint on my systeme/machine  the GPG2 program to do 
> the rest of the vérifycation like on the Qube page said?  On this one tha i 
> use now i have Windows 10 and on the othr one not on the web for now. The 
> silitech is Windows 7. 


If you want to verify Qubes key on Windows I guess you can use one of the 
binary provided by GnuPG: https://gnupg.org/download/. I would dig through 
this. Another solution is to boot on a livecd on your current machine and use 
the gpg program provided. A Fedora livecd can do the work.

Best regards,
Frédéric

PS : BEGIN FRENCH Si vous avez des difficultés pour bien comprendre certaines 
parties ou démarches à faire, n'hésitez pas à me demander en français. Je 
ferais de mon mieux pour transcrire les infos demandées après en anglais pour 
tout le monde. END FRENCH

 
> Thank a lot ! 
> Le dimanche 23 août 2020 à 11 h 21 min 36 s UTC-4, awokd a écrit :
> 
> Mélissa Ch.:
> 
> > Silitech
> >
> > Intel(R) Core(TM) i5-3450 CPU @ 3.10 GHz 3.10GHz
> >
> > Mémoire 16.0 Go ram
> >
> > Système d’exploitation 64 bits
> >
> > Windows 7 Familiale Premium
> >
> > Carte graphique ADM Radeon HD 7470
> 
> This one is the better Qubes candidate because of the AMD video card and
> 16GB RAM. Be aware Qubes can sometimes be more challenging to install
> than Windows, so might need troubleshooting.
> 
> -- 
> - don't top post
> Mailing list etiquette:
> - trim quoted reply to only relevant portions
> - when possible, copy and paste text instead of screenshots
> 
> -- 
> 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/22bea83c-bc5e-491b-a2eb-cd3901380063n%40googlegroups.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/3a58e6a4-5552-e624-815b-946dac69eb13%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

[qubes-users] qubes-split-ssh

[Frédéric Pierret]

Hi,

I would love to see qubes-split-ssh in our contrib repository but I've not 
identified the most recent fork/maintainer which would be used for putting it 
into QubesOS-contrib.

Does anyone here would be interested to propose it as 'Package contribution'? 
For guidelines, see https://www.qubes-os.org/doc/package-contributions.

Thank you for any help in this subject.

Best regards,
Frédéric

-- 
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/fbdad9ae-c238-28af-9751-21d934ee5e75%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Persistence: /usr/local/

[Frédéric Pierret]

Hi,

On 2020-08-04 11:32, Michael Lott wrote:
> Hi everyone
> 
> I've compiled the source for Wireshark-3.2.5 (as the Debian packages are 
> still on 2.6.x). By default this drops the compiled binaries into 
> /usr/local/bin/.

I would assume that you could manage to change default path to /usr/bin. 
Certainly in the configure or such.

> I've then shut down the TemplateVM and created a new AppVM (based on this 
> TemplateVM) called /my-new-qube/, as a test. However, when I start it up, the 
> wireshark binary is not available. In fact, when I list out the contents of 
> /usr/local/bin/ on /my-new-qube,/ there is nothing at all there.
> 
> From my understanding of the docs, /usr/local/ is persistent and should be 
> made available to any AppVMs that are based on the TemplateVM.

Yes.

> If that is indeed correct, I've hit a bit of a brick wall on this one, so any 
> help would be greatly appreciated.
> 
> Thanks heaps,
> Mike

Frédéric

-- 
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/5cef799c-aae7-17e8-0155-fde9fa0474f2%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Re: qubes template centos-8? 693M Updates

[Frédéric Pierret]

On 2020-07-27 16:27, ludwig...@gmail.com wrote:
> 
> Hi all,
> regarding templates. Is it possible to have rolling updates with the 
> templates, so all the users downloading templates
> dont need to update them.
> So once a week an update for the templetes would be nice. I am sure this can 
> be automated.
> 
> Installing the updates at the source of the templates scales better compared 
> to everyone installing updates.
> 

That's mostly a problem of limited ressources of infrastructure we have which 
are already heavily loaded.

Regards,

-- 
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/4306c97d-093a-c942-3585-6a548f3bed68%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] qubes template centos-8?

[Frédéric Pierret]

On 2020-07-27 15:08, ludwig...@gmail.com wrote:
> 
> Hi all, I tried to download a centos8-template, but it seems to be 
> unavailable.
> 
> xxx@dom0 ~]$ sudo qubes-dom0-update --enablerepo=qubes-templates-community 
> qubes-template-centos-8
> Using xxx-vm as UpdateVM to download updates for Dom0; this may take some 
> time...
> Fedora 25 - x86_64 - Updates    2.3 MB/s |  24 MB 00:10   
> Fedora 25 - x86_64  2.4 MB/s |  50 MB 00:21   
> Qubes Dom0 Repository (updates) 2.1 MB/s |  19 MB 00:09   
> determining the fastest mirror (15 hosts).. done.--  B/s |   0  B --:-- 
> ETA
> Qubes Templates repository  4.1 kB/s |  17 kB 00:03   
> Qubes Community Templates repository 13 kB/s | 5.7 kB 00:00   
> Last metadata expiration check: 0:00:01 ago on Mon Jul 27 13:04:40 2020.
> No match for argument: qubes-template-centos-8
> Error: Unable to find a match: qubes-template-centos-8
> [xxx@dom0 ~]$
> Any thoughts?

sudo qubes-dom0-update --enablerepo=qubes-templates-community-testing 
qubes-template-centos-8

-- 
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/67433971-73c5-5683-2cb3-a9aaf0a3659a%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Qubes Won't Boot with 4.19.125-1 Kernel, neither on ...128

[Frédéric Pierret]

On 2020-07-26 12:50, qubes via qubes-users wrote:
> On 6/27/20 6:55 AM, qubes via qubes-users wrote:
>> On 6/26/20 10:14 PM, Qubes wrote:
>>> On 6/26/20 9:49 PM, qubes via qubes-users wrote:
 On 6/13/20 5:36 PM, pudding wrote:
> I updated dom0 from the security-testing repo today due to the new CPU
> hardware bug. After finishing update and rebooting my laptop, it is
> stuck on the black screen forever, and will not load the LUKS decryption
> screen.
> ..

 Same problem on Lenovo t460 but "standard" repo/update.



>>> That is a real problem. I guess it is game over without a backup.
>>>
>>
>> As pudding said, you can boot the old kernel, thank spaghettimonster.
>> But what is the real cause of the problem?
>> Can I do something about it or will the next Dom0-Update fix this
>> problem? Shall I reinstall the .125-Kernel?
>> Or - worst case scenario - will newer kernels stop working on this
>> laptop in the future anyway?
> 
> 
> The newest kernel (128) won't boot neither :-(
> So I am still using 4.19.107.
> But on next update I will be out. (unless I can "preserve" the old kernel)
> 

In dom0, edit /etc/dnf/dnf.conf and change install_limit=3 to higher number to 
keep more kernel versions installed. Have you tried also kernel-latest? It's 
5.7.X version.

You say that you have black screen since kernel 4.19.125?

Best,
Frédéric

-- 
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/d27aaec4-680e-b032-0434-392750cb8c76%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Stuck in kernel panic, cannot rescue my system with anaconda

[Frédéric Pierret]

On 2020-07-22 20:23, 'Chempes Amt' via qubes-users wrote:
> Thank you so much for the answer and the suggestion, Donoban.
> I booted on a live version of Fedora and I was able to mount my QubesOs SSD, 
> which is really good. My problem now is that there is no more folders nor 
> files in /boot/efi. I think that I need to regenerate the entire efi 
> directory and I don't know how to do. Could you or someone else explain me 
> how to do that ?
> Here are files and directories of my /boot :
> 
> */boot*
> config-4.19.107-1.pvops.qubes.x86_64
> config-4.19.125-1.pvops.qubes.x86_64
> config-4.19.128-1.pvops.qubes.x86_64
> efi
> grub
> grub2
> initramfs-4.19.107-1.pvops.qubes.x86_64.img
> initramfs-4.19.125-1.pvops.qubes.x86_64.img
> initramfs-4.19.128-1.pvops.qubes.x86_64.img
> symvers-4.19.107-1.pvops.qubes.x86_64.gz
> symvers-4.19.125-1.pvops.qubes.x86_64.gz
> symvers-4.19.128-1.pvops.qubes.x86_64.gz
> System.map-4.19.107-1.pvops.qubes.x86_64
> System.map-4.19.125-1.pvops.qubes.x86_64
> System.map-4.19.128-1.pvops.qubes.x86_64
> vmlinuz-4.19.107-1.pvops.qubes.x86_64
> vmlinuz-4.19.125-1.pvops.qubes.x86_64
> vmlinuz-4.19.128-1.pvops.qubes.x86_64
> xen-4.8.5-19.fc25.config
> xen-4.8.5-19.fc25.gz
> xen-4.8.gz
> 
> Thank you in advance and have a nice evening everybody !
> **
> 
> 
>> 
>> From: donoban 
>> Sent: Tue Jul 21 23:46:29 CEST 2020
>> To: 
>> Subject: Re: [qubes-users] Stuck in kernel panic, cannot rescue my system 
>> with anaconda
>>
>>
>> On 2020-07-21 21:26, 'Chempes Amt' via qubes-users wrote:
>> > Hi everybody,
>> >
>> > [I'm sorry if I make some mistakes while writing in English but it isn't 
>> > my mother tongue. I'll try to explain my problem as easy as I can.]
>> >
>> > My QubesOS is installed on an external SSD storage (I know it's not ideal 
>> > but . In order to make my computer recognize Qubes, I have to copy 
>> > manually the xen.cfg and the xen.efi files at every kernel update (as here 
>> > : 
>> > https://www.qubes-os.org/doc/uefi-troubleshooting/#boot-device-not-recognized-after-installing
>> >  ).
>> >
>> > The problem is that at last update I forgot to change the xen.efi file 
>> > version and that now I'm stuck with a kernel panic every time I try to 
>> > boot on my QubesOS.
>> >
>> > I tried to rescue my OS with anaconda but I'm encountering two problems :
>> >
>> > - whenever I choose my external storage for booting, there is no grub menu 
>> > and Qubes boots automatically. So I cannot access any troubleshooting or 
>> > rescue shell.
>> >
>> > - I downloaded an iso image of Qubes in order to rescue my system but it 
>> > seems that anaconda --rescue can't recognize any linux partitions because 
>> > of this : https://github.com/QubesOS/qubes-issues/issues/5609
>> >
>> > - I tried by downloading an iso of Fedora 32 (server version) but anaconda 
>> > couldn't recognize my QubesOS partitions.
>> >
>> > Would anyone have any suggestions which could allow me to rescue my 
>> > system, please ?
>> >
>> > Thank you !
>> >
>>
>> I will avoid anaconda and just try with some live distro (fedora [1] or
>> ubuntu e.g.). You should mount EFI and Qubes partitions if needed with
>> default file manager without problems.
>>
>> https://fedoraproject.org/wiki/FedoraLiveCD
>>
>> --
>> 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/89d6b81a-c890-e775-9edd-b22e2d64cf8a%40riseup.net.
> 
> 
> -- 
> Sent with https://mailfence.com
> Secure and private email

Hi,
The convention here is not to top-post. Please scroll to the bottom of the 
message before you start typing. Or reply inline.

If you used default Qubes partitioning, you should have another partition 
containing what's in /boot/efi with xen.efi and conf.

Frédéric


-- 
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/1bc4e00b-a684-4bce-c173-76c4fbe128cf%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

[qubes-users] Re: Fw: qubes arch template

[Frédéric Pierret]

On 2020-07-16 16:51, fargubz wrote:
> Hi Frederic,
> 
> Having the https://github.com/QubesOS/qubes-issues/issues/5503 issue.

Hi, please don't ask directly to any member of the Qubes OS project (including 
me :)). Ask to the list directly for which I CC it.
 
> What is the step to fix this?

I'm pretty sure any person who built Archlinux could help you (which is not my 
case).

> Best regards!
> 
> fargubz
> 

Regards,

-- 
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/f237dd68-db2c-aa63-5954-218ca5dca4b8%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

[qubes-users] Re: need help or support

[Frédéric Pierret]

Hi

On 2020-07-07 11:50, david russo wrote:
> Hi
> 
> My names is david i’m french and I try to found a solution to cure one main 
> issue regarding the connection or intranet between SYS-NET and dom0.
> 
> (see the attached file)
> 
> The main issu is when I want to use internet acces as Firefox comboned with 
> TOR, I checked my IP on the websit « monip » and Nothing change, tor doesn’t 
> support the hide IP.
> 
> I suppose many small issue.
> 
> As required on the websit of QUBES the update was performed to be sure we get 
> a fresh installation with last package.
> 
> Could you ask around you how I can cure this issue maybe it is not an issue, 
> i just discovered QUBES and most of the youtuber don’t give the trouble 
> shooting for this event.
> 
> Thank you
> 
> Best regards
> 

There is a list for such request: qubes-users@googlegroups.com. More 
information at https://www.qubes-os.org/support/.

Here I transferred your original mail to it.

Best regards,
Frédéric

-- 
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/b25e61ae-2cd2-3ea0-607e-4bae5610c7f3%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

[qubes-users] kernel-5.7.6: nouveau issue on RTX2080 TI

[Frédéric Pierret]

Hi,
I'm having an issue on kernel-latest where a commit 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.7.6&id=bfe0bc40e53ac3198b6696282f83665757f26f67
 has been introduced to "Fixes display not coming up on high-bandwidth HDMI 
displays under a number of configurations.". Well in my case it does not what 
it's said. I'm having a nice black screen. I just build the same kernel with 
commit reverted and it works.

Any one has encountered this issue with NVIDIA card?

I'll try to investigate the problem and fix it. Probably related to Xen (again 
for those cards RTX).

Best,
Frédéric

-- 
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/c0d4b59b-23a0-6da8-759d-a92172e86ac0%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] safely remove yum from debian tempate?

[Frédéric Pierret]

On 2020-06-28 23:23, Dave C wrote:
> I'd like to 
> 
> |
> sudo apt remove yum
> |
> 
> because the yum files in /etc/bash_completion.d/ break things for fossil 
> (autocomplete appends a space instead of slash after directories when running 
> fossil).
> 
> However, apt warns the following:
> 
> |
> The following packages will be REMOVED:
>   qubes-core-agent-dom0-updates qubes-vm-recommended yum yum-utils
> 
> |
> 
> A) Is it safe to remove qubes-core-agent-dom0-updates and 
> qubes-vm-recommended from a debian template?
> 
> Also, apt tells me that autoremove would further remove quite a few packages, 
> including several from qubes:
> 
> |
>   qubes-core-agent-passwordless-root qubes-gpg-split
>   qubes-img-converter qubes-input-proxy-sender qubes-mgmt-salt-vm-connector
>   qubes-pdf-converter qubes-thunderbird qubes-usb-proxy
> |

When building normal template, we add a meta-package called 
qubes-vm-recommended which is responsible to pull above dependencies and 
notably qubes-core-agent-dom0-updates, which itself requires yum and yum-util. 
You can safely remove it if you don't use debian template as "UpdateVM" in 
Qubes global preferences.


> B) Is it safe to allow these to be autoremoved?
> 
> I'm guessing that it is ok to remove the former (A: yes) and not ok to remove 
> the latter (B: no).
> 
> I've noticed that installing qubes-vm-recommended brings yum and yum-utils 
> along with it.  This leaves me wondering, is there a way to uninstall yum on 
> a debian template?
> 
> Thanks for any help.
> 
> -- 
> 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/550e6bc7-8319-4587-83a2-94ea3b7432eao%40googlegroups.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/f0274833-f2b9-1a0f-95b5-9aa995ac2cdb%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Multiple X sessions in Dom0?

[Frédéric Pierret]

On 2020-05-31 16:52, brendan.h...@gmail.com wrote:
> On Friday, May 29, 2020 at 6:15:31 AM UTC-4, donoban wrote:
> 
> On 2020-05-29 02:34, brend...@gmail.com wrote:
> > Can Qubes support multiple X sessions in dom0?
> Or do you mean multiple X sessions with the same user?
> 
>  
> Yes, exactly.
> 
> On Friday, May 29, 2020 at 6:23:19 AM UTC-4, Frédéric Pierret wrote:
> 
> On 2020-05-29 02:34, brend...@gmail.com wrote:
> > Can Qubes support multiple X sessions in dom0?
> I guess you want to see VMs in separate X sessions. Without speaking of 
> user management, yes it can but currently gui-daemon is running on DISPLAY=:0 
> waiting for all VM start/shutdown and starting a proper server for them. In 
> your case of having multiple DISPLAY, that would mean to adapt the automatic 
> start of each deamon per VM.
> 
> I would say, wait or try the (undocumented) GuiVM implementation in R4.1, 
> that would ease such use-case/management..
> 
>  
> That sounds reasonable. As it is, without further adjustment, I cannot get a 
> second X server to start up correctly under 4.0.
> 
> I'm using window manager workspaces now to mentally separate out different 
> work-streams across a dozen running VMs sometimes.
> 
> However, it might be nicer to have a stronger organizational (and mental) 
> partition and multiple X servers with the UI of running VMs associated with 
> different X servers would be nice.
> 
> Perhaps multiple GUIVMs could serve that purpose?

Yes it's the idea.

The last remaining organizational thing would be how to display those multiple 
desktops/GuiVMs. That could still be separate DISPLAY or separate workspaces 
(shortcuts management difficulties probably).

Currently we have dom0 the "root" display, showing one fullscreen GuiVM (due to 
emulated GPU pass-through). But, I don't see any obstacle at dom0 boot, to 
start multiple Xsessions where you run manually gui-daemon associated to 
specific GuiVM. In the future, this setup would be initialized into the GuiVM 
itself with GPU passthrough.

If you run into this work, I could help you for support.

Best,
Frédéric

-- 
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/bd752014-29d3-b555-cca9-189e6990fcd3%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Another newbie question related to TemplateVMs

[Frédéric Pierret]

On 2020-05-30 11:30, viktor.ransm...@gmail.com wrote:
> Hello Frederic,
> 
> Am Freitag, 29. Mai 2020 19:00:55 UTC+2 schrieb Frédéric Pierret:
> 
> On 2020-05-29 18:26, viktor@gmail.com  wrote:
> > Am Freitag, 29. Mai 2020 14:01:46 UTC+2 schrieb Frédéric Pierret:
> >
> >     On 2020-05-29 13:53, viktor@gmail.com  wrote:
> >     >
> >     > I'm trying to continue my journey into the various Qubes OS 
> options from the smaller - and not - from the larger template POV.
> >     >
> >     > I'm not asking for any additions to the provided packages 
> available for example in 'fedora-31-minimal'.
> >     >
> >     > All I'm asking for is help to resolve the following question:
> >     >
> >     > *What do I need to do in order to activate / enable the copy / 
> paste pattern via copy-c/v for xterm?
> >     > *
> >
> >     Control+Middle mouse clic -> Select to Clipboard. Then, you can you 
> QubesOS clipboard shortcut (Control+Shift+C).
> >
> >
> > It may be obvious to you, but for me - coming from the Windows world - 
> it is not really clear ...
> 
> The middle click simply the wheel click but indeed, with only left and 
> right buttons it's both at the same time. Here when hold Control in addition 
> to left and right mouse button (keep holding) on xterm, it makes appearing a 
> little menu where the selection is made by unholding mouse buttons. On this 
> little menu you would see the 'Select to Clipboard' option.
> 
> 
> Which version of Qubes OS - and - of Fedora are you using?

QubesOS version does not matter (4.0) and it's Fedora 31 (does not matter 
either). It's mostly a problem related to xterm interpreting mouse buttons not 
Qubes/Templates at first. The menu you have is the same I have with only left 
click button. The menu with clipboard option is called 'VT Options'. I suggest 
you to search for how to enable 'VT Options' without middle click button.

> Have you made any changes to the 'default' X environment coming with the 
> Fedora template?
> 
> The reason why I ask, is that I re-tried your suggestion in both qubes, i.e. 
> 'f31-min-test-vm' and in 'f31-test-vm'.
> 
> In 'f31-min-test-vm' a not so small menu is opening up ("Main Options") but 
> it does not contain a 'Select to Clipboard' option!
> 
> And if I try the same on 'f31-test-vm', i.e. a fresh AppVM created from the 
> default 'Fedora-31' template I get no menu at all ...
> 
> With kind regards,
> 
> VR
> 
> -- 
> 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 
> <mailto:qubes-users+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/qubes-users/2cff7abe-695d-4152-a18c-95a04234e109%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/qubes-users/2cff7abe-695d-4152-a18c-95a04234e109%40googlegroups.com?utm_medium=email&utm_source=footer>.

-- 
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/9a238bdb-6771-eec2-ba5e-45ad35dde12e%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Another newbie question related to TemplateVMs

[Frédéric Pierret]

On 2020-05-29 18:26, viktor.ransm...@gmail.com wrote:
> Hello Frederic,
> 
> Am Freitag, 29. Mai 2020 14:01:46 UTC+2 schrieb Frédéric Pierret:
> 
> On 2020-05-29 13:53, viktor@gmail.com  wrote:
> >
> > I'm trying to continue my journey into the various Qubes OS options 
> from the smaller - and not - from the larger template POV.
> >
> > I'm not asking for any additions to the provided packages available for 
> example in 'fedora-31-minimal'.
> >
> > All I'm asking for is help to resolve the following question:
> >
> > *What do I need to do in order to activate / enable the copy / paste 
> pattern via copy-c/v for xterm?
> > *
> 
> Control+Middle mouse clic -> Select to Clipboard. Then, you can you 
> QubesOS clipboard shortcut (Control+Shift+C).
> 
> 
> It may be obvious to you, but for me - coming from the Windows world - it is 
> not really clear ...

The middle click simply the wheel click but indeed, with only left and right 
buttons it's both at the same time. Here when hold Control in addition to left 
and right mouse button (keep holding) on xterm, it makes appearing a little 
menu where the selection is made by unholding mouse buttons. On this little 
menu you would see the 'Select to Clipboard' option.
 
> I searched for 'middle mouse clic' & I was told that on a regular two button 
> mouse, this maps / translates to pressing both left & right mouse at the same 
> time.
> 
> However in the xterm started from the qube 'f31-min-test-vm' this does not 
> create any result :-(
> 
> Whenever I try to perform a Control+Shift+C operation afterwards, it reports 
> ZERO bytes ...
> 
> What am I missing?
>  
> 
> 
> > I do know, that this is not a Qubes OS specific question - but - it 
> seems to be a Qubes OS/ Minimal TemplateVM related question.
> >
> > I tried several options recommended to me, when I searched the Internet 
> for "copy text from xterm [fedora]". - Unfortunately w/o success :-(
> >
> > Additional information, just for the record:
> >
> > I created a qube, which I called 'f31-min-test-vm' based on the 
> template 'fedora-31-minimal'
> >
> > I start the xterm - and - would like to retrieve the content of all all 
> installed packages, i.e. 'rpm -qa | sort', to start adding necessary packages 
> for my use-case(s) ...
> >
> > Again for information only:
> >
> > When I execute 'rpm -qa | wc - l' in an xterm, it reports only
> >
> > * 431 for 'f31-min-test-vm' - but -
> > * 1142 for 'f31-test-vm' ...
> >
> > *Any suggestions to my initial question?
> 
> What is 'f31-test-vm'? You only spoke about f31-min-test-vm.
> 
> 
> You are right, I should have mentioned 'f31-test-vm' explicitly as well.
> 
> I created this qube fresh from the 'fedora-31' template, simply to get the 
> number of packages which are installed, if I would base any cloned template 
> on it.
> 
> I just mentioned it as an argument, why *I* want to start from the smaller - 
> and not - from the larger template.
> 
> With kind regards,
> 
> VR
> 
> -- 
> 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 
> <mailto:qubes-users+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/qubes-users/07a939fe-0884-45af-81bf-7a87b3c9b26c%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/qubes-users/07a939fe-0884-45af-81bf-7a87b3c9b26c%40googlegroups.com?utm_medium=email&utm_source=footer>.

-- 
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/3a70539d-3194-ea05-37c8-ef0a1fcfa9c3%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Another newbie question related to TemplateVMs

[Frédéric Pierret]

On 2020-05-29 13:53, viktor.ransm...@gmail.com wrote:
> Hello community,
> 
> I'm trying to continue my journey into the various Qubes OS options from the 
> smaller - and not - from the larger template POV.
> 
> I'm not asking for any additions to the provided packages available for 
> example in 'fedora-31-minimal'.
> 
> All I'm asking for is help to resolve the following question:
> 
> *What do I need to do in order to activate / enable the copy / paste pattern 
> via copy-c/v for xterm?
> *

Control+Middle mouse clic -> Select to Clipboard. Then, you can you QubesOS 
clipboard shortcut (Control+Shift+C).


> I do know, that this is not a Qubes OS specific question - but - it seems to 
> be a Qubes OS/ Minimal TemplateVM related question.
> 
> I tried several options recommended to me, when I searched the Internet for 
> "copy text from xterm [fedora]". - Unfortunately w/o success :-(
> 
> Additional information, just for the record:
> 
> I created a qube, which I called 'f31-min-test-vm' based on the template 
> 'fedora-31-minimal'
> 
> I start the xterm - and - would like to retrieve the content of all all 
> installed packages, i.e. 'rpm -qa | sort', to start adding necessary packages 
> for my use-case(s) ...
> 
> Again for information only:
> 
> When I execute 'rpm -qa | wc - l' in an xterm, it reports only
> 
> * 431 for 'f31-min-test-vm' - but -
> * 1142 for 'f31-test-vm' ...
> 
> *Any suggestions to my initial question?

What is 'f31-test-vm'? You only spoke about f31-min-test-vm.

> 
> With kind regards,
> 
> VR
> 
> -- 
> 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/c9dfac76-2e5b-4d89-8675-aad2647d97e2%40googlegroups.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/a2493abd-d8aa-2d5f-0f7f-c490776b650c%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Multiple X sessions in Dom0?

[Frédéric Pierret]

On 2020-05-29 02:34, brendan.h...@gmail.com wrote:
> Can Qubes support multiple X sessions in dom0?

I guess you want to see VMs in separate X sessions. Without speaking of user 
management, yes it can but currently gui-daemon is running on DISPLAY=:0 
waiting for all VM start/shutdown and starting a proper server for them. In 
your case of having multiple DISPLAY, that would mean to adapt the automatic 
start of each deamon per VM.

I would say, wait or try the (undocumented) GuiVM implementation in R4.1, that 
would ease such use-case/management..
 
> e.g. default session on primary terminal (via ctrl-alt-f1), then start 
> another session on the third pty (ctrl-alt-f3) after logging in as the 
> primary qubes user in dom0?
> 
> B
> 

Best,
Frédéric

-- 
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/d486161a-8ba4-cc22-3fad-aeb864a71176%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] qubes-builder / failed dependency for Phython?

[Frédéric Pierret]

On 2020-05-27 19:47, Sven Semmler wrote:
> On Wed, May 27, 2020 at 12:26:28PM -0500, Sven Semmler wrote:
>> echo "pythonver:Depends=python" >> debian/qubes.pdf-converter.substvars
>> dh_gencontrol
>> dpkg-gencontrol: warning: Depends field of package qubes-pdf-converter: 
>> unknown substitution variable ${pythonver:Depends}
>> dpkg-gencontrol: warning: can't parse dependency -nautilus
>> dpkg-gencontrol: error: error occurred while parsing Depends field: 
>> poppler-utils, imagemagick, -nautilus,
>> dh_gencontrol: dpkg-gencontrol -pqubes-pdf-converter -ldebian/changelog 
>> -Tdebian/qubes-pdf-converter.substvars -Pdebian/qubes-pdf-converter 
>> -UMulti-Arch returned exit code 25
>> dh_gencontrol: Aborting due to earlier error
> 
> I think this is the actual issue: unknown substitution variable 
> ${pythonver:Depends}

Those corresponds to freshly merged PR of components and notably 
qubes-pdf-converter. The problem is that we don't have tracking build for 
Ubuntu. I suggest you to checkout previous commits but this is related to 
python3 migration so maybe you will encounter python3 issues. I'll try to fix 
that soon.

> Unfortunately I am obliviouos to all things Phython.
> 
> I have python2 and python3 installed as well as all the dependencies
> listed on the Qubes website for qubes-builder. The build worked
> perfectly yesterday and now it's broken regardless of the commit version
> I try.
> 
> When I try to undo the last update I get this:
> 
> [user@app-qubes-builder qubes-builder]$ sudo dnf history undo 135
> Last metadata expiration check: 2:12:17 ago on Wed May 27 10:29:21 2020.
> Undoing transaction 135, from Tue May 26 12:44:00 2020
> Upgrade  json-c-0.13.1-12.fc30.x86_64 @updates
> Upgraded json-c-0.13.1-11.fc30.x86_64 @@System
> No package json-c-0.13.1-11.fc30.x86_64 available.
> Error: no package matched
> 
> I guess I could restore the backup from two nights ago and just pull
> from git but not update Fedora to see if this was it.
> 
> /Sven
> 
> 

-- 
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/eea6228e-00b2-dcd5-f9c4-9fe8a253f018%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Re: Errors during downloading metadata for repository 'fedora-modular':

[Frédéric Pierret]

On 2020-05-27 17:24, Sven Semmler wrote:
> On Wed, May 27, 2020 at 07:30:29AM -0700, Dave wrote:
>> The upgrade process for Standalone Fedora-31-work-test worked up until the 
>> end when it complained about disk space.
>> If necessary, I can add disk space and rerun it, but does this prove your 
>> suspicion regarding UpgradeProxy? 
> 
> It does. It also shows us a workaround. Just like you created the
> Standalone VM by qvm-clone --class StandaloneVM you can do the same
> after a successful upgrade...
> 
>   qvm-remove fedora-31-work
>   qvm-clone --class TemplateVM fedora-31-work-test fedora-31-work
>   qvm-remove fedora-31-work-test
> 
>> What about Frédéric's comment to "disable modular"? Wouldn't it be written 
>> into the command script:
>> *dnf --releasever= distro-sync --best* --allowerasing
>> * terminal transcript attached
> 
> I have no idea, but he is one of the core developers and from his
> comment I gather this is a rather routine issue. 
> 
> I imagine something like 'dnf config-manager --set-disabled
> fedora-modular' should do it? 

CLI way: simply set 'enabled=0' in /etc/yum.repos.d/fedora-modular.repo 
(TemplateVM :) )

>> Keeping you busy, huh? Always good to learn something. Thanks a heap for 
>> taking this on.
> 
> I am actually figuring this out together with you. It's a learning thing
> for me too. ;-)
> 
> /Sven
> 
> 

Best,
Frédéric

-- 
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/c601b194-20b7-fb7b-0cc9-9f4db8644697%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Errors during downloading metadata for repository 'fedora-modular':

[Frédéric Pierret]

On 2020-05-26 00:03, Dave wrote:
> platform: Qubes 4.0.3 / Intel 64
> 
> attempting to upgrade cloned Fedora-30 templates with user applications to 
> Fedora-31
> in accordance with instructions at 
> https://www.qubes-os.org/doc/template/fedora/upgrade/
> completed steps 1, 2, & 3 - shutdown, cloning from DOM0
> step 3 - "sudo dnf clean all" completed from new Fedora-31 template
> then:
> 
> [user@fedora-31-work ~]$ sudo dnf --releasever=fedora-31 distro-sync 
> --best --allowerasing
> Fedora Modular fedora-31 - x86_64   4.4 kB/s |  63 kB 
> 00:14   
> Errors during downloading metadata for repository 'fedora-modular':
>   - Status code: 404 for 
> https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-fedora-31&arch=x86_64
>  (IP: 127.0.0.1)
> Error: Failed to download metadata for repo 'fedora-modular': Cannot 
> prepare internal mirrorlist: Status code: 404 for 
> https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-fedora-31&arch=x86_64
>  (IP: 127.0.0.1)
> 
> 
> I couldn't reach the mirrors address in a browser either.
> Do the mirror addresses in the Qubes repository need updating?
> 
> TIA - David
> 
> -- 
> 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/c617677a-28b8-4ab1-ba22-e9b9b193cad4%40googlegroups.com
>  
> .

Unless you have specific needs for modular itself, we disable them by default 
in builds because we don't need them. So if you don't, simply disable them. 
Unfortunately, this is a recurrent problem with modular repos which are subject 
to very unstable behavior.

Best,
Frédéric

-- 
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/e877f64d-463e-2204-4f59-2a2517377bd0%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] How to check (in BASH and dom0) whether a appVM exists?

[Frédéric Pierret]

There is a tool for checking state of VMs:

[userdom0 ~]$ qvm-check toto
usage: qvm-check [--verbose] [--quiet] [--help] [--all] [--exclude EXCLUDE]
 [--running] [--paused] [--template] [--networked]
 [VMNAME [VMNAME ...]]
qvm-check: error: no such domain: 'toto'
[user@dom0 ~]$ echo $?
2
[user@dom0 ~]$ qvm-check sys-net
qvm-check: sys-net: exists
[user@dom0 ~]$ echo $?
0

Best,
Frédéric

On 2020-05-19 10:35, Christophe wrote:
> qvm-ls|grep yourvmname
> 
> On 20/05/19 10:32AM, Johannes Graumann wrote:
>> Hello,
>>
>> See subject line ;)
>>
>> Sincerely, Joh
>>
>> -- 
>> 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/74dcf0a303aa9afb95809626034f7e1e%40graumannschaft.org.
> 

-- 
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/c1b734ea-4acd-ae2a-5986-419695b538a4%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] AMD RX 5700 XT suddenly stopped working with Qubes

[Frédéric Pierret]

On 2020-05-17 19:36, Jarrah wrote:
> Good Morning,
> 
> About a month ago, kernel-latest 5.6.4 was released which resolved the
> issues booting Qubes on the RX 5700 XT. This has been working and stable
> since this time.
> 
> Yesterday I installed a number of updates (including Xen and
> kernel-latest) and (after the updates had completed) had an issue which
> reset my bios. Since then, I have been unable to boot Qubes using the
> 5700 XT. System works fine in another OS.
> 
> 
> The only error output I have seen is as follows (observed on different
> boots):
> 
> "[Firmware Bug]: cpu 2, try to use APIC520 (LVT offset 2) for vector
> 0xF4, but the register is already in use for vector 0x0 on this cpu."
> 
> A failure to start IOMMUv2 (does not occur with the other graphics card)
> 
> 
> After fixing the bios settings, my next thought was to roll back the Xen
> and kernel update. However, this did not solve the issue.
> 
> Other attempts:
> 
> * Boot the system with another GPU: Works fine
> 
> * Boot the system without Xen (just the dom0 kernel): works fine.
> 
> * Boot the system outputing to the hypervisor console: system boots to
> login screen. All autostarted VMs boot. Keyboard entry does not get sent
> to dom0, but ctl-alt-del reboots the system and outputs to screen.
> 
> * Boot the system and let it sit after the screen locks up: All
> autostarted VMs boot but I cannot interact with the system. I can tell
> by the hvc above and the fact that my mouse turns on.
> 
> * The error above has been connected to an ACPI issue. Adding the
> "acpi=off" boot parameter resulted in a kernel panic probably unrelated
> to the GPU issue.
> 
> * Tested the just-released 5.6.13 kernel: Same issue now found on 5.6.4
> (previously good) through 5.6.13.
> 
> * Set every IOMMU/ACS/SVM setting I can find in my bios.
> 
> 
> I'm stuck for ideas at this point. Has anyone experienced something similar?

At this point, I would rather suggest you to check in changelog of kernel
if there would be related commits but still, post a BZ issue on kernel.

> Thanks.
> 

Frédéric

-- 
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/d279318d-74ba-b83f-c78c-f1f99450195a%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Using Zoom in Qubes

[Frédéric Pierret]

On 2020-05-09 20:48, malalasilva via qubes-users wrote:
> Hi!
> Qubes 4.'0 is a really amazing piece of software. Even though I feel 
> absolutely safe, I can still do pretty much the same as with an unprotected 
> system.
> The only thing I cannot do is screen sharing in Zoom. Screen sharing works 
> fine in MS Teams, but on Zoom the shared sceed turns white, and only the zoom 
> buttons appear. Everithing else is not shown. If I drag a window to the 
> screen, it is not shown. The system resumes its normal behaviour when I stop 
> sharing.
> Has anyone had this problem? How can I solve it?

Please have a look to https://github.com/QubesOS/qubes-issues/issues/5789. That 
could certainly help.

Best,
Frédéric

-- 
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/11296525-a533-722c-84d3-592ffc0dbd30%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Set a Qube to shutdown when its last AppVM closes.

[Frédéric Pierret]

On 2020-05-09 13:05, Logan wrote:
> Is there a way to configure Qubes so that when I close the last AppvM 
> belonging to a TemplateBasedVM/Domain it auto shuts down?

By auto shuts down you mean poweroff your computer?

I think it's pretty easy to do it by writing your own Qubes core-admin addon 
extension. I would write function catching domain shutdown and looking if it 
remains running VM else poweroff.

Here are examples of core-admin addon extension: 
https://github.com/QubesOS/qubes-core-admin-addon-whonix 
https://github.com/QubesOS-contrib/qubes-core-admin-addon-bridge-device
 
> I have been dreaming of this for some time but haven't been able to find a 
> solution.
> 
> Logan
> 

Frédéric

-- 
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/0c445039-8c32-e93d-a26c-c35d524846b1%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Re: Docker and Fedora 31

[Frédéric Pierret]

On 2020-05-06 20:20, Rune Philosof wrote:
> 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/torvalds/linux/commit/76f969e8948d82e78e1bc4beb6b9465908e74873).
> Has any of you tried installing a >5.2 kernel in dom0?
> I couldn't find any newer kernels in the unstable qubes repo.

There is kernel-latest for this purpose on Qubes. Enable current-testing 
repository in dom0 you will have 5.6.X latest kernels. BTW, it's one I'm 
currently running on dom0.

Best,
Frédéric

-- 
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/154067f6-5f4a-5782-abfb-3fbda5fa8fd2%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Pulseaudio update error - fedora-31

[Frédéric Pierret]

On 2020-04-22 23:29, Frédéric Pierret wrote:
> Hi,
> From a brief look, it's due to newer Fedora pulseaudio and our Qubes package 
> requires older one. I'll try to fix that soon.
> 
> Best,
> Frédéric
> 
> On 2020-04-22 21:54, 'Max Andersen' via qubes-users wrote:
>> Hi everyone,

I spoke too fast. Here in my template I'm having pulseaudio-qubes-4.0.29-1 but 
you seem not. Have tried to:

1) dnf clean all
2) dnf update ?

>>  Problem 1: package pulseaudio-qubes-4.0.27-1.fc31.x86_64 requires 
>> pulseaudio = 13.0, but none of the providers can be installed
>>   - cannot install both pulseaudio-13.99.1-3.fc31.x86_64 and 
>> pulseaudio-13.0-1.fc31.x86_64
>>   - cannot install both pulseaudio-13.0-1.fc31.x86_64 and 
>> pulseaudio-13.99.1-3.fc31.x86_64
>>   - cannot install the best update candidate for package 
>> pulseaudio-qubes-4.0.27-1.fc31.x86_64
>>   - cannot install the best update candidate for package 
>> pulseaudio-13.0-1.fc31.x86_64
>>  Problem 2: package qubes-vm-recommended-4.0.6-1.fc31.noarch requires 
>> pulseaudio-qubes, but none of the providers can be installed
>>   - package pulseaudio-qubes-4.0.27-1.fc31.x86_64 requires pulseaudio = 
>> 13.0, but none of the providers can be installed
>>   - package pulseaudio-13.0-1.fc31.x86_64 requires 
>> libpulsecommon-13.0.so()(64bit), but none of the providers can be installed
>>   - package pulseaudio-13.0-1.fc31.x86_64 requires pulseaudio-libs(x86-64) = 
>> 13.0-1.fc31, but none of the providers can be installed
>>   - cannot install both pulseaudio-libs-13.99.1-3.fc31.x86_64 and 
>> pulseaudio-libs-13.0-1.fc31.x86_64
>>   - cannot install both pulseaudio-libs-13.0-1.fc31.x86_64 and 
>> pulseaudio-libs-13.99.1-3.fc31.x86_64
>>   - cannot install the best update candidate for package 
>> qubes-vm-recommended-4.0.6-1.fc31.noarch
>>   - cannot install the best update candidate for package 
>> pulseaudio-libs-13.0-1.fc31.x86_64
>>   - nothing provides pulseaudio = 12.99.2 needed by 
>> pulseaudio-qubes-4.0.26-1.fc31.x86_64
>>  Problem 3: problem with installed package 
>> pulseaudio-qubes-4.0.27-1.fc31.x86_64
>>   - package pulseaudio-qubes-4.0.27-1.fc31.x86_64 requires pulseaudio = 
>> 13.0, but none of the providers can be installed
>>   - cannot install both pulseaudio-13.99.1-3.fc31.x86_64 and 
>> pulseaudio-13.0-1.fc31.x86_64
>>   - cannot install both pulseaudio-13.0-1.fc31.x86_64 and 
>> pulseaudio-13.99.1-3.fc31.x86_64
>>   - package pulseaudio-module-bluetooth-13.99.1-3.fc31.x86_64 requires 
>> libpulsecore-13.99.so()(64bit), but none of the providers can be installed
>>   - package pulseaudio-module-bluetooth-13.99.1-3.fc31.x86_64 requires 
>> pulseaudio(x86-64) = 13.99.1-3.fc31, but none of the providers can be 
>> installed
>>   - cannot install the best update candidate for package 
>> pulseaudio-module-bluetooth-13.0-1.fc31.x86_64
>>  Problem 4: problem with installed package 
>> qubes-vm-recommended-4.0.6-1.fc31.noarch
>>   - package qubes-vm-recommended-4.0.6-1.fc31.noarch requires 
>> pulseaudio-qubes, but none of the providers can be installed
>>   - package pulseaudio-qubes-4.0.27-1.fc31.x86_64 requires pulseaudio = 
>> 13.0, but none of the providers can be installed
>>   - cannot install both pulseaudio-13.99.1-3.fc31.x86_64 and 
>> pulseaudio-13.0-1.fc31.x86_64
>>   - cannot install both pulseaudio-13.0-1.fc31.x86_64 and 
>> pulseaudio-13.99.1-3.fc31.x86_64
>>   - package pulseaudio-module-x11-13.99.1-3.fc31.x86_64 requires 
>> libpulsecore-13.99.so()(64bit), but none of the providers can be installed
>>   - package pulseaudio-module-x11-13.99.1-3.fc31.x86_64 requires 
>> pulseaudio(x86-64) = 13.99.1-3.fc31, but none of the providers can be 
>> installed
>>   - cannot install the best update candidate for package 
>> pulseaudio-module-x11-13.0-1.fc31.x86_64
>>   - nothing provides pulseaudio = 12.99.2 needed by 
>> pulseaudio-qubes-4.0.26-1.fc31.x86_64
>> ==
>>  Package   Architecture Version  
>>    Repository   Size
>> ==
>> Skipping packages with conflicts:
>> (add '--best --allowerasing' to command line to force their upgrade):
>>  pulseaudio    x86_64   13.99.1-3.fc31   
>>    updates

Re: [qubes-users] Pulseaudio update error - fedora-31

[Frédéric Pierret]

Hi,
From a brief look, it's due to newer Fedora pulseaudio and our Qubes package 
requires older one. I'll try to fix that soon.

Best,
Frédéric

On 2020-04-22 21:54, 'Max Andersen' via qubes-users wrote:
> Hi everyone,
> 
> I remember some time ago we had issues with pulseaudio on earlier templates, 
> and I believe a reinstall of pakages fixed the issue. I can't  seem to get 
> myself out of trouble with this one on fedora-31.
> 
> When doing update I get:
> 
> user@fedora-31 ~]$ sudo dnf update
> Last metadata expiration check: 0:50:13 ago on Wed Apr 22 20:44:57 2020.
> Dependencies resolved.
> 
>  Problem 1: package pulseaudio-qubes-4.0.27-1.fc31.x86_64 requires pulseaudio 
> = 13.0, but none of the providers can be installed
>   - cannot install both pulseaudio-13.99.1-3.fc31.x86_64 and 
> pulseaudio-13.0-1.fc31.x86_64
>   - cannot install both pulseaudio-13.0-1.fc31.x86_64 and 
> pulseaudio-13.99.1-3.fc31.x86_64
>   - cannot install the best update candidate for package 
> pulseaudio-qubes-4.0.27-1.fc31.x86_64
>   - cannot install the best update candidate for package 
> pulseaudio-13.0-1.fc31.x86_64
>  Problem 2: package qubes-vm-recommended-4.0.6-1.fc31.noarch requires 
> pulseaudio-qubes, but none of the providers can be installed
>   - package pulseaudio-qubes-4.0.27-1.fc31.x86_64 requires pulseaudio = 13.0, 
> but none of the providers can be installed
>   - package pulseaudio-13.0-1.fc31.x86_64 requires 
> libpulsecommon-13.0.so()(64bit), but none of the providers can be installed
>   - package pulseaudio-13.0-1.fc31.x86_64 requires pulseaudio-libs(x86-64) = 
> 13.0-1.fc31, but none of the providers can be installed
>   - cannot install both pulseaudio-libs-13.99.1-3.fc31.x86_64 and 
> pulseaudio-libs-13.0-1.fc31.x86_64
>   - cannot install both pulseaudio-libs-13.0-1.fc31.x86_64 and 
> pulseaudio-libs-13.99.1-3.fc31.x86_64
>   - cannot install the best update candidate for package 
> qubes-vm-recommended-4.0.6-1.fc31.noarch
>   - cannot install the best update candidate for package 
> pulseaudio-libs-13.0-1.fc31.x86_64
>   - nothing provides pulseaudio = 12.99.2 needed by 
> pulseaudio-qubes-4.0.26-1.fc31.x86_64
>  Problem 3: problem with installed package 
> pulseaudio-qubes-4.0.27-1.fc31.x86_64
>   - package pulseaudio-qubes-4.0.27-1.fc31.x86_64 requires pulseaudio = 13.0, 
> but none of the providers can be installed
>   - cannot install both pulseaudio-13.99.1-3.fc31.x86_64 and 
> pulseaudio-13.0-1.fc31.x86_64
>   - cannot install both pulseaudio-13.0-1.fc31.x86_64 and 
> pulseaudio-13.99.1-3.fc31.x86_64
>   - package pulseaudio-module-bluetooth-13.99.1-3.fc31.x86_64 requires 
> libpulsecore-13.99.so()(64bit), but none of the providers can be installed
>   - package pulseaudio-module-bluetooth-13.99.1-3.fc31.x86_64 requires 
> pulseaudio(x86-64) = 13.99.1-3.fc31, but none of the providers can be 
> installed
>   - cannot install the best update candidate for package 
> pulseaudio-module-bluetooth-13.0-1.fc31.x86_64
>  Problem 4: problem with installed package 
> qubes-vm-recommended-4.0.6-1.fc31.noarch
>   - package qubes-vm-recommended-4.0.6-1.fc31.noarch requires 
> pulseaudio-qubes, but none of the providers can be installed
>   - package pulseaudio-qubes-4.0.27-1.fc31.x86_64 requires pulseaudio = 13.0, 
> but none of the providers can be installed
>   - cannot install both pulseaudio-13.99.1-3.fc31.x86_64 and 
> pulseaudio-13.0-1.fc31.x86_64
>   - cannot install both pulseaudio-13.0-1.fc31.x86_64 and 
> pulseaudio-13.99.1-3.fc31.x86_64
>   - package pulseaudio-module-x11-13.99.1-3.fc31.x86_64 requires 
> libpulsecore-13.99.so()(64bit), but none of the providers can be installed
>   - package pulseaudio-module-x11-13.99.1-3.fc31.x86_64 requires 
> pulseaudio(x86-64) = 13.99.1-3.fc31, but none of the providers can be 
> installed
>   - cannot install the best update candidate for package 
> pulseaudio-module-x11-13.0-1.fc31.x86_64
>   - nothing provides pulseaudio = 12.99.2 needed by 
> pulseaudio-qubes-4.0.26-1.fc31.x86_64
> ==
>  Package   Architecture Version   
>   Repository   Size
> ==
> Skipping packages with conflicts:
> (add '--best --allowerasing' to command line to force their upgrade):
>  pulseaudio    x86_64   13.99.1-3.fc31
>   updates 1.0 M
>  pulseaudio-libs   x86_64   13.99.1-3.fc31
>   updates 707 k
> Skipping packages with broken dependencies:
>  pulseaudio-module-bluetooth   x86_64   13.99.1-3.fc31
>   updates  79 k
>  pulseaudio-module-x11 x86_64   13.99.1-3.fc

Re: [qubes-users] Build USB install with kernel 5+

[Frédéric Pierret]

On 2020-04-16 22:55, Max Andersen wrote:
> 
> On 4/16/20 10:46 PM, Frédéric Pierret wrote:
>> Also, if you wait a little bit, it will be in official repository soon. The 
>> PR has been merged few minutes ago and the build is in progress :)
> 
> Cool, I just changed it and it got me a new error so  I guess I might have 
> been to fast, sorry :)
> 
> -> Updating sources for linux-kernel...
> --> Fetching from https://github.com/fepitre/qubes-linux-kernel kernel-5.6...
> --> Verifying tags...
> No valid signed tag found!
> make: *** [Makefile:204: linux-kernel.get-sources] Error 1
> [user@qubes-builder qubes-builder]$
> 

It's because I don't sign commit tag. Please add NO_CHECK = 1 into 
builder.conf. BTW, don't hesitate to check documentation too.

-- 
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/1c91fec8-d43e-9619-469e-92932ea752aa%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Build USB install with kernel 5+

[Frédéric Pierret]

>>
>> -> Updating sources for linux-kernel...
>> --> Fetching from https://github.com/QubesOS/qubes-linux-kernel.git 
>> kernel-5.6...
>> fatal: Remote branch kernel-5.6 not found in upstream origin
>>
> There is a typo in 3.2. It should be :
> 
>   GIT_URL_linux_kernel=...
> 
> instead of just
> 
>   URL_...
> 

Also, if you wait a little bit, it will be in official repository soon. The PR 
has been merged few minutes ago and the build is in progress :)

-- 
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/e1b9c33e-1512-6604-d158-311eaa5cfdba%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Build USB install with kernel 5+

[Frédéric Pierret]

On 2020-04-16 22:34, 'Max Andersen' via qubes-users wrote:
> 
> On 4/15/20 10:05 AM, Frédéric Pierret wrote:
>> On 2020-04-15 08:09, Max Andersen wrote:
>>>> Den 14. apr. 2020 kl. 08.02 skrev Frédéric Pierret 
>>>> :
>>>>
>>>> Hi,
>>>> I used to build newer ISO in the past for such troubles with kernel-latest 
>>>> embedded. If you are interested, I can build you an 4.0.3 with 
>>>> kernel-latest-5.6 for try?
>>> When I try, the builder script fails horribly. Can you write a stepguide? 
>>> Maybe just commands and selections on how you build it(if it is not too 
>>> much of a hassle)?
>> Sure, here are the procedure for building latest Qubes 4.0.3 ISO with 
>> already built packages (templates included) using Qubes OS official 
>> repositories:
>>
>> 1) In a working directory, e.g. `/home/user/`, clone `qubes-builder`:
>>
>> git clone https://github.com/QubesOS/qubes-builder
>>
>> 2) Download specific builder conf file for such process:
>>
>> wget 
>> https://raw.githubusercontent.com/QubesOS/qubes-release-configs/master/R4.0/qubes-os-iso-full-online.conf
>>  -O /home/user/qubes-builder/builder.conf
>>
>> 3) Enable QubesOS testing packages for the build and specify release branch 
>> for the installer:
>>
>> echo 'USE_QUBES_REPO_TESTING=1' >> /home/user/qubes-builder/builder.conf
>> echo 'BRANCH_installer_qubes_os=release4.0' >> 
>> /home/user/qubes-builder/builder.conf
>>
>> 4) Get sources:
>>
>> cd /home/user/qubes-builder/
>> make get-sources
>>
>> 5) Enable `kernel-latest` in the ISO build process:
>>
>> sed -i 's#\(> type="\)optional\(">kernel-latest.*$\)#\1mandatory\2#' 
>> qubes-src/installer-qubes-os/conf/comps-qubes.xml
>>
>> 6) Build ISO:
>>
>> make iso
>>
>> 7) Get your freshly built ISO in `/home/user/qubes-builder/iso`
>>
>> The current kernel-5.6 is still at PR stage. If you want to try it you need 
>> to build it:
>>
>> 3.1) Add `linux-kernel` in `COMPONENTS`:
>>
>> echo 'COMPONENTS+=linux-kernel'
>>
>> 3.2) Change URL and BRANCH of the git repository:
>>
>> echo 'URL_linux_kernel=https://github.com/fepitre/qubes-linux-kernel' >> 
>> /home/user/qubes-builder/builder.conf
>> echo 'BRANCH_linux_kernel=kernel-5.6' >> 
>> /home/user/qubes-builder/builder.conf
>>
>> 4.1) Get sources of it:
>>
>> make get-sources
> 
> 
> It went  quite well with 5.5.13, but not with 5.6. I get the error:
> 
> -> Updating sources for linux-kernel...
> --> Fetching from https://github.com/QubesOS/qubes-linux-kernel.git 
> kernel-5.6...
> fatal: Remote branch kernel-5.6 not found in upstream origin
> 
There is a typo in 3.2. It should be :

GIT_URL_linux_kernel=...

instead of just

URL_...

-- 
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/95ab3e94-6d4a-7969-f461-885c71f9e368%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Build USB install with kernel 5+

[Frédéric Pierret]

On 2020-04-16 20:55, 'Max Andersen' via qubes-users wrote:
> New error emerges:
> 
> [user@qubes-builder qubes-builder]$ make iso
> -> Preparing for ISO build...
> --> Removing old rpms from the installer repos...
> ---> Cleaning up repo: dom0-updates...
> ---> Cleaning up repo: installer...
> ---> Cleaning up repo: qubes-dom0...
> --> Copying installer-qubes-os RPMs...
> ln: failed to access 
> 'pkgs/dom0-fc25/noarch/pykickstart-2.32-4.fc25.noarch.rpm': No such file or 
> directory
> ln: failed to access 
> 'pkgs/dom0-fc25/noarch/python-kickstart-2.32-4.fc25.noarch.rpm': No such file 
> or directory
> ln: failed to access 
> 'pkgs/dom0-fc25/noarch/python3-kickstart-2.32-4.fc25.noarch.rpm': No such 
> file or directory
> ln: failed to access 
> 'pkgs/dom0-fc25/noarch/python-blivet-2.1.11-6.fc25.noarch.rpm': No such file 
> or directory
> ln: failed to access 
> 'pkgs/dom0-fc25/noarch/python3-blivet-2.1.11-6.fc25.noarch.rpm': No such file 
> or directory
> ln: failed to access 'pkgs/dom0-fc25/x86_64/lorax-25.19-1.fc25.x86_64.rpm': 
> No such file or directory
> ln: failed to access 
> 'pkgs/dom0-fc25/x86_64/lorax-lmc-virt-25.19-1.fc25.x86_64.rpm': No such file 
> or directory
> ln: failed to access 
> 'pkgs/dom0-fc25/x86_64/lorax-lmc-novirt-25.19-1.fc25.x86_64.rpm': No such 
> file or directory
> ln: failed to access 
> 'pkgs/dom0-fc25/x86_64/lorax-templates-generic-25.19-1.fc25.x86_64.rpm': No 
> such file or directory
> ln: failed to access 
> 'pkgs/dom0-fc25/noarch/lorax-templates-qubes-4.0.6-1.fc25.noarch.rpm': No 
> such file or directory
> ln: failed to access 'pkgs/dom0-fc25/noarch/pungi-4.1.14-2.fc25.noarch.rpm': 
> No such file or directory
> ln: failed to access 
> 'pkgs/dom0-fc25/noarch/pungi-utils-4.1.14-2.fc25.noarch.rpm': No such file or 
> directory
> ln: failed to access 
> 'pkgs/dom0-fc25/x86_64/anaconda-25.20.9-17.fc25.x86_64.rpm': No such file or 
> directory
> ln: failed to access 
> 'pkgs/dom0-fc25/x86_64/anaconda-core-25.20.9-17.fc25.x86_64.rpm': No such 
> file or directory
> ln: failed to access 
> 'pkgs/dom0-fc25/x86_64/anaconda-gui-25.20.9-17.fc25.x86_64.rpm': No such file 
> or directory
> ln: failed to access 
> 'pkgs/dom0-fc25/x86_64/anaconda-tui-25.20.9-17.fc25.x86_64.rpm': No such file 
> or directory
> ln: failed to access 
> 'pkgs/dom0-fc25/x86_64/anaconda-widgets-25.20.9-17.fc25.x86_64.rpm': No such 
> file or directory
> ln: failed to access 
> 'pkgs/dom0-fc25/x86_64/anaconda-widgets-devel-25.20.9-17.fc25.x86_64.rpm': No 
> such file or directory
> ln: failed to access 
> 'pkgs/dom0-fc25/x86_64/anaconda-dracut-25.20.9-17.fc25.x86_64.rpm': No such 
> file or directory
> ln: failed to access 
> 'pkgs/dom0-fc25/x86_64/anaconda-debuginfo-25.20.9-17.fc25.x86_64.rpm': No 
> such file or directory
> ln: failed to access 
> 'pkgs/dom0-fc25/x86_64/anaconda-debugsource-25.20.9-17.fc25.x86_64.rpm': No 
> such file or directory
> ln: failed to access 
> 'pkgs/dom0-fc25/noarch/qubes-anaconda-addon-4.0.11-1.fc25.noarch.rpm': No 
> such file or directory
> ln: failed to access 'pkgs/dom0-fc25/noarch/qubes-release-4.0-8.noarch.rpm': 
> No such file or directory
> ln: failed to access 
> 'pkgs/dom0-fc25/noarch/qubes-release-notes-4.0-8.noarch.rpm': No such file or 
> directory
> ln: failed to access 
> 'pkgs/dom0-fc25/noarch/qubes-dom0-dist-upgrade-2.0-2.noarch.rpm': No such 
> file or directory
> make[1]: *** 
> [/home/user/qubes-builder/qubes-src/builder-rpm/Makefile.rpmbuilder:158: 
> update-repo-do] Error 1
> make: *** [Makefile:493: iso.copy-rpms.installer-qubes-os] Error 2
> [user@qubes-builder qubes-builder]$

If you built kernel

make iso COMPONENTS=linux-kernel

else

make iso COMPONENTS=

As 'installer-qubes-os' is in COMPONENTS of builder.conf it thinks that the 
packages have been built where as it downloaded it.

-- 
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/308aa2d9-87d7-5bcb-bf0f-89a61f5419ce%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Build USB install with kernel 5+

[Frédéric Pierret]

> When running make iso I get:
> 
> [user@qubes-builder qubes-builder]$ make iso
> -> Preparing for ISO build...
> --> Removing old rpms from the installer repos...
> which: no createrepo_c in 
> (/home/user/.local/bin:/home/user/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/home/user/qubes-builder/qubes-src/builder-rpm/tools)
> which: no createrepo in 
> (/home/user/.local/bin:/home/user/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/home/user/qubes-builder/qubes-src/builder-rpm/tools)
> ---> Cleaning up repo: dom0-updates...
> ./clean_repos.sh: line 6: -q: command not found
> ---> Cleaning up repo: installer...
> ./clean_repos.sh: line 6: -q: command not found
> ---> Cleaning up repo: qubes-dom0...
> ./clean_repos.sh: line 6: -q: command not found
> make[1]: *** [Makefile:80: clean-repos] Error 127
> make: *** [Makefile:485: iso.clean-repos] Error 2
> [user@qubes-builder qubes-builder]$
> 
> Do I need some libraries or something?

Yes normally you ran:

make install-deps

Here it seems that 'createrepo' or 'createrepo_c' is not installed. 

Hum a little fix in the script 'clean_repos.sh' is needed for proper exit and 
message. I'll fix that.

Best,
Frédéric

> Sincerely
> 
> Max
> 

-- 
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/5f66a10c-c3cd-6617-6e9b-b5f21ef0c648%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Build USB install with kernel 5+

[Frédéric Pierret]

On 2020-04-15 08:09, Max Andersen wrote:
> 
> 
>> Den 14. apr. 2020 kl. 08.02 skrev Frédéric Pierret 
>> :
>>
>> Hi,
>> I used to build newer ISO in the past for such troubles with kernel-latest 
>> embedded. If you are interested, I can build you an 4.0.3 with 
>> kernel-latest-5.6 for try?
> 
> When I try, the builder script fails horribly. Can you write a stepguide? 
> Maybe just commands and selections on how you build it(if it is not too much 
> of a hassle)?

Sure, here are the procedure for building latest Qubes 4.0.3 ISO with already 
built packages (templates included) using Qubes OS official repositories:

1) In a working directory, e.g. `/home/user/`, clone `qubes-builder`:

git clone https://github.com/QubesOS/qubes-builder

2) Download specific builder conf file for such process:

wget 
https://raw.githubusercontent.com/QubesOS/qubes-release-configs/master/R4.0/qubes-os-iso-full-online.conf
 -O /home/user/qubes-builder/builder.conf

3) Enable QubesOS testing packages for the build and specify release branch for 
the installer:

echo 'USE_QUBES_REPO_TESTING=1' >> /home/user/qubes-builder/builder.conf
echo 'BRANCH_installer_qubes_os=release4.0' >> 
/home/user/qubes-builder/builder.conf

4) Get sources:

cd /home/user/qubes-builder/
make get-sources

5) Enable `kernel-latest` in the ISO build process:

sed -i 's#\(kernel-latest.*$\)#\1mandatory\2#' 
qubes-src/installer-qubes-os/conf/comps-qubes.xml

6) Build ISO:

make iso

7) Get your freshly built ISO in `/home/user/qubes-builder/iso`

The current kernel-5.6 is still at PR stage. If you want to try it you need to 
build it:

3.1) Add `linux-kernel` in `COMPONENTS`:

echo 'COMPONENTS+=linux-kernel'

3.2) Change URL and BRANCH of the git repository:

echo 'URL_linux_kernel=https://github.com/fepitre/qubes-linux-kernel' >> 
/home/user/qubes-builder/builder.conf
echo 'BRANCH_linux_kernel=kernel-5.6' >> 
/home/user/qubes-builder/builder.conf

4.1) Get sources of it:

make get-sources

4.2) Build it:

make linux-kernel

Those extra steps X.Y) can be added into the whole ISO build process. Else, it 
can be done after you have installed the ISO previously built (or downloaded 
ISO from official website) with official Qubes packages and install the built 
kernel manually by copying the RPMs create into 
`/home/user/qubes-builder/qubes-src/linux-kernel/pkgs/dom0-fc25/x86_64/`.

I've probably written typo. Don't hesitate to ask in any case.

Best,
Frédéric

-- 
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/df39babb-03c3-ab0b-2157-d7d915292a02%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

[qubes-users] Re: requesting i3-gaps package

[Frédéric Pierret]

On 2020-04-15 08:59, Mr CapsLock wrote:
> Hi, I'm a Qubes-OS user. It's the best OS that I had.
> 
> Thanks for this project.

Welcome!

First of all, if you were not aware, please CC at least Qubes users mailing 
list for such request.

> I like tiling window manager like i3, but it's not very impressive without 
> gaps. How can I request to add i3-gaps package officially for Qubes-OS?

I would suggest you to create an issue here: 
https://github.com/QubesOS/qubes-issues/issues/


> I'm not pro user but maybe i can help to add this, but can you help me on 
> that?
> 
> In new release, i mean new release that have gui manager, is it possible to 
> use i3-gaps on Qubes-OS?

I'm not sure about what you are talking about for 'gui manager', maybe you 
refer to the Gui domain called GuiVM in upcoming 4.1 release? In all the cases, 
it's already possible to use i3 as primary desktop (I'm using it) and packages 
are available in official Qubes repositories. We don't provide i3-gaps yet but 
that could be possible. We don't aim to provide every desktop but that could 
possible into QubesOS-contrib repository.

So first of all, please create an issue as we can exchange about possibilities 
on it.

Best,
Frédéric

-- 
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/4a879828-0fa1-c387-b873-f5d32596c423%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Build USB install with kernel 5+

[Frédéric Pierret]

Hi,
I used to build newer ISO in the past for such troubles with kernel-latest 
embedded. If you are interested, I can build you an 4.0.3 with 
kernel-latest-5.6 for try?

Best,

On 2020-04-14 07:54, 'Max Andersen' via qubes-users wrote:
> Just want to mention the system(firmware, etc.) is brand new, so many
> issues might be lack of support.
> 
> On 4/14/20 1:28 AM, 'awokd' via qubes-users wrote:
>> 'Max Andersen' via qubes-users:
>>
>>> I can actually put in an older wireless usb in the machine, and it sees it 
>>> with lsusb in dom0, but I Dont know how To enable it in vm
>> In dom0, use qvm-usb to try to attach that device to sys-net. Some USB
>> devices don't passthrough very well, though.
> 
> qvm-usb shows no output:
> 
> [max@dom0 ~]$ qvm-usb
> BACKEND:DEVID  DESCRIPTION  USED BY
> [max@dom0 ~]$ lsusb
> Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 001 Device 006: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS
> 802.11n Wireless Network Adapter
> Bus 001 Device 005: ID 046d:c52f Logitech, Inc. Unifying Receiver
> Bus 001 Device 004: ID 046d:c318 Logitech, Inc. Illuminated Keyboard
> Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
> Bus 001 Device 003: ID 8087:0026 Intel Corp.
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> [max@dom0 ~]$
> 
>>> Tried qvm-pci
>>>
>>> It showed usb controller on that?
>>>
>>> When runming qvm-pci a sys-net-clone-1 dom0:00_14.0 it failed with got 
>>> empty response from qubesd and hung
>> You might be trying to attach the USB controller itself to
>> sys-net-clone-1. This can work, if you're sure nothing else is on it
>> (like your keyboard & mouse). Many systems only have one controller
>> though, so try USB passthrough first.
> 
> 
> That was probably what I did and it failed :).
> 
> Sincerely
> 
> Max
> 
> 

-- 
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/aa585133-1fc0-c11a-29a7-519a442075a3%40qubes-os.org.

Re: [qubes-users] Nvidia Geforce GTX 1660TI (1650)

[Frédéric Pierret]

Hi,
There is recent work done at kernel for making HDMI in NVIDIA laptops working. 
Currently, the patches are not merged into 5.6 or LTS 5.4. For example, Fedora 
has backported those patches for 5.6: 
https://src.fedoraproject.org/rpms/kernel/c/c242538da102e54acc0378e3322262058ba5a8de?branch=master

I had also a lot troubles with NVIDIA on laptops. So few days ago I decided to 
backport those upstream patches for Qubes and the result is excellent. I 
finally got HDMI working on problematic laptops.

Currently it's not merged into Qubes but soon. I tested the backport for LTS 
5.4 https://github.com/fepitre/qubes-linux-kernel/commits/v5.4.31-backport and 
5.6 https://github.com/fepitre/qubes-linux-kernel/commits/kernel-5.6-backport

The two branches are on top of current PR for Qubes linux-kernel component. So 
you can build them if you want. If you don't, the two kernels for Qubes 4.1 are 
available on my mirror:
- LTS 5.4: 
https://mirror.notset.fr/qubes/repo/notset/yum/r4.1/unstable/dom0/fc31/rpm/kernel-5.4.31-1.qubes.x86_64.rpm
- Latest: 
https://mirror.notset.fr/qubes/repo/notset/yum/r4.1/unstable/dom0/fc31/rpm/kernel-latest-5.6.3-1.qubes.x86_64.rpm

You can check the signature of the packages with 
https://mirror.notset.fr/qubes/repo/notset/RPM-GPG-KEY-notset

Best,
Frédéric

On 2020-04-13 11:58, user74...@disroot.org wrote:
> Hello,
> 
> 
> does anyone a Geforce GTX 1660 or similar working with qubes 4.0 or 4.1?
> I've already tried to compile the nvidia driver, which is working if i boot 
> qubes without xen.
> But nvidia driver and also the nouveau driver are not working for now.
> I get the device is not supported in Xorg.log.
> 
> 
> Please give me some hints how i can get it work.
> My problem is, that my laptop requires the nvidia card used to get the hdmi 
> port working :-(.
> 
> 
> 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 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/e9b84e87-e8e0-2246-b281-9b3286e10832%40qubes-os.org.

[qubes-users] Docker and Fedora 31

[Frédéric Pierret]

Hi all,

For those who are using docker and also gave a chance to Fedora 31 testing 
template, you may know that there is a "Cgroups Exception" for Fedora 31. 
According to the official page https://docs.docker.com/engine/install/fedora/, 
they suggest to:

"""
For Fedora 31 and higher, you need to enable the backward compatibility for 
Cgroups.

$ sudo grubby --update-kernel=ALL 
--args="systemd.unified_cgroup_hierarchy=0"

"""

That does not really fit Qubes. Globally, it's a matter of adding a kernel 
options to your VM where you run your dockers. Assming this VM is called 
'work-docker', in dom0:

1) Check your VM kernel opts:

qvm-prefs work-docker kernelopts

For me, it was only 'nopat'

2) Add the docker suggested option and your already present kernelopts:

qvm-prefs --set work-docker kernelopts 'nopat 
systemd.unified_cgroup_hierarchy=0'

That's all. You can continue to use your dockers in your Fedora 31 AppVM.

Another useful trick thanks to Qubes, is to use 'bind-dirs' 
(https://www.qubes-os.org/doc/bind-dirs/) for '/var/lib/docker'. It allows you 
to not modify default dockers location or symlink or copy paste at early boot 
or whatever.

Best,
Frédéric

-- 
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/f29726a0-610b-e1c5-0d56-470737a53536%40qubes-os.org.

Re: [qubes-users] Using Disk2vhd or VMware vCenter Converter to copy existing win10 installation to use in Qubes?

[Frédéric Pierret]

On 2020-03-06 15:24, Stumpy wrote:
> On 2020-03-06 09:20, Frédéric Pierret wrote:
>>
>> On 2020-03-03 09:43, Stumpy wrote:
>>> Hi, I have an existing win10 installation which I want to copy and then use 
>>> as a template in Qubes. I am sure I asked before somewhere about this and 
>>> the only thing i remember about the response was Disk2vhd.
>>
>> 1) From where you have win10 installation? It comes from a physical machine 
>> or VM? 
> 
> From a physical machine.
> 
> Yes this question from physical is necessary, especially if enabling proper 
> drivers in Windows is needed.
> 
> It would be from a physical machine, and its my hope to then install qubes on 
> this machine, and then run this win10 vm (along with other VMs) on this 
> machine.
>>
>> 2) In which format? OVA, VMDK?
> 
> Well i guess it depends, I am fine with whatever that is using vmware to copy 
> the physical machine to ova or vmdk - my pref i guess would be whichever is 
> easier.

I don't know how you want to go from your physical windows 10 (unrelated to 
vCenter) to a Qubes VM. I almost did something like this. The target was not 
Qubes but KVM(+libvirt) but this is almost the same for Qubes. Here is what 
I've done:

0) In the windows, enabled the related drivers at boot. First with IDE backend: 
atapi.sys, intelide.sys, pciide.sys and msahci.sys. I only identified those 
four for booting the VM and preventing the famous BSOD with 7B error.
1) Used 'dd' for creating a raw image of the physical drive,
2) Created a VM as I told you by using 'dd' from this raw image to an LVM
3) Booted the VM and installed missing drivers

Good luck :)
 
>>
>> I would go to use qemu-img for converting VMDK (certainly in sparse format 
>> if it comes from vCenter) into raw image. Then, creating a standalone HVM in 
>> Qubes with sufficient space then dd from your image to your root lvm 
>> partition of the newly created VM.
> 
> Thanks for the concise suggestion, i think i got it.
> 
> Will get it a try. Cheers
> 
>>
>>  
>>> So i am thinking its possible to copy an existing installation, and hoping 
>>> its possible to use that image as a template in Qubes but am really unsure 
>>> about the details.
>>>
>>> Is there a write or relevant howto for doing something like this?
>>>
>>> Thanks!
>>>
>>
>> Best,
>>
> 

-- 
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/08912aaa-473e-cd11-9601-342f2a445ab5%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Using Disk2vhd or VMware vCenter Converter to copy existing win10 installation to use in Qubes?

[Frédéric Pierret]

On 2020-03-03 09:43, Stumpy wrote:
> Hi, I have an existing win10 installation which I want to copy and then use 
> as a template in Qubes. I am sure I asked before somewhere about this and the 
> only thing i remember about the response was Disk2vhd.

1) From where you have win10 installation? It comes from a physical machine or 
VM? Yes this question from physical is necessary, especially if enabling proper 
drivers in Windows is needed.

2) In which format? OVA, VMDK?

I would go to use qemu-img for converting VMDK (certainly in sparse format if 
it comes from vCenter) into raw image. Then, creating a standalone HVM in Qubes 
with sufficient space then dd from your image to your root lvm partition of the 
newly created VM.

 
> So i am thinking its possible to copy an existing installation, and hoping 
> its possible to use that image as a template in Qubes but am really unsure 
> about the details.
> 
> Is there a write or relevant howto for doing something like this?
> 
> Thanks!
> 

Best,

-- 
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/014a351d-f742-049f-c424-7a5bbf8ae6fd%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Corrupted GUI after XFCE logon

[Frédéric Pierret]

Hi,

I would do something like:

- systemctl stop lighdtm
- mv ~/.config/xfce4{,.bak}
- systemctl restart lightdm

Your XFCE settings are backuped for further investigation.

Best,
Frédéric

On 2020-03-02 10:46, IX4 Svs wrote:
> Today I booted my Qubes laptop (Dell Precision M4800) which has been working 
> fine for a while and noticed that after entering my password in the GUI 
> session manager to enter XFCE I’m being logged on, but there is something 
> wrong with the resolution of the display and the result is a corrupted and 
> unusable GUI. (See attachment)
> 
> I can hit CTRL-ALT-F2 to get a console session, but not sure how I should 
> proceed to troubleshoot the XFCE settings from there. Is there a way to 
> “reset” the X server settings or force it to attempt to auto-detect the 
> screen size? This is odd as it used to work fine for the built-in laptop 
> display, but has now become unusable.
> 
> I installed all dom0 updates and rebooted to ensure I have the latest 
> patches, but it didn’t help. Qubes R4.0
> 
> Thanks in advance,
> 
> Alex
> 

-- 
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/f7f1da86-43ef-1e68-4c2d-d3c9b3869c72%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] i3 | dmenu | unable to open applications

[Frédéric Pierret]

Hi,

On 2020-03-01 19:06, stefan.ho...@posteo.net wrote:
> I am testing the i3 windows manager on 4.19.100-1.pvops.qubes.x86_64.
> I've installed it according to https://www.qubes-os.org/doc/i3/, including 
> i3-settings-qubes.
> Whenever I invoke dmenu (Mod+d) and start typing in order to search for an 
> application, dmenu just disappears.
> I've observed that behavior also on a freshly installed qubes4 system.
> 
> Any thoughts on getting it to work? Thanks!
> 

Yes it's about locales. I had this problem and I had to change it to en_US 
instead of C from what I remember.

Best,
Frédéric

-- 
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/0b07b0a0-d06f-8c94-ac68-2c0a4b515f22%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Is Qubes Split GPG safe?

[Frédéric Pierret]

On 2020-02-13 20:37, Claudio Chinicz wrote:
> Hi Frédéric,
> 
> Thanks, I've managed to install claws-mail on my Fedora template. The problem 
> is that Claws-mail does not support Oath2 (Google) authentication, just like 
> Kmail.

Your welcome.

> 
> Evolution does support Oatrh2 authentication but instead of Gnupg it supports 
> Open PGP, the same standard that TB 79 will support, replacing Enigmail.
> 
> Would Open PGP support/integrate with Qubes Split GPG?

I CC Marek to this question as I known there is some new version of it but I 
don't know what's inside.

Best regards,
Frédéric

-- 
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/107ce55b-e7e5-085f-7d50-b060aa95ea29%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Is Qubes Split GPG safe?

[Frédéric Pierret]

On 2020-02-13 18:36, Claudio Chinicz wrote:
> Hi Sven,
> 
> Thanks again. I've tried them and found the following:
> 
> - KMail is not allowed to authenticate with Oath2 from Google (my accounts 
> are Gmail)
> - Evolution now does not support Gnupg
> - Claws is not available for Fedora

'claws-mail' package is available in Fedora.

-- 
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/47b77bf4-4f6d-b90e-9d19-7f205187038a%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] create custom image result in problems with python-blivet sources

[Frédéric Pierret]

Hello,
You need the src.rpm. Else, you can use the branch in the PR 
https://github.com/QubesOS/qubes-blivet/pull/4
Best,
Frédéric

On 2020-02-09 19:16, user74...@disroot.org wrote:
> Hello.
> 
> thanks for your hints, but i need a little more help.
> The actual versions in fc31 are:
> - python3-blivet-3.1.5-2.fc31.noarch.rpm
> - python3-blivet-3.1.7-1.fc31.noarch.rpm
> 
> If i look for a matching storaged-project/blivet version then i don't find 
> the file blivet-xxx-tests.tar.gz.
> The only version with the test-archive is 3.2.0. This version would be 
> available in fc rawhide.
> And do i need the existing patches or some others?
> 
> I'm now not sure how i can solve this situation. 
> This is the first time for me to use the qubes-builder, can someone help me?
> 
> Thanks
> 
> 
>> Hello,
>> Do a 'make get-sources' in blivet repo. The pull of sources is done once 
>> during the global get sources. Here the problem is that we use SRPM from 
>> fedora repositories but they are not keeping all the versions. In 
>> consequence, we currently need to sync with Fedora update.
>>
>> Best,
>> Frédéric
>>
>> Le 8 février 2020 14:35:10 GMT+01:00, user74...@disroot.org a écrit :
>>> Hello,
>>> i'm trying to create a custom qubes image to install a fedora 31 dom0
>>> using https://www.qubes-os.org/doc/qubes-builder/ 
>>> (mailto:qubes-users+nore...@googlegroups.com)to see how it will run on
>>> my hardware.
>>> Already the step 'make get-sources' show the following problem up:
>>> --> Downloading additional sources for blivet...
>>> Cannot find source RPM: python-blivet-3.1.6-1.fc31.src.rpm
>>> make[1]: *** [Makefile:21: blivet-3.1.6.tar.gz.UNTRUSTED] Error 1
>>> make: *** [Makefile:205: blivet.get-sources-extra] Error 2
>>>
>>> I've tried to solve this with a newer version 3.1.7, but then there are
>>> the test-src's... missing while building.
>>> Please give me some hints to solve my problem .
>>> 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 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/649a6a486daecf809d99c69427baeff5%40disroot.org.
>> -- 
>> Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma 
>> brièveté.
> 

-- 
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/994ab7e0-3b68-2d87-f17e-0ce0b5c0be79%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] create custom image result in problems with python-blivet sources

[Frédéric Pierret]

Hello,
Do a 'make get-sources' in blivet repo. The pull of sources is done once during 
the global get sources. Here the problem is that we use SRPM from fedora 
repositories but they are not keeping all the versions. In consequence, we 
currently need to sync with Fedora update.

Best,
Frédéric

Le 8 février 2020 14:35:10 GMT+01:00, user74...@disroot.org a écrit :
>Hello,
>i'm trying to create a custom qubes image to install a fedora 31 dom0
>using https://www.qubes-os.org/doc/qubes-builder/ 
>(mailto:qubes-users+nore...@googlegroups.com)to see how it will run on
>my hardware.
>Already the step 'make get-sources' show the following problem up:
>--> Downloading additional sources for blivet...
>Cannot find source RPM: python-blivet-3.1.6-1.fc31.src.rpm
>make[1]: *** [Makefile:21: blivet-3.1.6.tar.gz.UNTRUSTED] Error 1
>make: *** [Makefile:205: blivet.get-sources-extra] Error 2
>
>I've tried to solve this with a newer version 3.1.7, but then there are
>the test-src's... missing while building.
>Please give me some hints to solve my problem ;-).
>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 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/649a6a486daecf809d99c69427baeff5%40disroot.org.

-- 
Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma 
brièveté.

-- 
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/F7B84AB1-F4D5-49B5-B140-9D9BE0B76631%40qubes-os.org.

Re: [qubes-users] Is CentOS in Qubes Broken?

[Frédéric Pierret]

Hi,

We have not put yes centos-7 in stable repository but soon!

You can get it by enabling qubes-templates-community-testing:

|--enablerepo=qubes-templates-community-testing|

Best,
Frédéric

On 2020-02-01 01:59, Mike Karasoff wrote:
> Hi,
>
> I'm trying to install the CentOS template, and cannot.  I failed both
> with getting the community template and trying to build one with
> qubes-builder.  I'm using Qubes V4.0.  I've had no trouble building
> Debian based templates (bionic, buster). 
>
> First, I tried to get the community template using the instructions
> from the docs here:  https://www.qubes-os.org/doc/templates/centos/
>
> The result was:
> /[user@dom0 ~]$ sudo qubes-dom0-update
> --enablerepo=qubes-templates-community qubes-template-centos-7/
> /Using sys-firewall as UpdateVM to download updates for Dom0; this may
> take some time.../
> /Last metadata expiration check: 22:12:59 ago on Thu Jan 30 17:43:53
> 2020./
> /No match for argument: qubes-template-centos-7/
> /Error: Unable to find a match/
>
> Has the centos template been removed?  Are there any pointers on how
> to search the /qubes-templates-community /repo?  I can't seem to find
> any links to that repo.
>
>
> I then tried to building the template with qubes-builder, and failed
> during make-template:
> /--> Finished Dependency Resolution//
> /
> /Error: Package: qubes-core-agent-4.0.52-1.centos7.x86_64
> (template-builder-repo)//
> /
> /   Requires: python3-daemon//
> /
> /Error: Package: qubes-core-agent-4.0.52-1.centos7.x86_64
> (template-builder-repo)//
> /
> /   Requires: python3-dbus//
> /
> /Error: Package: qubes-vm-recommended-4.0.6-1.centos7.noarch
> (template-builder-repo)//
> /
> /   Requires: thunderbird-qubes//
> /
> /Error: Package: qubes-core-agent-4.0.52-1.centos7.x86_64
> (template-builder-repo)//
> /
> /   Requires: python3-pyxdg//
> /
> /You could try using --skip-broken to work around the problem//
> /
> /You could try running: rpm -Va --nofiles --nodigest//
> /
> /make[1]: *** [Makefile:64: rootimg-build] Error 1/
>
> Am I doing something wrong here?  I don't know enough about what is
> going on in this build process, but this feels like some packages
> aren't getting installed properly at some point upstream.
>
> Has support for CentOS in Qubes been discontinued or broken in a
> recent update? 
> Is this a bug?  It is not clear to me where I should report the bug -
> community or Qubes.
>
>
>
> Thanks,
> Mike
> -- 
> 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/TqYjoJTboBJHBRRCGO3hIKgnMMwxHUGR4cfIztAL4-Z57iVmTwNFw3_WktVBkhTx2flOMj_Pekm_Md9w5P-L_gYyU-10HfWNlGolwmw6mmE%3D%40karatronics.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/77905b87-485b-e50e-aadd-3014930b71b7%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

[qubes-users] Re: [qubes-devel] NVIDIA RTX 20XX

[Frédéric Pierret]

Hi,

We debugged this problem with Marek and found a simple temporary
workaround:
https://mirror.notset.fr/qubes/repo/notset/yum/r4.0/unstable/dom0/fc25/rpm/

If you want to try and tell us it solves the problem on your side too,
you can find the built kernel with this path on my mirror:
https://mirror.notset.fr/qubes/repo/notset/yum/r4.0/unstable/dom0/fc25/rpm/
signed with my bot signature
https://mirror.notset.fr/qubes/repo/notset/RPM-GPG-KEY-notset

Best,

Frédéric

On 2020-01-25 00:30, Frédéric Pierret wrote:

> Hi,
>
> Thank you for your feedback. I just tested under R4.1 in development and
> I succeeded to have a kernel log thanks to Marek and few hacks in dom0.
>
> Here is the bug report: https://bugzilla.kernel.org/show_bug.cgi?id=206299
>
> FYI, I tried few months ago to build NVIDIA module under Qubes but I hit
> a problem of allocating buffers. It was the same problem than a one
> reported on NVIDIA dev forum by another person using Xen as a desktop
> machine (not Qubes).
>
> Best,
>
> Frédéric
>
> On 2020-01-24 17:22, Ralph Alexander Bariz wrote:
>> Have the same problem with a rtx 2070. My temporary solution is to put a 
>> cheap gpu into my pc(nvidia geforce 710) into the second pci port and cut of 
>> the power of the 2070 when using qubes.
>> the problem is simple. The included nouveau driver does not support it. You 
>> could install the properitary one whats a security problem.
>> my attemp to solve it, when I've got time, will be to compile the newest 
>> nouveau driver in a fedora 25 qubes and install it to dom0.
>> For sure its necessary to ensure cube nit getting compromised in the 
>> process. 
>>
>> BR
>>

-- 
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/4948e3bc-d8ec-a12f-65a7-8e8117d6dfaa%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

[qubes-users] Re: [qubes-devel] NVIDIA RTX 20XX

[Frédéric Pierret]

Hi,

Thank you for your feedback. I just tested under R4.1 in development and
I succeeded to have a kernel log thanks to Marek and few hacks in dom0.

Here is the bug report: https://bugzilla.kernel.org/show_bug.cgi?id=206299

FYI, I tried few months ago to build NVIDIA module under Qubes but I hit
a problem of allocating buffers. It was the same problem than a one
reported on NVIDIA dev forum by another person using Xen as a desktop
machine (not Qubes).

Best,

Frédéric

On 2020-01-24 17:22, Ralph Alexander Bariz wrote:
> Have the same problem with a rtx 2070. My temporary solution is to put a 
> cheap gpu into my pc(nvidia geforce 710) into the second pci port and cut of 
> the power of the 2070 when using qubes.
> the problem is simple. The included nouveau driver does not support it. You 
> could install the properitary one whats a security problem.
> my attemp to solve it, when I've got time, will be to compile the newest 
> nouveau driver in a fedora 25 qubes and install it to dom0.
> For sure its necessary to ensure cube nit getting compromised in the process. 
>
> BR
>

-- 
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/68642de8-f429-3c2c-5a3a-6fabc7004e83%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

[qubes-users] NVIDIA RTX 20XX

[Frédéric Pierret]

Hi,

Does anyone succeeded to have a working/non-crashing system with a
nvidia RTX 20XX, specifically 2080TI in my case? Currently having
instant reboot issues on Qubes 4.0 whereas on Windows it currently works
pretty well so I don't expect having GPU hardware issue.

Thank you in advance,

Frédéric


-- 
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/53a5c356-71bf-e02e-60f3-3457e5434fdf%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Fedora 29 has reached EOL

[Frédéric Pierret]

On 2019-12-02 01:01, Andrew David Wong wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On 2019-11-28 1:16 AM, Claudia wrote:
>> Andrew David Wong:
>>> Please note that no user action is required regarding the OS
>>> version in dom0. For details, please see our Note on dom0 and
>>> EOL. [6] [6]
>>> https://www.qubes-os.org/doc/supported-versions/#note-on-dom0-and-eol
>> Is it *possible* to upgrade dom0 to, say, F30, if we wanted to? I
>> seem to remember reading somewhere it's pretty much impossible, but
>> I haven't been able to find that article.
>>
> Not as far as I know, but Marek and Frédéric (CCed) would know more
> about this.

Even if in theory, this is possible but that would mean to patch R4.0
with a lot of adjustments in upstream R4.1. I would discourage such
attempt because there is major differences between fc25 and fc30. That
would also mean doing the work we have done for going to dom0 fc29.

We are going to use dom0 fc31 instead of fc29 for next release 4.1 and
there is also other troubles like python3 migration as python2 is
assumed deprecated in Fedora 31.

>> I have a newer machine, and I've found several hardware features
>> that work under F30 but not F25 and not under Qubes even with the
>> same kernel version as tested in F30 (suggesting the Fedora
>> userland plays a role too).
>>
>> It seems like the 5+ version lag could be holding back a lot of
>> potential Qubes users. Especially considering Qubes/Xen is quite
>> hardware-sensitive to begin with.
>>
> It sounds like your best bet might be to try R4.1, which will run
> Fedora 29: https://github.com/QubesOS/qubes-issues/issues/4225
>
> - -- 
> Andrew David Wong (Axon)
> Community Manager, Qubes OS
> https://www.qubes-os.org
>
> -BEGIN PGP SIGNATURE-
>
> iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAl3kVDAACgkQ203TvDlQ
> MDCynQ/9GqUp7ASrhpvnRicdammemQ6b11st6IU2Ra0WaD9VJJNwQuwJKH8Di2O1
> wdejuIlgz+hyD2Kx8LyeF28uR8EJiLPJt7CzK3zm5RuET1SjA4AXaIKrhhL8qMS6
> a3qYmQ7FxT0tobURxunt8+dejbweJ+RQCXYwqKgzsfjTos+z0bPmDISxEwbKFM/a
> Tr0u0SXHP8DY45P1XA4Y6o9k8PZVnrFxEcFYsxiHUl56Xa3IPDY1zq3uuSikcviv
> fWQFSnaKfk/Ki8EE/vHF4dvQi0X22k9kP4qQPM5d+xK+P4hkVtHQL8G8pRBb5rie
> Z0OHpMOdUq/AXp/jmV7QdJHRIjlpTj9VizRYsbH3atBgp9p8tSR0CjxkXRbhzDJ3
> Pudh3+uCFthUhSZdrXj8Nen2QE93wZtFfbn8vXYMzwD/zX9Utcc9lDb30HWpQSTn
> pkFnXAkv/TEA9k8XEtxFUoGyWg+XnZ2vJOet4Tcz3rxjw4IxCpsLHJRGVJyKqsUG
> U0qUp1/jXl9ndWfhPFB9sLjbHjRJi0dMJGBmqjC5gSIy8PZiSVqpphYYd90elp28
> vJuu9/7nL9KGadHS0Dw7wgkCNJw4pegqJHHkBFbblDBS96L8KNz49hv41xwbivw5
> N5xznSLSArMktz4VoR5gMIQTN8dIRj38ePr23X95vGUdqx35rPw=
> =Fn8X
> -END PGP SIGNATURE-
>
>

-- 
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/2f33a97b-d0e3-4584-4a8a-e31d5f25778d%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Re: Fedora-31 template

[Frédéric Pierret]

Hi,

Fedora 31 requires mostly newer python3 libraries. We have started
migration to python3 for only Qubes R4.1 (not yet released). It induces
major changes notably in core-agent that we prefer to not backport in R4.0.

We encourage you to be patient for newer Qubes release and keep using
Fedora 30.

Best regards,

Frédéric

On 2019-11-26 16:11, Dominique St-Pierre Boucher wrote:
> Thanks for the info, I did exactly that before seeing you documentation.
>
> Unfortunately, I got errors:
>
> Problem: Problem with installed package
> qubes-core-agent-4.0.50-1.fc30.x86_64
>  - package qubes-core-agent-4.0.50-1.fc31.x86_64 requires
> python-daemon, but none of the providers can be installed
>  - package qubes-core-agent-4.0.48-1.fc31.x86_64 requires
> python-daemon, but none of the providers can be installed
>  - package qubes-core-agent-4.0.50-1.fc31.x86_64 does not belong to a
> distupgrade repository
>  - package python2-daemon-2.2.3-1.fc30.noarch does not belong to a
> distupgrade repository
>
> Idea anyone?
>
> Dominique
> On Saturday, November 16, 2019 at 3:17:33 PM UTC-5, m...@militant.dk
> wrote:
>
> Hi Dominique,
>
> The official docs states:
> https://www.qubes-os.org/doc/templates/#updating
> 
>
> In an earlier version, I updated another fedora, by renaming some
> stuff in repo's.
>
> Guide is here, if you wan't to get inspiration:
> 
> https://www.militant.dk/2018/04/04/cloning-fedora-26-to-fedora-27-template-qubes-3-2/
> 
> 
>
> Sincerely
> Max
>
> fredag den 15. november 2019 kl. 21.23.54 UTC+1 skrev Dominique
> St-Pierre Boucher:
>
> Hello Qubes users,
>
> Do any of you tried and succeed upgrading a Fedora template to
> version 31?
>
> If so, how?
>
> Thanks
>
> Dominique
>
> -- 
> 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/498d4cd7-1089-490d-a696-aa36ef02b896%40googlegroups.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/04b3fb38-f996-e17a-943c-44b263093d18%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

[qubes-users] Re: HCL - Lenovo X270

[Frédéric Pierret]

I forgot to mention that HDMI is also working out of the box with
current kernel-4.19 provided by the R4.0.2rc1.

This is really a plug and play Qubes installation :)

Best,

On 7/16/19 7:22 PM, Frédéric Pierret wrote:
> Hi,
>
> I installed Qubes R4.0.2rc1 on a Lenovo X270 without any problem.
> Initial setup of Qubes with separate 'sys-usb', default VMs went fine.
> Suspend is currently working without any problem.
>
> The installation is in UEFI mode (with secure boot disabled).
>
> Best,
>

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/56c38727-7e12-3ae0-c040-64f7df8ddf16%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

[qubes-users] HCL - Lenovo X270

[Frédéric Pierret]

Hi,

I installed Qubes R4.0.2rc1 on a Lenovo X270 without any problem.
Initial setup of Qubes with separate 'sys-usb', default VMs went fine.
Suspend is currently working without any problem.

The installation is in UEFI mode (with secure boot disabled).

Best,

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/1d7cf0b4-9353-505f-8386-3ce0763ca63c%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


Qubes-HCL-LENOVO-20K5S3J102-20190716-191213.yml
Description: application/yaml


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Raid 5 failure

[Frédéric Pierret]

Hi,

It's not Qubes related. I encourage you to look at usual manual of
mdadm. Normally, after managing to repair your array, you should do
something like:

    1) Backup /etc/mdadm/mdadm.conf

    2) sudo mdadm --detail --scan --verbose > /etc/mdadm/mdadm.conf

    3) Reboot to check

Best,

Frédéric

On 7/10/19 10:23 PM, 'Whenow' via qubes-users wrote:
> I have a RAID 5 configuration that has failed. I physically removed
> the failed disk, inserted a new one of the same nominal capacity. Then
> in dom0 I used mdadm to add the new disk to the array and the new disk
> was successfully added in to the array. Upon every reboot now the disk
> is not automatically added to the RAID. I need to create the device
> node for the new hard drive's RAID partition and then manually enter
> "sudo mdadm --manage /dev/md127 --add /dev/sdc1" to complete the RAID
> setup. What do I need to do to make this setup automatic?
> -- 
> 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 post to this group, send email to qubes-users@googlegroups.com
> .
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/qubes-users/xyv3lRaE14w1yGqVz_mM0rVTgcGVUtjsihNjdYiALRZUHl9G7ClttjBn3gBgNaf9-jOq5eqPTyQTTipPqFUAk9370b7xWn3Zvn11jZvbH9Q%3D%40protonmail.com
> .
> For more options, visit https://groups.google.com/d/optout.

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/4dc1c070-883c-5f6d-cf02-98394d3b31ff%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] has any one get fully worked archlinux template?

[Frédéric Pierret]

Hi,

Why do you think someone would take take time to answer you if you don't
take time to write a proper demand? Some keywords for you: 'Hi',
'Thank', 'you'

On 6/15/19 4:31 PM, travorfirefuel...@gmail.com wrote:
> subj
>

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/d1411c43-3339-8b12-17b1-8fc17d0be4f6%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] DNF will only download packages for the transaction

[Frédéric Pierret]

The thing is that it will only download packages in the updatevm, then
these packages are passed to dom0 where normal 'dnf ACTION PACKAGES' is
done from this cached packages.

So what is exactly your current problem?

On 6/4/19 12:33 PM, Sphere wrote:
> This has annoyed me for the second time and IDK what to do about it anymore. 
> Got a workaround for this before with sudo dnf reinstall suggested by someone 
> on a thread I created back then but yeah it's back after I just did a
> sudo qubes-dom0-update --clean
>
> Seems the workaround doesn't work for kernel-qubes-vm and I haven't tried for 
> kernel but I assume it may be the same case.
>
> Could anyone help me with this?
>

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/3d4ba911-2679-2905-c987-2726ce799542%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Error: Unable to find a match for fedora-30/fedora-30-minimal (yet again for new templates)

[Frédéric Pierret]

Hi,

In dom0 try:

    sudo qubes-dom0-update --clean

and then you can

    sudo qubes-dom0-update qubes-template-fedora-30

Best,

On 6/4/19 10:55 AM, Sphere wrote:
> Hi, I have no idea why I'm experiencing the same old problem with the new 
> fedora-30 templates. I was able to successfully install fedora-29-minimal 
> when I had the first instance of this problem so I thought that the problem 
> may be residing on the repositories but with this happening then maybe 
> there's more to it than just that.
>
> I've already tried doing sudo dnf clean all to no avail but 
> sadly it doesn't solve the problem.
>

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/d51958d9-2535-0b6e-8782-2486059cc8fa%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

[qubes-users] Qubes Server Formulas

[Frédéric Pierret]

Dear Qubes community,

Just to inform you that I'm currently working on Qubes Server Formulas
(Salt) for providing examples of server configurations. It intends to
provide sufficient built-in Qubes materials for bringing Qubes to the
edge of server environments. You can track this work here:
https://github.com/QubesOS/qubes-issues/issues/5051. I succeeded to
create some working topologies but there is still some adjustments to do
in some Qubes components.

If you have any question on this work, please use the mailing list
instead of the issue itself.

Best regards,

Frédéric Pierret


-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/f28aa04d-626e-36ff-790a-a9002ff9785b%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] QVM-Create --HVM-Template Errors... Docs appear out of date...

[Frédéric Pierret]

Hi,

Please try the working procedure for windows 7 here:
https://www.qubes-os.org/doc/windows-vm/

On 4/12/19 8:47 AM, apaunov...@gmail.com wrote:
> I am trying to create a Windows 7 template for cloning into app VMs...
>
> I am following this doc here:
>
> https://www.qubes-os.org/doc/windows-tools/
>
> The command to create a TEMPLATE simply won't work.
>
>
>
> $ qvm-create --hvm-template win7-x64-template -l green
>
>
> The following error pops:
>
>
> unrecognized arguments: --hvm-template.
>
>
> So, how do I proceed with the creation of the template? It just won't create 
> it.
>

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/70767b3c-6f0a-370e-a22f-a68cc7604233%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes 4.0.1 and Ryzen APU - How to update kernel?

[Frédéric Pierret]

Can you please clarify what do you mean by 'no longer boot on the
intermediate/installation system'?

On 3/19/19 5:34 PM, mittend...@digitrace.de wrote:
> Thank you,
>
> sudo qubes-dom0-update kernel-latest
>
> worked for the target system. However this Qubes installation does no longer 
> boot on the intermediate/installation system. a 
> uname -a
> proves that the kernel was updated.
>
> Am 19.03.19 um 10:11 schrieb Frédéric Pierret:
>> Hi,
>>
>> 'unstable' repo is not used currently. Please use 'current-testing'
>> which have 4.19+ latest LTS kernels. You can also install
>> 'kernel-latest' which is mainline stable kernel.
>>
>> So you can do:
>>
>>     sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing
>> kernel kernel-qubes-vm
>>
>> Best,
>>
>> Frédéric
>>
>> On 3/19/19 9:14 AM, mittend...@digitrace.de wrote:
>>> I tried to install Qubes 4.0.1 on a different system and update it,
>>> but its still 4.14-XXX kernel and not booting with Ryzen 2200G APU. Even
>>> sudo qubes-dom0-update --enablerepo=qubes-dom0-unstable kernel
>>> kernel-qubes-vm
>>>
>>> does not install a newer Kernel, probably because it tries to find an
>>> update in the fedora 25 repository. What can Ryzen APU user do?
>>>

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/c4e568a5-a363-c2b2-5ba7-afa4c06bc62e%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Qubes 4.0.1 and Ryzen APU - How to update kernel?

[Frédéric Pierret]

Hi,

'unstable' repo is not used currently. Please use 'current-testing'
which have 4.19+ latest LTS kernels. You can also install
'kernel-latest' which is mainline stable kernel.

So you can do:

    sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing
kernel kernel-qubes-vm

Best,

Frédéric

On 3/19/19 9:14 AM, mittend...@digitrace.de wrote:
> I tried to install Qubes 4.0.1 on a different system and update it,
> but its still 4.14-XXX kernel and not booting with Ryzen 2200G APU. Even
> sudo qubes-dom0-update --enablerepo=qubes-dom0-unstable kernel
> kernel-qubes-vm
>
> does not install a newer Kernel, probably because it tries to find an
> update in the fedora 25 repository. What can Ryzen APU user do?
>

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/c1ff2077-93c5-7e52-2b84-85b7ab1901af%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Driver for usb wifi MT7610U

[Frédéric Pierret]

Hi,

Sorry for the few trouble you had with the .repo files which has been
corrected in recent updates.

Have a look into your VM where you attached your wifi adapter. Does
something like 'bad usb cable' appear?

Best,

Frédéric

On 3/18/19 3:32 PM, Christophe wrote:
>
> Hello, thank you for your help.
>
> sudo qubes-dom0-update kernel-latest-qubes-vm, did not find any
> package, by running sudo qubes-dom0-update -v I found out something
> was pointing to some non existing URL.
>
> https://yum.qubes-os.org/r25-5/current/dom0/fc25/repodata/repomd.xml.metalink
>
> After some research I did some changes in
> /etc/yum.repos.d/qubes-dom0.repo, I replaced all the $releasever by
> 4.0, I got an important amount of updates after this and I was finally
> able to user kernel 4.20.3-1 in my VMs.
>
> Unfortunately this still didn't solve my wifi adapter problem. When I
> now assign the wifi adapter to a vm with the qvm-usb attach command,
> it appears briefly in the lsusb results of the vm, but then just
> disappears.
>
> Best regards,
>
> Christophe
>
> On 3/17/19 10:15 PM, Frédéric Pierret wrote:
>>
>> Hi,
>>
>> I just googled
>> (https://wireless.wiki.kernel.org/en/users/drivers/mediatek) that it
>> seems to be in 4.19+ kernels. From your error, you seem to run 4.14
>> kernel into you vm. Or we provide 4.19+ kernels. You need to update
>> your dom0 (if it is not done) and change your vm settings to use
>> kernel-4.19.15 which is the current LTS. We also provide mainline
>> stable kernel by installing 'kernel-latest'. So if you are only
>> interested in having more updated kernels only in your VM, install
>> the package 'kernel-latest-qubes-vm' (in dom0: sudo qubes-dom0-update
>> kernel-latest-qubes-vm) and change your vm settings to the more
>> recent one.
>>
>> Best regards,
>>
>> Frédéric
>>
>> On 3/17/19 9:59 PM, 'Christophe Vial' via qubes-users wrote:
>>> Hi all, I'm trying to use a usb wifi adapter (TP-Link archer T2U).
>>>
>>> the lsusb command returns
>>>
>>> Bus 002 Device 002: ID 148f:761a Ralink Technology, Corp. MT7610U
>>> ("Archer T2U" 2.4G+5G WLAN Adapter
>>>
>>> After some research I found the driver to install from
>>> https://github.com/ulli-kroll/mt7610u
>>>
>>> But the make command fails. I tried both in fedora-29 and debian9 vm,
>>> but in both cases I get the same error :
>>>
>>> make ARCH=x86_64 CROSS_COMPILE= -C
>>> /lib/modules/4.14.74-1.pvops.qubes.x86_64/build M=/home/user/src/mt7610u
>>> modules
>>> make[1]: Entering directory
>>> '/usr/lib/modules/4.14.74-1.pvops.qubes.x86_64/build'
>>> make[2]: *** No rule to make target
>>> '/home/user/src/mt7610u/os/linux/rt_profile.o', needed by
>>> '/home/user/src/mt7610u/mt7610u.o'.  Stop.
>>> make[1]: *** [Makefile:1527: _module_/home/user/src/mt7610u] Error 2
>>> make[1]: Leaving directory
>>> '/usr/lib/modules/4.14.74-1.pvops.qubes.x86_64/build'
>>> make: *** [Makefile:370: modules] Error 2
>>>
>>> Does anyone knows how to fix it ?
>>>
>>> And if not, any recommendations for some usb wifi adapters working out
>>> of the box ? I still have few days to return this one if I can't get it
>>> working.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> -- 
>>> 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
>>> <mailto:qubes-users+unsubscr...@googlegroups.com>.
>>> To post to this group, send email to qubes-users@googlegroups.com
>>> <mailto:qubes-users@googlegroups.com>.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/qubes-users/Z0glcPBTr8ysTLe7JJX_K95S3BruPuVKAeqHIB2nPad1ANzOYUpWDhDmVTcRN56JaptfUPAKUySJ6iTNHxCy8e1AhKi4XnNkL_JRlh3kXq4%3D%40protonmail.com
>>> <https://groups.google.com/d/msgid/qubes-users/Z0glcPBTr8ysTLe7JJX_K95S3BruPuVKAeqHIB2nPad1ANzOYUpWDhDmVTcRN56JaptfUPAKUySJ6iTNHxCy8e1AhKi4XnNkL_JRlh3kXq4%3D%40protonmail.com?utm_medium=email&utm_source=footer>.
>>> For more options, visit https://groups.google.com/d/optout.

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/f644ca4f-7486-9e08-325e-d063bc5cb3cc%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Driver for usb wifi MT7610U

[Frédéric Pierret]

Hi,

I just googled
(https://wireless.wiki.kernel.org/en/users/drivers/mediatek) that it
seems to be in 4.19+ kernels. From your error, you seem to run 4.14
kernel into you vm. Or we provide 4.19+ kernels. You need to update your
dom0 (if it is not done) and change your vm settings to use
kernel-4.19.15 which is the current LTS. We also provide mainline stable
kernel by installing 'kernel-latest'. So if you are only interested in
having more updated kernels only in your VM, install the package
'kernel-latest-qubes-vm' (in dom0: sudo qubes-dom0-update
kernel-latest-qubes-vm) and change your vm settings to the more recent one.

Best regards,

Frédéric

On 3/17/19 9:59 PM, 'Christophe Vial' via qubes-users wrote:
> Hi all, I'm trying to use a usb wifi adapter (TP-Link archer T2U).
>
> the lsusb command returns
>
> Bus 002 Device 002: ID 148f:761a Ralink Technology, Corp. MT7610U
> ("Archer T2U" 2.4G+5G WLAN Adapter
>
> After some research I found the driver to install from
> https://github.com/ulli-kroll/mt7610u
>
> But the make command fails. I tried both in fedora-29 and debian9 vm,
> but in both cases I get the same error :
>
> make ARCH=x86_64 CROSS_COMPILE= -C
> /lib/modules/4.14.74-1.pvops.qubes.x86_64/build M=/home/user/src/mt7610u
> modules
> make[1]: Entering directory
> '/usr/lib/modules/4.14.74-1.pvops.qubes.x86_64/build'
> make[2]: *** No rule to make target
> '/home/user/src/mt7610u/os/linux/rt_profile.o', needed by
> '/home/user/src/mt7610u/mt7610u.o'.  Stop.
> make[1]: *** [Makefile:1527: _module_/home/user/src/mt7610u] Error 2
> make[1]: Leaving directory
> '/usr/lib/modules/4.14.74-1.pvops.qubes.x86_64/build'
> make: *** [Makefile:370: modules] Error 2
>
> Does anyone knows how to fix it ?
>
> And if not, any recommendations for some usb wifi adapters working out
> of the box ? I still have few days to return this one if I can't get it
> working.
>
>
>
>
>
>
>
> -- 
> 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 post to this group, send email to qubes-users@googlegroups.com
> .
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/qubes-users/Z0glcPBTr8ysTLe7JJX_K95S3BruPuVKAeqHIB2nPad1ANzOYUpWDhDmVTcRN56JaptfUPAKUySJ6iTNHxCy8e1AhKi4XnNkL_JRlh3kXq4%3D%40protonmail.com
> .
> For more options, visit https://groups.google.com/d/optout.

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/f475e830-8314-8dfe-f961-20df737f42c7%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

[qubes-users] Re: Qubes Os

[Frédéric Pierret]

Hi,

Even if I can answer the question in French, please ask to the list
first instead of me directly for such question as other will probably be
interested by your question.

Currently, as far as I know (please Andrew confirm), there is only
documentation in English.

French:

"De ce que je sais, il n'existe pas de documentation à l'heure actuelle
en français."

Best,

Frédéric

On 2/6/19 2:01 PM, Frédéric ASDRUBAL wrote:
> Bonjour,
> Est-il possible de trouver de la doc sur Qubes Os en français ?
> Merci
>
> _
> *Frédéric ASDRUBAL*
> /fasdru...@pm.me /
> Simple plan de Salut 
>
> Sent with ProtonMail  Secure Email.
>

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/c9dbf3ec-281e-1eb3-c884-73240e11a87a%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Trying to install Nvidia Driver

[Frédéric Pierret]

On 2/3/19 3:52 PM, Aly Abdellatif wrote:
> Thanks for your response @frederic
>
>
> Did you manage to make nouveau work ? By default I don't have a xorg.conf so 
> I don't know how to do it even when I close the X session and then in the 
> text console I write Xorg --configure -->  I have a seg fault error  and the 
> xorg.conf.new is not created.

Nouveau "should" work but over a lot of recent laptops with hybrid
graphics with NVIDIA, I always have to disable it (in grub add at the
end of the line containing 'rhgb quiet',  'nouveau.modeset=0').
Normally, you don't need any xorg.conf.

> Any idea to make the hdmi with an adapter(usb,usbC) work so it doesn't 
> connect to nvidia ?
I also tried to use an USB dock station with embedded HDMI port like
'IcyBox' but with sys-usb it is not possible. Without it, under a
classical Fedora, too much trouble with kernel module to load etc.
> I need the hdmi only for an appvm so I don't mind if it doesn't work on dom0 .

You could try GPU passthrough by attaching your discrete card to your VM
(there is a lot of topics on the qubes lists about it...good luck...)

I'm sorry for you that it is not easy. I had all these troubles and I
sold my previous laptop because I could not disable any GPU (integrated
or discrete), and my HDMI was only linked to my NVIDIA card. After
months of fighting, trying to debug upstream, building all the newer
kernels with related nouveau drivers commits, I just gave up and bought
a new one.

>
> P.S I forgot to mention : I'm on hybrid graphics
>
> Best regards 
> Aly Abdellatif
>
Best,

Frédéric


-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/d3a2bcd6-917f-64a6-3ba2-3348a281d4cd%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Trying to install Nvidia Driver

[Frédéric Pierret]

Hi,

I already went through all these problems. Even with rebuilding the
kernel with the proper option, it leads to other problems related to Xen
itself.

While NVIDIA is not working on the problem of using their drivers under
Xen, it is currently impossible (about 6 months I tried again and again)
to make it working.

Frédéric

On 2/3/19 2:07 PM, Aly Abdellatif wrote:
> Hi everyone,
>
> I'm actually using Qubes 4.0.1 on my Lenovo Thinkpad p52 in UEFI.
> To make it work I had to disable nouveau in the xen.cfg
> Now I'm trying to install NVIDIA Driver and I have several errors.
>
> I'm following https://www.qubes-os.org/doc/install-nvidia-driver/
>
> first I run ./NVIDIA-Linux-.run --ui=none 
> --no-x-check --keep --no-nouveau-check --no-kernel-module.
>
> I get an Installation interface and everything is fine.
> I can ask for a Xorg.conf .
>
> The problem is when I try to use "make" in NVIDIA/Kernels:
>
> make IGNORE_XEN_PRESENCE=1 CC="gcc -DNV_VMAP_4_PRESENT 
> -DNV_SIGNAL_STRUCT_RLIM" 
> I get this error :
>
> "Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install 
> libelf-dev, libelf-devel or elfutils-libelf-devel"
>
> then when I try to install one of them libelf-dev, libelf-devel or 
> elfutils-libelf-devel and I can only find elfutils-libelf-devel 
> with(enablerepo=unstable) 
>
> When I execute again the "make"
> after executing for several seconds : A lot of files are not found(object 
> files -> *.o).
>
> I read about the CONFIG_UNWINDER_ORC=y and that there's a way to make it work 
> without the elfutils-libelf-devel by rebuilding the kernel with 
> CONFIG_UNWINDER_FRAME_POINTER=y 
> But I don't know how and if it's a good idea.
>
>
> Of course I tried to reboot with the Xorg.conf(nvidia-xconfig)  but knowing 
> that it will not work and after entering my luks password , I have a black 
> screen so I can't log in into X, but I can login to  a text console (press 
> Ctrl-Alt-F2). So in the text console I uninstalled Nvidia and when I reboot 
> it everything went to normal without Nvidia driver and of course with nouveau 
> disabled(from the beginning).
>
> P.S: the HDMI is connected to the NVDIA GPU so I can't use it.
>
>
> Thanks in advance
>
> Best Regards
> Aly Abdellatif
>
>
>
>

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/eee85177-c66a-e592-28b5-74c3ca62f2ad%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Qubes 4.0.1 installer no grub menu

[Frédéric Pierret]

Check the post
https://groups.google.com/forum/#!msg/qubes-devel/pr8EzL7PjqE/DUFJbAItAQAJ

Frédéric

On 1/25/19 6:15 AM, gunnarmar...@gmail.com wrote:
> I can't get to the GRUB menu of the 4.0.1 installer, is there one? I can't 
> successfully install qubes without it.
>
> When I try to boot the installer from UEFI, some text appears at the top left 
> of the screen and then it goes black. The text says: 
> Xen 4.8.4 (c/s ) EFI loader 
> Using configuration file 'BOOTX64.cfg'"
>
> How do I get to the GRUB menu?
>

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/ffb7ed89-6ad2-d145-0fe3-7ae5f76edbac%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Re: Qubes 4.0.x - Linux kernel 4.19.15 package available in testing repository

[Frédéric Pierret]

The kernel in dom0 and VM is working fine, at least for me as I tested
it several days, but there is no reason now it should not.

For the bug with graphical boot we are looking at what is the problem.
It appears again if you try to boot directly on the linux kernel like
you would do in Fedora for example but it disappears in normal boot xen
kernel.

Frédéric

On 1/20/19 7:52 PM, seshu wrote:
> On Sunday, January 20, 2019 at 12:57:48 AM UTC, Marek Marczykowski-Górecki 
> wrote:
> Hi all,
>
> There is updated "kernel" package available in current-testing
> repository - it's a Linux long term support 4.19.x series, as an update
> over 4.14.x before. Since the upgrade switches to the next major LTS
> branch, I'll keep it in current-testing repository longer than usual 1-2
> weeks. This also applies to kernel package for VMs: kernel-qubes-vm.
> Please report new issues the usual way, at qubes-issues[1], or
> simply by replying here. In either case, please mark it clearly it
> happens after updating to 4.19, preferably including a link to the
> update:
> https://github.com/QubesOS/updates-status/issues/850
>
> 4.19.x kernel was already available as kernel-latest package for some
> time. Users of kernel-latest will see the update to 4.19.15 too, but
> kernel-latest soon will carry 4.20.x kernel version.
>
> [1] https://github.com/QubesOS/qubes-issues/issues
>
> > I noticed that there were kernel updates for the fedora 29 templates.
I did the update and the templates have been working well. Was this from
the Qubes team or an update that is from Fedora? > > Since the templates
and qubes are working fine, would that indicate the new kernel would
work fine on dom0? Just wondering if I should give it a try or not. >

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/0d110fd5-46b3-0588-e372-5c0610f4a977%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Re: Which parts of qubes-builder are guaranteed to work/supported?

[Frédéric Pierret]

On 1/23/19 8:21 AM, Foppe de Haan wrote:
> On Wednesday, January 2, 2019 at 10:35:37 PM UTC+1, Frédéric Pierret 
> (fepitre) wrote:
>> Le mercredi 2 janvier 2019 21:49:22 UTC+1, Achim Patzner a écrit :
>>> Hi!
>>>
>>>
>>> Is it worth creating issues if certain parts of the Builder tools do not 
>>> work (e. g. template-local-centos7 or template-local-fc29+xfce) which would 
>>> be creating things not in the Qubes distribution?
>>>
>>>
>>>
>>>
>>> Achim
>> What do you mean by 'parts'? The build of CentOS 7 and Fedora 29 with XFCE 
>> flavor works well. I did a build last week for both of them. Can you be more 
>> precise please?
>>
>> Frédéric
> OT, but could you briefly clarify the benefit of running the xfce flavor over 
> the generic f29 template?
>
Sure. I globally don't like gnome 3 tools/desktop. I prefer to use XFCE
tools/desktop directly in my AppVM. It's simple, flexible and easily
customizable. It's really a matter of taste. They are still some minor
UX tuning to do like default tray-icon of power management and
dnfdragora appearing but it's working fine and I'm using these flavors
since a very long time. So if there is also some feedback from other
users, it will help me to fix UX bugs I have not seen yet.

Frédéric


-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/8465237c-0b7a-fca3-b70c-c78ca6d22432%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] old version of xscreensaver

[Frédéric Pierret]

On 1/4/19 1:51 AM, unman wrote:
> On Fri, Jan 04, 2019 at 12:03:49AM +0100, Frédéric Pierret wrote:
>> We built the upstream package of xscreensaver in current-testing for
>> both Qubes 3.2 and 4.0.
>>
>> Welcome back to XFCE Chris :D !
>>
>> On 1/3/19 11:56 PM, Chris Laprise wrote:
>>> On 01/03/2019 02:00 PM, Achim Patzner wrote:
>>>> Am Mittwoch, den 02.01.2019, 20:42 -0800 schrieb pixel fairy:
>>>>> xscreensaver complains about being an old version. doubt this
>>>>> matters, but might scare some users.
>>>> There are worse problems with it (and some of them depend on X and the
>>>> hardware you're running on) which might also warrant finding something
>>>> different. I just have to find some time for constant rebooting of my
>>>> system to create a meaningful bug report.
>>>>
>>>> (To give you an idea: Imagine a machine (let's call it Lenovo P52) with
>>>> multiple GPUs where certain output channels are connected to one of the
>>>> GPUs only starting a screen server. If you connect your second monitor
>>>> to the right port the screen saver will not blank one of them if you
>>>> start X without an appropriately xorg.conf... And to make things worse
>>>> it also depends on the GPU you are using and the phase of the moon.)
>>> The bad screensaver is one of the reasons I switched back to KDE, and
>>> why I recommend it to other Qubes users. The default environment
>>> doesn't rise to the level of an every day functional desktop.
>>>
> Is this a thing now? Is Qubes going to provide updated packages for any
> other software? 
>
Absolutely not. It is just because it is annoying, at least, under XFCE.

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/ebca4da5-1017-e2fd-311d-213db323dab9%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] old version of xscreensaver

[Frédéric Pierret]

We built the upstream package of xscreensaver in current-testing for
both Qubes 3.2 and 4.0.

Welcome back to XFCE Chris :D !

On 1/3/19 11:56 PM, Chris Laprise wrote:
> On 01/03/2019 02:00 PM, Achim Patzner wrote:
>> Am Mittwoch, den 02.01.2019, 20:42 -0800 schrieb pixel fairy:
>>> xscreensaver complains about being an old version. doubt this
>>> matters, but might scare some users.
>>
>> There are worse problems with it (and some of them depend on X and the
>> hardware you're running on) which might also warrant finding something
>> different. I just have to find some time for constant rebooting of my
>> system to create a meaningful bug report.
>>
>> (To give you an idea: Imagine a machine (let's call it Lenovo P52) with
>> multiple GPUs where certain output channels are connected to one of the
>> GPUs only starting a screen server. If you connect your second monitor
>> to the right port the screen saver will not blank one of them if you
>> start X without an appropriately xorg.conf... And to make things worse
>> it also depends on the GPU you are using and the phase of the moon.)
>
> The bad screensaver is one of the reasons I switched back to KDE, and
> why I recommend it to other Qubes users. The default environment
> doesn't rise to the level of an every day functional desktop.
>

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/ca740da3-7f3f-698d-104e-f01a481b2928%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature