WARNING: don't update qubes, will break your install

[dro...@gmail.com]

I just finished a fresh install of Qubes, then updated dom0, fedora template, debian template, whonix gw and ws templates, as per instructions on

https://www.qubes-os.org/doc/installation-guide/

Shutdown, boot.

Qubes won't let me login. Same problem as in my other post.

[unman]

Nothing wrong with updates on my systems.
What's your hardware?
Did you reboot and log in successfully before updating the system?

[d]

Hi unman, thanks for responding.

Yes, I did a fresh install, went fine. Rebooted fine. Updated dom0 and all templates fine. After restart, something is broken. I guess my hardware doesn't like the latest update.

ASUS G73Jh 213 laptop
Q7...@1.73GHz i7 quadcore
AMD Mobility Radeon HD 5870

It's an older laptop, bought it in 2010. BIOS updated to final before they stopped supporting. Too bad, it runs Qubes great.

It gets stuck in a loop, right before login screen, keeps switching from text mode to GUI and back. Is there a way to force into console mode on qubes? That could be useful.

Otherwise, I can do a fresh install again, but not a good idea to run the shipping 4.01 without updating templates, especially the Debian, which I do use.

I'm open to suggestions. Thanks.

[dro...@gmail.com]

I just noticed on the Fedora forums they released Fedora 30 today.

Qubes runs Fedora 29, so I don't know if today's updates had anything to do with f30, but it might be related. Checking to see if anyone else on fedora forums has similar issue as mine.

[dro...@gmail.com]

I did a full backup a week ago. I think I'll do another fresh install, then restore it to last week.

I lost a week's worth of work. That's what I get for slacking on backups.

I'll have to hold off on ANY updates, until I hear something on this issue.

[unman]

Are you able to boot in to QUbes using an older Xen/kernel combination?
You should be able to select this at the boot menu.

[dro...@gmail.com]

Yes, that worked. I'm back to a fresh install.

I didn't know we could do that. Damn, I was a little hasty formatting my drive. That's okay, I didn't lose much.

If I try upgrading again, it will break again. Maybe whatever fedora broke will get fixed in the coming weeks. I don't like the idea of running without updates.

I can restore backups to last week, then just wait and see if any fixes come out.

[Антон Чехов]

I've been updating my system regularly since moving from Qubes3.2 to Qubes4 and never had any issues so far (default kernel is 4.19.45-1 at the moment) even with testing repos enabled.

I did have to check some VM for using the latest kernel (and change manually) even when I had chosen the latest one in the global settings already. But that might have been a mistake on my part - I can't really say anymore.

So, when updating dom0 via terminal you can see if the older kernels are being erased or if they are still in use somewhere.
I've read that maybe you could run out of space but that never happened to me and I keep looking that all my VM are using the latest kernel.

[Andrew David Wong]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Sorry for the troubles. The devs have been notified:

https://github.com/QubesOS/qubes-issues/issues/4934#issuecomment-496034991

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlzrDiAACgkQ203TvDlQ
MDCP0w/7BD96giZJc4CXxCOQB4IOr1Mc9BdWvxT/R1rpLaDeTP9r/697mIllKl2m
bVJTQzB9lFoKyrPog8/Lrk5lEP2odRw6dXh9+5STjNb74kvNqUBXX6neksAjqTIl
1KlsQwdrsgvdC7DF6MQb6bk1eST9Vuc5o1TqsVBHDM/s5gK/cPYJ9yV6vqwQ7RPj
+noGVObxI0YHr18l6pc5H1rE//L4pd2sxx1GBrbsK2WQNIv5ZdeLlWR0zF0cFQ3a
yNBZ8OFUXLMQieqS4ROsuuBDotnVBK0nbMd5vkQVj5KBe/bVbhCLc1UM6STM3NOH
UUmZXNfpRJn7fLtkVga6esQ/j8saFCfnp+M+4Sh2DipT8LnuCFdlG3qpvFnJ7d0L
TFBR/KXnSakRoWzMgloOENnglV0W71Yk5UBm8SY+NQvmcauvdTj8i4CXxnbh8Ecx
WoCXgqK1ZKihh8Khc59H0X1XXR5Drg/HSQ+xnvwpGSpyaCIgejg7/MWn+8z2uJeg
UqOX7srcCqEZ11Esa8gDdyIWMGFFJ67BNvJz/uQaXFvxE7NNLa2eJN61KtOEahQV
0KCTMZkXHg6WDS/8ZZ0xxWBNlR/iVCNufwvrnzvR+3xoFRjzuc6EbVMVNvqBSKPs
pnwH8mhGYB53z8KvzawgsnNx+YpC6xCELKuHbqJ+/Iug+FCl/SI=
=MQIM
-----END PGP SIGNATURE-----

