[Testing Update] 2020-03-31 - Gnome 3.36.1, XFCE, Browsers, Xorg-Server, Pamac

I gave linux56 a try - incl. virtualbox. It is ok for me. Virtualbox is working fine and all the rest too:

linux56+xfs+zfs+nvidia+xfce

@s9209122222 and @Yochanan can you post a screenshot of the issue?

Yep this can be usefull since i can t see issue..

EDIT: i see now in unstable with last changes made today

I think it is because gnome-shell got updated. Seems we have to rebuild our gdm theme.

Test on new kernel ik ok
be careful with ilwifi it was broken ( ok rev 2 nice ! )
( https://www.phoronix.com/scan.php?page=news_item&px=Linux-5.6-Broken-Intel-IWLWIFI)
checking log

sudo journalctl -b0 -p4
-- Logs begin at Wed 2018-08-29 20:14:34 CEST, end at Tue 2020-03-31 17:53:35 CEST. --
mars 31 17:51:34 mjro kernel: Unsupported mitigations=full, system may still be vulnerable
mars 31 17:51:34 mjro kernel: MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
mars 31 17:51:34 mjro kernel: TAA CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/tsx_async_abort.html for more details.
mars 31 17:51:34 mjro kernel:  #5 #6 #7
mars 31 17:51:34 mjro kernel: pci 0000:00:01.0: ASPM: current common clock configuration is broken, reconfiguring
mars 31 17:51:34 mjro kernel: efifb: Ignoring BGRT: unexpected or invalid BMP data
mars 31 17:51:34 mjro kernel: resource sanity check: requesting [mem 0xfdffe800-0xfe0007ff], which spans more than pnp 00:07 [mem 0xfdb00000-0xfdffffff]
mars 31 17:51:34 mjro kernel: caller pmc_core_probe+0x85/0x2f0 mapping multiple BARs
mars 31 17:51:34 mjro kernel: ata4.00: supports DRM functions and may not be fully accessible
mars 31 17:51:34 mjro kernel: ata1.00: supports DRM functions and may not be fully accessible
mars 31 17:51:34 mjro kernel: ata5.00: supports DRM functions and may not be fully accessible
mars 31 17:51:34 mjro kernel: ata2.00: supports DRM functions and may not be fully accessible
mars 31 17:51:34 mjro kernel: ata3.00: supports DRM functions and may not be fully accessible
mars 31 17:51:34 mjro kernel: ata1.00: supports DRM functions and may not be fully accessible
mars 31 17:51:34 mjro kernel: ata3.00: supports DRM functions and may not be fully accessible
mars 31 17:51:34 mjro kernel: ata5.00: supports DRM functions and may not be fully accessible
mars 31 17:51:34 mjro kernel: ata4.00: supports DRM functions and may not be fully accessible
mars 31 17:51:34 mjro kernel: ata2.00: supports DRM functions and may not be fully accessible
mars 31 17:51:34 mjro kernel: vboxdrv: loading out-of-tree module taints kernel.
mars 31 17:51:34 mjro kernel: VBoxNetAdp: Successfully started.
mars 31 17:51:34 mjro kernel: VBoxNetFlt: Successfully started.
mars 31 17:51:34 mjro kernel: nvidia: module license 'NVIDIA' taints kernel.
mars 31 17:51:34 mjro kernel: Disabling lock debugging due to kernel taint
mars 31 17:51:34 mjro kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 UTC 2020
mars 31 17:51:35 mjro systemd-vconsole-setup[471]: KD_FONT_OP_GET failed while trying to get the font metadata: Function not implemented
mars 31 17:51:35 mjro systemd-vconsole-setup[471]: Fonts will not be copied to remaining consoles
mars 31 17:51:35 mjro avahi-daemon[548]: Failed to parse address 'fe80::237:b7ff:fe98:964%enp0s31f6', ignoring.
mars 31 17:51:38 mjro kernel: kauditd_printk_skb: 30 callbacks suppressed
mars 31 17:51:38 mjro systemd[1]: User or group name "620" starts with a digit, accepting for compatibility.
mars 31 17:51:41 mjro ntpd[668]: bind(21) AF_INET6 fe80::be5d:48d6:1ba:8a01%2#123 flags 0x11 failed: Cannot assign requested address
mars 31 17:51:41 mjro ntpd[668]: unable to create socket on enp0s31f6 (5) for fe80::be5d:48d6:1ba:8a01%2#123
mars 31 17:51:45 mjro lightdm[656]: gkr-pam: unable to locate daemon control file
mars 31 17:51:45 mjro kernel: kauditd_printk_skb: 4 callbacks suppressed
mars 31 17:51:45 mjro systemd[1]: User or group name "1000" starts with a digit, accepting for compatibility.
mars 31 17:51:46 mjro kernel: process '/usr/lib/rtkit-daemon' started with executable stack
mars 31 17:51:47 mjro ntpd[668]: bind(25) AF_INET6 2a01:cb04:6fd:3600:c94b:6dc2:a4fc:e742#123 flags 0x11 failed: Cannot assign requested address
mars 31 17:51:47 mjro ntpd[668]: unable to create socket on enp0s31f6 (7) for 2a01:cb04:6fd:3600:c94b:6dc2:a4fc:e742#123
mars 31 17:51:55 mjro kernel: kauditd_printk_skb: 11 callbacks suppressed

appears with systemd
mars 31 17:51:38 mjro systemd[1]: User or group name "620" starts with a digit, accepting for compatibility.
mars 31 17:51:45 mjro systemd[1]: User or group name "1000" starts with a digit, accepting for compatibility.

and from kernel
mars 31 17:51:46 mjro kernel: process '/usr/lib/rtkit-daemon' started with executable stack

Iwlwifi got fixed in revision 2.

@Yochanan @s9209122222

1 Like

Heh, someone reminds me not to install anything KDE git version :stuck_out_tongue:
KDE now work perfectly!

Downgrade gnome-shell solve the issue so Need to investigate with Git bisect the offending commit..

In have the same ussie without LatteDock.

on first glance all good here with 5.6 on KDE/amd :+1:

Once i disabled that kwin effect i mentioned, my issue was gone. If you use some from AUR or elsewhere, maybe try to update them will help. I prefer to disable them as i was just making some tests about and forgot are enabled :slight_smile:

Kernel 5.6, virtualbox and all the rest running fine on my gnome desktop. :slight_smile:

'linux-latest' still points to 5.5 series. Do we wait for modules? Or it's just forgotten.

had a issue with the nvidia driver but was able to fix it by reinstalling

All looks good here. No issue that I've noticed.

Best to wait a couple kernel updates before pointing everyone to 5.6

3 Likes

Hello,

All is good with kernel5.5 but with kernel 5.6, the compilation of dkms module fail.

My module: broadcom-wl-dkms and bcwc-pcie/r242.ea832ac (aur).

Header are installed and the 2 modules work with kernel 5.5.

Fred

New manjaro-gdm-branding should fix the issue

1 Like

Landing in testing ...

$ plasmashell -v
plasmashell 5.18.4
1 Like

Forum kindly sponsored by