Re: [qubes-users] Qubes Won't Boot with 4.19.125-1 Kernel

[qubes via qubes-users]

On 6/26/20 10:14 PM, Qubes wrote:
> On 6/26/20 9:49 PM, qubes via qubes-users wrote:
>> On 6/13/20 5:36 PM, pudding wrote:
>>> I updated dom0 from the security-testing repo today due to the new CPU
>>> hardware bug. After finishing update and rebooting my laptop, it is
>>> stuck on the black screen forever, and will not load the LUKS decryption
>>> screen.
>>> ..
>>
>> Same problem on Lenovo t460 but "standard" repo/update.
>>
>>
>>
> That is a real problem. I guess it is game over without a backup.
> 

As pudding said, you can boot the old kernel, thank spaghettimonster.
But what is the real cause of the problem?
Can I do something about it or will the next Dom0-Update fix this
problem? Shall I reinstall the .125-Kernel?
Or - worst case scenario - will newer kernels stop working on this
laptop in the future anyway?


> You should be able to get your files off of the disk. I am sure I read a
> procedure in the documentation to mount the encrypted volume elsewhere
> to recover your data. I have not checked if it is possible to decrypt
> the drive while connected elsewhere, whether that is internal or
> connected externally with USB. Or even booted with live media or
> something like tinycore.
> 

-- 
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/b2d93c51-9676-119e-7696-a1c7bae39c29%40ixls.eu.

Re: [qubes-users] qubes installation problem on MS-16R3

['Radu' via qubes-users]

Hi 

Thank you for your reply

The laptop is a MS-16R3 model from MSI
CPU : Intel i7-9750H @ 2.60 GHz
6 Cores / 12 Threads
Processor Stepping : 0x906EA
RAM 16 GB DDR4
Wifi : Intel Wireless-AC 9560

Here is the output from dmesg : https://pastebin.com/9fmRMRJc

Here are the logs :
- anaconda.log : https://pastebin.com/fqGVt6m3
- program.log : https://pastebin.com/TY1Dn3U3
- storage.log : https://pastebin.com/sFXWz4bX
- syslog : https://pastebin.com/CLFYs8sg
- X.log : https://pastebin.com/0EYPDXfF 
- packaging.log and sensitive-info.log are empty

As for BIOS settings, I've seen advice here on disabling ACPI. 
Looking in the BIOS, under the Advances tab, there is an option called "C 
states", that is enabled; it enables/disables CPU Power Management, 
allowing the CU to go to C states when it's not 100% utilized.  Disabling 
it doesn't change anything for me.

Thanks for any help or advice

Best regards,
Radu
On Monday, June 22, 2020 at 3:05:23 AM UTC-4 Jarrah wrote:

> > I'm having this installation issue when trying to Install Qubes on a MSI 
> > Laptop
> Can we get a little more info on the laptop? CPU, GPU, etc.
> > [image: qubes_error.png]
> > How should I find out how to continue the installation (if there is any 
> > chance) ?
>
> Could you provide output of `dmesg` in a terminal while installing?
> (ctl-alt-f2 for TTY2) Also have a look at the logs in `/tmp/` and
> `/var/log/`, specifically the Xorg logs.
>
> If you need to get a file off, the installer will detect and allow you
> to mount another USB drive to copy them to.
>
>

-- 
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/78f60ccd-014e-4c50-b556-4df5f4ddd5ean%40googlegroups.com.

Re: [qubes-users] Qubes Won't Boot with 4.19.125-1 Kernel

['awokd' via qubes-users]

Qubes:
> On 6/26/20 10:17 PM, 'awokd' via qubes-users wrote:
>>> Should be able to boot with an older kernel.
>>> https://www.qubes-os.org/doc/software-update-dom0/#changing-default-kernel
>>>
> 
> That requires decrypting and booting, but the boot failing and you going
> to a recovery screen from where you can change to an older kernel. You
> cannot change anything while it is encrypted.
> 
/boot is not encrypted, and can be edited by booting the computer from
another OS. Xen.cfg is straight-forward to edit. Grub.cfg can also be
edited, but I don't know what changes to make if you haven't enabled
submenus previously.

-- 
- 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/9bef6aa7-fbf6-e4f9-6bec-439210a17f2e%40danwin1210.me.

Re: [qubes-users] Qubes Won't Boot with 4.19.125-1 Kernel

[Qubes]

