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

[Elias Mårtenson]

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 /etc/X11/xinit/xinitrc, that script sources another script which in 
turn sources $HOME/.profile, so as far as I can tell, this should work.

Could it be that the Nautilus server isn't started by the user's session 
itself? If so, how do I work around 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/ac3d022d-ee35-4890-8b50-23118d96ca23%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Issues with Yubikey 4 input

[Jon R.]

> Looks like the X server in target VM cannot access the device. See
> ~/.local/share/xorg/X.0.log there for lines like this:
>
>[247082.612] (EE) xf86OpenSerial: Cannot open device /dev/input/event1
>Permission denied.
>[247082.612] (II) event1: opening input device '/dev/input/event1'
failed (Permission denied).
>[247082.612] (II) event1  - failed to create input device
'/dev/input/event1'.

> In Fedora there is "ykpers" package, which ships appropriate udev rules
> to fix permissions.

This doesn't appear to be the issued. The only relevant messages I'm seeing
in both the sys-usb VM & the one I'm attaching it to (personal in this
case) is the following:

> [   684.323] (II) config/udev: Adding input device Yubico Yubikey 4
OTP+CCID (/dev/input/event8)
> [   684.323] (II) No input driver specified, ignoring this device.
> [   684.323] (II) This device may have been added with another device
file.

This appears in the sys-usb ~/.local/xorg/Xorg.0.log upon plugging in the
Yubikey however the Yubikey functions as usual. When attaching the device
to another VM the local ~/.local/xorg/Xorg.0.log shows the same message as
above however it does not work.

Just to remove the udev rules being the potential culprit I added both
ykpers / ykpers-devel to the fedora template and rebooted. The same
behavior persists.

On Sun, Mar 18, 2018 at 11:43 AM, Marek Marczykowski-Górecki <
marma...@invisiblethingslab.com> wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Fri, Mar 09, 2018 at 12:34:02PM -0500, Jon R. wrote:
> > Hello,
> >
> > I've scoured around the mailing lists / SO / Reddit and haven't come
> across
> > a solution to this yet. I'm running 4.0 (R4.0) and when I attempt to use
> my
> > Yubikey it's seemingly not picking up any input on the button press.
> >
> > It's detecting the USB properly and I can attach it fine:
> >
> > [cloe@dom0 Desktop]$ qvm-usb
> > BACKEND:DEVID  DESCRIPTION USED BY
> > sys-usb:2-1Yubico_Yubikey_4_OTP+CCID
> >
> > [cloe@dom0 Desktop]$ qvm-usb attach work sys-usb:2-1
> >
> > [cloe@dom0 Desktop]$ qvm-usb
> > BACKEND:DEVID  DESCRIPTION USED BY
> > sys-usb:2-1Yubico_Yubikey_4_OTP+CCID   work
> >
> > However upon button presses on the Yubikey in the "work" domain there is
> no
> > action. I've tested this in gedit, the terminal and elsewhere to no
> avail.
> >
> > Can someone point me in the right direction as to what may be happening?
> > I've successfully attached storage devices and other smart card related
> > devices without any issue so it seems to be isolated to the Yubikey
> itself.
> > I've tried 2 separate Yubikey 4's and an older version to no avail.
>
> Looks like the X server in target VM cannot access the device. See
> ~/.local/share/xorg/X.0.log there for lines like this:
>
> [247082.612] (EE) xf86OpenSerial: Cannot open device /dev/input/event1
> Permission denied.
> [247082.612] (II) event1: opening input device '/dev/input/event1'
> failed (Permission denied).
> [247082.612] (II) event1  - failed to create input device
> '/dev/input/event1'.
>
> In Fedora there is "ykpers" package, which ships appropriate udev rules
> to fix permissions.
>
> - --
> Best Regards,
> Marek Marczykowski-Górecki
> Invisible Things Lab
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> -BEGIN PGP SIGNATURE-
>
> iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlqoECkACgkQ24/THMrX
> 1ywKfgf/VZgu5vIHC0sNztwJU6+8nZ23LaBtoEAceGdN3v9GZCkVY0kFDQ6jDhKO
> Jzp3wVPNM2XopNXmo+5mCgheL6nFGEQZfv6yB4MSwAUqqzcKxXy3eBkxAvAHfr3F
> g0H/lEYLLQImuoaEgz0RfQZUwxz3VKItakj2S6tqUfDzUvprFTo1Gvhv/xT1wp+6
> OcfK953ID4pl1DTBdf18DOQcTFIxWplGpHBEScJVjFVrtVtxlW72c/kJvliEl7uh
> EQjGtCM3MHNL4GC2x8+n5aWrfva9tiEqVXlubvo/ReFbCtpqISxJI8TQkCi1IC8g
> pAbBb8scoDJ9ik97GjvhMfoDuXwZvw==
> =Ut6d
> -END PGP SIGNATURE-
>

-- 
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/CAJd29STs2k7DPqFVuhC0h-m3%3D%2BTbd%2Bd-w%2BYcCdVb1CX1S-epkg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] please remind me how to remove orphaned Domain: menu items, the AppVM is gone, but I still see it listed in the Application 'Q' menu in 3.2

[yrebstv]

On 2018-03-18 12:31, Unman wrote:
> On Sun, Mar 18, 2018 at 02:51:30PM -0700, yreb...@riseup.net wrote:
>> On 2018-03-13 16:36, awokd wrote:
>> > On Wed, March 14, 2018 12:30 am, yreb...@riseup.net wrote:
>> >> please remind me how to remove orphaned Domain: menu items,  the AppVM is
>> >> gone, but I still see it listed in the Application 'Q' menu in 3.2
>> >>
>> >> but not in  qvm-ls  ; I don't want to remove the wrong  config file
>> >> somewhere ,  I can't seem to find it in the  old  group  postings, though
>> >> I know it's there
>> >
>> > Look in the R3.2 section:
>> > https://www.qubes-os.org/doc/managing-appvm-shortcuts/
>>
>> hmm the issue seems to be that I have now upgraded debian-8 TemplateVM
>> to debian-9
>>
>> and the AppVM that won't go-away is based on the debian-8  TemplateVM
>> based on what I see in the menu-items in the "Q" menu..
>>
>> So:::
>>
>> something like:  qvm-sync -appmenus debian-8  isn't going to work   as
>> the Template is gone ...
>>
>> Further: after the debian-9 upgrade  I did do :
>>
>> [user@dom0 ~]$ sudo yum remove qubes-template-debian-8
>>
>> However, it ALSO is still in the "Q" menu on the taskbar  &  the
>> Right-Click  menus  Domain lists
>>
>>
>> any other ideas, besides this post and the previous one where I deleted
>> :
>>
>> /var/lib/qubes/appvms/  to no effect  .
>>
> Have you looked at:
> https://www.qubes-os.org/doc/remove-vm-manually/


