Den tir. 13. nov. 2018 kl. 14.12 skrev unman <[email protected]>:
> On Tue, Nov 13, 2018 at 01:46:39PM +0100, 'Ahmed Al Aqtash' via > qubes-users wrote: > > Den tir. 13. nov. 2018 kl. 13.38 skrev unman <[email protected] > >: > > > > > On Tue, Nov 13, 2018 at 04:31:49AM -0800, aaq via qubes-users wrote: > > > > 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 havent said what version of Qubes you are running. > > > What happens when you run qvm-start --verbose sys-net again? > > > > > > > I am running Qubes OS 4.0.0, only vanilla repos, only stable. > > > > Nothing happens when I run qvm-start --verbose sys-net. It just starts as > > if nothing is wrong. No feedback in the terminal. > > If I run it again, while sys-net is running, is simply outputs that > sys-net > > is already running. > > > > That's good. > Can you confirm you're using sys-firewall as updateVM? > qubes-prefs in dom0 - look at value for updatevm > > sys-firewall is set as updateVM yes > If so, when you start sys-firewall, and try again, do you get the same > response? > > Yes, the exact same response. It starts up as normal, then gives the message stating that it is already running. What is the output when you attempt the install? Well, I know that I am not connected to anything right now, since there is no wifi near me that I have connected to before. I tried beaming from my phone, and it didn't say that anything was connected. The output when I run: sudo qubes-dom0-update qubes-gui-dom0 Is: Using sys-firewall as UpdateVM to download updates for Dom0; this may take some time... Failed to synchronize cache for repo 'updates', disabling. Failed to synchronize cache for repo 'fedora', disabling. Failed to synchronize cache for repo 'qubes-dom0-current', disabling. Failed to synchronize cache for repo 'qubes-templates-itl', disabling. No match for argument: qubes-gui-dom0 Error: Unable to find a match It takes a while for it to bail 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CA%2B3%2BOvg-%3D_B%3D5kwidTYuc_RF9h%2BrA_ePB%2B%2BpuLLdBs-oFaqyPw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