On 6/26/20 10:17 PM, 'awokd' via qubes-users wrote:

Should be able to boot with an older kernel.
https://www.qubes-os.org/doc/software-update-dom0/#changing-default-kernel


That requires decrypting and booting, but the boot failing and you going 
to a recovery screen from where you can change to an older kernel. You 
cannot change anything while it is encrypted.


--
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/142bd106-9794-b0f4-c397-3c334e4eec77%40ak47.co.za.

Re: [qubes-users] Qubes Won't Boot with 4.19.125-1 Kernel

['awokd' via qubes-users]

Qubes:
> On 6/26/20 9:49 PM, qubes via qubes-users wrote:
>> On 6/13/20 5:36 PM, pudding wrote:
>>> I updated dom0 from the security-testing repo today due to the new CPU
>>> hardware bug. After finishing update and rebooting my laptop, it is
>>> stuck on the black screen forever, and will not load the LUKS decryption
>>> screen.
>>> ..
>>
>> Same problem on Lenovo t460 but "standard" repo/update.
>>
>>
>>
> That is a real problem. I guess it is game over without a backup.
> 
> You should be able to get your files off of the disk. I am sure I read a
> procedure in the documentation to mount the encrypted volume elsewhere
> to recover your data. I have not checked if it is possible to decrypt
> the drive while connected elsewhere, whether that is internal or
> connected externally with USB. Or even booted with live media or
> something like tinycore.
> Should be able to boot with an older kernel.
https://www.qubes-os.org/doc/software-update-dom0/#changing-default-kernel

-- 
- 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/fd40d8c7-f112-ae66-62e7-bccf530d3b85%40danwin1210.me.

Re: [qubes-users] Qubes Won't Boot with 4.19.125-1 Kernel

[Qubes]

On 6/26/20 9:49 PM, qubes via qubes-users wrote:

On 6/13/20 5:36 PM, pudding wrote:

I updated dom0 from the security-testing repo today due to the new CPU
hardware bug. After finishing update and rebooting my laptop, it is
stuck on the black screen forever, and will not load the LUKS decryption
screen.
..


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




That is a real problem. I guess it is game over without a backup.

You should be able to get your files off of the disk. I am sure I read a 
procedure in the documentation to mount the encrypted volume elsewhere 
to recover your data. I have not checked if it is possible to decrypt 
the drive while connected elsewhere, whether that is internal or 
connected externally with USB. Or even booted with live media or 
something like tinycore.


--
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/076387b3-c3b6-9b97-fd25-e75557607fbd%40ak47.co.za.

[qubes-users] missing usb device support after update

['Max Andersen' via qubes-users]

Hi everyone,

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

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

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

Any help appreciated

Sincerely

Max


-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/a12ee9a9-de8f-ccfe-3825-0d34aba35a4a%40militant.dk.

Re: [qubes-users] Qubes Won't Boot with 4.19.125-1 Kernel

[qubes via qubes-users]

On 6/13/20 5:36 PM, pudding wrote:
> I updated dom0 from the security-testing repo today due to the new CPU
> hardware bug. After finishing update and rebooting my laptop, it is
> stuck on the black screen forever, and will not load the LUKS decryption
> screen. 
> ..

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



-- 
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/322bc337-d01d-12ae-0c42-7966af2737ff%40ixls.eu.

[qubes-users] Re: Qubes OS and clonezilla

[didier . pelligra]

I cannot put NVME in SATA mode, nor can I clone disk to disk as I have to 
go through an intermediate image. I tried a LOT of clonezilla options and I 
was already familiar with clonezilla so I don't think any option can help 
me here.

Anyway I ended up setting up a PXE server and deploying Qubes from there, 
along with a kickstart file and configuration scripts.

Thanks

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/a87ca0c0-3618-45b2-8083-67e1719395a5o%40googlegroups.com.

Re: [qubes-users] How to split into two gateways

['awokd' via qubes-users]

'Matt Drez' via qubes-users:
>> Are you sure the second NIC works under Qubes, even by itself? Also, if
>> it's dual ports on a single card, try adding a separate physical NIC card.
> 
> Great thinking! That was one of the first things I have tried. And just to 
> clarify the first NIC is integrated on the mobo and the second one is was 
> added later into a pci slot. Both are single port NICs. 
> 
Might have missed it then, so the second NIC works by itself if you
assign it to the original netvm? If not, the drivers for it may not be
installed/loading correctly. Check sudo journalctl inside netvm for
messages relating to the NIC's init.

