[qubes-users] Recover broken bootloader

[lokedhs]

My laptop has started to fail to boot my 4.0rc2 installation. This started 
after doing a qubes-dom0-update, but I'm pretty sure that I had rebooted the 
machine successfully at least once since then.

The computer has now gone into a bootloop, and fails to display the GRUB 
screen. I can only assume that the bootloader is crashing. However, nothing is 
displayed on the screen.

Is there a recommended procedure to reinstall GRUB when booting from the 
installation media?

Regards,
Elias

-- 
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/1c7696e0-7a58-4913-b9df-266593aac15b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Qubes-4.0rc2 restore backup error

[lokedhs]

Before installing 4.0rc2, I did a backup of my VM's from 3.2. I've started 
restoring them one-by-one and for the most part is has been a reasonably 
painless operation.

However, when I tried to restore the "ssh" VM, I got the following error:

qubesadmin.backup: -> Restoring ssh...
qubesadmin.backup: Extracting data: 105.4 MiB to restore
qubesadmin.backup: Error extracting data: retrieved backup size exceed 
expected size, if you believe this is ok, use --ignore-size-limit option
qubesadmin.backup: Continuing anyway to restore at least some VMs
qubesadmin.backup: -> Done. Please install updates for all the restored 
templates

After this, I have an "ssh" VM, but it's empty. Or rather, it contains the 
default content as if I had manually created a new VM based on some template.

I then deleted the "ssh" VM and restored using the --ignore-size-limit flag. 
The output was different, but the end result was the same:

qubesadmin.backup: -> Restoring ssh...
qubesadmin.backup: Extracting data: 0 to restore
qubesadmin.backup: -> Done. Please install updates for all the restored 
templates

Again, the "ssh" VM was created, but it just contained the default content just 
as in the first case.

-- 
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/3b1f15bd-a1a0-4ba1-aa4e-f57ae722108d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Qubes-4rc2 timezone (or clocksync service) problems

[lokedhs]

I just installed rc2 and trying to configure the machine similar to the way 
things worked in my old (3.2) installation. One of the issues I have faced is 
that the timesync service doesn't seem to do the right thing.

I am in Singapore timezone (UTC+8). Typing "date" in dom0 shows that the 
correct timezone is configured, but the time is 8 hours in the future:

[dom0]$ date
Thu Oct 26 20:09:23 +08 2017

The actual time when I typed the command was 12:09.

Running "date" in sys-net (which is the VM that runs the clocksync service) 
gives me the same output as in dom0.

Is this a problem with clocksync? Where should I start looking in order to 
figure out the cause of this problem?

-- 
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/a8039e35-fd9e-4383-9b9e-bee88f1177fa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[lokedhs]

On Tuesday, 3 October 2017 19:26:29 UTC+8, Foppe de Haan  wrote:

> > When trying to start the VM using qvm-start, a window is opened with some 
> > diagnostic information scrolling past (too fast to see what's going on), 
> > and then the window disappears and the VM is shut down. Trying to go to 
> > settings shows a python error.
> 
> The python error is about mem-writer, presumably?

Actually no. The error reads:

Whoops. A critical error has occured. This is most likely
a bug in Qubes Manager.

TypeError: setChecked(self, bool): argument 1 has unexpected type 'str'
at line 9
of file /usr/bin/qubes-vm-settings

-- 
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/75af8904-3934-434f-b9bb-ff494c6d2245%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[lokedhs]

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 skip the 
> win7 VM?

Thanks for the reply.

Please allow me to do it all from the beginning again and record all the logs. 
I'll update in a day or so.

-- 
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/0d206c1f-adb2-4962-9d7c-fbf189abdb4e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Windows 7 VM on Qubes $

[lokedhs]

After installing Qubes 4rc1 on a new laptop, I took a backup of my Windows 7 VM 
from my old 3.2 installation and loaded it onto the new laptop. This did not 
work at all.

After some searching I came across a statement suggesting that Windows not work 
is a known issue and will be fixed with the final release of Qubes 4.

My question is: Will the Windows 7 support work once rc2 comes out? I don't use 
the Windows support much, but when I do, it's really important. At the same 
time I can't stay with Qubes 3.2 since my new laptop is using Kaby Lake, and 
thus requires Qubes 4.

What is the current status with regards to Windows 7 and Qubes 4?

-- 
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/c7baa3c2-d0df-41cc-a38d-87fe0aaa4b63%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] New potential way of disabling ME

[lokedhs]

Apparently ME has a HAP mode that can be enabled, which disables most of the ME 
functionality.

http://blog.ptsecurity.com/2017/08/disabling-intel-me.html

-- 
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/0c7b7077-e213-4c18-8784-3f335d54e73b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Windows 7 problems (R3.2)

[lokedhs]

On Saturday, 12 August 2017 03:33:38 UTC+8, PR  wrote:

> In total I ended up installing windows roughly 20 times, tweaking lots 
> of settings - but if know how it can be done, you get rewarded with a 
> working windows installation which is running fine in seamless mode.
> 
> I can walk you through the process, you can send me a private email so 
> that we can do instead of bothering people on the list ;-)

I did the same thing, having to reinstall Windows countless times. 
Unfortunately, it has now been a hile and I probably forgot a lot of the 
details, so if I had to do it again, it's likely I have to go through that 
dance all over again.

Thus, if you help OP out, perhaps one of you could take a notes while doing so, 
so that others can benefit from a proper guide?

Regards,
Elias

-- 
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/443e896e-b08e-4ad6-b674-4eed67f95c3d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes OS 4.0 first release candidate (rc1) has been released!

[lokedhs]

On Tuesday, 1 August 2017 13:19:21 UTC+8, Holger Levsen  wrote:

> so far so very good. i'm curious whether this will also be the case with qubes
> 3.2.1 and a 4.9 kernel (so far only tried with the older 4.8 one from the
> qubes repos…)
> 
> (but then, see the other mail on this list about my problems installing the
> 4.9 kernel on qubes 3.2…)

I'm having hangs on resume with kernel 4.9 on a Latitude E7470. That suggests 
to me that you'll probably have the same problem.

-- 
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/cd37e040-467e-407c-8977-e5988ba3208e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Request for feedback: 4.9 Kernel

[lokedhs]

On Monday, 31 July 2017 11:11:58 UTC+8, lok...@gmail.com  wrote:

> > 2) Hardware that didn't work with 4.4 or 4.8 still doesn't work.
> 
> I can now disable tap-to-click. Finally!

Note that I quoted the wrong question here. It didn't work in the old version, 
but works with 4.9.