ah yes, that was what I did last year at some point,  I guess I need to
add to my  list 'learn how to search qubes docs'  really 

steps 1 and 2 already did but not  3 -4   

thank you sir/s 

-- 
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/9fc1e2fa015a5e485ba816743d5eb915%40riseup.net.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] please remind me how to remove orphaned Domain: menu items, the AppVM is gone, but I still see it listed in the Application 'Q' menu in 3.2

[Unman]

On Sun, Mar 18, 2018 at 02:51:30PM -0700, yreb...@riseup.net wrote:
> On 2018-03-13 16:36, awokd wrote:
> > On Wed, March 14, 2018 12:30 am, yreb...@riseup.net wrote:
> >> please remind me how to remove orphaned Domain: menu items,  the AppVM is
> >> gone, but I still see it listed in the Application 'Q' menu in 3.2
> >>
> >> but not in  qvm-ls  ; I don't want to remove the wrong  config file
> >> somewhere ,  I can't seem to find it in the  old  group  postings, though
> >> I know it's there
> > 
> > Look in the R3.2 section:
> > https://www.qubes-os.org/doc/managing-appvm-shortcuts/
> 
> hmm the issue seems to be that I have now upgraded debian-8 TemplateVM
> to debian-9  
> 
> and the AppVM that won't go-away is based on the debian-8  TemplateVM
> based on what I see in the menu-items in the "Q" menu..
> 
> So:::
> 
> something like:  qvm-sync -appmenus debian-8  isn't going to work   as
> the Template is gone ... 
> 
> Further: after the debian-9 upgrade  I did do :
> 
> [user@dom0 ~]$ sudo yum remove qubes-template-debian-8
> 
> However, it ALSO is still in the "Q" menu on the taskbar  &  the 
> Right-Click  menus  Domain lists 
> 
> 
> any other ideas, besides this post and the previous one where I deleted
> :
> 
> /var/lib/qubes/appvms/  to no effect  .
> 
Have you looked at:
https://www.qubes-os.org/doc/remove-vm-manually/

-- 
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/20180318223125.uqcmzgoenugbi662%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] please remind me how to remove orphaned Domain: menu items, the AppVM is gone, but I still see it listed in the Application 'Q' menu in 3.2

[yrebstv]

On 2018-03-13 16:36, awokd wrote:
> On Wed, March 14, 2018 12:30 am, yreb...@riseup.net wrote:
>> please remind me how to remove orphaned Domain: menu items,  the AppVM is
>> gone, but I still see it listed in the Application 'Q' menu in 3.2
>>
>> but not in  qvm-ls  ; I don't want to remove the wrong  config file
>> somewhere ,  I can't seem to find it in the  old  group  postings, though
>> I know it's there
> 
> Look in the R3.2 section:
> https://www.qubes-os.org/doc/managing-appvm-shortcuts/

hmm the issue seems to be that I have now upgraded debian-8 TemplateVM
to debian-9  

and the AppVM that won't go-away is based on the debian-8  TemplateVM
based on what I see in the menu-items in the "Q" menu..

So:::

something like:  qvm-sync -appmenus debian-8  isn't going to work   as
the Template is gone ... 

Further: after the debian-9 upgrade  I did do :

[user@dom0 ~]$ sudo yum remove qubes-template-debian-8

However, it ALSO is still in the "Q" menu on the taskbar  &  the 
Right-Click  menus  Domain lists 


any other ideas, besides this post and the previous one where I deleted
:

/var/lib/qubes/appvms/  to no effect  .


-- 
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/566ba54571d3291e97b396081b3af3cb%40riseup.net.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Coreboot + Qubes :: Best Practises / Coreboot docs page

[Rusty Bird]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

799:
> > $ build/cbfstool build/coreboot.rom add-int -i 0 -n 
> > etc/pci-optionrom-exec
> 
> When do I need to run this? After building my Coreboot ROM?

Yes, see payloads/external/SeaBIOS/seabios/docs/Runtime_config.md for
a list of cbfs options.

> Can't this option be included in the Coreboot or SeaBIOS menuconfig?

Looks like CONFIG_OPTIONROMS=n ("BIOS Interfaces" -> "Option ROMS" in
SeaBIOS menuconfig) should be equivalent.

> I am already using the console setting in my grub installation.
> Can I still boot from a USB stick which has graphical boot enabled?

Booting works, but the GRUB screen is invisible. And the Qubes
installer boot screen (isolinux) is somewhat garbled.

> > You might also enjoy HEADS.
> > https://github.com/osresearch/heads
> 
> Thanks, looks very interesting, but as far as I understand I don't need
> Seabios when I am running Heads?
> Is somebody already using heads? From the website it seems that it is not
> that easy to install and maybe still under development?

I think that's all correct. Not sure though, I still haven't tried
HEADS myself yet.

Rusty
-BEGIN PGP SIGNATURE-

iQJ8BAEBCgBmBQJart5cXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ4NEI1OUJDRkM2MkIxMjlGRTFCMDZEMDQ0
NjlENzhGNDdBQUYyQURGAAoJEEadePR6ryrf1aQP+wU1fmTESwGkdUvT1Tzyrnyr
TVKH4hmo7zRv2WXeot12PbfLr/MUsiUkiHLA36u5M1k3HlZasi0wwrMllDNEJnaj
Neq6BtRZE+Dl2OYcMoksjT40deAWYzf4Kct3s6BK93RlsnrkoTSZ4QbJwRxSi0HJ
CZ4lxsW1ucVT6oAieVu7Ol1W8nRXPcrR0BvHKQ2qJGkfC2x8oMOZlLdNLB5hO8Dl
mqye+9V5la+jneVg/8z0PR8UVU/09n8+TmYp3w6isX0VHabv2fpXNQXjiF4gf5nz
uoTl+7/4nXpA81JMUk6CLl0HOnJhlRo0dcG/DaB2J/bSfGk7ADOzHBWrQ1ETifuy
8RLp6Hh0VZU69+BG409hCGte4pzObAjQEjkPYkruSqGLUny6YRGmtwiU/yiLrghV
WfiGW1zIes73NvymEW99Y4/IIy77xKq7HOR+54L5N/pXDOCLKDdslJRlEpYdlhIo
Vmmb58FidYuJ1aJMq45CDuzhFaLLj+DTklENQaUj3VRNZrAIA32aCPrfymabDSSQ
BDqqWge3+kdJi8NhPUJs4ljIK5a6I8942LOG8uUuvX9WXV4731y2DZwTMort0igT
OCjLNy28RGFDMKqSLJj+PVqdpTZNiT1VoNh9m+HstTjTf4mS8h2L51QrWIuKSfwf
yd8R4lXm5Suw6LtUOFlv
=4djs
-END PGP SIGNATURE-

-- 
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/20180318214708.GA2699%40mutt.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] upgraded debian 8 to 9 on qubes 3.2 but no file manager now.

[Unman]

