[Stable Update] 2024-05-13 - Kernels, Plasma 6, Gnome 46, LxQT 2.0, Nvidia, Pacman

[Aragorn]

@Randomname123

Thanks i’ll try that, but my initial issue is that I cannot access the TTY, whenever I try to it just goes to a blank screen (no text, login prompt or anything) and this happened even before I did the update but I don’t know how long its been like that it used to work before… all I can do is control+alt+F2 to go back to the GUI again…

Will managing the .pacnew files with manjaro-pacnew-checker help solve this problem?

I do not know, but mkinitcpio.conf.pacnew might be relevant, as it does contain some important changes.

For that matter, you can run the manjaro-pacnew-checker utility from a terminal window, or even from the application launcher — it’s GUI-based.

@Randomname123

Edit: sorry I re-posted this to show as a reply, i’m kind of still new in the forums

If you’re replying directly to only one person and you’re quoting their whole post, then Discourse — the forum engine we use — will remove the quoted section. Don’t worry about it.

[Randomname123]

@Aragorn

For that matter, you can run the manjaro-pacnew-checker utility from a terminal window, or even from the application launcher — it’s GUI-based.

Erm… I copy pasted manjaro-pacnew-checker in the terminal but it says bash: manjaro-pacnew-checker: command not found even after installing it (from pamac GUI)… I can’t find it in the application menu either, there is no entry with that name?

@Aragorn

If you’re replying directly to only one person and you’re quoting their whole post, then Discourse — the forum engine we use — will remove the quoted section. Don’t worry about it.

Discourse seems like a pretty cool engine though… It’s got nice editing features for quoting replies and stuff…

[Aragorn]

@Randomname123

Erm… I copy pasted manjaro-pacnew-checker in the terminal but it says bash: manjaro-pacnew-checker: command not found even after installing it (from pamac GUI)… I can’t find it in the application menu either, there is no entry with that name?

The executable is called pacnew-checker.

[soundofthunder]

@Randomname123

I cannot access the TTY, whenever I try to, it just goes to a blank screen (no text, login prompt or anything)

Sometimes, you might need to wait for the prompt to show; it could only be a few seconds, or even up to 30 seconds on some machines; potentially longer on some VM’s.

I would test that to see if it may be the case on your machine, before completely writing it off as not working.

[Randomname123]

Ah um… yes… ofc… *ehem* using the right executable in the first place would definitely help… (but how was I supposed to know that? )

Ok so now it’s asking me for each of:

/etc/passwd.pacnew
/etc/shells.pacnew
/etc/pam.d/kde.pacnew
/etc/mkinitcpio.conf.pacnew
/etc/pacman.conf.pacnew

If I want to:

1. View and merge
2. Keep the original and remove the pacnew file
3. Replace the original with the pacnew file
4. Do nothing
5. Ask Aragorn for help (ok maybe I made this one up but it was implicitly implied )

@soundofthunder

Sometimes, you might need to wait for the prompt to show; it could only be a few seconds, or even up to 30 seconds on some machines; potentially longer on some VM’s.

I would test that to see if it may be the case on your machine, before completely writing it off as not working.

Hello Thunder

Yeah I thought about that too, so I switched to a TTY and went to brush my teeth and came back…

Results: Shiny teeth but still a black screen…

[Aragorn]

@Randomname123

If I want to:

1. View and merge
2. Keep the original and remove the pacnew file
3. Replace the original with the pacnew file
4. Do nothing
5. Ask Aragorn for help (ok maybe I made this one up but it was implicitly implied )

View and merge. Look at what is new in the .pacnew file and merge it in with your existing configuration file, if applicable. Never blindly copy the .pacnew over the existing file.

---

@jaramo

@Aragorn

The problem is with the laziness and self-centered attitude of the people themselves. And it does get tiresome having to explain the same thing over and over and over again, and with each and every Stable Update.

The thing is that this could be addressed by what I was suggesting: Having a clear statement what the Manjaro way of doing things is in a easily found (or pointed to) place that in turn links to further resources on how to do them.

With Manjaro being based upon Arch, this should be implicit knowledge.

Unfortunately, an earlier version of Manjaro’s main website falsely claimed that Manjaro was a suitable distribution for absolute beginners, which is absolutely not the case. Not to toot my own horn, but it was yours truly who brought this discrepancy to the attention of the team, which then resulted in a rewrite — not by myself, though — of the text on the main Manjaro web page.

[ipolit]

No still the same issue.

[baeric]

I use the HighContract Icons and have the following small issues:

• Application Launcher has the default fedora icon
  • When I go through “Configure Application Launcher” and search the icons there are currently only colored manjaro icons
• dolphin has the default icon
  • When I go through “Edit Applications” also only a colored one

