Re: [qubes-users] Re: HCL - Intel NUC10i7FNK

['Max Andersen' via qubes-users]

On 7/24/20 5:51 PM, Zhao Jx wrote:
>
> 在 2020年4月14日星期二 UTC+8上午2:07:16，Max Andersen写道：
>
> Hi everyone,
>
> NUC's are promising. 64GB memory with 1TB NVMe is acceptable for a
> Qubes installation and takes up zero space.
>
> Got 800x600 with the 4.19 kernel. no wifi. Upgraded kernel to
> 5.5.13-1 and got my 4K monitor working. no wifi. wifi device
> flapping for a few minutes, then stop. Hoping for some upgrades at
> some point.
>
> Runs current-testing repo.
>
> Sincerely
>
> Max
>
>
> Thanks for the post!
> I also have nuc 10i7fnk. but I have problems installing qubes OS 4.0. 
> I hope I can get answers from you.
> I Set legecy mode, security booting off, use USB stick to install OS.
> The following warning maseges is displayed when installing.
> "WARN anaconda:
> /usr/lib64/python3.5/site-packages/pyanaconda/pwpolicy.py:101:PendingDeprecationWarning:
> add_option is deprecated and will be removed in pykickstart-3.  Use
> add_argument instead.
>    op.add.option("--minlen",type="int")
> ..
> WARN anaconda.stdout:Not asking for VNC because we don't have a network
> ..
> WARN anaconda:X startup failed: Xorg exited with status 1
> WARN anaconda.stdout:X startup failed,aborting installation
> ERR anaconda.stdout:X startup failed, aboting installation"
>
> Do I miss setting something in bios or do I need to install the OS
> with DVD?
> Thanks a lot!


I recently moved to Xubuntu on this device, since QubesOS suddenly would
not boot anymore. Just hung and my 4K support dissapeared suddenly a few
weeks prior to that.

I am sorry it's such a hassle. Kali, Ubuntu, etc. has no issues with
wireless so it seems to be Qubes specific.

Good luck. You will need it.

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/2811d5dc-afc0-64b9-87e3-12b35c5fae94%40militant.dk.

[qubes-users] missing usb device support after update

['Max Andersen' via qubes-users]

Hi everyone,

I used my usb headphones the other day, but now they fail and some
update might have ruined it.

The error I receive when trying to attach the headphones is:
https://www.militant.dk/wp-content/uploads/2020/06/jabra-error.png

I could list the device with qvm-usb in dom0 and sys-usb, but nothing
while doing readlink /sys/bus/usb/devices. Nothing is in there as I
believe it says here there should
be:https://www.qubes-os.org/doc/usb-devices/

Any help appreciated

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/a12ee9a9-de8f-ccfe-3825-0d34aba35a4a%40militant.dk.

[qubes-users] Missing wifi on Intel NUC10i7FNK

['Max Andersen' via qubes-users]

Hi everyone,

Tried Live Ubuntu on my IntelNUC10i7FNK, and wireless and bluetooth
worked. Cant get the wifi to work under Qubes, though. Network Manager
applet flaps.

