[Testing Update] 2020-12-07 - BREAKAGE EXPECTED - Kernels, Mesa 20.3, Python 3.9, Pamac 10

The installation of the update went very well. I liked the way it was updated inux59-nvidia, linux59-headers and linux - utils.

I am using a MacBook Pro 13" mid 2010
The updated worked for me.
BUT if I switch to nouveau driver, the power management does not work anymore.
Additionally I have since long time the issue that wifi does not work after cold-boot. Only after I send my macbook to sleep and wake it up again, the wifi works. But that does not work with nouveau driver, as it does not wake up from sleep anymore, or better said it does not really go to sleep mode. Display turns off but sleep LED does not light up. Have to hold power button for several seconds to turn off. The legacy NVIDIA driver works fine.

Manjaro-hello does not work in combination with Pamac 10 Beta. It requires version 9.0.

~ >>> manjaro-hello                                                                                                               
Traceback (most recent call last):
  File "/usr/bin/manjaro-hello", line 409, in <module>
    hello = Hello()
  File "/usr/bin/manjaro-hello", line 172, in __init__
    manager.get_modules(self)
  File "/usr/bin/manjaro-hello", line 30, in get_modules
    app.load(window)
  File "/usr/bin/manjaro-hello", line 80, in load
    from application_utility.browser.application_browser import ApplicationBrowser
  File "/usr/lib/python3.9/site-packages/application_utility/browser/application_browser.py", line 26, in <module>
    from application_utility.config.hello_config import HelloConfig
  File "/usr/lib/python3.9/site-packages/application_utility/config/hello_config.py", line 25, in <module>
    from application_utility.browser.config import Config
  File "/usr/lib/python3.9/site-packages/application_utility/browser/config.py", line 27, in <module>
    from .data import Data
  File "/usr/lib/python3.9/site-packages/application_utility/browser/data.py", line 31, in <module>
    gi.require_version("Pamac", "9.0")
  File "/usr/lib/python3.9/site-packages/gi/__init__.py", line 129, in require_version
    raise ValueError('Namespace %s not available for version %s' %
ValueError: Namespace Pamac not available for version 9.0'

I created an issue on gitlab: Manjaro-Hello does not run together with Pamac 10 Beta

i will add
correct video-nvidia by chroot
( remove nvidia-utils-455xx with option -Rdd , then mhwd -a pci free 0300 , mhwd -a cpi nonfree 0300)

nb : if you have Grub error on boot ( csm + secureboot activated --> no csm , no secureboot )

@Manjaro-Team

with lightdm - xfce - lock screen and systemd

i will check if trouble still occurs on screen lock:

  1. i can log in
  2. lost of video screen ( goes black )
  3. i log in TTY
  4. i apply “sudo systemctl restart lightdm” to get back xorg & video
    and then it’s ok

with boot kernel : systemd.unified_cgroup_hierarchy=1 ( need to apply 4)

next try : without systemd.unified_cgroup_hierarchy ( need to apply 4 )
next try : downgrade systemd ==> version 247 systemd is not ready
( lib32-systemd , systemd , systemd-libs , systemd-syscompat) ( need to apply 4 )

@philm
what i have see :
pam secret on lock xfce session do not know login ,

with check ( sudo systemctl status )
session 2 with login ( user ok on boot )
lock screen , type password
failed return session 2 ( no more login appears , pam secret with warn )

pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8004 service=[systemd-user] terminal=[] user=[lightdm] ruser=[<unknown>] rhost=[<unknow>]
==> NO USER HERE 

then Ctrl+Alt+F2
tty create session 5 with login ( user ok )
check , there is 2 session2 and 5 , only session5 has login --user

if i do sudo systemctl restart ligthdm.service
session 2 & session 5 are fusioned , video is back ( login user is ok )

==> we lost login --user HERE on lock screen

Had to downgrade linux-firmware due to wifi problems

affected device
Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter (rev 01)
Subsystem: Lite-On Communications Inc Device 6621
Kernel driver in use: ath9k
Kernel modules: ath9k

This switch to the new nvidia packages is kind of a mess. lib32-nvidia-utils correctly conflicts and replaces, while nvidia-utils does not for example (it only conflicts). I also ended up with linux59 without the nvidia kernel module thanks to linux-latest. Fixed all those issues on my end, but unless that’s addressed, we may end up with a lot of broken systems.

P.s.: Why not make kernel linux59 replace all previous kernels instead of using a proxy meta package? That would also solve various dependency issues. When for example the kernel gui tries to remove linux59.

Not sure why this happened. But I am running the testing branch on my laptop. I am using KDE Plasma. It’s an Asus Laptop. No dedicated GPU. It’s only GPU is the internal one by my CPU (Intel).

When checking for updates using yay, yay -Syu, I get “Missing aur packages: mwhd-nvidia-340xx, 418xx, 430xx, 440xx, 450xx, and 455xx”. I did not have this issue until this latest testing update.

Note: In the “missing aur packages” output I put, I didn’t include the “mwhd-nvidia” part for the rest of the packages just to save myself from typing it all out.

Another note and possible issue. When I go to “Add or Remove Software” and I check for updates via that, it get’s to about 90% and seems to finish but crashes. I think it may be crashing when it’s going to display the updates I have.

That means they’re orphans an you can remove them.

I was able to upgrade my intel/nvidia stack by removing conflicting packages and then reinstall the prime package for linux59. Everything went seamlessly from there on in respect to the gpu drivers and kernel upgrade.
But I have two other problems:

  1. I’m on a thinkpad T480 and with linux59 brightness controls are not working, no problems with linux54, linux58 and linux510. So I switched to linux510 for now and can live with this workaround

  2. I had to do a partial upgrade due to problems with the pipewire package and it’s pulse plugins:

    :: Synchronizing package databases...
     core                                  168,3 KiB  7,15 MiB/s 00:00 [------------------------------------------------------------------------------] 100%
     extra                                 1961,6 KiB  31,9 MiB/s 00:00 [------------------------------------------------------------------------------] 100%
     community                      6,3 MiB  31,7 MiB/s 00:00 [------------------------------------------------------------------------------] 100%
     multilib                            182,2 KiB  44,5 MiB/s 00:00 [------------------------------------------------------------------------------] 100%
    :: Starting full system upgrade...
    resolving dependencies...
    looking for conflicting packages...
    :: pipewire-pulse and pulseaudio are in conflict. Remove pulseaudio? [y/N] y
    :: pipewire-pulse and pulseaudio-modules-bt are in conflict (pulseaudio-bluetooth). Remove pulseaudio-modules-bt? [y/N] y
    error: failed to prepare transaction (could not satisfy dependencies)
    :: removing pulseaudio breaks dependency 'pulseaudio=14.0-1' required by pulseaudio-equalizer
    :: removing pulseaudio breaks dependency 'pulseaudio=14.0-1' required by pulseaudio-jack
    :: removing pulseaudio breaks dependency 'pulseaudio=14.0-1' required by pulseaudio-lirc
    :: removing pulseaudio breaks dependency 'pulseaudio=14.0-1' required by pulseaudio-zeroconf
    error installing repo packages```
    
    

I’m not sure if this is an individual problem.

UPDATE:
For now, I ended up with removing the pipewire-pulse package and the upgrade went fine. Will try the pulse replacement by pipewire later again.

To remove pulseaudio and use pipewireis difficult, but not impossible;
first remove all apps using pulsaudio and write down, which.
in this case:
pulseaudio-equalizer
pulseaudio-jack
pulseaudio-lirc
pulseaudio-zeroconf

With pamac its easier - if you get a warning, "remove (long list , containing e.g gdm, dont do that.
Do this as long, as no warning because oif de-install occurs.
Dependencies warning may be ignored - deinstall not
Than try upgrade - if pamac doesnot want to de-install anything, than its o.k.


For pipewire I have installed:
pipewire
pipewire-alsa
pipewire-jack
pipewire-pulse
gst-plugin-pipewire
libpipewire02
and:

systemctl --user enable pipewire.socket
systemctl --user enable pipewire.service

May the force be with you


1 Like

Will this break any desktops? I know cinnamon needs the pulseaudio libs and removing pulseaudio used to remove the cinnamon desktop as well. Hopefully this isn’t an issue anymore

Everything that removes something else than “pulseaudio*”
WILL break your System!
I am on Gnome. Did remove any pulseaudio-apps before upgrading - IF there was no warning about
removing the System like gdm (or cinnamon-desktop).
The upgrade-script using pamac managed to do this without breakage, whereas on TTY it could not be done


1 Like

hmm looks like those systemd-resolved issues weren’t that innocent, after this update on my testing machine that has DNS over TLS (cloudflare) I was getting a lot of core dumps in Chromium for example

Snip of those
09/12/2020 04:52	systemd-coredump	Process 5504 (chromium) of user 1000 dumped core.

Stack trace of thread 5521:
#0  0x00007fa7f1007615 raise (libc.so.6 + 0x3d615)
#1  0x00007fa7f0ff0862 abort (libc.so.6 + 0x26862)
#2  0x00007fa7e72041e4 n/a (libnss_resolve.so.2 + 0x101e4)
#3  0x00007fa7e71f6fe7 n/a (libnss_resolve.so.2 + 0x2fe7)
#4  0x00007fa7e72015c5 _nss_resolve_gethostbyname4_r (libnss_resolve.so.2 + 0xd5c5)
#5  0x00007fa7f10b3146 gaih_inet.constprop.0 (libc.so.6 + 0xe9146)
#6  0x00007fa7f10b3fc9 getaddrinfo (libc.so.6 + 0xe9fc9)
#7  0x0000563b7ce94411 n/a (chromium + 0x1fa7411)
#8  0x0000563b7cebe4fe n/a (chromium + 0x1fd14fe)
#9  0x0000563b7ceb4b9b n/a (chromium + 0x1fc7b9b)
#10 0x0000563b7ceb4dd8 n/a (chromium + 0x1fc7dd8)
#11 0x0000563b7f71b5ee n/a (chromium + 0x482e5ee)
#12 0x0000563b7f734078 n/a (chromium + 0x4847078)
#13 0x0000563b7f733b18 n/a (chromium + 0x4846b18)
#14 0x0000563b7f76a96d n/a (chromium + 0x487d96d)
#15 0x0000563b7f733592 n/a (chromium + 0x4846592)
#16 0x0000563b7f7403cb n/a (chromium + 0x48533cb)
#17 0x0000563b7f73ff8a n/a (chromium + 0x4852f8a)
#18 0x0000563b7f76b1d5 n/a (chromium + 0x487e1d5)
#19 0x00007fa7f50133e9 start_thread (libpthread.so.0 + 0x93e9)
#20 0x00007fa7f10ca293 __clone (libc.so.6 + 0x100293)

Stack trace of thread 5520:
#0  0x00007fa7f10bf56e ppoll (libc.so.6 + 0xf556e)
#1  0x00007fa7e71f90d5 n/a (libnss_resolve.so.2 + 0x50d5)
#2  0x00007fa7e72011d5 n/a (libnss_resolve.so.2 + 0xd1d5)
#3  0x00007fa7e7201543 _nss_resolve_gethostbyname4_r (libnss_resolve.so.2 + 0xd543)
#4  0x00007fa7f10b3146 gaih_inet.constprop.0 (libc.so.6 + 0xe9146)
#5  0x00007fa7f10b3fc9 getaddrinfo (libc.so.6 + 0xe9fc9)
#6  0x0000563b7ce94411 n/a (chromium + 0x1fa7411)
#7  0x0000563b7cebe4fe n/a (chromium + 0x1fd14fe)
#8  0x0000563b7ceb4b9b n/a (chromium + 0x1fc7b9b)
#9  0x0000563b7ceb4dd8 n/a (chromium + 0x1fc7dd8)
#10 0x0000563b7f71b5ee n/a (chromium + 0x482e5ee)
#11 0x0000563b7f734078 n/a (chromium + 0x4847078)
#12 0x0000563b7f733b18 n/a (chromium + 0x4846b18)
#13 0x0000563b7f76a96d n/a (chromium + 0x487d96d)
#14 0x0000563b7f733592 n/a (chromium + 0x4846592)
#15 0x0000563b7f7403cb n/a (chromium + 0x48533cb)
#16 0x0000563b7f73ff8a n/a (chromium + 0x4852f8a)
#17 0x0000563b7f76b1d5 n/a (chromium + 0x487e1d5)
#18 0x00007fa7f50133e9 start_thread (libpthread.so.0 + 0x93e9)
#19 0x00007fa7f10ca293 __clone (libc.so.6 + 0x100293)

Stack trace of thread 5522:
#0  0x00007fa7f10c1b7b __select (libc.so.6 + 0xf7b7b)
#1  0x0000563b7f76d7de n/a (chromium + 0x48807de)
#2  0x0000563b7f76b1d5 n/a (chromium + 0x487e1d5)
#3  0x00007fa7f50133e9 start_thread (libpthread.so.0 + 0x93e9)
#4  0x00007fa7f10ca293 __clone (libc.so.6 + 0x100293)

Stack trace of thread 5504:
#0  0x00007fa7f50196a2 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf6a2)
#1  0x0000563b7f767901 n/a (chromium + 0x487a901)
#2  0x0000563b7f7681b5 n/a (chromium + 0x487b1b5)
#3  0x0000563b7f767eab n/a (chromium + 0x487aeab)
#4  0x0000563b7f6ddd8b n/a (chromium + 0x47f0d8b)
#5  0x0000563b7f72d64e n/a (chromium + 0x484064e)
#6  0x0000563b7f704362 n/a (chromium + 0x4817362)
#7  0x0000563b7f431cdb n/a (chromium + 0x4544cdb)
#8  0x0000563b7f69fc84 n/a (chromium + 0x47b2c84)
#9  0x0000563b7f69df16 n/a (chromium + 0x47b0f16)
#10 0x0000563b7cd860a3 ChromeMain (chromium + 0x1e990a3)
#11 0x00007fa7f0ff2152 __libc_start_main (libc.so.6 + 0x28152)
#12 0x0000563b7ca8b56e _start (chromium + 0x1b9e56e)
...list continues
DNS o. TLS settings were these:
resolvectl status
Global
       LLMNR setting: yes                 
MulticastDNS setting: yes                 
  DNSOverTLS setting: yes                 
      DNSSEC setting: no                  
    DNSSEC supported: no                  
         DNS Servers: 1.1.1.1             
                      1.0.0.1             
                      2606:4700:4700::1111
                      2606:4700:4700::1001
Fallback DNS Servers: 8.8.8.8             
                      8.8.4.4             
                      2001:4860:4860::8888
                      2001:4860:4860::8884
          DNS Domain: ~.                  

Link 2 (enp61s0)
      Current Scopes: none
DefaultRoute setting: no  
       LLMNR setting: yes 
MulticastDNS setting: no  
  DNSOverTLS setting: yes 
      DNSSEC setting: no  
    DNSSEC supported: no  

Link 3 (wlp62s0)
      Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
DefaultRoute setting: yes                      
       LLMNR setting: yes                      
MulticastDNS setting: no                       
  DNSOverTLS setting: yes                      
      DNSSEC setting: no                       
    DNSSEC supported: no                       
         DNS Servers: 192.168.1.1              
                      fe80::1%21913            
          DNS Domain: ~.                       
                      home 

So apart from DNSSEC managed by systemd utterly broken for a long time already (does not respond at all from a point on and new updated default resolved.conf has set #DNSSEC=no replacing the previous default #DNSSEC=allow-downgrade), seems like systemd 247.1-1 is buggy with DNSoTLS as well :frowning:

Problem solved downgrading to previous 246.6-1, (no systemd-resolved CPU struggle, no Chromium core dumps), Arch adopted 247 too early?

systemd                      246.6-1              247.1-1
systemd-libs                 246.6-1              247.1-1
systemd-resolvconf           246.6-1              247.1-1
systemd-sysvcompat           246.6-1              247.1-1
1 Like

systemd 247.1-1 „was“ very buggy excepted some bugs on an Arch VPS > is ok with systemd 247.1-3 so in my opinion we should use this version in unstable and testing . In stable stay at 246.6.

3 Likes

Flatpak creates some issues in pamac. Will this be fixed in next stable update?

All good here. From the repos, libpurple, pidgin and python-tesserwarp need to be rebuilded.

1 Like

So I updated and rebooted. Now nvidia isnt working.

The GUI says that nvidia driver is not installed, so I tried to instal it. but then this message shows up:

" Waiting for user input...

Starting

Error: config 'video-hybrid-intel-nvidia-prime' conflicts with config(s): video-hybrid-intel-nvidia-455xx-prime

Hecho."

so I try this to remove the old driver
sudo mhwd -r pci video-hybrid-intel-nvidia-455xx-prime

but it complains that removing nvidia-455xx-utils breaks dependency with «nvidia-utils», needed for the package lib32-nvidia-utils

So what now? because it seems Im in a dead end here

Edit:

I was able to yay -R mhwd-nvidia-455xx

but the error is still here when installing from the driver GUI

Waiting for user input...
Starting
Warning: config '/var/lib/mhwd/local/pci/video-hybrid-intel-nvidia-455xx-prime/MHWDCONFIG' is invalid!
 Installing video-hybrid-intel-nvidia-prime...
Sourcing /etc/mhwd-x86_64.conf
Has lib32 support: true
Sourcing /var/lib/mhwd/db/pci/graphic_drivers/hybrid-intel-nvidia-prime/MHWDCONFIG
Processing classid: 0300
Sourcing /var/lib/mhwd/scripts/include/0300
:: Synchronizing package databases...
warning: nvidia-prime-1.0-4 is up to date -- skipping
warning: lib32-nvidia-utils-455.45.01-3 is up to date -- skipping
warning: linux510-nvidia-455.45.01-0.7 is up to date -- skipping
warning: linux59-nvidia-455.45.01-2 is up to date -- skipping
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
resolving dependencies...
looking for conflicting packages...
:: nvidia-utils and nvidia-455xx-utils are in conflict (nvidia-libgl). Remove nvidia-455xx-utils? [y/N] error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)

nvidia-utils and nvidia-455xx-utils are in conflict
Error: pacman failed!
Error: script failed!


Hecho.

Edit 2: uninstalling optimus manager fixed the nvidia card not working at all, but the problem above still remains, I cant install the driver that shows up in the driver GUI utility. Would be nice to have instructions about how to fix it since you already knew that were going to break.

Replace issues were solved with nvidia-utils already. I only have to fix mhwd-profiles similar like this. However I’m more occupied in ARM part of Manjaro, so I’ve less time to do x86_64 stuff.

The Nvidia drivers switch will mess up a lot of systems, so we have to figure out on how to switch the drivers best. Especially those systems with Hybrid drivers 


2 Likes

The first two are imported directly from Arch and are not related to migrating to Python 3.9. Does Pidgin still work? If not, create a new thread in Software & Applications.

As far as python-tesserwrap, it hasn’t been updated since 2014. The only thing that requires it is ocrdesktop. The project webpage is dead, can’t find anything about it.

I’m removing them from our repos, you’re on you’re own. Looks like they’re in the AUR.

“You are the weakest link. Goodbye”

1 Like

Seems the small icons in KDE audio widget, mentioned by omano, is still present.
I tried different Plasma Styles, and narrowed it to the colour-scheme-respecting Breath2.