This command lists āforeignā packages - often explicitely installed using pacman -U packagename
These packages are all old -
some just old and could be updated with regular repo packages, some must have come from AUR (google-chrome and brave-bin, for example) - perhaps even all of them.
You could try pacman -Syuu
and see whether some will be updated.
I have no idea how to rectify the mess except to first tend to any .pacnew files which you might have
and then perhaps to try to update one by one after you have removed everything that came from AUR.
Only you know what you did - everything is recorded in /var/log/pacman.log so you can look there to refresh your memory.
It lists packages not found in sync databases. So AUR or anything else manually built or anything that was removed from sync dbs. OP clearly has unmaintained system, so have fun fixing it in the next 100 posts.
Firstly, we have no idea what your issue is, apart from your inability to perform an update. You will need to provide useful information so that others might be able to help; nobody here is a mind-reader.
For example, what is the output resulting from your attempts to update? Effectively saying āitās not workingā doesnāt tell us anything. Exactly what have you done (provide the commands) and what output do you see? (errors, warnings, etc).
Please also note that this is the command to perform a Manjaro update:
sudo pacman -Syu
Notice in particular, there is only oney in that command. One y is the correct usage, despite the amount of forum members using two, and claiming otherwise. pacman-mirrors --fasttrack 5 is always a good addition.
A little housekeepingā¦
As a new user, please take some time to familiarise yourself with Forum requirements; in particular, the many ways to use the forum to your benefit. To that end, some or all these links will be invaluable:
And last, but not least, the Stable Update Announcements, which you should check frequently for important update related information. Occasionally an issue might be directly related to a particular update; itās always best to check those announcements.
Hello guys,
thank you all for your responses and forgive me for my incorrect explanation of the question.
I am not a very confident Linux user and have some difficulties in understanding specific technical terms.
However,
Firstly i tried to do a full update of my system, which was working fine before that time.
Updating did not complete successfully due to some problematic dependencies.
Then i rebooted the system, and received an error screen with the text from the topic title and the inability to log into my system.
Then, while reading the Manjaro forum I realized that the problem was in the updating KDE shell. And i tried to solve the problem from other similar forum topics, from where used the commands that I quoted in my first message.
For now, Iām trying to figure it out and do what you kindly shared here, despite my mistakes in post.
Here, you should have taken care of the problematic dependencies, and asked for help if needed while giving the exact command you entered and the output resulting from that command. Good so far?
The error screen as you call it said āThe current theme cannot be loaded due to the errors belowā - that told us nothing - What errors were they?
Throwing commands randomly found in forum threads, when you donāt really know what they do, is a recipe for disaster.
Iām guessing that you somehow managed to leave yourself in a partial update state. There are many similar threads on that topic, and all of them different, with varying solutions. It might even be easier to install Manjaro from scratch; but thatās up to you to decide.
You do not appear to have read any of the links previously posted for you. I suggest you do that before going much further (a does not show that you actually read anything). Here are some more:
Looking through the messages in the console, I was convinced that a large number of system files were being updated and reinstalled.
And in the end, the update was successful and without errors.
However, after rebooting the operating system does not start.
On the black start screen I only see the line: ā/dev/nvme0n1p2: clean, ā¦/ā¦files, ā¦/ā¦blocksā
There are plenty more hints if you follow the links previously given.
Thanks for attempting to make your output more readable, however, you used the wrong character as a backtick. The key you need is usually found under the Esc key (on a normal US keyboard) - it looks like `. Notice itās slanted backwards. Edit that post appropriately to have it display in a neat, tidy, scrollable text box.
Do this outputs working correctly from live-boot after chrooting?
Since he said, he canāt boot regulary. The output commands are normaly working when the install or at least the TTY is working with the default install or not?
There is also something else more fundamentally wrong because many of these āforeignā packages should not be foreign. kio for example is in the repos.
You might want to sort your mirrors
sudo pacman-mirrors -f && sudo pacman -Syu
packagekit should not be used by anyone.
Also heres a thing for if you need TTY or chroot etc.
Iām very sorry, but I canāt provide any command, because i tried to run the system update in graphical mode by clicking on the buttons in the Manjaro System Update window.
As I understand from reading the forum and this topic, I had a partial update.
Now Iām totally lost at understanding what you are doing.
You said:
So:
you are not booting your system, but a live system instead
and then using chroot to get into your actual system
⦠where you then have problems with updating it
The GUI you see in this case is that of the live system.
And you use a terminal to perform the chroot.
From then on you interact via that terminal with your actual system.
The GUI of the live system is, at that time, totally inconsequential.
You work on your system from that terminal only.
Iām at a total loss at following what you are actually doing and where.
sorry for my mistakes in explanation.
If we discard first moment of time what caused the problems,
and take only this current moment of time only.
For now i have actual version of live usb, from whitch i load manjaro in operative memory.
When it loaded, i go to my broken linux through chroot and operate there in konsole. From where i bring logs.