@pheiduck already answered your issue, but for more information on these things there is a good explanation in the known issues section above on why these directory permission warnings pop up from time to time.
error: failed to commit transaction (conflicting files)
npm: /usr/lib/node_modules/npm/node_modules/meant/.github/workflows/ci.yml exists in filesystem
npm: /usr/lib/node_modules/npm/node_modules/minimist/.travis.yml exists in filesystem
npm: /usr/lib/node_modules/npm/node_modules/minimist/LICENSE exists in filesystem
npm: /usr/lib/node_modules/npm/node_modules/minimist/example/parse.js exists in filesystem
npm: /usr/lib/node_modules/npm/node_modules/minimist/index.js exists in filesystem
npm: /usr/lib/node_modules/npm/node_modules/minimist/package.json exists in filesystem
npm: /usr/lib/node_modules/npm/node_modules/minimist/readme.markdown exists in filesystem
npm: /usr/lib/node_modules/npm/node_modules/minimist/test/all_bool.js exists in filesystem
npm: /usr/lib/node_modules/npm/node_modules/minimist/test/bool.js exists in filesystem
npm: /usr/lib/node_modules/npm/node_modules/minimist/test/dash.js exists in filesystem
npm: /usr/lib/node_modules/npm/node_modules/minimist/test/default_bool.js exists in filesystem
npm: /usr/lib/node_modules/npm/node_modules/minimist/test/dotted.js exists in filesystem
npm: /usr/lib/node_modules/npm/node_modules/minimist/test/kv_short.js exists in filesystem
npm: /usr/lib/node_modules/npm/node_modules/minimist/test/long.js exists in filesystem
npm: /usr/lib/node_modules/npm/node_modules/minimist/test/num.js exists in filesystem
npm: /usr/lib/node_modules/npm/node_modules/minimist/test/parse.js exists in filesystem
npm: /usr/lib/node_modules/npm/node_modules/minimist/test/parse_modified.js exists in filesystem
npm: /usr/lib/node_modules/npm/node_modules/minimist/test/proto.js exists in filesystem
npm: /usr/lib/node_modules/npm/node_modules/minimist/test/short.js exists in filesystem
npm: /usr/lib/node_modules/npm/node_modules/minimist/test/stop_early.js exists in filesystem
npm: /usr/lib/node_modules/npm/node_modules/minimist/test/unknown.js exists in filesystem
npm: /usr/lib/node_modules/npm/node_modules/minimist/test/whitespace.js exists in filesystem
Errors occurred, no packages were upgraded.
I was able to install the upgrade after the following command
sudo pacman -S npm --overwrite='*'
But now, randomly, I am not able to debug my local Angular application with Visual Studio Code…
In general update process went smooth but I have big issues with kernel 5.9.
After booting up I’m not able to open KDE session. This is because varius processes
are stuck, in ‘D’ state.:
71 ? D 0:00 [kworker/2:1+events_long]
149 ? D 0:00 [kworker/u16:2+netns]
287 ? D 0:00 [kworker/4:2+ipv6_addrconf]
3473 ? D 0:00 [kworker/u16:8+events_power_efficient]
5257 ? D 0:00 /usr/bin/ethtool -s lan2 wol g
5534 ? D 0:00 http.so [kdeinit5] https local:/run/user/1000/klauncherCzrgvi.1.slave-socket local:/run/user/1000/plasmashellKeOwiV.2.slave-socket
5573 ? D 0:00 /usr/bin/mysqld --defaults-file=/home/grubber/.local/share/akonadi/mysql.conf --datadir=/home/grubber/.local/share/akonadi/db_data/ --socket=/run/user/1000/akonadi/mysql.socket --pid-file=/run/user/1000/akonadi/mysql.pid
5586 ? D 0:00 /usr/bin/ksysguardd
This prevents normal working of the system. I’m not able to shutdown it normally – which is
obvious. Only MagicSysrq helps.
I do not know how to attach the dmesg output to the post. But there are
some reports of stuck processes and some other errors.
Of course everything is back to normal when I boot up kernel 5.8.
I have tried couple of times starting on kernel 5.9 and the problem
with stuck processes is always there.
Update went fine on 4 machines (Xfce)
One minor issue on two machines - journalctl shows:
pulseaudio[1117]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
What DE are you using ? KDE, Gnome both have a list of applications that are started when they start. Search for your DE and “autostart”, see if you can find nextcloud is in. Maybe the DE automatically detected it.
If not that, maybe it can by a systemd service that auto starts nextcloud, if a nextcloud service exists.
EDIT: saw your other comment, try running systemctl list-units --type=service, see if you find a nextcloud service. If you do, you can try disabling it sytemctl disable [service name]
I’m using xfce. In the start application gui /tmp/.mount_NextclAtndzP/usr/bin/nextcloud is started. But the problem is not the initial start at starting the DE, but the instant restart if I close it.