On Thursday, January 25, 2018 at 1:34:03 AM UTC-8, Vít Šesták wrote:
> Dave, why you start a new VM and not just use a loopback? Is the reason
> sharing apps from multiple VMs? If si, you are at least significantly
> weakening isolation. Maybe you are not keeping any, not sure. X11 was not
> des
ERROR: Device attach failed: /usr/lib/qubes/usb-import: 37: [: Illegal number:
stash: printf: I/O error.
How to solve 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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2018-01-26 05:14, awokd wrote:
> On Fri, January 26, 2018 3:36 am, Andrew David Wong wrote:
>> On 2018-01-25 12:28, awokd wrote:
>>> 1. Should I open an issue for tracking and move the discussion
>>> over there? Move to qubes-devel? Keep here?
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2018-01-26 05:38, 'awokd' via qubes-users wrote:
> On Fri, January 26, 2018 9:22 am, Alex Dubois wrote:
>> On Friday, 26 January 2018 03:36:33 UTC, Andrew David Wong
>> wrote:
>
>> Happy to contribute. maybe we can have a direct conversation so
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2018-01-26 09:37, Marek Marczykowski-Górecki wrote:
> Hi,
>
> Manual testing of installation is a time consuming job, so I was looking
> for some tool to automate it. And found one:
>
> http://open.qa/
>
> This works by launching the system und
>
> If you have the key files on disk, use --import:
> $ gpg2 --import qubes-master-signing-key.asc
> $ gpg2 --import qubes-release-3-signing-key.asc
>
> Then use --edit-key to set trust level to 4 on master key:
> $ gpg2 --edit-key 36879494
> gpg> trust
> gpg> save
>
> Then check that master<>r
Thanks for the support! Altough right now I'm not planning on using a VPN so I
might look at that in the future.
I'm sorry I probably still can't understand how updates work in Qubes: I set
the updateVM to sys-firewall as you said, I tried running sudo yum update in
the fedora template and it st
Thanks so much for your reply and your help. I installed using legacy boot and
it worked fine -- in fact, I'm responding from "untrusted firefox" right now!
I don't know if qubes comes up in the grub menu yet. I just got this
installed, and ran it from the BIOS boot sequence Legacy-USB option
On Fri, January 26, 2018 6:05 pm, Yuraeitha wrote:
> On Friday, January 26, 2018 at 6:47:14 PM UTC+1, goo...@itrichter.de
> wrote:
>
>> Am Samstag, 6. Januar 2018 20:28:21 UTC+1 schrieb goo...@itrichter.de:
>>
>> Addition: In order to get a stable Windows 7, I had to disable memory
>> balancing AN
On Tuesday, January 2, 2018 at 10:27:58 AM UTC+1, Roy Bernat wrote:
> Hi All
>
> i am trying to understand if someone succeeded to install win7/10 on qubes 4.
> R
https://github.com/QubesOS/qubes-installer-qubes-os-windows-tools
Seems like the Windows-Tools has been in-active for a long time. Ex
On Friday, January 26, 2018 at 6:47:14 PM UTC+1, goo...@itrichter.de wrote:
> Am Samstag, 6. Januar 2018 20:28:21 UTC+1 schrieb goo...@itrichter.de:
> > [...]
> > Standalone Windows 7 VMs seem to work, though only without seamless GUI.
> > But I have not been able to get template-based windows VMs,
Am Samstag, 6. Januar 2018 20:28:21 UTC+1 schrieb goo...@itrichter.de:
> [...]
> Standalone Windows 7 VMs seem to work, though only without seamless GUI.
> But I have not been able to get template-based windows VMs, they always fail
> with "Cannot execute qrexec-daemon!".
Addition: In order to ge
On Friday, January 26, 2018 at 4:59:00 PM UTC+1, bill...@gmail.com wrote:
> I tried to send this question from the email address I used to subscribe to
> the user group, but it's been about two hours and it hasn't shown up. I'm
> assuming it's a Google thing, but I apologize if this question show
On Thursday, January 25, 2018 at 8:21:37 PM UTC+1, dark...@gmail.com wrote:
> Thanks for the lenghty response! Indeed the errors were python-code related,
> but it turns out the problem was in the sys-net domain not starting correctly
> because of the card reader, which was seemingly seen as a ne
On Saturday, 13 January 2018 03:58:03 UTC+1, Andrew David Wong wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> The Qubes VM Manager will be returning in Qubes 4.0-rc4, which is
> scheduled for release next week. The returning Qubes Manager will be
> slightly different from the 3.2
On Friday, January 26, 2018 at 4:59:00 PM UTC+1, bill...@gmail.com wrote:
> I tried to send this question from the email address I used to subscribe to
> the user group, but it's been about two hours and it hasn't shown up. I'm
> assuming it's a Google thing, but I apologize if this question show
I tried to send this question from the email address I used to subscribe to the
user group, but it's been about two hours and it hasn't shown up. I'm assuming
it's a Google thing, but I apologize if this question shows up twice.
So, here I go again. I'm a newbie with Qubes, but I love the idea
On Fri, January 26, 2018 9:22 am, Alex Dubois wrote:
> On Friday, 26 January 2018 03:36:33 UTC, Andrew David Wong wrote:
> Happy to contribute. maybe we can have a direct conversation so that we
> can discuss what is needed and where I feel comfortable...
Speaking only on my own behalf of course
On Fri, January 26, 2018 3:36 am, Andrew David Wong wrote:
> On 2018-01-25 12:28, awokd wrote:
>> 1. Should I open an issue for tracking and move the discussion
>> over there? Move to qubes-devel? Keep here?
>
> Please open an issue in qubes-issues.
https://github.com/QubesOS/qubes-issues/issues/3
On Thu, January 25, 2018 7:19 pm, Krišjānis Gross wrote:
>
> here it is (attached). Hope that helps!
>From the journal:
Jan 25 20:53:15 localhost.localdomain kernel: [drm] The driver support for
your hardware in this kernel version is alpha quality
Se
On Friday, 26 January 2018 03:36:33 UTC, Andrew David Wong wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On 2018-01-25 12:28, awokd wrote:
> > Resuming working my way through splitting up the documentation now
> > that the 3.2 vs. 3.3 question has been mostly settled. Some
> > g
Den torsdag den 25. januar 2018 kl. 20.17.48 UTC+1 skrev Kevin Martinsen:
> i3 has been working fine for me.
>
> Did you follow the installation instructions on
> https://www.qubes-os.org/doc/i3/? Specifically:
> $ sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing
> i3-settings-qub
22 matches
Mail list logo