Integrated wireless model is: Intel® Wi-Fi 6 AX201
(https://www.intel.com/content/www/us/en/products/boards-kits/nuc/kits/nuc10i7fnh.html)

Any specific updates to try and resolve the wifi issue?

Video here: https://photos.app.goo.gl/DQFJvpibzCRES3gJ6

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/8fd1c26f-3443-e843-c73e-261d62b39c9f%40militant.dk.

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

['Max Andersen' via qubes-users]

On 4/22/20 11:36 PM, Frédéric Pierret wrote:
>
> 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 ?

Using testing repo works:

[user@fedora-31 ~]$ sudo dnf clean all
45 files removed
[user@fedora-31 ~]$ sudo dnf update
Fedora Modular 31 -
x86_64  
   
2.3 MB/s | 5.2 MB 00:02   
Fedora Modular 31 - x86_64 -
Updates 
  
1.5 MB/s | 4.0 MB 00:02   
Fedora 31 - x86_64 -
Updates 
  
5.5 MB/s |  24 MB 00:04   
Fedora 31 -
x86_64  
   
8.4 MB/s |  71 MB 00:08   
Qubes OS Repository for VM
(updates)   

143 kB/s | 128 kB 00:00   
skype
(stable)
 
5.8 kB/s | 3.7 kB 00:00   
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

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

['Max Andersen' via qubes-users]

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.fc31  updates  32 k
 pulseaudio-qubes  x86_64  
4.0.26-1.fc31   qubes-vm-r4.0-current    25 k

Transaction Summary
==
Skip  5 Packages

Nothing to do.
Complete!
[user@fedora-31 ~]$

Then I try the recomended action 

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

['Max Andersen' via qubes-users]

Den 17. apr. 2020 kl. 09.40 skrev Frédéric Pierret 
:
>> 
> 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.

Working like a charm, thank you .

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/4A4EC77A-7BCE-4850-88D7-E9F45EC12C8E%40militant.dk.

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

['Max Andersen' via qubes-users]

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

The builder.conf contains:

vim: ft=make

VERBOSE ?= 2

BACKEND_VMM ?= xen

GIT_BASEURL ?= https://github.com
GIT_PREFIX ?= QubesOS/qubes-

RELEASE ?= 4.0

DIST_DOM0 ?= fc25
DISTS_VM ?=

COMPONENTS = \
    installer-qubes-os \
    linux-yum \
    linux-kernel \
    builder-rpm

BUILDER_PLUGINS ?= builder-rpm

USE_QUBES_REPO_VERSION = $(RELEASE)

INSTALLER_KICKSTART=/home/user/qubes-src/installer-qubes-os/conf/iso-full-online.ks
USE_QUBES_REPO_TESTING=1
BRANCH_installer_qubes_os=release4.0
URL_linux_kernel=https://github.com/fepitre/qubes-linux-kernel
BRANCH_linux_kernel=kernel-5.6


Thank you very much for your help. I really appreciate it.

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/8e51dca8-61e0-128b-ad12-427334b8363c%40militant.dk.


signature.asc
Description: OpenPGP digital signature

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

['Max Andersen' via qubes-users]

On 4/16/20 8:44 PM, Frédéric Pierret wrote:
>> 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.

I cloned a new machine from the newest fedora-template-31, so I know
what is needed in the newest build.

Running make install-deps. installing :

Installed:
  annobin-8.78-3.fc31.x86_64  
createrepo_c-0.15.5-1.fc31.x86_64  
createrepo_c-libs-0.15.5-1.fc31.x86_64  
drpm-0.4.1-1.fc31.x86_64
dwz-0.12-11.fc31.x86_64  
efi-srpm-macros-4-3.fc31.noarch 
  elfutils-0.179-1.fc31.x86_64
fonts-srpm-macros-2.0.3-1.fc31.noarch  
fpc-srpm-macros-1.2-2.fc31.noarch   
gdb-minimal-8.3.50.20190824-30.fc31.x86_64  
ghc-srpm-macros-1.5.0-1.fc31.noarch  
gnat-srpm-macros-4-10.fc31.noarch   
  go-srpm-macros-3.0.8-4.fc31.noarch  
libmodulemd-2.9.1-1.fc31.x86_64
nim-srpm-macros-3-1.fc31.noarch 
ocaml-srpm-macros-5-6.fc31.noarch   
openblas-srpm-macros-2-6.fc31.noarch 
patch-2.7.6-11.fc31.x86_64  
  perl-Digest-SHA-1:6.02-440.fc31.x86_64  
perl-srpm-macros-1-33.fc31.noarch  
python-srpm-macros-3-54.fc31.noarch 
python3-sh-1.12.14-13.fc31.noarch   
qt5-srpm-macros-5.13.2-1.fc31.noarch 
redhat-rpm-config-143-1.fc31.noarch 
  rpm-build-4.15.1-1.fc31.x86_64  
rpm-sign-4.15.1-1.fc31.x86_64  
rpmdevtools-8.10-9.fc31.noarch  
rust-srpm-macros-13-1.fc31.noarch   
xemacs-filesystem-21.5.34-34.20190323hgc0ed7ef9a5a1.fc31.noarch  
zstd-1.4.4-1.fc31.x86_64  

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

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

['Max Andersen' via qubes-users]

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
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?

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/d05519f3-5234-8eaf-ecdc-4b943060c1fd%40militant.dk.


signature.asc
Description: OpenPGP digital signature

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

['Max Andersen' via qubes-users]

> 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)?

