"The current theme cannot be loaded due to the errors below"

after:
boot from live usb,

Tried to update through
manjaro-chroot -a
pacman-mirrors --fasttrack 5 && pacman -Syyu
and there is nothing to help.

then:
pacman -Qm
and have this output:

attica 5.109.0-1
baloo 5.109.0-1
bashrc-manjaro 5.1.016-2
bluez-qt 5.109.0-1
brave-bin 1:1.38.111-1
cantata 2.5.0-3
exifcleaner-bin 3.6.0-4
frameworkintegration 5.109.0-1
google-chrome 109.0.5414.74-1
haskell-x509-store 1.6.9-60
kactivities-stats 5.109.0-1
karchive 5.109.0-1
kauth 5.109.0-1
kbookmarks 5.109.0-1
kcalendarcore 5.109.0-1
kcmutils 5.109.0-1
kcodecs 5.109.0-1
kcolorpicker 0.2.0-1
kcompletion 5.109.0-1
kconfig 5.109.0-1
kconfigwidgets 5.109.0-1
kcoreaddons 5.109.0-1
kcrash 5.109.0-1
kdav 1:5.109.0-1
kdbusaddons 5.109.0-1
kdeclarative 5.109.0-1
kded 5.109.0-1
kdesu 5.109.0-1
kdiagram 2.8.0-1
kdnssd 5.109.0-1
kdoctools 5.109.0-1
kdsoap 2.1.1-1
kfilemetadata 5.109.0-1
kgamma5 5.27.7-1
kglobalaccel 5.109.0-1
kguiaddons 5.109.0-1
kholidays 1:5.109.0-1
ki18n 5.109.0-1
kiconthemes 5.109.0-1
kimageannotator 0.6.1-1
kimageformats 5.109.0-1
kio 5.109.0-2
kirigami-addons 0.11.0-1
kitemmodels 5.109.0-1
kitemviews 5.109.0-1
kjobwidgets 5.109.0-1
knewstuff 5.109.0-1
kpackage 5.109.0-1
kparts 5.109.0-1
kplotting 5.109.0-1
kpty 5.109.0-1
kquickcharts 5.109.0-1
ktextwidgets 5.109.0-1
kunitconversion 5.109.0-1
kuserfeedback 1.2.0-1
kwallet 5.109.0-1
kwayland 5.109.0-1
kwidgetsaddons 5.109.0-1
kwindowsystem 5.109.0-1
kxmlgui 5.109.0-1
libkcddb 23.08.0-1
libkdcraw 23.08.0-1
libqaccessibilityclient 0.4.1-2
libsignon-glib 2.1-6
linux63 6.3.13-2
linux64 6.4.12-1
manjaro-documentation-en 20181009-1
manjaro-firmware 20160419-1
modemmanager-qt 5.109.0-1
networkmanager-qt 5.109.0-1
plasma-framework 5.109.0-1
prison 5.109.0-1
purpose 5.109.0-1
qqc2-desktop-style 5.109.0-1
qt-gstreamer 1.2.0-4
solid 5.109.0-1
sonnet 5.109.0-1
syndication 5.109.0-1
syntax-highlighting 5.109.0-1
systemd-fsck-silent 239-1
telepathy-accounts-signon 2.1-3
telepathy-farstream 0.6.2-7
telepathy-kde-accounts-kcm 23.04.3-1
telepathy-kde-approver 23.04.3-1
telepathy-kde-auth-handler 23.04.3-1
telepathy-kde-call-ui 23.04.3-1
telepathy-kde-common-internals 23.04.3-1
telepathy-kde-contact-list 23.04.3-1
telepathy-kde-contact-runner 23.04.3-1
telepathy-kde-desktop-applets 23.04.3-1
telepathy-kde-filetransfer-handler 23.04.3-1
telepathy-kde-integration-module 23.04.3-1
telepathy-kde-send-file 23.04.3-1
telepathy-kde-text-ui 23.04.3-1
telepathy-logger-qt 17.09.0-1
telepathy-qt 0.9.8-2
threadweaver 5.109.0-1
transcode 1.1.7-41
yay-git 11.1.2.r11.ged2f533-1
youtube-dl 2021.12.17-2

