The easy way would be to install the Network-Manager and set the Cloned Mac
Address to Random,
or you can also change it per Script with Macchanger
You can try
sudo apt remove NetworkManager
sudo apt update
sudo apt install NetworkManager
sudo apt upgrade --fix-missing
It works fine here
--
Y
On Acer Aspire 717-72G
I plugged in an USB-Stick with Qubes 4.0.3 formatted by Rufus in DD-Mode.
It shows the Boot Sequence and displays Text like normal.
Right before displaying the installer it stays on Black Screen.
Last Text Message was: Xen is relinquishing VGA console
Need Help here
--
I have recently set up a vpn gateway qube according to the instructions as
listed [here](https://www.qubes-os.org/doc/vpn/). I have now gone to set up the
MAC Anonymization and have a question and a problem both.
Firstly the linked page wrote specifically not to include the network manager.
But
Hi,
I just downloaded the latest updates (incl. dom0 updates)... shortly
after installing them I saw a notification "Device () available" twice
and then maybe 2-3 minutes later "Device () removed" twice.
Any idea what this was? ... is this connected to the update? How would I
investigate?
/Sven
- On Feb 25, 2020, at 3:46 PM, Chris Laprise tas...@posteo.net wrote:
> On 2/25/20 4:12 PM, donov...@unseen.is wrote:
>> Specifically, I issue the "|$ sudo qubes-dom0-update
>> qubes-template-debian-10"and I get red lettering and "error could not
>> delete old database at
>> /var/lib/qubes/
On 2/25/20 4:12 PM, donov...@unseen.is wrote:
Specifically, I issue the "|$ sudo qubes-dom0-update
qubes-template-debian-10"and I get red lettering and "error could not
delete old database at
/var/lib/qubes/dom0-updates/home/user/.rpmold." where changes
if I repeat the command and tha
All,
This is interesting. My original installation of Qubes had Debian 9. I upgraded
it to Debian 10 following the Qubes documentation. No issues at all. In
learning and working with Qubes I found I needed more drive space, so I deleted
Debian. Having installed secondary storage for AppVMs and
Hello Qubers,
'Wyng' is a backup program I've been working on for a while that can
quickly backup "thin LVM" storage, the kind Qubes uses by default:
Link -
https://github.com/tasket/wyng-backup
Some ideas behind Wyng are:
* Backups shouldn't require re-scanning all data to find changes.
*
Is it necessary to connect to a Microsoft account when installing and using
Microsoft Office 365 (in a Win 10 HVM) or is it somehow possible to bypass this
requirement, and if so how ?
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscr
How to change the keys for secure copy and paste between VM’s ?
I have tried to change the keys in this file: etc/qubes/guid.conf to Ctrl +
Alt + C and Crtl + Alt + V But that didn’t work. Maybe because it isn’t
possible to use the Alt key here as it isn’t listed as a “valid modifier key
na
tir. 25. feb. 2020 kl. 14.09 skrev A E :
> tir. 25. feb. 2020 kl. 13.16 skrev A E :
>
>> tir. 25. feb. 2020 kl. 13.02 skrev A :
>>
>>> A way to download Windows 10 Pro manually and install it.
>>>
>>> I haven’t managed to download Windows 10 Pro by using the file
>>> “download-windows.sh”. So inst
Are there any security vulnerabilities that come with TLP ? Does it improve
battery life on Qubes ? Should it be only installed in dom0
--
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
Why not make it possible to stretch a HVM window so it can be easily resized to
the users need instead of only predetermined sizes ?
For example to view the content of two different HVM’s on the same screen.
Therefore, if it can be done, I suggest to make it possible.
--
You received this mess
tir. 25. feb. 2020 kl. 13.16 skrev A E :
> tir. 25. feb. 2020 kl. 13.02 skrev A :
>
>> A way to download Windows 10 Pro manually and install it.
>>
>> I haven’t managed to download Windows 10 Pro by using the file
>> “download-windows.sh”. So instead I downloaded Windows 10 Pro manually and
>> ran
tir. 25. feb. 2020 kl. 13.31 skrev A E :
> tir. 25. feb. 2020 kl. 13.26 skrev A E :
>
>> man. 24. feb. 2020 kl. 20.13 skrev A E :
>>
>>> man. 24. feb. 2020 kl. 14.12 skrev A E :
>>>
ons. 19. feb. 2020 kl. 15.51 skrev A E :
> tor. 13. feb. 2020 kl. 00.24 skrev M E :
>
>> søn.
tir. 25. feb. 2020 kl. 13.26 skrev A E :
> man. 24. feb. 2020 kl. 20.13 skrev A E :
>
>> man. 24. feb. 2020 kl. 14.12 skrev A E :
>>
>>> ons. 19. feb. 2020 kl. 15.51 skrev A E :
>>>
tor. 13. feb. 2020 kl. 00.24 skrev M E :
> søn. 26. jan. 2020 kl. 23.12 skrev 'Elliot Killick' via qub
man. 24. feb. 2020 kl. 20.13 skrev A E :
> man. 24. feb. 2020 kl. 14.12 skrev A E :
>
>> ons. 19. feb. 2020 kl. 15.51 skrev A E :
>>
>>> tor. 13. feb. 2020 kl. 00.24 skrev M E :
>>>
søn. 26. jan. 2020 kl. 23.12 skrev 'Elliot Killick' via qubes-users <
qubes-users@googlegroups.com>:
tir. 25. feb. 2020 kl. 13.02 skrev A :
> A way to download Windows 10 Pro manually and install it.
>
> I haven’t managed to download Windows 10 Pro by using the file
> “download-windows.sh”. So instead I downloaded Windows 10 Pro manually and
> ran the script afterwards.
>
> You can follow these s
A way to download Windows 10 Pro manually and install it.
I haven’t managed to download Windows 10 Pro by using the file
“download-windows.sh”. So instead I downloaded Windows 10 Pro manually and ran
the script afterwards.
You can follow these steps to do it the same way as I did it:
1) Open
On 2/24/20 7:17 PM, ncmy...@gmail.com wrote:
Thank you for your kind attention.
I want to make clear that in each case, the new kernel has worked
fine once I persuaded my BIOS to boot it. The problem is always
that, after each kernel upgrade, the BIOS no longer recognizes any
bootable partition,
20 matches
Mail list logo
