[qubes-users] Re: Post installation - VMs are not starting

2018-10-03 Thread rafudk
tirsdag den 2. oktober 2018 kl. 23.23.39 UTC+2 skrev raf...@gmail.com:
> New Qubes user! First install today.
> 
> "Qubes-R4.0-x86_64.iso" (DD image) is installed.
> Downloaded today (2nd October 2018) 
> 
> During the install during options for TemplateVMs, Sys-usb, etc. following 
> error appeared: 
> 
> 
> --
> 
> [Dom 0] Error
> ['/usr/bin/qubes-prefs','default-kernel','4.14.18-1'] failed:
> stdout:""
> stderr: "Traceback (most recent call last):
> File "/usr/bin/qubes-prefs", line 5, in 
> sys.exit(main())
> File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qubes_prefs.py", line 
> 42, in main
> return qubesadmin.tools.qvm_prefs.process_actions(parser, args, target)
> File "/usr/lib/python3.5/site-packafes/qybesadmin/tools/qvm_prefs.py", line 
> 116, in process_actions
> setattr(target, args.property, args.value)
> File "/usr/lib/python3.5/site-packages/qubesadmin/base.py", line 283, in 
> __setattr__
> str(value).encode('utf-8'))
> File "/usr/lib/python3.5/site-packages/qubesadmin/app.py" line 466, in 
> qubesd_call
> client_socket.connect(qubesadmin.config.QUBSED.SOCKET)
> FileNotFoundError: [Errno 2] No such file or directory
> 
> 
> 
> When I press OK, I can finish the setup and boot in Qubes OS. BUT there is no 
> sys-net, sys-usb or any TemplateVMs. 
> 
> I then used the command "sudo journalctl" in terminal
> 
> 
> 
> 
> Results (red text):
> 
> (1)
> "tpm tpm0: A TPM error (6) occurred attempting to read pcr value"
> 
> ### in white (TPM is disabled/deactivated (0x6))
> 
> (2) 
> "TDB: tdb_open_ex: could not open file /var/lib/xenstored/tdb: No such file 
> or directory"
> "Checking store ..."
> "Checking store complete."
> 
> (3)
> "Failed to start Qubes OS daemon."
> 
> 
> --2 hours later--
> 
> (4)
> Some ACPI errors
> 
> (5)
> Failed to find module 'uinput'
> 
> 
> 
> 
> 
> I have been searching GitHub and Reddit. This could be similar. 
> 
> #3028 
> https://github.com/QubesOS/qubes-issues/issues/3028#issuecomment-322330133
> 
> If it is the same problem, why do I get it when I haven't used R3.2? remains 
> from a previous owner? And what do I need to do to fix it?

Extra info:
I have a Lenovo PC, but I used Legacy Boot. 

Anyone who have an idea that might help me? 

-- 
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/352f138f-908e-447c-b9f2-38fa83b01ab3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Post installation - VMs are not starting

2018-10-02 Thread rafudk
New Qubes user! First install today.

"Qubes-R4.0-x86_64.iso" (DD image) is installed.
Downloaded today (2nd October 2018) 

During the install during options for TemplateVMs, Sys-usb, etc. following 
error appeared: 


--

[Dom 0] Error
['/usr/bin/qubes-prefs','default-kernel','4.14.18-1'] failed:
stdout:""
stderr: "Traceback (most recent call last):
File "/usr/bin/qubes-prefs", line 5, in 
sys.exit(main())
File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qubes_prefs.py", line 
42, in main
return qubesadmin.tools.qvm_prefs.process_actions(parser, args, target)
File "/usr/lib/python3.5/site-packafes/qybesadmin/tools/qvm_prefs.py", line 
116, in process_actions
setattr(target, args.property, args.value)
File "/usr/lib/python3.5/site-packages/qubesadmin/base.py", line 283, in 
__setattr__
str(value).encode('utf-8'))
File "/usr/lib/python3.5/site-packages/qubesadmin/app.py" line 466, in 
qubesd_call
client_socket.connect(qubesadmin.config.QUBSED.SOCKET)
FileNotFoundError: [Errno 2] No such file or directory



When I press OK, I can finish the setup and boot in Qubes OS. BUT there is no 
sys-net, sys-usb or any TemplateVMs. 

I then used the command "sudo journalctl" in terminal




Results (red text):

(1)
"tpm tpm0: A TPM error (6) occurred attempting to read pcr value"

### in white (TPM is disabled/deactivated (0x6))

(2) 
"TDB: tdb_open_ex: could not open file /var/lib/xenstored/tdb: No such file or 
directory"
"Checking store ..."
"Checking store complete."

(3)
"Failed to start Qubes OS daemon."


--2 hours later--

(4)
Some ACPI errors

(5)
Failed to find module 'uinput'





I have been searching GitHub and Reddit. This could be similar. 

#3028 https://github.com/QubesOS/qubes-issues/issues/3028#issuecomment-322330133

If it is the same problem, why do I get it when I haven't used R3.2? remains 
from a previous owner? And what do I need to do to fix 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/c76725a6-18d4-4910-82cb-5a474a9bfe28%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.