On Sun, Mar 18, 2018 at 02:29:07PM -0700, cooloutac wrote:
> On Thursday, March 15, 2018 at 7:44:23 PM UTC-4, Unman wrote:
> > On Thu, Mar 15, 2018 at 08:32:20PM +, Unman wrote:
> > > On Thu, Mar 15, 2018 at 12:49:43PM -0700, cooloutac wrote:
> > > > On Thursday, March 15, 2018 at 1:41:18 PM UTC-4, Unman wrote:
> > > > > On Thu, Mar 15, 2018 at 10:13:45AM -0700, cooloutac wrote:
> > > > > > So I upgraded debian-8 to debian-9 on qubes 3.2   But for some 
> > > > > > reason it has no file manager now.  Even if installing one from 
> > > > > > terminal and then syncing appmenus from dom0.  no file manager 
> > > > > > appears in list.
> > > > > > 
> > > > > > Is there a qubes debian 9 template to install to qubes 3.2?  
> > > > > > 
> > > > > > Thanks, Rich.
> > > > > > 
> > > > > There is a debian-9 template, but you have the choice of which file 
> > > > > manager
> > > > > you want installed. Just apt-get install whatever you want.
> > > > 
> > > > according to qubes-os website debian-9 template is only available for 
> > > > qubes 4.0?
> > > > 
> > > > I did try to install nautilus.  then did qvm-sync-appmenus  but still 
> > > > no file manager in the app list to add.
> > > > 
> > > You're right - there isnt a pre-built Debian-9 for 3.2.(I'm confused
> > > because I roll my own.)
> > > But you can build your own or upgrade an existing.
> > > I'm not quite clear on why file manager doesn't appear in the app list
> > > for you, because I installed it myself following your email and it just
> > > worked.
> > > Let me test again, with a clean debian-8 upgrade, and see if I can
> > > reproduce. (Just to check - do you have an updated dom0 and are you
> > > using Testing repos in dom0?)
> > 
> > So I've just started from a clean Debian-8, updated, dist-upgraded to
> > Debian-9 and reinstalled nautilus. Created New qube and the "Files" item
> > is there.
> > So that all seems fine.
> > Have you checked that the install went OK and have you tried the manual
> > method for adding menu items?
> > What are you running in dom0 - is that up to date? Running from Testing
> > repositories?
> 
> I still can't get a file manager to show up in the appmenu, even after 
> installing nautilus and confirming it loads from the template and doing a 
> qvm-sync-appmenus.  
> 
> I also realized that if I have debian-9 as template for sys-firewall I can't 
> update dom0.  It says it is missing the dom0 update folder.
> 

The second is a known issue which I thought had been fixed.
On the first you havent answered my questions.

-- 
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/20180318213953.uq4zkjkng52awxnh%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] upgraded debian 8 to 9 on qubes 3.2 but no file manager now.

[cooloutac]

On Thursday, March 15, 2018 at 7:44:23 PM UTC-4, Unman wrote:
> On Thu, Mar 15, 2018 at 08:32:20PM +, Unman wrote:
> > On Thu, Mar 15, 2018 at 12:49:43PM -0700, cooloutac wrote:
> > > On Thursday, March 15, 2018 at 1:41:18 PM UTC-4, Unman wrote:
> > > > On Thu, Mar 15, 2018 at 10:13:45AM -0700, cooloutac wrote:
> > > > > So I upgraded debian-8 to debian-9 on qubes 3.2   But for some reason 
> > > > > it has no file manager now.  Even if installing one from terminal and 
> > > > > then syncing appmenus from dom0.  no file manager appears in list.
> > > > > 
> > > > > Is there a qubes debian 9 template to install to qubes 3.2?  
> > > > > 
> > > > > Thanks, Rich.
> > > > > 
> > > > There is a debian-9 template, but you have the choice of which file 
> > > > manager
> > > > you want installed. Just apt-get install whatever you want.
> > > 
> > > according to qubes-os website debian-9 template is only available for 
> > > qubes 4.0?
> > > 
> > > I did try to install nautilus.  then did qvm-sync-appmenus  but still no 
> > > file manager in the app list to add.
> > > 
> > You're right - there isnt a pre-built Debian-9 for 3.2.(I'm confused
> > because I roll my own.)
> > But you can build your own or upgrade an existing.
> > I'm not quite clear on why file manager doesn't appear in the app list
> > for you, because I installed it myself following your email and it just
> > worked.
> > Let me test again, with a clean debian-8 upgrade, and see if I can
> > reproduce. (Just to check - do you have an updated dom0 and are you
> > using Testing repos in dom0?)
> 
> So I've just started from a clean Debian-8, updated, dist-upgraded to
> Debian-9 and reinstalled nautilus. Created New qube and the "Files" item
> is there.
> So that all seems fine.
> Have you checked that the install went OK and have you tried the manual
> method for adding menu items?
> What are you running in dom0 - is that up to date? Running from Testing
> repositories?

I still can't get a file manager to show up in the appmenu, even after 
installing nautilus and confirming it loads from the template and doing a 
qvm-sync-appmenus.  

I also realized that if I have debian-9 as template for sys-firewall I can't 
update dom0.  It says it is missing the dom0 update folder.

-- 
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/ac0425fc-aec4-4ad4-8ff3-9f5dc8bf2200%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes 4 RC5 on a Thinkpad F430: HCL and some observations

[nortiusmediae]

