Immediately after a recent update, all of the system text is in a non-Latin character set. Being your average stupid insular American, I can’t tell what script they belong to. I think all of the characters I’ve seen belong - very broadly - to the Brahmic scripts, but there appear to be a couple of Latin characters sprinkled in haphazardly, so there might be some good old-fashioned textual corruption afoot. Also, keyboard input to the KDE settings app is in this other script(s?), which has thus far prevented me from finding my way to the ‘language and internationalization’ section of the settings menu. Any method of correcting this would be greatly appreciated.
Aha! I think we’re getting somewhere. The
pacman -Sinvocation returned an error due to conflicting files, but this time they look like the package contents proper:
accountsservice: /usr/include/accountsservice-1.0/act/act-user-enum-types.h exists in filesystem accountsservice: /usr/include/accountsservice-1.0/act/act-user-manager.h exists in filesystem accountsservice: /usr/include/accountsservice-1.0/act/act-user.h exists in filesystem accountsservice: /usr/include/accountsservice-1.0/act/act.h exists in filesystem accountsservice: /usr/lib/accounts-daemon exists in filesystem
Could these be the glob targets you were referring to earlier?
The only one it mentions when I run it that way (
sudo pacman -S accountsservice) is the
file I noted in the OP. I tried passing that file path as the glob to
--overwrite, but doing so has the same effect as
sudo pacman -S accountsservice.
I’ve also tried
-Ql. The former just spits out the package name and version. The latter complains about a different missing file. Same path as the last one, but named, appropriately enough,
files. In fact, the only file remaining in that directory is called
mtree. Meanwhile, running
sudo pacman -S --overwrite /var/lib/pacman/local/<packagename-version>/* accountsservice
sudo pacman -S --overwrite /var/lib/pacman/local/<packagename-version>/mtree accountsservice
have the same effect; no change.
That last bit is easy enough. Output of
error: 'accountsservice-0.6.54+2+g204a4ab-1': description file is missing error: 'accountsservice-0.6.54+2+g204a4ab-1': file list is missing
And that’s it. Just the one package, missing two metadata indices.
This is embarrassing. I should know by now how to fix something like this, but I feel like this is still a problem for the Newbie Corner.
I should preface this by saying that the situation is very similar to what is described here: https://forum.antergos.com/topic/11172/can-t-log-in-to-antergos-kde-plasma
…with the exception that I don’t know how to create a new user. I suspect trying to do so would not work in any case, as neither of the users already on the system work. They both quit back to the greeter.
Next, I figured that I’ll just go in through the textual interface and update my packages. I reasoned that I was probably seeing the results of a regression that came in with the last update. At least I know how to get to the tty’s!
Sure enough, I was able to log in. But then I got this:
error: could not open file /var/lib/pacman/local/accountsservice-0.6.54+2+g204a4ab-1/desc: No such file or directory
The system then asserts that, since there is missing or corrupt metadata, it will not under any circumstances make changes of any sort to any package on the system. Naturally, there is also no obvious way to simply replace a package’s missing metadata with default values from the remote copy (assuming I understand the context of ‘package metadata’ correctly).
Fortunately, that isn’t my primary machine; I’m sending this from my Ubuntu desktop.
Hi! I’m not very experienced with Antergos, only been using it for a couple of months now. So far I’ve enjoyed the experience more than Ubuntu, but each has its upsides. The problem I’m having is this: whenever there are package updates, deselecting them on Pamac’s updates list doesn’t prevent the program from upgrading them anyway.
Case in point, just today there was a minor update to LibreOffice. I figured I could live without the absolute latest point release. It’s big enough that it adds several minutes to the update procedure, and stable enough that I don’t feel like updating it all the time is a big priority. Same thing with Code::Blocks; it was just a -n level update (What are those, anyway? Package config changes? Tweaks to build options?) to a really big app. I made sure that the boxes next to each were blank/white/unmarked before clicking Apply.
Pamac downloaded and updated them both anyway.
I’d just like to know what’s going on. Have I failed to understand the UI paradigm? Is this just a (mis)feature that’s explained somewhere in the docs? Or is this a genuine bug that I should report?
Relevant app details:
Operating System: Antergos Linux
KDE Plasma Version: 5.14.3
Qt Version: 5.11.2
KDE Frameworks Version: 5.52.0
Kernel Version: 4.19.2-arch1-1-ARCH
OS Type: 64-bit
Processors: 4 × Intel® Core™ i5-4200U CPU @ 1.60GHz
Memory: 7.5 GiB of RAM