[ARM Stable Update] 2020-10-27 - KDE Plasma, Firefox, Uboots and Kernels

Out of interest, what’s the best interpretation of figures such as these? Would the additional 30 packages most likely be additional packages ported to aarch64 that were not previously available on this architecture, or packages splitting?

Likely packages added to the Arch Linux repositories in general. :slight_smile:

I successfully update my rpi 4 4G.

[vidi@vidticus-miniman ~]$ screenfetch
                             vidi@vidticus-miniman
                             OS: Manjaro-ARM 20.10
                             Kernel: aarch64 Linux 5.9.1-1-MANJARO-ARM
         #####               Uptime: 7m
        #######              Packages: Unknown
        ##O#O##              Shell: bash 5.0.18
        #######              Disk: 9.6G / 112G (10%)
      ###########            CPU: BCM2835 @ 4x 1.5GHz
     #############           GPU: 
    ###############          RAM: 1080MiB / 3742MiB
    ################        
   #################        
 #####################      
 #####################      
   #################        
                            
                            
                            
[vidi@vidticus-miniman ~]$ uname -a
Linux vidticus-miniman 5.9.1-1-MANJARO-ARM #1 SMP PREEMPT Mon Oct 19 11:53:29 CDT 2020 aarch64 GNU/Linux

It was also the fastest boot I have had so far, so pretty happy.

No issues here on Pinebook Pro, thanks for the hard work!

2 Likes

Just updated on the Pinebook Pro. The sizing of the taskbar system tray icons is a bit all over the place. The date appears to have shrunk, while the other icons have increased on size. I’ve just checked the journalctl logs and the following error is present:

file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/main.qml:460: TypeError: Cannot read property 'length' of undefined

There are a few others relating to qt.qpa.xcb: QXcbConnection:, and one relating to kf.plasma.core:

In the good spirit of reporting things that work now for me that previously made trouble I am happy to report that both terminal emulations Alacritty and Kitty work now with the standard mesa drivers.
(They might have worked before and I was just not aware)

One thing is to do though. For both programms to work a terminal variable has to be set for each of them:

export MESA_GL_VERSION_OVERRIDE=3.3 MESA_GLSL_VERSION_OVERRIDE=330 alacritty
export MESA_GL_VERSION_OVERRIDE=3.3 MESA_GLSL_VERSION_OVERRIDE=330 kitty

After the respective variable is set the terminal emulation should start

1 Like

Sounds like these applications require a higher level of OpenGL, than Panfrost supplies by default. :slight_smile:

1 Like

I’m experiencing graphics artifacting on my Pinebook Pro when I reboot the device. There aren’t any issues when I shutdown normally or hard shutdown, and then startup using the power button. I’m not sure if this happens in other versions since I only just got the device. I flashed the eMMC using manjaro-arm-installer just a few hours ago. The only modification I’ve made is switching Firefox for Chromium.

Here’s a video showcasing the behavior:

System information:

Operating System: Manjaro-ARM
KDE Plasma Version: 5.20.1
KDE Frameworks Version: 5.76.0
Qt Version: 5.15.1
Kernel Version: 5.9.1-3-MANJARO-ARM
OS Type: 64-bit
Processors: 6 × 
Memory: 3.7 GiB of RAM
Graphics Processor: Mali T860
1 Like

I don’t think it’s the update… Might be the manjaro-arm-installer. I’m having the same problem with my pinebook pro which arrived last week. I flashed manjaro i3 to emmc via manjaro-arm-installer and since then every 2 boots out of 10 is like this… Just submitted a ticket about it and been told that I should disable the emmc and flash android to an sdcard and see if it boots from it. If it doesn’t boot it’s a faulty emmc, if it boots it’s a software issue…

I don’t think it’s a faulty eMMC, since the boot works sometimes.
But i don’t know. I have never experienced this issue on my dev unit.

Hi,

Odroid n2 kde up to date, it works.

[nln2@n2 ~]$ date -u
mer. 28 oct. 2020 13:33:06 UTC
[nln2@n2 ~]$ screenfetch
                             nln2@n2.20.06
                             OS: Manjaro-ARM 20.10
                             Kernel: aarch64 Linux 5.9.0-1-MANJARO-ARM
         #####               Uptime: 3m
        #######              Packages: Unknown
        ##O#O##              Shell: bash 5.0.18
        #######              Resolution: 1920x1080
      ###########            DE: KDE 5.75.0 / Plasma 5.20.1
     #############           WM: KWin
    ###############          GTK Theme: Breeze [GTK2/3]
    ################         Icon Theme: oxygen
   #################         Disk:
 #####################       CPU: Unknown @ 6x 1.992GHz
 #####################       GPU: 
   #################         RAM: 652MiB / 3628MiB
                            
                            
                            
[nln2@n2 ~]$ uname -a
Linux n2.20.06 5.9.0-1-MANJARO-ARM #1 SMP PREEMPT Mon Oct 19 08:34:37 +03 2020 aarch64 GNU/Linux
[nln2@n2 ~]$ 

I’ve also noticed that the latest version of rkward doesn’t seem able to open files from dolphin. The following output is produced in journalctl:

Oct 28 16:32:21 Scatha systemd[1052]: Started RKWard - GUI for R.
Oct 28 16:32:22 Scatha rkward[52846]: QCommandLineParser: already having an option named "h"
Oct 28 16:32:22 Scatha rkward[52846]: QCommandLineParser: already having an option named "help-all"
Oct 28 16:32:22 Scatha rkward[52846]: QCommandLineParser: already having an option named "v"
Oct 28 16:32:22 Scatha kwin_x11[1113]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 33051, resource id: 106954763, major code: 18 (ChangeProperty), minor code: 0
Oct 28 16:32:22 Scatha systemd[1052]: app-org.kde.rkward-7b3e087e0ec949f78445b28172c0d2f6.scope: Succeeded.
Oct 28 16:32:22 Scatha kwin_x11[1113]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 33061, resource id: 83886195, major code: 18 (ChangeProperty), minor code: 0

Files can still be opened from within rkward.

Updated my Pinebook Pro to Kernel 5.9.1-3-MANJARO-ARM.
Experiencing issues with sleep when “SuspendState=mem”. Pinebook simply does not wake up from sleep, have to hard reset it.

Changing conf to “SuspendState=freeze” solves the issue but I have experienced battery drain with this so it is not an ideal option.

1 Like

I’ll second this (Algismo), failed to wake
downgraded to 5.8.14, OK, enters/leaves suspend 3

1 Like

For what it’s worth, that reboot issue shows up regardless of whether I boot from the microSD card or eMMC. That being said, I did flash both using manjaro-arm-installer. I flashed the card from my PC so I could flash the eMMC from the Pinebook.

I have never had a failed cold boot from a shutdown, but without fail rebooting causes the artifacting. Maybe I should try an actual image.

Let me know how it goes with an image mate. I’ll write back if I have something new.

The same thing happens on reboot even when I image the card using Manjaro-ARM-kde-plasma-pbpro-20.10.img, the latest download available. So I don’t think it has to do with the image installer or this version.

I think I found a relevant thread here: Problem with the LCD screen when rebooting Pinebook Pro

For me, starting dolphin freezes entire system. Hard way.

No matter mesa or mesa-git.

I found that firefox with wayland and webrender enabled leads to massive kernel memory leaks. I wonder if it’s the same issue.

I can confirm this. PBP deep sleep will not wake up after update.

1 Like