I would love to build it on my own, so I can do it in the future, since my 
hardware is so new

Thank you very much
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/1C62A5AB-20E7-4C68-BA0B-80F4E6B3C64B%40militant.dk.

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

['Max Andersen' via qubes-users]

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/e1f5bbea-d78a-80a7-fd58-bc3349efbf64%40militant.dk.

[qubes-users] HCL - Intel NUC10i7FNK

['Max Andersen' via qubes-users]

Hi everyone,

NUC's are promising. 64GB memory with 1TB NVMe is acceptable for a Qubes
installation and takes up zero space.

Got 800x600 with the 4.19 kernel. no wifi. Upgraded kernel to 5.5.13-1
and got my 4K monitor working. no wifi. wifi device flapping for a few
minutes, then stop. Hoping for some upgrades at some point.

Runs current-testing repo.

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/dad871c9-9572-c0db-ce64-1e7b3c0345ae%40militant.dk.


Qubes-HCL-Intel_R__Client_Systems-NUC10i7FNK-20200413-194233.cpio.gz
Description: application/gzip


Qubes-HCL-Intel_R__Client_Systems-NUC10i7FNK-20200413-194233.yml
Description: application/yaml

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

['Max Andersen' via qubes-users]

> Den 28. mar. 2020 kl. 19.38 skrev Ilpo Järvinen 
> :
> 
> On Sat, 28 Mar 2020, max via qubes-users wrote:
> 
>> Hi everyone,
>> 
>> Any help appreciated.
>> 
>> I managed to install a Qubes 4.0.3 on an Intel NUC10FNK. No VM's can start
>> due to an error like: Internal error: Unable to reset PCI device
>> :00:1f:6:no FLR, PM rset or bus reset available.
> 
> Test setting permissive mode for that PCI device.

Hi Ilpo,

I tried your recommendation, and now it starts the vm, but it still has no 
network, since the driver propably only resides in newer kernels which dom0 
does not have. (it says sys-net has no network cards)

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

I tried readlink /sys/bus/usb/devices/usb1

It gave :00:14.0/usb1

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

Any ideas, maybe on getting kernel 5 on qubes?
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/C6333494-4A9C-4197-A70D-093A0ECAA72A%40militant.dk.

Re: [qubes-users] Firefox critical update not updating my latest fedora-30

['Max Andersen' via qubes-users]

On 1/11/20 11:25 PM, Lorenzo Lamas wrote:
> You can update from testing repo: sudo dnf update firefox 
> —enablerepo=updates-testing
>
> When newer fedora versions are released, updates for older versions are 
> usually slower. The comments on the update also show negative feedback which 
> is why it has not been pushed to stable automatically. However, there are no 
> problems if your system is up to date with latest stable nss and nspr.

Instead of asking for the repository, I used the advisory. That usually
works, but actually didn't because of me, having an entry in my repo
file, to ensure I always get the newest KeePassXC from testing repo, if
it exists. It apparently denies everything else, so I need to include it
in the file.

includepkgs=keepassxc. I had to add firefox in this case.

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/192aad8b-fae2-e4fd-fa3b-2a770dbf3c53%40militant.dk.

Re: [qubes-users] Re: 35c3 session: Introduction to Qubes OS

['Max Andersen' via qubes-users]

>>> During 35th Chaos Communication Congress in Leipzig we'll be organizing an
>>> introductory session to Qubes OS:
>>> 
>>> https://events.ccc.de/congress/2018/wiki/index.php/Session:Introduction_to_Qubes_OS
>> 
>> Was it recorded, so others can view it later? I cannot find it here: 
>> https://media.ccc.de/c/35c3 ?
> 
> AFAIK it wasn't. It was a „self-organised session”, so there was no camera
> manned by CCC staff, and no-one else would record since on the Congress the
> recording people is generally frowned upon by attendees and organisers alike.

Thank you for the answer. 

If you feel the urge to make a similar session to other users/backers of 
qubes-os, thank you in advance. Like Micah Lee’s presentation, I actually 
learned something new, and was looking forward to it.

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 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/5227D155-5075-43BB-BC7A-A34E3676EB78%40militant.dk.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] HCL - Purism Librem 13v2

