Re: [qubes-users] Issues with Qubes 4.0 on Lenovo T450s

2018-04-29 Thread maurice 
Thank you all!

I've managed to disable the shortcut on xfce! Now I can finally use FF in 
private more :)
Didn't find anything related with the ACPI errors though. I think its best if I 
can raise an issue in github?



April 29, 2018 7:38 PM, "awokd"  wrote:

> On Sat, April 28, 2018 8:15 pm, maur...@disroot.org wrote:
> 
>> Hi Everyone.
>> 
>> Whenever I try to get to private more in FF by pressing ctrl+shift+p all
>> my VMs get paused. Is there a reason for this? Is it possible to disable
>> it? Whenever that happen I have to manually select each VM and resume it,
>> which is kind of annoying.
> 
> There is a way to customize the XFCE keyboard shortcuts, but I can't
> remember how exactly. Think it involves editing a file. Try searching this
> mailing list- I like to use
> https://www.mail-archive.com/qubes-users@googlegroups.com.
> 
>> Qube manager is no longer started by default like in version 3.2, instead
>> I got now an icon on the top right corner that allows to invoke
>> operations on the running VMs. But some of the VMs in there are show an
>> inconsistent state (I'm only allow to check the logs, set the preferences
>> or kill it and not shut them down as with some of the displayed VMs)
>> there's a cursor looping for the inconsistent VMs. Is there a way to fix
>> this?
> 
> https://github.com/QubesOS/qubes-issues/issues/3660
> 
>> Also Qube manager shows all VMs and not only the running ones, is
>> there an option to show only the VMs that are running? Qube Manager
>> doesn't refresh the state of the VMs as it happened in Qubes 3.2. Instead
>> I have to manually hit refresh whenever I want to check when a VM has
>> stopped or started. Is there a way one could have check the state of the
>> VMs on Qube manager as it happened on version 3.2?
> 
> Qube Manager was originally not going to be included in 4.0 and got
> re-added relatively late so it still has some display issues. To refresh a
> single VM, you can click on a different one then back on that VM. It's a
> little faster than refreshing them all.
> 
>> During the boot and before unlock the LuKS volume I'm getting a lot of
>> ACPI errors regarding Namespace lookup failure:
> 
> I get these too but they don't seem to hurt anything. Try searching
> https://github.com/QubesOS/qubes-issues/issues to see if there's more info
> in there.
> 
>> Shutdown is also taking an huge amount of time to complete spending lots
>> of time waiting for the disk to be ready.
> 
> Try manually shutting down any AppVMs you have running first, before
> shutting down Qubes.

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

Re: [qubes-users] Issues with Qubes 4.0 on Lenovo T450s

2018-04-29 Thread Ivan Mitev 


On 04/29/2018 08:38 PM, 'awokd' via qubes-users wrote:
> On Sat, April 28, 2018 8:15 pm, maur...@disroot.org wrote:
>> Hi Everyone.
>>
> 
> 
>> Whenever I try to get to private more in FF by pressing ctrl+shift+p all
>> my VMs get paused. Is there a reason for this? Is it possible to disable
>> it? Whenever that happen I have to manually select each VM and resume it,
>> which is kind of annoying.
> 
> There is a way to customize the XFCE keyboard shortcuts, but I can't
> remember how exactly. Think it involves editing a file. Try searching this
> mailing list- I like to use

For XFCE:

Qubes menu -> System Tools -> Keyboard -> Application Shortcuts

Alternatively, edit the following file but the gui above is more
straightforward:

$HOME/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-keyboard-shortcuts.xml

> https://www.mail-archive.com/qubes-users@googlegroups.com/.
> 
>> Qube manager is no longer started by default like in version 3.2, instead
>> I got now an icon on the top right corner that allows to invoke
>> operations on the running VMs. But some of the VMs in there are show an
>> inconsistent state (I'm only allow to check the logs, set the preferences
>> or kill it and not shut them down as with some of the displayed VMs)
>> there's a cursor looping for the inconsistent VMs. Is there a way to fix
>> this?
> 
> https://github.com/QubesOS/qubes-issues/issues/3660
> 
>> Also Qube manager shows all VMs and not only the running ones, is
>> there an option to show only the VMs that are running? Qube Manager
>> doesn't refresh the state of the VMs as it happened in Qubes 3.2. Instead
>> I have to manually hit refresh whenever I want to check when a VM has
>> stopped or started. Is there a way one could have check the state of the
>> VMs on Qube manager as it happened on version 3.2?
> 
> Qube Manager was originally not going to be included in 4.0 and got
> re-added relatively late so it still has some display issues. To refresh a
> single VM, you can click on a different one then back on that VM. It's a
> little faster than refreshing them all.
> 
>> During the boot and before unlock the LuKS volume I'm getting a lot of
>> ACPI errors regarding Namespace lookup failure:
> 
> I get these too but they don't seem to hurt anything. Try searching
> https://github.com/QubesOS/qubes-issues/issues to see if there's more info
> in there.
> 
>> Shutdown is also taking an huge amount of time to complete spending lots
>> of time waiting for the disk to be ready.
> 
> Try manually shutting down any AppVMs you have running first, before
> shutting down Qubes.
> 
> 

-- 
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/6f4d0850-7909-2e74-d3a7-e7f8a853c5b2%40maa.bz.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Issues with Qubes 4.0 on Lenovo T450s

2018-04-29 Thread 'awokd' via qubes-users 
On Sat, April 28, 2018 8:15 pm, maur...@disroot.org wrote:
> Hi Everyone.
>