and have no any ideas what i need to do now,
please help to solve

Hi @happy_m, and welcome!

That list does not seem to be from an updated installation, so it seems either:

  1. That list is from an older ISO; or
  2. it is from your installation which is unupdated.

And, AFAIK this command:

…should not list anything to do with:

Mine doesn’t:

$ pacman -Qm | grep bal

So it’s quite obvious to me that something’s messed-up there…

So I’d suggest the following:

  1. Download, dd/etcher/whatever a new ISO to a thumb drive and boot with that.
  2. Enter a chroot environment from there.
  3. Sync the whole system COMPLETELY

How to chroot

  1. Ensure you’ve got a relatively new ISO or at least one with a still supported LTS kernel.

  2. Write/copy/dd the ISO to a USB thumb drive.

  3. When done, boot with the above mentioned USB thumb drive into the live environment.

  4. Once booted, open a terminal and enter the following command to enter the chroot environment:

manjaro-chroot -a
  1. If you have more than one Linux installation, select the correct one to use from the list provided.

When done, you should now be in the chroot environment.

But, be careful, as you’re now in an actual root environment on your computer, so any changes you make will persist after a restart.

Once you’ve chrooted successfully, run the following to re-sync the complete system:

pamac upgrade --no-aur

Reboot and see what happens. We’re not done if everything works, though, But test, and provide any and all errors you might get.

2 Likes

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.

1 Like

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. :stuck_out_tongue:

2 Likes

Hi @happy_m and welcome to the Manjaro community.

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 one y 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.

I hope this helps. Cheers.

3 Likes

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.

1 Like

Let’s try to address what you have done so far:

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 :heart: does not show that you actually read anything). Here are some more:

If these guides and tutorials are too much, you might also consider:

I hope this helps. Cheers.

1 Like

I repeated the steps that you described here.

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’

Thank you for your hint about the place where I can look at the logs.

Early I tried to update this system from time to time, but the update failed every time and aborted the operation.

Here is the log from the moment I started trying to fix the system update:

