Thank you all! I've managed to disable the shortcut on xfce! Now I can finally use FF in private more :) Didn't find anything related with the ACPI errors though. I think its best if I can raise an issue in github?
April 29, 2018 7:38 PM, "awokd" <[email protected]> wrote: > On Sat, April 28, 2018 8:15 pm, [email protected] wrote: > >> Hi Everyone. >> >> Whenever I try to get to private more in FF by pressing ctrl+shift+p all >> my VMs get paused. Is there a reason for this? Is it possible to disable >> it? Whenever that happen I have to manually select each VM and resume it, >> which is kind of annoying. > > There is a way to customize the XFCE keyboard shortcuts, but I can't > remember how exactly. Think it involves editing a file. Try searching this > mailing list- I like to use > https://www.mail-archive.com/[email protected]. > >> Qube manager is no longer started by default like in version 3.2, instead >> I got now an icon on the top right corner that allows to invoke >> operations on the running VMs. But some of the VMs in there are show an >> inconsistent state (I'm only allow to check the logs, set the preferences >> or kill it and not shut them down as with some of the displayed VMs) >> there's a cursor looping for the inconsistent VMs. Is there a way to fix >> this? > > https://github.com/QubesOS/qubes-issues/issues/3660 > >> Also Qube manager shows all VMs and not only the running ones, is >> there an option to show only the VMs that are running? Qube Manager >> doesn't refresh the state of the VMs as it happened in Qubes 3.2. Instead >> I have to manually hit refresh whenever I want to check when a VM has >> stopped or started. Is there a way one could have check the state of the >> VMs on Qube manager as it happened on version 3.2? > > Qube Manager was originally not going to be included in 4.0 and got > re-added relatively late so it still has some display issues. To refresh a > single VM, you can click on a different one then back on that VM. It's a > little faster than refreshing them all. > >> During the boot and before unlock the LuKS volume I'm getting a lot of >> ACPI errors regarding Namespace lookup failure: > > I get these too but they don't seem to hurt anything. Try searching > https://github.com/QubesOS/qubes-issues/issues to see if there's more info > in there. > >> Shutdown is also taking an huge amount of time to complete spending lots >> of time waiting for the disk to be ready. > > Try manually shutting down any AppVMs you have running first, before > shutting down Qubes. -- 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/1effa0f9bc9c27512c995277f3f9ac15%40disroot.org. For more options, visit https://groups.google.com/d/optout.