-- 
- 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/93858191-1cbb-c3d7-fde9-9b88b80eaf68%40danwin1210.me.

Re: [qubes-users] Qubes OS and clonezilla

['Matt Drez' via qubes-users]

> > > > Hi,
> > > > Has anyone had any luck with cloning a crypted Qubes installation using
> > > > Clonezilla?
> > > > Even using DD the clone just won't boot
> > > > Thanks

I had no problem cloning an encrypted Qubes (nvme to nvme). I used the advanced 
mode.Make sure you chose disk to disk. That's maybe the 2nd questions it asks.  

-- 
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/CxmJ3NEmkX3fGarPY2LnXVLbYfARkXGqmrCgKZBTTUQb18c94-eKFVu4xVzSDivrzFe9MA3ScuETmz8vAg-gZsOcbfJwHnbq6Zce9MPHsrQ%3D%40pm.me.


publickey - mattdrez@pm.me - 0x8196D0F4.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] How to split into two gateways

['Matt Drez' via qubes-users]

> Are you sure the second NIC works under Qubes, even by itself? Also, if
> it's dual ports on a single card, try adding a separate physical NIC card.

Great thinking! That was one of the first things I have tried. And just to 
clarify the first NIC is integrated on the mobo and the second one is was added 
later into a pci slot. Both are single port NICs. 

-- 
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/VguPWyl0aKo3mFMqPu3FfUUWe7XL2zimAoKvpIt90grYDPB8Vmz3lfWtqw4pe7DAmv3hX0_0eANfvH1W1Lvw_e2ey5Tk-Jpqd4c9PUkOYzk%3D%40pm.me.


publickey - mattdrez@pm.me - 0x8196D0F4.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] How to split into two gateways

['awokd' via qubes-users]

'Matt Drez' via qubes-users:
>> Try just doing the passthrough first. If you can get the NICS to show up
>> in `lspci` in the two sys-nets and configure networking so you can ping
>> out.
>>
> 
>> Command to attach the NIC: `qvm-pci attach sys-net2 dom0:`.
>>
> 
>> PCI-address can be found in the output of `qvm-pci`.
> 
> Those are the exact steps I tried but no luck. 
> 
> 
> I have no problem passing the NIC to the gw and it shows up with lspci but it 
> won't acquire an IP. The "funny" thing is that as soon as the sys-net starts 
> the green light goes out on the the NIC. If I issue an `ip addr` command I 
> cannot even see its MAC. 
> 
> 
> I even tried connecting the second NIC to a completely different network and 
> router but made no difference. 
> 
Are you sure the second NIC works under Qubes, even by itself? Also, if
it's dual ports on a single card, try adding a separate physical NIC card.

-- 
- 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/65aa0552-99d1-a195-60ac-3807934d10d5%40danwin1210.me.

Re: [qubes-users] Updating Linux and Whonix

[max via qubes-users]

fredag den 26. juni 2020 kl. 17.06.22 UTC+2 skrev E. Foster:
>
>
> None the less, I am still a little worried about what I did during the 
> upgrade process.  Because, I can't seem to have any peripheral programs 
> such libre office or other in an accessible or visible manner.  ( Currently 
> working on the installs).   There are a lot of programs available for quick 
> install but once you believe you installed them.  I can't find them in any 
> drop down menu.  Perhaps, I did something wrong.  
>

Whatever programs you need in your AppVM's, needs to be installed in your 
template VM's, the AppVM's are based on. Then you have to "refresh" the 
menu, becuase you might not want everything in the menu. That is mentioned 
here:https://www.qubes-os.org/doc/managing-appvm-shortcuts/

However, I am still working on the Zoom install, hopefully, I can figure 
> out how to upgrade to fedora 31, ---snip
>

This might work if you change 30 with 31: 
https://www.qubes-os.org/news/2019/05/30/fedora-30-template-available/ or 
follow the guide mentioned earlier:
On Thursday, June 25, 2020 at 6:12:03 PM UTC, dhorf-hfr...@hashmail.org 
wrote:
>
> fedora 30 is unsupported. 
> you should install fedora 31 or 32 first. 
> https://www.qubes-os.org/news/2020/04/30/fedora-31-template-available/ 
> 
>  
>

Sincerely
Max

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/d9eab084-37d9-4713-9a54-cd7ca30f1cfbo%40googlegroups.com.