On Friday, March 16, 2018 at 8:55:40 PM UTC-4, nortiu...@gmail.com wrote:
> (I originally posted this via gmane, but it hasn't shown up so far)
> 
> Hi, all,
> 
> I've spent a bunch of time in the last day or two getting RC5 running on my 
> daily driver, a Thinkpad 430 with 16 GB of memory and a 1 TB SSD.  It 
> normally runs 3.2, so I got a new WD SSD for playing with 4.0.
> 
> First observation:  It's pretty slick overall.  Kudos to the ITL team for 
> another winner.  If I ever visit Poland I'll be sure to budget for quite a 
> lot of beer, because I owe you folks.
> 
> There are a few curiosities:
> 
> 1. In dom0, typing
> 
> qvm-run -a myqube xterm
> 
> blocks the dom0 terminal till I close the xterm (or whatever other program).  
> I much preferred the 3.2 behaviour, in which the dom0 prompt returned right 
> away.  It's inelegant to keep going ctl-C in dom0, and I don't like the 
> setsid alternative since I don't know how much cruft I'm accumulating that 
> way.
> 
> 2. DispVMs based on AppVMs seem to crash on startup a lot.  As an engineer I 
> really like the ability to run old apps on archival VMs without corrupting 
> the archives, but on my box startup is a bit flaky. Once they're properly 
> running I haven't seen an issue so far.
> 
> 3. It would be nice if the DispVM frame gave some indication what template or 
> AppVM it was based on.  [disp xxxy] is a commendably unique identifier, but 
> there's a lot of space on the window frame, so "workDVMxxxy" or 
> "personalDVMzzzx" would be pretty useful.  (I usually have several AppVMs 
> going at once.)
> 
> 4. (probably most important)  Dom0 lies through its teeth about the disk 
> usage.  I gather you folks have hidden the VMs' guts so you can't just poke 
> around /var/lib/qubes anymore, but in the process you've completely confused 
> the only tools we mortals have left to manage disk space: domo's du and df 
> commands.
> 
> On a 1T SSD, I restored over 450G worth of AppVMs, but dom0's df returns:
> 
> Use% Mounted on
> devtmpfs  1995976   0   1995976   0% /dev
> tmpfs 2009828   0   2009828   0% /dev/shm
> tmpfs 20098281612   2008216   1% /run
> tmpfs 2009828   0   2009828   0% /sys/fs/cgroup
> /dev/mapper/qubes_dom0-root 935037724 3866076 883604596   1% /
> tmpfs 2009828   8   2009820   1% /tmp
> xenstore  2009828 416   2009412   1% 
> /var/lib/xenstored
> /dev/sda1  999320   79676850832   9% /boot
> tmpfs  401964   8401956   1% /run/user/1000
> 
> You'd never know that the disk is actually half full or a little more. I have 
> no idea how to manage my disk space on Qubes 4.0.
> 
> Thanks again
> 
> BillW
> 
> 
> 
> ---
> layout:
>   'hcl'
> type:
>   'notebook'
> hvm:
>   'yes'
> iommu:
>   'yes'
> slat:
>   'yes'
> tpm:
>   ''
> remap:
>   'yes'
> brand: |
>   LENOVO
> model: |
>   2349S7W
> bios: |
>   G1ET73WW (2.09 )
> cpu: |
>   Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz
> cpu-short: |
>   FIXME
> chipset: |
>   Intel Corporation 2nd Generation Core Processor Family DRAM Controller 
> [8086:0104] (rev 09)
> chipset-short: |
>   FIXME
> gpu: |
>   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
> Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
> gpu-short: |
>   FIXME
> network: |
>   Intel Corporation 82579LM Gigabit Network Connection (Lewisville) (rev 04)
>   Intel Corporation Centrino Wireless-N 2200 (rev c4)
> memory: |
>   16073
> scsi: |
>   WDC WDS100T2B0A- Rev: 30WD
>   DVD ROM DDU7740H Rev: 1RS0
> usb: |
>   3
> versions:
> 
> - works:
> 'FIXME:yes|no|partial'
>   qubes: |
> R4.0
>   xen: |
> 4.8.3
>   kernel: |
> 4.14.18-1
>   remark: |
> FIXME
>   credit: |
> FIXAUTHOR
>   link: |
> FIXLINK
> 
> ---

T430 not F430.  Fat fingers.

BW

-- 
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/6f1f5d8f-4691-48c5-9e91-4a5388d8fe6c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: HCL - Lenovo ideapad 700

[ishahinism]

On Sunday, August 20, 2017 at 5:00:33 PM UTC+4:30, daniel@gmail.com wrote:
> On Tuesday, October 11, 2016 at 7:34:15 PM UTC+2, Jan Fabo wrote:
> > Hi,
> > 
> > seems good on this machine.
> 
> Your report shows that IOMMU isn't supported, but Intel specs 
> (http://ark.intel.com/products/88967/Intel-Core-i7-6700HQ-Processor-6M-Cache-up-to-3_50-GHz)
>  say that VT-d is supported on the CPU. Are you sure you sure VT-d is enabled 
> in your BIOS (if you checked in a fully up-to-date BIOS I would be very 
> thankful) ? I found a post 
> https://www.reddit.com/r/nvidia/comments/58tqdx/pci_passthrough_geforce_gtx_960m/
>  which says that PCI passthrough works on Ideapad Y700 (although it is 
> different from Ideapad 700 I believe they are similar - but HCL shows that 
> IOMMU isn't supported on Y700 either ?).

I've updated BIOS to `E5CN61WW`, still no sign of VT-d in configuration. Just 
"Intel virtualization technology" is available which I enabled, but couldn't 
find any registered DMAR device for passthrough. 

BTW I own another Lenovo laptop (g50-70) which is identical in BIOS 
configuration options with ideapad 700 (15ISK), but enabling "Inter 
virtualization technology" is enough to get IOMMU enabled. 

-- 
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/9a5c60ef-63f3-4715-804d-e5e0938d26d4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes 4.0-rc5 freez during configuration

[Dominique St-Pierre Boucher]

On Sunday, March 18, 2018 at 10:22:06 AM UTC-4, Frédéric Pierret (fepitre) 
wrote:
> Le dimanche 18 mars 2018 15:18:50 UTC+1, Dominique St-Pierre Boucher a écrit :
> > On Sunday, March 18, 2018 at 10:16:30 AM UTC-4, Frédéric Pierret (fepitre) 
> > wrote:
> > > Is it related to this: 
> > > https://github.com/QubesOS/qubes-issues/issues/3198 ?
> > 
> > unfortunately no, it freezes in the setting up networking phase...
> 
> To be sure this is not the same strange phenomena, try to boot the setup with 
> rd.driver.blacklist=nouveau nouveau.modeset=0 video=vesa:off

Unfortunately same issue.

-- 
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/bacb062d-4627-4d24-8a42-ee12b9e2bf60%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Failed to start Qubes OS daemon

[Marek Marczykowski-Górecki]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sun, Mar 18, 2018 at 10:40:39AM -0700, qubel...@gmail.com wrote:
> On Sunday, March 18, 2018 at 7:17:39 PM UTC+2, Marek Marczykowski-Górecki 
> wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> > 
> > On Sun, Mar 18, 2018 at 09:39:17AM -0700, qubel...@gmail.com wrote:
> > > On Sunday, March 18, 2018 at 5:13:44 PM UTC+2, Marek Marczykowski-Górecki 
> > > wrote:
> > > > -BEGIN PGP SIGNED MESSAGE-
> > > > Hash: SHA256
> > > > 
> > > > On Sun, Mar 18, 2018 at 01:22:36AM -0700, qubel...@gmail.com wrote:
> > > > > After trying to restore one windows-7 appvm backup(R3) from external 
> > > > > usb drive(restore failed), I cant start no sys-net, no other appvms 
> > > > > after that. Present time I have R4 on my laptop(Lenovo x1 carbon 4th 
> > > > > gen). No Qubes GUIs doesn't work related qubes itself(e.x Create 
> > > > > Qubes VM,Restore Backup etc). "Systemctl status qubesd.service" 
> > > > > command gives me answer - Qubes OS daemon loaded but not 
> > > > > active.Failed to start Qubes OS daemon. What to do? 
> > > > 
> > > > Try running `sudo systemctl status qubesd.service`, you should see more
> > > > details about the reason for failed startup.
> > > 
> > > `sudo systemctl status qubesd.service`
> > > 
> > > qubesd.service - Qubes OS daemon
> > > Loaded:loaded(/usr/lib/systemd/system/qubesd.service; enabled;vendor 
> > > preset:enabled)
> > > Active:failed(Result:start-limit-hit) since ...;7 h ago
> > > Process:20536 ExecStart=/usr/bin/qubesd(code=exited,status=1/FAILURE)
> > > Main PID:20536(code=exited,status=1/FAILURE)
> > > 
> > > dom0 systemd[1]: Failed to start Qubes OS daemon.
> > > dom0 systemd[1]:qubesd.service:Unit entered failed state.
> > > dom0 systemd[1]:qubesd.service:Failed with result 'exit-code'.
> > > dom0 systemd[1]:qubesd.service:Service hold-off time over,scheduling 
> > > restart
> > > dom0 systemd[1]:Stopped Qubes OS daemon.
> > > dom0 systemd[1]:qubesd.service:Start request repeated too quickly
> > > dom0 systemd[1]: Failed to start Qubes OS daemon.
> > > dom0 systemd[1]:qubesd.service:Unit entered failed state.
> > > dom0 systemd[1]:qubesd.service:Failed with result start-limit-hit
> > 
> > Looks like more interesting data is beyond last 10 lines. See `journalctl
> > - -u qubesd.service`.
> 
> Please see attached file.

Ok, it looks like /var/lib/qubes/qubes.xml is empty. See
/var/lib/qubes/backup for backup copies. Note that some latest changes
(like creating/removing qubes) may be missing there.

- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlqoNSsACgkQ24/THMrX
1yyiFQf/cK5FVw1TQs1Ph5Tkus2mCPM+lcGMSR2i4Vvr9To+b/ZcIrFnRnXJLra0
x6yxiEzvjymR9fRk0t+J/Ut0qRgJJxpLjqZLaVcv3dN42yMrxjWRMWF7sTLMDbHL
cmCbgxvAjDUvcKcyf7s0jITaLcNevegUW8/XjvL1UCJUkClZBTbLmaq4cxStbU4u
mJtuljiDT89VhvBdzBcq8kU7rJk0+zpzKui7607n9erJr39TdZI8HmN+y/Qapr38
ZpKrY710tdTFW6JdKU3uuTqyc5Ok1P2k20e22oLM3oNfOCO7knBQliNPsQUsc+mp
ZB65FGYix1MnHwPaNeDA/oawM5/Pvg==
=YB46
-END PGP SIGNATURE-

-- 
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/20180318182054.GK8712%40mail-itl.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Failed to start Qubes OS daemon

[Marek Marczykowski-Górecki]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sun, Mar 18, 2018 at 09:39:17AM -0700, qubel...@gmail.com wrote:
> On Sunday, March 18, 2018 at 5:13:44 PM UTC+2, Marek Marczykowski-Górecki 
> wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> > 
> > On Sun, Mar 18, 2018 at 01:22:36AM -0700, qubel...@gmail.com wrote:
> > > After trying to restore one windows-7 appvm backup(R3) from external usb 
> > > drive(restore failed), I cant start no sys-net, no other appvms after 
> > > that. Present time I have R4 on my laptop(Lenovo x1 carbon 4th gen). No 
> > > Qubes GUIs doesn't work related qubes itself(e.x Create Qubes VM,Restore 
> > > Backup etc). "Systemctl status qubesd.service" command gives me answer - 
> > > Qubes OS daemon loaded but not active.Failed to start Qubes OS daemon. 
> > > What to do? 
> > 
> > Try running `sudo systemctl status qubesd.service`, you should see more
> > details about the reason for failed startup.
> 
> `sudo systemctl status qubesd.service`
> 
> qubesd.service - Qubes OS daemon
> Loaded:loaded(/usr/lib/systemd/system/qubesd.service; enabled;vendor 
> preset:enabled)
> Active:failed(Result:start-limit-hit) since ...;7 h ago
> Process:20536 ExecStart=/usr/bin/qubesd(code=exited,status=1/FAILURE)
> Main PID:20536(code=exited,status=1/FAILURE)
> 
> dom0 systemd[1]: Failed to start Qubes OS daemon.
> dom0 systemd[1]:qubesd.service:Unit entered failed state.
> dom0 systemd[1]:qubesd.service:Failed with result 'exit-code'.
> dom0 systemd[1]:qubesd.service:Service hold-off time over,scheduling restart
> dom0 systemd[1]:Stopped Qubes OS daemon.
> dom0 systemd[1]:qubesd.service:Start request repeated too quickly
> dom0 systemd[1]: Failed to start Qubes OS daemon.
> dom0 systemd[1]:qubesd.service:Unit entered failed state.
> dom0 systemd[1]:qubesd.service:Failed with result start-limit-hit

Looks like more interesting data is beyond last 10 lines. See `journalctl
- -u qubesd.service`.

- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlqoJiwACgkQ24/THMrX
1ywa5Af9F37oaUiPYhF3qT0gIIbaWR8FDSJtqEWleZ8mmFBx1yKi8Eef8ODkzyoh
jLoLewLB9/xCj+xcpdoMs9JKrg2uvgCX6W6sfJBIgSfN+anOVHyy5orlsrOybnho
dzlQXIx6SkPmomhqVjNKgnWXhJBDrVvFlJ9SiZrL1TMsvjffv9sDqKc4L+zAYovE
JETPUKuNG1o14BVvy1sob1Zw/o4vhUqzx7pEyo0PXls+bCnNdv1VngRkKd09xEJ5
kI+5SuR/YxbLZmhiR9y5BZGe09UsweKa3oPhmatIgqGh6VxbPmWCYE/v5nVjD9g6
WpGxDXIUFuJdOW6vyHFgWUOf/gcewg==
=fw28
-END PGP SIGNATURE-

-- 
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/20180318171655.GJ8712%40mail-itl.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Failed to start Qubes OS daemon

[qubeloop]

On Sunday, March 18, 2018 at 5:13:44 PM UTC+2, Marek Marczykowski-Górecki wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> On Sun, Mar 18, 2018 at 01:22:36AM -0700, qubel...@gmail.com wrote:
> > After trying to restore one windows-7 appvm backup(R3) from external usb 
> > drive(restore failed), I cant start no sys-net, no other appvms after that. 
> > Present time I have R4 on my laptop(Lenovo x1 carbon 4th gen). No Qubes 
> > GUIs doesn't work related qubes itself(e.x Create Qubes VM,Restore Backup 
> > etc). "Systemctl status qubesd.service" command gives me answer - Qubes OS 
> > daemon loaded but not active.Failed to start Qubes OS daemon. What to do? 
> 
> Try running `sudo systemctl status qubesd.service`, you should see more
> details about the reason for failed startup.
> 
> - -- 
> Best Regards,
> Marek Marczykowski-Górecki
> Invisible Things Lab
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> -BEGIN PGP SIGNATURE-
> 
> iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlqoCSMACgkQ24/THMrX
> 1yyS9Af/QGINuOyCYkbgVPfV34K2tklADIVgOqdNudG8Gh3WtLP3T0+2R4nf+rUE
> 6BaRPSqs/ChWPSaF5vftCVHIZqCzKAq4xxEnZ+PCcMOtBiCiw6wyZTGCpN4ThNBe
> /uiJhre1wvFdF2TeHobFeA1gK+v3290gnCmt0qfdK0CykmJnJJlGkkFFhSnZYedB
> cECKd6A+o6Ozs4oDPzh4KgAEAQm/oV9hxvQgpUXX8qMr6nBMSvlJSW+dyWQ2ZRPi
> vV/GG835v+nnxhwfpgN3QkAorcJw07l4LRAnTC/DBReK2WaPVgsAlk66vGTPHLgV
> 4aZ3IxaX2qDC/yYAKjt2/TiNUtaT1Q==
> =S0jV
> -END PGP SIGNATURE-