......
[2024-02-18T15:25:29+0200] [PACKAGEKIT] synchronizing package lists
[2024-02-19T14:17:21+0200] [PACKAGEKIT] synchronizing package lists
[2024-02-20T05:48:59+0200] [PACMAN] Running 'pacman -Syu'
[2024-02-20T05:48:59+0200] [PACMAN] synchronizing package lists
[2024-02-20T05:49:12+0200] [ALPM] running '00-timeshift-autosnap.hook'...
[2024-02-20T05:49:12+0200] [ALPM-SCRIPTLET] ==> skipping timeshift-autosnap due skipRsyncAutosnap in /etc/timeshift-autosnap.conf set to TRUE.
[2024-02-20T05:49:12+0200] [ALPM] running '05-snap-pac-pre.hook'...
[2024-02-20T05:49:12+0200] [ALPM] transaction started
[2024-02-20T05:49:12+0200] [ALPM] upgraded archlinux-keyring (20230821-1 -> 20231222-1)
[2024-02-20T05:49:12+0200] [ALPM-SCRIPTLET] ==> Adding keys from a file 'archlinux.gpg'...
[2024-02-20T05:49:15+0200] [ALPM-SCRIPTLET] ==> Local signing of trusted keys in a keychain...
[2024-02-20T05:49:15+0200] [ALPM-SCRIPTLET]   -> Locally signed 1 keys.
[2024-02-20T05:49:15+0200] [ALPM-SCRIPTLET] ==> Importing owner trust values...
[2024-02-20T05:49:15+0200] [ALPM-SCRIPTLET] gpg: inserting ownertrust of 4
[2024-02-20T05:49:15+0200] [ALPM-SCRIPTLET] ==> Blocking revoked keys...
[2024-02-20T05:49:15+0200] [ALPM-SCRIPTLET]   -> Disabled 8 keys.
[2024-02-20T05:49:15+0200] [ALPM-SCRIPTLET] ==> Updating the trust table...
[2024-02-20T05:49:16+0200] [ALPM-SCRIPTLET] gpg: marginals needed: 3  completes needed: 1  trust model: pgp
[2024-02-20T05:49:16+0200] [ALPM-SCRIPTLET] gpg: depth: 0  reliable:   1  signed:  24  trust: 0-, 0q, 0n, 0m, 0f, 1u
[2024-02-20T05:49:16+0200] [ALPM-SCRIPTLET] gpg: depth: 1  reliable:  24  signed: 101  trust: 0-, 0q, 0n, 24m, 0f, 0u
[2024-02-20T05:49:16+0200] [ALPM-SCRIPTLET] gpg: depth: 2  reliable:  74  signed:  29  trust: 74-, 0q, 0n, 0m, 0f, 0u
[2024-02-20T05:49:16+0200] [ALPM-SCRIPTLET] gpg: due date for next trust table check 2024-04-10
[2024-02-20T05:49:16+0200] [ALPM] transaction completed
[2024-02-20T05:49:16+0200] [ALPM] running '30-systemd-daemon-reload.hook'...
[2024-02-20T05:49:16+0200] [ALPM] running '30-systemd-update.hook'...
[2024-02-20T05:49:16+0200] [ALPM] running '90-packagekit-refresh.hook'...
[2024-02-20T05:49:16+0200] [ALPM] running 'zz-snap-pac-post.hook'...
[2024-02-20T05:49:16+0200] [PACMAN] starting full system upgrade
[2024-02-20T05:51:54+0200] [PAMAC] synchronizing package lists
[2024-02-20T05:54:33+0200] [PACKAGEKIT] synchronizing package lists
[2024-02-20T13:34:00+0200] [PACKAGEKIT] synchronizing package lists
.......
[2024-03-04T13:56:17+0200] [PACKAGEKIT] synchronizing package lists
[2024-03-04T17:59:10+0200] [PACKAGEKIT] synchronizing package lists
[2024-03-04T18:07:50+0200] [PACMAN] Running 'pacman -S snapd'
[2024-03-04T18:08:06+0200] [ALPM] running '00-timeshift-autosnap.hook'...
[2024-03-04T18:08:06+0200] [ALPM-SCRIPTLET] ==> skipping timeshift-autosnap due skipRsyncAutosnap in /etc/timeshift-autosnap.conf set to TRUE.
[2024-03-04T18:08:06+0200] [ALPM] running '05-snap-pac-pre.hook'...
[2024-03-04T18:08:06+0200] [ALPM] transaction started
[2024-03-04T18:08:06+0200] [ALPM] upgraded snapd (2.60.2-1 -> 2.61.1-1)
[2024-03-04T18:08:06+0200] [ALPM] transaction completed
[2024-03-04T18:08:06+0200] [ALPM] running '30-systemd-daemon-reload.hook'...
[2024-03-04T18:08:07+0200] [ALPM] running '30-systemd-tmpfiles.hook'...
[2024-03-04T18:08:07+0200] [ALPM] running '30-systemd-update.hook'...
[2024-03-04T18:08:07+0200] [ALPM] running '90-packagekit-refresh.hook'...
[2024-03-04T18:08:07+0200] [ALPM] running 'dbus-reload.hook'...
[2024-03-04T18:08:07+0200] [ALPM] running 'update-desktop-database.hook'...
[2024-03-04T18:08:07+0200] [ALPM] running 'zz-snap-pac-post.hook'...
[2024-03-04T18:12:08+0200] [ALPM] running '05-snap-pac-pre.hook'...
[2024-03-04T18:12:08+0200] [ALPM] transaction started
[2024-03-04T18:12:08+0200] [ALPM] removed telegram-desktop (4.9.3-1)
[2024-03-04T18:12:08+0200] [ALPM] transaction completed
[2024-03-04T18:12:08+0200] [ALPM] running '30-systemd-update.hook'...
[2024-03-04T18:12:08+0200] [ALPM] running '90-packagekit-refresh.hook'...