Re: [qubes-users] Qubes OS and clonezilla

['awokd' via qubes-users]

didier.pelli...@gmail.com:
> Hi,
> 
> I'm using EFI and a NVME SSD.
> 
> Here is a screenshot of the error
> 
> [image: IMG_20200618_164119.jpg]
> 
> 
> 
> 
> Le mercredi 17 juin 2020 23:22:49 UTC+2, awokd a écrit :
>>
>> didier@gmail.com : 
>>> Hi, 
>>>
>>> Has anyone had any luck with cloning a crypted Qubes installation using 
>>> Clonezilla? 
>>>
>>> Even using DD the clone just won't boot 
>>>
>>> Thanks 
>>>
>> Should work if you are using legacy BIOS boot on both source & 
>> destination. UEFI boot might need a command on the destination system to 
>> add the new boot source, something like efibootmgr. 
>>
>> -- 
>> - don't top post 
>> Mailing list etiquette: 
>> - trim quoted reply to only relevant portions 
>> - when possible, copy and paste text instead of screenshots 
>>
> 
> Le mercredi 17 juin 2020 23:22:49 UTC+2, awokd a écrit :
>>
>> didier@gmail.com : 
>>> Hi, 
>>>
>>> Has anyone had any luck with cloning a crypted Qubes installation using 
>>> Clonezilla? 
>>>
>>> Even using DD the clone just won't boot 
>>>
>>> Thanks 
>>>
>> Should work if you are using legacy BIOS boot on both source & 
>> destination. UEFI boot might need a command on the destination system to 
>> add the new boot source, something like efibootmgr. 
>>
That's interesting, if you're getting that far in the boot process it
seems like the rest is right. Maybe try to put NVME in SATA
compatibility mode, if it lets you.

-- 
- 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/dfb0e4a6-695a-9e01-390a-d94783b8ce6f%40danwin1210.me.

Re: [qubes-users] Updating Linux and Whonix

[E. Foster]

Greetings, 

Thanks for responding,  

Yes you are correct.  I made a visual mistake.  I read through the 
documentation a week or so ago and those were the version numbers I 
retained.  To answer your question:  Install 4.0.3, Debian 10, Fedora30, 
Whonix 15.  

However, as you said, I should upgrade to Fedora 31.  Or my system should 
have upgraded it to Fedora 31.  Other news flash, I did find the error in 
parameters for setting up whonix connections without the signal.  I had to 
match the templates between advanced and basic in the settings for the VM. 

None the less, I am still a little worried about what I did during the 
upgrade process.  Because, I can't seem to have any peripheral programs 
such libre office or other in an accessible or visible manner.  ( Currently 
working on the installs).   There are a lot of programs available for quick 
install but once you believe you installed them.  I can't find them in any 
drop down menu.  Perhaps, I did something wrong.  

However, I am still working on the Zoom install, hopefully, I can figure 
out how to upgrade to fedora 31, Is there a means to check for all internet 
connections such as Netstat, so I can identify the IPs and block all the 
others?  

Thanks so much for your suggestions,  









On Thursday, June 25, 2020 at 6:12:03 PM UTC, dhorf-hfr...@hashmail.org 
wrote:
>
> On Thu, Jun 25, 2020 at 11:03:19AM -0700, E. Foster wrote: 
> > I finally got latest version of Qubes installed.  thanks for the 
>
> what version is that? 
>
>
> > version displayed did not change.  From reading the documentation,  The 
> > updater should have updated to Whonix 16, and Fedora 35 or 36 as 
> indicated 
>
> what documentation is that? 
> there is no "fedora 35 or 36" yet. 
> those are versions that will be released in 1-2 years. 
>
>
> > Fedora 30.  Would any of you have some suggestions as to how to build a 
>
> fedora 30 is unsupported. 
> you should install fedora 31 or 32 first. 
> https://www.qubes-os.org/news/2020/04/30/fedora-31-template-available/ 
>
>
>

-- 
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/629ed73e-f8af-41c4-a085-2e002e7abaefo%40googlegroups.com.

Re: [qubes-users] Move To a Larger Disk

[Franz]

On Fri, Jun 26, 2020 at 6:43 AM  wrote:

> On Fri, Jun 26, 2020 at 06:38:09AM -0300, Franz wrote:
>
> > Next time I would suggest a very simple and reliable backup of the old
> > disk, install Qubes on the new disk, restore backup on the new disk and
> > you'll have a clean new system with no problems.
>
> uh. even in the best case, this is a _lot_ more effort than just
> copying over the disk and resizing the partition.
>

