Re: [qubes-users] MS Office 365 in Qubes

2021-05-13 Thread 'taran1s' via qubes-users




Sven Semmler:



need to use MS Office 365


Condolences.


Thank you, taken sadly.




workaround other than necessity to install whole Windows OS


https://www.codeweavers.com/compatibility/crossover/microsoft-office-365

WIN7 or WIN10 [...] point me to a how to guide? 


https://github.com/elliotkillick/qvm-create-windows-qube

But if Office 365 Suite are the only windows apps you need I'd go for 
CrossOver.





I believe that I could possibly to get out with the MS Office 2019 
instead of Office 365. Would this change the equation and make things 
easier?


--
Kind regards
taran1s

gpg: 12DDA1FE5FB39C110F3D1FD5A664B90BD3BE59B3

--
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/1119c0e0-cb0f-dcd3-c9b3-11e56b796a6d%40mailbox.org.


[qubes-users] MS Office 365 in Qubes

2021-05-13 Thread 'taran1s' via qubes-users
I am using Qubes as my main OS and now it seems that due to my work 
assignment, I will need to use MS Office 365 and I would like to keep 
using my Qubes laptop.


I will need to use the MS Office 365 ideally with/without the following 
features:


- no need to have internet connection
- no need to have win apps other than the MS Office 365 are needed now
- need to copy and paste text in between win-AppVMs and non-win-AppVMs
- need to file sharing between win-AppVMs and non-win-AppVMs (copy and move)
- need to ideally be able to open the MS Office 365 files in various 
separate AppVMs, but it is not a killer and I can live without it if it 
complicates the situation too much.


My question is, if there is some workaround other than necessity to 
install whole Windows OS in my Qubes.


If the Windows OS installation is a necessity in this case, would you 
consider the WIN7 or WIN10 as better, less troublesome option? Could you 
point me to a how to guide? There is this guide 
https://www.qubes-os.org/doc/windows/. Is there any other one you would 
propose for this case?


--
Kind regards
taran1s

--
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/67f41fe8-af95-f3eb-ecec-ce0a59d2091c%40mailbox.org.


Re: [qubes-users] How do I install trezor-bridge on a Qubes system without a sys-usb qube e

2021-05-12 Thread 'awokd' via qubes-users

unman:


Is it unusual to have more than one controller on a laptop? Venerable
old Thinkpads had 2 or 3, and you could easily keep one for dom0 and the
other(s) for sys-usb purposes.


From what I hear/have seen, newer laptops often only have one, in the 
continued pursuit of saving a few pennies at the customer's expense. 
Maybe I've only heard of them because of that issue, however.


--
- 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/3b44817c-dc66-daeb-efe2-d887ee31fafa%40danwin1210.me.


Re: [qubes-users] Dom0 update error (Converting database from bdb to sqlite backend)

2021-05-12 Thread 'awokd' via qubes-users

load...@gmail.com:

On Monday, May 10, 2021 at 10:06:10 PM UTC+3 awokd wrote:



Unfortunately the '*/var/lib/qubes/dom0-updates/*' completely empty in
sys-firewall.
  


If it still fails, you might want to create a fresh sys-firewall, or

change your UpdateVM to point to a different AppVM.



I tried with sys-net and also I tried with new netvm, but still have this
error.


In dom0, check the files in /etc/yum.repos.d for the problem value. 
Could possibly be copying them from there.


--
- 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/b68deb60-6bed-479b-d063-2b8f32dbfc93%40danwin1210.me.


[qubes-users] DNS issues: servfail on selected subdomains, Qubes modifying DNS replies by stripping IPv6?

2021-05-11 Thread 'qtpie' via qubes-users
I have a very annoying issue with DNS recently. I'm using the standard 
DNS device and servers provided by my internetprovider which runs a full 
dual-stack IPv4/6. Other non-qubes devices have no issues. I think this 
might be a Qubes bug but I want to ask for help first to rule out an 
error on my side.


Selected domainnames (all subdomains, eg www.qubes.org, so not 
qubes.org) get a SERVFAIL when trying to resolve them within 
applications, and on the commandline with 'host' and 'nslookup'. 
Strangely enough, 'dig' has no issues, (querying the same default 
resolver ip of course). At times, the domainname will resolve inside 
sys-net and certain app-vm's, and not in another app-vm. At other times, 
it resolves nowhere. When quering resolvers directly (like my isp's 
resolvers or 1.1.1.1) the issue does not occur.


What can be happening here? One of the only consistent hints I found is 
that Qubes does not seem to pass the full nslookup response from sys-net 
to the appvm (compare nslookup examples below). My router gives a 
servfail when quering it via ipv4, nslookup then tries it's ipv6 
address, where it does get a reply, but this reply is not passed to the 
appvm. The servfail might be an ipv6 issue or an issue with my router, 
but I think still Qubes should pass the full response, right?



some affected domainnames:
www.duckduckgo.com
www.startpage.com
textsecure-service.whispersystems.org



user@chat-1:~$ host -v www.startpage.com
Trying "www.startpage.com"
Host www.startpage.com not found: 2(SERVFAIL)
Received 35 bytes from 10.139.1.2#53 in 2 ms

-

user@chat-1:~$ nslookup  www.startpage.com
;; Got SERVFAIL reply from 10.139.1.1, trying next server
Server:        10.139.1.2
Address:    10.139.1.2#53

** server can't find www.startpage.com: SERVFAIL



user@sys-net:~$ host -v www.startpage.com
Trying "www.startpage.com"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22135
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www.startpage.com.        IN    A

;; ANSWER SECTION:
www.startpage.com.    2393    IN    CNAME    startpage.com.
startpage.com.        10    IN    A    145.131.132.72

Received 65 bytes from 192.168.0.1#53 in 4 ms
Trying "startpage.com"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8508
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;startpage.com.            IN    

;; AUTHORITY SECTION:
startpage.com.        2598    
IN    SOA    dns1.p01.nsone.net. 
hostmaster.nsone.net. 1619470914 3600 600 1209600 3600


Received 96 bytes from 192.168.0.1#53 in 3 ms
Trying "startpage.com"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;startpage.com.            IN    MX

;; ANSWER SECTION:
startpage.com.        2598    
IN    MX    10 mx2.startmail.com.
startpage.com.        2598    
IN    MX    10 mx1.startmail.com.


Received 81 bytes from 192.168.0.1#53 in 1 ms




user@sys-net:~$ nslookup  www.startpage.com
;; Got SERVFAIL reply from 192.168.0.1, trying next server
Server:        fd00::(redacted):ee5e
Address:    fd00::(redacted):ee5e#53

Non-authoritative answer:
www.startpage.com    canonical name = startpage.com.
Name:    startpage.com
Address: 37.0.87.39



--
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/cf58fe9c-c3f8-be3c-42be-1e40fd64b135%40disroot.org.


Re: [qubes-users] Dom0 update error (Converting database from bdb to sqlite backend)

2021-05-10 Thread 'awokd' via qubes-users

load...@gmail.com:


Configuration: OptionBinding with id "failovermethod" does not existInvalid
configuration value: failovermethod=priority in
/var/lib/qubes/dom0-updates/etc/yum.repos.d/fedora-updates.repo;
Configuration: OptionBinding with id "failovermethod" does not existFedora


In a sys-firewall terminal session, make a backup copy of the file it's 
complaining about 
(/var/lib/qubes/dom0-updates/etc/yum.repos.d/fedora.repo), then edit it. 
Remove the value it's complaining about (failovermethod=priority). Save 
and try again.


If it still fails, you might want to create a fresh sys-firewall, or 
change your UpdateVM to point to a different AppVM.


--
- 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/5de32156-241f-4dd7-2684-4d6612ffed8f%40danwin1210.me.


Re: [qubes-users] detect tcp/ip connections of executables due to qubes firewall restrictions

2021-05-10 Thread 'awokd' via qubes-users

lik...@gmx.de:

Hi!

Due to the current implementation/design of qubes firewall, it's hard to use domain names 
for firewall rules, because of "static" DNS resolution:
https://github.com/QubesOS/qubes-issues/issues/5225

To find out the "connection wishes/tries" of an executable, what's the 
recommendation to use them for firewall rules?
1.  Let's assume all network access except DNS is restricted from a 
AppVM. How can I find out which domains/IPs which executable is trying to 
use/connect to?
2. What are you're best practices to find out all IPs for a domain to 
white list them?

Best, P

1. netstat -pan, and/or tcpdump from somewhere networking isn't blocked. 
Might have to watch DNS requests to see what it's attempting to resolve. 
Don't know of a way to do it with networking disabled.

2. Check the vendor's documentation/KB.

--
- 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/2880b609-c97a-b4bc-27ed-d53c1a079f8c%40danwin1210.me.


Re: [qubes-users] Qubes won't boot

2021-05-10 Thread 'awokd' via qubes-users

Qubes User:

Hello,
I was using Qubes for about 3 months and didn't use it last month.
Yesterday it wouldn't boot.
Using Qubes rescue didn't help. After typing passphrase it says Linux system not
found so it doesn't mount.
So i found a way to mount disk manually. Going through directories found out
that boot folder is empty.
Also if that is not an option i want to save my files but seems like private.img
are missing. There is only icon.png file in VM folders.
Is there any way to recover boot files so i can boot it again or at least save
files from VMs somehow?


Try booting with a LiveCD distribution. Scan and mount the LVM thin 
volumes with vgchange -ay. You may need to install a package to support 
LVM thin. You should be able to pull data from the VMs that way.


--
- 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/f5eb34ec-a6c0-f198-1e75-2546be97620c%40danwin1210.me.


Re: [qubes-users] Support Issue

2021-05-10 Thread 'awokd' via qubes-users

'Ride4life223' via qubes-users:

This is a support notice for Lenovo Legion 5 I5IMH05H
Unable to install Qubes OS R4.0.4 using live USB iso. Freezes halfway through 
the boot process does not make it to install start screen.


Have you seen 
https://www.qubes-os.org/doc/installation-troubleshooting/, and the UEFI 
troubleshooting guide it links to too?


--
- 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/f214c05c-3ef8-613a-a92a-64c055c8d847%40danwin1210.me.


Re: [qubes-users] How do I install trezor-bridge on a Qubes system without a sys-usb qube e

2021-05-10 Thread 'awokd' via qubes-users

'Joanna Anders' via qubes-users:


I'm trying to make Trezor Model T work on my Qubes system installed on a
ssd *usb drive* according to this guide https://wiki.trezor.io/Qubes_OS .
So by default the *sys-usb qube is disabled*. If I try to enable it my
whole system turns unusable.

Should I edit the *sys-net* qube instead of nonexistent *sys-usb* ?

If I'm not mistaken, running Qubes directly from a USB drive requires 
dom0 to own at least the USB controller responsible for the drive. This 
would mean you would have to run the trezor service there as well, but 
as dom0's networking is disabled, wouldn't get you any further. 
Unfortunately, think you pretty much require a sys-usb. If you have more 
than one controller driving the external ports (fairly unusual on 
laptops, though) you may be able to assign a single unused controller to 
a sys-usb qube and use the Trezor device on those specific ports. Not an 
option if your drive is on one of the same ports. Other option could be 
to install Qubes on local disk instead of USB.


--
- 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/428ac0fe-86e8-1d44-b1b7-6f304c2f1044%40danwin1210.me.


[qubes-users] Qubes won't boot

2021-05-06 Thread Qubes User
Hello,

 

I was using Qubes for about 3 months and didn't use it last month.

Yesterday it wouldn't boot.

 

Using Qubes rescue didn't help. After typing passphrase it says Linux system not found so it doesn't mount.

So i found a way to mount disk manually. Going through directories found out that boot folder is empty.

 

Also if that is not an option i want to save my files but seems like private.img are missing. There is only icon.png file in VM folders.

 

Is there any way to recover boot files so i can boot it again or at least save files from VMs somehow?



-- 
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/trinity-b05fda5f-b9b7-48bc-94c1-aa98fb89ee53-1620324425410%403c-app-mailcom-lxa10.


[qubes-users] Support Issue

2021-04-29 Thread 'Ride4life223' via qubes-users
This is a support notice for Lenovo Legion 5 I5IMH05H
Unable to install Qubes OS R4.0.4 using live USB iso. Freezes halfway through 
the boot process does not make it to install start screen.

