dbus. Wow. You are now posting the second incident of that I have seen recently for Nautilus.
I do not use Nautilus or Gnome, so maybe I am missing something about "pkexec".
For now, open your Nautilus file manager normally, and then navigate as you would normally to the above files, but be aware that without the Exec, you will nto be able to Edit or Write to the files. Since we are just trying to ensure the files exist in those directories, though, it should be fine for now.
For later use, you might try enabling opening Nautlis as Admin with an extension for it:
sudo apt install nautilus-admin
Then once installed, you should be able to login with Root privileges by Right clicking an open area in the file manager and selecting it from the popover menu.
(May require a log out and in to take effect).
No, the system would create the folder upon recognizing the hardware. What I am trying to determine is where the fault is:
Is the system seeing the battery, but not communicating its status properly? OR is it not seeing it at all?
It appears that it is not seeing it at all; which brings us back to the points about checking in the UEFI settings above.
Let's check your module blacklist- just in case. I admit that I doubt your battery module could be blacklisted but I do not mind being surprised.
in terminal can you run
sudo nano /etc/modprobe.d/blacklist.conf
Then post a Screenshot of it (may need two screenshots after arrow-key'ing down to the bottom).
The reasons for screenshot is that the Forum Software will try to parse the commented out lines.
Thanks, sorry for bothering you though. I got:
awk: 1: unexpected character 0xe2
awk: line 2: missing } near end of file
No support for device type: power_supply
It states the bug affects all Surface users running Linux. It is not surprising as the Surface was manufactured For Microsoft Windows directly.
It also states a patch was sent in in 2020- So probably is included in the latest kernel.
This MAY mean it will work properly in Zorin 16 when it is released.
One possible option may be to upgrade your kernel to a higher version. I highly recommend you Back Up your system before upgrading- just in case. The 5.6 kernel is currently not fully tested on Zorin 16. If you would like to try it, can write a walk-through on that.
If the 5.6 kernel fails, do not worry- you can roll back to the kernel you are using now and boot normally.
To use the USB stick that you installed Zorin with, you can use a Parition Manager to delete the partition on it with the Zorin Install, then click the free space, add as new partition and format that as FAT32. Then you can use it to install Windows, if you need. So do not worry, all is not lost and you do still have options.
But I did post above about a kernel upgrade just as your post appeared, so please see that first, as well.
Rather than patching the kernel yourself, I think it would be better to upgrade to a newer kernel. That your notebook is a newer model may help a lot. It’s older machines where putting a newer kernel on it can cause troubles.
One moment, though- I will post a walk-through in a moment- But I am cross checking some things first.
Sometimes, installing the Mainline kernel will not work properly with UEFI or with Secure Boot enabled- (Which we covered above about needing Secure Boot disabled). So I am checking that first.
Also checking which newer kernel is best, given when that patch was submitted and what Ubuntu is using.