['Max Andersen' via qubes-users]

Major issues with Coreboot, crashes, etc.

-
https://forums.puri.sm/t/building-coreboot-from-source-official-script/1264/113

- https://github.com/QubesOS/qubes-issues/issues/3753

After several updates, install went fine. Now only minor issues:

Rattling fan noise, due to bios version. Will maybe get fixed:
https://militant.dk/Ny%20optagelse%203.m4a?dl=0

Pipe not recognized properly:
To make change permanent a workaround is required:
https://forums.puri.sm/t/keyboard-layout-unable-to-recognize-pipe/2022/3?u=max4

Having issues with danish keyboard layout and the '@' sign. Also having
issues with keyboard layout in qubes has to be default and not danish,
since copy paste fails to work.

Can not recommend this laptop for Qubes usage. I even ordered it with
qubes installed, but PureOS was installed and I had a battle to get
things right. Took forever and is actually not worth it, in my book.
Read about it here, if you like:
https://www.militant.dk/2018/02/22/ordering-a-purism-librem-13v2-to-run-qubes-4-0rc4/

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 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/2c7302dc-e925-60ba-3ea5-f8a2e0762df7%40militant.dk.
For more options, visit https://groups.google.com/d/optout.


Qubes-HCL-Purism-Librem_13_v2-20180804-220810.yml
Description: application/yaml


signature.asc
Description: OpenPGP digital signature

[qubes-users] Assigning USB to VM fails

['Max Andersen' via qubes-users]

I have trouble attaching my USB RJ45 adapter. I get the following error :

[Max@dom0 ~]$ qvm-usb -a lokal-belkin sys-usb:3-2
ERROR: Device attach failed: No device info received, connection failed,
check backend side for details
[Max@dom0 ~]$

It is properly attached to sys-usb:

[Max@dom0 ~]$ qvm-usb
sys-usb:2-1.8    5986:0535 Generic_Lenovo_EasyCamera_200901010001
sys-usb:3-2    0b95:7720 ASIX_Elec._Corp._AX88x72A_10FD4D
sys-usb:2-1.1    046d:c52f Logitech_USB_Receiver
sys-usb:2-1.7    04f3:016f ELAN_Touchscreen
sys-usb:2-1.6    2047:0855 Invensense_Lenovo_Yoga_31F3806F24001100
sys-usb:2-1.4    8087:07dc 8087_07dc
[Max@dom0 ~]$

I documented the behaviour earlier for future reference here:
https://www.militant.dk/2018/02/20/add-usb-network-adapter-to-a-specific-qube-to-configure-router-in-qubes-3-2/

It seems it has worked and now it doesn't. Users might have had similar
issues before

https://github.com/QubesOS/qubes-issues/issues/3026
https://github.com/QubesOS/qubes-issues/issues/3272

Any ideas?

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 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/b2a84d72-a1da-107c-d52a-c1be4bd73b33%40militant.dk.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Qubes canary over due...

['Max Andersen' via qubes-users]