`sudo systemctl status qubesd.service`

qubesd.service - Qubes OS daemon
Loaded:loaded(/usr/lib/systemd/system/qubesd.service; enabled;vendor 
preset:enabled)
Active:failed(Result:start-limit-hit) since ...;7 h ago
Process:20536 ExecStart=/usr/bin/qubesd(code=exited,status=1/FAILURE)
Main PID:20536(code=exited,status=1/FAILURE)

dom0 systemd[1]: Failed to start Qubes OS daemon.
dom0 systemd[1]:qubesd.service:Unit entered failed state.
dom0 systemd[1]:qubesd.service:Failed with result 'exit-code'.
dom0 systemd[1]:qubesd.service:Service hold-off time over,scheduling restart
dom0 systemd[1]:Stopped Qubes OS daemon.
dom0 systemd[1]:qubesd.service:Start request repeated too quickly
dom0 systemd[1]: Failed to start Qubes OS daemon.
dom0 systemd[1]:qubesd.service:Unit entered failed state.
dom0 systemd[1]:qubesd.service:Failed with result start-limit-hit


-- 
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/3c88fb4a-3b74-4f91-a2d0-4d72525b4305%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Issues with Yubikey 4 input

[Marek Marczykowski-Górecki]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Fri, Mar 09, 2018 at 12:34:02PM -0500, Jon R. wrote:
> Hello,
> 
> I've scoured around the mailing lists / SO / Reddit and haven't come across
> a solution to this yet. I'm running 4.0 (R4.0) and when I attempt to use my
> Yubikey it's seemingly not picking up any input on the button press.
> 
> It's detecting the USB properly and I can attach it fine:
> 
> [cloe@dom0 Desktop]$ qvm-usb
> BACKEND:DEVID  DESCRIPTION USED BY
> sys-usb:2-1Yubico_Yubikey_4_OTP+CCID
> 
> [cloe@dom0 Desktop]$ qvm-usb attach work sys-usb:2-1
> 
> [cloe@dom0 Desktop]$ qvm-usb
> BACKEND:DEVID  DESCRIPTION USED BY
> sys-usb:2-1Yubico_Yubikey_4_OTP+CCID   work
> 
> However upon button presses on the Yubikey in the "work" domain there is no
> action. I've tested this in gedit, the terminal and elsewhere to no avail.
> 
> Can someone point me in the right direction as to what may be happening?
> I've successfully attached storage devices and other smart card related
> devices without any issue so it seems to be isolated to the Yubikey itself.
> I've tried 2 separate Yubikey 4's and an older version to no avail.

