Re: [qubes-users] Computer shutsoff when lid is closed when it should suspend

[zw wi]

Just tried the "systemctl suspend" in terminal again it shuts off. but now in 
journactl log it shows

"-- Reboot --
Dom0 systemd[1]: Starting Qubes suspend hooks ...
Dom0 52qubes-pause-vms[12838]: 0
Dom0 systems[1]: Started Qubes suspend hooks.

--Reboot--
Dom0 systemd[1]: qubes-suspend. Service: Unit not needed anymore. stopping"

It looks like suspend hook worked but I am not sure could it the resume hook" 
since it shuts off after exec suspend hook? 

-- 
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/77728746-f744-4433-beae-0412af9fa84c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Computer shutsoff when lid is closed when it should suspend

[zw wi]

Yes, I have that parameter in grub.cfg and regenerated but it is still a no go. 
Running "systemctl suspend" in 
 the terminal will turn off the computer, and closing the lid will produce the 
same result.

Doing "systemctl status qubes-suspend.service" shows suspend as loaded and 
inactive(dead)
Doing "journalctl -u qubes-suspend.service" shows

"Dom0 systemd[1]: starting Qubes suspend hooks ...
Dom0 systemd[1]: qubes-suspend.service: Main process exited, code=exited, 
status=203/EXEC
Dom0 systemd[1]: Failed to start Qubes suspend hooks.
Dom0 systemd[1]: qubes-suspend.service: Unit entered failed state
Dom0 systemd[1]: qubes-suspend.service: Failed with result 'exit-code'."

In terminal to check mem_sleep value "sudo cat /sys/power/men_sleep " shows  
deep selected "s2idle [deep]" 



-- 
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/cfeaf978-430b-4c7d-8931-41e4719447cc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Problem with a (headless) appvm

[g80vmgmsqw]

martinga...@gmail.com:
> Hi, I have a problem with an unresponsive appvm that starts up but won't run 
> any commands.
> 
> Tried qvm-run --verbose appvm nautilus for example, which would open a Files 
> window but that command only shows: running 'nautilus' on appvm.
> 
> If one couldn't open windows on the damaged appvm, at least accessing its 
> filesystem would work around the problem.
> 
> Any suggestion? Thanks in advance!
> 

You should hopefully at least be able to get a shell with: `sudo xl
console appvm`.

-- 
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/6067bfa8-4d70-e244-bddd-d9aa73a1b47d%40riseup.net.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Problem with a (headless) appvm

[martingauna]

Hi, I have a problem with an unresponsive appvm that starts up but won't run 
any commands.

Tried qvm-run --verbose appvm nautilus for example, which would open a Files 
window but that command only shows: running 'nautilus' on appvm.

If one couldn't open windows on the damaged appvm, at least accessing its 
filesystem would work around the problem.

Any suggestion? Thanks in advance!

-- 
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/ed00897c-4d54-4daa-aea1-9e1bbef607f9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] qubes vpn autostart

['botaniga' via qubes-users]

Thanks. I will try the cli way, but as i understand, i wont have the 
networkmanager option of switching the vpn servers, which is a dealbreaker for 
me, i need to be able to easily switch vpn servers, see my current connections 
etc.

The gui way is the way ive done it, works great, so do the qubes-vpn-support 
anti-leak features, the only thing i cant get to work is the autoconnect.

Switching vpn servers in the shell just isnt an option for me at all, i have to 
have a setup which is usable for my family, and that means no shell.
Maybe its a bit early to switch to qubes os for endusers?


Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐
Am Dienstag, Mai 14, 2019 2:40 PM schrieb Daniil Travnikov :

> I recommend you to try cli version of install like here:
> https://www.youtube.com/watch?v=K1_zqT7_N7k
>
> But also you could try to do it like here in gui way:
> https://www.youtube.com/watch?v=wYEmDZebow4
>
> P.S. If you plan to use Qubes OS, I strongly recommend to learn cli-way of 
> using. It is not too hard for newbies if we talking about step by step 
> instructions. In most cases you can do not understand what are you doing, but 
> it will still works. :)
>
> On Monday, May 13, 2019 at 3:40:35 PM UTC+3, botaniga wrote:
>
> > Thank you.
> > Well, NM works with my fed 29 template, so does qubes-vpn-support. The only 
> > thing i just cant get to work is the autoconnect at boot, anti-leak 
> > features do work.
> > Are there any mistakes in the nmcli-line i wrote?
> > Im sure the qubes-tunnel instructions make sense for somebody who knows 
> > what he is doing, but all i can do is follow step by step instructions :(.
>
> --
>
> 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/b3384aa5-5e99-4da3-a916-50e45180a3d9%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.


-- 
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/IAgyp_UHaXLA08MPrAT_9txlzr2KS-68gXyoYB2FH6golb4gofDYIqmWPaYYDOV_WIrYJDYNhmXobyaFlmszihBCfAJz0X1zT77QyLSN06U%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Adding a Firefox add-on error to -dvm ?

[Daniil Travnikov]

On Monday, May 6, 2019 at 8:58:48 PM UTC+3, 22...@tutamail.com wrote:
> I used to be able to add "add-ons" to my -dvm's (e.g. HHTPS Everywhere, No 
> Script, etc...). I would periodically update these add-ons in the -dvm.
> 
> Recently I noticed an add-on needed update and when I went to update it, it 
> says it was no longer compatible? I knew enough to start the -dvm using 
> gnome->terminal->firefox in -dvm however this time it didn't allow me to 
> update the add-on?
> 
> Not sure this is a security enhancement with a recent update but any feedback 
> would be appreciated...I hate running scripts on random webpages...
> 
> Thx rip22...

