[qubes-users] Enabling and disabling external monitors based on laptop lid status
I'm scratching my head over this... How are people configuring their QubeOS 4 instances to enable and disable external monitors based on the laptops lid status? Current laptop (EliteBook 1040 g2) works flawlessly with Qubes (even suspend...) and my only current issue is that I have to manually enable and disable screens when I dock the machine. Normally, I'd use ACPI hooks and I'm guessing this needs to be done in dom0 (I don't suppose any DomU's have access to reconfigure screens?) but acpid isn't available om dom0. What would you recommend? I guess a possible solution could be to source an acpid RPM, or find the source code, and install that manually in dom0? Best regards Mads -- 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/DB7PR02MB43790171789259B3B5C6F305BDEA0%40DB7PR02MB4379.eurprd02.prod.outlook.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Enabling and disabling external monitors based on laptop lid status
On 10/4/18 11:10 AM, 'Mads R. Havmand' via qubes-users wrote:
> I'm scratching my head over this... How are people configuring their QubeOS 4
> instances to enable and disable external monitors based on the laptops lid
> status?
I've been through this too - see below.
> Current laptop (EliteBook 1040 g2) works flawlessly with Qubes (even
> suspend...) and my only current issue is that I have to manually enable and
> disable screens when I dock the machine.
I too manually enable/disable screens but I have configured a keyboard
shortcut that runs a custom shell script with xrandr commands based on
the presence - or lack thereof - of my external monitor.
All it takes is to dock the laptop and hit the shortcut - lightning fast.
> Normally, I'd use ACPI hooks and I'm guessing this needs to be done in dom0
> (I don't suppose any DomU's have access to reconfigure screens?) but acpid
> isn't available om dom0.
Yes this needs to be done in dom0.
On moderm distros systemd handles lid events provided no other
application has inhibited ("overridden") the event. See `man logind.conf`.
In the case of Qubes, Xfce's power manager overrides HandleLidSwitch=
(but not HandleLidSwitchedDocked=). There's an option in xfce power
manager to turn the display off when the lid is closed but it won't be
able to differentiate when the laptop's docked or not so it's useless.
IIRC there are a few ways to run a script based on lid events without
resorting to installing acpid (which is not even guaranteed to work):
eg. listening for dbus lid close/open events, monitoring
/proc/acpi/button/lid/LID/state, ... ; An alternative is to run stuff on
dock/undock events, via dbus and/or udev rules.
In the end my hacky keyboard shortcut "solution" worked well enough that
I didn't spend time to investigate the solutions above...
> What would you recommend? I guess a possible solution could be to source an
> acpid RPM, or find the source code, and install that manually in dom0?
>
> Best regards
> Mads
>
--
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/f6fb81f1-bfb8-0cd0-8b96-3bfcafee8d5c%40maa.bz.
For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Networking between qubes and HVMs
On Wed, Oct 03, 2018 at 10:47:20AM -0700, jmarkdavi...@gmail.com wrote: > I literally just read that and going to post an apology for repeating a > question > No problem. If you need some further pointers shout 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/20181004142031.7v4xwjagkcydgron%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Installing/updating apps in a TemplateVM
On Friday, 28 September 2018 14:14:55 UTC+1, unman wrote: > On Fri, Sep 28, 2018 at 01:56:41PM +0100, unman wrote: > > On Fri, Sep 28, 2018 at 01:02:22PM +0100, unman wrote: > > > On Fri, Sep 28, 2018 at 03:15:22AM -0700, OutdoorAcorn wrote: > > > > On Friday, 28 September 2018 10:48:19 UTC+1, unman wrote: > > > > > On Fri, Sep 28, 2018 at 05:09:22AM +, 'awokd' via qubes-users > > > > > wrote: > > > > > > > > > > > > > > > > > > OutdoorAcorn: > > > > > > > I've just installed Qubes OS 4.0 on my old laptop to get the hang > > > > > > > of it before I (hopefully) make my leap over from Windows! > > > > > > > > > > > > > > I wanted to install some new software in the personal and work > > > > > > > domains so I went to the "Qubes Menu -> Template: fedora-26 -> > > > > > > > fedora-26: Software" and clicked the Install button for an app > > > > > > > however it only ever displayed pending. I opened up the Qubes > > > > > > > Manager and noticed that no NetVM was assigned to any of the > > > > > > > templates. I opened the settings and assigned it sys-firewall > > > > > > > which then allowed me to install programs. > > > > > > > > > > > > > > On the https://www.qubes-os.org/doc/software-update-vm/ page > > > > > > > under "Notes on trusting your TemplateVM(s)" heading it says: > > > > > > > > > > > > > > "Only install packages from trusted sources – e.g. from the > > > > > > > pre-configured Fedora repositories. All those packages are signed > > > > > > > by Fedora, and we expect that at least the package’s installation > > > > > > > scripts are not malicious. This is enforced by default (at the > > > > > > > firewall VM level), by not allowing any networking connectivity > > > > > > > in the default template VM, except for access to the Fedora > > > > > > > repos." > > > > > > > > > > > > > > This no longer seems the case in Qubes OS 4.0 - no NetVM is > > > > > > > attached to the TemplateVMs and no default firewall rules. Okay, > > > > > > > onto the questions: > > > > > > > > > > > > > > 1) Have these defaults been missed out from the Qubes OS 4.0 > > > > > > > install? > > > > > > > 2) Or is the documentation out of date and it's now recommended > > > > > > > to do something else? > > > > > > > 3) How should I go about installing/updating apps in the > > > > > > > TemplateVMs? > > > > > > > 3a) permanently attach sys-firewall and create firewall rules to > > > > > > > only allow trusted repos as the docs currently suggest > > > > > > > 3b) or only attach sys-firewall when updating/installing and > > > > > > > disconnect afterwards? > > > > > > > > > > > > The docs are right, but what they mean is that you can't use the > > > > > > "Software" > > > > > > application to install apps in templates. You should leave NetVM on > > > > > > (none) > > > > > > on the templates and instead use dnf on Fedora or apt on Debian. > > > > > > > > > > To put a bit more flesh on that: > > > > > 1. The mechanism has changed in Qubes 4.0, so the old defaults no > > > > > longer > > > > > apply. > > > > > Instead of using restricted access to a netvm, in Qubes 4.0 the update > > > > > proxy is reached by qrexec calls. This provides better insulation for > > > > > the template. > > > > > You should not attach a TemplateVM to a netVM. > > > > > 2. The docs should be clarified. > > > > > 3. Open a terminal in the TemplateVM and run 'sudo dnf' or appropriate > > > > > package manager, as awokd says. > > > > > 3a. For reason above do not do this in Qubes 4.0 > > > > > 3b. For reason above do not do this in Qubes 4.0 > > > > > > > > > > > > > > > If you want to install software not already packaged, then download > > > > > (and > > > > > verify) it in a online qube and qvm-move it to the TemplateVM. Be > > > > > aware > > > > > of the additional risks involved. > > > > > > > > > > unman > > > > > > > > > > > > Thanks for the response awokd and unman. I can confirm that this works > > > > as expected using dnf and apt. Reading further down on that page it > > > > explains in more detail how this is done via the qubes-update-proxy > > > > service. > > > > > > > > If you can't install apps via the "Software" gui app how come it is > > > > listed in "Qubes Menu -> Template: fedora-26"? It seems like this is > > > > just going to lead newbies like myself down a dead end. > > > > > > > > You could go as far to say that the "Software" app isn't useful and > > > > should be removed. It can only be used in an AppVM or DVM (with an > > > > attached NetVM) and in the case of the AppVM the installed app would be > > > > removed on reboot. > > > > > > > > Thanks again for clearing this up for me. > > > > =) > > > > > > > > > > I'm not a Fedora user, but I would have expected the Software gui to > > > work. The proxy use is set in dnf config and it would be surprising if > > > the GUI program didn't honour that. > > > Certainly in Debian based Ubuntu all the dpkg based package managers u
[qubes-users] hardware-level attack
Chinese government vs Supermicro servers: https://www.bloomberg.com/news/features/2018-10-04/the-big-hack-how-china-used-a-tiny-chip-to-infiltrate-america-s-top-companies -- 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/CACXcFm%3Dd4NmQ-wTc_Q2hotq207-zwiJYwmhqQ1Xfchkbp-2gPg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Installation of windows 7 on qubes 4.0 fails
Hello, I'm running qubes os 4.0. I tried to set up windows 7 HVM. I tried both ultimate and home (most basic one) editions with this same effect. I managed to get installator running after upgrading dom0, disabling memory balancing and setting amout of ram to 2048M. After installation HVM starts to shut down, its screen disappears but on qubes manager i still see yellow dot in the state field for this vm. After an hour i pressed stop button for this vm and killed it due to 20s timeout. When i tried to power it up i got message from windows that installation was interrupted and i need to repeat it. I have made about 3 attempts to set up this vm with this same effect. I was considering just setting up virtualbox in some appvm but i was told that this is impossible. Is there any workaround for my problem other that setting up virtual machine with windows on other physical computer? I do not need very specyfic version of windows as long as it will be 64bit and qubes tools for that will be working. I can paste logs and config just please tell me what will be usefull. -- 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/20181004174754.GC60808%40hackerspace.pl. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] I still want anti virus with Qubes OS. but which one is compatible?
> Going beyond that, antivirus is an option. One way to run it is from a dispVM > to which you attach various private volumes (one at a time) for scanning. > An implementation of a similar idea across several VMs is: VM1: any TemplateVM with clamav installed. VM2: AppVM based on above, which is network-connected so it can download new virus definitions. /var/lib/clamav contains the virus definitions so make it a bind-dir. VM3: DisposableVM based on the above, which is offline, that does the actual scanning. To scan a VM, use qvm-block to attach a VM's private volume to the disposable VM.[1] The actual updating and scanning can be streamlined using shell scripts run from dom0. I think the nice properties of this setup are: * distro-packaged, open source antivirus* antivirus lives outside the VM you are scanning * since the antivirus processes a lot of untrusted input, scans are done from a disposable VM3, so if it is compromised in the course of a scan, only that session is compromised* since the antivirus may process a lot of sensitive information, VM3 is also offline, making it harder for compromised antivirus to exfiltrate anything. [1]To make a DisposableVM have different NetVM than its template, you can use for VM3 the static DisposableVM created by `qvm-create --class DisposableVM --template VM2 ...`, it can have the specific NetVM setting of None, different from their template. -- 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/LO-HhSr--3-1%40tutanota.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Installation of windows 7 on qubes 4.0 fails
Hi, On 10/4/18 8:47 PM, Cranix wrote: Hello, I'm running qubes os 4.0. I tried to set up windows 7 HVM. I tried both ultimate and home (most basic one) editions with this same effect. I managed to get installator running after upgrading dom0, disabling memory balancing and setting amout of ram to 2048M. After installation HVM starts to shut down, its screen disappears but on qubes manager i still see yellow dot in the state field for this vm. After an hour i pressed stop button for this vm and killed it due to 20s timeout. Did you follow the official doc [1] ? If yes, at which step does the VM fails to shutdown ? [1] https://www.qubes-os.org/doc/windows-vm/#qubes-40---windows-vm-installation -- 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/a0797c89-0f57-0ef9-5dce-b4292b1dd221%40maa.bz. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Enabling and disabling external monitors based on laptop lid status
On 10/04/2018 04:59 AM, Ivan Mitev wrote:
On 10/4/18 11:10 AM, 'Mads R. Havmand' via qubes-users wrote:
I'm scratching my head over this... How are people configuring their QubeOS 4
instances to enable and disable external monitors based on the laptops lid
status?
I've been through this too - see below.
Current laptop (EliteBook 1040 g2) works flawlessly with Qubes (even
suspend...) and my only current issue is that I have to manually enable and
disable screens when I dock the machine.
I too manually enable/disable screens but I have configured a keyboard
shortcut that runs a custom shell script with xrandr commands based on
the presence - or lack thereof - of my external monitor.
All it takes is to dock the laptop and hit the shortcut - lightning fast.
Normally, I'd use ACPI hooks and I'm guessing this needs to be done in dom0 (I
don't suppose any DomU's have access to reconfigure screens?) but acpid isn't
available om dom0.
Yes this needs to be done in dom0.
On moderm distros systemd handles lid events provided no other
application has inhibited ("overridden") the event. See `man logind.conf`.
In the case of Qubes, Xfce's power manager overrides HandleLidSwitch=
(but not HandleLidSwitchedDocked=). There's an option in xfce power
manager to turn the display off when the lid is closed but it won't be
able to differentiate when the laptop's docked or not so it's useless.
IIRC there are a few ways to run a script based on lid events without
resorting to installing acpid (which is not even guaranteed to work):
eg. listening for dbus lid close/open events, monitoring
/proc/acpi/button/lid/LID/state, ... ; An alternative is to run stuff on
dock/undock events, via dbus and/or udev rules.
In the end my hacky keyboard shortcut "solution" worked well enough that
I didn't spend time to investigate the solutions above...
What would you recommend? I guess a possible solution could be to source an
acpid RPM, or find the source code, and install that manually in dom0?
This is one of several problems I resolved by simply switching back to
KDE. Xfce had too many bugs and omissions for me.
https://www.qubes-os.org/doc/kde/
--
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/03ce78ce-ce8d-3ab6-7931-a122bdb78b5a%40posteo.net.
For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] I still want anti virus with Qubes OS. but which one is compatible?
> > An implementation of a similar idea across several VMs is: > > > > VM1: any TemplateVM with clamav installed. > > > > > > VM2: AppVM based on above, which is network-connected so it can download new > virus definitions. /var/lib/clamav contains the virus definitions so make it > a bind-dir. > > > > > > VM3: DisposableVM based on the above, which is offline, that does the actual > scanning. To scan a VM, use qvm-block to attach a VM's private volume to the > disposable VM.[1] > > > > The actual updating and scanning can be streamlined using shell scripts run > from dom0. > > > I think the nice properties of this setup are: > * distro-packaged, open source antivirus> * antivirus lives outside the VM > you are scanning > * since the antivirus processes a lot of untrusted input, scans are done from > a disposable VM3, so if it is compromised in the course of a scan, only that > session is compromised> * since the antivirus may process a lot of sensitive > information, VM3 is also offline, making it harder for compromised antivirus > to exfiltrate anything. > [1]To make a DisposableVM have different NetVM than its template, you can use > for VM3 the static DisposableVM created by `qvm-create --class DisposableVM > --template VM2 ...`, it can have the specific NetVM setting of None, > different from their template. > Other nice properties: * by mounting a snapshot of the private volume, you have the option to scan while the target VM is running * by mounting a snapshot, you can ensure no modification of the target volume, which some people might like from a forensics point of view. > > > -- 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/LO-L6ng--3-1%40tutanota.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Installation, no AMD-vi, interrupt mapping, etc.
Most consumer mobos have broken IOMMU, I suggest instead of wasting your time trying to make it work you simply buy a KCMA-D8 or KGPE-D16 plus used cpu and install coreboot-libre. Without HVM/IOMMU your security will suck. -- 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/048b7372-e140-1150-9d08-a07a0e414b89%40gmx.com. For more options, visit https://groups.google.com/d/optout. 0xDF372A17.asc Description: application/pgp-keys
Re: [qubes-users] Installation of windows 7 on qubes 4.0 fails
On Thu, Oct 04, 2018 at 09:18:22PM +0300, Ivan Mitev wrote: > Did you follow the official doc [1] ? If yes, at which step does the VM > fails to shutdown ? Thanks for quick reply. I did not created custom config becouse there is no config file in /var/lib/qubes/appvms/* There are directories for appvms but none of them contains any config file. I just created HVM without memory balancing. Most of detailed instructions are for qubes 3.2 if i correctly see. After windows installer finished it's job and started powering down VM, VM's window disappeared but there was yellow dot in qubes manager for hour (literally i watied hour to see if it will finish by itsefl), then i forced vm shutdown. After reboot i got message that installation failed. -- 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/20181004184639.GA832%40hackerspace.pl. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Lenovo P52
I just tried installing Qubes 4.0 on a Lenovo P52 (out of the box, no firmware updates) and it didn't even boot the distribution media off USB (after trying several USB ports; there are at least three separate controllers in this thing). I'm getting exactly 4 lines of mesages during boot and as it is a 4k display I would have had to take a photo of it to enlarge whatever was written there (so I can't really tell you what I saw). My first suspicion is the RAM; I ordered it with 128GB to keep it from even thinking about swapping. Is there a limit on in the current distribution? The firmware has old bugs I encountered on P70 already; I turned off secure boot and reordered the EFI boot entries resulting in a machine that is not even displaying the Lenovo banner after turning it on so I have enough time to think about the errors of my ways (kids, don't try this at home -- there aren't any replacement mainboards in Europe and a "repair" will take 6 weeks so you have to force IBM UK into calling it a late DOA if it happens). Does anyone have an idea how to convince it to boot? Achim -- 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/9485b3e9bac5d921fcffbae2a1690d6f3048510b.camel%40noses.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Installation of windows 7 on qubes 4.0 fails
On 10/4/18 9:46 PM, Cranix wrote: On Thu, Oct 04, 2018 at 09:18:22PM +0300, Ivan Mitev wrote: Did you follow the official doc [1] ? If yes, at which step does the VM fails to shutdown ? Thanks for quick reply. I did not created custom config becouse there is no config file in /var/lib/qubes/appvms/* There are directories for appvms but none of them contains any config file. I just created HVM without memory balancing. Most of detailed instructions are for qubes 3.2 if i correctly see. The page I linked to has separate sections for R3.2 and R4.0. The instructions for R4.0 are in the "Qubes 4.0 - Windows VM installation" section. After windows installer finished it's job and started powering down VM, VM's window disappeared but there was yellow dot in qubes manager for hour (literally i watied hour to see if it will finish by itsefl), then i forced vm shutdown. After reboot i got message that installation failed. That kind of error is unfortunately common with windows so it's difficult to pinpoint what could be causing it. I'd suggest that you try another install, this time following the instructions in the doc ; many users had windows installed successfully that way, hopefully it'll work for you too. If it doesn't, please send more details with the step you're stuck at and the last 10 lines or so of the debug/log files specified in the doc. Hope this helps ! -- 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/9ec1796a-ccc4-0d2b-891e-f2fff10180be%40maa.bz. For more options, visit https://groups.google.com/d/optout.
[qubes-users] HCL - Sony VAIO Fit 14 (SVF14A15CXB)
TOUCH SCREEN - Touch screen does not work if the USB controller containing the Atmo Digitizer is assigned to VMs. I tried editing Qubes.InputTablet, Qubes.InputMouse, Qubes.InputKeyboard to no effect. Touch screen works fine with that USB controller in dom0. WIFI - Wifi does not work except with a USB wifi adapter. (wifi also did not work with other Linux distros on this computer) SOUND - Sound card does not show up in Pulseaudio Volume Manager, does not work in dom0 except some random loud "system beep" sounds. It works fine in HVM VMs if I assign the sound card to them. SUSPEND - When waking up from suspend, sometimes the keyboard is frozen. (also had this problem with Fedora 28 on this computer and solved it by editing some GRUB file) Battery life is rather short. Everything else seems to be working 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/gJ2nK556DRGpJLxYJLmP9bkFsR564qPZxswSgcld9McsOmejvWAuriEU0lBTods2ugFJIVShj8oncZ66klkTJS-ZAvKZm-oaMEVmBGwBfWc%3D%40protonmail.com. For more options, visit https://groups.google.com/d/optout. Qubes-HCL-Sony_Corporation-SVF14A15CXB-20181004-220503.yml Description: application/yaml
Re: [qubes-users] session managers for VMs?
On 2018-09-22 07:13, Daniel Allcock wrote: > Sometimes I need to shut down a qube I'm working in for some reason > (changing out sys-net for a specialized sys-net, or closing sensitive > material before working in a public place). It would be nice to be > able to come back to the same window setup I left, when restarting the > qube. > > dom0 has this kind of session management via xfce. Is it possible to > run a session manager in another qube? How would I do this? I know > how to start a window manager using exec, but I haven't figured out > the X startup files in the VMs yet. Perhaps each vm already has a > window manager running? But if so then I still need to enable that > wm's session manager. > > Even better would be to "hibernate" a qube by suspending it to disk, > but I know the qubes team has other priorities. I'm hoping per-vm > session management is something I could do right now. > > Thank you very much, > Daniel > > X11 session management is dead (as much as it pains me to say that), and so is multiple sessions by a single user (thank systemd session management and dconf for that). Best bet would be to implement actual hibernate/thaw for VMs. That's a tall order though. -- Rudd-O http://rudd-o.com/ -- 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/58c468c1-f59b-3064-f3ac-9d7f44284f73%40rudd-o.com. For more options, visit https://groups.google.com/d/optout.