Looks like the X server in target VM cannot access the device. See
~/.local/share/xorg/X.0.log there for lines like this:

[247082.612] (EE) xf86OpenSerial: Cannot open device /dev/input/event1
Permission denied.
[247082.612] (II) event1: opening input device '/dev/input/event1' failed 
(Permission denied).
[247082.612] (II) event1  - failed to create input device 
'/dev/input/event1'.

In Fedora there is "ykpers" package, which ships appropriate udev rules
to fix permissions.

- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlqoECkACgkQ24/THMrX
1ywKfgf/VZgu5vIHC0sNztwJU6+8nZ23LaBtoEAceGdN3v9GZCkVY0kFDQ6jDhKO
Jzp3wVPNM2XopNXmo+5mCgheL6nFGEQZfv6yB4MSwAUqqzcKxXy3eBkxAvAHfr3F
g0H/lEYLLQImuoaEgz0RfQZUwxz3VKItakj2S6tqUfDzUvprFTo1Gvhv/xT1wp+6
OcfK953ID4pl1DTBdf18DOQcTFIxWplGpHBEScJVjFVrtVtxlW72c/kJvliEl7uh
EQjGtCM3MHNL4GC2x8+n5aWrfva9tiEqVXlubvo/ReFbCtpqISxJI8TQkCi1IC8g
pAbBb8scoDJ9ik97GjvhMfoDuXwZvw==
=Ut6d
-END PGP SIGNATURE-

-- 
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/20180318154300.GI8712%40mail-itl.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Disk problems when installing ReactOS 0.4.5 on HVM

[Marek Marczykowski-Górecki]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sat, Mar 17, 2018 at 10:19:22AM +0100, Giulio wrote:
> |Hello,
> i need to run some simple windows applications that should run on ReactOS
> that compared to Windows has the advantage to be open source and very
> lightweight.
> 
> I have read
>  - https://github.com/QubesOS/qubes-issues/issues/2809
>  - 
> https://github.com/Jeeppler/QubesOS-notes/blob/master/ReactOS/Qubes-ReactOS.md
>  - 
> https://mark911.wordpress.com/2017/12/09/procedure-for-installing-newest-reactos-operating-system-in-stand-alone-hvm-in-qubes-os-3-2/
> 
> My HCL report is attached.
> 
> This is the command i use to create the StandaloneVM
> 
> qvm-create reactos --class StandaloneVM --property virt_mode=hvm --property
> kernel="" property memory=4096 --property maxmem=4096 --label green
> 
> If i try booting the installation ISO the the procedure fails because it
> cannot recognize the block device. (install_error.png)
> If i convert the VirtualBox image a similar error occur during boot.
> (virtualbox_error.png)
> 
> Is there someway i can change the device type in HVM? i.e. set it as an IDE
> device? I tried also installing Windows XP and it failed for a related
> reason.

I've tried that already and it doesn't help (you exchange disk not found error
for crashing installation). This may be related to *much* newer qemu
version in Qubes 4.x, than was used in Qubes 3.x, apparently devices
emulated there are not supported by ReactOS drivers.

But, ReactOS live image seems to work much better.

- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlqoDHAACgkQ24/THMrX
1yzpjgf/Zp0TKl3RHFJ1G4PLjIz/vlgdgOYJtI2mtYl4e/vvhbQH3arH93Jy7qzu
hXJkTGWlfTcaeIlJIFIqXOabRc++e0Q4/adp9XPYNazamRJb/BHMRnCwNTwZrl4L
5TyBB483HBBaXkRHUzBRxawfIqfKxPqG7rP7KJQMNbm4N3J2GBNHawintyj2hSEJ
Envau4J7wSzWaPlpaBD820j1EO2qzdgq8jANf+gCdJg5THcpWAXElzUzU4ulIM6M
BTfcsHdU+iQff0GUL8IV+Axec8+nW85iPhEvrNs5O6Ffxp/ETVp/3/pYMEi52ETv
XX0813yWsB4eckrWstnrOy2zpDRQxw==
=Wodv
-END PGP SIGNATURE-

-- 
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/20180318152707.GH8712%40mail-itl.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Failed to start Qubes OS daemon

[Marek Marczykowski-Górecki]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sun, Mar 18, 2018 at 01:22:36AM -0700, qubel...@gmail.com wrote:
> After trying to restore one windows-7 appvm backup(R3) from external usb 
> drive(restore failed), I cant start no sys-net, no other appvms after that. 
> Present time I have R4 on my laptop(Lenovo x1 carbon 4th gen). No Qubes GUIs 
> doesn't work related qubes itself(e.x Create Qubes VM,Restore Backup etc). 
> "Systemctl status qubesd.service" command gives me answer - Qubes OS daemon 
> loaded but not active.Failed to start Qubes OS daemon. What to do? 

Try running `sudo systemctl status qubesd.service`, you should see more
details about the reason for failed startup.

- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlqoCSMACgkQ24/THMrX
1yyS9Af/QGINuOyCYkbgVPfV34K2tklADIVgOqdNudG8Gh3WtLP3T0+2R4nf+rUE
6BaRPSqs/ChWPSaF5vftCVHIZqCzKAq4xxEnZ+PCcMOtBiCiw6wyZTGCpN4ThNBe
/uiJhre1wvFdF2TeHobFeA1gK+v3290gnCmt0qfdK0CykmJnJJlGkkFFhSnZYedB
cECKd6A+o6Ozs4oDPzh4KgAEAQm/oV9hxvQgpUXX8qMr6nBMSvlJSW+dyWQ2ZRPi
vV/GG835v+nnxhwfpgN3QkAorcJw07l4LRAnTC/DBReK2WaPVgsAlk66vGTPHLgV
4aZ3IxaX2qDC/yYAKjt2/TiNUtaT1Q==
=S0jV
-END PGP SIGNATURE-

-- 
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/20180318151302.GG8712%40mail-itl.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] using non-default dispvms in 4.0

[Marek Marczykowski-Górecki]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Thu, Sep 28, 2017 at 05:55:39PM -0700, Joshua Thayer wrote:
> Hi, I'm trying to use non-default disposable VMs in Qubes 4.0 and
> running in to problems. My dom0 and AppVM templates are up to date with
> the testing repos as of today.
> 
> My understanding from reading documentation and various mailing list
> threads is that in Qubes 4.0 it should be possible to specify a template
> to use when using disposable VMs using a syntax like:
> 
>     $ qvm-open-in-vm '$dispvm:kitten-dvm' ./cute-kitten.jpg
> 
> Assuming a VM named `kitten-dvm` exists on your system, and it has its
> `template_for_dispvms` pref set to True via `qvm-prefs`, and the
> appropriate policy is set in `/etc/qubes-rpc/policy/qubes.OpenInVM`...
> in this case:
> 
>     $anyvm '$dispvm:kitten-dvm' allow
> 
> However, I consistently get "Request refused" when running the example
> `qvm-open-in-vm` command above even when using the target_vmname
> `$dispvm:fedora-25-dvm`.
> 
> Any help understanding how to use the new-style dispvm specification
> would be appreciated!

See journalctl in dom0, you'll find details about the reason for the request
refused.

- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlqoCBkACgkQ24/THMrX
1yyRDQf/S4zlKBLiIg91CDQRPm4dlYmwYy6sT9aJDZl13IFAKqbU4wdLVA4XpQ2H
bpa03IHPq1m+MxQXmhPfMnpnUYDI/cQE8UGjFW8girAqoJ6vSntp3OK3B3glh6MH
3ZAa+HS73uE8FqyBj6cKGjej91EEbPWZMVkrqC/lgbxVhFLXZv2XYKfq4GnE18oT
v9Mkkirashi7GsGswV8CNcB3w4IqrlPeiEEn3QAbasnC9UzW0NA6nLwMe7igU5Bk
1WLs5NRxawNkINuPYD3caVKPAMF7baLdmJzg0wl6F8LfZ1998U5D4j/STCLXJeoT
KST8GbgkbRV8bOXEG5HyuaqeZnxtGA==
=algA
-END PGP SIGNATURE-

-- 
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/20180318150836.GF8712%40mail-itl.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes 4.0-rc5 freez during configuration

['awokd' via qubes-users]

On Sun, March 18, 2018 2:05 pm, Dominique St-Pierre Boucher wrote:
> Hello, I tried to install Qubes 4.0-rc5 on my laptop. It freezes during
> the configuration phase. Mouse stop responding, unable to switch screen.
> Any idea?

Is it freezing on the first template it tries to set up, or at the network
configuration? If network configuration, you can try to temporarily
disable your wifi card (either in your UEFI or pulling it) for the
install, then add it back later.

-- 
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/a662ceec8be39a5e61800eb162202249.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes 4.0-rc5 freez during configuration

[fepitre]

Le dimanche 18 mars 2018 15:18:50 UTC+1, Dominique St-Pierre Boucher a écrit :
> On Sunday, March 18, 2018 at 10:16:30 AM UTC-4, Frédéric Pierret (fepitre) 
> wrote:
> > Is it related to this: https://github.com/QubesOS/qubes-issues/issues/3198 ?
> 
> unfortunately no, it freezes in the setting up networking phase...

To be sure this is not the same strange phenomena, try to boot the setup with 
rd.driver.blacklist=nouveau nouveau.modeset=0 video=vesa:off

-- 
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/2328b078-8dc3-4d9c-9667-bc46df1abf51%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes 4.0-rc5 freez during configuration

[Dominique St-Pierre Boucher]

On Sunday, March 18, 2018 at 10:16:30 AM UTC-4, Frédéric Pierret (fepitre) 
wrote:
> Is it related to this: https://github.com/QubesOS/qubes-issues/issues/3198 ?

unfortunately no, it freezes in the setting up networking phase...

-- 
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/a9404cb2-af31-438b-8746-9b9c34d9820b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes 4.0-rc5 freez during configuration

[fepitre]

Is it related to this: https://github.com/QubesOS/qubes-issues/issues/3198 ?

-- 
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/323273ba-8562-440e-9874-904714054722%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Qubes 4.0-rc5 freez during configuration

