Actionless Loveless

i see from the log that the last command which causing this error is: > pikspect => pacman --color=always --sync --sysupgrade does the error persists if run that pacman command...

this doesn't make any sense and what happens if you run it again in the pikaur?

then make sure you don't have this option set in pikaur's config: https://github.com/actionless/pikaur?tab=readme-ov-file#gpgdir-default--root-default-etcpacmandgnupg (or better try with the empty config, so it would just use defaults)

since you have close-to-default pikaur config, and the problem not happens in general with default arch setup but happens to you during privilege escalation only - then some of your...

i don't use bash myself, but from looking o nthe file i have potential ideas why it could interfere with pacman's completions, https://github.com/actionless/pikaur/blob/master/packaging/usr/share/bash-completion/completions/pikaur try: 1) replacing in each function name...

thanks! 👍 doesn't matter much

i think it could be related to this: https://github.com/awesomeWM/awesome/issues?q=is%3Aissue+startup_id

ah, i thought his problem that he did that change but client is not being moved to that tag

sure, @vijayabhaskar78, i'll be thankful for that 😺👍

release is ready, but is blocked by https://github.com/themix-project/themix-gui/issues/523 however it won't help regarding Arc theme, see pinned issues for more info