On 03/15/2018 08:06 PM, Marek Marczykowski-Górecki wrote:
> On Thu, Mar 15, 2018 at 11:37:29AM -0700, code9n wrote:
> > ...but only by a day  (see Qubes canary #14 -
> https://github.com/QubesOS/qubes-secpack/blob/master/canaries/canary-014-2017.txt)
>
> There is new one, in usual place:
> https://github.com/QubesOS/qubes-secpack/blob/master/canaries/canary-015-2018.txt

Shouldn't it be news since Canary #14 was announced in the news section?:
https://www.qubes-os.org/news/

And it's also missing here in the overview of canaries:
https://www.qubes-os.org/security/canaries/

But it's here in github, so maybe the other pages, should autoupdate or
something?:
https://github.com/QubesOS/qubes-secpack/tree/master/canaries

Is it only released on github in the future?

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 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/f91f0081-1005-6d02-712f-7e0641f4641f%40militant.dk.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Locked screen message "This version of XScreenSaver is very old! Please upgrade!"

['Max Andersen' via qubes-users]

On 03/05/2018 08:09 PM, Unman wrote:
> On Mon, Mar 05, 2018 at 07:32:47PM +0100, 'Max Andersen' via qubes-users 
> wrote:
>> Hi everyone,
>>
>> Qubes 3.2 displays the message "This version of XScreenSaver is very
>> old! Please upgrade!", when the screen is locked with Xscreensaver 5.36
>>
>> I haven't seen an update to Dom0 when running sudo qubes-dom0-update, so
>> is this just annoying or an actual issue?
>>
>> Sincerely
>>
>> Max
>>
>>
> It's just a reflection of the fact that dom0 is still using fedora 23,
> which is long past eol. SO no updates for the screensaver.
> Is it an issue?
> I don't think there have been advisories since 34, so 5.36 should be fine.

Didn't think so either, but why did I get the message in the first
place? Does it check for newer versions or is it just a timer ?

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 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/97a5d8bc-87e3-8dba-288e-432ce2c770d7%40militant.dk.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Locked screen message "This version of XScreenSaver is very old! Please upgrade!"

['Max Andersen' via qubes-users]

Hi everyone,

Qubes 3.2 displays the message "This version of XScreenSaver is very
old! Please upgrade!", when the screen is locked with Xscreensaver 5.36

I haven't seen an update to Dom0 when running sudo qubes-dom0-update, so
is this just annoying or an actual issue?

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 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/294ac4df-58c1-f61c-9f4c-d1e67c55341d%40militant.dk.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Can I hope to run Qubes OS on Macbook Air 2013

['Max Andersen' via qubes-users]

On 03/02/2018 06:12 PM, andrewashbac...@gmail.com wrote:
> On Wednesday, January 13, 2016 at 5:15:06 AM UTC-8, mariusz...@gmail.com 
> wrote:
>> Same as topic name. I am currently running mac os with heavy virtual 
>> machines usage to get more security/privacy. I will probably switch to linux 
>> soon but since i plan on using a lot of one time use VMs or even whonix i 
>> would rather get as secure host as possible. So i figured why not use Qubes 
>> OS since i already do everything manually.
>>
>> If not mba what high end ultrabook would you recommend ?
> Have you seen the Purism Libre laptops?  https://puri.sm/products/librem-13/

Having a Lenovo X1 Carbon 16GB and 256SSD, a macbook air 8GB 256SSD, a
purism 13v2 with 512nvme and 16gb memory and a Lenovo Yoga 2 pro 8GB adn
256GB SSD, I must say, that the purism is bought with kill switches in
mind. It's more expensive, heavier and thicker.

If Open Source BIOS and kill switches is secondary, then The Lenovo's
are both hard rocking Qubes machines(and the qubes developer team uses
the X1 Carbon). I've had a few issues with the Librem(bios, fan's ,etc),
so be clear about your needs before purchase. If the Purism concept
appeals to you, go for it. If not, don't.

I even bought the Librem5 phone and await its arrival in a year or so,
but I guess I'm just a fanboy.

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 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/ecd543b3-fb11-008a-1bce-fd94e88e4f6a%40militant.dk.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Kali-rolling issue: kali-defaults collides with qubes-core-agent

['Max Andersen' via qubes-users]

Hi,

I get an error when installing Kali rolling using the Qubes-guide : 
https://www.qubes-os.org/doc/pentesting/kali/#create-a-kali-linux-rolling-template


The error comes when installing kali-defaults, which seems to collide 
with qubes-core-agent:


user@Kali-Rolling:~$ sudo apt --fix-broken install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following additional packages will be installed:
  kali-defaults
The following NEW packages will be installed:
  kali-defaults
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
1435 not fully installed or removed.
Need to get 0 B/1,545 kB of archives.
After this operation, 2,722 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 304913 files and directories currently installed.)
Preparing to unpack .../kali-defaults_2018.2.0_all.deb ...
Leaving 'diversion of /etc/skel/.bashrc to /etc/skel/.bashrc.original by 
kali-defaults'
Leaving 'diversion of 
/etc/xdg/xfce4/xfconf/xfce-perchannel-xml/xsettings.xml to 
/etc/xdg/xfce4/xfconf/xfce-perchannel-xml/xsettings.xml.original by 
kali-defaults'