Before the latest update the icons existed

https://paste.pics/d2c3100d70409064231615d5f67b50b2

[BlackMagic]

i am currently experiencing an issue due to the update. before the upgrade i can connect my openvpn , now the connection keep restarted without being connected

i have timeshift activated and when im back to before the upgrade, the issue did not occur
anyone experiencing this issue?

[ferdinan]

After update 2024-05-13 manjaro gnome can´t start.

Intel core 2 linux 5.15 ATI whithe xf86-video-ati X11 session here some errors at start:
File /var/log/journal/e945672d862f45acb827e859f2c9c028/system.journal corrupted or uncleanly shut down, renaming and replacing.
kernel: intel_rng: Firmware space is locked read-only. If you can’t or
intel_rng: don’t want to disable this in firmware setup, and if
intel_rng: you are certain that your system has a functional
radeon 0000:01:00.0: Direct firmware load for radeon/CAICOS_pfp.bin failed with error -2
may 13 18:36:00 casa kernel: ni_cp: Failed to load firmware “radeon/CAICOS_pfp.bin”
kernel: [drm:evergreen_init [radeon]] *ERROR* Failed to load firmware!
radeon 0000:01:00.0: Fatal error during GPU init
radeon: probe of 0000:01:00.0 failed with error -2
r8169 0000:03:00.0: Direct firmware load for rtl_nic/rtl8168d-1.fw failed with error -2
may 13 18:36:11 casa kernel: r8169 0000:03:00.0: Unable to load firmware rtl_nic/rtl8168d-1.fw (-2)
/usr/lib/gdm-x-session[597]: ATI Radeon HD 4850 x2, ATI FirePro V8750 (FireGL),
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: ATI FirePro V7760 (FireGL), ATI Mobility RADEON HD 4850,
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: ATI Mobility RADEON HD 4850 X2, ATI FirePro RV770,
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: AMD FireStream 9270, AMD FireStream 9250, ATI FirePro V8700 (FireGL),
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: ATI Mobility RADEON HD 4870, ATI Mobility RADEON M98,
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: ATI FirePro M7750, ATI M98, ATI Mobility Radeon HD 4650,
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: ATI Radeon RV730 (AGP), ATI Mobility Radeon HD 4670,
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: ATI FirePro M5750, ATI RV730XT [Radeon HD 4670], ATI RADEON E4600,
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: ATI Radeon HD 4600 Series, ATI RV730 PRO [Radeon HD 4650],
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: ATI FirePro V7750 (FireGL), ATI FirePro V5700 (FireGL),
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: ATI FirePro V3750 (FireGL), ATI Mobility Radeon HD 4830,
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: ATI Mobility Radeon HD 4850, ATI FirePro M7740, ATI RV740,
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: ATI Radeon HD 4770, ATI Radeon HD 4700 Series, ATI RV610,
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: ATI Radeon HD 2400 XT, ATI Radeon HD 2400 Pro,
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: ATI Radeon HD 2400 PRO AGP, ATI FireGL V4000, ATI Radeon HD 2350,
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: ATI Mobility Radeon HD 2400 XT, ATI Mobility Radeon HD 2400,
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: ATI RADEON E2400, ATI FireMV 2260, ATI RV670, ATI Radeon HD3870,
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: ATI Mobility Radeon HD 3850, ATI Radeon HD3850,
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: ATI Mobility Radeon HD 3850 X2, ATI Mobility Radeon HD 3870,
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: ATI Mobility Radeon HD 3870 X2, ATI Radeon HD3870 X2,
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: ATI FireGL V7700, ATI Radeon HD3690, AMD Firestream 9170,
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: ATI Radeon HD 4550, ATI Radeon RV710, ATI Radeon HD 4350,
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: ATI Mobility Radeon 4300 Series, ATI Mobility Radeon 4500 Series,
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: ATI FirePro RG220, ATI Mobility Radeon 4330, ATI RV630,
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: ATI Mobility Radeon HD 2600, ATI Mobility Radeon HD 2600 XT,
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: ATI Radeon HD 2600 XT AGP, ATI Radeon HD 2600 Pro AGP,
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: ATI Radeon HD 2600 XT, ATI Radeon HD 2600 Pro, ATI Gemini RV630,
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: ATI Gemini Mobility Radeon HD 2600 XT, ATI FireGL V5600,
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: ATI FireGL V3600, ATI Radeon HD 2600 LE,
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: ATI Mobility FireGL Graphics Processor, ATI Radeon HD 3470,
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: ATI Mobility Radeon HD 3430, ATI Mobility Radeon HD 3400 Series,
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: ATI Radeon HD 3450, ATI Radeon HD 3430, ATI FirePro V3700,
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: ATI FireMV 2450, ATI Radeon HD 3600 Series, ATI Radeon HD 3650 AGP,
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: ATI Radeon HD 3600 PRO, ATI Radeon HD 3600 XT,
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: ATI Mobility Radeon HD 3650, ATI Mobility Radeon HD 3670,
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: ATI Mobility FireGL V5700, ATI Mobility FireGL V5725,
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: ATI Radeon HD 3200 Graphics, ATI Radeon 3100 Graphics,
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: ATI Radeon HD 3300 Graphics, ATI Radeon 3000 Graphics, SUMO, SUMO2,
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: ATI Radeon HD 4200, ATI Radeon 4100, ATI Mobility Radeon HD 4200,
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: ATI Mobility Radeon 4100, ATI Radeon HD 4290, ATI Radeon HD 4250,
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: AMD Radeon HD 6310 Graphics, AMD Radeon HD 6250 Graphics,
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: AMD Radeon HD 6300 Series Graphics,
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: AMD Radeon HD 6200 Series Graphics, PALM, CYPRESS,
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: ATI FirePro (FireGL) Graphics Adapter, AMD Firestream 9370,
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: AMD Firestream 9350, ATI Radeon HD 5800 Series,
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: ATI Radeon HD 5900 Series, ATI Mobility Radeon HD 5800 Series,
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: ATI Radeon HD 5700 Series, ATI Radeon HD 6700 Series,
may 13 18:36:28 casa /usr/lib/gdm-x-session[597]: ATI Mobility Radeon HD 5000 Series, ATI Mobility Radeon HD 5570,

