[Stable Update] 2021-04-18 - Kernels, Mesa, Wine, Plasma5, KDE Frameworks, LibreOffice, Bluez

I got a file like that in my home folder too, what is that?

Had no issue using matcha-sea-dark theme on qt apps in previous updates. now it looks like this

link: https://imgur.com/a/JTuji0N

notice how some panes are light-themed and texts are almost impossible to read (using manjaro-gnome)

1 Like
  1. Please wrap your links in single backticks (`) in the future, until youā€™ve reached the required trust level to post links. This will cause them to be rendered like this: https://imgur.com/a/JTuji0N. It just makes it that much easier to read and work with the links.
  2. It looks like a descrepency between QT and GTK applications, specifically, it looks like the GTK apps do not have a dark theme, making them stand out. Ensure this is correct.

Hope this helps!

Solved. Thanks!

Me too.

ā€œyou would actually have been able to login to your desktop even with that old login screen, and then from there you could have changed your SDDM theme to something that worksā€

Thatā€™s the problem, I cant log in when this broken.

Fair enough.

Gnome, 5.4

After the update I have lost RDP functionality in Remmina. So far I have tried reinstalling Remmina, and various RDP plugins. If I find a solution Iā€™ll post for anyone else that has this issue.

No problem with the upgrade. but can someone help me how to make it so that when I upgrade the kernel to a newer version, the package related to the kernel is also upgraded without having to manually declare it.
In my case, when I upgrade the kernel from linux54 to linux510, I also need to include linux510-nvidia and linux510-bbswitch.

This is the output of the command, no difference when the monitor is connected or not:

Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
eDP1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 310mm x 170mm
   1920x1080     60.01*+  59.93  
   1680x1050     59.95    59.88  
   1400x1050     59.98  
   1600x900      60.00    59.95    59.82  
   1280x1024     60.02  
   1400x900      59.96    59.88  
   1280x960      60.00  
   1368x768      60.00    59.88    59.85  
   1280x800      59.81    59.91  
   1280x720      59.86    60.00    59.74  
   1024x768      60.00  
   1024x576      60.00    59.90    59.82  
   960x540       60.00    59.63    59.82  
   800x600       60.32    56.25  
   864x486       60.00    59.92    59.57  
   640x480       59.94  
   720x405       59.51    60.00    58.99  
   640x360       59.84    59.32    60.00  
DP1 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

Yes, that fixes the problem. The check does not like multiple GRUB_DISABLE_OS_PROBER entries, even if it is just a comment.

1 Like

Thanks for posting the link to the check. My grub file had two problems. First, I had added a space between # and GRUB_DISABLE_OS_PROBER=false. Second, I actually needed to delete the #GRUB_DISABLE_OS_PROBER=false comment altogether.

Actually the check is faulty, not your config :slight_smile:

1 Like

Iā€™m having an issue with one of the latest updatesā€¦on KDE/Plasma.

This issue presented itself after the 2021-04-09 update. I figured Iā€™ll just give it a couple of days to try to figure it out or maybe an update will roll out. But since there hasnā€™t any solution out, or I couldnā€™t find any after looking around. I thought itā€™s time to make a post, but the thread for the last update is closed, so Iā€™ll post here.

The problems Iā€™m having is when trying to start applications that are dependent on the aom package for AV1 codec.
So far Iā€™ve seen it on digikam, ksysguard, kdenliva and cantata, mpv with celluloid and also having problem viewing some online content.
And the error message I get if I try to start the applications from the terminal is the following:
[application name]: error while loading shared libraries: libaom.so.2: cannot open shared object file: No such file or directory

I have tried to:

  1. Reinstall aom
  2. Removed aom and build/install aom-git
  3. Reinstall the applications that are affected both standard and building git-versions of them.

I have tried to search and find solutions but to no avail.
The only thing that works is downgrading aom all the way to version 2.0.2-1
I did find this bug report for Arch Linux.

This is working for me for now. But long term, this is a dealbreaker, regardless of where the problems lie or whoā€™s fault it is. I need to trust that the media and codecs are working without any stupid problems like this, for my work.

Matchama-dark theme isnā€™t applying to Manjaro settings manager properly, applied from Kvantum Manager.
Folders is all apps menu (gnome) isnā€™t transparent. Slight transparent folders looked good.
5.10 kernel is now showing as LTS but not showing as recommended in Manjaro settings manager.
Settings not opening for Desktop icons (ding).

1 Like

The update went well, but I have a strange problem with volume, when I press up or down arrow to increase or decrease the volume I hear crackling noise (in YouTube or VLC etc) but not always. Does anyone know what the problem is?

The output of xrandr is weird then.

Does /var/log/Xorg.0.log reveal anything about the missing monitor, maybe that it canā€™t find something?

Do you see something useful when you look at your Settings - Display settings?

Can you try to disconnect eDP1 and only connect the ā€œbrokenā€ monitor? If that isnā€™t working, do you have ways to prove that the ā€œbrokenā€ monitor is actually working?

I noticed that starting Audacity in Manjaro Gnome is killing all audio output. When the Audacity is starting in the background, the Gnome shell starts glitching.