tirsdag den 13. november 2018 kl. 12.26.58 UTC+1 skrev unman: > On Tue, Nov 13, 2018 at 12:00:40AM -0800, aaq via qubes-users wrote: > > Hello! > > > > I have broken the GUI in dom0 in some weird way. > > I tried to install KDE, then I tried to remove it again, before realising > > that I was fine with having it. Unfortunately, when I wanted to reinstall > > it, dnf kept saying that I already had the group installed, so I couldn't > > just run the `sudo qubes-dom0-update @kde-desktop-qubes`. > > > > I ended up doing a `sudo dnf remove @kde` in dom0, which resulted in the > > package `qubes-gui-dom0` being deleted. I assume this is the package that > > is needed to show GUI from different VMs. > > > > Basically, dom0 works fine. All of dom0 GUI works as intended, I am happily > > using KDE and SDDM. With that being said, none of my VMs work, so I can't > > really use my machine for anything. > > > > I found this thread > > https://groups.google.com/forum/#!topic/qubes-users/7GeA1_xCeTg > > > > But I cannot start VMs with `--no-guid` flag. I cannot for the love of my > > life get the package back.. I haven't cleared my cache or anything, but for > > some reason I am not able to install `qubes-gui-dom0` again without a > > network connection. Since my VMs don't start properly, I don't have network. > > > > Is there any solution to this :S > > > > PS: I backed up all my VMs the other day (happy coincidence) so I guess I > > could just reinstall, but I am quite happy with my current install :( > > > > Thanks for any input! > > > > The obvious solution would be to download the files in another machine > and then transfer them to dom0 using a transfer disk. > If you're on a laptop and have a sys-usb set up then you will need to > interrupt boot and edit the kernel parameters to remove the section that > says rd.qubes.hide_all_usb - that will allow you to connect USB to > dom0 at some cost to your security. > > If you dont want to do that we can try troubleshooting your inability > to start headless qubes. > If you wnat to do that then try starting just sys-net from the command > line and check the logs, and report back any error from the logs or > command line.
Thank you so much for you time! When having all Qubes shutdown, I run qvm-start --verbose sys-net No feedback in the terminal. I cannot seem to find anything in the logs that might seem interesting either. I don't know if I am looking the wrong places. I looked into /var/logs/qubes/ and then anything with sys-net in it. I also looked at the xen logs for the VM, but again, I can't seem to find anything special that stands 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/5f1921d0-3bdd-422b-ab29-2e577e893d3b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
