search

C2N14 / AutomaThemely

Simple, set-and-forget python application for changing between desktop themes according to light and dark hours
GNU General Public License v3.0
206 stars 31 forks source link

Failure to Uninstall (after error in setting Cinnamon Desktop theme) #8

Open sanctuariesman opened 5 years ago

sanctuariesman commented 5 years ago

OS: Linux Mint 18.3 Cinnamon 3.6.7 (64-bit) Linux Kernel: 4.15.0-45-generic

(Reading database ... 593498 files and directories currently installed.) Removing automathemely (1.3) ... sudo: unknown user: --global sudo: unable to initialize policy plugin Removed symlink /etc/systemd/user/timers.target.wants/automathemely.timer. sudo: unknown user: --global sudo: unable to initialize policy plugin dpkg: error processing package automathemely (--purge): subprocess installed pre-removal script returned error exit status 1 sudo: invalid option -- 'm' usage: sudo -h | -K | -k | -V usage: sudo -v [-AknS] [-g group] [-h host] [-p prompt] [-u user] usage: sudo -l [-AknS] [-g group] [-h host] [-p prompt] [-U user] [-u user] [command] usage: sudo [-AbEHknPS] [-r role] [-t type] [-C num] [-g group] [-h host] [-p prompt] [-u user] [VAR=value] [-i|-s] [<command>] usage: sudo -e [-AknS] [-r role] [-t type] [-C num] [-g group] [-h host] [-p prompt] [-u user] file ... sudo: unknown user: --global sudo: unable to initialize policy plugin Created symlink /etc/systemd/user/timers.target.wants/automathemely.timer, pointing to /usr/lib/systemd/user/automathemely.timer. sudo: unknown user: --global sudo: unable to initialize policy plugin crontab: user-l' unknown crontab: user -' unknown Errors were encountered while processing: automathemely E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover:

Any Solutions to making Automathemely work? (I'd like to be able to keep it and using it.)

C2N14 commented 5 years ago

Hmmmm did you install/uninstall through apt? I think the script is failing because $SUDO_USER isn't being passed correctly...

C2N14 commented 5 years ago

Are you still having the same issue? Have you tried rebooting like #11 ?