Hi,
I am a bit lost with Qubes 4.0 RC3 ...
Before moving to 4.0, I have done my VM's backup.
How to restore them to Qubes 4.0 ?
Thx
--
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
Solved.
Not sure if it was relevant but since the most recent Whonix updates this has
gone back to normal.
Thanks to all.
--
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
Apparently creating a post for help is like replacing something you've lost,
only to find it immediately after replacing it.
Here's the solution to this problem:
Apparently Emacs will trick you into thinking you've changed the
epa-gpg-program variable, but it won't actually honor that change
On Sunday, January 28, 2018 at 4:17:10 AM UTC+1, Jo wrote:
> Yes, im running the backups trough sys-usb-> extern ssd.The sys-usb is
> the default one from the installation.Im doing a complete new setup, for
> the very same reasons you mentioned.
>
> Updating (and enabling testingrepos) was the
On Saturday, January 27, 2018 at 3:45:28 PM UTC+1, Yoganandam Marava wrote:
> by adding forward rules at sysfirewall we can ping each other VM through ip
> address but not using VM name.
> Is this some thing possible with Qubes 4? I am naive in networking.please
> suggest if there is a way?
>
>
Yes, im running the backups trough sys-usb-> extern ssd.The sys-usb is
the default one from the installation.Im doing a complete new setup, for
the very same reasons you mentioned.
Updating (and enabling testingrepos) was the very first thing i did.
Im using coreboot+seabios and
On Sunday, January 28, 2018 at 2:03:35 AM UTC+1, bill...@gmail.com wrote:
> On Saturday, January 27, 2018 at 6:23:54 PM UTC-5, Yuraeitha wrote:
> > On Friday, January 26, 2018 at 8:45:43 PM UTC+1, bill...@gmail.com wrote:
> > > Thanks so much for your reply and your help. I installed using legacy
On Sunday, January 28, 2018 at 3:17:05 AM UTC+1, Jo wrote:
> hello guys,
>
> i played a bit with rc3 and came across the following bugs:
>
>
> qvm-backup/restore results in a complete system-shutdown, which is very
> annoying.Using the gui/ qubes-manager instead of the terminal makes no
>
On Sunday, January 28, 2018 at 10:30:47 AM UTC+8, awokd wrote:
> On Sun, January 28, 2018 2:13 am, xxx wrote:
> > I burned the ISO to USB stick then started to install Qubes but got the
> > following:
> >
> >
> > [0.093375] ACPI Error: [\SB_.PCIO.XHC_.RHUB.HS11] Namespace lookup
> > failure,
On Sun, January 28, 2018 2:33 am, Yuraeitha wrote:
>
> Awkward same-time posting x)
> But listen to awokd, he has more experience than I do.
Not that much more! Unfortunately, on these boot issues most come down to
trial and error like you said...
--
You received this message because you are
On Sunday, January 28, 2018 at 3:30:47 AM UTC+1, awokd wrote:
> On Sun, January 28, 2018 2:13 am, joeh9...@gmail.com wrote:
> > I burned the ISO to USB stick then started to install Qubes but got the
> > following:
> >
> >
> > [0.093375] ACPI Error: [\SB_.PCIO.XHC_.RHUB.HS11] Namespace lookup
On Sunday, January 28, 2018 at 3:13:47 AM UTC+1, joeh...@gmail.com wrote:
> I burned the ISO to USB stick then started to install Qubes but got the
> following:
>
> [0.093375] ACPI Error: [\SB_.PCIO.XHC_.RHUB.HS11] Namespace lookup
> failure, AE_NOT_FOUND (20170531/dswload-210)
> [
On Sun, January 28, 2018 2:13 am, joeh9...@gmail.com wrote:
> I burned the ISO to USB stick then started to install Qubes but got the
> following:
>
>
> [0.093375] ACPI Error: [\SB_.PCIO.XHC_.RHUB.HS11] Namespace lookup
> failure, AE_NOT_FOUND (20170531/dswload-210) [0.093383] ACPI
>
hello guys,
i played a bit with rc3 and came across the following bugs:
qvm-backup/restore results in a complete system-shutdown, which is very
annoying.Using the gui/ qubes-manager instead of the terminal makes no
difference.
I will have a look into it/ try to fix it in my spare time these
I burned the ISO to USB stick then started to install Qubes but got the
following:
[0.093375] ACPI Error: [\SB_.PCIO.XHC_.RHUB.HS11] Namespace lookup failure,
AE_NOT_FOUND (20170531/dswload-210)
[0.093383] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog
(20170531/psobject-252)
Just a heads-up for anyone else reading this thread who may want to try this
too and is not aware of this pitfall, a warning before trying. Any mistakes
done in the scripts can make the template unable to start applications. For
example even if it can boot-up, applications may not start.
So
On Wednesday, January 24, 2018 at 8:32:24 PM UTC+1, Chris Laprise wrote:
> On 01/24/2018 10:55 AM, Yuraeitha wrote:
>
> >
> > All 3 suggestions are you guys brought up are really intriguig, I'm pretty
> > excited about this, these ideas are excellent, even better than I hoped for.
> >
> > I'm
On Saturday, January 27, 2018 at 6:23:54 PM UTC-5, Yuraeitha wrote:
> On Friday, January 26, 2018 at 8:45:43 PM UTC+1, bill...@gmail.com wrote:
> > 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
I would ask on the Whonix Forum. https://forums.whonix.org/
--
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
On Wednesday, January 24, 2018 at 3:30:11 AM UTC+1, Kyle Breneman wrote:
> >Note that those directions are about upgrading *templates*, not dom0.
>
> >Dom0 should generally stay at the fedora release it started at,
>
> >otherwise you are asking for compatibility trouble.
>
>
> Thanks for that
No one offered yet? Must be someone out there that keep some old
desktops/laptops laying around.
Can an increase in subscription based donations be of use? For example if, say,
10 people each donate 10 euro (or alternatively expand any current donation
subscription with 10 euro), then it
On Friday, January 26, 2018 at 8:45:43 PM UTC+1, bill...@gmail.com wrote:
> 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
> On 01/27/18 22:12, haaber wrote:
>> Hello, all of my appVMs run on random times. I reall having had this
>> issue on Q3.2 but it comes back on Q4.3 - I forgot the solution in the
>> meantime. Qumes-Manager indicates sys-net is ClockVM. How do I configure
>> all AppVM's to fetch time there??
I downloaded and installed KDE today, and it went fine. Now I am upgrading the
default fedora-25 template to fedora-26. I've gone through the downloading and
all, and am now at the "change default template" part.
So... I click on Applications-> System Tools -> Qubes Global Settings and
On 01/27/18 22:12, haaber wrote:
Hello, all of my appVMs run on random times. I reall having had this
issue on Q3.2 but it comes back on Q4.3 - I forgot the solution in the
meantime. Qumes-Manager indicates sys-net is ClockVM. How do I configure
all AppVM's to fetch time there?? Thank you !!
On Sat, 27 Jan 2018, beso wrote:
> On Saturday, January 27, 2018 at 4:33:47 PM UTC+2, awokd wrote:
> > On Sat, January 27, 2018 2:20 pm, beso wrote:
> >
> > >> On Sat, January 27, 2018 6:31 am, beso wrote:
> > >>
> > >>> ERROR: Device attach failed: /usr/lib/qubes/usb-import: 37: [:
> > >>>
Hello, all of my appVMs run on random times. I reall having had this
issue on Q3.2 but it comes back on Q4.3 - I forgot the solution in the
meantime. Qumes-Manager indicates sys-net is ClockVM. How do I configure
all AppVM's to fetch time there?? Thank you !! Bernhard
--
You received this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, Jan 26, 2018 at 11:37:31PM -0600, Andrew David Wong wrote:
> 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
On Thursday, 25 January 2018 19:28:58 CET 'awokd' via qubes-users wrote:
> Resuming working my way through splitting up the documentation now that
> the 3.2 vs. 3.3 question has been mostly settled. Some general questions:
Awesome!
I was thinking about the qubes docs when I saw a wiki that had a
That was it! Thanks, folks. Problem is solved.
billo
--
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
workarounds, fixes: https://github.com/QubesOS/qubes-issues/issues/3486
--
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.
On 01/27/2018 12:26 PM, billol...@gmail.com wrote:
> I recently installed Qubes 4 rc3 on my Dell laptop, and it seems to working
> well. However, there's a little bit of a problem with my networking. It
> comes up fine when I reboot the machine, and runs like a charm... but when I
> close the
I recently installed Qubes 4 rc3 on my Dell laptop, and it seems to working
well. However, there's a little bit of a problem with my networking. It comes
up fine when I reboot the machine, and runs like a charm... but when I close
the laptop lid, networking turns off, and I can't figure out
I installed Qubes 4 rc3 yesterday and am having a great time exploring it. I'm
kind of a KDE person, so I installed KDE, and it works pretty much like a
charm, though I'm having a bit of an issue personalizing it.
If anybody can give me some aid, I'd appreciate it.
First, while KDE seems to
On Sat, January 27, 2018 3:00 pm, beso wrote:
> On Saturday, January 27, 2018 at 4:33:47 PM UTC+2, awokd wrote:
>
>> On Sat, January 27, 2018 2:20 pm, beso wrote:
>>
>>
On Sat, January 27, 2018 6:31 am, beso wrote:
> ERROR: Device attach failed: /usr/lib/qubes/usb-import: 37: [:
Yeh, the anon-whonix app vm is routed through sys-whonix properly. I haven't
changed that from default.
I do route most non-whonix app vms through a vpn in a proxy vm but that all
works as it should.
Both systems have worked independently and as expected for months.
Checking today some IP
On Saturday, January 27, 2018 at 4:33:47 PM UTC+2, awokd wrote:
> On Sat, January 27, 2018 2:20 pm, beso wrote:
>
> >> On Sat, January 27, 2018 6:31 am, beso wrote:
> >>
> >>> ERROR: Device attach failed: /usr/lib/qubes/usb-import: 37: [:
> >>> Illegal
> >>> number: stash: printf: I/O error.
>
by adding forward rules at sysfirewall we can ping each other VM through ip
address but not using VM name.
Is this some thing possible with Qubes 4? I am naive in networking.please
suggest if there is a way?
Thanks
--
You received this message because you are subscribed to the Google Groups
On Sat, January 27, 2018 2:20 pm, beso wrote:
>> On Sat, January 27, 2018 6:31 am, beso wrote:
>>
>>> ERROR: Device attach failed: /usr/lib/qubes/usb-import: 37: [:
>>> Illegal
>>> number: stash: printf: I/O error.
>>> How to solve this problem?
>>>
> Sorry,
No trouble!
> Qubes - 3.2;
>
On Saturday, January 27, 2018 at 3:58:35 PM UTC+2, awokd wrote:
> On Sat, January 27, 2018 6:31 am, beso wrote:
> > ERROR: Device attach failed: /usr/lib/qubes/usb-import: 37: [: Illegal
> > number: stash: printf: I/O error.
> > How to solve this problem?
>
> Not to sound cranky, but can you
On Sat, January 27, 2018 11:46 am, code9n wrote:
> Running the WhonixCheck from the default anon-whonix app vm in the Qubes
> manager list; the fail warning basically says:
>
> SocksPort test [fails]. ... (curl exit code: [7] - [failed to connect to
> host])
>
> The browser - anon-whonix app vm
Am Freitag, 26. Januar 2018 19:05:37 UTC+1 schrieb Yuraeitha:
> Also on my Qubes 3.2. Win7 on Qubes 4, I can easily transfer files in and out
> of Win7, and everything else Qubes related "seems" to work, except I have no
> internet connection. Just a heads up, and does anyone else experience
Running the WhonixCheck from the default anon-whonix app vm in the Qubes
manager list; the fail warning basically says:
SocksPort test [fails]. ... (curl exit code: [7] - [failed to connect to host])
The browser - anon-whonix app vm (default)/Tor browser - opens like normal to
the Whonix page
43 matches
Mail list logo