-- 
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/80d048d6-8b5e-4d1a-adaa-143348426582%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Request for feedback: 4.9 Kernel

[lokedhs]

The machine I'm testing on is a Dell Latitude E7470.

> 1) Hardware that used to work with 4.4 or 4.8 no longer works with 4.9.

The computer now greets me with a black screen (hung? I don't know) when coming 
out of sleep. Thankfully I don't usually put the machine to sleep, so I can 
live with it.

> 2) Hardware that didn't work with 4.4 or 4.8 still doesn't work.

I can now disable tap-to-click. Finally!

> 4) General feedback on the 4.9 kernel.

Other than the two things above, nothing has changed as far as I can tell.

-- 
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/0eb29d23-e64b-4165-ba56-f1153b729f1a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[lokedhs]

On Thursday, 20 July 2017 20:29:11 UTC+8, Patrik Hagara  wrote:

> On 07/20/2017 02:08 PM, Patrik Hagara wrote:
> > As for the Linux kernel, you want to use the earlyprintk param,
> > either "earlyprintk=vga,keep" or "earlyprintk=xen,keep" should
> > work. Again, the full (and fairly long) list of supported
> > parameters is available at this link [2].
> > 
> > The Linux early printk logging should yield some useful info, I 
> > hope.
> 
> Also, removing the "quiet" option might be necessary. Try adding
> "nowatchdog panic=0" if the system reboots too quickly after logging
> the errors.

Unfortunately, after doing all of this (and trying a few different variations), 
I still have the behaviour that the machine reboots immediately after SENTER.

>From this I draw the conclusion that the kernel isn't even started.

What happens (or is supposed to happen) between SENTER and the kernel being 
loaded?

Regards,
Elias

-- 
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/4f3cf7d8-1115-497d-9741-05449a0e421d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[lokedhs]

On Thursday, 20 July 2017 16:22:22 UTC+8, Patrik Hagara  wrote:

> That's a non-fatal error, I have that in my log too.
> 
> What's more interesting is the last photo, in particular the line:
> 
>   ERR: SENTER disabled by feature control MSR (5)
> 
> I _think_ this means that your motherboard/BIOS does not support Intel
> TXT as it seems to be deliberately disabled in the CPU's
> Model-Specific Register (MSR).
> 
> Maybe try searching for the TXT-enabling option in BIOS again (it may
> be hidden until you turn on something else, eg. Intel VT-d/IOMMU like
> on my Lenovo laptop). Check whether there's a BIOS update available, too

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 machine reboots shortly after the "SENTER", causing the 
machine go into an infinite bootloop.

Note that it never even gets to the point where it asks for the TPM password.

Would screenshots of all the pages of debug be useful?

Thanks and regards,
Elias

-- 
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/2c3ad010-b75a-41e0-8fe1-950d7fd1b540%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[lokedhs]

On Thursday, 20 July 2017 15:18:26 UTC+8, Patrik Hagara  wrote:

> Try checking the tboot log (from dom0) for any obvious error messages:
>   sudo txt-stat

Thanks. I did this, but I'm not sure how to interpret the information. It does 
say "TXT measures launch: FALSE". Does that mean that TXT is not available?

Here's the output of the command:

Intel(r) TXT Configuration Registers:
STS: 0x0082
senter_done: FALSE
sexit_done: TRUE
mem_config_lock: FALSE
private_open: TRUE
locality_1_open: FALSE
locality_2_open: FALSE
ESTS: 0x00
txt_reset: FALSE
E2STS: 0x0004
secrets: FALSE
ERRORCODE: 0x
DIDVID: 0x0001b0068086
vendor_id: 0x8086
device_id: 0xb006
revision_id: 0x1
FSBIF: 0x
QPIIF: 0x9d003000
SINIT.BASE: 0x
SINIT.SIZE: 0B (0x0)
HEAP.BASE: 0x
HEAP.SIZE: 0B (0x0)
DPR: 0x
lock: FALSE
top: 0x
size: 0MB (0B)
PUBLIC.KEY:
2d 67 dd d7 5e f9 33 92 66 a5 6f 27 18 95 55 ae 
77 a2 b0 de 77 42 22 e5 de 24 8d be b8 e3 3d d7 

***
 TXT measured launch: FALSE
 secrets flag set: FALSE
***
unable to find TBOOT log   

-- 
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/f61e87e3-3f7c-48d5-921a-6d36cc56e49d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[lokedhs]

On Friday, 14 July 2017 16:16:21 UTC+8, Patrik Hagara  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> On 07/14/2017 09:45 AM, loke...@gmail.com wrote:
> > On Friday, 30 June 2017 04:17:08 UTC+8, Marek Marczykowski-Górecki 
> > wrote:
> > 
> >> Oh, it isn't listed in updates-status[1], so I completely forgot.
> >> Probably it was uploaded to testing before introducing that
> >> system. Of course it should be migrated to current, will do.
> > 
> > I updated to the latest AEM, but after I did that, nothing worked 
> > anymore. I outlined it in this post, but no one replied to it. Is 
> > there anything I can do to collect more information?
> > 
> > https://groups.google.com/forum/#!topic/qubes-users/JMipWyv2heU
> > 
> > Regards, Elias
> > 
> 
> This error means that your AEM setup never worked, even before
> updating. The AEM boot would always succeed no matter what, even if a
> hundred evil maids tampered with it.
> 
> Did you follow the AEM installation instruction to the letter? Do you
> have Intel TXT enabled in BIOS? Did you download the right SINIT
> module and add it to the GRUB config as a module loaded last? Does
> GRUB load the SINIT module successfully?
> 
> If it still doesn't work, try fully resetting the TPM (usually only
> possible from the BIOS) and setting it up again.

Thank you. This explains some of the things I have seen.

Unfortunately I have reset the TPM (multiple times, throughout my testing) and 
I keep getting the same error.

I have also double-checked the SINIT module, and it's the correct one.

As for Intel TXT, I can't find any option in the BIOS settings to control this 
specifically.

Regards,
Elias

-- 
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/bb88e664-f384-4dff-aff9-324d44ef943d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[lokedhs]

On Friday, 30 June 2017 04:17:08 UTC+8, Marek Marczykowski-Górecki  wrote:

> Oh, it isn't listed in updates-status[1], so I completely forgot.
> Probably it was uploaded to testing before introducing that system. Of
> course it should be migrated to current, will do.

I updated to the latest AEM, but after I did that, nothing worked anymore. I 
outlined it in this post, but no one replied to it. Is there anything I can do 
to collect more information?