[brenda...@gmail.com]

Guess I lucked out by using kernel-latest this time...

[dro...@gmail.com]

On Sunday, May 26, 2019 at 6:54:40 PM UTC-7, brend...@gmail.com wrote:
> Guess I lucked out by using kernel-latest this time...

It's working fine now. They had a new kernel that doesn't like old ATI Radeon video cards. The kernel was removed from updates.

Hopefully in the future, somebody will make sure the kernel doesn't break the old video cards again.

[Andrew David Wong]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

This will happen if users who have such video cards test updates and
provide feedback on updates-status:

https://www.qubes-os.org/doc/testing/

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlzrSbcACgkQ203TvDlQ
MDCqshAAiNESVvVnar/IB4i94uoEScfLQCD18JFTBKp8NxMhOAozescUb86Yet3Z
JzSX6JZGV4ZRHS4XMw3iYDUDNDzlyeY2iF2d1mkxFF3iWmpYxJtHEHHYCcmmWqk0
IM3NdvZ2bZssLYA5VddAO8XXfV7h8JscDhJtNjIUYa37e2Gx9ATndOGhhn0q1YTv
JDFlPBkXbHQ6z4f+Ddy0Ww9gpubVa7v3bZ/gGl8GZXMg2i2tIwQJEu2M6lD0/h8u
YD6twLrkluxrJSpfsra+P7gnzQJwMBeQ18LFVGWt79OZpESnEKz0cBOGeIbTx5W4
K+w6kX6h1KuhRbhRNJr4Y7TFVJswZjT3xSEbSNgOsBu9OKhHKr5uyoopZj+Vvt9D
AxQyf39PYjk/jsi7fPZy55JN7pgCQGbaUFJDNxtch1QTZNpU0B6BNcncZ0fqsY/V
sFh9b9yp5vnH7C3En+SMTTpSJM59ZlESnYpADuqmrktI4OT33TFWFDor6uQ9Zt0f
RW1Op4Ul4A5KPrv/0vzG10KCaSHMjJjroLxONH+wG8DrM+PA18fByUL1126rgnwY
c5Q6Hds+3c0TAwVzqbKf4doWjYOtuMiOptoNN9QE3lNsdCOvrgHHeWMY3kdANLMQ
GXe+4UrpqLhnql+LDxNO0LGRbmw0y0J2JmpG6hV5a9l2XwT4L6s=
=RSTz
-----END PGP SIGNATURE-----

[dro...@gmail.com]

I'll join the testing.

I was reading about those testing repositories yesterday. Now that I'm used to doing reinstalls :) I might as well try it out. That's what backups are for.

However, one of my backups failed to restore, errors. I'm hoping when they upgrade the qubes backup/restore software, they can improve reliability and fault recovery. It's a shame that one error prevents the rest of the restore. Now I'm going to start backing up each qube separately, making many small backups, and run verify every time. There's got to be a better way.

[Andrew David Wong]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 27/05/2019 11.28 AM, dro...@gmail.com wrote:
> On Sunday, May 26, 2019 at 7:21:54 PM UTC-7, Andrew David Wong

> wrote: On 26/05/2019 9.17 PM, dro...@gmail.com wrote:
>>>> On Sunday, May 26, 2019 at 6:54:40 PM UTC-7,
>>>> brend...@gmail.com wrote:
>>>>> Guess I lucked out by using kernel-latest this time...
>>>>
>>>> It's working fine now. They had a new kernel that doesn't
>>>> like old ATI Radeon video cards. The kernel was removed from
>>>> updates.
>>>>
>>>> Hopefully in the future, somebody will make sure the kernel
>>>> doesn't break the old video cards again.
>>>>
>
> This will happen if users who have such video cards test updates
> and provide feedback on updates-status:
>
> https://www.qubes-os.org/doc/testing/
>
>

