Re: [qubes-users] Re: Qubes locks up half the time on startup with filenotfound error trying to run qubes manager
On Friday, September 14, 2018 at 4:48:17 AM UTC-5, Marcus Linsner wrote:
> On Thursday, September 13, 2018 at 7:43:57 PM UTC+2, Guy Frank wrote:
> > On Tuesday, September 11, 2018 at 5:12:00 PM UTC-5, Guy Frank wrote:
> > > On Tuesday, September 11, 2018 at 4:29:02 PM UTC-5, awokd wrote:
> > > > On Tue, September 11, 2018 7:10 pm, Guy Frank wrote:
> > > > > On Tuesday, September 11, 2018 at 1:44:13 PM UTC-5, Guy Frank wrote:
> > > > >
> > > > >> Was a bit premature thinking that my qubes installation was stable.
> > > > >> About half the time I start the system, it locks up and I am only
> > > > >> able
> > > > >> to access Dom0 (qubes manager will not open, nor will any qubes, even
> > > > >> from command line). The system gives a serious 'filenotfound' error
> > > > >> msg. I've looked at previous posts on problems like this, but my
> > > > >> problem doesn't seem to fit what others reported--qubes.xml is not
> > > > >> empty and disk utilization is minimal (or near 50% in one case). The
> > > > >> error message is:
> > > > >>
> > > > >> #
> > > > >> Whoops. A critical error has occurred. This is most likely a bug in
> > > > >> Qubes Manager
> > > > >> FileNotFoundError: [Errno 2]
> > > > >> No such file or directory
> > > > >> at line 9 of file /usr/bin/qubes-qube-manager #
> > > > >>
> > > > >>
> > > > >> Line 9 reads: load_entry_point('qubesmanager==4.0.16',
> > > > >> 'console_scripts', 'qubes-qube-manager')()
> > > > >>
> > > > >>
> > > > >> Ok, so the weird thing is that this works fine half the time. On
> > > > >> half
> > > > >> of my boot ups, I don't encounter this problem. So if there is no
> > > > >> such
> > > > >> file or directory, it's not there half the time. qubes.xml looks
> > > > >> good
> > > > >> (to my untrained eyes), and df -h shows nothing at more than 1%
> > > > >> utilization except for /dev/nvme0n1p1 mounted on /boot/efi which is
> > > > >> 56%
> > > > >> of 200MB. nvme0n1p1 is, I believe, the GPT table?
> > > > >>
> > > > >> I'm worried about coming to rely on this installation if at some
> > > > >> point
> > > > >> the error doesn't go away every other reboot and becomes permanent.
> > > > >> Am
> > > > >> trying updates now--maybe that will help.
> > > > >>
> > > > >> Guy
> > > > >>
> > > > >
> > > > > Updating the software in dom0 doesn't make the problem disappear,
> > > > > though
> > > > > now the main error message is:
> > > > >
> > > > > QubesDaemonCommunicationError: Failed to connect to qubesd service:
> > > > > [Errno 2] No such file or directory
> > > > > at line 9 of file /usr/bin/qubes-qube-manager
> > > >
> > > > Nothing related earlier in the "sudo journalctl -e" log? Try "sudo
> > > > systemctl restart qubesd"?
> > >
> > > Thanks awokd! I'll give these a try next time I run into the problem
> >
> > Ok, so on my next reboot, it ran into this problem again. I made a copy of
> > the journalctl log and tried to restart qubesd, to no effect.
> >
> > The attached file, jnlctlErr.txt, if you scroll down to 09:24:43, I think
> > you can see where the Qubes OS daemon fails. It is immediately preceded by
> > the 1d.2 pci device worker failing, suggesting that something about this
> > failure is causing the daemon from starting (which occurs below the blank
> > line I added to the log). 1d.2 is a PCI Bridge, Intel Corp Device a332. No
> > idea what exactly this is or how to find out (not a hardware person).
> >
> > One thing I thought of is the fact that there's a PS/2 card in the machine
> > to which a PS/2 keyboard & mouse are attached. Neither has ever worked in
> > Qubes (though they worked in Windows), so maybe that's what's triggering
> > the problem? Will do some testing.
> >
> > When I attempt to start qubes daemon w/ sudo systemctl restart qubesd,
> > journalctl log shows other errors. The qubes daemon doesn't get started
> > and I can't use the system.
> >
> > What I can do is reboot. And about every other time, Qubes comes up and is
> > fine. My concern is that at some point it'll stop doing this, so I'd
> > really like to figure out how to solve this problem.
> >
> > Guy
>
> Looking the the relevant errors, in context (and the time between them):
>
> ...
> Sep 13 09:20:23 localhost kernel: usb 1-10.1: New USB device found,
> idVendor=413c, idProduct=2002
> Sep 13 09:20:23 localhost kernel: usb 1-10.1: New USB device strings: Mfr=1,
> Product=2, SerialNumber=0
> Sep 13 09:20:23 localhost kernel: usb 1-10.1: Product: Dell USB Keyboard Hub
> Sep 13 09:20:23 localhost kernel: usb 1-10.1: Manufacturer: Dell
> Sep 13 09:20:23 localhost kernel: input: Dell Dell USB Keyboard Hub as
> /devices/pci:00/:00:14.0/usb1/1-10/1-10.1/1-10.1:1.0/0003:413C:2002.0001/input/input3
> Sep 13 09:20:23 localhost kernel: hid-generic 0003:413C:2002.0001:
> input,hidraw0: USB HID v1.10 Keyboard [Dell Dell USB Keyboard Hub] on
> usb-:00:14.0-10.1/input0
> Sep 13 09:20:23 localhost kernel: input: Dell Dell USB Keyb
Re: [qubes-users] Re: Qubes locks up half the time on startup with filenotfound error trying to run qubes manager
On Thursday, September 13, 2018 at 7:43:57 PM UTC+2, Guy Frank wrote:
> On Tuesday, September 11, 2018 at 5:12:00 PM UTC-5, Guy Frank wrote:
> > On Tuesday, September 11, 2018 at 4:29:02 PM UTC-5, awokd wrote:
> > > On Tue, September 11, 2018 7:10 pm, Guy Frank wrote:
> > > > On Tuesday, September 11, 2018 at 1:44:13 PM UTC-5, Guy Frank wrote:
> > > >
> > > >> Was a bit premature thinking that my qubes installation was stable.
> > > >> About half the time I start the system, it locks up and I am only able
> > > >> to access Dom0 (qubes manager will not open, nor will any qubes, even
> > > >> from command line). The system gives a serious 'filenotfound' error
> > > >> msg. I've looked at previous posts on problems like this, but my
> > > >> problem doesn't seem to fit what others reported--qubes.xml is not
> > > >> empty and disk utilization is minimal (or near 50% in one case). The
> > > >> error message is:
> > > >>
> > > >> #
> > > >> Whoops. A critical error has occurred. This is most likely a bug in
> > > >> Qubes Manager
> > > >> FileNotFoundError: [Errno 2]
> > > >> No such file or directory
> > > >> at line 9 of file /usr/bin/qubes-qube-manager #
> > > >>
> > > >>
> > > >> Line 9 reads: load_entry_point('qubesmanager==4.0.16',
> > > >> 'console_scripts', 'qubes-qube-manager')()
> > > >>
> > > >>
> > > >> Ok, so the weird thing is that this works fine half the time. On half
> > > >> of my boot ups, I don't encounter this problem. So if there is no such
> > > >> file or directory, it's not there half the time. qubes.xml looks good
> > > >> (to my untrained eyes), and df -h shows nothing at more than 1%
> > > >> utilization except for /dev/nvme0n1p1 mounted on /boot/efi which is 56%
> > > >> of 200MB. nvme0n1p1 is, I believe, the GPT table?
> > > >>
> > > >> I'm worried about coming to rely on this installation if at some point
> > > >> the error doesn't go away every other reboot and becomes permanent. Am
> > > >> trying updates now--maybe that will help.
> > > >>
> > > >> Guy
> > > >>
> > > >
> > > > Updating the software in dom0 doesn't make the problem disappear, though
> > > > now the main error message is:
> > > >
> > > > QubesDaemonCommunicationError: Failed to connect to qubesd service:
> > > > [Errno 2] No such file or directory
> > > > at line 9 of file /usr/bin/qubes-qube-manager
> > >
> > > Nothing related earlier in the "sudo journalctl -e" log? Try "sudo
> > > systemctl restart qubesd"?
> >
> > Thanks awokd! I'll give these a try next time I run into the problem
>
> Ok, so on my next reboot, it ran into this problem again. I made a copy of
> the journalctl log and tried to restart qubesd, to no effect.
>
> The attached file, jnlctlErr.txt, if you scroll down to 09:24:43, I think you
> can see where the Qubes OS daemon fails. It is immediately preceded by the
> 1d.2 pci device worker failing, suggesting that something about this failure
> is causing the daemon from starting (which occurs below the blank line I
> added to the log). 1d.2 is a PCI Bridge, Intel Corp Device a332. No idea
> what exactly this is or how to find out (not a hardware person).
>
> One thing I thought of is the fact that there's a PS/2 card in the machine to
> which a PS/2 keyboard & mouse are attached. Neither has ever worked in Qubes
> (though they worked in Windows), so maybe that's what's triggering the
> problem? Will do some testing.
>
> When I attempt to start qubes daemon w/ sudo systemctl restart qubesd,
> journalctl log shows other errors. The qubes daemon doesn't get started and
> I can't use the system.
>
> What I can do is reboot. And about every other time, Qubes comes up and is
> fine. My concern is that at some point it'll stop doing this, so I'd really
> like to figure out how to solve this problem.
>
> Guy
Looking the the relevant errors, in context (and the time between them):
...
Sep 13 09:20:23 localhost kernel: usb 1-10.1: New USB device found,
idVendor=413c, idProduct=2002
Sep 13 09:20:23 localhost kernel: usb 1-10.1: New USB device strings: Mfr=1,
Product=2, SerialNumber=0
Sep 13 09:20:23 localhost kernel: usb 1-10.1: Product: Dell USB Keyboard Hub
Sep 13 09:20:23 localhost kernel: usb 1-10.1: Manufacturer: Dell
Sep 13 09:20:23 localhost kernel: input: Dell Dell USB Keyboard Hub as
/devices/pci:00/:00:14.0/usb1/1-10/1-10.1/1-10.1:1.0/0003:413C:2002.0001/input/input3
Sep 13 09:20:23 localhost kernel: hid-generic 0003:413C:2002.0001:
input,hidraw0: USB HID v1.10 Keyboard [Dell Dell USB Keyboard Hub] on
usb-:00:14.0-10.1/input0
Sep 13 09:20:23 localhost kernel: input: Dell Dell USB Keyboard Hub as
/devices/pci:00/:00:14.0/usb1/1-10/1-10.1/1-10.1:1.1/0003:413C:2002.0002/input/input4
Sep 13 09:20:23 localhost kernel: usb 4-3: new low-speed USB device number 2
using ohci-pci
...
Sep 13 09:20:23 localhost kernel: hid-generic 0003:413C:2002.0002:
input,hidraw1: USB HID v1.10 Device [Dell Dell USB Keyboard Hub] on
usb-:00:1
Re: [qubes-users] Re: Qubes locks up half the time on startup with filenotfound error trying to run qubes manager
On Thu, September 13, 2018 5:43 pm, Guy Frank wrote: > Ok, so on my next reboot, it ran into this problem again. I made a copy > of the journalctl log and tried to restart qubesd, to no effect. > > The attached file, jnlctlErr.txt, if you scroll down to 09:24:43, I think > you can see where the Qubes OS daemon fails. It is immediately preceded > by the 1d.2 pci device worker failing, suggesting that something about > this failure is causing the daemon from starting (which occurs below the > blank line I added to the log). 1d.2 is a PCI Bridge, Intel Corp Device > a332. No idea what exactly this is or how to find out (not a hardware > person). What is :06:00.0 (and :05:00.0 for that matter), one of your USB controllers? Check with lspci. Try unplugging all USB devices except keyboard and mouse, and seeing if that error still shows. If so, try moving your keyboard and mouse to a different controller, and disable :06:00.0. > One thing I thought of is the fact that there's a PS/2 card in the > machine to which a PS/2 keyboard & mouse are attached. Neither has ever > worked in Qubes (though they worked in Windows), so maybe that's what's > triggering the problem? Will do some testing. > > When I attempt to start qubes daemon w/ sudo systemctl restart qubesd, > journalctl log shows other errors. The qubes daemon doesn't get started > and I can't use the system. Only qubesd errors I see in that log are: Sep 13 09:52:19 dom0 systemd[1]: qubesd.service: Start operation timed out. Terminating. I don't know how to get more detailed logs to see why it's doing that- maybe it has a systemd dependency on udev? > What I can do is reboot. And about every other time, Qubes comes up and > is fine. My concern is that at some point it'll stop doing this, so I'd > really like to figure out how to solve this problem. -- 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/32f41dfe1a184191d6358bf2424dc263.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes locks up half the time on startup with filenotfound error trying to run qubes manager
On Tuesday, September 11, 2018 at 5:12:00 PM UTC-5, Guy Frank wrote:
> On Tuesday, September 11, 2018 at 4:29:02 PM UTC-5, awokd wrote:
> > On Tue, September 11, 2018 7:10 pm, Guy Frank wrote:
> > > On Tuesday, September 11, 2018 at 1:44:13 PM UTC-5, Guy Frank wrote:
> > >
> > >> Was a bit premature thinking that my qubes installation was stable.
> > >> About half the time I start the system, it locks up and I am only able
> > >> to access Dom0 (qubes manager will not open, nor will any qubes, even
> > >> from command line). The system gives a serious 'filenotfound' error
> > >> msg. I've looked at previous posts on problems like this, but my
> > >> problem doesn't seem to fit what others reported--qubes.xml is not
> > >> empty and disk utilization is minimal (or near 50% in one case). The
> > >> error message is:
> > >>
> > >> #
> > >> Whoops. A critical error has occurred. This is most likely a bug in
> > >> Qubes Manager
> > >> FileNotFoundError: [Errno 2]
> > >> No such file or directory
> > >> at line 9 of file /usr/bin/qubes-qube-manager #
> > >>
> > >>
> > >> Line 9 reads: load_entry_point('qubesmanager==4.0.16',
> > >> 'console_scripts', 'qubes-qube-manager')()
> > >>
> > >>
> > >> Ok, so the weird thing is that this works fine half the time. On half
> > >> of my boot ups, I don't encounter this problem. So if there is no such
> > >> file or directory, it's not there half the time. qubes.xml looks good
> > >> (to my untrained eyes), and df -h shows nothing at more than 1%
> > >> utilization except for /dev/nvme0n1p1 mounted on /boot/efi which is 56%
> > >> of 200MB. nvme0n1p1 is, I believe, the GPT table?
> > >>
> > >> I'm worried about coming to rely on this installation if at some point
> > >> the error doesn't go away every other reboot and becomes permanent. Am
> > >> trying updates now--maybe that will help.
> > >>
> > >> Guy
> > >>
> > >
> > > Updating the software in dom0 doesn't make the problem disappear, though
> > > now the main error message is:
> > >
> > > QubesDaemonCommunicationError: Failed to connect to qubesd service:
> > > [Errno 2] No such file or directory
> > > at line 9 of file /usr/bin/qubes-qube-manager
> >
> > Nothing related earlier in the "sudo journalctl -e" log? Try "sudo
> > systemctl restart qubesd"?
>
> Thanks awokd! I'll give these a try next time I run into the problem
Ok, so on my next reboot, it ran into this problem again. I made a copy of the
journalctl log and tried to restart qubesd, to no effect.
The attached file, jnlctlErr.txt, if you scroll down to 09:24:43, I think you
can see where the Qubes OS daemon fails. It is immediately preceded by the
1d.2 pci device worker failing, suggesting that something about this failure is
causing the daemon from starting (which occurs below the blank line I added to
the log). 1d.2 is a PCI Bridge, Intel Corp Device a332. No idea what exactly
this is or how to find out (not a hardware person).
One thing I thought of is the fact that there's a PS/2 card in the machine to
which a PS/2 keyboard & mouse are attached. Neither has ever worked in Qubes
(though they worked in Windows), so maybe that's what's triggering the problem?
Will do some testing.
When I attempt to start qubes daemon w/ sudo systemctl restart qubesd,
journalctl log shows other errors. The qubes daemon doesn't get started and I
can't use the system.
What I can do is reboot. And about every other time, Qubes comes up and is
fine. My concern is that at some point it'll stop doing this, so I'd really
like to figure out how to solve this problem.
Guy
--
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/2556521e-ba44-48fd-b66f-5db21767abf9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Sep 13 09:50:49 dom0 sudo[4220]: pm : TTY=pts/1 ; PWD=/var/lib/qubes ;
USER=root ; COMMAND=/bin/systemctl restart qubesd
Sep 13 09:50:49 dom0 kernel: audit: type=1123 audit(1536850249.779:214):
pid=4220 uid=1000 auid=1000 ses=2 msg='cwd="/var/lib/qubes"
cmd=73797374656D63746C207265737461727420717562657364 terminal=pts/1 res=success'
Sep 13 09:50:49 dom0 kernel: audit: type=1110 audit(1536850249.779:215):
pid=4220 uid=0 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_env,pam_unix
acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1
res=success'
Sep 13 09:50:49 dom0 audit[4220]: USER_CMD pid=4220 uid=1000 auid=1000 ses=2
msg='cwd="/var/lib/qubes" cmd=73797374656D63746C207265737461727420717562657364
terminal=pts/1 res=success'
Sep 13 09:50:49 dom0 audit[4220]: CRED_REFR pid=4220 uid=0 auid=1000 ses=2
msg='op=PAM:setcred grantors=pam_env,pam_unix acct="
Re: [qubes-users] Re: Qubes locks up half the time on startup with filenotfound error trying to run qubes manager
On Tuesday, September 11, 2018 at 4:29:02 PM UTC-5, awokd wrote:
> On Tue, September 11, 2018 7:10 pm, Guy Frank wrote:
> > On Tuesday, September 11, 2018 at 1:44:13 PM UTC-5, Guy Frank wrote:
> >
> >> Was a bit premature thinking that my qubes installation was stable.
> >> About half the time I start the system, it locks up and I am only able
> >> to access Dom0 (qubes manager will not open, nor will any qubes, even
> >> from command line). The system gives a serious 'filenotfound' error
> >> msg. I've looked at previous posts on problems like this, but my
> >> problem doesn't seem to fit what others reported--qubes.xml is not
> >> empty and disk utilization is minimal (or near 50% in one case). The
> >> error message is:
> >>
> >> #
> >> Whoops. A critical error has occurred. This is most likely a bug in
> >> Qubes Manager
> >> FileNotFoundError: [Errno 2]
> >> No such file or directory
> >> at line 9 of file /usr/bin/qubes-qube-manager #
> >>
> >>
> >> Line 9 reads: load_entry_point('qubesmanager==4.0.16',
> >> 'console_scripts', 'qubes-qube-manager')()
> >>
> >>
> >> Ok, so the weird thing is that this works fine half the time. On half
> >> of my boot ups, I don't encounter this problem. So if there is no such
> >> file or directory, it's not there half the time. qubes.xml looks good
> >> (to my untrained eyes), and df -h shows nothing at more than 1%
> >> utilization except for /dev/nvme0n1p1 mounted on /boot/efi which is 56%
> >> of 200MB. nvme0n1p1 is, I believe, the GPT table?
> >>
> >> I'm worried about coming to rely on this installation if at some point
> >> the error doesn't go away every other reboot and becomes permanent. Am
> >> trying updates now--maybe that will help.
> >>
> >> Guy
> >>
> >
> > Updating the software in dom0 doesn't make the problem disappear, though
> > now the main error message is:
> >
> > QubesDaemonCommunicationError: Failed to connect to qubesd service:
> > [Errno 2] No such file or directory
> > at line 9 of file /usr/bin/qubes-qube-manager
>
> Nothing related earlier in the "sudo journalctl -e" log? Try "sudo
> systemctl restart qubesd"?
Thanks awokd! I'll give these a try next time I run into the problem
--
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/6d9e29be-c928-4b8e-a740-f7b26079a557%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes locks up half the time on startup with filenotfound error trying to run qubes manager
On Tue, September 11, 2018 7:10 pm, Guy Frank wrote:
> On Tuesday, September 11, 2018 at 1:44:13 PM UTC-5, Guy Frank wrote:
>
>> Was a bit premature thinking that my qubes installation was stable.
>> About half the time I start the system, it locks up and I am only able
>> to access Dom0 (qubes manager will not open, nor will any qubes, even
>> from command line). The system gives a serious 'filenotfound' error
>> msg. I've looked at previous posts on problems like this, but my
>> problem doesn't seem to fit what others reported--qubes.xml is not
>> empty and disk utilization is minimal (or near 50% in one case). The
>> error message is:
>>
>> #
>> Whoops. A critical error has occurred. This is most likely a bug in
>> Qubes Manager
>> FileNotFoundError: [Errno 2]
>> No such file or directory
>> at line 9 of file /usr/bin/qubes-qube-manager #
>>
>>
>> Line 9 reads: load_entry_point('qubesmanager==4.0.16',
>> 'console_scripts', 'qubes-qube-manager')()
>>
>>
>> Ok, so the weird thing is that this works fine half the time. On half
>> of my boot ups, I don't encounter this problem. So if there is no such
>> file or directory, it's not there half the time. qubes.xml looks good
>> (to my untrained eyes), and df -h shows nothing at more than 1%
>> utilization except for /dev/nvme0n1p1 mounted on /boot/efi which is 56%
>> of 200MB. nvme0n1p1 is, I believe, the GPT table?
>>
>> I'm worried about coming to rely on this installation if at some point
>> the error doesn't go away every other reboot and becomes permanent. Am
>> trying updates now--maybe that will help.
>>
>> Guy
>>
>
> Updating the software in dom0 doesn't make the problem disappear, though
> now the main error message is:
>
> QubesDaemonCommunicationError: Failed to connect to qubesd service:
> [Errno 2] No such file or directory
> at line 9 of file /usr/bin/qubes-qube-manager
Nothing related earlier in the "sudo journalctl -e" log? Try "sudo
systemctl restart qubesd"?
--
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/963e2ab68bb85859c8c2be6500375ec7.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes locks up half the time on startup with filenotfound error trying to run qubes manager
On Tuesday, September 11, 2018 at 1:44:13 PM UTC-5, Guy Frank wrote:
> Was a bit premature thinking that my qubes installation was stable. About
> half the time I start the system, it locks up and I am only able to access
> Dom0 (qubes manager will not open, nor will any qubes, even from command
> line). The system gives a serious 'filenotfound' error msg. I've looked at
> previous posts on problems like this, but my problem doesn't seem to fit what
> others reported--qubes.xml is not empty and disk utilization is minimal (or
> near 50% in one case). The error message is:
>
> #
> Whoops. A critical error has occurred. This is most likely a bug in Qubes
> Manager
> FileNotFoundError: [Errno 2]
> No such file or directory
> at line 9
> of file /usr/bin/qubes-qube-manager
> #
>
> Line 9 reads: load_entry_point('qubesmanager==4.0.16', 'console_scripts',
> 'qubes-qube-manager')()
>
> Ok, so the weird thing is that this works fine half the time. On half of my
> boot ups, I don't encounter this problem. So if there is no such file or
> directory, it's not there half the time. qubes.xml looks good (to my
> untrained eyes), and df -h shows nothing at more than 1% utilization except
> for /dev/nvme0n1p1 mounted on /boot/efi which is 56% of 200MB. nvme0n1p1 is,
> I believe, the GPT table?
>
> I'm worried about coming to rely on this installation if at some point the
> error doesn't go away every other reboot and becomes permanent. Am trying
> updates now--maybe that will help.
>
> Guy
Updating the software in dom0 doesn't make the problem disappear, though now
the main error message is:
QubesDaemonCommunicationError: Failed to connect to qubesd service: [Errno 2]
No such file or directory
at line 9
of file /usr/bin/qubes-qube-manager
--
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/b27ad833-346e-4f2f-9061-03c2a908a3c0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