I think it could be a problem which created by Mozilla:

https://blog.torproject.org/noscript-temporarily-disabled-tor-browser


You could try to do this:

1. Open the address about:config in the Firefox Browser address bar
2. At the top of the page, search for xpinstall.signatures.required
3. Set the xpinstall.signatures.requiredentry to false by double clicking it

-- 
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/78f8dd52-22c5-4789-bffc-a4e18801e8fc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] qubes vpn autostart

[Daniil Travnikov]

I recommend you to try cli version of install like here:
https://www.youtube.com/watch?v=K1_zqT7_N7k


But also you could try to do it like here in gui way:
https://www.youtube.com/watch?v=wYEmDZebow4


P.S. If you plan to use Qubes OS, I strongly recommend to learn cli-way of 
using. It is not too hard for newbies if we talking about step by step 
instructions. In most cases you can do not understand what are you doing, but 
it will still works. :)


On Monday, May 13, 2019 at 3:40:35 PM UTC+3, botaniga wrote:
> Thank you.
> Well, NM works with my fed 29 template, so does qubes-vpn-support. The only 
> thing i just cant get to work is the autoconnect at boot, anti-leak features 
> do work.
> Are there any mistakes in the nmcli-line i wrote?
> Im sure the qubes-tunnel instructions make sense for somebody who knows what 
> he is doing, but all i can do is follow step by step instructions :(.
>

-- 
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/b3384aa5-5e99-4da3-a916-50e45180a3d9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes on Huawei Matebook Pro

[John Jonathan]

On Tuesday, May 14, 2019 at 1:44:23 PM UTC+2, awokd wrote:
> 
> > Hello, I am unable to install Qubes on my new Huawei Matebook Pro.
> > 
> > I have obviously disabled secure boot in the BIOS.
> > Booting from USB stick stops at the initrd stage. I modified
> > slightly the Anaconda partition, by changing the file EFI/BOOT/Boot64.cfg 
> > according to an older suggestion here, changing the default qubes-verbose 
> > entry for efi to
> > 
> > efi=no-rs
> > 
> > but that did not do the trick for me, the installation still halts at the 
> > initrd stage. Is there anything else I should/could do/try? The very same 
> > stick boots perfectly on an old Toshiba.
> > 
> Try 
> https://www.qubes-os.org/doc/uefi-troubleshooting/#installation-freezes-before-getting-to-anaconda-qubes-40
>  
> instead of or in addition to no-rs.

Yes, thank you, it did take both things for me to work, i.e., both efi=no-rs 
and the two options suggested in the link you posted. 

Now the only thing which does not seem to work is the touchpad, but apart from 
this it is installing just fine.

Thanks a lot!!! 

-- 
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/ff409f1d-a7de-488c-aa5b-832f45b2a047%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes on Huawei Matebook Pro

['awokd' via qubes-users]

jjsk...@gmail.com:

Hello, I am unable to install Qubes on my new Huawei Matebook Pro.

I have obviously disabled secure boot in the BIOS.
Booting from USB stick stops at the initrd stage. I modified
slightly the Anaconda partition, by changing the file EFI/BOOT/Boot64.cfg 
according to an older suggestion here, changing the default qubes-verbose entry 
for efi to

efi=no-rs

but that did not do the trick for me, the installation still halts at the 
initrd stage. Is there anything else I should/could do/try? The very same stick 
boots perfectly on an old Toshiba.

Try 
https://www.qubes-os.org/doc/uefi-troubleshooting/#installation-freezes-before-getting-to-anaconda-qubes-40 
instead of or in addition to no-rs.


--
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/2a0281a8-45ae-c80e-0de2-ca94ace06db1%40danwin1210.me.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] debian-10 and libdvd-pkg

[haaber]

Just to inform you to be careful when using libdvd-pkg in debian-10
(happily I made a test install inside an AppVMand not the template). A
bug messes up the apt mechanism ... the issue seems known to
debian-team. So no dvd's on my qubes-machine, at least for a while :((