> I'll join the testing.
>
> I was reading about those testing repositories yesterday. Now that
> I'm used to doing reinstalls :) I might as well try it out. That's
> what backups are for.
>
> However, one of my backups failed to restore, errors. I'm hoping
> when they upgrade the qubes backup/restore software, they can
> improve reliability and fault recovery.

Please report this bug if it hasn't already been reported. The
improvements you seek will not happen if the developers are not aware
of the problems you're experiencing.

> It's a shame that one error prevents the rest of the restore. Now
> I'm going to start backing up each qube separately, making many
> small backups, and run verify every time. There's got to be a
> better way.
>

FWIW, I use qvm-backup every day, and I've found it pretty reliable.
If you're making very large backups, try forgoing compression to see
if that makes a difference.

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlzsX8UACgkQ203TvDlQ
MDCv0hAAzjLnLsci024R8TrgN773L6qZ+93ntKRuPscFzKi48QI5wvcpF/2rwvTu
A+3uv0u/Wum4ufYz0Cl+f/KCYwawd1vfpseZxw4J3VLRvTJ5z2PRZLsAg74A7Yke
o25YeMOdLtwU7kPvAGs+jPKQNenWtFO2TI9PMTPVJm0FAR/IhrOVyp8GSvg30oES
DWYIqGkG/wqmDxnnX9ND8ZcGhjbzAQ7ujgDAwLwJuONcfyry74BUSNsG595uXyA3
3nDbuxo48nUpvaNwmpw7jUqoc0O+Fzb+BNVPww5hbcK4gUBpfAX6B8FnRbuXWAib
19t1hpF07/6Oq2V6FLgMgTdmTSw/0BCBot4M+mWbVOjf3XW2u6RpTDgDRVtQfTj9
P7YaQERMF51wjPBnYoHBK+J0StlUpxDRqkCvk6FrB9HIaNhvIsQ0W4Uhqwp8xtoJ
CqaeR+gI5307rrX4E5lTyN+YhSNcX5FbMbKObpRg8wDsW4ZH7e6n+8LtrBT9Tth1
p8MjT4Ce+k04L/AC51dGFXKnIFaxuwZq3qW2qSrO0VcMX/GD1klEVdnSJC/0E+hk
bNuD5vjefNA5KRAwFbLxTGbDprWRat3uuNeiixX7bDKWbpgyn4uBri/fB3EmU2ss
UIRbTscxuuhMziRle1U3Lg/ND3dJfEfGhfjyKrF5EcwQoleAj90=
=5bkW
-----END PGP SIGNATURE-----

[Jon deps]

for the record from the github


qubes-bot said

The package kernel-4.19.46-3.pvops.qubes has been pushed to the r4.0
testing repository for dom0.
To test this update, please install it with the following command:

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


I did a dom0 update but haven't rebooted yet, I am at uptime of 10
days, shall I install over the top of the last dom0 update with
the above ???




personally I don't even backup 1x/month, but then I am not creating very
many files locally

those are in the Vault , and rarely do I add anything to it ....

I can't recall the last dom0 reinstall , nice thing is I can fail on
the Templates and just reinstall those .... akin to borking a computer
OS, without the risk to my local files as they live in the AppVMs :)

[Jon deps]

On 5/26/19 1:32 AM, drokmed-Re5JQEe...@public.gmane.org wrote:
> I just noticed on the Fedora forums they released Fedora 30 today.
>
> Qubes runs Fedora 29, so I don't know if today's updates had anything to do with f30, but it might be related. Checking to see if anyone else on fedora forums has similar issue as mine.
>

Are you saying you think your Fedora-29 template caused your dom0
domain to fail ?

afaik the Qubes Fedora-29 template is not going to auto update to
Fedora-30 like with $dnf upgrade or something

[dro...@gmail.com]

I see the new kernel is back in the dom0 repository, same name/version, no idea if it's a fix or the original.

I spent the whole weekend getting my laptop working again, not ready to break it again. I'll hold off a few days on this one. Work to do.