> Whenever I try to get to private more in FF by pressing ctrl+shift+p all
> my VMs get paused. Is there a reason for this? Is it possible to disable
> it? Whenever that happen I have to manually select each VM and resume it,
> which is kind of annoying.

There is a way to customize the XFCE keyboard shortcuts, but I can't
remember how exactly. Think it involves editing a file. Try searching this
mailing list- I like to use
https://www.mail-archive.com/qubes-users@googlegroups.com/.

> Qube manager is no longer started by default like in version 3.2, instead
> I got now an icon on the top right corner that allows to invoke
> operations on the running VMs. But some of the VMs in there are show an
> inconsistent state (I'm only allow to check the logs, set the preferences
> or kill it and not shut them down as with some of the displayed VMs)
> there's a cursor looping for the inconsistent VMs. Is there a way to fix
> this?

https://github.com/QubesOS/qubes-issues/issues/3660

> Also Qube manager shows all VMs and not only the running ones, is
> there an option to show only the VMs that are running? Qube Manager
> doesn't refresh the state of the VMs as it happened in Qubes 3.2. Instead
> I have to manually hit refresh whenever I want to check when a VM has
> stopped or started. Is there a way one could have check the state of the
> VMs on Qube manager as it happened on version 3.2?

Qube Manager was originally not going to be included in 4.0 and got
re-added relatively late so it still has some display issues. To refresh a
single VM, you can click on a different one then back on that VM. It's a
little faster than refreshing them all.

> During the boot and before unlock the LuKS volume I'm getting a lot of
> ACPI errors regarding Namespace lookup failure:

I get these too but they don't seem to hurt anything. Try searching
https://github.com/QubesOS/qubes-issues/issues to see if there's more info
in there.

> Shutdown is also taking an huge amount of time to complete spending lots
> of time waiting for the disk to be ready.

Try manually shutting down any AppVMs you have running first, before
shutting down Qubes.


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

[qubes-users] Issues with Qubes 4.0 on Lenovo T450s

2018-04-28 Thread maurice 
Hi Everyone.

I have a lenovo T450s and I've finally updated my Qubes 3.2 to 4.0. and I was 
finally able to get this version working (in the process I was forced to switch 
to enable legacy boot instead of UEFI since apparently Qubes 4.0 doesn't 
support it as its predecessor Q3.2 version for lenovo laptops)
However, despite the apparent success I'm still facing some issues, reason why 
I'm addressing this to the community in the hope of getting some clarification.
So these are the main issues I'm currently facing right now:

Whenever I try to get to private more in FF by pressing ctrl+shift+p all my VMs 
get paused. Is there a reason for this? Is it possible to disable it? Whenever 
that happen I have to manually select each VM and resume it, which is kind of 
annoying.

Qube manager is no longer started by default like in version 3.2, instead I got 
now an icon on the top right corner that allows to invoke operations on the 
running VMs. But some of the VMs in there are show an inconsistent state (I'm 
only allow to check the logs, set the preferences or kill it and not shut them 
down as with some of the displayed VMs) there's a cursor looping for the 
inconsistent VMs. Is there a way to fix this? Also Qube manager shows all VMs 
and not only the running ones, is there an option to show only the VMs that are 
running?
Qube Manager doesn't refresh the state of the VMs as it happened in Qubes 3.2. 
Instead I have to manually hit refresh whenever I want to check when a VM has 
stopped or started. Is there a way one could have check the state of the VMs on 
Qube manager as it happened on version 3.2? 

During the boot and before unlock the LuKS volume I'm getting a lot of ACPI 
errors regarding Namespace lookup failure:

[ 1.726445] ACPI Error: [_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND 
(20170728/psargs-364)
[ 1.726525] ACPI Error: Method parse/execution failed _PR.CPU1._CST, 
AE_NOT_FOUND (20170728/psparse-550)
[ 1.726609] ACPI Error: [_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND 
(20170728/psargs-364)
[ 1.726739] ACPI Error: Method parse/execution failed _PR.CPU2._CST, 
AE_NOT_FOUND (20170728/psparse-550)
[ 1.726932] ACPI Error: [_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND 
(20170728/psargs-364)
[ 1.727136] ACPI Error: Method parse/execution failed _PR.CPU3._CST, 
AE_NOT_FOUND (20170728/psparse-550)
[ 1.727332] ACPI Error: [_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND 
(20170728/psargs-364)
[ 1.727517] ACPI Error: Method parse/execution failed _PR.CPU4._CST, 
AE_NOT_FOUND (20170728/psparse-550)
[ 1.727709] ACPI Error: [_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND 
(20170728/psargs-364)
[ 1.727896] ACPI Error: Method parse/execution failed _PR.CPU5._CST, 
AE_NOT_FOUND (20170728/psparse-550)
[ 1.728105] ACPI Error: [_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND 
(20170728/psargs-364)
[ 1.728290] ACPI Error: Method parse/execution failed _PR.CPU6._CST, 
AE_NOT_FOUND (20170728/psparse-550)
[ 1.728483] ACPI Error: [_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND 
(20170728/psargs-364)
[ 1.728667] ACPI Error: Method parse/execution failed _PR.CPU7._CST, 
AE_NOT_FOUND (20170728/psparse-550)

Is there any way one could resolve this?

Shutdown is also taking an huge amount of time to complete spending lots of 
time waiting for the disk to be ready. Any idea how one can improve it?
Thank you all for the fantastic work!

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