Yes I do have the same issue.
It seems it was mentioned a few times on the mailing lists but no concrete
solutions were found. People suggested a magic bullet being this command:
sudo dpkg-reconfigure locales
However this command exits prematurely due to the localesall (sp?) package
being
After testing again is seems as if that does fix the shutdown problem.
I'm shutting down through a dom0 `shutdown now`. Perhaps this isn't allowing
Qubes to shutdown the VM properly on it's own?
On December 10, 2016 8:37:04 PM PST, Andrew David Wong
wrote:
>-BEGIN PGP
On 04/22/2017 03:21 PM,
craig.g.jes...@gmail.com wrote:
> On Wednesday, April 19, 2017 at 1:35:06 PM UTC-7,
> craig.g...-re5jqeeqqe8avxtiumw...@public.gmane.org wrote:
>> I am having at boot problem with my Qubes OS 3.2. When I boot up I enter
>> the disk password and the boot process continues
dom0's
/boot/efi/EFI/qubes/xen.cfg.
You can do this from a liveUSB or another OS if you do not have the
ability to edit it from within Qubes.
Credit to mnords on IRC for the solution.
Andrew Morgan
--
You received this message because you are subscribed to the Google Groups
"qubes-u
ss ESC in the Qubes-logo booting process to show
more detailed information, as well as removing the 'quiet' entry in the
kernel arguments on boot (you can do this by pressing 'e' at the
grub/bootup screen, press right arrow-key to see the rest of the arguments).
Andrew Morgan
--
You received this
this?
Andrew Morgan
--
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 q
instructions to update the provided Fedora 23 template since Fedora 23 is
> end-of-life.
>
> Any help greatly appreciated.
>
> Thanks,
> Greg
>
Does the `lsblk` command show anything different when the device is
attached versus not attached in the fedora vm?
Andrew
Hey all,
Trying to update my Ubuntu Xenial template, but hitting following
dependency issue. You can see my attempts to resolve this to no avail:
...
Reading state information... Done
3 packages can be upgraded. Run 'apt list --upgradable' to see them.
user@xenial-desktop:~$ sudo apt list
ne 3.1
> issues in order to help us determine which issues had to be migrated
> to Milestone 3.2 and which could be closed. Thank you both!
>
>
Yep, they've been super helpful on the mailing list in resolving user
issues, including my own. Thanks guys!
Andrew Morgan
--
You receiv
it?
Andrew Morgan
--
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 q
have validation that prevents going forward
> with that username). :)
>
That sounds like a bad bug, but one that can be remedied pretty easily.
I've created an issue in QubesOS/qubes-issues for this here:
https://github.com/QubesOS/qubes-issues/issues/2793
Andrew Morgan
--
You received this
-u root sys-vpn "/rw/config/rc.local"
Change sys-vpn to the name of your VPN VM.
This all assumes you followed the iptables and CLI scripts section of
the Qubes VPN docs: https://www.qubes-os.org/doc/vpn/
That section also sets up VPN as soon as your VPN VM launches and
prevents any non-V
for helping with testing and debugging.
Andrew Morgan
On August 23, 2017 2:02:36 PM PDT, djeff...@linuxfoundation.org wrote:
>On Wednesday, August 23, 2017 at 2:38:11 PM UTC-6, Andrew Morgan wrote:
>> I did perform a dom0 update a few days ago, but I think this behavior
>only started afte
I did perform a dom0 update a few days ago, but I think this behavior only
started after restarting Qubes fully.
Do you have security-testing enabled in dom0? Perhaps it is an issue with an
unstable kernel/xen version.
Andrew Morgan
On August 23, 2017 11:00:56 AM PDT, djeff
On 08/29/2017 12:22 AM, Andrew Morgan wrote:
> On 08/28/2017 10:27 PM, Reg Tiangha wrote:
>> FYI, trying to view the qubes-devel Google Group on a web browser
>> currently displays this message:
>>
>> Banned Content Warning
>> The group that you are attempti
want to do... Also
what about the old kernels? Do they matter at all since kernels are
typically provided by dom0 anyways?
Thanks,
Andrew Morgan
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop rece
too much on it.
>
> Any ideas on this problem?
>
>
Would it be similar to this issue?
https://groups.google.com/d/msg/qubes-users/LkP-6ORGwME/AQLyuqvnCAAJ
Andrew Morgan
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To u
version, such as 4.0+ within a Qube?
Thanks,
Andrew Morgan
--
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.co
isn't launching. I have to manually launch everything from Qubes
Manager -> Run command in VM -> gnome-terminal.
Is there a way I can debug this further?
Thanks,
Andrew Morgan
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To
On 04/09/2018 12:52 PM, 'Neelix' via qubes-users wrote:
> Hi Andrew,
>
>
> Did you also make a back up of the templates? Or did you installed the
> same applications on your new templates?
>
>
>
>
> On 04/09/2018 05:52 AM, Andrew Morgan wrote:
>> Hey t
On 04/08/2018 11:59 PM, Drew White wrote:
> On Monday, 9 April 2018 13:52:34 UTC+10, Andrew Morgan wrote:
>> Hey there,
>>
>> The upgrade to Qubes 4.0 was mostly painless, with a few things needed
>> to be set up and worked-around here and there. I did do a backup from
21 matches
Mail list logo