[Stable Update] 2021-02-19 - Kernels, AMDVLK, Palemoon, Firefox-dev, Firefox, Haskell, Python

Hi @salome,

I use KDE, but I’ve just installed lxtask to test this and mine works flawlessly.

  • Are you sure you default browser is set correctly?
  • Or it might be a MIME type association.

Unfortunately, I don’t know where else to check or/and test.

Hope this helps.

Edit:

Accoring to this page:

Alternate way is to add the following line export BROWSER=/usr/bin/firefox to your ~/.bashrc

So, assuming you use ZSH, the command to make that permanent would be:

$ echo "export BROWSER=<directory_to_browser_executable>" >> ~/.zshrc

If you use bash the command would be:

$ echo "export BROWSER=<directory_to_browser_executable>" >> ~/.bashrc

For example, in my case the directory is

/usr/bin/firefox

So the command would be

$ echo "export BROWSER=/usr/bin/firefox" >> ~/.zshrc

That should, in theory at least, set it.

Hope this helps!

Thanks for that info. Switched to lz4 cause I’m planning to stay on 5.4 LTS for a long time. My old iMac 13,2 (27" late 2012) cannot change display brightness with newer kernels…

Everything good on two computers running KDE and one with XFCE.

Since we support older LTS kernels this change won’t be made on our end.

No, it’s about the Arch default. We have our own kernels and mkinitcpio package.

4 Likes

Update broke HDMI over USB-C on pinebook pro. Solution:
sudo pacman -Syyu linux-pinebookpro linux-pinebookpro-headers

A post was split to a new topic: How can i work with the KDE development ISO?

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!). :crazy_face:

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:

I use megasync-nopdfiumAUR without issue.

megasync-binAUR might also work

1 Like