:-) for you Dhorf, who are a brilliant computer scientist, for you. Or for
others that have the capacity and the biological memory to store this
information. But for more normal users, the backup route is easy enough to
be done safely without headaches and without arriving at a dead end where
the only chance is asking for help. It is just spending some time.   Not
only that, the Qubes backup system is very good and safe,  better than all
other systems I tried, Windows or Linux. Over about 10 years I restored my
systems lots of times and Qubes never failed. But Dhorf you are a good
teacher, the other time you taught me how to repair a filesystem with fsck
and I remembered it enough to use it with a another non-Qubes system and it
solved the problem, Thanks.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/CAPzH-qC1VW__7YKvFcFcsdxQ3v%2BPV%2BRJc1Ya_%3D0yjwFkaguQdA%40mail.gmail.com.

Re: [qubes-users] Global Dark Theme For Qt (KDE) Based Applications

[Qubes]

On 6/23/20 5:37 PM, Sven Semmler wrote:

Install qt5ct and style plugins ...

Fedora: sudo dnf install qt5ct qt5-qtstyleplugins
Debian: sudo apt install qt5ct qt5-style-plugins

Then set QT_QPA_PLATFORMTHEME=qt5ct in etc/environment and reboot the
qube.

Now launch qt5ct and select the 'gtk2' theme.


Thank you for your instructions, but I have a problem. I first thought 
it was because I was using a Fedora-30 TemplateVM for my test so I 
upgraded to Fedora-31, but same problem.


After installing the qt5 packages I edit the Qubes settings and I add 
'Qt5 Settings' to the TemplateVMs 'Applications'. As soon as I start 
'Qt5 Settings' there is an error message at the top of the window 'The 
application is not configured correctly'. If I ignore it and click on 
the 'Style' dropdown menu anyway to select 'gtk2' the window freezes as 
I click on 'gtk2' from the dropdown menu. I have to reboot the VM to 
recover it. I can choose any of the other options in the dropdown menu 
and Apply them without problems.


--
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/40a5afab-8233-55df-5c56-262769ca430b%40ak47.co.za.

Re: [qubes-users] Move To a Larger Disk

[dhorf-hfref . 4a288f10]

On Fri, Jun 26, 2020 at 06:38:09AM -0300, Franz wrote:

> Next time I would suggest a very simple and reliable backup of the old
> disk, install Qubes on the new disk, restore backup on the new disk and
> you'll have a clean new system with no problems.

uh. even in the best case, this is a _lot_ more effort than just 
copying over the disk and resizing the partition.

but yes. it is important to have backups and know how to restore them.
i recommend borgbackup for this.



-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/20200626094322.GK137863%40priv-mua.

Re: [qubes-users] Move To a Larger Disk

[Franz]

On Thu, Jun 25, 2020 at 7:45 PM  wrote:

> On Thu, Jun 25, 2020 at 10:29:33PM +, 'Matt Drez' via qubes-users
> wrote:
> > How to safely raise it to the maximum size (1TB ) and not just an
> > arbitrary number that's close enough?
>
> which "it"?
> if you bought a "1TB disk", that usualy means 931GiB.
>
> the pvresize dance means the pv is now as big as the partition/luks.
>
> >   VG #PV #LV #SN Attr   VSize   VFree
> >   qubes_dom0   1 141   0 wz--n- 929.32g 556.51g
>
> so 929.32g sounds about right, thats the size of your disk minus
> the boot partition minus some headers.
>
> >   pool00 qubes_dom0 twi-aotz-- 897.98g 33.45  14.82
>
>
> you can probably grow that pool some more.
> check "vgs" again, the VFree is now something like 6.5g?
>
> so run "lvresize -L +6g qubes_dom0/pool00"
>
> i would NOT assign the last few megabytes to a device, but keep
> them "free" in case i need to dig myself out of a "oops, metadata
> is full because i have too many snapshots" situation.
>
>
Next time I would suggest a very simple and reliable backup of the old
disk, install Qubes on the new disk, restore backup on the new disk and
you'll have a clean new system with no problems.

-- 
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/CAPzH-qDsB9VJguSFjFaWBr8aySCa%3DoV2uRBAmorPKdj03WO95Q%40mail.gmail.com.