Update broke HDMI over USB-C on pinebook pro. Solution:
sudo pacman -Syyu linux-pinebookpro linux-pinebookpro-headers
I had the same issue with megasync on nemo (check my thread on it) it transpired the culprit was glib2. I updated glib2 to 2.66.7-1 from the unstable branch and it fixed megasync plus Dropbox issues as well. Like I said this was on nemo not nautilus but nemo is a fork of nautilus
2 Likes
Updated with tty Intel i7 lts kernel 2 monitors
A quick check of apps all good
Big Thank You to all the team and especially those in testing for sharing your time.
Noel.
Another straightforward, uneventful update for me in Manjaro Cinnamon, using run-level 3 and pamac update.
These updates have been going so smoothly, it’s like you devs are tempting me to do something silly, e.g. slap another two or three Linuxes on the system (all various Manjaro editions, of course!). 
1 Like
all good on my gnome+nvidia box
thank you, manjaro team.
Thanks to manjaro team, all went well. XFCE, kernel 5.10
Thank you for the info, @sawdoctor. You mentioned:
updated glib2 to 2.66.7-1 from the unstable branch
How do I go about doing this?
I have issues, sometimes, when the System coming up from suspend, a short time the desktop content is viewable, the (gnome) desktop seems to crash, restart and then desktop is locked. But this could really be an security issue.
I did it the lazy way. I installed downgrade package from the repos which is meant for downgrading packages but it also let me upgrade as well
2 Likes
So, fun story. I installed the zst file from here (click ‘download from mirror’ on the right). It installed most admirably. Thing is, I uninstalled megasync in the flurry of attempts to solve the original problem. Now, apparently, megasync can only be installed through AUR, but when I try to build, I now get the error:
/usr/bin/ld: warning: libicuuc.so.67, needed by /usr/lib/gcc/x86_64-pc-linux-gnu/10.2.0/../../../../lib/libpdfium.so, not found (try using -rpath or -rpath-link)
/usr/bin/ld: /usr/lib/gcc/x86_64-pc-linux-gnu/10.2.0/../../../../lib/libpdfium.so: undefined reference to `u_tolower_67'
/usr/bin/ld: /usr/lib/gcc/x86_64-pc-linux-gnu/10.2.0/../../../../lib/libpdfium.so: undefined reference to `u_toupper_67'
/usr/bin/ld: /usr/lib/gcc/x86_64-pc-linux-gnu/10.2.0/../../../../lib/libpdfium.so: undefined reference to `u_isspace_67'
/usr/bin/ld: /usr/lib/gcc/x86_64-pc-linux-gnu/10.2.0/../../../../lib/libpdfium.so: undefined reference to `u_isalnum_67'
/usr/bin/ld: /usr/lib/gcc/x86_64-pc-linux-gnu/10.2.0/../../../../lib/libpdfium.so: undefined reference to `u_isalpha_67'
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:1063: megasync] Error 1
make[1]: Leaving directory '/var/tmp/pamac-build-avltbyzn/megasync/src/MEGAsync/src/MEGASync'
make: *** [Makefile:47: sub-MEGASync-make_first] Error 2
==> ERROR: A failure occurred in build().
Aborting...
Is there any way to ameliorate this situation? How would I go about installing the libicuuc.so.67?
If I remember correctly isn’t there a megasync bin file in the aur? I’m sure that’s what I installed, a bin file should be already compiled
2 Likes
Working fine in my Thinkpad E14 2nd Gen, with XFCE, Gnome and the latest kernel (linux511 5.11-rc7)
My trackpoint wasn’t working previously, after this update started working as expected.
There is a looming demand for certain package group to be added - nvidiaXXX.YY-dkms. There seem to be quite a few who use custom kernels, but they cant easily have nvidia modules built in these kernels. An old thread was started with no official replies from either mods or maintainers.
If one wants to install xanmod or other customized kernel, they often have to install some heavily customized or beta/old version drivers from AUR. That way they can get kernel module sources that automatically build.
This is a trivial packaging fix, but leaving things as-is is a big nuisance.
Could somebody bake in some *-dkms packages for nvidia drivers in repositories?
You are on the wrong section. Check this out:
Just out of curiosity, is pamac and pamac-gtk actually a thing anymore? Is it like developed at all?
$ pamac checkupdates
Your system is up-to-date.
Ye right... no it's not.
$ sudo pacman -Syyu
[sudo] password for deemon:
:: Synchronizing package databases...
core 166.6 KiB 2.43 MiB/s 00:00 [------------------------------------] 100%
extra 2002.3 KiB 16.3 MiB/s 00:00 [------------------------------------] 100%
community 6.5 MiB 35.5 MiB/s 00:00 [------------------------------------] 100%
multilib 181.3 KiB 679 KiB/s 00:00 [------------------------------------] 100%
:: Starting full system upgrade...
warning: wine: ignoring package upgrade (5.22-1 => 6.1-1)
resolving dependencies...
looking for conflicting packages...
Packages (56) amd-ucode-20210208.r1828.b79d239-1 bluez-5.55-2 bluez-hid2hci-5.55-2 bluez-libs-5.55-2
bluez-plugins-5.55-2 bluez-utils-5.55-2 btrfs-progs-5.10.1-1 cifs-utils-6.12-1
cryptsetup-2.3.4-2 device-mapper-2.03.11-3 dmraid-1.0.0.rc16.3-13 docker-1:20.10.3-2
enet-1.3.17-1 firefox-85.0.2-1 firefox-i18n-en-us-85.0.2-1 fuse-common-3.10.2-1
fuse3-3.10.2-1 ghostscript-9.53.3-3 git-2.30.1-1 glib2-2.66.6-2 grub-2.04-16
gtk-update-icon-cache-1:4.0.3-1 imagemagick-7.0.10.62-1 json-glib-1.6.2-1 lcms2-2.12-1
lib32-glib2-2.66.6-2 lib32-libunwind-1.4.0-1 libblockdev-2.25-2 libburn-1.5.4-1
libisofs-1.5.4-1 linux-firmware-20210208.r1828.b79d239-1 linux54-5.4.97-1
linux54-headers-5.4.97-1 lvm2-2.03.11-3 nfs-utils-2.5.2-3 nfsidmap-2.5.2-3 pacman-5.2.2-4
parted-3.4-2 pigz-2.5-1 psmisc-23.4-1 pstoedit-3.75-4 python-3.9.1-2
python-packaging-20.9-1 python-soupsieve-2.2-1 python2-packaging-20.9-1 thunar-4.16.3-1
udisks2-2.9.2-1 vim-8.2.2489-1 vim-runtime-8.2.2489-1 vulkan-headers-1:1.2.169-1
vulkan-tools-1.2.166-1 winetricks-20210206-1 wpa_supplicant-2:2.9-8
xfce4-taskmanager-1.4.2-1 xfsprogs-5.10.0-2 youtube-dl-2021.02.04.1-2
Total Download Size: 445.09 MiB
Total Installed Size: 1633.07 MiB
Net Upgrade Size: 28.23 MiB
:: Proceed with installation? [Y/n]
1 Like
2 Likes
lvm2 was upgraded from 2.02 to 2.03, and there were a lot of changes to lvm.conf. It was the only .pacnew. I have been unsuccessful in finding the lvm change log/commit list. Could someone point me to it. I want to find out what happened to use_lvmetad = 0. Thank you.
Is anyone else getting this
Some time back Dolphin had a slow react time when click to open file(s) , I remember that it maybe was a Dolphin/Plasma Issue and then either one or the other caught up and the click to open files was back to its speedy self,
I’m getting the wait to open hesitation from Dolphin again so is this just another wait and wait for Plasma and Dolphin to catch up to each other and opening files will be back on fast response,
I’m not worried about it, it’s just a Dolphin/Plasma hiccup same as happened before
Has anyone noticed this it happens after sitting idle for a while and also happens other times when busy but at random no pattern showing up.
Hope I put this in right place
Thank you