Hi,
just removed some unnessesary progs on a stand-alone-vm and after some sudo dnf remove comes: “We trust you have received the usual lecture from the local SystemAdministrator. It usually boils down to these three things: … and so on”
somebody any idea?
i think, i somehow killed some settings with removing cheese and keepassxc… no idea how.
I can not even move the stuff to a new made vm… puh…
thanks, this is a real rabbit hole… have no idea, how does it suddenly happend!
i created it just over the qube manager.
It shows me, that the vm has sys-firewall as netvm, IP x.x.x.x IPBACK is empty and then Gateway x.x.x.x
The IP of the sys-firewall is wrong (!!!)
how could it be??
In the resolv.conf of the vm i have two nameservers
10.139.1.2
10.139.1.1
don’t know what it means in that context.
#update:
vm and gateway (fw) IPs seem to be write 10.137.x.x
not even qubes-usb-proxy is installed in the VM… WTF???
it seem to be completely isolated… so i have no idea, how can i get my data copied from there to another vm and just kill this rabbit hole after that.
That’s what I wanted to do, but i can not move any files to the created vm.
If i rightklick on the file, there is no option to copy it to another vm anymore.
I can not even mount usb to the ruined vm.
So what is the possibility in that case to get the data I see (and r/w)?
I don’t know how I didn’t remeber to point this out to you first… And it’s probably too late now, but if you break a VM you can always restore it to the last state it was in:
If it were an AppVM (I guess the encouraged option), it would be as simple as switching the template. But since it’s a standalone, it’s a bit more complicated.
I guess something you can do is to a backup of that qube and then perform an emergency restore of that (potentially at a later date). But this is a complex process.