[Dominique St-Pierre Boucher]

Hello, I tried to install Qubes 4.0-rc5 on my laptop. It freezes during the 
configuration phase. Mouse stop responding, unable to switch screen. Any idea?

Dominique

-- 
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/294388f2-6db2-443d-81db-e9b4a4353ddc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Coreboot + Qubes :: Best Practises / Coreboot docs page

[799]

Sorry, last Email send in advance while writing...

Hello Rusty,

Rusty Bird  schrieb am Sa., 17. März 2018, 23:18:

SeaBIOS is nice. You can build it with CONFIG_SEABIOS_VGA_COREBOOT=y
> (might be the default now), and completely disable dynamic loading of
> any dubious option ROMs:
>
> $ build/cbfstool build/coreboot.rom add-int -i 0 -n
> etc/pci-optionrom-exec
>

When do I need to run this? After building my Coreboot ROM?
Can't this option be included in the Coreboot or SeaBIOS menuconfig?


That's incompatible with graphical mode GRUB, but you can simply
> change GRUB_TERMINAL_OUTPUT from "gfxterm"[1] to "console"[2] in
> /etc/default/grub and rerun 'grub2-mkconfig -o /boot/grub2/grub.cfg'.
>

I am already using the console setting in my grub installation.
Can I still boot from a USB stick which has graphical boot enabled?


You might also enjoy HEADS.
> https://github.com/osresearch/heads


Thanks, looks very interesting, but as far as I understand I don't need
Seabios when I am running Heads?
Is somebody already using heads? From the website it seems that it is not
that easy to install and maybe still under development?

[799]

-- 
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/CAJ3yz2sJovy_hWYNBEcdng0ZJvOO1bJHb8cJYPhrk86TM7NP1Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Coreboot + Qubes :: Best Practises / Coreboot docs page

[799]

Hello Rusty,

Rusty Bird  schrieb am Sa., 17. März 2018, 23:18:

>
> SeaBIOS is nice. You can build it with CONFIG_SEABIOS_VGA_COREBOOT=y
> (might be the default now), and completely disable dynamic loading of
> any dubious option ROMs:
>
> $ build/cbfstool build/coreboot.rom add-int -i 0 -n
> etc/pci-optionrom-exec
>

When do I need to run this?
After I

>
> That's incompatible with graphical mode GRUB, but you can simply
> change GRUB_TERMINAL_OUTPUT from "gfxterm"[1] to "console"[2] in
> /etc/default/grub and rerun 'grub2-mkconfig -o /boot/grub2/grub.cfg'.
>
> IMO it actually looks better - no blindingly bright blue light at
> night, and fewer font changes during startup. I've been meaning
> (forever) to open a pull request to make this the default...
>
> You might also enjoy HEADS[3].
>
> Rusty
>
>
> 1. https://image.ibb.co/jGvCCx/grub_gfxterm.png
> 2. https://image.ibb.co/mbnsCx/grub_console.png
> 3. https://github.com/osresearch/heads
> -BEGIN PGP SIGNATURE-
>
> iQJ7BAEBCgBmBQJarZQ6XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
> ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ4NEI1OUJDRkM2MkIxMjlGRTFCMDZEMDQ0
> NjlENzhGNDdBQUYyQURGAAoJEEadePR6ryrfSKUP+NrPMBRzFqbxr7ciUg/Qnh9m
> 5ykQ4unpLU9CfiAotMDo7xJdjEZA7lwTeloVtsPL1GeVPTpYuFbkX2rxjSUQAb7H
> JSWUxTZOU2YjNjQfOz+W/Wnb0uHK9G8a5h2Pf9v8lEW5/Z3iGeTeOiSSjSc6OJjw
> Nn9ycrr2m6PvcM14OZ5DqnISdKKogUZBz+9TemhPVgSogA1RpsB9GRHgUcDermgs
> D7T62f2Bs79suOMwRDM/IZ6f4MNvsSF1pFSN+xE3JOpivx+xfAgBlc///vsz7dM2
> 05hqyVLoeCs6qHwe2PtbBlHfLdfPVoaC/kwQRDV8Obj9hP4/CFnQkRDyvN1dnwDi
> lV27YYcuWE0lgfsuRW9PwAySzyxEa4OYyDNDEJYW20lB8eTYsusDJAxxiM0X+Ba9
> pxf1FQwRoX7C4yjHU1tWb97cTPOMif07O8a5AFod9FPAwmUcwdPC/X/H3eU2CsaP
> UP5NEK81Wx1avWdTIBuvrbuPZe5Dj0dwTk0Z5TC5hbKUMYxczDLuFnh/1TnViSRo
> 4pOUNfXx4Blg4elUrTXASOnPQnZA5X2snVhkQrmqi3nAyRztzTK6x++OqvjlF+q3
> T8YiSg66Ssi3iXUFiZlEerCfzpe0Wc+kyvVXh9sM0NhwBs6hErLpmSlLD3785Bxr
> P5Lc8JEJpNcnac70K0c=
> =L0qD
> -END PGP SIGNATURE-
>
>

-- 
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/CAJ3yz2s_uDpfYWQvQ2DgwpWR4GUeeKjHZLsu61Mo1UXKhc9NBg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] DispVM broken in 3.2? (xen-4.6.6-37)

[qubes-lists]

I used the following commands in dom0 to restore dispVM functionality: 
 

qubes-dom0-update  xen-libs-4.6.6-36.fc23.x86_64 
xen-hypervisor-4.6.6-36.fc23.x86_64 xen-runtime-4.6.6-36.fc23.x86_64 
xen-hvm-4.6.6-36.fc23.x86_64 xen-4.6.6-36.fc23.x86_64 
xen-license-4.6.6-36.fc23.x86_64

dnf downgrade xen-libs-4.6.6-36.fc23.x86_64 xen-hypervisor-4.6.6-36.fc23.x86_64 
xen-runtime-4.6.6-36.fc23.x86_64 xen-hvm-4.6.6-36.fc23.x86_64 
xen-4.6.6-36.fc23.x86_64 xen-license-4.6.6-36.fc23.x86_64


(downgrading the packages in the template was not necessary) 

-- 
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/f0a7a149-c5ed-c234-89ab-6ca26457f0d1%40riseup.net.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Failed to start Qubes OS daemon

[qubeloop]

After trying to restore one windows-7 appvm backup(R3) from external usb 
drive(restore failed), I cant start no sys-net, no other appvms after that. 
Present time I have R4 on my laptop(Lenovo x1 carbon 4th gen). No Qubes GUIs 
doesn't work related qubes itself(e.x Create Qubes VM,Restore Backup etc). 
"Systemctl status qubesd.service" command gives me answer - Qubes OS daemon 
loaded but not active.Failed to start Qubes OS daemon. What to do? 

-- 
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/1b6d1626-b9ad-4165-ac4a-bea1b4a8bd90%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.