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

-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

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

-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 >  

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

-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

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

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

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

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

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

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

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

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

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

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] Re: Qubes 4.0-rc5 freez during configuration

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

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

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

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

-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

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

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

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

-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

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

-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

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

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: > > >

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

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 >

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

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

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

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 > >

[qubes-users] Failed to start Qubes OS daemon

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

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

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

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

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

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

-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

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

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

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

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

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

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,

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

> 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

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

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