https://groups.google.com/forum/#!topic/qubes-users/JMipWyv2heU

Regards,
Elias

-- 
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/3ca8e6a9-35d7-48f2-a271-8887f8d97070%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] AEM failure after upgrade

[lokedhs]

The AEM package was upgraded recently (probably because of this thread: 
https://groups.google.com/forum/#!topic/qubes-users/3ZkmS5v7E38), and after I 
installed the updated version, AEM stopped working completely.

Now, it asks me for the AEM password. I type it in, and it doesn't display my 
secret message. Instead, it immediately asks me for the disk password, and 
while it boots the system, I see a message telling me: "PCR sanity check 
failed".

I have tried to completely clear and reinstall AEM several times, but the same 
issue persists.

This is the content of the journalctl log:

Jul 07 16:25:36 dom0 systemd[1]: Starting Anti Evil Maid sealing...
Jul 07 16:25:39 dom0 anti-evil-maid-seal[1982]: tpm_z_srk: detecting whether 
SRK is password protected
Jul 07 16:25:39 dom0 anti-evil-maid-seal[1982]: Tspi_Key_CreateKey failed: 
0x0001 - layer=tpm, code=0001 (1), Authentication failed
Jul 07 16:25:39 dom0 anti-evil-maid-seal[1982]: tpm_z_srk: yes, SRK is password 
protected; resetting dictionary attack lock...
Jul 07 16:25:39 dom0 anti-evil-maid-seal[1982]: PCR-17: FF FF FF FF FF FF FF FF 
FF FF FF FF FF FF FF FF FF FF FF FF
Jul 07 16:25:39 dom0 anti-evil-maid-seal[1982]: PCR-18: FF FF FF FF FF FF FF FF 
FF FF FF FF FF FF FF FF FF FF FF FF
Jul 07 16:25:39 dom0 anti-evil-maid-seal[1982]: PCR-19: FF FF FF FF FF FF FF FF 
FF FF FF FF FF FF FF FF FF FF FF FF
Jul 07 16:25:39 dom0 systemd[1]: anti-evil-maid-seal.service: Main process 
exited, code=exited, status=1/FAILURE

Any idea what the cause of this issue could be?

Regards,
Elias

-- 
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/36028d9f-fb42-4761-b605-ef69d219fb18%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Adding appmenu entries to AppVM's

[lokedhs]

On Thursday, 6 July 2017 06:21:01 UTC+8, Unman  wrote:
> On Wed, Jul 05, 2017 at 09:20:48PM +, js...@riseup.net wrote:
> > loke...@gmail.com:
> > > I have some applications I have installed manually in /usr/local on 
> > > appvms. I would like to create appmenu entries for these applications. 
> > > However, the Qubes appmenu management only deals with menus coming from 
> > > templates.
> > > 
> > > Is there an official way to handle this?
> > 
> > I don't think there's an "official" way to do it, but it is possible.
> > 
> > I made a few custom appmenu entries by creating a new .desktop file in
> > /usr/share/applications/ in the *template* on which the appvm is based.
> > You'll never launch it in the template, but you have to create the
> > .desktop file there so Qubes will recognize it.
> > 
> > Then create a new .desktop file in
> > /var/lib/qubes/vm-templates//apps.templates/ in dom0 pointing
> > to the .desktop file you created in the template.
> > 
> > If that's not enough it might also be necessary to create another
> > .desktop file in /var/lib/qubes/appvms//apps/ in dom0 for it as well.
> > 
> > This will result in it being possible to add your new entry for any
> > appvm based on that template, not just the one you installed the
> > application on, but it should get the job done.
> 
> There's another way which is somewhat simpler, and which fits your
> scenario somewhat better.
> BUT , if you create a custom entry in an AppVM menu it will get
> overwritten when qvm-sync-menus is called (e.g template update, add new
> shortcuts etc.) You can work round this by making a custom menu
> containing custom menu entries - I do this on setup, because in my
> experience naive users dont need to know about the underlying VM
> structures to work efficiently in Qubes.
> 
> Remember that you can use qvm-run in dom0 to launch applications in
> appVMs. So you can create a simple .desktop file which will run the
> command in the required qube. If you look at the desktop files in
> /var/lib/qubes/appvms/XXX/apps/ you can see the structure.
> Those files tend to use qubes-desktop-run but you can call the
> application directly in many cases. (HINT - open a terminal in the qube
> and find out what command you need to run to start the application. Then
> try that command in dom0 using qvm-run. THEN create a desktop file
> using that command.)
> 
> Then just write a custom menu entry calling that desktop file.
> 
>   My menu
> 
>   custom.desktop
> 
> 

Thank you.

Yours, and the template-based method mentioned in the previous reply both work, 
but neither of them are ideal. I haven't decided which method to go for yet.

In my opinion, qvm-sync-menus should take the entries in /usr/local in the 
appvms into consideration as well. I haven't looked at how it's implemented but 
it seems like something that shouldn't be too difficult to implement?

-- 
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/48acae2b-e094-4285-a4d3-f3ed8f0aaae3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Adding appmenu entries to AppVM's

[lokedhs]

I have some applications I have installed manually in /usr/local on appvms. I 
would like to create appmenu entries for these applications. However, the Qubes 
appmenu management only deals with menus coming from templates.

Is there an official way to handle this?

-- 
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/ce5ba6ac-1f0c-42ff-b320-7e903d6270d1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[lokedhs]

Thanks for the reply. 

The funny thing is that I did see my secret message. That's why I thought it 
was so weird. 

That's why I asked for a way to force a failure so that I can double check 
this. 

-- 
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/4240cf2a-0ca7-4064-95ec-4d783ca0ceda%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[lokedhs]

I enabled AEM some time ago, and so far it's worked the way I'd expect it to.

Based on what I have read here, I came to the understanding that after 
upgrading the dom0 kernel I'd get an AEM error when I reboot the machine, since 
the kernel is different from the last boot.

Yesterday, I installed a new dom0 update which included an updated kernel 
package. I was expecting to see an AEM error when I rebooted, but that never 
happened.

This suggests to me that my AEM configuration is incorrect. Is there a way I 
can test whether it works or not? Perhaps my manipulating something in the boot 
process that would trigger an AEM failure?

-- 
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/1a6ad28c-081d-4294-a4f6-49204e7ccae2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Xen high CPU usage, but nothing is running in the VM

[lokedhs]

On Sunday, 18 June 2017 14:54:03 UTC+8, Vít Šesták  wrote:
> BTW, I remember having such issue (including real CPU load), but that time,
> avahi-daemon was to blame, related to VPN. But it was shown in htop. Disabling
> avahi-daemon has helped.
> 
> On recreating VMs (or VM templates): It might help if the load is shown in
> Qubes Manager. If the load is not shown in Qubes Manager, I'd guess it is a
> Xen-related or dom0-related issue.

I have tried to recreate the circumstances under which this happened, but I 
haven't been able to.

The fact that none of the diagnostics tools I ran, both on dom0 and the VM 
other than xentop was showing anything suggests to me that it's definitely 
Xen-related as you said.

If it happens again, is there something I can do to collect more information in 
order to figure out what is happening? Some tools I forgot to run, or some logs 
I never looked at?

-- 
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/6553a6e6-8661-4382-805b-c67472c6e822%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Not enough memory to start VM

[lokedhs]

On Saturday, 17 June 2017 18:38:10 UTC+8, Nikolai Stenfors  wrote:
> Hello Qubes-users, 
> 
> I've made a fresh standard installation of Qubes OS on a Lenovo SL510 with
> 220 GB memory. A reclaimed all disk memory during the installation to whipe
> out my previous Debian installation. 
> However, whatever I do, for instance open firefox on my personal VM, I get
> the message "Not enough memory to start VM. Close on or more running VMs"

Your computer doesn't have 220 GB of memory. You have 220 GB of disk space. 
Assuming your computer is the Lenovo X220, you probably only have 4 GB of 
memory in this machine, as this was the amount the machine was sold with back 
when it came out.

Unfortunately, 4 GB will not get you very far with Qubes. You can do wotk with 
8, but you really need 16.

> Could somebody give my some step-by-step instructions on how to solve my 
> problem?

I've googled a bit, and it seems as though the X220 supports up to 16 GB, so 
the solution for you is to buy a memory upgrade. It should be reasonably cheap.

-- 
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/1d74e8c7-b07d-4594-9f65-18187b350453%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Xen high CPU usage, but nothing is running in the VM

[lokedhs]

On Saturday, 17 June 2017 18:35:39 UTC+8, Vít Šesták  wrote:
> What CPU usage does  Qubes Manager show? I guess is shows low CPU usage.
> 
> Do you see any other symptoms of high CPU usage like heat or fan activity?
> 
> I guess the Xen just allocates some CPU time for some VMs, but the time is not
> used. As a result, xentop seems to overestimate actual CPU usage.

I've restarted the offending VM's now, so I can't test anymore.

The fan was blowing at maximum speed (which is why I looked into this in the 
first place) so there was definitely something happening.

The VM that was running with the most CPU usage according to xentop (150% or 
so) had been used to run an Atari ST emulator (which uses lots of CPU). 
However, the emulator had been killed and the machine left idle while I was off 
doing other things for at least 30 minutes. It was when I came back to the 
computer that I noticed that the fan was blowing and that's when I noticed the 
problem.

-- 
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/a10f889e-9c51-460a-9615-58af1dd0c986%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Xen high CPU usage, but nothing is running in the VM

[lokedhs]

I noticed that my laptop fan was blowing more than usual, so I started ‘xentop’ 
in dom0 to see which VM was using CPU. I noticed two VM's were using 150% and 
abour 70% respectively (according to ‘xentop’ output).

However, when running ‘top’ in the VM's themselves, I saw nothing using any 
CPU. That is what I would expect, as they were not running anything 
CPU-intensive at the time.

Has anyone seen this before, and what can I do to diagnose this problem when/if 
it happens again?

-- 
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/003254bd-a9fb-445c-809f-1c1cac1261f4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Network issues - Could use some help

[lokedhs]

On Tuesday, 13 June 2017 18:06:31 UTC+8, Alchemist  wrote:
> Noor, 
> 
> most Http only sites work more often, but there are instances where they get 
> hit by this "slowdown" and it seems to be affecting the whole appvm not just 
> the browser. 
> 
> The problem seems to be transient, no restarts needed if I just change the 
> AppVM's firewall to something else and back. 
> 
> Though after some further testing I think whatever is going on is affecting 
> the FirewallVM since things connected to sys-net are more (But not 100%) 
> reliable. 
> 
> (So it's possible there may be independent issues in sys-net and sys-firewall 
> that are causing this)
> 
> I currently am not in a position to test wired access unfortunately.

Do you happen to have a firewall outside your computer that blocks ICMP? If so, 
you might actually be seeing a problem where MTU discovery fails. That often 
manifests itself in this way.

If that's the case, then fix your firewall so that it doesn't block ICMP.

-- 
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/3f495857-0ca3-4134-97ec-e37a01eb56f2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Custom shared directory between VM's

[lokedhs]

I regularly compile the latest version of Emacs for use in my development VM. I 
simply compile Emacs from the git repository and install it in /usr/local. All 
works the way it's supposed to.

However, I now have more than one VM where I need to use Emacs, and I would 
like to avoid having to compile it from source in both VM's.

The only way I can think of to handle this situation is to create a separate 
templatevm for this, enabline networking in the template so that I can use git 
from it, and then compile Emacs there.

Is there a better way to handle this? Ideally I'd like to be able to compile 
Emacs and install it to some specific directory that can then be made available 
to both VM's.

What is the best way to handle this situation?

-- 
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/ecced993-8dad-4200-9537-4f213f68b3bd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Laptop with discrete graphics card, any chance it'll work?

[lokedhs]

On Thursday, 18 May 2017 03:17:42 UTC+8, Vít Šesták  wrote:

> With external GPU, be careful about additional outputs (HDMI/DVI/DP/VGA). 
> They 
> might be wired to the dedicated GPU, which can cause various problems with 
> your 
> setup. First, it is generally poorly supported with Linux. (It should be 
> reportedly better soon, but it might require Wayland, which you will likely 
> wait 
> a while for.) Second, if you manage to attach the second GPU to an AppVM, you 
> obviously cannot access it from dom0.

Thanks for the information.

I have no intention of connecting an external monitor, so the HDMI issue is not 
a problem for me. Attaching the GPU to an appvm is exactly what I need to do, 
since the only VM that needs it is the one I run my development environment in.

Does this work with all laptops that has a Radeon GPU? Or is there something 
else I need to check before committing?

Finally, I've been looking for Radeon laptops, and all I've found so far are 
big "mobile workstation" machines, weighing around 4 kg or more. Does anyone 
know of a smaller machine with Radeon graphics?

Thanks,
Elias

-- 
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/3a17f9f8-50a6-4231-b96b-67cb5a421d8f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Laptop with discrete graphics card, any chance it'll work?

[lokedhs]

On Monday, 15 May 2017 03:12:18 UTC+8, tai...@gmx.com  wrote:

> I would get a laptop with AMD graphics instead, or get an older model 
> like the T430 or W530 (and you can install open source init coreboot on 
> that)

Thanks. I'm convinced. I'll go for a laptop with Radeon chipset.

I've been looking around for one, but I can't really find any machines that are 
appealing. The only ones I've been able to find are huge things that seems 
incredibly uncomfortable to use and carry around.

I also haven't been able to find a single laptop with the R9 chipset.

Does anyone have a suggestion on a reasonably light laptop (2 kg or so) with a 
modern CPU and Radeon chipset? Something similar to the XPS 15. Price is not 
really an issue.

Does anything like that even exist?

-- 
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/740fedee-9c37-4c7e-b0ad-f1a885679c72%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Laptop with discrete graphics card, any chance it'll work?

[lokedhs]

On Sunday, 14 May 2017 00:50:01 UTC+8, Grzesiek Chodzicki  wrote:
> W dniu sobota, 13 maja 2017 15:30:07 UTC+2 użytkownik lok...@gmail.com 
> napisał:
> > I am about to buy a new laptop, and jst about the only requirements I have 
> > is that it should be reasonably small, and that I am able to use the GPU in 
> > it. The latter is because I need to do some development which requires it.
> > 
> > I am OK with installing Nvidia's proprietary drivers on dom0. I'm aware of 
> > the potential security issues with that, but I am willing to accept it if 
> > necessary (i.e. if there is no other solution).
> > 
> > Right now I'm considering buying the Dell XPS 15 laptop which has a 
> > discrete Nvidia 1050 card: http://www.dell.com/sg/p/xps-15-9560-laptop/pd
> > 
> > Would this work? If not, is there another alternate for me? I really want 
> > to be using Qubes on this machine, but if there is no way I can get a GPU 
> > to work, I'm going to have to use a dedicated machine for the GPU work, 
> > which means I have to get two laptops, and I'd rather not do that.
> > 
> > Any ideas?
> 
> 10 series Nvidia GPU's aren't supported by the version of nouveau Qubes ships 
> with.

I'm aware of this, which is why I said that I'm ok with installing Nvidias 
drivers. If I understand you correctly, you're suggesting that this is not an 
option? 

Assuming that Noveau will eventually support it, will it be possible to to 
utilise the GPU in a vm at that time?

-- 
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/882cd36d-453f-4a01-9b08-ff595d4ef8fa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Laptop with discrete graphics card, any chance it'll work?

[lokedhs]

I am about to buy a new laptop, and jst about the only requirements I have is 
that it should be reasonably small, and that I am able to use the GPU in it. 
The latter is because I need to do some development which requires it.

I am OK with installing Nvidia's proprietary drivers on dom0. I'm aware of the 
potential security issues with that, but I am willing to accept it if necessary 
(i.e. if there is no other solution).

Right now I'm considering buying the Dell XPS 15 laptop which has a discrete 
Nvidia 1050 card: http://www.dell.com/sg/p/xps-15-9560-laptop/pd

Would this work? If not, is there another alternate for me? I really want to be 
using Qubes on this machine, but if there is no way I can get a GPU to work, 
I'm going to have to use a dedicated machine for the GPU work, which means I 
have to get two laptops, and I'd rather not do that.

Any ideas?

-- 
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/1f4e83e3-1543-4f17-abc8-eaff48e7f660%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] say it out (loud) - Qubes OS Stickers

