Re: [qubes-users] Failure to delete fedora-28 (mgmt vm problem)

On Thu, 28 Feb 2019 at 11:24, 'awokd' via qubes-users < qubes-users@googlegroups.com> wrote: > You can't remove default-mgmt-dvm. Qubes uses it internally. You can > change it to a different template, say fedora-29. Then you should be > able to remove fedora-28. If not, try removing it with "dnf

[qubes-users] Failure to delete fedora-28 (mgmt vm problem)

After having migrated all my VM's to fedora-29, I wanted to delete the old fedora-28 template, but it fails: $ qvm-remove fedora-28 This will completely remove the selected VM(s)... fedora-28 Are you sure? [y/N] y VM fedora-28 cannot be removed. It is in use as: -

[qubes-users] Re: [qubes-devel] Template disappeared: qubes-template-fedora-29-minimial

On Friday, 1 February 2019 18:21:46 UTC+8, Marek Marczykowski-Górecki wrote: > Probably something gone wrong with removing the template. Templates > which are still installed are excluded from being installed again. > Verify this with: > > rpm -q qubes-template-fedora-29-minimial > > If

[qubes-users] Re: Unable to assign USB microphone to a VM

On Tuesday, 21 August 2018 14:02:57 UTC+8, Elias Mårtenson wrote: > I then start a VM, and run the following from dom0: > > qvm-device mic attach dom0:mic > > I start pavucontrol and audacity in the VM. As soon as I click on “monitor” > in audacity I can see it s

[qubes-users] Unable to assign USB microphone to a VM

I have been unable to get my microphone working, and I'm coming here in the hope that someone might be able to provide some advice. Here's all the relevant details I can think of at the moment: This is on a workstation that is not currently using sys-usb, since I don't have neither a PS2

Re: [qubes-users] Settings environment variable system-wide in a VM

On Tuesday, 20 March 2018 22:59:17 UTC+8, Unman wrote: > I'm not familiar with Fedora, but setting a variable in .profile DOES > seem to expose it to nautilus, at least in a qube using a > Fedora-26-minimal template. > So can we take a step back and can you explain what variable you want > set

Re: [qubes-users] Settings environment variable system-wide in a VM

On Tuesday, 20 March 2018 21:34:38 UTC+8, Unman wrote: > You dont seem to have followed my recommendations :-( Actually, I did. :-) Note that your recommendation works perfectly on Debian-9. I'm using Fedora-26, and things are not as neat there. > On a Debian system, sourcing user defined

Re: [qubes-users] Settings environment variable system-wide in a VM

On Monday, 19 March 2018 20:06:41 UTC+8, Unman wrote: > generally the Xsession wont touch .profile - there are exceptions. > It's picking up stuff from /etc/X11/Xsession.d > You can also use ~/.xsessionrc which is sourced from a file in > /etc/X11/Xsession.d > You probably dont want to source

[qubes-users] Settings environment variable system-wide in a VM

How do I set an environment variable that will be accessible to all programs started in a session? Specifically, I'm trying to set KRB5CCNAME in $HOME/.profile, and it becomes available from a terminal session as expected, but it never gets set in Nautilus, where it is needed. Looking at

[qubes-users] Using Salt to provision an appvm

I'm trying to use Salt to set up my standard configuration, which includes a few appvms used for various purposes. I have been able to create scripts that sets up the dom0 configuration, creates the VMs, and configures the templates. But when I try to use the same mechanism to configure the

[qubes-users] Re: GPU?

On Tuesday, 16 January 2018 04:02:13 UTC+8, Vít Šesták wrote: > It might be possible, just no one has implemented it in a way that does not > require complex processing by trusted parts of system. > > There is an attempt called XenGT (for Intel iGPUs), but I am not sure about > its state and

Re: [qubes-users] What happened to domain manager in 4?

On 8 December 2017 at 00:16, Unman wrote: > Backup/restore is already on the target list. > What doesnt seem to be at the moment is the ability to show all qubes, > and how they are connected, and what their status is. That's a nice > target. > If by "status" you

Re: [qubes-users] What happened to domain manager in 4?

On 7 December 2017 at 12:57, Chris Laprise wrote: > I myself find it strange and frustrating using Qubes VMs without the > visual reminders for the templates they're based on, updates, last backup > date, etc. If I need to see the template for a VM, going into VM settings >

Re: [qubes-users] What happened to domain manager in 4?

On Thursday, 7 December 2017 11:56:13 UTC+8, mikih...@gmail.com wrote: > I stopped using qubes because my use case depends on it. I'm not going to judge the way you use the software, but I am curious as to what kind of use case you have that made the VM manages so important that you literally

Re: [qubes-users] What happened to domain manager in 4?

On Thursday, 7 December 2017 00:14:04 UTC+8, Tom Zander wrote: > On Wednesday, 6 December 2017 16:08:28 CET Unman wrote: > > "useful, but wasnt any good" - do you mean buggy or poorly designed? > > What 2 features should be implemented/fixed? > > > > I confess I rarely use the Manager, so

Re: [qubes-users] What happened to domain manager in 4?