Unpacking kali-defaults (2018.2.0) ...
dpkg: error processing archive 
/var/cache/apt/archives/kali-defaults_2018.2.0_all.deb (--unpack):
 trying to overwrite '/etc/dconf/profile/user', which is also in 
package qubes-core-agent 4.0.20-1+deb9u1

dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/kali-defaults_2018.2.0_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
user@Kali-Rolling:~$

I've tried forcing to no avail. Even trying to uninstall 
qubes-core-agent, but It seems to be demanding more packages to be 
uninstalled, than I might think maybe necessary.


user@Kali-Rolling:~$ sudo apt-get remove qubes-core-agent
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
 kali-desktop-common : Depends: kali-defaults but it is not going to be 
installed
 qubes-core-agent-networking : Depends: qubes-core-agent but it is not 
going to be installed
 qubes-gui-agent : Depends: qubes-core-agent (>= 3.0.14) but it is not 
going to be installed
 qubes-input-proxy-sender : Depends: qubes-core-agent (>= 3.0.25) but 
it is not going to be installed
 qubes-vm-dependencies : Depends: qubes-core-agent but it is not going 
to be installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages 
(or specify a solution).

user@Kali-Rolling:~$


Any ideas?

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 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/f8c98e44-918d-baed-0a7f-88d66a39b197%40militant.dk.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] removing fedora-26 template from Qubes ?

['Max Andersen' via qubes-users]

> Den 27. feb. 2018 kl. 06.16 skrev ThierryIT :
> 
> Hi,
> How to properly remove this template ?

> user@dom0 ~]$ sudo dnf remove qubes-template-fedora-23
> Thx
> 
> -- 
> 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/8b630b1c-3c72-4ac7-a2d2-f714e5161434%40googlegroups.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/FC933BCC-A43F-4990-9A9E-4FAEFC3A1D94%40militant.dk.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Qubes 3.2: Network doesn't connect automatically with hidden wifi

['Max Andersen' via qubes-users]

On 02/22/2018 08:09 AM, Yuraeitha wrote:
> On Thursday, February 22, 2018 at 3:20:32 AM UTC+1, Max Andersen wrote:
>> Sendt fra min iPhone
>>
>>> Den 21. feb. 2018 kl. 21.23 skrev Yuraeitha :
>>>
 On Wednesday, February 21, 2018 at 8:13:44 PM UTC+1, Max Andersen wrote:
 Hi,

 I've noticed that after disabling SSID broadcast on my wifi, I need to
 disable and reenable my network, every time I login.

 I've tried to describe it in detail here: https://militant.dk/?p=174

 Maybe anyone has ideas to resolve this?

 Sincerely

 Max
