[Testing Update] 2020-09-25 - Calibre, KDE-git, Deepin, Python, Haskell

Yeah, that David’s hack works for the time being at least, tested immediately on another user’s account without reboot. Of course a proper fix would be a much better solution, but we have to wait for KDE devs to prepare and release it. Thanks Phil for the quick patch.

XFCE + BTRFS + linux58

Getting this:

/etc/profile.d/perlbin.sh:6: command not found: append_path
/etc/profile.d/perlbin.sh:8: command not found: append_path
/etc/profile.d/perlbin.sh:10: command not found: append_path

I just noticed that too.

It’s not just for root it’s for any user:

I see the same on my system. It is worth mentioning that sudo su does not show the same errors.

I just edit/revert the /etc/profile.d/perlbin.sh…append_path -> PATH=$PATH:


(Bug) FS#67990 - append_path not defined
(commit) Check if PATH is already set in $PATH

edit: I see this behaviour/error on Tilix terminal but not on Konsole terminal…as workaround to this error…I revert it

Please do not post screenshots of terminal output, copy+paste and use proper formatting.

anyone having yakuake not conform to proper height settings?

filesystem package needs an update (last packager is @philm):
appendpath function from /etc/profile changed to append_path and /etc/profile.d/perlbin.sh (from updated perl package) tries to use it.


The proper fix is currently in review. More or less it is a regression in Qt. So if you want to test it with qt5-base, I could provide a package, however it is too early, so I rather keep the working workaround for Plasma and check later when upstream completed the code-review at Qt Inc.


Some more fixes …

:: Different sync package(s) in repository community x86_64

                             PACKAGE              testing             unstable
                        deepin-movie         1:         1:
                 firefox-dark-reader             4.9.19-1             4.9.20-1
                                john       1.9.0.jumbo1-3       1.9.0.jumbo1-4
                             neomutt           20200821-1           20200925-1
                              puppet             6.17.0-1             6.18.0-1
                       python-editor              1.0.4-3              1.0.4-4
                       python-geoip2              4.0.2-1              4.1.0-1
                   python-hypothesis             5.36.0-1             5.36.1-1
                       python-imdbpy                6.8-3          2020.9.25-1
                 python-openstacksdk             0.49.0-1             0.50.0-1
                       python-orjson              3.3.1-1              3.4.0-1
                        python-paste              3.4.5-1              3.4.6-1
              python-pytest-services              2.1.0-1              2.2.0-1
                      python2-editor              1.0.4-3                    -
                            ruby-irb              1.2.4-1              1.2.7-1
                      shairport-sync              3.3.6-1              3.3.6-2
                               v2ray             4.28.2-1             4.29.0-1

:: Different overlay package(s) in repository core x86_64

                             PACKAGE              testing             unstable
                          filesystem            2020.05-1            2020.09-1

:: Different sync package(s) in repository extra x86_64

                             PACKAGE              testing             unstable
                            ghostpcl             9.53.1-1             9.53.2-1
                         ghostscript             9.53.1-1             9.53.2-1
                            ghostxps             9.53.1-1             9.53.2-1

Thanks @philm that fixed the sudo -i problem.

On dual monitor, it’s now fixed on me, KDE, linux58. Thanks.

The last


2020-09-26T07:38:12+0200] [PACMAN] Running ‘pacman -Syyu’
[2020-09-26T07:38:12+0200] [PACMAN] synchronizing package lists
[2020-09-26T07:38:13+0200] [PACMAN] starting full system upgrade
[2020-09-26T07:38:28+0200] [ALPM] transaction started
[2020-09-26T07:38:28+0200] [ALPM] warning: /etc/nsswitch.conf installed as /etc/nsswitch.conf.pacnew
[2020-09-26T07:38:28+0200] [ALPM] upgraded filesystem (2020.05-1 -> 2020.09-1)
[2020-09-26T07:38:28+0200] [ALPM] upgraded ghostscript (9.53.1-1 -> 9.53.2-1)
[2020-09-26T07:38:29+0200] [ALPM] upgraded plasma-workspace (5.19.5-1.1 -> 5.19.5-1.2)
[2020-09-26T07:38:29+0200] [ALPM] upgraded ruby-irb (1.2.4-1 -> 1.2.7-1)
[2020-09-26T07:38:29+0200] [ALPM] transaction completed

produced a new /etc/nsswitch.conf.pacnew.

Existing nsswitch.conf:
# Commented out because of boot problems and NetworkManager failure
# passwd: files mymachines systemd
# group: files mymachines systemd
passwd: files mymachines
group: files mymachines

passwd: files systemd
group: files systemd

Any suggestions how to merge this?

1 Like

It was produced because of boot problems we had some time ago when new (at that moment) systemd brought incompatibilities with network devices. Remember? NFS mounts and stuff.
These commented entries in your nsswitch.conf are meant to workaround that bad situation, but now there’s no need in that, assuming you have done correcting mount units or fstab options for mounts. Search through old forum announcements and you’ll find the case.

To be clear: there’s no such pacnew on my machine. Those strings are not commented out.

1 Like

Thanks @openminded, with other words adding systemd and keeping mymachines?

All good here on 5.8/KDE/AMD. It seems the plasma-multimonitor-workaround is working properly :slight_smile:

This is how it looks on my system:

# Name Service Switch configuration file.
# See nsswitch.conf(5) for details.

passwd: files systemd
group: files systemd
shadow: files

publickey: files

hosts: files mymachines mdns4_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] dns mdns4 myhostname
networks: files

protocols: files
services: files
ethers: files
rpc: files

netgroup: files

With that new nsswitch.conf my system still has looong boot times and Unexpected error response from GetNameOwner(): errors. sddm even dumps core.
Upstream bug is still open:

I’m back to:

passwd: files mymachines
group: files mymachines

and all is well…

1 Like

2 posts were split to a new topic: Questions about the Manjaro PinePhone