[Stable Update] 2023-06-04 - Kernels, Gnome 44.1, Plasma 5.27.5, Python 3.11, Toolchain, Firefox

cfinnberg · 4 June 2023 15:38

After the update the list should be much shorter (or empty). After the update you run the command again and all packages that show up in the list must be rebuilt

linub · 4 June 2023 15:40

with this command?
pamac build $(pacman -Qoq /usr/lib/python3.10)

Aragorn · 4 June 2023 15:40

After updating, there should no longer be a /usr/lib/python3.10/ directory. If you still have one, then everything that remains in there needs to be rebuilt.

Updated kernels are on the way. They’ll probably be on your local mirrors in a few hours, or possibly — if your selected mirrors are slow — by tomorrow.

cfinnberg · 4 June 2023 15:41

That will rebuild all packages that are in the list. You can also rebuild them one by one if you want

linub · 4 June 2023 15:43

Thank you both.

Aragorn · 4 June 2023 16:08

Well, I do have a bit of an issue after this update, albeit that it’s not important enough to include it in my vote on the poll, because it’s not actually a Manjaro problem. Chromium is a package we pull in from Arch, but even Arch doesn’t maintain this software — Google does, as a “community-developed project” that serves as the basis for their proprietary Chromium browser.

The thing is that the new version of Chromium insists on using a dark theme everywhere. I’ve already tried to disable it using the chrome://flags — but it’s simply ignoring those — and by explicitly choosing a light theme on websites that support doing so.

And yes, I am using a dark theme for my Plasma settings, but up until now Chromium has always used a light theme by default, including on its settings pages.

And Google’s help — which is more about Chrome than about Chromium — is, um, no help at all. I found a few threads started by people with the same issue, but they were closed before anyone could reply on them, notwithstanding that dozens of people clicked the I have the same problem button.

Typically Google and their narcissistic arrogance, of course.

bedna · 4 June 2023 16:11

After reboot I got stuck on the “Manjaro …” screen. Tried changing tty but to no effort.
ctrl+alt+del and it rebooted without issues.

myCatnip · 4 June 2023 16:27

Ridiculously complex? Not sure we are looking at the same thing here… I’m seeing a very clear and simple explanation of exactly what cases need attention, a one liner to show you what needs attention, and a one liner to try and fix it all. Finally there’s a tool to check if anything else still needs to be fixed. Literally 3 spoon fed steps is ridiculously complex?

Cl00e9ment · 4 June 2023 16:28

After the update and reboot, instead of seeing GDM, I got granted by a tty asking me to log in.
I tried to reboot multiple times but it was always the same.
I eventually reverted the update with Timeshift to get a working system.

Yochanan · 4 June 2023 16:38

Chromium 114 now goes by the Gtk theme. There are plenty of people also complaining in upstream bug reports as well.

There are no flags. enable-force-dark is not related.

For now, you can use a light Gtk theme and make sure gtk-application-prefer-dark-theme is set to 0 in ~/.config/gtk-3.0/settings.ini.

philm · 4 June 2023 16:55

Sometimes this happens, especially when you use Gnome. Also bigger updates it is better not to use the graphical environment and their package managers. pamac and pacman both work fine in a TTY

matt-hires · 4 June 2023 16:59

@philm thanks for recompiling the kernels

Keruskerfuerst · 4 June 2023 17:04

I have two computers running XFCE.
On both computers, thunderbird starts only after the second attempt.
(First click to start thunderbird does not start it, the second time start thunderbird).

lir5 · 4 June 2023 17:11

Don’t know for chromium, but on ungoogled-chromium (113.0.5672.126, using chaotic aur build) you can switch between classic (light theme) and gtk theme (hits the system theme).

pheiduck · 4 June 2023 17:19

See wiki-post:

philm:

Many applications (firefox, thunderbird, etc) slow to start on desktops other than Gnome

There is a bug with xdg-desktop-portal-gnome (more details here ).

Workaround for gtk-based desktops (including Xfce)
sudo pacman -Rdd xdg-desktop-portal-gnome
sudo pacman -S xdg-desktop-portal-gtk