could this be useful information for a solution, or do I need to provide more logs, or should I be looking for something specific?

Possibly.

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.

Additionally, the outputs of:

inxi --admin --verbosity=8 --filter --no-host --width

and

journalctl --boot=-1 --priority=3 --catalog --no-pager

may also be useful - these too were in the links previously given; possibly in the very first one.

Cheers.

2 Likes
please format terminal output like this:
[2024-02-18T15:25:29+0200] [PACKAGEKIT] synchronizing package lists
[2024-02-19T14:17:21+0200] [PACKAGEKIT] synchronizing package lists
[2024-02-20T05:48:59+0200] [PACMAN] Running ā€˜pacman -Syu’
[2024-02-20T05:48:59+0200] [PACMAN] synchronizing package lists
[2024-02-20T05:49:12+0200] [ALPM] running ā€˜00-timeshift-autosnap.hook’…
[2024-02-20T05:49:12+0200] [ALPM-SCRIPTLET] ==> skipping timeshift-autosnap due skipRsyncAutosnap in /etc/timeshift-autosnap.conf set to TRUE.
[2024-02-20T05:49:12+0200] [ALPM] running ā€˜05-snap-pac-pre.hook’…
[2024-02-20T05:49:12+0200] [ALPM] transaction started
[2024-02-20T05:49:12+0200] [ALPM] upgraded archlinux-keyring (20230821-1 → 20231222-1)
[2024-02-20T05:49:12+0200] [ALPM-SCRIPTLET] ==> Adding keys from a file ā€˜archlinux.gpg’…
[2024-02-20T05:49:15+0200] [ALPM-SCRIPTLET] ==> Local signing of trusted keys in a keychain…
[2024-02-20T05:49:15+0200] [ALPM-SCRIPTLET] → Locally signed 1 keys.
[2024-02-20T05:49:15+0200] [ALPM-SCRIPTLET] ==> Importing owner trust values…
[2024-02-20T05:49:15+0200] [ALPM-SCRIPTLET] gpg: inserting ownertrust of 4
[2024-02-20T05:49:15+0200] [ALPM-SCRIPTLET] ==> Blocking revoked keys…
[2024-02-20T05:49:15+0200] [ALPM-SCRIPTLET] → Disabled 8 keys.
[2024-02-20T05:49:15+0200] [ALPM-SCRIPTLET] ==> Updating the trust table…
[2024-02-20T05:49:16+0200] [ALPM-SCRIPTLET] gpg: marginals needed: 3 completes needed: 1 trust model: pgp
[2024-02-20T05:49:16+0200] [ALPM-SCRIPTLET] gpg: depth: 0 reliable: 1 signed: 24 trust: 0-, 0q, 0n, 0m, 0f, 1u
[2024-02-20T05:49:16+0200] [ALPM-SCRIPTLET] gpg: depth: 1 reliable: 24 signed: 101 trust: 0-, 0q, 0n, 24m, 0f, 0u
[2024-02-20T05:49:16+0200] [ALPM-SCRIPTLET] gpg: depth: 2 reliable: 74 signed: 29 trust: 74-, 0q, 0n, 0m, 0f, 0u
[2024-02-20T05:49:16+0200] [ALPM-SCRIPTLET] gpg: due date for next trust table check 2024-04-10
[2024-02-20T05:49:16+0200] [ALPM] transaction completed
[2024-02-20T05:49:16+0200] [ALPM] running ā€˜30-systemd-daemon-reload.hook’…
[2024-02-20T05:49:16+0200] [ALPM] running ā€˜30-systemd-update.hook’…
[2024-02-20T05:49:16+0200] [ALPM] running ā€˜90-packagekit-refresh.hook’…
[2024-02-20T05:49:16+0200] [ALPM] running ā€˜zz-snap-pac-post.hook’…
[2024-02-20T05:49:16+0200] [PACMAN] starting full system upgrade
[2024-02-20T05:51:54+0200] [PAMAC] synchronizing package lists
[2024-02-20T05:54:33+0200] [PACKAGEKIT] synchronizing package lists
[2024-02-20T13:34:00+0200] [PACKAGEKIT] synchronizing package lists
…
[2024-03-04T13:56:17+0200] [PACKAGEKIT] synchronizing package lists
[2024-03-04T17:59:10+0200] [PACKAGEKIT] synchronizing package lists
[2024-03-04T18:07:50+0200] [PACMAN] Running ā€˜pacman -S snapd’
[2024-03-04T18:08:06+0200] [ALPM] running ā€˜00-timeshift-autosnap.hook’…
[2024-03-04T18:08:06+0200] [ALPM-SCRIPTLET] ==> skipping timeshift-autosnap due skipRsyncAutosnap in /etc/timeshift-autosnap.conf set to TRUE.
[2024-03-04T18:08:06+0200] [ALPM] running ā€˜05-snap-pac-pre.hook’…
[2024-03-04T18:08:06+0200] [ALPM] transaction started
[2024-03-04T18:08:06+0200] [ALPM] upgraded snapd (2.60.2-1 → 2.61.1-1)
[2024-03-04T18:08:06+0200] [ALPM] transaction completed
[2024-03-04T18:08:06+0200] [ALPM] running ā€˜30-systemd-daemon-reload.hook’…
[2024-03-04T18:08:07+0200] [ALPM] running ā€˜30-systemd-tmpfiles.hook’…
[2024-03-04T18:08:07+0200] [ALPM] running ā€˜30-systemd-update.hook’…
[2024-03-04T18:08:07+0200] [ALPM] running ā€˜90-packagekit-refresh.hook’…
[2024-03-04T18:08:07+0200] [ALPM] running ā€˜dbus-reload.hook’…
[2024-03-04T18:08:07+0200] [ALPM] running ā€˜update-desktop-database.hook’…
[2024-03-04T18:08:07+0200] [ALPM] running ā€˜zz-snap-pac-post.hook’…
[2024-03-04T18:12:08+0200] [ALPM] running ā€˜05-snap-pac-pre.hook’…
[2024-03-04T18:12:08+0200] [ALPM] transaction started
[2024-03-04T18:12:08+0200] [ALPM] removed telegram-desktop (4.9.3-1)
[2024-03-04T18:12:08+0200] [ALPM] transaction completed
[2024-03-04T18:12:08+0200] [ALPM] running ā€˜30-systemd-update.hook’…
[2024-03-04T18:12:08+0200] [ALPM] running ā€˜90-packagekit-refresh.hook’…