Sent with [ProtonMail](https://protonmail.com) 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/8wE7RM1Ci8ja6zRKctZ4JkT_McRhBPRlHZgy7pnAIlkEBC2YxybUJ3tzxf8BJkW5e6yGVt5hglmXEJmxmUMhlojBeLHnB7Gxt3bzuFdDZvE%3D%40protonmail.com.


[qubes-users] How do I install trezor-bridge on a Qubes system without a sys-usb qube e

2021-04-29 Thread 'Joanna Anders' via qubes-users

I'm trying to make Trezor Model T work on my Qubes system installed on a 
ssd *usb drive* according to this guide https://wiki.trezor.io/Qubes_OS . 
So by default the *sys-usb qube is disabled*. If I try to enable it my 
whole system turns unusable.

Should I edit the *sys-net* qube instead of nonexistent *sys-usb* ?

*in sys-usb:* 

* sudo vim /usr/local/etc/qubes-rpc/trezord-service * 

*add this line: *

* socat - TCP:localhost:21325* 

-- 
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/41fc9a76-7921-4bc1-ac9b-6e931d6fd69fn%40googlegroups.com.


[qubes-users] draw.io desktop running from a template

2021-04-28 Thread 'cubit' via qubes-users
This is a bit of a long shot but is there anyone using draw.io / diagrams.net 
<http://draw.io/diagrams.net> via the desktop app installed in a template.

I've got it installed in a debian template but when you launch it from an appVM 
 it does not see any of the available templates.

would love to hear others experience 

-- 
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/MZPNmpb--7-2%40tutanota.com.


[qubes-users] Re: HCL - Dell XPS 9310 2-in-1

2021-04-27 Thread turscar via qubes-users

Sven

I just saw your reply. Finally, something that works. I settled on this 
configuration, in case it helps anyone else. Thank you very much.


\-> remove \`gnome-settings-daemon\` from template(s)/some dependencies removed 
also
\-> in templates add:
/etc/X11/Xresources (Fedora/Dom0) Xft.dpi: 192
/etc/X11/Xresources/x11-common (Debian/Whonix WS+GW) Xft.dpi: 192
XFCE-settings in Appearance to DPI 192 / font 11
All Terminals ->Prefs->enable Custom Font-->set 11
Window Manager - \`xhdpi\` + Title font = 11
Settings Editor->xsettings->create "IconSizes" and set 'gtk-menu=32,32'
\ Original Message 
On 28 Márta 2021 20:15, < turs...@pm.me> wrote:

>
>
>
>
>
>
> I found it very difficult to get Qubes installed and useable. These are some 
> notes I made at the time and may need some adjustment for other scenarios.
>
>
>
>
>
> INSTALLATION 4.04rc2:
>
>
> Use 8GB USB stick (left OR right side works). Bigger sizes failed for me.
>
>
> disable Secure Boot
>
>
> enable ACHI
>
>
>
>
>
> edit sda2 EFI/BOOT/BOOTX64.cfg
>
>
> comment out under 'qubes-verbose' section
>
>
> \# noexitboot=1
>
>
> \# mapbs=1
>
>
> text install with 'inst.text' placed before i915 in the following line:
>
>
> kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-R4.0-x86\_64 i915.alpha\_support=1
>
>
> make sure networking is attached to bring up GUI
>
>
>
>
>
> I had to combine sys-net and sys-usb in the install options because I was 
> using a docking station for ethernet.
>
>
> Disable power mgmt except blank screen in Screensaver
>
>
> Touchpad settings: enable tap and adjust speed
>
>
>
>
>
> sudo qubes-dom0-update kernel-latest-qubes-vm
>
>
> sudo qubes-dom0-update kernel-latest
>
>
> (remove old kernel in qubes EFI)
>
>
> sudo qubes-dom0-update --action=\[reinstall\|remove\|list\] 
> kernel-latest\[-qubes-vm\]
>
>
> sudo dnf remove qubes-template-fedora-32
>
>
>
>
>
> A lot of video issues causing crashes. Found the following fixed it enough so 
> far to make it useable:
>
>
> [https://github.com/Qubes-Community/Contents/blob/master/docs/troubleshooting/intel-igfx-troubleshooting.m][https_github.com_Qubes-Community_Contents_blob_master_docs_troubleshooting_intel-igfx-troubleshooting.m]
>
>
>
>
>
> change: i915.alpha\_support=1 -> i915.force\_probe=\*
>
>
>
>
>
>
>
>
>
>
>
> The following are some miscellaneous notes to get the DPI and GTK working 
> right. I never tuned this properly, so you will have to play around. Please 
> post configurations if you ever get this correct.
>
>
>
>
>
> DPI 288 & Font size adjust to 6 in Appearance settings
>
>
> Window Manager - xhdpi
>
>
>
>
>
>  *  *about:config in Firefox and search for layout.css.devPixelsPerPx set 
> this value to 2 or 1.5 as you wish to adjust the size of the Firefox icons*
>
>  *  
> https://askubuntu.com/questions/652021/adapt-font-and-icon-sizes-to-high-definition-screen-resolutions-in-ubuntu-studio
>
>  *   *  1. Set a Custom DPI setting
>
>  *  Open a terminal with CTRL+ALT+t and enter
>
>
>  *  LANG=c xfce4-settings-manager
>
>  *  In "Appearence"->Fonts-> "Custom DPI Setting:" set this to 288 
> (instead of the default 96).
>
>  *  Log off and on again to accept the new settings in all windows.
>
>  *  2. Adapt Theme and settings
>
>
>  *  Set your panel size to a height of 48
>
>  *  In xfce4-settings-manager->"Settings Editor" 
> (xfce4-settings-editor)
>
>
>  *  in section xfce4-desktop (create an entry if it doesn't exist)
>
>  *  desktop-icons/icon-size Type Integer and set it to 128
>
>
>  *  in section xsettings set CursorThemeSize to 48
>
>  *  in section xsettings set Gtk/IconSizes to
>
>  *  
> gtk-large-toolbar=32,32:gtk-small-toolbar=24,24:gtk-menu=32,32:gtk-dialog=88,88:gtk-button=32,32:gtk-dnd=32,32
>
>  *  Or use the commandline:
>
>  *  xfconf-query -c xsettings -p /Gtk/IconSizes -s 
> "gtk-large-toolbar=32,32:gtk-small-toolbar=24,24:gtk-menu=32,32:gtk-dialog=88,88:gtk-button=32,32:gtk-dnd=32,32"
>
>
>  *  gtk-large-toolbar are main toolbars
>
>  *  gtk-small-toolbar are secondary toolbars
>
>  *  gtk-menu are menus
>
>  *  gtk-dialog are dialog icons
>
>  *  gtk-button are buttons (eg the xfce panel uses buttons)
>
>  *  gtk-dnd are the icons displayed if you drag and drop a file or a 
> 

Re: [qubes-users] HCL - Thinkpad L540 (i5-4300M)

2021-04-27 Thread 'awokd' via qubes-users

A Luciani:


One thing : sys-usb don't work, i'm currently trying to see why, maybe i
have to check something in the BIOS because the VM will boot if there is no
PCI (USB) device in "device" option.

Also experiment with the strict_reset and/or permissive option on the 
USB controller: 
https://www.qubes-os.org/doc/usb-troubleshooting/#usb-vm-does-not-boot-after-creating-and-assigning-usb-controllers-to-it.


--
- 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/9c7c47e6-5703-67e8-aae8-42cdad51db4f%40danwin1210.me.


[qubes-users] delaying total shutdown of disposable qube

2021-04-21 Thread 'Ólafur Jens Sigurðsson' via qubes-users

Hi

When we open an attachment from emails, like .odf files and such, and 
start writing in them, meaning to send the edited file back to the 
sender. Then there is a slight chance of a person saving the file, 
closing the editor and then loosing the file because the qube has shut 
down.


We would like to add a new disposable template in which the disposable 
vm's will be shut down with a delay of a few minutes, just enough for 
the person to start replying to the email and finding that they need the 
file and then open up the file manager from that disposable qube that 
was almost shut down and thus saving the file.


How would we do this? Is there some option in Qubes-OS that supports this?

If no option exists then I would like to know what happens when you 
close an app like librewriter that is opened in a dispvm. How does the 
dispvm know that it is supposed to shut down when the app is closed? 
Perhaps we can find a way through there to implement some kind of delay.


--
Med venlig hilsen
Ólafur Jens Sigurðsson
Systemadministrator

Kontor: 70 40 40 70
Direkte: 70 40 40 67
Email: o...@nemtilmeld.dk

NemTilmeld.dk
- Online tilmeldingssystem - Nemt for dig og dine deltagere!

--
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/960c045c-6af7-bf28-761d-e78d31cc3b0b%40nemtilmeld.dk.


[qubes-users] Introducing: Qubes Video Companion v1.0

2021-04-20 Thread 'Elliot Killick' via qubes-users
Hello, everyone!

Starting this past early September, I've been working on and off to
create a new tool for secure webcam integration in Qubes OS out of
/absolute necessity/ for remote work at both my (new) job and school at
the university I'm newly attending. The tool is called Qubes Video
Companion and I'm proud to announce that it's evolved far past that
basic requirement and at version 1.0.4 is now publicly available for
testing!

Before resorting to the creation of an entirely new project, I thought
of many other potential solutions for allowing me to use a webcam in
Qubes but all of them fell flat in one way or another, to list them all
(skip through this list if you're not up for too much reading, haha):

1. Do video conferencing in the sys-usb qube with the webcam device attached

Unfortunately, the desktop I run Qubes OS on doesn't have a sys-usb qube
due to complications of its hardware. The primary issue being that I
require a USB sound card which has to stay attached to dom0 where the
other Qubes audio components are. Not to mention, this solution is also
far from being optimal from a security standpoint particularly because I
also use a USB mouse and keyboard meaning I would essentially have to
hand over control of those devices to sys-usb. This leaves the door open
for keyboard injection into dom0 thereby compromising it (and the entire
system) in the case sys-usb is compromised due to, for example, a bug in
the video conferencing software. This also means enabling networking
(removing the air gap) for sys-usb which again is harmful to security.

Note that I don't personally consider not having a sys-usb qube for
protecting dom0 from physical USB device attacks as much of a security
issue because my desktop is always at home which is outside of my threat
model.

2. Do video conferencing in any qube with qrexec+usbip (with a sys-usb
qube; can't be done from dom0)

Even disregarding my personal hardware issues above, qrexec+usbip is a
mess to get working and does poor on performance according to this
GitHub issue: https://github.com/QubesOS/qubes-issues/issues/4035.
Although, I've never been able to test it out myself. Additionally, the
security concerns of using TCP/IP and USBIP between qubes is there. This
also remotely exposes the webcam firmware which is yet another security
risk with this configuration.

3. Do video conferencing in any qube with a bought USB hub PCI card

This also means taking on all the security risks of attaching that
physical hardware directly to the VMs which considering they are to run
applications I don't trust such as Zoom (which my job requires; I
wouldn't use Zoom given the choice of course) — doesn't sit well with me
at all. Plus, hot swapping PCI devices, though supported by Xen, is
disabled in Qubes because of what a complex operation it is
security-wise leaving the door open to bugs (I read this was the reason
somewhere I think in the Qubes mailing list I think). This means that in
order to use my webcam on different qubes (my "school" and "work" qubes
for my purposes) I would have to reboot them each time to attach and
remove the USB hub with my webcam plugged into it. This would be very
inconvenient for my use case particularly when I'm trying to get work
done efficiently. I thought about combining my school and work qubes
into just one qube but at that point why am I even bothering to use
Qubes OS if I don't utilize its most basic security feature. Lastly, I
could also buy multiple USB hub PCI cards but that was just too hacky
for me.

4. Do video conferencing in any qube with FFmpeg for streaming video

At the time, there were preliminary outlines of a working solution for
webcam video streaming with FFmpeg. While this was a good start, it just
didn't cut it for my needs. The resolution was very low (when I tried to
raise it to 1920x1090 it didn't work) and even with that low resolution
the latency was below optimal and it just tore up my CPU power when I
needed it the most; hence this too was not a realistic solution. Plus,
FFmpeg isn't available in Fedora without adding RPM Fusion repo due to
patent issues which was just one more little gripe I had with it. And to
top it off, FFmpeg doesn't exactly have an amazing security track record...

5. Dual booting and other OSs

Finally, as a very last resort (not being able to use my webcam wasn't
an option for me), I thought about dual booting (way too inconvenient
not to mention the security downfalls) and (just for a very brief moment
for the sake of completeness) other OSs. However, I have already
contributed one project (qvm-create-windows-qube) to Qubes OS and have
now been "locked in" to the Qubes ecosystem (haha) by fantastic features
such as Qubes Split GPG, a great community as well as countless other
qualities and would feel insecure running any other operating system.

As far as using a webcam in Qubes OS went, I needed something that /just
worked/, I needed — Qubes V

[qubes-users] HCL -

2021-04-17 Thread celiashc via qubes-users
Hi I'm here to report how Qubes works on my 6-year-old laptop after 1-month of 
installation. In short, it can take longer time to start-up VMs (inevitable for 
my 8Gb RAM), but once a VM is on, softwares within it run smoothly. I once 
received a warning like "not enough memory to start a new VM", but that was 
when I had 6 other VMs running.

Pre-installation check:
This model has Intel VT-d available (checked on intel official specs: 
https://ark.intel.com/content/www/us/en/ark/products/85212/intel-core-i5-5200u-processor-3m-cache-up-to-2-70-ghz.html).
But I wanted to make sure if it was on, as this aspect is not visible on the 
very restricted factory BIOS. I downloaded the Intel Processor Identification 
Utility to scan my hardware, and it appears that Intel VT-d is turned off.
I could not find a way to turn this feature on without replacing my BIOS, so I 
figured I'd try the installation anyway.

I installed Qubes-R4.0.4-x86_64 through a bootable USB made with Rufus on 
Windows 10.

Booting with UEFI: (didn't work for me)
I chose to wipe the disk and did a full install. It all went fine and it said 
"Installation complete". But then I was unable to boot into Qubes. My BIOS(?) 
thought its windows OS is corrupted and offered to reinstall/ repair windows, 
and both options returned error.

Booting with legacy: (worked)
I then force-close the laptop and try install Qubes in legacy mode, and it went 
smoothly. Did not meet error with Intel VT-d feature.

Qubes management: 
I chose to install the additional Debian TemplateVM, sys-net, sys-firewall, 
sys-whonix. They all worked fine. I was unable to update TemplateVMs with the 
GUI Qubes updater, but with command prompts it worked fine.

Other functionalities:
1. wifi connection: OK
-a minor bug: when I wake laptop from sleep and wifi network reconnects, system 
message displayed "Network disconnected", even though I was connected to the 
wifi)
- the time display wasn't accurate at first, but once I got the system on the 
internet it synchronised automatically

2. i-bus Pinyin input: OK (I installed on TemplateVMs, so when I turned on both 
fedora and debian VMs, there're two input method icons displayed)

3. fn keyboard shortcuts: OK
- no problem to adjust volumn, screen brightness and logout/hibernate options 
with original keyboard shortcuts

4. USB ports: partial OK
- USB 2.0 port, but not USB 3.0 port is usable. The USB 2.0 can be isolated in 
a VM and then attach to another workspace VM (e.g. personal)

5. Software installation: OK
Apart from command prompts, I used Synaptic Package manager for Debian and 
Software Manager that comes with Fedora. Both worked fine.

And yeah, that's all. I am practically a newbie in Linux and there were other 
bloopers when I tried install Qubes, but the detailed documentation solved most 
of my problems. Thanks for the teams great work!




-- 
 Sent with Tutanota, the secure & ad-free mailbox: 
 https://tutanota.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/MYYVlb2--3-2%40tutanota.com.


Qubes-HCL-Acer-Aspire_V3_371.yml
Description: application/yaml


[qubes-users] HCL - HP Spectre x360 15-BL152NR

2021-04-17 Thread 'Ben Moody' via qubes-users
Set the following kernel options on the installer usb media:

Comment out noexitboot=1 and mapbs=1
(https://www.qubes-os.org/doc/uefi-troubleshooting/)

Blacklisted nouveau (https://www.qubes-os.org/doc/uefi-troubleshooting/)

Set i915.force_probe=*
(https://github.com/Qubes-Community/Contents/blob/master/docs/troubleshooting/intel-igfx-troubleshooting.md)



Works perfectly out of the box.


Touchpad isn't very good on this laptop (nothing to do with qubes). It's
an older synaptics unit and has weird acceleration behaviour. I tried
playing around with the config but would definitely say Lenovos and
Dells have much better thinkpads.

I've been testing qubes on a few older workstation laptops - all have 4K
screens. I haven't found dealing with that particularly difficult even
with i3. Follow the instructions here off the bat:
https://github.com/Qubes-Community/Contents/blob/master/docs/troubleshooting/intel-igfx-troubleshooting.md.

I use an ultrawide monitor at my desk, but have the laptop display
switched off when it's connected, so I don't have to deal with multiple
displays at different DPIs. I just wrote a script that checks the screen
resolution then rewrites the dom0 xft.resources dpi setting, passes the
gsettings commands to all running vms via qvm-run and restarts lightdm,
and bound it to a key in my i3 config. I then have another script that
autostarts in each VM to check what the screen resolution is and sets
the scaling for the VM appropriately. A little bit fiddly initially but
works fine, and given I only have to use it when I'm docking or
undocking the machine (which is not that often), restarting lightdm
isn't a particularly big deal. I'll post my configs elsewhere, but I
wouldn't let that deter you from running Qubes on a 4k laptop, it's
really nowhere near as annoying as some of the threads you get from a
google search suggest.

-- 
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/a60608b2-f0bf-fb47-df15-abfddd801916%40protonmail.com.
---
layout:
  'hcl'
type:
  'convertible'
hvm:
  'yes'
iommu:
  'yes'
slat:
  'yes'
tpm:
  'unknown'
remap:
  'yes'
brand: |
  HP
model: |
  HP Spectre x360 Convertible 15-bl1XX
bios: |
  F.42
cpu: |
  Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz
cpu-short: |
  FIXME
chipset: |
  Intel Corporation Device [8086:5914] (rev 08)
chipset-short: |
  FIXME
gpu: |
  Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
  Intel Corporation Sunrise Point-LP Integrated Sensor Hub [8086:9d35] (rev 21)
gpu-short: |
  FIXME
network: |
  Intel Corporation Wireless 8265 / 8275 (rev 78)
memory: |
  16260
scsi: |

usb: |
  1
versions:

- works:
    'yes'
  qubes: |
R4.0
  xen: |
4.8.5-29.fc25
  kernel: |
5.4.90-1
  remark: |
FIXME
  credit: |
Ben
  link: |
FIXLINK

---



[qubes-users] HCL - Dell Precision 5520

2021-04-17 Thread 'Ben Moody' via qubes-users
Set the following kernel options on the installer usb media:

Comment out noexitboot=1 and mapbs=1
(https://www.qubes-os.org/doc/uefi-troubleshooting/)

Blacklisted nouveau (https://www.qubes-os.org/doc/uefi-troubleshooting/)

Set i915.force_probe=* (https://www.qubes-os.org/doc/uefi-troubleshooting/)


Installed in legacy mode - will try another install at some point to see
if I can get UEFI working.


Otherwise - install is perfect. Everything works out of the box, no issues.

-- 
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/bcc471f9-3d43-cf3a-6046-86718bd7ec53%40protonmail.com.
---
layout:
  'hcl'
type:
  'notebook'
hvm:
  'yes'
iommu:
  'yes'
slat:
  'yes'
tpm:
  'unknown'
remap:
  'yes'
brand: |
  Dell Inc.
model: |
  Precision 5520
bios: |
  1.22.1
cpu: |
  Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
cpu-short: |
  FIXME
chipset: |
  Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM 
Registers [8086:5910] (rev 05)
chipset-short: |
  FIXME
gpu: |
  Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
gpu-short: |
  FIXME
network: |
  Intel Corporation Wireless 8265 / 8275 (rev 78)
memory: |
  32291
scsi: |

usb: |
  2
versions:

- works:
'FIXME:yes|no|partial'
  qubes: |
R4.0
  xen: |
4.8.5-30.fc25
  kernel: |
5.4.107-1
  remark: |
FIXME
  credit: |
FIXAUTHOR
  link: |
FIXLINK

---



[qubes-users] Issues merging salt pillars

2021-04-15 Thread 'hut7no' via qubes-users
Hi guys!
I am having some trouble merging some salt pillars, and was wondering if anyone 
here has experience with this.
I have some default settings in a yaml file, and am trying to overwrite values 
based on vm types.
I get the wanted behaviour from running something like "qubesctl --show-output 
--targets dom0 defaults.merge '{a: {b: 1.1, c: 2.1}}' '{a: {b: 1.2}}'" from the 
terminal:
--
a:
  b:
- 1.2
  c:
- 2.1
--
(b is overwritten, but c remains untouched)
When using slsutil.renderer on the map.jinja, the whole list is replaced 
instead, leaving only completely untouched lists and new values:
--
dvm:
  vcpus:
- 2
disp:
  vcpus:
- 2
template:
  source:
- d10m
  include_in_backups:
- True 
--
default_prefs.yaml:
--
template:
  - source: d10m
  - include_in_backups: True
dvm:
  - netvm: none
  - provides_network: False
  - klass: AppVM
  - template_for_dispvms: True
  - default_dispvm: none
  - default_user: user
  - vcpus: 1
  - memory: 300
  - maxmem: 4096
  - kernel: 5.4.107-1.fc25
  - kernelopts: nopat apparmor=1 security=apparmor
  - virt_mode: pvh
  - label: gray
  - include_in_backups: True
disp:
  - netvm: none
  - klass: DispVM
  - default_dispvm: none
  - default_user: user
  - vcpus: 1
  - memory: 300
  - maxmem: 4096
  - kernel: 5.4.107-1.fc25
  - kernelopts: nopat apparmor=1 security=apparmor
  - virt_mode: pvh
  - label: black
  - include_in_backups: True
--
map.jinja:
--
{% import_yaml 
'/srv/salt/user_pillar/base/vm_prefs/templates/default_prefs.yaml' as 
default_settings %}

{#{% if grains['id'].endswith('med') %}#}
# what makes the type different from default
{%- load_yaml as type_diff %}
dvm:
  - vcpus: 2
disp:
  - vcpus: 2
{% endload %}
{#{% endif %}#}
{% set merged = salt['defaults.merge'](default_settings,type_diff) %}
{{ merged }}
--
I noticed that some functions(defaults.update) and 
arguments(merge_lists,in_place) are not available for the installed salt 
version, do I need those ?

-- 
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/20210414183258.GA878%40mail2-dvm.


Re: [qubes-users] X230 - external monitor how to

2021-04-14 Thread 'taran1s' via qubes-users




unman:

On Thu, Apr 08, 2021 at 01:25:57PM +, 'taran1s' via qubes-users wrote:



unman:

On Wed, Apr 07, 2021 at 01:59:10PM +, 'taran1s' via qubes-users wrote:

How do I use the X230+Qubes 4.0 with external monitor of at least 1080p or
higher? I understand that a dock station (Ultrabase?) is required to be able
to use the HiDPI external monitor with X230.

What smallest dock station would you propose for this purpose? Is there
possibly some other, more portable way, to get X230 to use HiDPI external
monitor?



You don't need a dock for this - the x230 supports 1920x1200 through HDMI
and 2560x1600 through the DisplayPort.
Of course, a dock is always nice.


This is really interesting and thank you a tone for this information. I dont
see the HDMI output from my X230 but there seem to be a Mini Displayport.
Very nice.



You can also mod the x230 with a board and updated panel to get 1080p on
a larger IPS panel - very portable and a real boost to the x230.


Can you please elaborate more on this? What kind of board and updated panel
is it? I didn't know that X230 can be modded to have 1080p IPS display at
all. This would possibly solve most need to have external display for simple
media.



There are a number of boards you can use - imo the best is from
nitrocaster  - nitrocaster.me/store
They all work in the same way - you solder the board on the motherboard
and "steal" output from the dock. With some minor modification to the
screen enclosure you can fit a really nice 1080p IPS panel to the x230.

There are a number of people who will do this for you, if you doubt
your soldering skills. If you didnt already have an x230 you can also buy
x230 premodded, but that's no use to you. :-(



Thank you!

--
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/273200cf-3552-0e10-786c-ca9fad8ec548%40mailbox.org.


Re: [qubes-users] R4.0.4 Wiin10: block device dom0:loop1 not available

2021-04-14 Thread 'awokd' via qubes-users

Steve Coleman:

I have been having problems with starting a Win10 VM for a while now.
Previously Qubes would always timeout and shut it down even though the VM
was up and running fine. My impression is that once the VM was forcibly
terminated/killed due to a timeout, usually the next time it would start up
normally. I could spend as much as an hour just trying to get it startup
properly, and now it doesn't even get that far.


Disabling swap or setting it to a fixed size seemed to help me here, 
although my issue was the Win10 VM crashing on startup.



Now after enough forced terminations it is unable to even begin starting
and no logs are being created at all. The only symptom is the popup message
"block device dom0:loop1 not available". I don't see anything significant
from journalctl or dmesg. Running in debug mode does absolutely nothing.
Restoring from backup just gives the same loop error message when
attempting to start the restored VM.


Have you enabled debug mode, booted, then checked the vm's log in 
/var/log/qubes? You might also need to set qvm-feature gui-emulated to 1 
on the VM to see a display with debug checked, but see if it's already 
set first with qvm-features .



Q: What is this loop1 supposed to point at, and is there a way to recreate
it?


I booted my Win10 VM and don't have a loop1. Is it possible you set up 
your VM somehow to automatically map an ISO?


--
- 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/ce82839d-f215-3ab0-2195-d665ffd42b67%40danwin1210.me.


[qubes-users] HCL - MSI Z490-A Pro Motherboard

2021-04-13 Thread 'Encrypted Giraffe' via qubes-users
Everything works, video, networking, sound, usb, suspend to ram, etc.
Needs kernel 5.8+ for networking.

-- 
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/MYCSUP1--7-2%40encryptedgiraffe.xyz.


Qubes-HCL-Micro_Star_International_Co___Ltd_-MS_7C75-20210413-165420.yml
Description: application/yaml


Re: [qubes-users] Black Screen on installation

2021-04-11 Thread 'awokd' via qubes-users

Balmhood:


- 2 different USB keys (verbatim 8GB and samsung 32GB)
- In bootx64.cfg, I’ve commented out both *“#noexitboot=1”* and
*“#mapbs=1”* => this takes me to another screen but then I get stuck at
multiple lines of *: “localhost dracut-initqueue[545]: Warning:
dracut-initqueue timeout - starting timeout scripts"* And then it times
out and stops.
- In my BIOS (latest v1.06), I do not have access to modify either
 secure boot or UEFI boot to Legacy (Thanks Acer), so I cannot try
troubleshoots I have seen with these modified.
- Plugging a monitor via HDMI, no change


There is another switch like nomodeset for nvidia cards, worth trying if 
you have one. Might also want to try a 4.1 alpha and see if you get any 
further.


--
- 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/529de8e8-5196-fb78-b047-59a303bae181%40danwin1210.me.


[qubes-users] Qube starts but applications don't launch

2021-04-09 Thread 'newquber' via qubes-users
I have a major problem with my one of my Qubes. It’s super important to get it 
back running as I have very sensitive information on it which I need.

I’m an absolute newbie when it comes to Qube/ codes or whatsoever so I would 
kindly ask to explain me things as if you are talking to your mother explaining 
an smartphone.

So heres the issue:
My Debian-10 Qube (standalone vm) suddenly stopped working. I did not update 
nor did I change anything in that qube. It literally stopped working from one 
day to another. The qube starts, I get the pop-ups that the qube started but no 
application starts. Not even the terminal starts. Nothing.

I can do: “sudo xl console -t pv VMNAME”, I get a reaction but it then asks for 
a login. I don’t know what to type in there. I tried my qubes login but it 
doesn’t work.

I went to Qube Settings and checked “run in debug”. I read that I can get some 
logs? But where are they? And what should I do with these logs? I’m probably 
not even able to understand them. So a step by step solution where to 
get/upload/post them would be great.

I tried cloning. It didn’t help. I also tried: “qvm-start-gui --all”.

I searched the forum to find a solution but nothing helped me. These tho come 
close to my problem:

One of my qubes suddenly won’t start any applications. Terminal windows, web 
browsers, nothing. The qube itself launches without issue (qvm-ls shows it as 
“running”) but I’m unable to launch any apps in it. I tried cloning it, but the 
clone has the same behavior (not too surprised there). It worked fine when I 
shutdown yesterday, and all my other qubes seem to be fine. Any idea where to 
start troubleshooting this?

https://www.mail-archive.com/qubes-users@googlegroups.com/msg31474.html

Any help is much appreciated.

I just found this: Mount LVM image | Qubes OS
If I can restore the files through this, I think it would also help but I don’t 
understand fully how to do that. An step by step manual would be great. The 
qube that needs to get restored is named: “GroundedVM”

All my others qubes work well.

-- 
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/TcHdueQfCVfsPT-Mfo2iXperIq2MeavF6UHoJn5ecbFAeqYhyV5ia1ISyxWEKelEh1rwXIlqSwKBzFOqso49TvqwKUTdkQksPmHggp6Lxsg%3D%40protonmail.com.


Re: [qubes-users] X230 - external monitor how to

2021-04-08 Thread 'taran1s' via qubes-users




unman:

On Wed, Apr 07, 2021 at 01:59:10PM +, 'taran1s' via qubes-users wrote:

How do I use the X230+Qubes 4.0 with external monitor of at least 1080p or
higher? I understand that a dock station (Ultrabase?) is required to be able
to use the HiDPI external monitor with X230.

What smallest dock station would you propose for this purpose? Is there
possibly some other, more portable way, to get X230 to use HiDPI external
monitor?



You don't need a dock for this - the x230 supports 1920x1200 through HDMI
and 2560x1600 through the DisplayPort.
Of course, a dock is always nice.


This is really interesting and thank you a tone for this information. I 
dont see the HDMI output from my X230 but there seem to be a Mini 
Displayport. Very nice.




You can also mod the x230 with a board and updated panel to get 1080p on
a larger IPS panel - very portable and a real boost to the x230.


Can you please elaborate more on this? What kind of board and updated 
panel is it? I didnt know that X230 can be modded to have 1080p IPS 
display at all. This would possibly solve most need to have external 
display for simple media.


--
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/0a0364ea-66d6-007c-0e61-a82d9c60263f%40mailbox.org.


[qubes-users] X230 - external monitor how to

2021-04-07 Thread 'taran1s' via qubes-users
How do I use the X230+Qubes 4.0 with external monitor of at least 1080p 
or higher? I understand that a dock station (Ultrabase?) is required to 
be able to use the HiDPI external monitor with X230.


What smallest dock station would you propose for this purpose? Is there 
possibly some other, more portable way, to get X230 to use HiDPI 
external monitor?


--
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/10f700de-a6ee-4a28-7bc3-4f9a32bc94e5%40mailbox.org.


Re: [qubes-users] X230 - switch-on backlit keyboard

2021-04-06 Thread 'taran1s' via qubes-users




unman:

On Tue, Apr 06, 2021 at 12:44:31PM +, 'taran1s' via qubes-users wrote:

I have got my X230 with Qubes preinstalled. Everything seems to work well,
but I cant switch-on the backlit keyboard. Pressing Fn+Space just cycles
between ON and OFF of the upper light (besides camera). The X230 of course
has, or should have, the backlit keyboard.

I didn't find any options in the Qubes Settings Manager to make it run. How
can I make it run?

Thank you!



This isn't a Qubes issue, because the backlit keyboard works fine on
varieties of 4.
Just to check - you **do** have a backlit keyboard? When you look at the
lamp icon on the space bar, are the beams pointing to the screen or
toward you?



Ah I see. The beams pointing towards me.

--
Kind regards
taran1s

gpg: 12DDA1FE5FB39C110F3D1FD5A664B90BD3BE59B3

--
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/9c278863-4396-517d-e70c-94b4c461820a%40mailbox.org.


[qubes-users] X230 - switch-on backlit keyboard

2021-04-06 Thread 'taran1s' via qubes-users
I have got my X230 with Qubes preinstalled. Everything seems to work 
well, but I cant switch-on the backlit keyboard. Pressing Fn+Space just 
cycles between ON and OFF of the upper light (besides camera). The X230 
of course has, or should have, the backlit keyboard.


I didn't find any options in the Qubes Settings Manager to make it run. 
How can I make it run?


Thank you!


--
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/f27a30ff-15e6-fd5f-d24b-e7a64baf3164%40mailbox.org.


Re: [qubes-users] https://www.qubes-os.org/news/2021/03/19/qsb-067/

2021-04-05 Thread qubes-os

Try running the commands separately:

sudo qubesctl --skip-dom0 --templates state.sls update.qubes-vm

followed by:

sudo qubesctl --skip-dom0 --standalones state.sls update.qubes-vm

That worked on this end when I got the same error.




--
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving 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/ccb3793c-2b69-00e5-a338-92cfe19e97d7%40go-bailey.com.


Re: [qubes-users] Screen shot: open in DocumentViewer in AppVM

2021-04-02 Thread 'awokd' via qubes-users

Beto HydroxyButyrate:


When I screen scrape in dom0, one option is to open in DocumentViewer in
one AppVM.
I assume it is because this is the only AppVM I have DocumentViewer added
to the big menu.  Anyway, nothing ever happens.  Does anyone use this?  Has
anyone used this?


I don't use that option, but save to dom0 then copy to an AppVM. There 
are some code samples and links under Productivity here: 
https://github.com/Qubes-Community/Contents/tree/master/code.


--
- 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/7e54ca22-9af4-fd69-e70f-6eac8cd3695d%40danwin1210.me.


[qubes-users] HCL - Dell XPS 9310 2-in-1

2021-03-28 Thread turscar via qubes-users
I found it very difficult to get Qubes installed and useable. These are some 
notes I made at the time and may need some adjustment for other scenarios.

INSTALLATION 4.04rc2:
Use 8GB USB stick (left OR right side works). Bigger sizes failed for me.
disable Secure Boot
enable ACHI

edit sda2 EFI/BOOT/BOOTX64.cfg
comment out under 'qubes-verbose' section
# noexitboot=1
# mapbs=1
text install with 'inst.text' placed before i915 in the following line:
kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-R4.0-x86_64 i915.alpha_support=1

make sure networking is attached to bring up GUI

I had to combine sys-net and sys-usb in the install options because I was using 
a docking station for ethernet.
Disable power mgmt except blank screen in Screensaver
Touchpad settings: enable tap and adjust speed

sudo qubes-dom0-update kernel-latest-qubes-vm
sudo qubes-dom0-update kernel-latest
(remove old kernel in qubes EFI)
sudo qubes-dom0-update --action=[reinstall|remove|list] kernel-latest[-qubes-vm]
sudo dnf remove qubes-template-fedora-32

A lot of video issues causing crashes. Found the following fixed it enough so 
far to make it useable:
[https://github.com/Qubes-Community/Contents/blob/master/docs/troubleshooting/intel-igfx-troubleshooting.m](https://github.com/Qubes-Community/Contents/blob/master/docs/troubleshooting/intel-igfx-troubleshooting.md)

change: i915.alpha_support=1 -> i915.force_probe=*

The following are some miscellaneous notes to get the DPI and GTK working 
right. I never tuned this properly, so you will have to play around. Please 
post configurations if you ever get this correct.

DPI 288 & Font size adjust to 6 in Appearance settings
Window Manager - xhdpi

- about:config in Firefox and search for layout.css.devPixelsPerPx set this 
value to 2 or 1.5 as you wish to adjust the size of the Firefox icons

- 
https://askubuntu.com/questions/652021/adapt-font-and-icon-sizes-to-high-definition-screen-resolutions-in-ubuntu-studio

-

- 1. Set a Custom DPI setting
- Open a terminal with CTRL+ALT+t and enter

- LANG=c xfce4-settings-manager

- In "Appearence"->Fonts-> "Custom DPI Setting:" set this to 288 (instead of 
the default 96).
- Log off and on again to accept the new settings in all windows.
- 2. Adapt Theme and settings

- Set your panel size to a height of 48
- In xfce4-settings-manager->"Settings Editor" (xfce4-settings-editor)

- in section xfce4-desktop (create an entry if it doesn't exist)

- desktop-icons/icon-size Type Integer and set it to 128

- in section xsettings set CursorThemeSize to 48
- in section xsettings set Gtk/IconSizes to

- 
gtk-large-toolbar=32,32:gtk-small-toolbar=24,24:gtk-menu=32,32:gtk-dialog=88,88:gtk-button=32,32:gtk-dnd=32,32
- Or use the commandline:
- xfconf-query -c xsettings -p /Gtk/IconSizes -s 
"gtk-large-toolbar=32,32:gtk-small-toolbar=24,24:gtk-menu=32,32:gtk-dialog=88,88:gtk-button=32,32:gtk-dnd=32,32"

- gtk-large-toolbar are main toolbars
- gtk-small-toolbar are secondary toolbars
- gtk-menu are menus
- gtk-dialog are dialog icons
- gtk-button are buttons (eg the xfce panel uses buttons)
- gtk-dnd are the icons displayed if you drag and drop a file or a folder

- you can change them to any size as long your icon theme supports it

- In xfce4-settings-manager->"Window Manager"

- select the theme Default-xhdpi (since Xfce 4.12 - [upgrade instructions for 
14.04](http://ubuntuportal.com/2015/03/how-to-upgrade-xfce-4-10-to-xfce-4-12-in-xubuntu-14-04-and-xubuntu-14-10.html))
- Set the Title Font to 12

- Download the [Widepanel 
Appearance](http://xfce-look.org/content/show.php/Widepanel?content=174213) ** 
in xfce4-settings-manager->"Appearance" select Widepanel
- In the File Manager thunar adapt the preferences:

- Set Iconsize in the sidepanel to "small" or "normal"

xfce4-display-settings command.
display resolution 3840x2400 in 
.config/xfce4/xfconf/xfce-perchannel-xml/displays.xml

-- 
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/CCtyEKU1ZDBH9U-BMo1WNoViZEmVe2aml3HXk1jZi_fLx5QuCTyFm0tIMxtwoeIlXDWGP-zkh_CdfaNrmGB5NjoV2uK_dHaLSQcmUTY11js%3D%40pm.me.


Qubes-HCL-Dell_Inc_-XPS_13_9310_2_in_1-20210328-191641.yml
Description: application/yaml


[qubes-users] Qubes - SSH (soon VNC) into Qubes dom0 - Testers Wanted!

2021-03-27 Thread 'Patrick Schleizer' via qubes-users
Encrypted, authenticated SSH or VNC into Qubes dom0 over an
authenticated Tor onion v3 service.

Only available in Qubes R4.1 and above.

User documentation:
 
https://www.whonix.org/wiki/Remote_Administration#Qubes_-_SSH_or_VNC_into_Qubes_dom0

Source code:
 https://github.com/QubesOS/qubes-remote-support

Development notes:
 https://www.whonix.org/wiki/Dev/Qubes_Remote_Support

Qubes ticket:
 https://github.com/QubesOS/qubes-issues/issues/6364

Qubes repository upload status:
 https://github.com/QubesOS/updates-status/issues/2353

x2go (VNC) support broken until upstream fix for issue flows to Qubes
R4.1 dom0:
 https://github.com/QubesOS/updates-status/issues/2353

Forum discussion:
https://forums.whonix.org/t/qubes-ssh-soon-vnc-into-qubes-dom0-testers-wanted/11330

Credits:
This has been a shared project among Qubes and Whonix project.

- conceptual planning: Patrick Schleizer, Whonix, Marek
Marczykowski-Górecki, Qubes OS, Insurgo
- command line backend utilities, Whonix integration: Patrick Schleizer,
Whonix
- graphical user interface (GUI), Qubes Remote Support GUI: Marta
Marczykowska-Górecka (Qubes OS)

Gratitude is expressed to NLnet for funding this functionality as part
of accessible security project!

-- 
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/176bd8b8-ade0-3a60-1b12-f168719293a1%40whonix.org.


Re: [qubes-users] Whonix uwtwrapper Error using SSH / torsocks

2021-03-26 Thread 'Patrick Schleizer' via qubes-users
'qubebe' via qubes-users:
> Hi,
> 
> I am new to QubesOS, and now wanted to just ssh into my server.
> But if I want to ssh I get the following error message, I didn't changed 
> anything at the standard config (Whonix-ws-15):
> 
> user@host:~$ ssh
> uwtwrapper uwt wrapper ERROR: /usr/bin/ssh.anondist-orig does not exist.
> 
> Could you please help me?
> 


Install ssh.

sudo apt update

sudo apt install openssh-client

-- 
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/3d2bf5fe-cbd7-5012-bf8f-5a8ac7d6554d%40whonix.org.


[qubes-users] HCL - MSI GF63 Thin 9RCX

2021-03-23 Thread 'Eddie' via qubes-users
Hi

I installed Qubes 4.0.4 on my machine by following these instructions :

- Legacy mode in BIOS
- Secure Boot disabled
- added nouveau.modset=0

Wifi and sound work without any fiddling

I'm so happy... I've had this laptop for 1,5 years and had already tried to 
install Qubes several times; could it be because of better support of "newer" 
hardware (i7, 9th generation) in version 4.0.4 ?!

Cheers,
Eddie



-- 
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/lQyR0qhpz9_-F7bxb12i_c2NgclGZ2XeySAAupTU_QWdMDl1rJXvQq0cu159hjHWjIl_hbI-5KjFWXhxWse1ZetVimqikpYsT7SfU-OhIZ4%3D%40protonmail.com.


Qubes-HCL-Micro_Star_International_Co___Ltd_-GF63_Thin_9RCX-20210323-221806.yml
Description: application/yaml


Qubes-HCL-Micro_Star_International_Co___Ltd_-GF63_Thin_9RCX-20210323-221856.cpio.gz
Description: application/gzip


[qubes-users] Re: Fedora 32: dnf update fails

2021-03-22 Thread mmoris via qubes-users
: 127.0.0.1)
- Status code: 404 for 
http://ftp.fi.muni.cz/pub/linux/fedora/linux/updates/32/Everything/x86_64/repodata/c6fada7ba37735a8e9a626b24a79cf1004b84045849914d13e1e7bf71f58db7c-filelists.xml.zck
 
(http://ftp.fi.muni.cz/pub/linux/fedora/linux/updates/32/Everything/x86_64/repodata/c6fada7ba37735a8e9a626b24a79cf1004b84045849914d13e1e7bf71f58db7c-filelists.xml.zck)
 (IP: 127.0.0.1)
- Status code: 404 for 
http://fr2.rpmfind.net/linux/fedora/linux/updates/32/Everything/x86_64/repodata/38f9e903e71072ff56a975d1d81f948bf95c0c00eeff1e176d7896c06f8790a8-primary.xml.zck
 
(http://fr2.rpmfind.net/linux/fedora/linux/updates/32/Everything/x86_64/repodata/38f9e903e71072ff56a975d1d81f948bf95c0c00eeff1e176d7896c06f8790a8-primary.xml.zck)
 (IP: 127.0.0.1)
- Status code: 404 for 
http://mirror.23media.com/fedora/linux/updates/32/Everything/x86_64/repodata/f0314321dc894d96fced1d116292504ec7a5d2347ffa2b9e9db5bbbda4d18c7d-prestodelta.xml.zck
 
(http://mirror.23media.com/fedora/linux/updates/32/Everything/x86_64/repodata/f0314321dc894d96fced1d116292504ec7a5d2347ffa2b9e9db5bbbda4d18c7d-prestodelta.xml.zck)
 (IP: 127.0.0.1)
- Status code: 404 for 
http://ftp.fau.de/fedora/linux/updates/32/Everything/x86_64/repodata/9afb9ab991468ac22370460b83d5b727aeee02ab89154adc9715a1f45b365a69-updateinfo.xml.zck
 
(http://ftp.fau.de/fedora/linux/updates/32/Everything/x86_64/repodata/9afb9ab991468ac22370460b83d5b727aeee02ab89154adc9715a1f45b365a69-updateinfo.xml.zck)
 (IP: 127.0.0.1)
- Status code: 404 for 
http://ftp.nluug.nl/pub/os/Linux/distr/fedora/linux/updates/32/Everything/x86_64/repodata/9afb9ab991468ac22370460b83d5b727aeee02ab89154adc9715a1f45b365a69-updateinfo.xml.zck
 
(http://ftp.nluug.nl/pub/os/Linux/distr/fedora/linux/updates/32/Everything/x86_64/repodata/9afb9ab991468ac22370460b83d5b727aeee02ab89154adc9715a1f45b365a69-updateinfo.xml.zck)
 (IP: 127.0.0.1)
- Status code: 404 for 
http://www.mirrorservice.org/sites/dl.fedoraproject.org/pub/fedora/linux/updates/32/Everything/x86_64/repodata/38f9e903e71072ff56a975d1d81f948bf95c0c00eeff1e176d7896c06f8790a8-primary.xml.zck
 
(http://www.mirrorservice.org/sites/dl.fedoraproject.org/pub/fedora/linux/updates/32/Everything/x86_64/repodata/38f9e903e71072ff56a975d1d81f948bf95c0c00eeff1e176d7896c06f8790a8-primary.xml.zck)
 (IP: 127.0.0.1)
- Status code: 404 for 
https://fr2.rpmfind.net/linux/fedora/linux/updates/32/Everything/x86_64/repodata/9afb9ab991468ac22370460b83d5b727aeee02ab89154adc9715a1f45b365a69-updateinfo.xml.zck
 
(https://fr2.rpmfind.net/linux/fedora/linux/updates/32/Everything/x86_64/repodata/9afb9ab991468ac22370460b83d5b727aeee02ab89154adc9715a1f45b365a69-updateinfo.xml.zck)
 (IP: 127.0.0.1)
- Status code: 404 for 
http://ftp.fi.muni.cz/pub/linux/fedora/linux/updates/32/Everything/x86_64/repodata/38f9e903e71072ff56a975d1d81f948bf95c0c00eeff1e176d7896c06f8790a8-primary.xml.zck
 
(http://ftp.fi.muni.cz/pub/linux/fedora/linux/updates/32/Everything/x86_64/repodata/38f9e903e71072ff56a975d1d81f948bf95c0c00eeff1e176d7896c06f8790a8-primary.xml.zck)
 (IP: 127.0.0.1)
- Status code: 404 for 
http://mirrors.chroot.ro/fedora/linux/updates/32/Everything/x86_64/repodata/9afb9ab991468ac22370460b83d5b727aeee02ab89154adc9715a1f45b365a69-updateinfo.xml.zck
 
(http://mirrors.chroot.ro/fedora/linux/updates/32/Everything/x86_64/repodata/9afb9ab991468ac22370460b83d5b727aeee02ab89154adc9715a1f45b365a69-updateinfo.xml.zck)
 (IP: 127.0.0.1)
Error: Failed to download metadata for repo 'updates': Yum repo downloading 
error: Downloading error(s): 
repodata/38f9e903e71072ff56a975d1d81f948bf95c0c00eeff1e176d7896c06f8790a8-primary.xml.zck
 - Cannot download, all mirrors were already tried without success; 
repodata/c6fada7ba37735a8e9a626b24a79cf1004b84045849914d13e1e7bf71f58db7c-filelists.xml.zck
 - Cannot download, all mirrors were already tried without success; 
repodata/f0314321dc894d96fced1d116292504ec7a5d2347ffa2b9e9db5bbbda4d18c7d-prestodelta.xml.zck
 - Cannot download, all mirrors were already tried without success; 
repodata/9afb9ab991468ac22370460b83d5b727aeee02ab89154adc9715a1f45b365a69-updateinfo.xml.zck
 - Cannot download, all mirrors were already tried without success

-- 
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/18fbf47a01a8d12bb358756510b53ba4%40disroot.org.


[qubes-users] Re: Fedora 32: dnf update fails

2021-03-22 Thread mmoris via qubes-users
/pub/linux/fedora/linux/updates/32/Everything/x86_64/repodata/c6fada7ba37735a8e9a626b24a79cf1004b84045849914d13e1e7bf71f58db7c-filelists.xml.zck)
 (IP: 127.0.0.1)
- Status code: 404 for 
http://fr2.rpmfind.net/linux/fedora/linux/updates/32/Everything/x86_64/repodata/38f9e903e71072ff56a975d1d81f948bf95c0c00eeff1e176d7896c06f8790a8-primary.xml.zck
 
(http://fr2.rpmfind.net/linux/fedora/linux/updates/32/Everything/x86_64/repodata/38f9e903e71072ff56a975d1d81f948bf95c0c00eeff1e176d7896c06f8790a8-primary.xml.zck)
 (IP: 127.0.0.1)
- Status code: 404 for 
http://mirror.23media.com/fedora/linux/updates/32/Everything/x86_64/repodata/f0314321dc894d96fced1d116292504ec7a5d2347ffa2b9e9db5bbbda4d18c7d-prestodelta.xml.zck
 
(http://mirror.23media.com/fedora/linux/updates/32/Everything/x86_64/repodata/f0314321dc894d96fced1d116292504ec7a5d2347ffa2b9e9db5bbbda4d18c7d-prestodelta.xml.zck)
 (IP: 127.0.0.1)
- Status code: 404 for 
http://ftp.fau.de/fedora/linux/updates/32/Everything/x86_64/repodata/9afb9ab991468ac22370460b83d5b727aeee02ab89154adc9715a1f45b365a69-updateinfo.xml.zck
 
(http://ftp.fau.de/fedora/linux/updates/32/Everything/x86_64/repodata/9afb9ab991468ac22370460b83d5b727aeee02ab89154adc9715a1f45b365a69-updateinfo.xml.zck)
 (IP: 127.0.0.1)
- Status code: 404 for 
http://ftp.nluug.nl/pub/os/Linux/distr/fedora/linux/updates/32/Everything/x86_64/repodata/9afb9ab991468ac22370460b83d5b727aeee02ab89154adc9715a1f45b365a69-updateinfo.xml.zck
 
(http://ftp.nluug.nl/pub/os/Linux/distr/fedora/linux/updates/32/Everything/x86_64/repodata/9afb9ab991468ac22370460b83d5b727aeee02ab89154adc9715a1f45b365a69-updateinfo.xml.zck)
 (IP: 127.0.0.1)
- Status code: 404 for 
http://www.mirrorservice.org/sites/dl.fedoraproject.org/pub/fedora/linux/updates/32/Everything/x86_64/repodata/38f9e903e71072ff56a975d1d81f948bf95c0c00eeff1e176d7896c06f8790a8-primary.xml.zck
 
(http://www.mirrorservice.org/sites/dl.fedoraproject.org/pub/fedora/linux/updates/32/Everything/x86_64/repodata/38f9e903e71072ff56a975d1d81f948bf95c0c00eeff1e176d7896c06f8790a8-primary.xml.zck)
 (IP: 127.0.0.1)
- Status code: 404 for 
https://fr2.rpmfind.net/linux/fedora/linux/updates/32/Everything/x86_64/repodata/9afb9ab991468ac22370460b83d5b727aeee02ab89154adc9715a1f45b365a69-updateinfo.xml.zck
 
(https://fr2.rpmfind.net/linux/fedora/linux/updates/32/Everything/x86_64/repodata/9afb9ab991468ac22370460b83d5b727aeee02ab89154adc9715a1f45b365a69-updateinfo.xml.zck)
 (IP: 127.0.0.1)
- Status code: 404 for 
http://ftp.fi.muni.cz/pub/linux/fedora/linux/updates/32/Everything/x86_64/repodata/38f9e903e71072ff56a975d1d81f948bf95c0c00eeff1e176d7896c06f8790a8-primary.xml.zck
 
(http://ftp.fi.muni.cz/pub/linux/fedora/linux/updates/32/Everything/x86_64/repodata/38f9e903e71072ff56a975d1d81f948bf95c0c00eeff1e176d7896c06f8790a8-primary.xml.zck)
 (IP: 127.0.0.1)
- Status code: 404 for 
http://mirrors.chroot.ro/fedora/linux/updates/32/Everything/x86_64/repodata/9afb9ab991468ac22370460b83d5b727aeee02ab89154adc9715a1f45b365a69-updateinfo.xml.zck
 
(http://mirrors.chroot.ro/fedora/linux/updates/32/Everything/x86_64/repodata/9afb9ab991468ac22370460b83d5b727aeee02ab89154adc9715a1f45b365a69-updateinfo.xml.zck)
 (IP: 127.0.0.1)
Error: Failed to download metadata for repo 'updates': Yum repo downloading 
error: Downloading error(s): 
repodata/38f9e903e71072ff56a975d1d81f948bf95c0c00eeff1e176d7896c06f8790a8-primary.xml.zck
 - Cannot download, all mirrors were already tried without success; 
repodata/c6fada7ba37735a8e9a626b24a79cf1004b84045849914d13e1e7bf71f58db7c-filelists.xml.zck
 - Cannot download, all mirrors were already tried without success; 
repodata/f0314321dc894d96fced1d116292504ec7a5d2347ffa2b9e9db5bbbda4d18c7d-prestodelta.xml.zck
 - Cannot download, all mirrors were already tried without success; 
repodata/9afb9ab991468ac22370460b83d5b727aeee02ab89154adc9715a1f45b365a69-updateinfo.xml.zck
 - Cannot download, all mirrors were already tried without success

-- 
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/875cb445364a056380318c0fe2b5d8b5%40disroot.org.


[qubes-users] Re: Fedora 32: dnf update fails

2021-03-22 Thread mmoris via qubes-users
/x86_64/repodata/38f9e903e71072ff56a975d1d81f948bf95c0c00eeff1e176d7896c06f8790a8-primary.xml.zck)
 (IP: 127.0.0.1)
- Status code: 404 for 
http://mirror.23media.com/fedora/linux/updates/32/Everything/x86_64/repodata/f0314321dc894d96fced1d116292504ec7a5d2347ffa2b9e9db5bbbda4d18c7d-prestodelta.xml.zck
 
(http://mirror.23media.com/fedora/linux/updates/32/Everything/x86_64/repodata/f0314321dc894d96fced1d116292504ec7a5d2347ffa2b9e9db5bbbda4d18c7d-prestodelta.xml.zck)
 (IP: 127.0.0.1)
- Status code: 404 for 
http://ftp.fau.de/fedora/linux/updates/32/Everything/x86_64/repodata/9afb9ab991468ac22370460b83d5b727aeee02ab89154adc9715a1f45b365a69-updateinfo.xml.zck
 
(http://ftp.fau.de/fedora/linux/updates/32/Everything/x86_64/repodata/9afb9ab991468ac22370460b83d5b727aeee02ab89154adc9715a1f45b365a69-updateinfo.xml.zck)
 (IP: 127.0.0.1)
- Status code: 404 for 
http://ftp.nluug.nl/pub/os/Linux/distr/fedora/linux/updates/32/Everything/x86_64/repodata/9afb9ab991468ac22370460b83d5b727aeee02ab89154adc9715a1f45b365a69-updateinfo.xml.zck
 
(http://ftp.nluug.nl/pub/os/Linux/distr/fedora/linux/updates/32/Everything/x86_64/repodata/9afb9ab991468ac22370460b83d5b727aeee02ab89154adc9715a1f45b365a69-updateinfo.xml.zck)
 (IP: 127.0.0.1)
- Status code: 404 for 
http://www.mirrorservice.org/sites/dl.fedoraproject.org/pub/fedora/linux/updates/32/Everything/x86_64/repodata/38f9e903e71072ff56a975d1d81f948bf95c0c00eeff1e176d7896c06f8790a8-primary.xml.zck
 
(http://www.mirrorservice.org/sites/dl.fedoraproject.org/pub/fedora/linux/updates/32/Everything/x86_64/repodata/38f9e903e71072ff56a975d1d81f948bf95c0c00eeff1e176d7896c06f8790a8-primary.xml.zck)
 (IP: 127.0.0.1)
- Status code: 404 for 
https://fr2.rpmfind.net/linux/fedora/linux/updates/32/Everything/x86_64/repodata/9afb9ab991468ac22370460b83d5b727aeee02ab89154adc9715a1f45b365a69-updateinfo.xml.zck
 
(https://fr2.rpmfind.net/linux/fedora/linux/updates/32/Everything/x86_64/repodata/9afb9ab991468ac22370460b83d5b727aeee02ab89154adc9715a1f45b365a69-updateinfo.xml.zck)
 (IP: 127.0.0.1)
- Status code: 404 for 
http://ftp.fi.muni.cz/pub/linux/fedora/linux/updates/32/Everything/x86_64/repodata/38f9e903e71072ff56a975d1d81f948bf95c0c00eeff1e176d7896c06f8790a8-primary.xml.zck
 
(http://ftp.fi.muni.cz/pub/linux/fedora/linux/updates/32/Everything/x86_64/repodata/38f9e903e71072ff56a975d1d81f948bf95c0c00eeff1e176d7896c06f8790a8-primary.xml.zck)
 (IP: 127.0.0.1)
- Status code: 404 for 
http://mirrors.chroot.ro/fedora/linux/updates/32/Everything/x86_64/repodata/9afb9ab991468ac22370460b83d5b727aeee02ab89154adc9715a1f45b365a69-updateinfo.xml.zck
 
(http://mirrors.chroot.ro/fedora/linux/updates/32/Everything/x86_64/repodata/9afb9ab991468ac22370460b83d5b727aeee02ab89154adc9715a1f45b365a69-updateinfo.xml.zck)
 (IP: 127.0.0.1)
Error: Failed to download metadata for repo 'updates': Yum repo downloading 
error: Downloading error(s): 
repodata/38f9e903e71072ff56a975d1d81f948bf95c0c00eeff1e176d7896c06f8790a8-primary.xml.zck
 - Cannot download, all mirrors were already tried without success; 
repodata/c6fada7ba37735a8e9a626b24a79cf1004b84045849914d13e1e7bf71f58db7c-filelists.xml.zck
 - Cannot download, all mirrors were already tried without success; 
repodata/f0314321dc894d96fced1d116292504ec7a5d2347ffa2b9e9db5bbbda4d18c7d-prestodelta.xml.zck
 - Cannot download, all mirrors were already tried without success; 
repodata/9afb9ab991468ac22370460b83d5b727aeee02ab89154adc9715a1f45b365a69-updateinfo.xml.zck
 - Cannot download, all mirrors were already tried without success

-- 
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/19a1f2932a3418ea62564e2f6e377f3a%40disroot.org.


[qubes-users] Fedora 32: dnf update fails

2021-03-22 Thread mmoris via qubes-users
-prestodelta.xml.zck
 (IP: 127.0.0.1)
 - Status code: 404 for 
http://ftp.fau.de/fedora/linux/updates/32/Everything/x86_64/repodata/9afb9ab991468ac22370460b83d5b727aeee02ab89154adc9715a1f45b365a69-updateinfo.xml.zck
 (IP: 127.0.0.1)
 - Status code: 404 for 
http://ftp.nluug.nl/pub/os/Linux/distr/fedora/linux/updates/32/Everything/x86_64/repodata/9afb9ab991468ac22370460b83d5b727aeee02ab89154adc9715a1f45b365a69-updateinfo.xml.zck
 (IP: 127.0.0.1)
 - Status code: 404 for 
http://www.mirrorservice.org/sites/dl.fedoraproject.org/pub/fedora/linux/updates/32/Everything/x86_64/repodata/38f9e903e71072ff56a975d1d81f948bf95c0c00eeff1e176d7896c06f8790a8-primary.xml.zck
 (IP: 127.0.0.1)
 - Status code: 404 for 
https://fr2.rpmfind.net/linux/fedora/linux/updates/32/Everything/x86_64/repodata/9afb9ab991468ac22370460b83d5b727aeee02ab89154adc9715a1f45b365a69-updateinfo.xml.zck
 (IP: 127.0.0.1)
 - Status code: 404 for 
http://ftp.fi.muni.cz/pub/linux/fedora/linux/updates/32/Everything/x86_64/repodata/38f9e903e71072ff56a975d1d81f948bf95c0c00eeff1e176d7896c06f8790a8-primary.xml.zck
 (IP: 127.0.0.1)
 - Status code: 404 for 
http://mirrors.chroot.ro/fedora/linux/updates/32/Everything/x86_64/repodata/9afb9ab991468ac22370460b83d5b727aeee02ab89154adc9715a1f45b365a69-updateinfo.xml.zck
 (IP: 127.0.0.1)
Error: Failed to download metadata for repo 'updates': Yum repo downloading 
error: Downloading error(s): 
repodata/38f9e903e71072ff56a975d1d81f948bf95c0c00eeff1e176d7896c06f8790a8-primary.xml.zck
 - Cannot download, all mirrors were already tried without success; 
repodata/c6fada7ba37735a8e9a626b24a79cf1004b84045849914d13e1e7bf71f58db7c-filelists.xml.zck
 - Cannot download, all mirrors were already tried without success; 
repodata/f0314321dc894d96fced1d116292504ec7a5d2347ffa2b9e9db5bbbda4d18c7d-prestodelta.xml.zck
 - Cannot download, all mirrors were already tried without success; 
repodata/9afb9ab991468ac22370460b83d5b727aeee02ab89154adc9715a1f45b365a69-updateinfo.xml.zck
 - Cannot download, all mirrors were already tried without success

-- 
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/d4cc80a09ab946a298b6c329338769e3%40disroot.org.


[qubes-users] HCL - Razer Blade 15 Advanced Model Early 2020 RZ09-0330

2021-03-21 Thread 'Henrik Kramselund Jereminsen' via qubes-users


-- 
Mvh/Best regards

Henrik
—
Henrik Kramselund Jereminsen, Follower of the Great Way of Unix
internet samurai cand.scient CISSP
h...@kramse.org h...@zencurity.dk +45 2026 6000

-- 
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/20210321193645.5512fe86%40zencurity.com.


Qubes-HCL-Razer-Blade_15_Advanced_Model__Early_2020RZ09_033-20210321-193043.yml
Description: application/yaml


[qubes-users] RE: Spoofing CPUID to AppVM?

2021-03-21 Thread 'Null' via qubes-users
Hello,

I am wondering if there is a straightforward way to spoof the CPUID to an 
AppVM, more specifically, to remove the "XenVMMXenVMM" string?

I am aware of these patches:

https://gist.github.com/dylangerdaly/2ec8172116e63fd56feb0cf95f4d5a69
https://gist.github.com/dylangerdaly/74be3f316ce8f0ddfb27b0202aa5ec2d

But was hoping for a solution that did not introduce additional maintenance 
burdens.

I have searched online to no avail.

Many thanks for any answers.

Regards,
N

-- 
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/NbCtGb43XoN6csXEzBLUVpgbA9kFVFrW_RzUoysc5FYuBoaHAaXqUUTLPstnRaybSkJE60dwpNiIaMf_zunPsOYc9LbmnBaMUYax3hAE3Xc%3D%400x00.email.


Re: [qubes-users] Networking issue with sys-whonix, missing vif*

2021-03-19 Thread 'awokd' via qubes-users

Vladimir Lushnikov:

Hello,

Since updating to latest Whonix 15/Qubes R4.1, I am having issues with
sys-whonix not bringing up the virtual interfaces for downstream VMs
correctly. I could find nothing conclusive in the bug tracker but am
hesitant to raise it on qubes-issue in case it only affects me.

The symptoms are as follows:

* AppVMs connected to sys-whonix do not get networking
* There is an incorrect nameserver specified in the AppVM
/etc/resolv.conf (the IP does not match the IP of sys-whonix)
* There are no vif* interfaces in sys-whonix, or they are down and have
no IP address
* There are errors in the logs of sys-whonix like:


Was this a fresh install of R4.1? If so, an issue would probably be the 
best course of action since it's not released yet, so might not have 
been widely encountered. If you upgraded by some other means, try 
uninstalling the various Whonix templates & VMs and reinstalling via the 
Salt commands documented on the Whonix website.


--
- 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/8a9e487c-4918-e9ad-a466-337191d6c28a%40danwin1210.me.


Re: [qubes-users] Replacing the wpa_supplicant wifi daemon with iwd

2021-03-18 Thread 'qtpie' via qubes-users


On 3/18/21 12:46 PM, haaber wrote:
> On 3/3/21 5:19 PM, 'qtpie' via qubes-users wrote:
>> Due to mysterious, unsolvable Wifi issues, I decided to replace the
>> wpa_supplicant wifi daemon with iwd.
>   -- snip --
>> $ dnf remove wpa_supplicant
>> $ echo -e "[device] \nwifi.backend=iwd" | tee -a
>> /etc/NetworkManager/NetworkManager.conf
>> $ systemctl enable iwd.service
>> $ systemctl start iwd.service
>
> interesting. I tried that in my debian-minimal-net but I cannot start
> iwd with systemctl. Errors similar to here
>
>   https://bbs.archlinux.org/viewtopic.php?id=250220
>
> but the proposed "solution" does not work. The thread suggests
>
>   sudo cp /usr/lib/systemd/system/iwd.service /etc/systemd/system/
>
> but that file does simply not exist, so I cannot copy it. So I stopped
> that experiment for the moment. Maybe @unman has a suggestion for a
> well-working debian-based 'minimal' solution without  networkmanager
> and/or   wpa_applicant ?  Best,
>
>

For those who want to stick to NetworkManager, II found out that the

$ systemctl enable iwd.service
$ systemctl start iwd.service

from my initial post, should not be necessary and can cause conflict.
Because NetworkManager is supposed to handle starting iwd, after iwd is
added to the NetworkManager config file.

That networkmanager does not handle iwd correctly, is a known issue with
NetworkManager. We can only wait for it to get updated with future
Fedora releases I guess.
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/101

I am now also curious about non-networkmanager alternatives and their
usability though.

-- 
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/73c466a3-2c9e-6227-343b-be8197d2b618%40disroot.org.


[qubes-users] Re: ANN: Qubes arbitrary network topology

2021-03-16 Thread 'awokd' via qubes-users

Manuel Amador (Rudd-O):

Hello, folks!  I'm here to share this:

https://github.com/Rudd-O/qubes-arbitrary-network-topology 
<https://github.com/Rudd-O/qubes-arbitrary-network-topology>


This software lets you turn your Qubes OS 4.0 machine into an arbitrary 
network topology host. It is ideal to create networks of interconnected 
VMs with arbitrary pathways between them, and minimal effort compared to 
manually setting everything up using xl attach in your dom0 as root.


Thank you, Rudd-O. I've had to suggest to some people in the past they 
use a different virtualization product like Virtualbox if they needed 
more flexible networking, but this might let them continue to use Qubes 
instead.


--
- 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/01d48a87-c265-9fc1-83a4-08cea35f3174%40danwin1210.me.


Re: [qubes-users] Survey from HackerNCoder: Colors in QubesOS

2021-03-16 Thread tetrahedra via qubes-users

On Mon, Mar 15, 2021 at 10:16:04PM +, hackerncoder wrote:
I have created a survey about colors in Qubes, to help understand 
users: Are there too many colors? Too few? What do users associate with 
the colors? what are they used for?


There wasn't any space in the survey for general comments, so let me say 
here: more colors, please! I find it makes the most sense to be able to 
isolate *both* by threat level and theme, and there simply aren't enough 
colors to do that.


Colors are not just about preventing one VM from pretending to be 
another VM.


Colors also really help prevent *user error*, where you accidentally 
confuse e.g your chat window with Mom with the chat window you use for 
communicating with journalistic sources -- and end up asking Mom to get 
undercover footage from North Korea. Woops!


--
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/YFD9hgjWUbvDtUvA%40danwin1210.me.


[qubes-users] Custom LAN Network with dhcpd

2021-03-15 Thread 'Nyx' via qubes-users
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 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/IUbiSSRQZ-eNLCIZh5y-81UZrPRnit3Onx2J81ZIoyhYIs0tFpNLfCPuarHsrZ2WYDKBPYpQlKCXm_-xZ5-rXJfC36oAzaMUB3Sa24YLkyk%3D%40protonmail.com.


[qubes-users] HCL - Ryzen Threadripper 1920x, ASRock X399 Taichi, GeForce GT 710B

2021-03-14 Thread 'followentropy' via qubes-users
Didn't test extensively so far. The computer isn't waking up from hibernation.

Cheers

-- 
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/hWzW9zBg7-KrLFULdfDbqk-wgefpI0Sj82ZEZzG5vUsJ22Xc4xz8EJDCz2lnXqvlM5tkCN2wO3SmXbwPEMj000C02rsOvfLJwYLEPePGfYk%3D%40protonmail.com.


Qubes-HCL-ASRock-X399_Taichi-20210314-225756.yml
Description: Binary data


[qubes-users] Memory issue

2021-03-12 Thread thefifthseason via qubes-users


 The quick: 

 Dom0 Task Manager shows memory usage percent as always increasing.
Closing Virtual Machines does not seem to free up any memory by
displayed memory usage percent. 

 The questions: 

 Are there any advice on what I should do with this situation?Should
I clean out Qubes memory buffer/catch? If so, what safe command should
be used?Or, if that isn’t the issue, what should I look for? What
more information do you good elves need to help the issue? 

 The slow: 

 I noticed this situation a good week ago when I looked at Dom0 task
manager. It showed my memory usage to be around 95%, that is a lot.
The computers total memory capacity is 32gig. My normal memory usage
tend to be around 35-40%, a fairly steady level measured over long
time. After seeing my memory maxing out I attempted to close down one
virtual machine after the other, but it did not appear to make any
difference in terms of freeing up memory. So I decided to restart my
computer and that made everything back to normal—for a little while.
Starting my normal virtual machines and got to the normal memory usage
level. But then it just kept adding on, a disposable machine opened
and closed and the memory usage increased, another virtual machine
opened and the memory increased, closing it did not affect the memory
level. And so it kept adding on more and more memory usage as I did my
normal computing things like browsing and so on. In writing moment
I’ve reached 93% of memory capacity.   

 The extra: 

 Please, treat me as a newbie. Although I’ve been using Qubes OS
for several years (its pretty cool operating system, thank you
creators and maintainers 

-- 
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/20210312201043.070C58106A3%40smtp.hushmail.com.


Re: [qubes-users] Intel 7260 WiFi Problem: Failed to run INIT ucode: -110

2021-03-09 Thread 'awokd' via qubes-users

'nickyfuentez' via qubes-users:


It is a Intel 7260 from a HP ZBook G2. It is using the iwlwifi kernel module 
which upon load will log the failure message block starting with
"Failed to load firmware chunk!"
and ending with
"Failed to run INIT ucode: -110."




Help would be much appreciated. I'm very new to Qubes. My guess is that the 
wifi-adapter uses perhaps some functions that are not avaialble with 
PCI-passthrough? Perhaps some power saving functions or whatnot.


That is a good guess, and same as mine. Many of the Intel adapters are 
not designed to work with pass-through. You can try the permissive mode 
mentioned in https://www.qubes-os.org/doc/pci-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/b1051f28-a8ad-8b96-4bf3-48cbda731673%40danwin1210.me.


Re: [qubes-users] [HCL] ASRock B550 Phantom Gaming 4/ac

2021-03-09 Thread 'awokd' via qubes-users

Vít Šesták:

Hello,
I'm posting HCL report for my computer with this ASRock B550 Phantom Gaming
4/ac and Ryzen 7 5800X. I've few comments:



Short reasoning why I decided for this MoBo: ECC support for a good price.


Interesting.


ASrock's quality is reportedly comparable to ASUS, and those vendors are
the only two who have ECC support on a non-server board. Also, the I've
seen rather compatible ASrock MoBos in the Qubes HCL.


ASUS's quality hasn't been that great from what I've seen (hardware 
design flaws in 2/2 of their mobos I've owned), but haven't heard bad 
things about ASrock. Thanks for the report, might be time for one of my 
systems to get an upgrade.


--
- 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/76ee0b4a-98f7-5d0b-0c6d-d3455d604c5a%40danwin1210.me.


Re: [qubes-users] 4K videos on external monitor lagging like hell

2021-03-09 Thread 'hut7no' via qubes-users
Qubes doesn't use video acceleration as it is less secure.
Mplayer is IMO the best option for video playback in VMs, as it focuses a lot 
on optimizing without using acceleration.
You can also sacrifice some quality for speed with some of these options:
mplayer -vfm ffmpeg -sws 4 -lavdopts 
skiploopfilter=all:fast:gray:lowres=3:threads= 

You can change the default configuration and/or create an alias in either the 
template or the dvm/appvm.
I set dropping frames(g key) to enabled, but change to hard(pressing g again) 
if audio video timing is especially important.
You can also check if assigning more memory and vcpus helps, if you have not 
already.
Launching many qubes, like qubes updater does, can also cause signifigant 
stutter with slow drives in my experience.
Also remember that h264 decodes a lot faster.

-- 
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/20210309172952.GA821%40mail2-dvm.


[qubes-users] Qubes AEM: write protecting BIOS is not possible

2021-03-09 Thread tetrahedra via qubes-users
The [Qubes AEM docs](https://github.com/QubesOS/qubes-antievilmaid) 
recommend:



Some hints: connect the write protect pin on BIOS flash chip to ground
(prevents attacker from booting their own software which would bypass
BIOS protections and overwrite it) and make sure physically accessing
the chip will be tamper-evident by eg. covering the screws holding
laptop body together in glitter and taking high-res photos, then
examining before each use.


However, the given suggestion will do nothing on most laptops, providing 
a false sense of security.


The reason is that many/most BIOS flash chips require the SRWD and block 
protect bits to be set **in software** before the **hardware** write 
protect pins will do anything.


Unfortunately, Flashrom does not currently support setting these bits, 
though there is an open proposal to add support:

https://github.com/flashrom/flashrom/issues/142
https://github.com/flashrom/flashrom/issues/185

--
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/YEagdOwtmnEOZ6PR%40danwin1210.me.


[qubes-users] Intel 7260 WiFi Problem: Failed to run INIT ucode: -110

2021-03-08 Thread 'nickyfuentez' via qubes-users
Hi there!
I've been struggling to get my WiFi-Adapter working. It never has been a 
problem in any other distro, such as fedora, debian or arch, but in Qubes 
something weird is happening.

It is a Intel 7260 from a HP ZBook G2. It is using the iwlwifi kernel module 
which upon load will log the failure message block starting with
"Failed to load firmware chunk!"
and ending with
"Failed to run INIT ucode: -110."
After some research i added the disable_rxq=1 flag to loading iwlwifi using 
qvm-prefs. That was not recognized as the kernel was too old (5.4) so I updated 
the kernel to 5.10 and then the flag was recognized, but it didnt change 
anything. Same messages.

Switching from the fedora template to debian changed nothing, except that I had 
to install firmware-iwlwifi for it to find the appropiate firmware (in the 
sys-net qube)

The name of the firmware being used is: iwlwifi-7260-17.ucode
I have reset the BIOS to default and also tried to change a few WiFI releated 
options which I dont really understand, but to no avail.
Every available virtualisation technology including TXT is enabled in the BIOS.

I tried to add the disable_rxq=1 flag to the xen hypervisor (by adding 
iwlwifi.disable_rxq=1 to the corresponding grub entry) but it didnt change 
anything.

Using HVM or PV did not make a difference either (in the qube Settings for 
sys-net).

The wifi button shows an orange color, indicating it is hard blocked and 
pressing it doesnt change anything, though I believe when I started out it was 
not orange (yesterday), not sure.
installing rfkill inside sys-net and calling "rfkill list all" didnt show 
anything.

Help would be much appreciated. I'm very new to Qubes. My guess is that the 
wifi-adapter uses perhaps some functions that are not avaialble with 
PCI-passthrough? Perhaps some power saving functions or whatnot.

Nicky

-- 
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/hWKGJrHQIpfV-Eg6MHE4KZdwnqQC46C1de3wj-SSXQ_uyhkSqyrpu6vR0n5QE4BWEimvPjY4C1Er3dtrMjP8-lLZ8lXOVf5oYgOOGteFfEs%3D%40protonmail.com.


[qubes-users] Re: Fullscreen Multiple Monitors not possible?

2021-03-06 Thread 'mic...@schefczyk.net' via qubes-users
Thank you very much! The idea does make maximum sense, I think. However, 
without turning on full screen, there is the problem that the window - 
indeed created large enough to cover the full screen - will be truncated by 
the frame decorations. That brings issues particularly with the task bar. 
Once one clicks full screen, the screen gets limited to one monitor (-> 
"full monitor"). As far as I understand, one has the following instruments 
available in Qubes and freerdp:
- allow_fullscreen and override_redirect_protection in guid.conf in dom0
- the trapezoid slider "floatbar" created by xfreerdp 
/floatbar:sticky:off,show:always
As far as I can tell, no combination of these instruments can resolve the 
issue. In Debian, the floatbar does allow maximizing the window across 
multiple monitors, but not in Qubes.

I nice solution might have been to accept the windows decoration and create 
the window slightly smaller (less height would be enough, because the top 
decoration is the main issue. That, however, does not seem to work because 
of freerdp: You need to set "xrfreerdp /multimon" but then you are unable 
to reduce the height. You can set a large screen, but without multimon, it 
does not extend accross monitors. This seems to be an endless cycle.

It would be good to know, if developers intend to change this behavior or 
not. I can accept the security concept of not welcoming fullscreen too 
much. However, when this is fully possible with one monitor but not 
possible with two monitors, that does not seem fully consistent - either or 
would make sense, but the number of monitors should not be the decisive 
factor from a concept standpoint.

Vít Šesták schrieb am Samstag, 6. März 2021 um 22:12:00 UTC+1:

> I guess that the xfreerdp just creates a window that is large enough and 
> positioned in a way that hides the window borders. However, Qubes OS AFAIK 
> does not allow the positioning for security reasons. However, you can do 
> this yourself. It depends on your desktop environment and configuration, 
> there is rough howto for Xfce:
>
> * Adjust the window position by alt+left-click and movement.
> * Adjust the window size by alt+right-click and movement.
> * If needed, make the window always-on-top by Alt+Space and selecting 
> Always on Top.
>
> I am pretty sure this can be automated by xdotool or something similar.
>
> Regards,
> Vit Sestak 'v6ak'
>
> On Saturday, March 6, 2021 at 8:04:32 AM UTC+1 mic...@schefczyk.net wrote:
>
>> Dear All,
>>
>> In QubesOS R4.0, I have two monitors connected to form a large screen 
>> made up by two monitors side by side. I would like to achieve what does 
>> work in Debian, for example, that is a fullscreen window covering the 
>> entire screen (i. e., both monitors). This is particularly useful in 
>> rdp-seccions using freerdp. It can be achieved using:
>>
>> xfreerdp /multimon
>>
>> This leads to a freerdp connection across multiple monitors at leaset in 
>> Debian GNOME.
>>
>> In QubesOS R4.0 it does work in principle. A window as wide as the set of 
>> monitors does get created. However, the fullscreen feature does not work. 
>> As soon as one clicks fullscreen, the window gets confined to one of the 
>> monitors. Of course, I did allow fullscreen as described here: 
>> https://www.qubes-os.org/doc/full-screen-mode/ And of corse, everything 
>> does work well with just one monitor connected. And yes, I do understand 
>> the security concept of normally not covering the entire screen but showng 
>> the window decorations including the VM color.
>>
>> Is there a way to overcome that limitation? If "fullscreen" can be made 
>> to work across physical monitors in general, xfreerdp /multimon should work 
>> as well.
>>
>> Thank you very much!
>>
>> Michael Schefczyk
>>
>

-- 
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/33a6fd49-65ca-4985-bc5e-b5ba2562fb99n%40googlegroups.com.


[qubes-users] Fullscreen Multiple Monitors not possible?

2021-03-05 Thread 'mic...@schefczyk.net' via qubes-users
Dear All,

In QubesOS R4.0, I have two monitors connected to form a large screen made 
up by two monitors side by side. I would like to achieve what does work in 
Debian, for example, that is a fullscreen window covering the entire screen 
(i. e., both monitors). This is particularly useful in rdp-seccions using 
freerdp. It can be achieved using:

xfreerdp /multimon

This leads to a freerdp connection across multiple monitors at leaset in 
Debian GNOME.

In QubesOS R4.0 it does work in principle. A window as wide as the set of 
monitors does get created. However, the fullscreen feature does not work. 
As soon as one clicks fullscreen, the window gets confined to one of the 
monitors. Of course, I did allow fullscreen as described here: 
https://www.qubes-os.org/doc/full-screen-mode/ And of corse, everything 
does work well with just one monitor connected. And yes, I do understand 
the security concept of normally not covering the entire screen but showng 
the window decorations including the VM color.

Is there a way to overcome that limitation? If "fullscreen" can be made to 
work across physical monitors in general, xfreerdp /multimon should work as 
well.

Thank you very much!

Michael Schefczyk

-- 
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/8d373902-5a9c-492f-a752-3c8cb304886en%40googlegroups.com.


Re: [qubes-users] How screwed am I? (corrupt backup files?)

2021-03-05 Thread 'awokd' via qubes-users

Stumpy:

I am trying to figure out how to restore them manually per the qubes 
emergency restore doc page and am getting errors like:


tar: Archive contains ‘Q\352\334\\\275h\274\202B*\275s’ where numeric 
off_t value expected



Can someone explain how bad things are looking from these errors?

If you haven't already, try fully patching the Qubes OS where you are 
attempting the restores.


--
- 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/92a61e67-43c0-5e55-1a96-f4d6731f37ed%40danwin1210.me.


Re: [qubes-users] Migrating to Qubes OS

2021-03-05 Thread 'awokd' via qubes-users

Flex:





1&2: I had a look into that but did not try yet as I was afraid of
breaching the security of dom0, but if it is the only workaround
possible I might take that risk.
Would https://www.qubes-os.org/doc/usb-qubes/#automatic-setup do the same?
Further I am not sure if that will solve the keyboard layout problem or
has a potential to make things worse?




Regarding 1&2 would it be possible to clone the usb-qube and then sort
the usb-controllers to both qubes and giving one usb-controller the
access to dom0 as described in
https://www.qubes-os.org/doc/usb-qubes/#automatic-setup ?



Those automatic setup steps will create a USB qube for you if you chose 
to not do so on install. However, if sounds like you did, so it won't 
help to run again. The manual step I linked to permit an external 
keyboard to dom0 isn't awful from a security perspective, as sys-usb 
still acts as a middleman between the USB hardware and dom0. It does 
open up a class of attacks where if your keyboard gets reprogrammed by 
someone with physical access without your knowledge (or is hopefully not 
wireless), they could maliciously send keystrokes.


Splitting USB controllers between dom0 and sys-usb is entirely possible, 
but is arguably less safe than passing the external keyboard through 
sys-usb, as it exposes dom0 to the USB controller and USB devices 
attached to it.


Not positive either way about the keyboard layout issue, or the others, 
sorry.


--
- 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/eb11f0ac-2f12-eec9-b5ed-53678f9e3ed7%40danwin1210.me.


[qubes-users] Replacing the wpa_supplicant wifi daemon with iwd

2021-03-03 Thread 'qtpie' via qubes-users
Hi,

Due to mysterious, unsolvable Wifi issues, I decided to replace the
wpa_supplicant wifi daemon with iwd. iwd itself is excellent and a
definite improvement over wpa_supplicant. I can't find Fedora working on
this though. In the Fedora 33 template, it currently comes down to:

$ dnf remove wpa_supplicant
$ echo -e "[device] \nwifi.backend=iwd" | tee -a
/etc/NetworkManager/NetworkManager.conf
$ systemctl enable iwd.service
$ systemctl start iwd.service
$ systemctl restart NetworkManager

There are just two integration issues remaining that I hope people can
help me with. I am using the standard Qubes Fedora template, and want to
stay as close to it as possible, so I'm not interested in ditching
NetworkManager unless it is unavoidable.

1. /etc/dbus-1/system.d/org.freedesktop.GeoClue2.conf: this is the only
other file in /etc/ that mentions wpa_supplicant. It contains policy to
allow wpa_supplicant to be used for geolocation. Since I don't care for
geolocation, I just removed it (don't comment it out. But if someone
cares to adapt this to iwd, it would be nice.

2. Occasionally, NetworkManager says 'device not ready' under wifi, and
wifi stops working. It is solved temporarily by ``$ systemctl restart
iwd.service && systemctl restart NetworkManager.service`` in sys-net. I
don't get from the log what the exact issue is though.

--

Resources:
- I used this howto from Josh Stoik as a starter:
https://blobfolio.com/2019/replacing-wpa-supplicant-with-iwd-in-ubuntu-eoan/
- https://wiki.archlinux.org/index.php/Iwd

GeoClue2 policy:

  
    
    

    
    

    

    

    

    
  


-- 
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/a92da205-6c3d-5ae7-3a9e-78ad19cefaaa%40disroot.org.


[qubes-users] Open sourcing my salt configs

2021-03-03 Thread 'keyandthegate' via qubes-users
I've been developing a lot of salt config for myself and I want to start open 
sourcing it so that I can:

- Ask for public security review
- Accept patches
- Help people use Qubes a little better, when I think Qubes supports 
anarchistic praxis and is a force of good in the world

I'm worried about the following things:

- I lose my security through obscurity, which I don't want to do without the 
help of at least one non-amateur code reviewer for anything I publish

- (and I'm not sure if the economics/incentives work out here such that I 
should be paying someone to help me with this or not)
- I don't want to publish anything security sensitive without code review 
because I don't want to harm people

Additionally, I'm not sure how to package salt config via a .deb package. Are 
there any existing examples of this?

As an example of what I want to publish, I've written some config to create a 
private debian package repo vm powered by a YAML file that lets you specify 
sources to download packages (e.g. that are hosted as github releases) and 
verify them via gpg, then provide them to vms. My motivation is towards the 
goal of being able to destroy and recreate my templates from salt at any time, 
because salt is not stateless (unlike e.g. nix or bazel), e.g. if you decide to 
no longer add a package repo, you have to manually remove it from the domain in 
addition to updating the salt config, and you may forget; being able to 
recreate templates solves the otherwise almost intractable problem of knowing 
your templates aren't out of sync; it also means you can exclude templates from 
backups if you're brave, which can save a lot of space.

Another example of some code I may want to publish:
(WARNING: I think this may have a critical security issue of exposing config 
files to domains they don't belong to, but I'm not sure. Would need to 
investigate before publishing)
This fixes TemplateNotFound errors when you try to jinja-include another file 
within a `file.managed` `template.jinja` file.

> # MAINTAIN: Removed when fixed: https://github.com/saltstack/salt/issues/31531
> 'patch salt issue 31531':
> cmd.run:
> - name: |
> if [[ ! -f "$XDG_DATA_HOME"/patched-salt-31531 ]]; then
> cat < sudo sed -i'' "s#if fn_.strip() and fn_.startswith(path):#if fn_.strip() and 
> (fn_.startswith(path) or path == '/'):#" 
> /usr/lib/python3/dist-packages/salt/fileclient.py && \
> if ! grep extra-filerefs /etc/qubes-rpc/qubes.SaltLinuxVM >/dev/null; then 
> sudo sed -i'' "s#salt-ssh#salt-ssh --extra-filerefs salt:///#" 
> /etc/qubes-rpc/qubes.SaltLinuxVM; fi
> CMD
> fi
> sudo mkdir -p "$XDG_DATA_HOME" || exit 1
> sudo touch "$XDG_DATA_HOME"/patched-salt-31531 || exit 1

-- 
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/NTmFFT8PX6ISKTuoQoqTiNW-F2DglyltdvA9x8wO347GSSL_I4S-c74Mbov1E4USGtpiWIpH39AZ-6lT3zzA9Uym9nxrRtGKGl8t_YsP3oE%3D%40protonmail.com.


Re: [qubes-users] Re: Howto grab/capture sound of one VM

2021-03-02 Thread gorki via qubes-users
Am 23.02.21 um 17:25 schrieb Steve Coleman:
> 
> 
> ...
> 
> Not sure exactly what you mean by capture. To play the audio, or record it?
> 
> Look at the pulse audio configuration apps inside that VM. You should be
> able to figure out what device channels are processing sound by looking
> at the audio volume meters inside that VM.
> 
> If recording it is what you want then look for a sound recorder app in
> that VM. If playing the sound is what you want then look at the
> pulseaudio controls in dom0.

I cannot record inside the VM, the app doesn't allow saving the stream.
But the data should somehow pass the Dom0 I guess.
So there (I wish) it should be possible to 'cat < VMsoundIO >
Audiofile.raw" (or similar  )

Just curious
G.



-- 
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/f0f4a9e8-1592-f623-9453-8637e6f02720%40ixls.eu.


Re: [qubes-users] qrexec_timeout does not truly accept 3600

2021-03-02 Thread 'awokd' via qubes-users

Rob Townley:

qvm-prefs vmName qrexec_timeout 3600
does not return an error message.   When read, 3600 is returned.
However, the VM is forcibly stopped after 15 minutes.

1800 works
2700 works
3600 is not honored

How can i get by this so this one VM can do finish its upgrade before
forcibly rebooted?

Think you can disable qrexec with "qvm-features [vmname] qrexec 0". Do 
this on the template. Set back to 1 when done.


--
- 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/38ea9107-5d4d-8042-fbd6-b0777c70a5cc%40danwin1210.me.


Re: [qubes-users] Unable to get VPN to ping out. Unable to set up ProxyVM as sys-vpn

2021-03-02 Thread 'awokd' via qubes-users

roberto re:


I've looked around but I can't seem to find any up-to-date, uncomplicated
step by step guide to get a fail closed, antileak VPN tunnel environment.


https://github.com/QubesOS-contrib/qubes-tunnel

--
- 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/a842f938-57ef-6a87-018f-a23897992a4b%40danwin1210.me.


Re: [qubes-users] trouble with apt-get on dabian

2021-03-02 Thread 'awokd' via qubes-users

Steve Coleman:


Apparently, I need to reinstall a new fedora-33 template baseline and
painstakingly install all these packages one at a time while restarting
Debian-10 to try an 'apt-get update' between package installs. Somewhere
along the way, it will break and whatever I just installed will be the
culprit. I think I'll be doing a lot of cloning of templates creating
checkpoints along the way.


Good find. Hope my suggestions didn't cost you too much time.

Depending how many packages you're talking about, a binary search might 
help- install half of them recursively.


--
- 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/3b78adc2-73b3-b0d2-58ac-f3f1b2227eca%40danwin1210.me.


Re: [qubes-users] Migrating to Qubes OS

2021-03-02 Thread 'awokd' via qubes-users

Flex:

Hello,

migrating from Ubuntu 20.04 to Qubes OS I have still quite a few
problems I ran into and could not solve yet using the documentation etc.

1. I need to use an external USB-Keyboard which is plugged into the
docking station of my X230 Thinkpad. I can connect the Keyboard to one
running VM using sys-usb but this results in a falsely changed keyboard
layout (US instead of DE) and I need to reboot to reset this as the
built in keyboard layout is affected in the same way.

2. Further it would be great to know how to automatically connect to
several selected VM after boot without connecting it directly to dom0 or
if not possible how to connect it to dom0 as I was not able to
understand the many different options mentioned in the documentation etc.

3. The sys-net VPN (PPTP) is not working although the settings are the
same as using Ubuntu, where it connected. Is there a way to get the VPN
up and running?

4. The qubes add on for thunderbird is not compatible with thunderbird
78 is it planned to upgrade it soon?

5. When disconnecting from the docking station to which the 2nd screen
is connected to, the windows are not automatically resized/-grouped so
it is kind of hard to access those invisible on the second screen which
is no longer attached, is there a way to improve this?

That is it for now though I might run in to more issues the coming days.
Hope you can help me especially with the first and 3rd issue as those
are most urgent.

Many thanks!
Flex

For 1 & 2, have you attempted the steps under 
https://www.qubes-os.org/doc/usb-qubes/#manual-setup ?


3 Does your VPN provider support OpenVPN? It's better. If so, 
https://github.com/QubesOS-contrib/qubes-tunnel is probably the best 
approach. Otherwise, try 
https://www.mail-archive.com/qubes-users@googlegroups.com/msg02913.html.


4 Unknown

5 Only fix I can think of might be to switch the desktop from xfce to 
something like i3, but haven't attempted that.

--
- 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/0c183f83-3637-87b0-6dbc-2474328e2439%40danwin1210.me.


Re: [qubes-users] Opening applications using qvm-run

2021-03-01 Thread tetrahedra via qubes-users

On Sun, Feb 28, 2021 at 08:03:47PM +0100, airelemental via qubes-users wrote:

Try:

$ qvm-run --service anon qubes.StartApp+janondisttorbrowser
$ qvm-run --service untrusted qubes.StartApp+firefox
$ qvm-run --service personal qubes.StartApp+thunderbird


Thanks, that did the trick!

Two questions:

1. Is there any way to pass arguments?

2. for some applications the name I have to pass to qubes.StartApp is 
not the same as the command used on the command line (e.g 
`janondisttorbrowser` instead of `torbrowser`). How do I find out the 
correct name for an arbitrary application? is it always the same as the 
name of the .desktop file in /usr/share/applications?


--
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/YDwdXuakojz8gdV8%40danwin1210.me.


Re: [qubes-users] Opening applications using qvm-run

2021-03-01 Thread tetrahedra via qubes-users

On Sun, Feb 28, 2021 at 11:49:04PM +, unman wrote:
It's not Torbrowser specific for me, that was just an example using a 
Whonix

Workstation VM. (it does work as stated -- I did test it)

In actuality I want to launch specific applications (that launch fine using
applications menu) from a dom0 script, but the only way I can find to launch
them without blocking the script execution is using gnome-terminal. And that
opens an extra (unneeded) terminal window.



Do you have the same problem with non Whonix qubes?
I dont use Whonix, and dont have this problem with any of my other
template based qubes.


Yes. But the other solution (qubes.StartApp) did the trick.

--
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/YDz2ddi0Rrp6RuLw%40danwin1210.me.


Re: [qubes-users] Opening applications using qvm-run

2021-02-28 Thread airelemental via qubes-users
Feb 27, 2021, 14:16 by qubes-users@googlegroups.com:

> I'm trying to figure out how to open applications in VMs from dom0 using 
> qvm-run, and how to do so without blocking the terminal in dom0.
>
> For example:
> ```
> $ qvm-run anon "torbrowser qubes-os.org"
> Running 'torbrowser qubes-os.org' on anon
>
> ```
>
> The above command sucessfully launches Tor Browser in the `anon` VM, but I 
> can't run another command in the same dom0 terminal window until Tor Browser 
> (in the VM) finishes (exits).
>
> Alternately I can do something like
> ```
> $ qvm-run anon "gnome-terminal -- torbrowser qubes-os.org"
> ```
> but that leaves a terminal window running in the `anon` VM.
>
>
Try:

$ qvm-run --service anon qubes.StartApp+janondisttorbrowser
$ qvm-run --service untrusted qubes.StartApp+firefox
$ qvm-run --service personal qubes.StartApp+thunderbird

-- 
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/MUe0b60--3-2%40tutanota.com.


Re: [qubes-users] Opening applications using qvm-run

2021-02-28 Thread tetrahedra via qubes-users

On Sat, Feb 27, 2021 at 11:57:32PM +, unman wrote:

Is this Torbrowser specific? Because it doesn't block with other
programs (or at least doesn't seem to do so for me).
On what is the "anon" qube based? How is it configured to run torbrowser
with no path?


It's not Torbrowser specific for me, that was just an example using a 
Whonix Workstation VM. (it does work as stated -- I did test it)


In actuality I want to launch specific applications (that launch fine 
using applications menu) from a dom0 script, but the only way I can find 
to launch them without blocking the script execution is using 
gnome-terminal. And that opens an extra (unneeded) terminal window.



--
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/YDuQ6zSFT31ESepY%40danwin1210.me.


[qubes-users] Opening applications using qvm-run

2021-02-27 Thread tetrahedra via qubes-users
I'm trying to figure out how to open applications in VMs from dom0 using 
qvm-run, and how to do so without blocking the terminal in dom0.


For example:
```
$ qvm-run anon "torbrowser qubes-os.org"
Running 'torbrowser qubes-os.org' on anon

```

The above command sucessfully launches Tor Browser in the `anon` VM, but I 
can't run another command in the same dom0 terminal window until Tor Browser 
(in the VM) finishes (exits).


Alternately I can do something like
```
$ qvm-run anon "gnome-terminal -- torbrowser qubes-os.org"
```
but that leaves a terminal window running in the `anon` VM.

I've also tried all the usual variations on `nohup`, `disown`, `&`, and the 
like, but none of them seem to do the trick.


Any ideas?

--
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/YDpUQIsYO4hJyRt4%40danwin1210.me.


[qubes-users] Opening applications using qvm-run

2021-02-27 Thread tetrahedra via qubes-users
I'm trying to figure out how to open applications in VMs from dom0 using 
qvm-run, and how to do so without blocking the terminal in dom0.


For example:
```
$ qvm-run anon "torbrowser qubes-os.org"
Running 'torbrowser qubes-os.org' on anon

```

The above command sucessfully launches Tor Browser in the `anon` VM, but 
I can't run another command in the same dom0 terminal window until Tor 
Browser (in the VM) finishes (exits).


Alternately I can do something like
```
$ qvm-run anon "gnome-terminal -- torbrowser qubes-os.org"
```
but that leaves a terminal window running in the `anon` VM.

I've also tried all the usual variations on `nohup`, `disown`, `&`, and 
the like, but none of them seem to do the trick.


Any ideas?

--
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/YDjjDMmmzJzTkk0J%40danwin1210.me.


[qubes-users] HCL-Dell Precision 5520

2021-02-27 Thread 'joe renotse' via qubes-users


-- 
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/141877827.384049.1614445354101%40mail.yahoo.com.


Qubes-HCL-Dell_Inc_-Precision_5520-20210227-102502.yml
Description: application/yaml


[qubes-users] HCL - Dell XPS 9570

2021-02-25 Thread 'Ben Moody' via qubes-users
HCL reports attached for Qubes 4.04 and 4.1.

Some prior reports report these machines are working - I've noted a few caveats 
to that which may be useful for anyone considering one.

2018 XPS 9570.
* 4k screen
* 32gb RAM
* Samsung 970 Evo

4.0.4
Installer requires mapbs, noexitboot, modprobe.blacklist=nouveau commented out 
as per UEFI troubleshooting page.

Installation completes fine and system boots, however var/log/Xorg.0.log shows 
'Reverting to software rendering' even with i915.alpha_support=1. Tried various 
combinations of drivers and options, no result. Issue detailed here 
(https://github.com/QubesOS/qubes-issues/issues/5244) indicates this is likely 
due to fc25 Mesa drivers.

High CPU load, poor performance (input latency).

Upgrade to kernel 5.10 produces significant graphical glitching and does not 
resolve problem.

4.1

Installer boots and completes, system boots out of the box. Wifi, etc all 
working.
Software rendering issue from 4.0.4 is fixed.

However - I experienced some input and gui lag which seemed to me to be in 
excess of that I experience on my current Qubes machine - an X1 Carbon 5th 
running 4.0.4 w/ i3. Attempting to resolve this highlighted a few issues:

Refresh rate in AppVMs
Refresh rate issue mentioned here applies 
(https://github.com/QubesOS/qubes-issues/issues/3175) - I worked around this by 
using xrandr to set mode to 2560x1440. I didn't research Qubes experience with 
HiDPI screens before purchasing because I'm an idiot.

Intel GPU issues
Journalctl produces the following error in substantial volumes:
"dom0 kernel: [drm:gen8_de_irq_handler.isra.0 [i915]] *ERROR* Fault errors on 
pipe A: 0x0080"

Intel pstate issues
Journalctl --boot reports:
intel_pstate: CPU model not supported
Xenpm can't retrieve CPU info as per this issue: 
https://github.com/QubesOS/qubes-issues/issues/4604
modprobe xen_acpi_processor allows xenpm to retrieve info andcpufreq-average 
indicates scalings is working, but I'm not sure if that information means much 
- there's a substantial discussion in the linked issue on the reporting of cpu 
info - I may be misinterpreting - read it for yourself and reach your own 
conclusions if you have better understanding of these issues than me.
hypervisor.log shows 6 CPUs identified.

App performance

On both kernels 5.4 and 5.10, in Fedora 32 and 33 templates, and on 2 clean 
installs, Libreoffice runs extremely poorly - significant performance issues 
working with an 8 page document (text only). Tried LO 6.4 and 7.1, from RPM and 
flatpak. Tried clean template installs. No improvement.

MOCS failed to program

Upgraded to Kernel 5.10 to see if any improvement on noted issues. Journalctl 
produces the msg "Failed to program MOCS register; expect performance issues". 
See here for some info: https://github.com/QubesOS/qubes-issues/issues/6397.

5.10 produces significant graphical artefacts on dom0 menus.

I've experimented with different driver settings (modesetting, intel, glamor, 
etc, etc), no impact.

Also tried blacklisting Nouveau on an existing installation and reinstalling 
with Nouveau blacklisted from installer - no change. On a normal installation 
system seems to find and default to the uhd 630 anyway.

Conclusion

I feel like this machine as it is doesn't seem to represent any noticeable 
performance improvement over my X1 Carbon 5th, which runs Qubes extremely well 
and without issue. Maybe it's an issue with my specific hardware - not sure.

Not sure what the cause is of these issues - similar painful experiences to 
those associated with every other hybrid graphics workstation type laptop in 
the HCLs. Begs the question of why I thought it was a good use of time to try...

Did give me an opportunity to try the 4.1 alpha though - super impressive. Very 
excited for the release and upgrade on my X1. If anyone wants an XPS 9570, let 
me know...

Ben

-- 
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/98TBMzQfjgXJmUKBxUjMQ64cIgMagVMA5turlXOGxzR_aCb44KaX13t-ESpxMjEo9VUMeYTmUgLiDxIYSvK5LNu5KXWAZeJFjrCsF_50tnM%3D%40protonmail.com.


Qubes-HCL-Dell_Inc_-XPS_15_9570-20210226-102904.yml
Description: application/yaml


Qubes-HCL-Dell_Inc_-XPS_15_9570-20210225-192445.yml
Description: application/yaml


Qubes-HCL-Dell_Inc_-XPS_15_9570-20210225-192445.cpio.gz
Description: application/gzip


Re: [qubes-users] trouble with apt-get on dabian

2021-02-24 Thread 'awokd' via qubes-users

Steve Coleman:


I installed the stock Debian-10 rpm yesterday and it also fails to update
using the default proxy. The whonix templates based on Debian work because
they are using a different update vm.

I really don't have a clue how all the Fedora templates work using the
exact same default update proxy while the Debian ones do not. I have not
made any deliberate custom modifications to any of the update settings, but
something obviously changed.

My suspicion is on the receiving side proxy configuration in sys-firewall
but I don't know how to debug that. With the TERM setting being complained
about I am wondering how this proxy is being launched without a full set of
environment variables. This error text is in red, as coming through the
pipe, so its on the other side, not in the template itself. The update pipe
is not a terminal afaik so I don't know why the proxy would be complaining
it doesn't know the terminal type. But then why does the Fedora update
still work and Debian not using the exact same update gateway. Very odd.

I agree, sounds like something broken in sys-firewall given your other 
UpdateVM is working. You could change your templates to use the same 
UpdateVM as Whonix if you wanted to confirm. Otherwise, there's nothing 
special about the sys-firewall AppVM. If you don't mind recreating any 
firewall rules, try creating a new AppVM and confirm you don't get that 
TERM warning at the terminal. Next, change anything that points to 
sys-firewall for networking to the new one, and make it your new UpdateVM?


--
- 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/d4fc7d1d-e1b2-0f10-a127-a104fe627636%40danwin1210.me.


Re: [qubes-users] trouble with apt-get on dabian

2021-02-23 Thread 'awokd' via qubes-users

Steve Coleman:

I have a somewhat confusing issue with debian-10 updates and would like any
suggestions on where to look.

All my fedora templates update just fine. Dom0 updates but it gives some
errors through the return pipe.

can't get terminal type, defaulting to vt100.
please set the TERM env variable.


I wonder if your Debian template is messed up somehow, and/or your 
Updatevm (can be determined by looking at qubes-prefs). If you open a 
regular terminal session on either, do you get that same warning? If so, 
you could temporarily switch your UpdateVM's template to Fedora and 
attempt an update. If the issue still occurs and it's with the template 
itself, there's probably a more subtle fix but I would switch my AppVMs 
over to Fedora, delete & reinstall a fresh copy of the Debian template, 
then switch them back.


--
- 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/689ffe55-e72e-8383-ed16-49fcd24f77bc%40danwin1210.me.


Re: [qubes-users] General setup questions from Noob

2021-02-21 Thread 'awokd' via qubes-users

Alexander Reseneder:

Hello qubes-users,

im a Noob to Linux, but i wanna try it because it seems that it offers
great security advantages over a normal "bare metal" System or Windows.

However i have some problems, like setup my network printer properly, i


Have you seen 
https://github.com/Qubes-Community/Contents/blob/master/docs/configuration/network-printer.md?



Also i ran into that problem that my Authy client installed over Snap
stopped working, terminal prints out that:


IIRC, both Authy and Snap can be challenging to run under Qubes, but I 
don't remember what it takes. Think others have managed though. Try 
searching this mailing list for "Authy"?



Also i want to update my old InsydeH20 Bios, because it is the first
release version and my PC is from 2016, they were several ME Firewall
patches and also drivers for touchpad for linux were delivered etc. etc.
and Microcode Update. I tried updating with FreeDOS from SD Card, but it
seems that my Bios does nut support booting from SD card. My Bios version
is V1.12 this is the first release..


Try a USB drive instead, maybe.


I have Qubes installed in Legacy Mode. Is it possible to switch it to UEFI
mode? Because maybe it will boot much faster? The problem is i cannot turn
off Secure Boot in my Bios by default, i am even not able to turn
hyperthreading of, because the InsydeH20 stock bios looks like from a
Kindergarden.


Qubes will install itself the same way you booted the install media- 
legacy in this case. PCs from 2016 have iffy UEFI support, so if you're 
functioning under Legacy boot now I wouldn't change it. The boot times 
on both seem roughly equivalent, so that shouldn't be a major reason to 
switch.


--
- 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/14ecb3af-4e70-e58e-411a-903c5ae5bd3b%40danwin1210.me.


Re: [qubes-users] Configuration Files, Nested Virtualization

2021-02-21 Thread 'awokd' via qubes-users

my kay:


So I have been trying to enable nested virtualization so that I can run
Virtualbox in a Windows HVM, but I am running into issues. I was trying to
follow the instructions from the Xen wiki, as well as this
https://groups.google.com/g/qubes-devel/c/UzO0BsIfIow/m/C7us11XHAwAJ post,
but I am new to Qubes so I didn't realize that it no longer uses individual
config files for AppVMs. I found this
https://groups.google.com/g/qubes-users/c/K8lfxC8xdp4/m/jGwC-gxnBAAJ
thread, and am now trying to create a custom config file in
/etc/qubes/templates/libvirt/xen/by-name based off of the default xen.xml
file, but I am not sure how to edit the file in a way that would allow
nested virtualization in my windows vm.

A somewhat more recent thread: 
https://www.mail-archive.com/qubes-users@googlegroups.com/msg29743.html. 
Editing config files would be the easy part; I think you'd have to 
recompile Qubes to enable nested virtualization. I used to run 
Virtualbox on Windows as well, but instead converted my workflows/VMs 
over to Qubes only. Do you have a specific use case that requires 
Virtualbox?


--
- 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/4e6401a2-e601-3680-7a5b-79357e08d1d1%40danwin1210.me.


Re: [qubes-users] debian 10 VM: "Unable to init server: Could not connect: Connection refused."

2021-02-20 Thread qubes-lists
solved: the disk of the template was full

-- 
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/a354f75a-4aea-302a-8100-8b2637586263%40riseup.net.


[qubes-users] debian 10 VM: "Unable to init server: Could not connect: Connection refused."

2021-02-20 Thread qubes-lists
Hi,

Since today I'm unable to start any GUI application (testing with 
gnome-terminal and xterm) within a debian 10 based AppVM:

In Qubes Manager the VM shows the green state icon.

To collect logs I connected via 'xl console':

sudo xl console debian-10:

journalctl -f



Log output:

qrexec-agent[599]: executed user:QUBESRPC qubes.VMShell dom0 pid 24766
qrexec-agent[24766]: pam_unix(qrexec:session): session opened for user user by 
(uid=0)
systemd[1]: Started Session c17 of user user.
qubes.VMShell-dom0[24775]: .[0;1;39m.[0;1;31m.[0;1;39mUnable to init server: 
Could not connect: Connection refused.[0m
qrexec-agent[24766]: pam_unix(qrexec:session): session closed for user user
qrexec-agent[599]: send exit code 1
qrexec-agent[599]: pid 24766 exited with 1
qrexec-agent[599]: eintr
systemd[1]: session-c17.scope: Succeeded.

The last updates according to /var/log/apt/history.log within that VM:

Start-Date: 2021-02-01
Commandline: /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold -o 
DPkg::Options::=--force-confdef dist-upgrade
Install: linux-headers-4.19.0-14-amd64:amd64 (4.19.171-2, automatic), 
linux-headers-4.19.0-14-common:amd64 (4.19.171-2, automatic), 
linux-image-4.19.0-14-amd64:amd64 (4.19.171-2, automatic)
Upgrade: linux-libc-dev:amd64 (4.19.160-2, 4.19.171-2), 
linux-compiler-gcc-8-x86:amd64 (4.19.160-2, 4.19.171-2), 
linux-image-amd64:amd64 (4.19+105+deb10u8, 4.19+105+deb10u9), 
linux-headers-amd64:amd64 (4.19+105+deb10u8, 4.19+105+deb10u9), lightning:amd64 
(1:78.6.0-1~deb10u1, 1:78.7.0-1~deb10u1), thunderbird:amd64 
(1:78.6.0-1~deb10u1, 1:78.7.0-1~deb10u1), linux-kbuild-4.19:amd64 (4.19.160-2, 
4.19.171-2)



Any help to further debug or solve this issue is greatly appreciated.

-- 
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/a481cfc2-248d-b408-8650-babcb09bf4c6%40riseup.net.


[qubes-users] HCL - Dell Latitude 3330

2021-02-19 Thread 'p-trenz' via qubes-users
Hey

I did a fresh install and updated everything what was possible over the ''Qubes 
Update Widget''.
After that i generated the HCL report over the terminal like it says on your 
website.

I'm a complete newbie to qubes but all i saw and heard from it was awesome! You 
are really doing important work here! Thanks to all of you :)

Best
Phil

-- 
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/hQzzLcd0YNlcBbrNtHpyROxJz8AHA_3AXZmEFsdhWajG5f3kGBzy4xb35DYCdXyop6OERhoiH55zZLS8-d2Q5yv-2x7vhnMB0gpB-jusLzQ%3D%40protonmail.ch.


Qubes-HCL-Dell_Inc_-Latitude_3330-20210219-205102.yml
Description: application/yaml


Re: [qubes-users] How to use USB Devices in Qubes?

2021-02-19 Thread 'awokd' via qubes-users

Data Eight:


*The usb mouse is working well after fresh install only. Afterwards, that
is second time when the system is powered on, the usb mouse is not
functioning. Only touchpad is working. *I have four usb port & all are
getting power. *But when I connect any usb devices (both use mouse and usb
blocked devices-external hard disks, they are not listed or prompted with
their corresponding names under the connected-devices-widget.*

I have tried installing OS with and without selecting sys-usb qube check
box. That is separate qube for USB devices (sys-usb) and same qube for both
net and usb devices (sys-net). The same problem exists in both of these
ways .


Check the file and settings mentioned in 
https://www.qubes-os.org/doc/usb-qubes/#auto-enabling-a-usb-mouse.


--
- 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/90d54f4a-18ba-d1b9-e8a0-5e10c39bd393%40danwin1210.me.


Re: [qubes-users] Re: dom0: no space left on device / Qubes partition size?

2021-02-19 Thread 'awokd' via qubes-users

Tray G:

hey , i need your help with qubes and installing partition on the usb to
save files.. do you do it on the windows while you download Qubes in the
terminal or once your first running qubes ?


If you're talking about creating a USB drive to install Qubes, see 
https://www.qubes-os.org/doc/installation-guide/#copying-the-iso-onto-the-installation-medium.


If you want to format a USB drive for use with Qubes once you have it 
installed, it will be most straightforward to format it from Qubes. 
There are some Microsoft FAT/NTFS formats Linux can work with out of the 
box, but you have to add support for others it does not, which you can 
avoid by formatting under Qubes/Linux in the first place.


--
- 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/7ea700b6-9e0e-8020-ecaf-063e66b9121b%40danwin1210.me.


Re: [qubes-users] I'm looking for a laptop with these requirements

2021-02-19 Thread 'awokd' via qubes-users

qubeslaptop via qubes-users:

I'm looking for a laptop like this

hardware kill switches
100% free
Qubes works

Do you know of any laptops like this one?

I'm not aware of any laptops that meet all the criteria, and have looked 
as well. Closest I could get was flashing Coreboot to a Lenovo G505s, 
but you would have to hack in your own kill switches and the controller 
chip isn't 100% free.


--
- 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/d1efcce3-cf12-fec6-6d2b-8b72e0e27512%40danwin1210.me.


[qubes-users] HCL - Lenovo 20RYS0M200 (T490 10th-gen)

2021-02-17 Thread 'Kevin O'Gorman' via qubes-users
Hi all,

Installed 4.0.3 on a 10th-gen Lenovo T490 - went well with a few hiccups:

- Networking:
  - network devices had to be detached and reattached with `
--persistent --option no-strict-reset=True` on sys-net
  - wifi chipset not supported by default kernel (5.4.88) - fixed by
installing kernel-latest-qubes-vm in dom0 and switching sys-net to use
5.10.8
  - occasionally have to restart sys-net after waking laptop from sleep
mode to re-enable wifi

- Video:
  - installed kernel-latest as part of troubleshooting networking, which
resulted in weird graphical behaviour where windows were only repainted
when the mouse cursor moved. Downgraded back to default kernel,
behaviour went away
  - there is a barely noticeable vertical glitch down the middle of the
screen, where it looks like pixel brightness is increased for
alternating columns? Tried increasing VRAM in both the BIOS and in dom0,
no effect.

Everything else seems fine so far. With the tweaks above this machine
works fine with Qubes.


K.

-


-- 
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/4372a427-b35a-ec0a-2a57-924f3257a059%40freedom.press.


Qubes-HCL-LENOVO-20RYS0M200-20210217-095456.yml
Description: application/yaml


[qubes-users] Howto grab/capture sound of one VM

2021-02-13 Thread qubes via qubes-users
Dear Qubes-Users,

how can I grab/capture the audio-output of one VM?

It should be possible in Dom0 somehow.

Thanks a lot in advance for any hint
G.


-- 
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/a4e463c7-fe58-9ef6-1b16-b73201b45645%40ixls.eu.


[qubes-users] HCL - Lenovo Thinkpad P15v (20TQ004AFR)

2021-02-12 Thread 'Vincent Bernaud [FR]' via qubes-users
Hi,

After hours trying to troubleshoot a black screen before the installer shows up 
(Xen is relinquishing VGA console) on R4.0.3, I tried the R4.0.4-rc2 and 
everything works fine (except for the TPM not found and bluetooth) without 
tweaking the boot config.

Ethernet networking works well but Wifi requires a kernel > 5.8 (Intel AX201) 
to work.

Otherwise, suspend, sound, brightness, usb-c (thunderbolt), mic and camera are 
working out of the box.

Vincent

-- 
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/MN2PR15MB3613C3E9C45528D82E04EC729C8B9%40MN2PR15MB3613.namprd15.prod.outlook.com.


Qubes-HCL-LENOVO-20TQ004AFR-20210212-101446.yml
Description: Qubes-HCL-LENOVO-20TQ004AFR-20210212-101446.yml


Re: [qubes-users] kernel crashes (?) 5.10.13

2021-02-09 Thread 'awokd' via qubes-users

haaber:

I am testing the above xen kernel. I experience random freezes of the
system, with no significant "last words" in the logs, if it is not many
many  qmemman notices like these (sorry for the length). Is this a known
issue?? Any hints to stabilite the system?   Cheers!


Anything in the Xen log (xl dmesg)? Some other debugging tips if it is 
Xen freezing are listed at the beginning of 
https://wiki.xenproject.org/wiki/Debugging_Xen before the stuff about 
Xenstore, and https://wiki.xenproject.org/wiki/Xen_Serial_Console to 
capture Xen oops messages. Not sure if there's a more state of the art 
way to do it. You might also want to mention it in 
https://github.com/QubesOS/updates-status/issues for the specific kernel 
you're testing.


--
- 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/ae52a0bf-585c-46e7-aa59-c0a5529f1bc4%40danwin1210.me.


[qubes-users] I'm looking for a laptop with these requirements

2021-02-09 Thread qubeslaptop via qubes-users
I'm looking for a laptop like this

hardware kill switches
100% free
Qubes works

Do you know of any laptops like this one?

-- 
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/9e3d72c7fc5b4a88160bef2391eeb593.squirrel%40danielas3rtn54uwmofdo3x2bsdifr47huasnmbgqzfrec5ubupvtpid.onion.


Re: [qubes-users] No sound in XPS9310

2021-02-08 Thread 'awokd' via qubes-users

Rama McIntosh:


fedora 33 5.10 kernel supports much more devices and audio works in the
upstream fedora on both the 9700 and 9310 dells.  I'll see if I can get a
patch into qubes the upstream kernel modules which fedora has added or at
the minimum the SOF stuff in the patch.   Then all our audio will just work
with qubes.


Thanks for jumping in, Rama. It's difficult to troubleshoot hardware 
without hands-on.


--
- 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/88c05757-d26e-b0f6-3255-e13be0d578c6%40danwin1210.me.


Re: [qubes-users] qubes-split-browser issues

2021-02-08 Thread 'taran1s' via qubes-users




Rusty Bird:

taran1s:

Rusty Bird:

Anything interesting in 'sudo journalctl' on
the DisposableVM?



Can you navigate me how to open the terminal in the active dispvm please?


In the Domains Widget (system tray Q button), there's 'Run Terminal'
inside the disp1234 submenu.


Sorry, in the Domains Widget there is no active disp12... available. I 
can see the dispvm only in the Qube Manager.




The logs in the *persistent* VM would be relevant too:

 journalctl -t qubes.StartApp+split-browser-dom0 \
-t qubes.StartApp+split-browser-safest-dom0







- At the end, if I save a bookmark in the disp VM TB, launched from
the surfer VM, the bookmark doesnt survive the killing of the disp
VM and is not available from the another disp VM launched from the
surfer VM.


Did you use the hotkeys? Ctrl-d to save a persistent bookmark, and
Alt-b to open the persistent bookmarks list. Other methods (like
clicking the star outline in the address bar, etc.) unfortunately
won't work.



Yes I did. Clicking ctrl-d saves the bookmark with blue Saved to library!
popup in the active TB dispVM. alt-b opens up the bookmarks menu and I can
see the bookmark. It doesn't but survive the reboot.


Ah, for some reason the hotkeys aren't intercepted. Can you start a
new Split Browser, and post the full contents of Tor Browser's Browser
Console? (Ctrl-Shift-j)


split-browser-safest

[02-08 11:25:56] Torbutton NOTE: Initializing security-prefs.js
[02-08 11:25:56] Torbutton NOTE: security-prefs.js initialization complete
Content Security Policy: Couldn’t parse invalid host 'wasm-eval'
[Exception... "Component returned failure code: 0x80520001 
(NS_ERROR_FILE_UNRECOGNIZED_PATH) [nsIXPCComponents_Utils.readUTF8URI]" 
 nsresult: "0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH)"  location: 
"JS frame :: resource://gre/modules/L10nRegistry.jsm :: 
L10nRegistry.loadSync :: line 661"  data: no] 14 L10nRegistry.jsm:661:19
Bootstrapped manifest not allowed to use 'resource' directive. 
chrome.manifest:2

Content Security Policy: Couldn’t parse invalid host 'wasm-eval'
[Exception... "Component returned failure code: 0x80520001 
(NS_ERROR_FILE_UNRECOGNIZED_PATH) [nsIXPCComponents_Utils.readUTF8URI]" 
 nsresult: "0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH)"  location: 
"JS frame :: resource://gre/modules/L10nRegistry.jsm :: 
L10nRegistry.loadSync :: line 661"  data: no] L10nRegistry.jsm:661:19

Content Security Policy: Couldn’t parse invalid host 'wasm-eval'
[Exception... "Component returned failure code: 0x80004001 
(NS_ERROR_NOT_IMPLEMENTED) [nsIAppStartup.secondsSinceLastOSRestart]" 
nsresult: "0x80004001 (NS_ERROR_NOT_IMPLEMENTED)"  location: "JS frame 
:: resource:///modules/BrowserGlue.jsm :: 
_collectStartupConditionsTelemetry :: line 1743"  data: no] 
BrowserGlue.jsm:1743:9

Error: setevents stream -> 510 Command filtered tor-control-port.js:237:19
[02-08 11:25:59] Torbutton NOTE: no SOCKS credentials found for current 
document.
Unchecked lastError value: Error: Could not establish connection. 
Receiving end does not exist. store.js:135

a11y.sitezoom - Unknown scalar.
[02-08 11:26:02] Torbutton WARN: Your Tor Browser is out of date.
Key event not available on GTK2: key=“u” modifiers=“accel shift” 
id=“torbutton-new-identity-key” browser.xhtml
Key event not available on some keyboard layouts: key=“r” 
modifiers=“accel,alt” id=“key_toggleReaderMode” browser.xhtml
Key event not available on some keyboard layouts: key=“i” 
modifiers=“accel,alt,shift” id=“key_browserToolbox” browser.xhtml


--
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/453e9c0c-60d0-2271-81d2-82f8ca72d424%40mailbox.org.


Re: [qubes-users] No sound in XPS9310

2021-02-08 Thread 'awokd' via qubes-users

Fabrizio Romano Genovese:


I installed qubes on a Dell XPS9310. I was using kernel 5.4.90 and sound
was working, but wi-fi did not. So I upgraded to kernel 5.10.13 and now I
have both wifi and sound not working :D

It seems that the sound issues are due to a problem with driver
sof-audio-pci.
In this thread: https://groups.google.com/g/qubes-users/c/Fa65-e8vqdM it
turns out another user was having a similar problem with a dell 9700, which
was apparently solved. Indeed in the thread it is said:

Audio works (with kernel 5.10 and attached kernel base-config patch  +
latest 1.6.1 sof-bin firmware https://github.com/thesofproject/sof-bin and
alsa-ucm-config files.   see
https://blog.fts.scot/2020/07/04/dell-xps-2020-how-to-get-audio-working-on-linux/
for alsa ucm config ).

Unfortunately, I am not technically skilled enough to really understand the
fix. Does it mean that I have to download kernel 5.10 (from were?), apply
the patch provided in the thread (how?), include firmware and config files
(how?) and then compile and install?
As you can see I don't really have a specific question, and I'm more in
search of a few clarifications to understand how to apply an apparently
already available solution. :)


Per https://groups.google.com/g/qubes-users/c/Fa65-e8vqdM, are you 
running Qubes 4.1? That might be the first place to start. It implements 
audio in a separate VM, which might automagically resolve the issue or 
at least make for a more easily implemented solution. In that case, 
you'll want your VM's kernel to be the latest, so in dom0 do sudo 
qubes-dom0-update kernel-qubes-vm-latest (from memory). See if the audio 
driver loads in the audio VM. If not, it gets more complex.


You could convert it to an HVM which would allow you to recompile the 
kernel internal to the VM using standard Linux procedures- check 
documentation for the distribution you're using. If you didn't want to 
convert to HVM, I think you would have to build a kernel for dom0 first 
per 
https://www.mail-archive.com/qubes-users@googlegroups.com/msg10886.html, 
then package for VM usage with 
https://www.qubes-os.org/doc/managing-vm-kernel/#installing-different-vm-kernel-based-on-dom0-kernel 
(note I haven't attempted this before).




--
- 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/f0e56ef8-445a-ac71-534c-a97e8444f8ed%40danwin1210.me.


Re: [qubes-users] No sound in XPS9310

2021-02-08 Thread 'awokd' via qubes-users

Fabrizio Romano Genovese:


I installed qubes on a Dell XPS9310. I was using kernel 5.4.90 and sound
was working, but wi-fi did not. So I upgraded to kernel 5.10.13 and now I
have both wifi and sound not working :D

It seems that the sound issues are due to a problem with driver
sof-audio-pci.
In this thread: https://groups.google.com/g/qubes-users/c/Fa65-e8vqdM it
turns out another user was having a similar problem with a dell 9700, which
was apparently solved. Indeed in the thread it is said:

Audio works (with kernel 5.10 and attached kernel base-config patch  +
latest 1.6.1 sof-bin firmware https://github.com/thesofproject/sof-bin and
alsa-ucm-config files.   see
https://blog.fts.scot/2020/07/04/dell-xps-2020-how-to-get-audio-working-on-linux/
for alsa ucm config ).

Unfortunately, I am not technically skilled enough to really understand the
fix. Does it mean that I have to download kernel 5.10 (from were?), apply
the patch provided in the thread (how?), include firmware and config files
(how?) and then compile and install?
As you can see I don't really have a specific question, and I'm more in
search of a few clarifications to understand how to apply an apparently
already available solution. :)


Per https://groups.google.com/g/qubes-users/c/Fa65-e8vqdM, are you 
running Qubes 4.1? That might be the first place to start. It implements 
audio in a separate VM, which might automagically resolve the issue or 
at least make for a more easily implemented solution. In that case, 
you'll want your VM's kernel to be the latest, so in dom0 do sudo 
qubes-dom0-update kernel-qubes-vm-latest (from memory). See if the audio 
driver loads in the audio VM. If not, it gets more complex.


You could convert it to an HVM which would allow you to recompile the 
kernel internal to the VM using standard Linux procedures- check 
documentation for the distribution you're using. If you didn't want to 
convert to HVM, I think you would have to build a kernel for dom0 first 
per 
https://www.mail-archive.com/qubes-users@googlegroups.com/msg10886.html, 
then package for VM usage with 
https://www.qubes-os.org/doc/managing-vm-kernel/#installing-different-vm-kernel-based-on-dom0-kernel 
(note I haven't attempted this before).


--
- 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/5d493b9c-fb1b-2221-5a02-d43d9d0e7f5e%40danwin1210.me.


Re: [qubes-users] Include ath11k in kernel 5.10

2021-02-07 Thread 'awokd' via qubes-users

Fabrizio Romano Genovese:


I tried, but nothing changes. My card is still read as "unassigned class".
Do you know if adding support to QEMU is in the works by any chance? I
don't mind waiting, but it would be nice to have at least a vague idea of
the time windows we are looking at (months? years?).


It sounded like the author of that other thread was looking into writing 
support, but it probably is not a simple matter so I would guess a year 
minimum for the code to be developed (if he decides to proceed) then 
pushed through the ecosystem.


--
- 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/0cd1c146-c928-f271-f936-af901e9a5367%40danwin1210.me.


Re: [qubes-users] Include ath11k in kernel 5.10

2021-02-06 Thread 'awokd' via qubes-users

Fabrizio Romano Genovese:

Yes, I managed to get 5.10.13-1 working. The things that do not work at the
moment are:
- Wifi (AX500, according to google a notorious throublemaker), that is
still detected as unassigned both in sys-net and dom0.


Check out this thread: 
https://www.mail-archive.com/qubes-devel@googlegroups.com/msg04757.html. 
Looks like there's a limitation in QEMU that makes it unable to 
passthrough multiple MSI vectors on a device, so driver upgrades will 
not help. You could try disabling them and see if it reverts to old 
style interrupts with the following:


qvm-prefs sys-net kernelopts "nopat iommu=soft swiotlb=8192 pci=nomsi"

Qvm-shutdown sys-net and start it again and test. If it doesn't help, 
repeat the above command less the pci=nomsi option. Only option at that 
point is to wait until appropriate support is added to QEMU then Xen & 
Qubes, or to switch to a USB wifi device (but search on this list, etc. 
to find one known to work with Qubes).



- Sound (must be a problem with the driver, sof-audio-pci
- Sleep (no idea what the problem may be, but sometimes fixing wifi
improves this too)

The closest thing to what I need is this:
https://groups.google.com/g/qubes-users/c/Fa65-e8vqdM which fixed audio for
XPS9700 (I have XPS9310), but not wifi, even if the drivers were included
in the kernel.


Mind starting a new thread for these two issues, or pointing me towards 
one if you already have? They are a bit off-topic from the thread title 
of ath11k.


--
- 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/5e1702ea-0f25-6bf1-f192-f9feb5837f9c%40danwin1210.me.


Re: [qubes-users] installing Trezor wallet on qubes

2021-02-06 Thread 'awokd' via qubes-users

Alaa Ashkar:


*in sys-usb:*

sudo vim /usr/local/etc/qubes-rpc/trezord-service

add this line:
socat - TCP:localhost:21325

but i couldnt find the path /usr/local/etc/qubes-rpc/ in sys-usb (in
terminal), so i couldnt create the file and add the line into it, i tried
both in the root and the normal user.


Path doesn't exist on mine either. Try creating the directory first 
with: "sudo mkdir /usr/local/etc/qubes-rpc".


--
- 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/eb64283f-fb89-de7d-71c5-4127c065b979%40danwin1210.me.


Re: [qubes-users] qubes-split-browser issues

2021-02-06 Thread 'taran1s' via qubes-users




Rusty Bird:

taran1s:

- TB opens up in disp-VM whonix-ws-15-disp.


In a VM named like disp1234 though, right?


Right.




The welcome page is not Whonix Welcome Page as normally when I open
the TB in the disp VM directly, but instead it opens up the About
Tor welcome page. Is this intended?


Yes, so far so good.

I've configured about:tor as the homepage, because Tor Browser has
been plagued by a bunch of obscure bugs on first startup (which should
be every startup for DisposableVMs) when it's blank or a file:// URL.


- TB opens up in the Security Level: Standard, instead of Safest, as
mentioned in the name of the link (Split Browser (TB Security level:
Safest). [...]



- once I close the TB, the disp VM remains active and needs to be
stopped manually.


Those two are strange. Anything interesting in 'sudo journalctl' on
the DisposableVM?


Can you navigate me how to open the terminal in the active dispvm please?




- At the end, if I save a bookmark in the disp VM TB, launched from
the surfer VM, the bookmark doesnt survive the killing of the disp
VM and is not available from the another disp VM launched from the
surfer VM.


Did you use the hotkeys? Ctrl-d to save a persistent bookmark, and
Alt-b to open the persistent bookmarks list. Other methods (like
clicking the star outline in the address bar, etc.) unfortunately
won't work.


Yes I did. Clicking ctrl-d saves the bookmark with blue Saved to 
library! popup in the active TB dispVM. alt-b opens up the bookmarks 
menu and I can see the bookmark. It doesn't but survive the reboot.





This behavior is the same if I execute split-browser in the
terminal, or through the GUI as Split Browser or as Split Browser
(TB Security level: Safest).


So 'split-browser --safest' also opens up on Standard?


Both open on Standard and don't kill the dispvm once switched off. It 
needs to be stopped manually.




Hmm, maybe try with a freshly created DisposableVM template instead of
whonix-ws-15-disp? I'm definitely interested in debugging this.

Rusty

>
>

--
Kind regards
taran1s

gpg: 12DDA1FE5FB39C110F3D1FD5A664B90BD3BE59B3

--
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/d530f9a2-ac29-c0ef-f39b-83670a22839e%40mailbox.org.


Re: [qubes-users] BIG instability problems of qubes

2021-02-06 Thread 'awokd' via qubes-users

haaber:


- The last upgrade removed my last 4.9 xen kernel which would work fine
(how can I get that one back??) so I switched to 5.10 directly. The last
one braught by update won't work: under 5.10.11 kernel, NO WAY to boot a
debian-vm. Journalctl says:


You may be able to get the old kernel back by specifying its version 
number with something like "dnf install kernel-4.19.155-1.pvops.qubes". 
Not entirely positive on the syntax or if it will work or further break 
your system.


--
- 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/4f17329f-2f58-76e9-60c2-892daaa59b00%40danwin1210.me.


Re: [qubes-users] Re: Firefox unresponsive script

2021-02-06 Thread 'awokd' via qubes-users

Shawn Creighton:

Those unresponsive script errors in Firefox don't happen to anyone else?
It's happening so often now I am about to reinstall the system and use
Brave instead.


Not here. Try Firefox LTR if you aren't already?

--
- 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/0fe1cce1-3da9-6811-b08c-a2f66d727e4f%40danwin1210.me.


Re: [qubes-users] kernel version mismatches

2021-02-06 Thread 'awokd' via qubes-users

Rob Townley:

Kernel version numbers seem off, way off in some VMs and templates.

Mainly, that /boot/initramfs does not does not match uname -r.

uname -r vs ls /boot/initramfs*  vs cat /proc/version vs cat /etc/os-release

OK dom0: 5.4.88-1.qubes, 5.4.88-1.qubes,  5.4.88-1.qubes, 4.0

BAD vm: 5.4.88-1.qubes, 5.10.11-100.fc32, 5.4.88-1.qubes, 32

BAD vmTemplate: 5.4.88-1.qubes, 5.10.11-100.fc32, 5.4.88-1.qubes, 32


I'm not sure what /proc/version shows on "normal" Linux vs. uname -r, 
but maybe check what kernel the BAD vm or template is set to use on its 
advanced tab?


--
- 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/f0d3ac27-0a90-0b0c-28fd-8d3bfa0e4a18%40danwin1210.me.


  1   2   3   4   5   6   7   8   9   10   >