>>> Think of it this way. Hackers love challenges. By the act of trying to hide 
>>> that way, you're giving a hacker a challenge. He or she, may even get a 
>>> kick out of showing you how insecure your network really is by messing with 
>>> you, simply because you do something that has no effect, such as hiding the 
>>> SSID. 
>>>
>>> You're either giving them a challenge to work on, or it might even be 
>>> schadenfreude https://en.wikipedia.org/wiki/Schadenfreude
>>>
>>> Tbh, you're better off just enabling SSID again.
>> So, the solution is actually security by nudging?
>>
>> Don’t do it, or we will make qubes network manager crash to nudge you back :)
>>
>> I’d bet my network is not that interesting for a wardriving kali hacker, but 
>> it still seem like a bug that I would love to get fixed.
>>
>> Sincerely
>> Max
> hehe, well you can probably find a hack to get what you need, for example 
> making a script that automatically repairs your connection at boot. I'm not 
> seeing the particular details atm, but it seems like it might just work. I'm 
> no expert though.
>
> The bug itself is likely not related to Qubes btw. It's very likely that it 
> belongs upstream in Fedora, and even in Fedora the Network Manager may come 
> from up further upstream. Even if you track down the Network Manager 
> developers, the piece of code they're using may come even further upstream, 
> and even there, it may yet again come from another upstream. This is usually 
> called upstream/downstream movements. Linux is like lego, many pieces comes 
> elsewhere, and no one have the resources to do everything. If they tried, 
> they'd drawn in work to do. And if they change upstream code, then it becomes 
> really, really messy when new updates arrive from upstream, and you need to 
> incorporate the code changes you made to all your packages every time a new 
> update arrives. To make matters worse, it's not their code, so it can be hard 
> to find your way around and find the right places in the code, wasting a lot 
> of time. And then there is the aspect that security can be tough to enforce 
> if you spread out too far. You have to trust other developers to some extent, 
> otherwise you'd spend all your time looking for security flaws and never get 
> anything else done.
>
> The closer to you get to the source upstream, the higher your odds are that a 
> developer will track it down and report the issue. Qubes is pretty far away 
> from the source, and operates on a more broad level of coding 
> (macro-perspective, piecing a lot of different codes and mechanism together). 
> You can kind of look at Qubes as an infrastructure, and not an organ like 
> operation systems are. Qubes in and on itself is not an operation system, 
> it's a network or "mesh" of operation systems. So this issue has to be 
> tracked down.
>
> It's also an issue if developers have to spend time reporting all the bugs to 
> each others, they'd spend a huge amount of time on that. A single bug may not 
> seem like wasting a lot of time, but it piles up. Say one spends 20 dollars, 
> it's pennies, not a lot of money (well at least in some countries). Now 
> imagine if you had to pay for 1.000 pieces, then it becomes 20.000 dollars, 
> and it suddenly became very expensive. 
>
> That's why developers have to prioritize their time and focus, because if 
> they do not, they'd drawn in everything else. Qubes top priority is security. 
> I doubt they will be looking into this bug.
>
> But the community can help, by reporting the bug closer to the source, or at 
> the actual source. This way the bug can get fixed, and it may go faster too 
> (not always though) if the actual developers behind it are reported about it 
> directly. If the community does this, it'll save all developers a huge amount 
> of time. So this kind of bug, may be a matter of tracking down the actual 
> Network Manager developers. 
>
> But if you'd like a fix though, a sort of "hack", then as mentioned earlier, 
> a script may work out. But before trying to look into it, I'll ask if this is 
> something you need? or do you prefer to wait for a real bug fix? (It can take 
> a long time for what may be deemed minor bugs, and also requires someone 
> reporting it at the appropriate issue-tracker).
>
> I may not be able to make such a script though, I'm only an average Linux 
> user. But I'll 

Re: [qubes-users] Re: Qubes 3.2: Network doesn't connect automatically with hidden wifi

['Max Andersen' via qubes-users]

Sendt fra min iPhone

> Den 21. feb. 2018 kl. 21.23 skrev Yuraeitha :
> 
>> On Wednesday, February 21, 2018 at 8:13:44 PM UTC+1, Max Andersen wrote:
>> Hi,
>> 
>> I've noticed that after disabling SSID broadcast on my wifi, I need to
>> disable and reenable my network, every time I login.
>> 
>> I've tried to describe it in detail here: https://militant.dk/?p=174
>> 
>> Maybe anyone has ideas to resolve this?
>> 
>> Sincerely
>> 
>> Max
> 
> Think of it this way. Hackers love challenges. By the act of trying to hide 
> that way, you're giving a hacker a challenge. He or she, may even get a kick 
> out of showing you how insecure your network really is by messing with you, 
> simply because you do something that has no effect, such as hiding the SSID. 
> 
> You're either giving them a challenge to work on, or it might even be 
> schadenfreude https://en.wikipedia.org/wiki/Schadenfreude
> 
> Tbh, you're better off just enabling SSID again.

So, the solution is actually security by nudging?

Don’t do it, or we will make qubes network manager crash to nudge you back :)

I’d bet my network is not that interesting for a wardriving kali hacker, but it 
still seem like a bug that I would love to get fixed.

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 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/CE8AE914-924E-4A56-B1F6-1D7EF649472F%40militant.dk.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Qubes 3.2: Network doesn't connect automatically with hidden wifi

['Max Andersen' via qubes-users]

Hi,

I've noticed that after disabling SSID broadcast on my wifi, I need to
disable and reenable my network, every time I login.

I've tried to describe it in detail here: https://militant.dk/?p=174

Maybe anyone has ideas to resolve this?

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 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/e8818af2-c4f9-7027-16a4-f55dcd1c410f%40militant.dk.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] cannot remove/create VM exists and doesn't exist [SOLVED]