[lokedhs]

On Saturday, 22 April 2017 07:46:28 UTC+8, Dominique St-Pierre Boucher  wrote:

> I would love a big logo like the one on the Twitter post in 2015. I would 
> also 
> like to have a small on to cover that windows logo on the keyboard... I would 
> also 
> like one with "Qubes inside"...

If you want a sticker, wouldn't it make more sense to have something without 
text. I'd argue that the best symbol for a secure laptop is one without any 
symbols or stickers at all. Just a single colour no-label laptop.

If there was a way to remove the vendor label (Dell, HP, etc...) from a latpop, 
I'd do it. :-)

-- 
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/2cd99f47-8cb4-4b18-8999-bcb47222c1bd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] My Windows VM always stops after a while

[lokedhs]

I have a Windows VM where I run Outlook for work purposes. It works great and I 
keep it in a separate xfce workspace. I'm running it in desktop mode (i.e. the 
Windows desktop is in a single Xfce window).

After a certain amount of time (hard to say how long, but I'd guess it's in the 
30 minute to 1 hour range) the Windows desktop disappears, and in the Qubes 
manager the Windows VM is marked as yellow. It will stay yellow until I 
hard-kill the VM.

Does anyone have any idea what is going on, and what I can do to fix it?

-- 
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/5cf85e70-f517-412f-a0ea-f38522794e8d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[lokedhs]