On Wednesday, 6 December 2017 21:58:56 UTC+8, Unman wrote: > On Mon, Dec 04, 2017 at 03:34:25PM -0800, r...@tuta.io wrote: > > Just read it. Thats fucking stupid. > > > > -- > > I think it's safe to say that opinion is divided on the removal. I liked the old tool. However, I am also on the

[qubes-users] Re: Creating a HVM in Qubes 4.0rc2 for Windows 7 Qube

On Wednesday, 15 November 2017 09:24:25 UTC+8, car...@gmail.com wrote: > > After tinkering with the memory and hard drive allocation I got it to work. > The windows tools aren't in the repository. Are they available for q4? Is > there > a place where I can manually download the

[qubes-users] Can Qubes 4 do SVM VM snapshots like in 3.2?

In 3.2, the DVM stored a snapshot of the booted system so that new dispvm's could be booted very quickly. This doesn't seem to happen in 4.0, which cuases them to take over 30 seconds to start. I recall reading somewhere that 4.0 would support creating snapshots for all VM's, not just DVM's.

Re: [qubes-users] Re: Why is there no qubes manager in V4.0?

On Wednesday, 1 November 2017 12:23:22 UTC+8, Desobediente wrote: > Just felt like I have to say that I would love to stop everything I'm doing > in > my life to write a proper Qubes Manager for 4. > > But I don't see that happening. It sounds trivial at first, but it requires a > lot of

[qubes-users] Re: Why is there no qubes manager in V4.0?

On Wednesday, 1 November 2017 11:32:58 UTC+8, Fun Zork wrote: > And not just that. If I'm being honest, it is also because it makes me feel > more like I am running a cool, unique, complicated OS. The qubes manager is > kind of Qubes' signature look. It's > > I agree that the UI for it is

Re: [qubes-users] Re: Windows 7 VM on Qubes $

On 3 October 2017 at 18:48, Foppe de Haan <0spinbo...@gmail.com> wrote: > On Tuesday, October 3, 2017 at 11:01:47 AM UTC+2, lok...@gmail.com wrote: > > On Tuesday, 3 October 2017 16:56:24 UTC+8, Foppe de Haan wrote: > > > > > Did the backup restoration process work at all, or did it error and >

Re: [qubes-users] How can I test that my AEM configuration is correct?

On 20 July 2017 at 17:49, Patrik Hagara wrote: > Oh yes, now I remember! This was definitely a Linux kernel issue for > me, it just didn't setup VGA console logging yet so it seems like a > tboot hang. See the mail I just sent about updating dom0 kernel. I now have

Re: [qubes-users] How can I test that my AEM configuration is correct?

On 20 July 2017 at 17:31, Patrik Hagara wrote: Now that I tried removing min_ram from my setup it still works, so > perhaps the fix for this was something different... Can't recall what > though. :-\ > > Ah well, guess we'll have to go back to taking pictures of the screen.

Re: [qubes-users] How can I test that my AEM configuration is correct?

On 20 July 2017 at 16:51, Patrik Hagara wrote: > > Thank you! You were right of course. There was a disabled option > > referring to "trusted execution" that was turned off. Enabling that > > gave me much more than 3 pages of debug output. > > > > Unfortunately, the

Re: [qubes-users] How can I test that my AEM configuration is correct?

On 20 July 2017 at 15:58, Patrik Hagara wrote: > This looks to me like tboot either wasn't loaded at all or memory > logging is disabled. > > Check the tboot cmdline used -- search for the following in > /boot/grub2/grub.cfg: > > multiboot /tboot.gz placeholder

Re: [qubes-users] Re: Building Qubes from source, strange error.

On 27 March 2017 at 18:19, Andrew David Wong wrote: They won't be identical until we achieve reproducible builds: > > https://github.com/QubesOS/qubes-issues/issues/816 The builds are significantly different. The main difference that I noted was that while the image I can

Re: [qubes-users] Building Qubes from source, strange error.

On 23 Mar 2017 00:19, "Unman" wrote: Strange because the builder.conf there has linux-utils as entry before artwork. Did you succesfully build linux-utils? I'm not sure. I made the mistake of not capturing output to a file. Is there an easy way to check? Regards,

Re: [qubes-users] Building Qubes from source, strange error.

On 23 Mar 2017 00:00, "Unman" wrote: How did you get your builder.conf file? The build order is important and it looks as if you are trying to build artwork before you have built qubes-utils. You can either comment out artwork for the moment, build the rest and then

Re: [qubes-users] Fwd: HCL - Dell Latitude E7470

On 17 February 2017 at 13:19, taii...@gmx.com wrote: I would also insist on linux touchpad drivers, which again you can do > (because it is a business laptop) > I think it's possible to get it to work in Fedora 24, but Qubes dom0 is based on Fedora 23. I'll try it again once

[qubes-users] Fwd: HCL - Dell Latitude E7470

(resend, with attachments this time) I've been using Qubes 3.2 on this laptop for a month or two now, and pretty much everything works well. Note that immediately after installing the system the WLAN didn't work. I connected using ethernet and did a software update. After this the WLAN worked

[qubes-users] HCL - Dell Latitude E7470

I've been using Qubes 3.2 on this laptop for a month or two now, and pretty much everything works well. Note that immediately after installing the system the WLAN didn't work. I connected using ethernet and did a software update. After this the WLAN worked correctly. The laptop seems to have