Update 2025-06-23 Breaks the Display of my Laptop's GUI when Invoked from Pamac, Works with Pacman

I’ve postponed this update after I saw its effect and installed a virgin Manjaro-Gnome, but in view of Keep your System Updated and Avoid Partial Updates! and with the hope that it and following ones will remove the issues with this fresh installation¹⁾ I think it’s time to give it a try.

Unfortunately, I’ve no idea of how to install the hoped-for subsequent update (with the repair of the then broken display) afterwards, i.e. that I’d have to do it without a working GUI.

Since the “desktop system” did/does not suffer from any display problems of the new version, I think that differences of the two machines should give an indication of the failure’s reason (details of the both systems can be seen in their inxi outputs contained in the above link¹⁾.) While the desktop has an Intel-only GPU the laptop has a NVIDIA GP107GLM at its side.

If someone can list the commands to install the hoped-for subsequent update per TTY, I might be able to copy them (on the desktop from which I’m writing this) into a file, take that to the laptop and open it there per mc (Midnight Commander) …

While there is no success guarantees attached - from my long experience with Manjaro - user since 2016 - I can say I have had more issues with plain Arch than I ever had with Manjaro.

[HowTo] Updating Manjaro as safely as possible
[root tip] [How To] Update Manjaro the smart way

Issues usually comes from either one or a combination

  • Custom packages (AUR)
  • Nvidia
  • Faulty hardware

Proactive maintenance

  • make a habit of noting when you make configuration changes
  • if you sync an application
    • remove it if you don’t use it
    • long forgotten apps may cause interference
  • stay informed (Announcements threads)
    • incidents on testing or unstable may be equally relevant when packages reach stable branch
  • Comment #2 in the announcement thread informs of known issues
2 Likes

Thanks for answering, but I have unexpected further difficulties.
At first glance of your 2nd link I remembered how easy that should indeed be.
But I didn’t find a way to log into a TTY - it always said “Login incorrect” after I entered the password. Missing keyboard configuration (which works when logging into the GUI)? First time I have that problem with an already running system.
And when I type pacman -$yu into the GUI’s Terminal, it answers
Fehler: Argument »-« übergeben ohne Eingabe auf Standardeingabe.
Sorry for the German, I don’t know how it’s phrased in English. It means something like:
“Error: argument »-« passed without input to standard input”.

btw.: What do you mean with “sync” in this context?

This should a capital S not $.

If you have configured your console keymap - since you are German - it should look like this

 $ cat /etc/vconsole.conf
# Written by systemd-localed(8) or systemd-firstboot(1), read by systemd-localed
# and systemd-vconsole-setup(8). Use localectl(1) to update this file.
KEYMAP=de
FONT=lat2-16
FONT_MAP=8859-1
XKBLAYOUT=de
XKBMODEL=pc105
XKBOPTIONS=terminate:ctrl_alt_bksp

It refers the action of adding an application to the system.

Technically applications consist of one or more packages (archived installation files) which is synced from the official repo to the pacman cache located at /var/cache/pacman/pkg. Only after all required packages are synced (downloaded) successfully the package manager will unpack the archives and run the required installation scripts.

1 Like

It is:
pacman -Syu (it is an upper case letter “s”)

not
pacman -$yu

Perhaps you use a password wit characters that are located differently on an english vs. a german keyboard layout.
Try assuming an english layout (y and z are switched, for example).
Top row letters are qwertz in a german layout, but qwerty in an english one - that’s also where the name for these layout comes from.
Without configuration like @linux-aarhus wrote, the TTY layout will be assumed to be qwerty.

2 Likes

Oh dear! How could I’ve been that blind! :nerd_face:
Reminds me of another (non-electric) pending update: my glasses.
It’s run absolute smoothly now in the GUI’s terminal. Is faster, clearer and with a verbosity that seems to have been removed from pamac and which I missed badly.

That’s just 10 bytes on this system and contains nothing but KEYMAP=de. I never edited it, so I wonder why the rest is missing - which might be responsible for the failure.

Ah well, like a synonym to (keep) install(ed) - no mystery about it.

Well, it would be “worse”. Not really a novel but might make for a conte, with parts of it written with AltGr pressed (which is dead on an American keyboard).

As for the solution, I’d like to mark both posts. Since that’s not possible and @linux-aarhus’ one arrived earlier and contains more info that I appreciate, I’ll mark that one and @Nachlese’s one with a ‘like’ …

… and stay waiting for a further update that will hopefully repair the dconf-issues.

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.