--
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/f493d110-2159-d439-1378-d9f131328bd6%40web.de.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Computer shutsoff when lid is closed when it should suspend

['awokd' via qubes-users]

eduzw...@gmail.com:

Does anyone have the i3 suspend command so the pc doesn't shutoff when lid is 
closed in R4?


mem_sleep_default=deep ?

--
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/1404352f-f74f-cb6b-374a-d486d1542fcc%40danwin1210.me.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Spontaneous rebooting

[google]

On 2019-05-13 22:27, Michael Siepmann wrote:

On 4/19/19 12:45 AM, Jon deps wrote:

On 4/13/19 8:01 PM, Michael Siepmann wrote:

 
On 4/13/19 12:28 PM, Chris wrote:

Hello Michael,

‐‐‐ Original Message ‐‐‐
On Friday, April 12, 2019 3:24 PM, Michael Siepmann
 wrote:


On 8/10/18 12:37 PM, Kelly Dean wrote:


Am I the only one having a problem with Qubes spontaneously
rebooting on Intel hardware? Only other reports I see are about
AMD problems, but I'm using an Intel Core i3.

Happens every few weeks. Sometimes just 1 or 2 weeks, sometimes 5
or 6. Got it on Qubes 3.2, and now 4.0 too (new installation, not
upgrade), multiple times.

Unlikely to be a hardware problem. The system passed both
memtest86 and a multi-day mersenne prime stress test. And other
OSes tested on this hardware before I switched to Qubes, including
Debian and Windows, never had a problem.

The rebooting seems completely random. No apparent trigger, and no
warning. Acts like an instant hard reset. Sometimes even when the
system is idle, and I haven't touched the console for hours.

It's wearingly inevitable enough that I don't even bother
intentionally rebooting after system updates anymore, in order to
minimize how many reboots I have to deal with (setting my
workspace back up is an ordeal), because I know the system will
end up spontaneously rebooting a week or two later anyway.


I'm having this problem too. I hadn't had it for a while but in the
past week or so it's happened a few times. I have a Lenovo ThinkPad
T440p with Intel Core i7, and Qubes 4.0 which I keep updated.



I had this problem which was due to Intel AMT Control being enabled 
in

the BIOS. Since turning this off my system has not rebooted.

Regards,

Chris

-
Chris Willard
chris-houdeaah+1aqdljmjb2...@public.gmane.org




Thanks for the suggestion, Chris. I appreciate it. I checked and 
Intel
AMT was already disabled so I guess something else must be causing it 
in

my case.




and what does
#journalctl -r   say if anything ?


In a dom0 terminal if I type "journalctl -r" I see a lot of info.
Anything in particular I should look for?


for instance if your machine spontaneously rebooted sometime between 
2019-05-13 23:30 and 2019-05-14 you could issue:


journalctl --since "2019-05-13 23:30" --until "2019-05-14" -p debug 
--no-pager | grep Reboot --before-context 42


this will output the final 42 log entries just before your machine 
rebooted.
i'm stuck with the same issue (as i described here 
https://www.mail-archive.com/qubes-users@googlegroups.com/msg28344.html 
) and my guess is you won't find anything useful in logs. anyway, i feel 
your pain. calling unman et al. : what systems are sporting 60+ days 
uptime?


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

[qubes-users] Possible to disable HVM window?

[Rendov Norra]

I'm looking to have a daemon VM that serves files from my ZFS array to
other trusted VMs. ZFS is a bit of a pain on linux, so I was hoping to
use FreeBSD. I have no problems booting or installing it, but it
leaves a window open to the vga console, which is rather annoying. I'm
wondering if there is a way to tell Qubes to not open a window for
this particular qube?

I would make it a standalone Xen guest, but I'm unsure as to how I'd
get it to interface with other Qubes if I were to do that, and I'd
lose out on the benefits of it being a qube.

-- 
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/CAPmquXD4OADaSRrvA4z0Ozv%3DgxEoJZdnWQW%3DD_tpQj1-wKm8yA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Qubes on Huawei Matebook Pro

[jjskoli]

Hello, I am unable to install Qubes on my new Huawei Matebook Pro. 

I have obviously disabled secure boot in the BIOS.
Booting from USB stick stops at the initrd stage. I modified 
slightly the Anaconda partition, by changing the file EFI/BOOT/Boot64.cfg 
according to an older suggestion here, changing the default qubes-verbose entry 
for efi to

efi=no-rs

but that did not do the trick for me, the installation still halts at the 
initrd stage. Is there anything else I should/could do/try? The very same stick 
boots perfectly on an old Toshiba. 

-- 
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/37fe653e-8607-40d9-bb4e-7e921b2efd33%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.