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

I take it you are referring to gwenview. Make sure you have kimageformats installed.


Yes, but it’s not — as @jaramo thinks — because I’ve got more experience as a GNU/Linux user. It’s because I’ve got four years of experience here at the forum, and another year before that on the previous iteration of the forum.

With every Stable Update, it’s the same old song all over: people starting a myriad of threads about the same thing, which was then already pointed out on the Stable Updates announcement thread before they updated their system, and the fact that they’re all posting about the same things illustrates that, not only did they not look at the Announcements thread, but they also never bothered to search the forum for similar threads.

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.


:point_right: Pacnew & Pacsave files - Manjaro Wiki


pacdiff -o

You may need to install pacman-contrib from the repo first before you can use that command.

4 Likes

Ok so here’s how I sroped the pipewire nagging messages that froze my desktop :

sudo pacman -S pipewire-pulse
systemctl --user stop pulseaudio.service
systemctl --user --now enable pipewire pipewire-pulse

Note : there are some packages that are going to be removed

pulseaudio

and

pulseaudio-bluetooth

A reboot after that to make sure all is good.

I’m really loving plasma6 by the way :heart_eyes:

1 Like

pipewire is used by default now.
If you want to switch to it you need only use the metapackage.

sudo pacman -Syu manjaro-pipewire

I’ve tried that but it didn’t work for me.

Without examples we can only wonder.
In most scenarios only installing the metapackage will do all thats needed including replacing packages and services etc.
I suspect it would not fail to do so for you - but possibly the exchange was blocked by something else like an unsupported package.

1 Like

After this update I also updated the kernel to 6.9 from 6.7. This broke the boot splash and now it gets stuck on loading so I had to remove the splash command from grub script thingy.

1 Like

Just posting here in case you run into someone with the same issue, I know it wont be found in this long long thread.
I did have kvantum-qt5 installed. I was able to fix what I found wrong. In VLC there is an option in the interface page of the settings to force window style. you can set it to “qt5ct-style”. Same in Qterminal, in the Appearance you can set the widget style to “qt5ct-style”. QBittorrent was my own stupidity, I was using an old AUR package (unsupported, I know), and switched it to the one in the repo and it followed the kvantum theme.

2 Likes

Both commands resulted in:

==> ERROR: Cannot find the vim -d binary required for viewing differences.

but I tried what @Aragorn said:

and got this:

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

You can install manjaro-pacnew-checker from the repository. It’ll help you handle the .pacnew files.

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?

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

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.

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

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? :sweat_smile:

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

The executable is called pacnew-checker. :wink:

1 Like

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.

1 Like

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

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 :innocent:)

Hello Thunder :wave:

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

Results: Shiny teeth :grin: but still a black screen… :cry:

1 Like

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.


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.

3 Likes

No still the same issue.

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

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
image
i have timeshift activated and when im back to before the upgrade, the issue did not occur
anyone experiencing this issue?

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,