On Friday, 24 March 2017 19:34:47 UTC+8, Opal Raava  wrote:
 
> > Ah, problem solved. In the web build documentation it says to:
> > 
> > cp example-configs/qubes-os-master.conf builder.conf
> > 
> > if you instead do:
> > 
> > cp example-configs/qubes-os-r3.2.conf
> > 
> > you get a better branch. I'm currently trying to build that
> 
> I have now a new shiny ISO, so this works. Isn't it a bug in the website 
> documentation that they recommend building from the master branch?

I'm building it myself at the moment. I'm wondering if what I'll be getting is 
something identical to the release image that you can download?

My goal with all of this is to build an image that contains the most recent 
release in the image, so that I might be able to escape the Catch-22 situation 
where I need the network in order to download the update so I can use the 
network.

-- 
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/2289c69a-121a-44ef-a1ef-d4f797e3f6c7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[lokedhs]

On Thursday, 23 March 2017 18:23:30 UTC+8, Opal Raava  wrote:
> On Thursday, March 23, 2017 at 3:27:58 AM UTC+1, lok...@gmail.com wrote:
> > On Thursday, 23 March 2017 02:45:53 UTC+8, Opal Raava  wrote:
> > 
> > > Which tells us that we probably really do need version 3.9.0 of 
> > > qubes-tools.
> > 
> > Where can that version be found? Looking at the latest master of 
> > qubes-linux-utils, it only contains version 3.2.3:
> > 
> > https://github.com/QubesOS/qubes-linux-utils/blob/master/version

