You are not logged in.
Pages: 1
My backups are failing. It appears that it is due to PackageKit failing with "Failed to initialize alpm: using /etc/PackageKit/alpm.d/pacman.conf: invalid SigLevel value:". I don't think duplicity or deja-dup should ever find PackageKit relevant, but that may be a third issue.
Posts I've gone through to troubleshoot:
https://forums.archlinux.fr/viewtopic.p … =1&t=18656
https://bugzilla.redhat.com/show_bug.cgi?id=1188455
https://github.com/FZUG/repo/issues/77
https://bbs.archlinux.org/viewtopic.php?id=191286
/etc/pacman.conf: https://pastebin.com/m6m2pmij
`ls /etc/PackageKit/alpm.d/`: https://pastebin.com/2ucmYK89
/etc/PackageKit/alpm.d/pacman.conf: https://pastebin.com/XfVtvu6Q
`dmesg`: https://pastebin.com/TPczAwrB
`sudo journalctl --system --user --no-tail -xr --full --all --output=verbose | head -n 5000`: https://pastebin.com/2wVqi2mj
`sudo journalctl -r | head -n 5000`: https://pastebin.com/LErUGiiU
Any ideas?
Offline
What happens if you change line 40 of your /etc/pacman.conf to it's default setting...
SigLevel = Required DatabaseOptionalOffline
I had that set earlier.
```
● packagekit.service - PackageKit Daemon
Loaded: loaded (/usr/lib/systemd/system/packagekit.service; static; vendor preset: disabled)
Active: failed (Result: core-dump) since Wed 2017-10-18 09:03:38 EDT; 9s ago
Process: 4723 ExecStart=/usr/lib/PackageKit/packagekitd (code=dumped, signal=TRAP)
Main PID: 4723 (code=dumped, signal=TRAP)
Oct 18 09:03:38 doge systemd[1]: Starting PackageKit Daemon...
Oct 18 09:03:38 doge PackageKit[4723]: daemon start
Oct 18 09:03:38 doge packagekitd[4723]: Failed to initialize alpm: using /etc/PackageKit/alpm.d/pacman.conf: inv
Oct 18 09:03:38 doge systemd[1]: packagekit.service: Main process exited, code=dumped, status=5/TRAP
Oct 18 09:03:38 doge systemd[1]: packagekit.service: Failed with result 'core-dump'.
Oct 18 09:03:38 doge systemd[1]: Failed to start PackageKit Daemon.
```
Offline
Use code tags please, see https://bbs.archlinux.org/help.php#bbcode
packagekit.service: Failed with result 'core-dump'.coredumpctl is useful for getting details from core dumps.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
It gives a few stack traces into glibc and the like -- probably not the problem.
Offline
Could be a parsing error in packagekit .
Try splitting the comment part on line 40 in /etc/pacman.conf to a separate line.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
That appears to have fixed the problem. However, that means that packagekit parser behavior changed recently. I need to submit a bug report somewhere.
Offline
Pages: 1