[anon51566685]

[HowTo] Post command output and file content as formatted text

Difficulty: ★☆☆☆☆ Formatting differences Discourse – this forum’s engine – uses Markdown to format its posts, and removes “unnecessary” whitespace. Terminal commands often produce output formatted so that they are better readable by the user, taking advantage of the monospaced font used. Programming code often rely on indentation to make it more readable. Using preformatting in Markdown Markdown includes a pattern to provide preformatting when necessary. You only need to put the part to form…

(This should seriously be put on a red blinking banner on the front page.)

[bogota]

@Marsa

By the way, about your error message quote, you have to select the text before pressing Ctrl+e.

no change after the command and/or reboot…

what does this mean “By the way, about your error message quote, you have to select the text before pressing Ctrl+e.”

[Mirdarthos]

It will still be ignored…

[nikgnomic]

If pipewire-pulse is installed to replace pulseaudio & pulseaudio-bluetooth and system is restarted, there is no need to stop pulseaudio.service because the service is no longer present
Also no need to enable and start pipewire and pipewire-pulse services because they are usually enabled and started automatically

[glottophilos]

Got it, my apologies, didn’t mean to astound you, but you’re quite right that it doesn’t show up via a search in system settings which is how I had been accustomed to accessing it so I thought I would ask, and I appreciate the clarification since I didn’t see it mentioned in the changes notes up above either.

Since that’s dealt with and is clearly unrelated to the other issue at this point, do we have any ideas as to what might be going on with the ethernet port? It’s rather concerning that that is rendered useless with the new kernel and I’m afraid that’s rather above my paygrade in terms of troubleshooting.

[agolovanov]

Surprisingly, I have an issue only with the GNOME update. Some of the tray icons look weird now, noticeably lower resolution than they are supposed to be, see the MEGASync (red) and the Telegram (blue with the barely readable message counter) ones.

Before the update, they used to be good. Does anyone know what might cause this? I’m running Wayland at 100% scaling.

[1efaf7d71a8637c6800a]

Sorry, but where and why did Phil’s / Linux-Aarhus’ linux-firmware important message at the top go? Was it replaced by 6.7 EOL?

[beermad]

@Randomname123

Ah um… yes… ofc… ehem using the right executable in the first place would definitely help… (but how was I supposed to know that? )

Simple trick for you. After you’ve installed the package, look at the “files” tab in its entry in pamac-manager. The executable’s name will be shown in /usr/bin (or possibly just /bin). It’s amazing how often I’ve needed this after installing something.

[tomthecat]

I anybody else encounters this problem:

I did set up a virtual display on my large 4K screen, see:

Setup virtual display with xrandr

this is my setup: the widescreen and the laptop screen and I am only sharing the the red frame DP1-2 [grafik] what I don’t get is this: does the “5360 x 1440” have to include DP1-1 and eDP1? and I am not sure why I get the notification for the missing " ] " when running the script a second time.

Very useful for video conferences. However, after the update, all I could see was a black screen with just the mouse pointer showing up. To resolve this issue, I switched to the console and renamed the virtmon.sh script, which allowed me to return to normal operations.

[FancierTech]

thank you