['Max Andersen' via qubes-users]

On 01/01/2018 01:40 PM, Max Andersen wrote:
>
> On 01/01/2018 11:52 AM, awokd wrote:
>> On Mon, January 1, 2018 10:41 am, Max Andersen wrote:
>>> Hi awokd
>>>
>>>
>>>> Den 1. jan. 2018 kl. 11.32 skrev awokd <aw...@danwin1210.me>:
>>>>
>>>>
>>>>> On Mon, January 1, 2018 4:36 am, 'Max Andersen' via qubes-users
>>>>> wrote:
>>>>>
>>>>>
>>>>>
>>>>> libvirtError: operation failed: domain 'win7' already exists with
>>>>> uuid 
>>>>>
>>>> Sometimes a reboot clears up discrepancies like that for me.
>>>>
>>> I’m sorry, I tried that, after restarting the libvirtd service and that
>>> didn’t work.
>>>
>> Can try to rename Win7 to Win7b. There is also a "virsh destroy" but
>> ordinarily you shouldn't have to use that.
> I cannot rename or do a simple list with qvm-prefs. Only with virsh, so
> there must be a discrepancy between the 2.
>
> qvm-ls shows no win7, but virsh does.
>
> Sincerely
> Max
I started up the virsh shell, typed 'undefine win7', and started all
over. That worked.

Thank you for your efforts, awokd

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 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/1aaded14-36e1-08f1-88ea-5268d0afc196%40militant.dk.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] cannot remove/create VM exists and doesn't exist

['Max Andersen' via qubes-users]

On 01/01/2018 11:52 AM, awokd wrote:
> On Mon, January 1, 2018 10:41 am, Max Andersen wrote:
>> Hi awokd
>>
>>
>>> Den 1. jan. 2018 kl. 11.32 skrev awokd <aw...@danwin1210.me>:
>>>
>>>
>>>> On Mon, January 1, 2018 4:36 am, 'Max Andersen' via qubes-users
>>>> wrote:
>>>>
>>>>
>>>>
>>>> libvirtError: operation failed: domain 'win7' already exists with
>>>> uuid 
>>>>
>>> Sometimes a reboot clears up discrepancies like that for me.
>>>
>> I’m sorry, I tried that, after restarting the libvirtd service and that
>> didn’t work.
>>
> Can try to rename Win7 to Win7b. There is also a "virsh destroy" but
> ordinarily you shouldn't have to use that.

I cannot rename or do a simple list with qvm-prefs. Only with virsh, so
there must be a discrepancy between the 2.

qvm-ls shows no win7, but virsh does.

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 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/ef665cec-2311-5be6-8547-15419fbc664e%40militant.dk.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] cannot remove/create VM exists and doesn't exist

['Max Andersen' via qubes-users]

Hi awokd

> Den 1. jan. 2018 kl. 11.32 skrev awokd <aw...@danwin1210.me>:
> 
>> On Mon, January 1, 2018 4:36 am, 'Max Andersen' via qubes-users wrote:
>> 
>> 
>> libvirtError: operation failed: domain 'win7' already exists with uuid
>> 
> 
> Sometimes a reboot clears up discrepancies like that for me.

I’m sorry, I tried that, after restarting the libvirtd service and that didn’t 
work.

Thank you for your reply

Soncerely
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 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/51441858-AD36-414F-840C-52046DE0E02A%40militant.dk.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] cannot remove/create VM exists and doesn't exist

['Max Andersen' via qubes-users]

Hi everyone,

I created a win7 HVM as per instructions here:

https://github.com/QubesOS/qubes-issues/issues/2488

And it installed nicely. After applying windows updates and
qubes-windows-tools, the VM wouldn't start, so I thought I'd remove it
and recreate it all over again, but I get an error:

libvirtError: operation failed: domain 'win7' already exists with uuid 

I can see it with "sudo virsh list -all" a it shows:

- win7  Shut off

Any ideas on how to remove it since a new remove syas it isn't there
anymore?

qvm-remove win7
A VM with the name 'win7' does not exist in the system

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 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/9a901661-56dd-d80a-5235-26a3fec897d7%40militant.dk.
For more options, visit https://groups.google.com/d/optout.