FancierTech · 4 June 2023 17:24

This update was the strangest one for me… Let me explain:

Update and reboot
Stuck on “Failed to start Load Kernel Module” (I used 5.15 LTS)
Somehow after 2-3 tries the only TTY-2 has been worked
I found out how to install a new kernel and then reboot (update to 6.1 LTS)
KDE Plasma totally lost its theme configurations and any commands in Konsole gave result like there wasn’t any arguments for anything (for example, pacman -Qoq /usr/lib/python3.10/ command gave me only the list of commands like “pacman list, install, update…” and pamac GUI couldn’t do anything and even didn’t ask password to enter the settings)
After resetting language to English and a few reboots later, everything has started to work normally as expected.
I still cannot run kernel 5.15 (see p.2)

So… What the was that… Idk, like I don’t know if I can fix the issue with 5.15 or should just wait for the further updates keep using 6.1

Ros · 4 June 2023 18:05

Dolphin was quickly upgraded

weingeist · 4 June 2023 18:16

Jun 04 20:06:58 weingeist-PC avahi-daemon[885]: *** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is th>
Jun 04 20:06:58 weingeist-PC avahi-daemon[885]: *** WARNING: Detected another IPv6 mDNS stack running on this host. This makes mDNS unreliable and is th>
Jun 04 20:07:03 weingeist-PC avahi-daemon[885]: Host name conflict, retrying with weingeist-PC-2

thats new

systemctl status systemd-resolved.service                                                                                   INT ✘  3m 7s  
● systemd-resolved.service - Network Name Resolution
     Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; enabled; preset: enabled)
     Active: active (running) since Sun 2023-06-04 20:06:58 CEST; 11min ago
       Docs: man:systemd-resolved.service(8)
             man:org.freedesktop.resolve1(5)
             https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
             https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
   Main PID: 812 (systemd-resolve)
     Status: "Processing requests..."
      Tasks: 1 (limit: 14157)
     Memory: 6.5M
        CPU: 126ms
     CGroup: /system.slice/systemd-resolved.service
             └─812 /usr/lib/systemd/systemd-resolved

Jun 04 20:06:58 weingeist-PC systemd-resolved[812]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Jun 04 20:06:58 weingeist-PC systemd-resolved[812]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in->
Jun 04 20:06:58 weingeist-PC systemd-resolved[812]: Using system hostname 'weingeist-PC'.
Jun 04 20:06:58 weingeist-PC systemd[1]: Started Network Name Resolution.
Jun 04 20:07:03 weingeist-PC systemd-resolved[812]: enp0s25: Bus client set default route setting: yes
Jun 04 20:07:03 weingeist-PC systemd-resolved[812]: enp0s25: Bus client set DNS server list to: fd00::464e:6dff:feb2:1640, 2a03:e440:800:e800:464e:6dff:>
Jun 04 20:07:03 weingeist-PC systemd-resolved[812]: enp0s25: Bus client set search domain list to: fritz.box
Jun 04 20:07:03 weingeist-PC systemd-resolved[812]: enp0s25: Bus client set DNS server list to: 192.168.0.1, fd00::464e:6dff:feb2:1640, 2a03:e440:800:e8>
Jun 04 20:08:14 weingeist-PC systemd-resolved[812]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 192.168.0.1.
Jun 04 20:08:14 weingeist-PC systemd-resolved[812]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 192.168.0.1.

systemctl status avahi-daemon                                                                                                  ✔  1m 37s  
● avahi-daemon.service - Avahi mDNS/DNS-SD Stack
     Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.service; enabled; preset: disabled)
     Active: active (running) since Sun 2023-06-04 20:06:58 CEST; 12min ago
TriggeredBy: ● avahi-daemon.socket
   Main PID: 885 (avahi-daemon)
     Status: "avahi-daemon 0.8 starting up."
      Tasks: 2 (limit: 14157)
     Memory: 1.2M
        CPU: 29ms
     CGroup: /system.slice/avahi-daemon.service
             ├─885 "avahi-daemon: running [weingeist-PC-2.local]"
             └─896 "avahi-daemon: chroot helper"

