[Testing Update] 2020-06-03 - Software-Center, Arc Themes, Linux 5.7, Firefox 77, Systemd 245.6

[Danielsuarez369]

@Termy

linux-latest still points to 5.6

Normal, often Manjaro points them to the latest kernel after a few bug fix releases

[freggel.doe]

http://phb-crystal-ball.org/

[openminded]

Waow!

[LinuxFreak]

So XOrg is being updated. One has to be careful in of case using old NVIDIA drivers, which are related/connected to XOrg...

[Nvidia] Deprecation of 340xx driver series

[image] We had a good run with Nvidia 340xx driver series. However, at some point also we have to drop that driver. With Manjaro 19.0 release we will remove that driver from mhwd-db. This means the driver won't be recommended or detected by our distro by default. 340.108 was the last release by Nvidia to support X 1.20 and Kernel 5.4. As soon as there is an update to X that driver is gone. poll

trying the testing update now..

---

ALL OK

Graphics:
  Device-1: NVIDIA GT215 [GeForce GT 240] driver: nvidia v: 340.108 
  bus ID: 08:00.0 
  Display: x11 server: X.Org 1.20.8 driver: nvidia 
  resolution: 1920x1080~60Hz 
  OpenGL: renderer: GeForce GT 240/PCIe/SSE2 v: 3.3.0 NVIDIA 340.108 
  direct render: Yes 

[j77h]

@LinuxFreak

Display: x11 server: X.Org 1.20.8

Looks like X.Org is still 1.20.
Warn us when it jumps to 1.21.

[j77h]

@openminded

I've switched to Unstable today a couple of hours before this announcement, found close to zero issues, at least for packages pulled to this Testing update. Qt 5.15 ...

@philm Some PyQt apps don't work with Qt 5.15 yet, including TortoiseHg.
https://bugs.archlinux.org/task/66887
The initial report of that bug isn't quite right. Antonio Rojas later commented

... no trace of qscintilla in the backtrace ...
The crash is in PyQt, please report upstream to riverbank.

Hope Qt 5.15 doesn't go to stable until that's fixed.

[blw]

compiz-manjaro has not been rebuilt against the new version of protobuf which results in ccsm not working and compiz ignoring the settings previously made there

[Agentx]

Did you manually 5.10? When I check my Wine version it's still 5.9 and I did both the 05032020 and 05072020 testing updates.

[Helg1980]

I took the version Wine 5.10 from the Arch Linux repository:

https://www.archlinux.org/packages/?sort=&q=wine-staging&maintainer=&flagged=

[Helg1980]

Excuse me. This is a problem with wine-staging 5.10, regardless of the kernel version. I was too hasty.

[philm]

@freggel.doe: Seems there is a huge discussion going on regarding this problem. Can you check if some of your services have this After=network-online.target in them?

doc: Try to clarify automount dependency confusion

https://bugs.archlinux.org/task/66908

Ordering cycle reported, prevents non-root login or failed automount

[freggel.doe]

Yup, I'm having an automount in my /etc/fstab with the x-systemd.requires=network-online.target option set like described in the second issue you mentioned.

[philm]

Why do you have that? By upstream this is claimed to be utterly wrong. How was this added?

[freggel.doe]

Added manually, intend was to autmount an nfs share after the network was available.
Will have to see what's the proper way to do this.

[philm]

@freggel.doe Maybe chip into the discussion here:

Ordering cycle reported, prevents non-root login or failed automount

For now I'll keep the revert until it is clear.

[freggel.doe]

Upstream (systemd) has clarified documentation to explicitly mention these options as wrong.
Upstream ( arch) is reverting their own revert for the next systemd-build.

I will adjust that mount entry accordingly, there's no way around that.

[philm]

My question was more: Did you add those network options by yourself or was it part of some provided systemd service files?

[freggel.doe]

Ah. That entire entry was added manually including all options.

[openminded]

I guess it was done as per advice on the respective ArchWiki page. NFS article there has (d) such recommendation. I was a victim of this approach too.