search

ChrisTitusTech / Debian-titus

Debian customizations from Chris Titus Tech
GNU General Public License v3.0
414 stars 152 forks source link

Script Execution Failure at nala 94% on Debian-Titus BSPWM Branch #106

Open TechTune-1 opened 3 months ago

TechTune-1 commented 3 months ago

I have an issue with Debian-Titus (bspwm branch). During the execution of the script, the process halted at 94% completion with Nala, and my screen suddenly lost signal. so, I restarted my computer with the power button and ran the script again, it then rebooted and it briefly displayed “[FAILED] Failed to start polkit.service - Authorization Manager” before returning me to the terminal interface again.

blusewill commented 3 months ago

Maybe try manually install it? Since that script is kinda outdated?

TechTune-1 commented 2 months ago

Sorry for my late response. I tried to manually install policykit-1 before executing ./install.sh, but that unfortunately did not resolve the issue. My monitor lost signal at the beginning of the script, so I had to reboot my PC again. After executing the script again, I encountered this error:

Error: E: Unable to correct problems, you have held broken packages.
Synchronizing state of lightdm service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
Executing: /usr/lib/systemd/systemd-sysv-install enable lightdm
The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
Also=, or Alias= settings in the [Install] section, and Default Instance= for
template units). This means they are not meant to be enabled or disabled using systemctl.

I appreciate your help.

blusewill commented 2 months ago

You should install some polkit manager service such as gnome-keyring I think. That should resolved the issue

TechTune-1 commented 2 months ago

I tried to manually install lxpolkit and gnome-keyring before running the script but the error persists. When I executed sudo lightdm, I got the login screen, but after entering my credentials, it didn’t bring me to the desktop. After logging In a few times, the system froze.