[Testing Update] 2019-12-08 - Systemd 242.153-2, Pamac 9.2, Linux-Firmware

Known issues and solutions

This is a wiki post; please edit as necessary.
Please, consider subscribing to the Testing Updates Announcements RSS feed

Do I need to downgrade systemd?

Not necessarily. If systemd 243.162-2 works fine for you, you can keep it. If you have issues related to systemd, of course, you may want to downgrade the packages related to systemd.

This is valid until Manjaro Team says otherwise. If the team asks everyone to downgrade the packages for a reason or another, do it.

From philm:

Pamac: I can't build AUR packages

Before anything else, please verify in /etc/pamac.conf if BuildDirectory is set up correctly. For example:

## AUR build directory:
BuildDirectory = /var/tmp

If you have something like /var or / instead, you might have been affected by the following bug. A bug in Pamac "corrupted" the value of BuildDirectory, which ultimately leads to a directory that Pamac can't write in (to create a directory) because the user does not have the permission to do so, hence why Pamac failed to build AUR packages.

This bug should be fixed by now in Pamac 9.2.0rc, but users affected by the bug have to change back this parameter to a correct value manually, which can be done either with a text editor by editing /etc/pamac.conf OR graphically within Pamac GTK by going in Preferences > AUR.

I am not having any issues with systemd 243.162-2. My system seems to be running fine. Do I still need to downgrade?


Got SSL error, but update went ok


::ERROR [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate is not yet valid (_ssl.c:1108) 'https://manjaro.moson.eu/'

Just got renewed today. Looks ok to me though. What's the time on your sys?

1 Like

11:30 On my timezone :smiley:

I can access it now as well :slight_smile:

EDIT: After digging, the clock not synced with HWclock after poweron.

1 Like

You can keep it if it is fine for you. We might update to v244 series in unstable soon to test that series out ...


FYI, the upstream bug i've been mentioning for a while now, https://github.com/netblue30/firetools/issues/45 including in the previous Testing Update [Testing Update] 2019-12-06 - Kernels, Mesa, Firefox, KDE-git, continues to manifest in my Arch with 244. I had to downgrade it back to 242 same as with my Manjaro.

May be you should report the bug against systemd rather than firetools? You’ll get a response from systemd, one way or another.


Hmm. You can't really expect the systemd team to figure out issues with other software.

IMHO that issue should be addressed to the firetools developers (which was already done). Now those guys need to see why it is not working anymore with newer systemd versions and either fix their software to make it working again OR if they see that the issue is related to systemd, contact systemd then.

How do you know it’s not a systemd fault? Looks more like a systemd fault than one with firetools. Especially since going back to older versions of systemd prevent the issue from occurring.

Report it with both and let the devs figure it out with all info provided.

Well, I do not know that. Could very well be.
But again, you cannot expect the systemd team to figure out what the issue is with some other software that is utilizing systemd. The developer (firetools in this case) of the software should figure out why their software is not working anymore. And then if it turns out if there is something wrong with systemd, address it to systemd finally.

It's like if I am developing an app which utilizes certain libraries and then and then breaks with an update of those libraries, I either have to adapt my code to make it work with the newer version, or I have to contact the developers of the library about what's wrong. I cannot expect that the suppliers of that library to fix my programs...

Anyways, this is getting off-topic. I'm gonna stop here.

1 Like

Again the usual message to systemd

Warnung: lib32-systemd: Lokale Version (243.162-1) ist neuer als multilib (242.153-2)
Warnung: systemd: Lokale Version (243.162-2) ist neuer als core (242.153-2)
Warnung: systemd-libs: Lokale Version (243.162-2) ist neuer als core (242.153-2)
Warnung: systemd-sysvcompat: Lokale Version (243.162-2) ist neuer als core (242.153-2)

No, until Manjaro Team will say otherwise (for example, a rebuild against newer libraries).

EDIT: Made an entry in the wiki post.


Seems to be fine on my side on my laptop.

At that point, with systemd 242, I do not see anything holding back for a Stable release. We could focus on systemd later, once Stable got their long-awaited updates.

[frog@ideapad ~]$ neofetch
██████████████████  ████████   frog@ideapad 
██████████████████  ████████   ------------ 
██████████████████  ████████   OS: Manjaro Linux x86_64 
██████████████████  ████████   Host: 80SM Lenovo ideapad 310-15ISK 
████████            ████████   Kernel: 5.3.15-1-MANJARO 
████████  ████████  ████████   Uptime: 45 mins 
████████  ████████  ████████   Packages: 1088 (pacman) 
████████  ████████  ████████   Shell: bash 5.0.11 
████████  ████████  ████████   Resolution: 1280x720 
████████  ████████  ████████   DE: Cinnamon 4.4.3 
████████  ████████  ████████   WM: Mutter (Muffin) 
████████  ████████  ████████   WM Theme: Mint-Y-Dark-Teal (Mint-Y-Dark) 
████████  ████████  ████████   Theme: Mint-Y-Darker-Teal [GTK2/3] 
████████  ████████  ████████   Icons: Papirus-Maia [GTK2/3] 
                               Terminal: gnome-terminal 
                               CPU: Intel i5-6200U (4) @ 2.800GHz 
                               GPU: Intel Skylake GT2 [HD Graphics 520] 
                               Memory: 1598MiB / 7869MiB 

[frog@ideapad ~]$ inxi -Fxxxn
  Host: ideapad Kernel: 5.3.15-1-MANJARO x86_64 bits: 64 compiler: gcc 
  v: 9.2.0 Desktop: Cinnamon 4.4.3 dm: LightDM 1.30.0 Distro: Manjaro Linux 


  Processes: 180 Uptime: 46m Memory: 7.69 GiB used: 1.47 GiB (19.2%) 
  Init: systemd v: 242 Compilers: gcc: 9.2.0 Shell: bash v: 5.0.11 
  running in: gnome-terminal inxi: 3.0.37 


Agreed, this is going to be one hell of a big update for them though. Brace for impact when it does release. :bowing_man::fireworks:


runs perfect here, too.

██████████████████  ████████   OS: Manjaro Linux x86_64 
██████████████████  ████████   Kernel: 5.4.2-1-MANJARO 
████████  ████████  ████████   Packages: 1864 (pacman), 6 (snap) 
████████  ████████  ████████   Shell: bash 5.0.11 
████████  ████████  ████████   Resolution: 3840x2160 
████████  ████████  ████████   DE: GNOME 3.34.1 
████████  ████████  ████████   WM: Mutter 
████████  ████████  ████████   WM Theme: Adwaita 
████████  ████████  ████████   Theme: Adwaita-dark [GTK2/3] 
████████  ████████  ████████   Icons: Papirus-Dark [GTK2/3] 
████████  ████████  ████████   Terminal: gnome-terminal 
                               CPU: Intel i7-8700K (12) @ 4.700GHz 
                               GPU: NVIDIA GeForce GTX 1080 Ti 
                               GPU: Intel UHD Graphics 630 
                               Memory: 3891MiB / 64184MiB```

No problems with Systemd 243.162-2 here either.

Have you considered doing a git-bisect of systemd to see if you can find the problem?


No, i always forget about this possibility.

Great, now i have another thing over which to feel guilty. :stuck_out_tongue_winking_eye:



Have you seen how many commits there are to go through? Literally thousands and that’s not even a joke.

Guess we know what @kdemeoz is doing for the next six months :rofl:


Forum kindly sponsored by