> Yes, and that is what surprises me as well. The relevant source has not been 
> touched in a while. I've looked, but I don't know why the build breaks. 
> 
> All I know for a fact is what you said, it asks for 3.9.0 and delivers 3.2.3 
> at the master branch. And that the relevant source files all have not been 
> changed recently.

The spec file was updated from 2.0.10 to 3.9.0 as of commit 
9780a95a0ad20b63f2da401f108f2dcb3511554b. The interesting thing is that the 
commit was on the 17'th December 2015. This is more than half a year before the 
most recent ISO images were built.

I really have no idea what the cause for this could be.

Regards,
Elias

-- 
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/08b31cd7-630b-4e7c-8310-66706fd3b302%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[lokedhs]

On Thursday, 23 March 2017 02:45:53 UTC+8, Opal Raava  wrote:

> Ok that build did not work. I'm getting the following error:
> 
> ../../bin/mkpadlock.py -s 36 -c 0xcc devices/appvm-red.png
> Traceback (most recent call last):
>   File "../../bin/mkpadlock.py", line 25, in 
> import qubesimgconverter
> ImportError: No module named qubesimgconverter
> ../Makefile.common:39: recipe for target 'devices/appvm-red.png' failed
> make[2]: *** [devices/appvm-red.png] Error 1
> make[2]: Leaving directory '/home/user/qubes-src/artwork/icons/36x36'
> Makefile:4: recipe for target 'all' failed
> make[1]: *** [all] Error 1
> 
> Which tells us that we probably really do need version 3.9.0 of qubes-tools.

Where can that version be found? Looking at the latest master of 
qubes-linux-utils, it only contains version 3.2.3:

https://github.com/QubesOS/qubes-linux-utils/blob/master/version

Regards,
Elias

-- 
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/6ef47e73-d96f-421a-9f7d-870a3309e24d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[lokedhs]