click the line or the arrow

in between three backticks ``` at the beginning and at the end
or use the symbol </> in the edit window

Provide the command you run and all it’s output so we can see what you try to do and why it doesn’t work.

3 Likes

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?

As he said - it’s from inside chroot - which is as good as if the system itself was booted.

1 Like

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.

1 Like

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.

And after that partial update on start i recieved screen like this:
https://forums.opensuse.org/uploads/default/original/2X/d/d37b67e8de68bb0aece49bd524d7761022d039d9.jpeg

Please note, this is not my screenshot. I just had the same visual appearance.

yes, moment of chrooting looks like this:

 ļŒ’ ī‚°  ~ ī‚° manjaro-chroot -a                                                                                                                            āœ” 
grub-probe: error: cannot find a GRUB drive for /dev/sdb1.  Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sdb1.  Check your device.map.
==> Mounting (ManjaroLinux) [/dev/nvme0n1p2]
 --> mount: [/mnt]
 --> mount: [/mnt/boot/efi]
[manjaro /]# 

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.

1 Like

@Nachlese just confirmed that you can provide commands, since you can post your journal and inxi after you doing a chroot command from your Live Boot.

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.

That inxi output looks strange :face_with_raised_eyebrow:

The most stuff is missing… i have no clue if that is normal when doing liveboot+ chroot + inxi or what’s going on here.