I like using Zorin and Zorin Connect. I have been able to figure out how to manage this amazing OS mostly on my own with minimal Linux experience. Thank you.
My issue:
Lock screen constantly waking due to Zorin Connect notifications.
I realize I can turn off notifications in BOTH 'Settings' and the individual Zorin Connect radio toggles.
My question:
I want to know how to change what wakes the computer. Specifically, which applications and their notifications are allowed to send this wake command.
Disclaimer: New to Linux and Zorin in general. Be kind.
You can view which devices have the Wake ability with nano:
sudo nano /proc/acpi/wakeup
Or GUI by opening file manager and navigating to /proc/acpi/wakeup and opening with a text editor.
PWRB is Power Button and the EHC- or Mouse...
You might paste your 'wakeup" file results here and see if you have anything additional in it.
Checking in from Mobile so forgive any auto-corrects here...
Normally I wouldn't do this but I won't be testing soon since my computer boot looped after disabling Mobile Devices in the tray to Off.
I did this once I found out that Zorin Connect errors were causing 'indefinite' growth of my syslog file.
The only reason I know this is because I woke up today to find notifications from disk usage manager that my entire drive was out of space.
~333.8GB syslog.1 file. Only after finding this info was I able to put together that Zorin Connect was the thing keeping it open and unclearable by erroring out. At this point is when I tried turning off Mobile Devices down in system tray before even fully recording the error that was occurring. Boot loop
Edit: @Aravisian the following error was the return of the syslog last majority of errors in the syslog.1
"[Date],[Computer], org.gnome.Shell.Extensions.ZorinConnect[1947]: #0 5591adc176a0 i /usr/share/gnome-shell/extensions/zorin-connect@zorinos.com/service/daemon.js:726 (39cc1bd84920 @ 971)
[Date],[Computer], org.gnome.Shell.Extensions.ZorinConnect[1947]: = Stack trace for context 0x5591adbf01a0 =
I'm pretty sure that's what was in my terminal window before the boot loop.
BTW any quick advice on restoring my system? I can access the files while using Live OS try mode.
Thank you.
Can you please advise how to clear out this log folder safely while only being able to boot to the USB Zorin demo-mode?
Currently that is the only way I can locate find the massive syslog file. But while running the clear command within the folder the message returns saying I do not have proper permissions.
I ran sudo cat /dev/null > /var/log/syslog
Also I feel I should note that the massive file's name is syslog.1
The syslog file without the .1 extension is only 138MB.
If easier, I would almost prefer advice on being able to re-boot into the filesystem so that I can run the sudo command while inside own root.
Please bear in mind that I have extensive computer experience but little Linux experience. I came to Zorin to escape M$.