Re: [qubes-users] Add this to the Qubes docs page?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 26/05/2019 10.05 AM, Stumpy wrote: > Hi, I was trying to figure how how to install the onlykey hardware > token program and for whatever reason thier page, > https://docs.crp.to/qubes.html, isnt the first thing that pops up > when I searched so I thought I'd suggest putting a link to thier > qubes setup page. > Thanks. Added: https://www.qubes-os.org/doc/#security-guides - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlzrSgEACgkQ203TvDlQ MDCMbBAAk73yA72Az6za7z+tdFUh8cZp5aTNCwRjgEC7GQQImSdQIO4LgWz4yLLk ag04BhYruV97m7ayv8QI9w40o/cQUdcnbD4Ma00ZX5ofyP5O68LOyZXvAmfS2hop SHMTcqGu58WAdALFcV0r+HJ+7WLFzLZcHY2bGQxRAGktxkPXqpM3LZGcv4yWJAn0 q5Yr0h0BH+v80W4cSp1Y22d4HBsW3hw+UguYUxNKtCpVQWXoPSEqo7XnvqEAVirj AEr9HNWcTZ0XXtqd+zXT9XTZvis/G/WcU8Wsf0eMNZu8tR+bTnwjx9/9NGwmFtJ/ 0ErqnSBqPXM56dxO3wUnhyhH3X6xrcu70sVfCTZkO9xGUqAPHE1OOcE2/dFNd4zc Bk6o6/ZBQ1dfB72CuzdSXgcaXPsCF+8/E87GYb0dgIsjbXFUR4eNu/Hyd2w+T+4a plGkpVC2ELTRnDolDHpKvXy4aApDvMbGhUJUJ/ahOx7dYpLLrbXSh0ig6hOd1LNE c0SFpDR7UxuQ3uar8JRt65l85370DyU5lAyY3769XI+vKaPeCWDDmA8yatAxAskt 8voxgDm5fwsER25qHdjmbkVjIAigzKYn2eN+poD0ahaUHUQivp88FWNH+ZIxIMFg pntcLqp+r2umxZsV64CdG+B721R9WYI8Eiipez78C/QLa8vdgM0= =q3ye -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/8bc80ada-9b13-bda2-ee73-683535ef2c63%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] WARNING: don't update qubes, will break your install
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 26/05/2019 9.17 PM, drok...@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/ - -- 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- -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/b6f1c808-aee9-588a-ee93-1deaa79a0965%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] WARNING: don't update qubes, will break your install
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. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/0df51700-1ba3-48b2-9e57-0fa82ab9e050%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] WARNING: don't update qubes, will break your install
Guess I lucked out by using kernel-latest this time... -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/64ce9310-6bb9-4d86-98f3-137d3d9bfb72%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Just did fresh install + all updates = everything working fine
Thanks to everyone who helped troubleshoot the latest dom0 kernel update issue. Everything seems to be working just fine. Fresh install uses kernel 4.14.74-1, and a full update takes it to 4.14.119-2. Both working fine. I hope the next kernel update doesn't break systems that have the old ATI Radeon video cards. Fingers crossed, we shall see. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/fa862b42-803c-4749-ba59-f9f82473886c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Recover from /boot wipe
After installing Qubes, I attempted to install Windows as a dualboot option. Unfortunately, I didn't check to make sure windows wouldn't wipe my boot partitions, so now I have nothing under /boot other than the Linux .imgs in the LVM partition. Is there a way to recover the old install? I installed Qubes onto a different partition to get the /boot files back, what lines do I need to change to point to the correct encrypted LVM partition? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/LfqTsL2--3-1%40schunkc.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] [Dom0] Houston, we have a problem...
On Sunday, May 26, 2019 at 2:55:40 PM UTC-7, Andrew David Wong wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 26/05/2019 4.47 PM, Andrew David Wong wrote: > > On 26/05/2019 3.31 PM, drok...@gmail.com wrote: > >> Can't launch Qubes Global settings window. I get: > > > >> [Dom0] Houston, we have a problem... > > > >> Whoops. A critical error has occured. This is most likely a bug > >> in Qubes Global Settings application. > > > >> TypeError: setChecked(self, bool): argument 1 has unexpected type > >> 'str' at line 248 of file global_settings.py. > > > >> > > > >> I had tried to turn off checking for updates, both dom0 updates, > >> and all updates. It refused to let me turn off checking all > >> updates. I would turn it off and save it, but after reboot, it > >> was turned back on again. > > > >> I made those changes after a fresh install, but before upgrading > >> dom0. > > > > A lot of bugs like these have been fixed after the last ISO was > > released, so if you use the system before updating dom0, you might > > be seeing bugs that have already been fixed. You can get the fixes > > by updating dom0, so I'd recommend doing that, then seeing if the > > problem persists. If it does, please file a bug report: > > > > https://www.qubes-os.org/doc/reporting-bugs/ > > > > Found an existing issue for this bug: > > https://github.com/QubesOS/qubes-issues/issues/4988 > > >> I wonder what else got broken. Maybe I should just wipe the > >> drive and start all over again. One more time after all of this > >> is just par for the course. Then again, I might as well wait > >> until there is a fix for the current kernel not liking my Radeon > >> card. > > - -- > Andrew David Wong (Axon) > Community Manager, Qubes OS > https://www.qubes-os.org > > -BEGIN PGP SIGNATURE- > > iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlzrC08ACgkQ203TvDlQ > MDBkQg/9GwMX8rdvxygfrB5eaf6xBaHRNu8Ml3s5BvoXII43NqeRs/O8HMLB9zP6 > WyEYVNBlgJqZwwWEX/C5q5c5gmvgu7GMHpZ7eDTQoZKF+KI1MIoQui4dk1zlRvbC > mTME/YsmTFmYeDhkT1RXMd/0w1yHSxmp1xvrqhtNSP/wHdLQ2OX6g04s+/PJ76Sp > iz/OdEGKILk9HxynsHAoOrWZLJJYshfEqoV/u0mXq67FZ1Wi0nqzLPdQLEuofnLX > NZMgTP0xkacP8EFqmF+Y2wEaNeDtSRA2hEoWUH30nl1lw26jwlyEnpY7MlvIJhc8 > eRACGYTieBQhXDNt/lPMioH542RvQk7GHiPo46zrySdFPTKjyaIj3qdBHYp6qQUJ > nFjqlAaG3XdLI0h+mZOhK3jBxhkrOqt03Lu4E7NtyK4T6bG83FZQTKKXX13W3taK > sg33DYib4iV5h0GJ6yq8Q09O3sa2NntZkNjEBk+cLqB99IwftQlKdMpFo6jG6397 > veYd4dFRVzs8+vHmMSl5JB9pxqrc4P9H7ziZLPMof3pkoTDpkFMET4TiSbwWHBQ5 > Vw5GaEgLRN9RUHxrtsWV8S7dDB7cy/LYzIRZcOl0QZ9BtNS9Lmblzgv3ywh8A8jg > obYfcrfoC52QOoCGQeGCZVhiUuznLNTQbxaqaIDgdHtPRv24viA= > =CICX > -END PGP SIGNATURE- Thanks for checking for me. I'll try an update, but will probably just do another fresh install, after the kernel issue gets worked out. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20a8b900-0dee-4c31-811b-0b047a497a99%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Kernel 4.19.43 Issues
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 26/05/2019 5.04 PM, Andrew David Wong wrote: > > On 26/05/2019 3.39 PM, Eva Star wrote: > If 4.19 is this problematic, should the update be pulled? >>> >>> Yes, please pull 4.19.43-1 kernel update, if possible. Would solve my >>> problem. >>> > >> Yes, problems :( >> Currently, you can install all dom0 updates, but before actual reboot change >> kernel manually to previous that reboot and all must be fine > > > Thanks, all. I've posted a question for Marek about whether the update > should be pulled: > > https://github.com/QubesOS/qubes-issues/issues/4934#issuecomment-496034991 > Kernel 4.19 has been pulled from the "current" repo for now: https://github.com/QubesOS/qubes-issues/issues/4934#issuecomment-496035377 - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlzrDv8ACgkQ203TvDlQ MDATVg//emqLXvTO/lOnJPT/THNOw82RuH3d2R06ZDaT1VK8iryxvg2ql+sPm3q8 UXkc4y7UskdjlvtsLmI26Drb9sws13fyOwH9O7nTb7XxnOsh7grrKmQ89hLj01Lq SfCQA3oVb5kaqp57J6EeG2l9ln+pDARmwZLiUHoi8jrz49T1vh752bYVYl+CifwF /+hYeJZZXk+kEGWnDZOU6ryLDFAXpjoVl7eDkZtd7aUVckBWVD31370ESHS/9nga 2kj36mmKFKz812WfC5HHeJ6zUPNKRzNzHLiptdG4rui1twZx+o6tpPoxkrOIt3Tb HD3YBpsoME8rqJvsOAvl/3vQFWYo5v+rVj9dP0Sw7/x4zd4NoM8x+KxF7HBJLbN8 Jat/AAeHcVx02XH+h3sWGG8WxojNZQTsxFFE5u1fYhNIWTKFZBv74g1lizULJo6I t5p08JeZvEEK4R0qiabNGMwfkB3w2ZRtA1GTCjmnHlZa093LA09fdlUH4iyJ94eT Q6A+2dwxWBdZb5EyhA2+iypFko+kkmDK7vSVzCO21zBlIwUI8//n/V+tFN7X06So wnrGOcCi0lANiVSQ1F5shVnFxZvSE+/ahqynbEVjkDEROab+bQyG4qd70mUQdoAW 3g0id1qyBc56diqAZnWmcuxJp545kiqGL5ZtPV7/4HnY34/bx3c= =mUla -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/9880b24e-9700-430b-210a-c51419f75f5b%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] After last update system DEAD
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 26/05/2019 3.44 PM, Eva Star wrote: > >> Don't touch your existing M.2 drive. Get a spare drive (spinning rust >> is OK) at least as large as your M.2 drive and that you can attach to >> your machine (e.g. with a USB SATA dock). >> >> Download Tails to a USB stick. Boot your machine into Tails. Connect >> your spare drive. `fdisk -l` to be sure you have the right device names >> for all your disks. `dd` your M.2 to the spare drive. Now `sync` the >> disk and detach it. You now have a backup of your current state. >> >> If you _need_ to access some VM data now, you can (with major negative >> security implications) decrypt your M.2 disk manually with `cryptsetup`, >> navigate to /var/lib/qubes/appvms/ and use `losetup` to >> help mount the VM's data disk in Tails so you can copy off whatever data >> you urgently need. > > > Thanks! It must be at the qubes FAQ. Next time it will help. Here are the emergency manual restore instructions (for future reference): https://www.qubes-os.org/doc/backup-restore/#emergency-backup-recovery-without-qubes > I got the idea with cloning drive (vs actual remove it and do something with > it). And looks like it's not so hard to decrypt the whole drive and mount > some qubes data disks. Hope I will run without troubles, but will know this > opportunity for future use. > > Chris, thanks! Now solved. I'm at EFI. It was not possible to select > something on the boot time or I don't know how to do this. > - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlzrDsgACgkQ203TvDlQ MDDoQw//boohe5Dfja8JQE3qOYzFxpJVu2Ke0wpATl06aDdaLzcP7db73X8HgYr8 /MD6kOhQSboslN7SLoZXmrQffnANPwOB87P+KTkzDK80KUofNDwv2xMnzORqhLva /7V7j9UGYRpmQRINPB1Ibon3wJ6930IeOd2jgnxFY7jubxk8aXFlIgzVl4tBMvna kfVrTJbz9gRfKCfyGxsl8IlorEscdGLXCleJCTDZj7VBjwg4W6mo819h3FCebkDR v5GZa0SgVAJQBsm7yUsa4+AWPr7YYni2oJAoK1A8fVXHGfBJFdPgdrv3RZvM43Qf GMh6Ql9kyHG3b6MrYe57mXBg8/ijnTgyNCP+vMJF5V501tiEy5fyeyuAKwwDFIeA iN2sCNMJf0j5HvXK+EcMkt8gg7p4/K7hYP/YyZuXMsgdKJEZaL46KQ76H6lF8Nlp L0qcI4TpBE7gD2w1JjPHnlKbscq/ugPjFMmzghRbzqtFFS9q6pB7kC2UUZWyv7Ik xCpjsp4cfwAkB1ZnFernMvtzPu9q3jBQU0bZ1zOc7KX0icEIVv9ntjpi78yrERCl BVIXmx0GR4Wn7Dannk9K3WXvWxx7ExZZ4oK8HmUv4G5TtOV6w40LrqYzlDU/hagh EXKqkKj9h6PcDQC87BbyZHf71RZgymU+mzATbw5RDJorSx3Pq18= =necR -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/cd7daa07-9b57-0627-5276-abf25c496005%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] WARNING: don't update qubes, will break your install
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 25/05/2019 9.16 PM, drok...@gmail.com wrote: > 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. > 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- -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/e4415ecc-7bec-f8e2-9394-88141da6a8c4%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Kernel 4.19.43 Issues
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 26/05/2019 3.39 PM, Eva Star wrote: > >>> If 4.19 is this problematic, should the update be pulled? >> >> Yes, please pull 4.19.43-1 kernel update, if possible. Would solve my >> problem. >> > > Yes, problems :( > Currently, you can install all dom0 updates, but before actual reboot change > kernel manually to previous that reboot and all must be fine > Thanks, all. I've posted a question for Marek about whether the update should be pulled: 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- iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlzrDXoACgkQ203TvDlQ MDD/Jg//Qx+rud/Fu0xp3k9/Gw6NI03e5ZOYyQq2yB3bKXSCxiCVF2v7ZKNywRVf Sq0Wagv6EwLaq6Wz+E9pFwkBZSgKFa1nNskI7AvTf27+FVTlamleRJqEpBNQ2HJV tCaEzr+mEAdUcBKO1WKcBQnBZI7fkHQRWn+GGgVXrlkNxnIgWkKmNiCjcWr8O30L uHoH25BvVH+xxrF7DAuV65vdtztA9m6cyAjubss2U92y5DB4PTQM9qqVAyi2pIQw xXVuwTRo4eDdr1/e8gjgdeHepxP1a2kacBlI3tKOgV7CbHzWm5iz1RvdnILyP3bZ dkKTIxUzNydG1nGVyM0dvcCeAYnr8Mf0pxv95Pzl1E6V2IphwAHSrZfwePESRFgQ tfCOlf7pMU3Ll1ZNLZG5Ey2yv7XeOGz0lLTo+eeWBFeNEqKnpZKVekmpTs3tRqL+ c3G6Z0kK+JFIt5jv3ZH+UAXHPXtCOf8ofe6qEYwBOCuZY0OzVnayuOxqNYNGh88b oXMGxroZdQU/M03sYMLHu6zhgJ+TXGHa3GICvFosoFZXDjxf1KWqQykkF3ubiMsp MTG9WRa3kjvCchsC6LbNtPXXp2TjKljjYDyQBLWO+RnuHXDs2qsSK1+f9SrSZ20B UA97yXk7csI59LSMdSL8kX/c4f7zJPC3/MayAycmruh2IRZg16c= =7rc+ -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/4a0a5a44-1c63-8373-0ccc-b77e943f4b4d%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] [Dom0] Houston, we have a problem...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 26/05/2019 4.47 PM, Andrew David Wong wrote: > On 26/05/2019 3.31 PM, drok...@gmail.com wrote: >> Can't launch Qubes Global settings window. I get: > >> [Dom0] Houston, we have a problem... > >> Whoops. A critical error has occured. This is most likely a bug >> in Qubes Global Settings application. > >> TypeError: setChecked(self, bool): argument 1 has unexpected type >> 'str' at line 248 of file global_settings.py. > >> > >> I had tried to turn off checking for updates, both dom0 updates, >> and all updates. It refused to let me turn off checking all >> updates. I would turn it off and save it, but after reboot, it >> was turned back on again. > >> I made those changes after a fresh install, but before upgrading >> dom0. > > A lot of bugs like these have been fixed after the last ISO was > released, so if you use the system before updating dom0, you might > be seeing bugs that have already been fixed. You can get the fixes > by updating dom0, so I'd recommend doing that, then seeing if the > problem persists. If it does, please file a bug report: > > https://www.qubes-os.org/doc/reporting-bugs/ > Found an existing issue for this bug: https://github.com/QubesOS/qubes-issues/issues/4988 >> I wonder what else got broken. Maybe I should just wipe the >> drive and start all over again. One more time after all of this >> is just par for the course. Then again, I might as well wait >> until there is a fix for the current kernel not liking my Radeon >> card. - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlzrC08ACgkQ203TvDlQ MDBkQg/9GwMX8rdvxygfrB5eaf6xBaHRNu8Ml3s5BvoXII43NqeRs/O8HMLB9zP6 WyEYVNBlgJqZwwWEX/C5q5c5gmvgu7GMHpZ7eDTQoZKF+KI1MIoQui4dk1zlRvbC mTME/YsmTFmYeDhkT1RXMd/0w1yHSxmp1xvrqhtNSP/wHdLQ2OX6g04s+/PJ76Sp iz/OdEGKILk9HxynsHAoOrWZLJJYshfEqoV/u0mXq67FZ1Wi0nqzLPdQLEuofnLX NZMgTP0xkacP8EFqmF+Y2wEaNeDtSRA2hEoWUH30nl1lw26jwlyEnpY7MlvIJhc8 eRACGYTieBQhXDNt/lPMioH542RvQk7GHiPo46zrySdFPTKjyaIj3qdBHYp6qQUJ nFjqlAaG3XdLI0h+mZOhK3jBxhkrOqt03Lu4E7NtyK4T6bG83FZQTKKXX13W3taK sg33DYib4iV5h0GJ6yq8Q09O3sa2NntZkNjEBk+cLqB99IwftQlKdMpFo6jG6397 veYd4dFRVzs8+vHmMSl5JB9pxqrc4P9H7ziZLPMof3pkoTDpkFMET4TiSbwWHBQ5 Vw5GaEgLRN9RUHxrtsWV8S7dDB7cy/LYzIRZcOl0QZ9BtNS9Lmblzgv3ywh8A8jg obYfcrfoC52QOoCGQeGCZVhiUuznLNTQbxaqaIDgdHtPRv24viA= =CICX -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/e008e5e7-2b66-d4e7-87c1-e910b1a8e4d9%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] qubes backup and restore question
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 26/05/2019 10.15 AM, drok...@gmail.com wrote: > On Sunday, May 26, 2019 at 5:38:00 AM UTC-7, awokd wrote: >> drok...@gmail.com: >>> What is the point of backing up a qube, if you can't restore to it? >>> >>> I'm restoring a full backup, and instead of restoring to qubes, it's >>> creating new ones with different names. WTF! >>> >>> What the hell am I supposed to do now? Delete the original qubes, and >>> rename the restores? I'm guessing that will break a bunch of links, which >>> I'll have to manually fix. Am I the only person that thinks this is >>> totally stupid? >>> >>> And it says the restored dom0 files are located in some other directory. >>> What the hell am I supposed to do with that? Dom0 can't be restored? Are >>> you kidding me? >> >> The easiest way to restore qubes with the same names is to delete the >> old ones prior to restore. You'll want to leave or clone an equivalent >> of sys-usb and somewhere to mount the backup for the restore, so don't >> delete them all. >> >> See https://github.com/QubesOS/qubes-issues/issues/4946 on how to move >> the restored dom0 files to the right place, it's pretty straight-forward. > > Thanks that was very helpful. > Thanks for sharing your experience. I've updated the issue with some further thoughts on how we can make this better: https://github.com/QubesOS/qubes-issues/issues/4946#issuecomment-496032480 - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlzrCfwACgkQ203TvDlQ MDDtmhAArvHDwRCm/dQ2r4rM8VV0BO8Zcp0SLMIQyP4q206DJx/viagqsuzuMh5j fQcsqEUx0PBGATEBOiVyIh6392N7/W60llcK4bxWARZH3OmzlmC2GbL8zAGYh51P eMYUU8MWFawej5itiax4wQiWyhFzkYvnQgIWuh9DNCJOsH15WhOqFfgyVSSe2diC Pm19+DRnA3z71C9RCWaomtdVnll7Kmqz4x59wVPhtSAqILevMPCpQ+95bGZE+t44 qaITkM8YBra3cEujCQiMJIBF5j2T2fcRRCL9MmsnhU04Wtqk+qMg+QTuTo4jhvMJ PRDQ0sFuvysOTu0MOJMp31qgx+4wjHzbOQ6wEHBdgG/Hz33Lr7vWysDJrCyMPCbO a3UsuYuCo4OzhyLqRf64pjARR9Hns8/4auQ2L9lc4DgU4MPiNmXojEkDF31tRz6p s3E3fQJ07k6U4N/5YjasFVxDR5iEYFP8Dcc/a6tS7PGmNecyiBsh7a8uU8K1x/sK gMApdfubJ40cMj6hSb0PQ08E32jsiozd1o9As0rtwYhy+XHaTWq0jf1hHM0vD3ux g1j54O1sxkTUVLgZ4OdHI9qmDHiuN6xVef1tpffJLCU6h3Vf3y9oMY/c56ZD5Ez0 nwFtDquke68ZPNjm9BZwWowqG4aiVjSNk2xkiUuQqvO1+bP/e4I= =CQ6x -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/6e67fae2-c40b-b4e4-ee37-65eadaad3bff%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] [Dom0] Houston, we have a problem...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 26/05/2019 3.31 PM, drok...@gmail.com wrote: > Can't launch Qubes Global settings window. I get: > > [Dom0] Houston, we have a problem... > > Whoops. A critical error has occured. This is most likely a bug > in Qubes Global Settings application. > > TypeError: setChecked(self, bool): argument 1 has unexpected type > 'str' at line 248 of file global_settings.py. > > > > I had tried to turn off checking for updates, both dom0 updates, > and all updates. It refused to let me turn off checking all > updates. I would turn it off and save it, but after reboot, it > was turned back on again. > > I made those changes after a fresh install, but before upgrading > dom0. A lot of bugs like these have been fixed after the last ISO was released, so if you use the system before updating dom0, you might be seeing bugs that have already been fixed. You can get the fixes by updating dom0, so I'd recommend doing that, then seeing if the problem persists. If it does, please file a bug report: https://www.qubes-os.org/doc/reporting-bugs/ > I wonder what else got broken. Maybe I should just wipe the drive > and start all over again. One more time after all of this is just > par for the course. Then again, I might as well wait until there > is a fix for the current kernel not liking my Radeon card. > - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlzrCYMACgkQ203TvDlQ MDBMFg/+PoiB/VPVGIxumwRGoPojUhXgnGPvM+ad4X/scIGGSakP3lJJRM0CEKXS kneniwtiTVCpkHTNZob6mdgoCNyLPv97m/A6d1VVKXUk35w4bqtt2+4aUzYJMhx4 TpPcTEKQkJk36+U1MmEkL8YMJvg8fPQOmWd8E7cg2dS52R3IqEFVoISP0/7D5TYK irJiv8eRrT4eVGpGbXc1+IWZ0zobrGO5vsTtPj9k7Gk5X/E27XGkdVzD2LPhbGjd AU3Ad+4qXz/owlogHR+M3zbfAhdQdR6qHMWbHX7PsYyPLe0svOeISyJp1+EM2vTG U38vdFK0LH0Gl9Q5bsHvmwhQ4HcUS1ZHmhU33lklHk3PoOyPPJLrVWQjiGm4xGyA fSdt2W5urxWyIyOWaYxEX3pDLFS5YLlnQSujAeLHaO3WtFACmnlN7GmEQKuJFwSo 5RCtckrHE8zP1g2mRmkYOpFDPoOigZ9RNQN8iAjxbCDM/qsYdpyAdDJ14phSHXCE KXGpX7WnExY/BBc1CR/Au4eEM3TwWD5sHp3h2MFbalbUyjcS+NpDhyxte1Ui/P4v jcFrBmwjwWZ3DBf72Z2olFG89caMZBxvXIUOpdZHFtRwGcY6bEciXs0AvC3oIdPJ LpFZQolnxNUmogvnm8/5XJU3I6kj286AEeivPWQfb/1K82geweU= =rmz0 -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/86308b6b-ac2c-6966-ab44-0efea96cb204%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Fwd: Us congress hearing of maan alsaan Money laundry قضية الكونغجرس لغسيل الأموال للمليادير معن الصانع
YouTube videos of U.S. Congress money laundering hearing of Saudi Billionaire " Maan Al sanea" with *bank of America* and The owner of Saad Hospital and Schools in the Eastern Province in *Saudi Arabia* and the Chairman of the Board of Directors of Awal Bank in *Bahrain* With Arabic Subtitles *موقع اليوتيوب الذي عرض جلسة استماع الكونجرس الأمريكي * * لمتابعة نشاطات غسل الأموال ونشاطات* *السعودي معن عبدالواحد الصانع* *مالك مستشفى وشركة سعد ومدارس سعد بالمنطقة الشرقية بالسعودية ورئيس مجلس ادارة بنك اوال البحريني* *مترجم باللغة العربية* http://www.youtube.com/watch?v=mIBNnQvhU8s -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CANaYHjyXAdEzYEbdnwwy0gk%3DrLRPWPpfQs88Ti%3DhrJ1%3DXXr%3DAQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] After last update system DEAD
> Don't touch your existing M.2 drive. Get a spare drive (spinning rust > is OK) at least as large as your M.2 drive and that you can attach to > your machine (e.g. with a USB SATA dock). > > Download Tails to a USB stick. Boot your machine into Tails. Connect > your spare drive. `fdisk -l` to be sure you have the right device names > for all your disks. `dd` your M.2 to the spare drive. Now `sync` the > disk and detach it. You now have a backup of your current state. > > If you _need_ to access some VM data now, you can (with major negative > security implications) decrypt your M.2 disk manually with `cryptsetup`, > navigate to /var/lib/qubes/appvms/ and use `losetup` to > help mount the VM's data disk in Tails so you can copy off whatever data > you urgently need. Thanks! It must be at the qubes FAQ. Next time it will help. I got the idea with cloning drive (vs actual remove it and do something with it). And looks like it's not so hard to decrypt the whole drive and mount some qubes data disks. Hope I will run without troubles, but will know this opportunity for future use. Chris, thanks! Now solved. I'm at EFI. It was not possible to select something on the boot time or I don't know how to do 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/c509637f-12e6-4fb6-a993-59a78d3b2976%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Kernel 4.19.43 Issues
> > If 4.19 is this problematic, should the update be pulled? > > Yes, please pull 4.19.43-1 kernel update, if possible. Would solve my > problem. > Yes, problems :( Currently, you can install all dom0 updates, but before actual reboot change kernel manually to previous that reboot and all must be fine -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/5c632aac-f3f3-4d7d-8348-0fa5d145dcfe%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] [Dom0] Houston, we have a problem...
Can't launch Qubes Global settings window. I get: [Dom0] Houston, we have a problem... Whoops. A critical error has occured. This is most likely a bug in Qubes Global Settings application. TypeError: setChecked(self, bool): argument 1 has unexpected type 'str' at line 248 of file global_settings.py. I had tried to turn off checking for updates, both dom0 updates, and all updates. It refused to let me turn off checking all updates. I would turn it off and save it, but after reboot, it was turned back on again. I made those changes after a fresh install, but before upgrading dom0. I wonder what else got broken. Maybe I should just wipe the drive and start all over again. One more time after all of this is just par for the course. Then again, I might as well wait until there is a fix for the current kernel not liking my Radeon card. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/472c7f08-4e11-4bb5-afdd-b5fde3f134f3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] offline backup/restore of qubes, boot from usb
drok...@gmail.com: I agree the qubes backup/restore is easier. I learned the lesson of don't make any changes to system templates like Debian-9, because you can't backup/restore them. I'm trying to keep the number of qubes down to just one screen full in Qubes Manager, which gets hard quickly. I'll either have to start creating a bunch of extra templates, or start writing down any changes I make. I'll probably just write down the changes, then lose that piece of paper DOH! Templates are easier to manage. Before updating, make a clone of them. If the update goes well, delete the clone. If not, delete the original and rename the clone. This does not negate the need for periodic full backups, of course. For full Qubes version upgrades, it's useful to keep a record of changes you make to templates too. I keep meaning to do that one of these days! -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/a5c8be2a-7213-0b6e-23ee-e7ba44342f29%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] offline backup/restore of qubes, boot from usb
On Sunday, May 26, 2019 at 10:15:09 AM UTC-7, awokd wrote: > drok...@gmail.com: > > Hi, > > > > I'd like to boot a usb, and do full backup/restores of a qubes install, > > offline. > > > > Anyone doing this already? Some kind of qubes specific recovery usb, with > > lots of room for backups. > > In my opinion (others might have better ideas), Qubes isn't the right > tool for that job. Look for something that can do a full image/bare > metal backup of your internal drives. It doesn't have to be very fancy. > Nearly any distro that can boot as a liveUSB can run "sudo cp /dev/sdd > sddbackup" [where sdd is an example of an internal system drive as > viewed from the liveUSB command line]. Note that the file generated this > way will be equivalent in size to your internal drive's size. > > Personally, I use qubes-backup and do a reinstall & restore of Qubes on > the rare occasions I need to instead of the above. Full image backups > can get impractical. I agree the qubes backup/restore is easier. I learned the lesson of don't make any changes to system templates like Debian-9, because you can't backup/restore them. I'm trying to keep the number of qubes down to just one screen full in Qubes Manager, which gets hard quickly. I'll either have to start creating a bunch of extra templates, or start writing down any changes I make. I'll probably just write down the changes, then lose that piece of paper DOH! -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/b6fca98a-e8e0-409a-bc33-fe982ecb357f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Kernel 4.19.43 Issues
On Sunday, May 26, 2019 at 10:46:51 AM UTC-7, awokd wrote: > Eva Star: > > > >> Seems that the 4.19.x branch was problematic with some AMD cards. > >> > > > > Maybe :) But I have problem and there is hybrid index hd + nvidia card (not > > used). In my case this kernel have problems with CPU :) > > > For a counterpoint, I think drokmed also had a Radeon card, and their > incompatibility with 4.19 has been mentioned a couple times previously > on this list: > https://www.mail-archive.com/qubes-users@googlegroups.com/msg27411.html > https://www.mail-archive.com/qubes-users@googlegroups.com/msg27685.html > > I have an older Radeon card on one of my Qubes systems. Am currently > running a full backup on it, but will test the update once it completes. > Expect I'll encounter the same problems. > > If 4.19 is this problematic, should the update be pulled? Yes, please pull 4.19.43-1 kernel update, if possible. Would solve my problem. I was curious if it was the kernel, or the xfce and lightdm, so I tried a fresh install, and when done, reboots fine. Then I didn't update anything, but I did switch over to kde/sddm with fingers crossed, hoping that was it. No such luck. I updated dom0 only, then after reboot, the same ole problem. Computer boots all the way up to the point of login, then when using kde, just appears to stop. PC not locked up, can still toggle numlock and capslock, but ctrl-alt-del doesn't work, have to press power button, then pc shuts down on it's own. I have an older ATI Radeon card too: (ATI) now called AMD Mobility Radeon HD 5870 on an Intel ASUS G73Jh 213 laptop It's not the AMD cpu for me, I have Intel. I can still get in, booting new Xen 4.8.5-6 with old kernel 4.14.74 (from fresh install). -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/39649a44-88be-45ee-8035-7d155605728e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] After last update system DEAD
On 5/26/19 8:04 AM, evas...@firemail.cc wrote: Hello, Oh no... :( After last update (kernel) system almost dead! It can boot and I have access to dom0 console, but mouse not work and there is 100% cpu usage by (1.xvdb-1 / 7.xvdc-1) and other processes eating to much cpu How to remove last update? How to recover now? Data is urgent. I have too old backups :( Please, help :((( I guess now it's not possible to reinstall, because any full update wll break the system again. And also my data. How to recover it? It's SSH M.2 drive and I don't have other machine with M.2 slot to recover. Or how to do this? :( :( :( Thanks. (new email because no access to my password and data :( ) Based on what others have posted about the update, you should try to select the prior kernel version under "Advanced options" in the grub boot menu. -- Chris Laprise, tas...@posteo.net https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/ffa62bcd-5c2e-8396-fc55-1b81d3fe3dd4%40posteo.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] After last update system DEAD
evas...@firemail.cc: > Hello, > Oh no... :( > After last update (kernel) system almost dead! > It can boot and I have access to dom0 console, but mouse not work and > there is 100% cpu usage by (1.xvdb-1 / 7.xvdc-1) and other processes > eating to much cpu > How to remove last update? How to recover now? > Data is urgent. I have too old backups :( Please, help :((( > > I guess now it's not possible to reinstall, because any full update wll > break the system again. And also my data. How to recover it? It's SSH > M.2 drive and I don't have other machine with M.2 slot to recover. Or > how to do this? :( :( :( > Thanks. > > (new email because no access to my password and data :( ) > Don't touch your existing M.2 drive. Get a spare drive (spinning rust is OK) at least as large as your M.2 drive and that you can attach to your machine (e.g. with a USB SATA dock). Download Tails to a USB stick. Boot your machine into Tails. Connect your spare drive. `fdisk -l` to be sure you have the right device names for all your disks. `dd` your M.2 to the spare drive. Now `sync` the disk and detach it. You now have a backup of your current state. If you _need_ to access some VM data now, you can (with major negative security implications) decrypt your M.2 disk manually with `cryptsetup`, navigate to /var/lib/qubes/appvms/ and use `losetup` to help mount the VM's data disk in Tails so you can copy off whatever data you urgently need. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/a5939499-0fbf-f337-4dae-de863375d755%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Secondary hdd as storage
On 5/26/19 1:14 PM, Eva Star wrote: I have secondary drive with windows 10. I never run windows, but I keep it, because it maybe be useful(needed) some day. But now I want to use this secondary drive as storage for some of my VMs. Maybe 1) part of this drive and keep windows or 2) whole drive for storage. What are the possibilities? Any partitioning and formatting that Linux/fedora25 supports should be possible. What's better? What is more convenient? The most convenient and flexible is Btrfs, followed by Thin LVM. Qubes has "full" integration with these two. How to implement it? Best bet is to first partition what you need (reducing Windows partition if necessary), then setup encryption on it with 'cryptsetup luksCreate /dev/devname'. Then you can add that device to /etc/crypttab. Next, format it: For Thin LVM there are guides on the net that describe this multi-step process of setting up a volume group and then creating a thin pool within it. For Btrfs its much easier, just use 'mkfs.btrfs' on the luks volume. Finally, if you want to run VMs from this volume use 'qvm-pool' to define a storage pool that points to it. If you don't setup a pool you can still use 'qvm-block attach' to let VMs access the space as secondary disks. I guess need to reduce size of current windows partition then empty part of hdd to format to ext4 or other linux filesystem and then it will be possible to use as storage for appvms? Thanks -- Chris Laprise, tas...@posteo.net https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/776c129e-6415-bed8-1e1b-92edd6e5e411%40posteo.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Kernel 4.19.43 Issues
Eva Star: Seems that the 4.19.x branch was problematic with some AMD cards. Maybe :) But I have problem and there is hybrid index hd + nvidia card (not used). In my case this kernel have problems with CPU :) For a counterpoint, I think drokmed also had a Radeon card, and their incompatibility with 4.19 has been mentioned a couple times previously on this list: https://www.mail-archive.com/qubes-users@googlegroups.com/msg27411.html https://www.mail-archive.com/qubes-users@googlegroups.com/msg27685.html I have an older Radeon card on one of my Qubes systems. Am currently running a full backup on it, but will test the update once it completes. Expect I'll encounter the same problems. If 4.19 is this problematic, should the update be pulled? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/081b5f7e-d4dd-ad2f-ce53-7088682bb982%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Kernel 4.19.43 Issues
> Seems that the 4.19.x branch was problematic with some AMD cards. > Maybe :) But I have problem and there is hybrid index hd + nvidia card (not used). In my case this kernel have problems with CPU :) -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/7f8e34ae-375c-4904-85c4-64191996c6e7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Kernel 4.19.43 Issues
Like others have reported, I updated my Qubes system earlier today with the 4.19.43 kernel along with the xen updates. Past updates have gone smoothly for the duration of my running Qubes but unfortunately this one wasn't. The update itself installed fine with no issues or errors. I was able to reboot successfully but when the system gets to the normal LightDM user logon screen, the monitor output is garbled and has many artifacts. If I attempt to log in, after a few seconds of the system attempting to start up the Qubes Desktop, I get kicked back out to the login screen again. The system will keep looping in such a manner. I'm able to boot back into the system using the older 4.14.116 and everything works again so I suspected the issue had to do with the 4.19.43 kernel and the system's graphics card. I'm running an AMD processor with a Radeon R7 graphics card. Upon searching Google, it appears that there are known issues with the 4.19.x kernels with certain AMD systems/cards. For example: https://bugs.freedesktop.org/show_bug.cgi?id=108981 https://forum.manjaro.org/t/upgrade-to-4-19-disables-my-amdgpu/64920/5 Seems that the 4.19.x branch was problematic with some AMD cards. Since the graphics are borked and I can't get into the system with 4.19.x, what might be the best way to try to troubleshoot what the specific issue might be? Thanks in advance. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/932614dd-2f2d-f81a-bc6f-b94fb1d7e94b%40go-bailey.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] offline backup/restore of qubes, boot from usb
drok...@gmail.com: Hi, I'd like to boot a usb, and do full backup/restores of a qubes install, offline. Anyone doing this already? Some kind of qubes specific recovery usb, with lots of room for backups. In my opinion (others might have better ideas), Qubes isn't the right tool for that job. Look for something that can do a full image/bare metal backup of your internal drives. It doesn't have to be very fancy. Nearly any distro that can boot as a liveUSB can run "sudo cp /dev/sdd sddbackup" [where sdd is an example of an internal system drive as viewed from the liveUSB command line]. Note that the file generated this way will be equivalent in size to your internal drive's size. Personally, I use qubes-backup and do a reinstall & restore of Qubes on the rare occasions I need to instead of the above. Full image backups can get impractical. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/c856b647-91be-a1c1-81f6-d05edf6ff0fd%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Secondary hdd as storage
I have secondary drive with windows 10. I never run windows, but I keep it, because it maybe be useful(needed) some day. But now I want to use this secondary drive as storage for some of my VMs. Maybe 1) part of this drive and keep windows or 2) whole drive for storage. What are the possibilities? What's better? What is more convenient? How to implement it? I guess need to reduce size of current windows partition then empty part of hdd to format to ext4 or other linux filesystem and then it will be possible to use as storage for appvms? 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/98ad64dd-d18f-44c1-b379-e78ffc28fa03%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: After last update system DEAD
'Evastar' via qubes-users: Again, what to do now? Never update or try to wait for month and then update? Short term, continue applying template updates as usual. If you run "sudo qubes-dom0-update", you can check for updates, but make sure to choose not to apply them with N. Wait for the next dom0 kernel release before trying to upgrade dom0 again, then pick and choose from my suggestions in the last 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/df0d5648-eb3f-4bba-d560-9c7661dc0a13%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: qubes updater broken? just had to re-install qubes
Thanks for the note...I saw this just before my recent Dom0 and other updates. I too had similar symptoms including: " I noticed that several qubes didn't shutdown quite right, click on the right Q button, they were still there, but showed zero memory usage." I did a back up before shutting down...very good advice and reminder! Everything booted up fine for me...little sketchy for a while but I had no problem with the 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/ac4b9403-1993-494c-9df6-3ffe30c5e6a2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: After last update system DEAD
> Did you notice any other errors around the soft lockup? Try searching > for them; it would be good to figure out what's causing the lockup, but > it can be hard to do. Only one error: all system very unresponsive, :) And as I'm already note 100% cpu usage by some processes. Also I saw strange "battary" icon at taskbar. It was like zero with some little dot image at the bottom corner of zero(gray) battery. System very quick take "dead lock" and freeze. Only Qubes Manager staring at this time. It freeze at 45%, at 91% and some time Qubes Manager load successfully, but after this system freeze. I guest problem not with some software, but how processor work with this kernel. > Most important thing is to backup your system before dom0 kernel updates. I have this idea on my mind after I install this new update and before reboot, but other mind come "what could be wrong. I update it since Q4 exists and never had problems with update :)". Again, what to do now? Never update or try to wait for month and then update? Thank you very much for your help! -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/XDiSl2Z1LU4w9tgvbWMQODym3wZrgZTqKQBc4oiDEjbOxDa62F7EV9jRHz5-S1xWapMkUI6MfjJoGnTiFsBUHGHbX8qO9xaF6NolU-OlVh0%3D%40protonmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] offline backup/restore of qubes, boot from usb
Hi, I'd like to boot a usb, and do full backup/restores of a qubes install, offline. Anyone doing this already? Some kind of qubes specific recovery usb, with lots of room for backups. 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/87f25361-e5a6-41cc-88ae-a2c66f6f13e2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: After last update system DEAD
evas...@firemail.cc: By the way, I got the idea and switched to other tty before login to the system where Qubes Manager and other tasks start. It give me some time to use the system. And I found the bug at std error output: ! wachdog: BUG: soft lockup - CPU#3 stuck for 23s! [1.xvda-1:4325] kernel changed successfully to previous one. What next? yes, now I will do new backups ASAP. But what next? Never run qubes-dom0-update? Did you notice any other errors around the soft lockup? Try searching for them; it would be good to figure out what's causing the lockup, but it can be hard to do. Most important thing is to backup your system before dom0 kernel updates. If uptime is a priority for you, wait for a week or so when dom0 kernel updates come out and monitor qubes-issues and the mailing lists to see if others are reporting problems. If so, hold off until they get addressed. If uptime is critical and you can afford it, get another machine with the same hardware configuration, and test out updates there first before applying them to your production system. See also Chris's suggestion https://www.mail-archive.com/qubes-users@googlegroups.com/msg27411.html. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/230c659a-9e93-018c-f7a3-fc35b33324ac%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Add this to the Qubes docs page?
Hi, I was trying to figure how how to install the onlykey hardware token program and for whatever reason thier page, https://docs.crp.to/qubes.html, isnt the first thing that pops up when I searched so I thought I'd suggest putting a link to thier qubes setup page. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/b56bca14-9489-1338-b966-d4f6969e8e87%40posteo.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: After last update system DEAD
By the way, I got the idea and switched to other tty before login to the system where Qubes Manager and other tasks start. It give me some time to use the system. And I found the bug at std error output: ! wachdog: BUG: soft lockup - CPU#3 stuck for 23s! [1.xvda-1:4325] kernel changed successfully to previous one. What next? yes, now I will do new backups ASAP. But what next? Never run qubes-dom0-update? 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/f8b4b009de708356a8b765b43a4fa3ee%40firemail.cc. For more options, visit https://groups.google.com/d/optout.
[qubes-users] R4: Graphics issues: flashbacks and rendering freezes
Hello, I have two rendering issues. Maybe they are related, maybe they aren't. ## 1. screen flashbacks I don't remember when it started. Some parts of screen have short random flashbacks, i.e. it shows the content shown some time ago. You can see a short video there: https://drive.google.com/file/d/1ypHdDKiPpeE3SfwsdAwDzR3e-AyN932Q/view?usp=sharing I am not moving the cursor, but it sometimes flashes the previous state. This happens even on lockscreen (=> dom0-related). I remember I have screenshotted it (I can't find the screenshot, though), so it does not look like screen controller issue. Usually, alt+tab; alt+tab (i.e., switching to another window and then back) helps, at least for some time. ## 2. screen rendering freezes This one is likely related to the recent update. Screen rendering freezes completely (except mouse cursor) with kwin in some deterministic cases: * Alt+tab. * Screen rotated by 90° or -90°. (It is fine for 180°.) With Xfwm, I see no such issue. ## Some info about my computer CPU+GPU: Intel i7 7500U $ cat /proc/cmdline root=/dev/mapper/qubes_dom0-root rd.lvm.lv=qubes_dom0/root rd.lvm.lv=volatile i915.alpha_support=1 rhgb quiet rd.qubes.hide_all_usb plymouth.ignore-serial-consoles $ uname -r 4.19.43-1.pvops.qubes.x86_64 Do you have any idea what to do with it? Regards, Vít Šesták 'v6ak' -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/47e9caa3-5f7b-4698-a94e-8fc3b525ed5d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: After last update system DEAD
Maybe it's possible to return to this emergency mode? System freeze until Qubes Manager start. It can freeze at 45% or at 91% or at any point. I see high cpu usage. It freeze because of this. I shutdown it before at this point and filesystem corrupt. Need the way to access /boot/efi without actual system load or I will lose all data and nothing will changed... -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/525fc0e42b6a4589f719abdb82d66d9a%40firemail.cc. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: After last update system DEAD
Filesystem corruption is a different issue. In the emergency console, "fsck /dev/mapper/qubes_dom0-root". Answer y to everything it asks, then "reboot". If that lets you get back into Qubes, DO NOT DO ANYTHING ELSE UNTIL RUNNING A FULL BACKUP. Then try editing xen.cfg as previously described. Thanks! Booted. I'm not sure that it's possible to make full backup now, because system freeze time to time with this kernel. But I will try. It's a good idea. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/37b34f11d64009824f8a3be95f0c3249%40firemail.cc. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: After last update system DEAD
evas...@firemail.cc: On 2019-05-26 15:57, 'awokd' via qubes-users wrote: Log(url): i DOT imgur DOT com SLASH Z8GbXLJ.jpg it request to run fsch or e2fsck. What I must run first and how? Then if filesystem will be fixed, how to mount boot to change it? I guess this emergency console can help me, because dom0 console after boot not usable now (system can freeze). Here is a good point to change things. Hope that it's possible to recover filesystem here. Filesystem corruption is a different issue. In the emergency console, "fsck /dev/mapper/qubes_dom0-root". Answer y to everything it asks, then "reboot". If that lets you get back into Qubes, DO NOT DO ANYTHING ELSE UNTIL RUNNING A FULL BACKUP. Then try editing xen.cfg as previously described. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/51d2efbc-55cc-6e07-9e66-5ca7cc1706c5%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: After last update system DEAD
On 2019-05-26 15:57, 'awokd' via qubes-users wrote: Log(url): i DOT imgur DOT com SLASH Z8GbXLJ.jpg it request to run fsch or e2fsck. What I must run first and how? Then if filesystem will be fixed, how to mount boot to change it? I guess this emergency console can help me, because dom0 console after boot not usable now (system can freeze). Here is a good point to change things. Hope that it's possible to recover filesystem here. 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/0b9ce701cd9af700435436ec0595f6f8%40firemail.cc. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: After last update system DEAD
On 2019-05-26 16:32, 'awokd' via qubes-users wrote: Yes, but be aware that it may mount the boot directory you're looking to edit underneath a different location, so watch the messages when you do. What is correct "mount" command to do this? And to fix filesystem then... -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/63c611b6eb33a0c34d7f8efcfc89b2f8%40firemail.cc. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Template Settings not showing
ptilden: Hello, I have installed Qubes 4.0.1 I need to configure a printer in the Template VM. I start fedora-29 TemplateVM and select Template:fedora-29 -> fedora-29: Settings and after a bit of disk activity nothing appears. I have also started Template:fedora-29 -> fedora-29: Terminal and typed the command system-config-printer and bash tells me that the command is not found. Are you sure you want to connect a printer to your template? Usually they get connected to the AppVM/qube built on a template. In any case, with a qube based on the debian-9 template you'd add Print Settings to your application list and configure that way. Fedora 29 might be missing the equivalent package; try adding system-config-printer to your template with dnf. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/93477033-4401-4ede-aa55-2c1bb6c43e03%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: After last update system DEAD
evas...@firemail.cc: On 2019-05-26 15:57, awokd wrote: First thing to try is to rollback the dom0 kernel update. If you're using UEFI boot, "sudo nano /boot/efi/EFI/qubes/xen.cfg" and change the default kernel line at the top to point to the previous version number. Save and reboot. If you're not sure how to do that, send me your xen.cfg file. Totally DEAD :( After reboot -> boot -> system freeze because high cpu ussage -> reboot... Now it boot only to console: generating "/run/initramfs/rdsosreport.txt" Entering emergency mode. Exit the shell to continue etc. Also this message say that it's possible to mount boot. Maybe it's good ideato mount it, change setting and then try to boot again? Yes, but be aware that it may mount the boot directory you're looking to edit underneath a different location, so watch the messages when you do. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/6e80f360-640e-c519-03ec-4709c83cebc4%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: After last update system DEAD
On 2019-05-26 15:57, awokd wrote: First thing to try is to rollback the dom0 kernel update. If you're using UEFI boot, "sudo nano /boot/efi/EFI/qubes/xen.cfg" and change the default kernel line at the top to point to the previous version number. Save and reboot. If you're not sure how to do that, send me your xen.cfg file. Totally DEAD :( After reboot -> boot -> system freeze because high cpu ussage -> reboot... Now it boot only to console: generating "/run/initramfs/rdsosreport.txt" Entering emergency mode. Exit the shell to continue etc. Also this message say that it's possible to mount boot. Maybe it's good ideato mount it, change setting and then try to boot again? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/c8d7bf962eb7f15855c0d0b0f2212e39%40firemail.cc. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Template Settings not showing
Hello, I have installed Qubes 4.0.1 I need to configure a printer in the Template VM. I start fedora-29 TemplateVM and select Template:fedora-29 -> fedora-29: Settings and after a bit of disk activity nothing appears. I have also started Template:fedora-29 -> fedora-29: Terminal and typed the command system-config-printer and bash tells me that the command is not found. dom0 and fedora-29 have all updates applied. What do I do next? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/77dcfd62-b7f5-46e5-a3d0-f8d8f8451b15%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: After last update system DEAD
evas...@firemail.cc: Okey... keep calm... Time to time I can use dom0 console without troubles (sudo qubes-dom0-update also still work by no fix still come :( ) I guess now need to somehow change new kernel to old one? How to do this? I guess I'm at UEFI mode (new notebook) 1) boot from some qubes installed usb flash and I will see recovery mode? Or not? 2) I tried to access /boot/efi/ to edit xen.cfg (only it must be edited?), but no access. sudo cd /boot/efi/ (success) then-> sudo ls show me my home folder. How to get access to /boot/efi and what I must edit to return to my old kernel? 3) or any other recovery methods please :) Thanks! First thing to try is to rollback the dom0 kernel update. If you're using UEFI boot, "sudo nano /boot/efi/EFI/qubes/xen.cfg" and change the default kernel line at the top to point to the previous version number. Save and reboot. If you're not sure how to do that, send me your xen.cfg file. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/f7ea68d7-6f55-9f2e-3a8c-fc4ba4e94855%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: After last update system DEAD
Okey... keep calm... Time to time I can use dom0 console without troubles (sudo qubes-dom0-update also still work by no fix still come :( ) I guess now need to somehow change new kernel to old one? How to do this? I guess I'm at UEFI mode (new notebook) 1) boot from some qubes installed usb flash and I will see recovery mode? Or not? 2) I tried to access /boot/efi/ to edit xen.cfg (only it must be edited?), but no access. sudo cd /boot/efi/ (success) then-> sudo ls show me my home folder. How to get access to /boot/efi and what I must edit to return to my old kernel? 3) or any other recovery methods please :) 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/513ac84ee49fc40e0b7d3a97f4b896ef%40firemail.cc. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] qubes backup and restore question
drok...@gmail.com: What is the point of backing up a qube, if you can't restore to it? I'm restoring a full backup, and instead of restoring to qubes, it's creating new ones with different names. WTF! What the hell am I supposed to do now? Delete the original qubes, and rename the restores? I'm guessing that will break a bunch of links, which I'll have to manually fix. Am I the only person that thinks this is totally stupid? And it says the restored dom0 files are located in some other directory. What the hell am I supposed to do with that? Dom0 can't be restored? Are you kidding me? The easiest way to restore qubes with the same names is to delete the old ones prior to restore. You'll want to leave or clone an equivalent of sys-usb and somewhere to mount the backup for the restore, so don't delete them all. See https://github.com/QubesOS/qubes-issues/issues/4946 on how to move the restored dom0 files to the right place, it's pretty straight-forward. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/8a82b2e0-680b-a3b4-18e7-2cee6b037f26%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
[qubes-users] After last update system DEAD
Hello, Oh no... :( After last update (kernel) system almost dead! It can boot and I have access to dom0 console, but mouse not work and there is 100% cpu usage by (1.xvdb-1 / 7.xvdc-1) and other processes eating to much cpu How to remove last update? How to recover now? Data is urgent. I have too old backups :( Please, help :((( I guess now it's not possible to reinstall, because any full update wll break the system again. And also my data. How to recover it? It's SSH M.2 drive and I don't have other machine with M.2 slot to recover. Or how to do this? :( :( :( Thanks. (new email because no access to my password and data :( ) -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/f4a6382ba2757bd7dbbc42dfd1487a0d%40firemail.cc. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: WARNING: don't update qubes, will break your install
On Saturday, May 25, 2019 at 10:55:44 PM UTC+2, dro...@gmail.com wrote: > 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. 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. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/d3c43284-1fd9-4d03-8680-5908ea272f60%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