I'm trying to build Qubes from source, but when following the instructions 
(https://www.qubes-os.org/doc/qubes-builder/), the build fails with the message 
below. Does anyone have any advice?

Regards,
Elias

make[1]: Leaving directory '/home/emartenson/qubes-builder'
make[1]: Entering directory '/home/emartenson/qubes-builder'
-> Building core-admin-linux (rpm_spec/core-dom0-linux.spec) for fc23 dom0 
(logfile: build-logs/core-admin-linux-dom0-fc23.log)
--> Done:
  
qubes-src/core-admin-linux/pkgs/fc23/x86_64/qubes-core-dom0-linux-3.2.12-1.fc23.x86_64.rpm
  
qubes-src/core-admin-linux/pkgs/fc23/x86_64/qubes-core-dom0-linux-debuginfo-3.2.12-1.fc23.x86_64.rpm
  
qubes-src/core-admin-linux/pkgs/fc23/x86_64/qubes-core-dom0-linux-kernel-install-3.2.12-1.fc23.x86_64.rpm
-> Building core-admin-linux (rpm_spec/core-dom0-vaio-fixes.spec) for fc23 dom0 
(logfile: build-logs/core-admin-linux-dom0-fc23.log)
--> Done:
  
qubes-src/core-admin-linux/pkgs/fc23/x86_64/qubes-core-dom0-vaio-fixes-1.6.1-1.fc23.x86_64.rpm
make[1]: Leaving directory '/home/emartenson/qubes-builder'
make[1]: Entering directory '/home/emartenson/qubes-builder'
make[1]: Leaving directory '/home/emartenson/qubes-builder'
-> Building core-agent-linux (rpm_spec/core-vm.spec) for fc23 vm (logfile: 
build-logs/core-agent-linux-vm-fc23.log)
--> Done:
  
qubes-src/core-agent-linux/pkgs/fc23/x86_64/python2-dnf-plugins-qubes-hooks-3.2.16-1.fc23.x86_64.rpm
  
qubes-src/core-agent-linux/pkgs/fc23/x86_64/python3-dnf-plugins-qubes-hooks-3.2.16-1.fc23.x86_64.rpm
  
qubes-src/core-agent-linux/pkgs/fc23/x86_64/qubes-core-vm-3.2.16-1.fc23.x86_64.rpm
  
qubes-src/core-agent-linux/pkgs/fc23/x86_64/qubes-core-vm-debuginfo-3.2.16-1.fc23.x86_64.rpm
  
qubes-src/core-agent-linux/pkgs/fc23/x86_64/qubes-core-vm-systemd-3.2.16-1.fc23.x86_64.rpm
  
qubes-src/core-agent-linux/pkgs/fc23/x86_64/qubes-core-vm-sysvinit-3.2.16-1.fc23.x86_64.rpm
-> Building core-agent-linux (rpm_spec/core-vm-doc.spec) for fc23 vm (logfile: 
build-logs/core-agent-linux-vm-fc23.log)
--> Done:
  
qubes-src/core-agent-linux/pkgs/fc23/noarch/qubes-core-vm-doc-3.2.16-1.noarch.rpm
make[1]: Entering directory '/home/emartenson/qubes-builder'
-> Building linux-kernel (kernel.spec) for fc23 dom0 (logfile: 
build-logs/linux-kernel-dom0-fc23.log)
--> Done:
  
qubes-src/linux-kernel/pkgs/fc23/x86_64/kernel-4.4.55-11.pvops.qubes.x86_64.rpm
  
qubes-src/linux-kernel/pkgs/fc23/x86_64/kernel-devel-4.4.55-11.pvops.qubes.x86_64.rpm
  
qubes-src/linux-kernel/pkgs/fc23/x86_64/kernel-qubes-vm-4.4.55-11.pvops.qubes.x86_64.rpm
make[1]: Leaving directory '/home/emartenson/qubes-builder'
make[1]: Entering directory '/home/emartenson/qubes-builder'
-> Building artwork (qubes-artwork.spec) for fc23 dom0 (logfile: 
build-logs/artwork-dom0-fc23.log)
--> build failed!
make[2]: Entering directory '/home/emartenson/qubes-builder'
/home/emartenson/qubes-builder/qubes-src/builder-fedora//update-local-repo.sh 
fc23
sudo BACKEND_VMM=xen chroot /home/emartenson/qubes-builder/chroot-fc23 sh -c 
'cd /home/user/qubes-src/artwork; dnf  --refresh -y update'
Dependencies resolved.
Nothing to do.
Complete!
sudo BACKEND_VMM=xen chroot /home/emartenson/qubes-builder/chroot-fc23 sh -c 
'cd /home/user/qubes-src/artwork; dnf builddep --allowerasing --best  -y 
qubes-artwork.spec'
Package ImageMagick-6.9.2.7-1.fc23.x86_64 is already installed, skipping.
Package netpbm-progs-10.75.99-1.fc23.x86_64 is already installed, skipping.
No matching package to install: 'qubes-utils >= 3.9.0'
Not all dependencies satisfied
Error: Some packages could not be found.
/home/emartenson/qubes-builder/qubes-src/builder-fedora/Makefile.fedora:106: 
recipe for target 'dist-build-dep' failed
make[2]: *** [dist-build-dep] Error 1
make[2]: Leaving directory '/home/emartenson/qubes-builder'
Makefile.generic:147: recipe for target 'packages' failed
make[1]: *** [packages] Error 1
make[1]: Leaving directory '/home/emartenson/qubes-builder'
Makefile:221: recipe for target 'artwork-dom0' failed
make: *** [artwork-dom0] Error 1

-- 
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/b259f326-303f-4511-8644-40cd59b22892%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Error in qubes-builder: "Can't check signature"

[lokedhs]

On Wednesday, 22 March 2017 12:29:59 UTC+8, lok...@gmail.com  wrote:

> I'm trying to use qubes-builder to build an image from source. I followed the 
> instructions on the web site, but I'm getting errors when running "make 
> get-sources":

I did a new checkout of the source code, and then it worked. I'm not sure what 
happened but I'm not getting this error message anymore.

-- 
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/46777300-ba5e-4cfe-b9e8-90b4ea6dcf77%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Error in qubes-builder: "Can't check signature"

[lokedhs]

I'm trying to use qubes-builder to build an image from source. I followed the 
instructions on the web site, but I'm getting errors when running "make 
get-sources":

=
$ make get-sources
-> Updating sources for builder...
--> Fetching from https://github.com/QubesOS/qubes-builder.git master...
--> Verifying tags...
No valid signed tag found!
---> One of invalid tag:
object 2548dc6d3d44cd04d121643b5f3c7dcc28650776
type commit
tag mm_2548dc6d
tagger Marek Marczykowski-Górecki  1490065453 
+0100

Tag for commit 2548dc6d3d44cd04d121643b5f3c7dcc28650776
gpg: Signature made Mon 20 Mar 2017 08:04:12 PM PDT using RSA key ID 42CFA724
gpg: Can't check signature: No public key
error: could not verify the tag 'mm_2548dc6d'
make: *** [builder.get-sources] Error 1
=

Note that the signature seems to be fine, as the tag command works:

=
$ git tag -v `git describe`
object 2548dc6d3d44cd04d121643b5f3c7dcc28650776
type commit
tag mm_2548dc6d
tagger Marek Marczykowski-Górecki  1490065453 
+0100

Tag for commit 2548dc6d3d44cd04d121643b5f3c7dcc28650776
gpg: Signature made Mon 20 Mar 2017 08:04:12 PM PDT using RSA key ID 42CFA724
gpg: Good signature from "Marek Marczykowski-Górecki (Qubes OS signing key) 
"
=

Any suggestions as to what I'm supposed to do?

Regards,
Elias

-- 
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/92f8f402-768d-4ce0-ac89-01c7b460732b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: HCL - Dell Latitude 7480

[lokedhs]

On Tuesday, 21 March 2017 21:46:25 UTC+8, Mike Keehan  wrote:

> On Sun, 19 Mar 2017 21:39:15 -0700 (PDT)
> loke...@gmail.com wrote:
> 
> > On Monday, 20 March 2017 12:27:43 UTC+8, lok...@gmail.com  wrote:
> > > I have not been able to install Qubes 3.2 on this machine.
> > > 
> > > The installer cannot start as the graphics card is not supported.
> > > The result is that you get dropped into the text-based installer
> > > which does not work.
> > > 
> > > This is kind of disappointing as this is a very light laptop that
> > > supports up to 32 GB RAM, which would be very nice to have with
> > > Qubes.  
> > 
> > I forgot to include the actual specs for the machine I used for
> > testing:
> > 
> > Intel(R) Core(TM) i7-7600U CPU @ 2.80GHz
> > 16 GB RAM
> > Intel Integrated HD Graphics 620
> > 
> > Specs at: http://www.dell.com/sg/business/p/latitude-14-7480-laptop/pd
> > 
> 
> Have you booted in UEFI mode?  I had the same problem when using legacy
> boot.

Thank you. Doing that allowed me to do a normal install. However, the resulting 
installation does not have working networking (neither wired nor wireless). 
Doing "ip link" does not show any physical devices, so I suspect that this is a 
driver issue.

I will build a new installer image in the hope that it will contain the 
appropriate drivers. I will update this post when this is done.

-- 
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/d1fd7ced-d079-4092-be29-4a7375ad2e76%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] New Qubes installer image?

[lokedhs]

On Tuesday, 21 March 2017 10:01:57 UTC+8, Andrew David Wong  wrote:

> We almost never publish new ISOs for Qubes OS versions that have
> already been released. It's likely that the next time a new ISO will
> be published with updated drivers will be when Qubes 4.0 is released.

Thank you for the honest reply, even if it's one that causes me some amount of 
trouble.

The fact Qubes 3.2 can't be installed on modern hardware is problematic, so 
here's hoping that Qubes 4 will be out in a reasonable amount of time.

Now for a question:

In a recent post you asked people to try the beta repositories. In that email 
there was a link to instructions how to build the ISO image. If I were to do 
that, would that image contain the latest kernel and drivers? If so, that could 
possibly be a solution to the problem of installing 3.2 on a modern laptop.

Regards,
Elias

-- 
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/f75e91b4-eb95-4872-b13f-dcbc63a46edf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] New Qubes installer image?

[lokedhs]

Since Qubes cannot be easily installed if things like networking or graphics is 
not available during installation, is there any plan to create a new installer 
image that has newer drivers?

On my old Dell Latitude E7470, I was unable to get WLAN working until I had 
performed a dom0 update. I was lucky to have access to a wired connection at 
the time, but if I had not, this would have been a difficult problem.

The newest laptop I have is a Dell Latitude 7480, where pretty much nothing 
works using the drivers that are included in the installer (To be fair, this 
machine is new enough that I'm doubtful that even the latest dom0 update would 
have support for it. But that does not change the question).

Are there any plans to create an updated installer image?

Regards,
Elias

-- 
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/d9e06a46-53d3-4fed-ad95-a5972edb7b2f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: HCL - Dell Latitude 7480

[lokedhs]