Jun 04 20:07:03 weingeist-PC avahi-daemon[885]: Withdrawing address record for ::1 on lo.
Jun 04 20:07:03 weingeist-PC avahi-daemon[885]: Withdrawing address record for 127.0.0.1 on lo.
Jun 04 20:07:03 weingeist-PC avahi-daemon[885]: Host name conflict, retrying with weingeist-PC-2
Jun 04 20:07:03 weingeist-PC avahi-daemon[885]: Registering new address record for 2a03:e440:800:e800:1119:de8c:5d01:d82c on enp0s25.*.
Jun 04 20:07:03 weingeist-PC avahi-daemon[885]: Registering new address record for ::1 on lo.*.
Jun 04 20:07:03 weingeist-PC avahi-daemon[885]: Registering new address record for 127.0.0.1 on lo.IPv4.
Jun 04 20:07:03 weingeist-PC avahi-daemon[885]: Joining mDNS multicast group on interface enp0s25.IPv4 with address 192.168.0.2.
Jun 04 20:07:03 weingeist-PC avahi-daemon[885]: New relevant interface enp0s25.IPv4 for mDNS.
Jun 04 20:07:03 weingeist-PC avahi-daemon[885]: Registering new address record for 192.168.0.2 on enp0s25.IPv4.
Jun 04 20:07:05 weingeist-PC avahi-daemon[885]: Server startup complete. Host name is weingeist-PC-2.local. Local service cookie is 1992427314.

journalctl -b | grep "avahi"                                                                                                      ✔  19s  
Jun 04 20:45:31 weingeist-PC avahi-daemon[813]: Found user 'avahi' (UID 972) and group 'avahi' (GID 972).
Jun 04 20:45:31 weingeist-PC avahi-daemon[813]: Successfully dropped root privileges.
Jun 04 20:45:31 weingeist-PC avahi-daemon[813]: avahi-daemon 0.8 starting up.
Jun 04 20:45:31 weingeist-PC avahi-daemon[813]: Successfully called chroot().
Jun 04 20:45:31 weingeist-PC avahi-daemon[813]: Successfully dropped remaining capabilities.
Jun 04 20:45:31 weingeist-PC avahi-daemon[813]: No service file found in /etc/avahi/services.
Jun 04 20:45:31 weingeist-PC avahi-daemon[813]: Failed to create server: No suitable network protocol available
Jun 04 20:45:31 weingeist-PC avahi-daemon[813]: avahi-daemon 0.8 exiting.
Jun 04 20:45:31 weingeist-PC systemd[1]: avahi-daemon.service: Main process exited, code=exited, status=255/EXCEPTION
Jun 04 20:45:31 weingeist-PC systemd[1]: avahi-daemon.service: Failed with result 'exit-code'.

Solution ?
Edit /etc/systemd/resolved.conf

MulticastDNS=no
LLMNR=no

Is this Solution correct ?

beermad · 4 June 2023 18:42

A note for anyone who has searx-ng installed from source (not AUR or Manjaro repos). The Python update breaks it. After wasting a lot of time trying to work out how to get everything in order for it, I found that the best (and quickest) way to get it working again was to completely delete the searxng user’s home directory and reinstall it as per the step by step installation guide

[edit]: the Python update instructions linked at the top would probably have helped a bit in this, though I have a feeling searx-ng itself would still have needed a complete manual rebuild.

samo_dadela · 4 June 2023 19:08

hamster-time-tracker does not work after python upgrade.

# hamster 
Traceback (most recent call last):
  File "/usr/bin/hamster", line 415, in <module>
    i18n.setup_i18n()
  File "/usr/lib/python3.11/site-packages/hamster/lib/i18n.py", line 24, in setup_i18n
    module.bind_textdomain_codeset('hamster','utf8')
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: module 'gettext' has no attribute 'bind_textdomain_codeset'

This is a known issue, fixed upstream… workaround here: