Hi,
I'm not able to get the user crontab running, apparently this happens because
threre's no crond service nor unit files:
systemctl status crond
Unit crond.service could not be found.
Being the only service available the cron mount:
systemctl | grep -i cron
var-spool-cron.mount loaded active
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 leno
Hi Everyone!
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.CPU
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, mau
I'm also experiencing the same issue.
Whenever my laptop resumes after have being suspended, the sys-usb is frozen
and all USB devices attached to it fail to work. I have to kill the appvm and
start it again. This only affects the sys-usb though, the sys-net is working
fine during the resume.
Th
Hi folks!
Whenever my laptop resumes after have being suspended, the sys-usb is stalled
and all USB devices attached fail to work. They are all disconnected.
Whenever that happens the only way to have the sys-usb working again is to kill
it.
Strangely this only affects the sys-usb and not the sy
Unfortunately that only describes the process for the sys-net.
According to the issue described in the github the blacklist of the module
xhci-pci was already
merged into the stable repo r4.0 under the qubes-core-dom0-4.0.11-1.fc25.
So I guess that will not work either.
Are there any other sugges
" I needed to remove the assignement of one of the USB controllers from sys-usb
"
What do you mean by that? Are you unloading a kernel module before suspending
or the PCI controller? Which module is this?
The sys-usb still freezes on resume, so for the time being I have to manually
kill and star
Hi Folks!
Does anyone knows or have an idea of how to fix this? The sys-usb is freezing
every time the laptops is suspended.
I've tried to blacklist lots of for the PIC devices but that doesn't solve
anything.
Is it possible to re-open the github issue since this is not fixed?
Thank you!
May 11
Unfortunately this doesn't work for me. Detaching the USB controller doesn't
work.
My sys-usb always hangs on resume. No matter which update I make this problem
continues to persist.
Does anyone has any idea how to solve this?
Thank you!
May 17, 2018 4:32 PM, maur...@disroot.org (mailto:maur...
Anyone was able to solve this warning messages on boot without having to
install a fresh Qubes?
These messages show up on every boot.
Thank you!
April 29, 2018 5:48 PM, maur...@disroot.org (mailto:maur...@disroot.org) wrote:
Hi Everyone!
During the boot and before unlock the LuKS volume I'm get
I have updated my BIOS to the latest version just in case.
I have no Thunderbolt in the BIOS. I'm using a thinkpad T450s laptop from
lenovo (no Thunderbolt support).
The problem still persists, after resume the sys-usb is dead have to kill it
and start it again to resume my USB devices (keyboard
Does anyone have any idea how to get rid of these messages without installing
the system from scratch again?
January 13, 2019 8:05 PM, maur...@disroot.org (mailto:maur...@disroot.org)
wrote:
Anyone was able to solve this warning messages on boot without having to
install a fresh Qubes?
These m
13 matches
Mail list logo