On Monday, 20 March 2017 12:27:43 UTC+8, lok...@gmail.com  wrote:
> I have not been able to install Qubes 3.2 on this machine.
> 
> The installer cannot start as the graphics card is not supported. The result 
> is that you get dropped into the text-based installer which does not work.
> 
> This is kind of disappointing as this is a very light laptop that supports up 
> to 32 GB RAM, which would be very nice to have with Qubes.

I forgot to include the actual specs for the machine I used for testing:

Intel(R) Core(TM) i7-7600U CPU @ 2.80GHz
16 GB RAM
Intel Integrated HD Graphics 620

Specs at: http://www.dell.com/sg/business/p/latitude-14-7480-laptop/pd

-- 
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/cdf03343-0ab2-442c-aec2-8bcda3f546af%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] HCL - Dell Latitude 7480

[lokedhs]

I have not been able to install Qubes 3.2 on this machine.

The installer cannot start as the graphics card is not supported. The result is 
that you get dropped into the text-based installer which does not work.

This is kind of disappointing as this is a very light laptop that supports up 
to 32 GB RAM, which would be very nice to have with 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 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/003a1f65-7fc0-4390-b8ed-4e24bdf763d7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Dealing with ssh

[lokedhs]

What is the best way to handle ssh in Qubes?

I have a set of machines I often log in to remotely, and I want to make sure 
the sessions (as well as the private keys) are protected from vulnerabilities 
in other applications.

Currently I have set of a dedicates ssh qube from which I run all my ssh 
sessions. I've also set its firewall to only allow access to the machines I 
normally connect to.

Is there a better way to handle this? Ideally, I'd like to be able to use 
dispvms for ssh, but how would I handle the private keys?

How do other people do this?

Regards,
Elias

-- 
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/733c2264-8f4a-4170-9122-697d50f83a6c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] postfix

[lokedhs]

On Wednesday, 8 March 2017 14:08:29 UTC+8, Nick Darren  wrote:

> First, the commands I added to /rw/config/rc.local don't seem to run.
> Namely, it doesn't appear to be mounting the /usr/local/etc/postfix
> directory in /etc/postfix. Also postfix doesn't appear to be running on
> startup. How do we tell if that gets run correctly?

You have to set the executable bit on the script. If you don't do that, the 
script won't run.

-- 
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/54c7c1e6-68c6-4cc6-9c38-f8412f794f58%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes 4 Release Date

[lokedhs]

On Wednesday, 8 March 2017 02:59:18 UTC+8, cooloutac  wrote:
> I think most new users want more passthrough like gpu. IMO if I want to be 
> secure 
> on my pc i try to avoid those things.  I have a separate machine for gaming 
> for 
> example.  But I guess the idea of qubes is to be able to do risky things more 
> securely in isolated manner and is originally aimed at home users.

Didn't the Linux kernel gain VGPU support recently? The whole point of that 
feature is to allow VM's to take advantage of the GPU. Couldn't that be 
supported in 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 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/7e473c0a-6764-4458-b065-329ac7c50862%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Upgrading from Qubes 3 to 4.

[lokedhs]

On Tuesday, 7 March 2017 03:56:20 UTC+8, Jean-Philippe Ouellet  wrote:

> https://www.qubes-os.org/news/2016/09/02/4-0-minimum-requirements-3-2-extended-support/
> 
> Note that those are bare minimum requirements, and that you will
> probably want more. If you need to run windows HVMs, I'd say at least
> double those recommendations.
> 
> I'm probably something of a power user, but used to run out of memory
> regularly with 8gb and am about to run out of disk with 500gb.
> 
> I think perhaps we should consider adding a "recommended requirements"
> section instead of just "minimum requirements".

Thank you. I have read that, and I have already settled on getting a 32 GB 
laptop. My question, however, was whether it's expected that the upgrade 
procedure will be difficult to the point where doing a full reinstall is easier.

In particular, I'd like to know if existing QVM's will be compatible with Qubes 
4 (i.e. can I just back them up and load them into Qubes 4?).

Of course, if Qubes 4 isn't going to be out until much later, then the entire 
question is moot anyway since I'll have no choice but to go for Qubes 3.2 
anyway. That is the reason I was asking whether there is a release date for 
Qubes 4 yet.

-- 
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/b4610ab6-f7ce-4a5b-b91e-d9ee6e495f36%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Upgrading from Qubes 3 to 4.

[lokedhs]

Hello,

I'm looking at getting a new laptop in the next few months. I will, of course, 
run Qubes on this thing but since Qubes 4 is on the horizon I'm wondering how 
easy/difficult it will be to upgrade once it's out. Has anything been said 
about this?

Since I don't really need my new computer until June, I'm considering holding 
off and wait for Qubes 4 to come out. Has anything been said about the release 
date? Googling doesn't reveal much in the way of recent information.

Regards,
Elias

-- 
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/72ae1f44-22ef-464c-bc13-086e1815be85%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Programmatically performing software update

[lokedhs]

On Thursday, 2 March 2017 03:59:39 UTC+8, Jimmy Axenhus  wrote:

> I got a Python script for that. Put in dom0 and run it. Unlike Andrews
> script this one will update all VMs in parallel and is interactive
> rather than non-interactive.

Thanks a lot to both you and David for helping out with this. I have no managed 
to do what I want.

By the way, is there a way to access this Qubes management API without using 
Python? (I specifically want to use Lisp, but I can hook into anything that 
isn't language-specific).

Regards,
Elias

-- 
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/de5c80dd-2ef5-41c1-a5d8-ef264733114b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Programmatically performing software update

[lokedhs]

I tend to use Qubes VM's not just for security purposes, but also as a very 
convenient way to have clean, manageable VM's where I only install the stuff I 
need for a specific task.

This has led me to have a large number non-template VM's, all of which needs to 
be manually updated every time there is a software update.

Right now, for each VM, I have to click on update, wait for the dialogue box to 
spin for a while waiting for the VM to start, then manually choose “yes” to 
update. This process gets old really fast.

Is there a way to automate this so that I can simply say “yes, I want to update 
all these VM's, go ahead and do it”?

Regards,
Elias

-- 
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/9ccf70a8-9eb7-4973-bb3e-45d27b918c61%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Archlinux template system update

[lokedhs]

On Tuesday, 21 February 2017 02:25:25 UTC+8, Francesco  wrote:

> I wonder if am the only one with this issue.

You're not the only one. I have it too and I haven't been able to get past it. 
It happens immediately when trying to upgrade the standard Arch 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/981f4c58-701e-4405-9040-ad437c6c2167%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.