[ARM Stable Update] 2020-11-08 - Manjaro ARM Tools, OBS Studio, Kodi and Kernels

ARM Stable Updates
42

OBS crashes for me as well. I’m using the es2 versions of qt5.
Lets see if I can find that script to switch between es2 and normal qt5 quickly

Okey, in theory it should be just a few packages: qt5-base qt5-declarative qt5-multimedia
https://github.com/McMarius11/Pinebook-Pro/blob/master/graphics_driver_pf_fb.sh

In practice I’ve forgotten what I have been doing on my PBP :smiley: I’m pretty sure I have at least 5 packages that are for plasma-mobile on it which aren’t too happy to go back to regular qt5.

43

Well, as it turns out… Kate is dependent on qt5-base-es2 as well. But if my painful reinstallation of QT5 related stuff, which is probably 90% of what I have on the PBP, doesn’t work… I’ll give this script a look.

44

I’ll be going the other way around - currently choosing the sacrificial sd card. I’ll place a new install of Manjaro KDE (which should be coming with qt5-base if I recall correctly) on it and see how that goes before messing with my main install on the eMMC. Well… at least before messing more with my main install anyway

45

Hah . Now my machine is hanging on startup. So I guess I’m looking at getting an SD Card and doing a fresh install anyway… And I had so much configuration done!

46

Most likely you can still save the configs from your home folder. But yes - use the sd card when in doubt or prepare a good strategy for recovering the setup before jumping into action :slight_smile:
At some point I would have to take a look at btrfs for the emmc

47

Alright, results when it comes to OBS - requires qt5-base instead of it’s es2 equivalent qt5-es2-base and you have to set PAN_MESA_DEBUG=gl3 to get it working.
My desktop has Nvidia GPU so this has been my first time trying to do it from Wayland - nope, had to use Plasma with the X session.

Now, this is a small test capturing the PinePhone from the Pinebook Pro :partying_face:
https://youtu.be/iT6eL1_RBqk

48

Thanks for the confirmation. At least my reinstallation should fix it. Which image did you use?

49

I went directly with the manjaro-arm-installer instead of passing around images.

1 Like
50

Hi,

Odroid c2 kde and odroid n2 kde up to date, they work.

51

How did it go with your PBP? Have you been able to solve thte issue?

52

Hi, I still can’t reach desktop after the last update. The desktop remains loading without finishing proposing the password. I’m on rockpi4b (manjaro 20.10) and this happens with the last update (2020/11/08)
Can somebody help me?

53

Alright! I got my SD card in and was able to reinstall and get OBS etc working.

Are you having odd behavior with mntray though? A left click brings up a window; right click brings up what I’d expected out of a left click.

Other than a few theme oddities (the package manager GUI being blue instead of green, etc) and that it so far seems good, and running well. I do appreciate your assistance getting me here.

EDIT: I realized immediately after posting this that I was starting with Plasma Wayland. Switching off fixed all of the oddball issues.

1 Like
54

I updated my PBP last week. Everything seemed fine at the time. I continued using it and then shut it down. It froze on the splash screen though next time I booted (circling dots freeze). Is there a keystroke I can use at boot to make the initialization verbose? I use KDE. I’m temporarily displaced, so creating a bootable SD card to fix it is a bit of a challenge right now.

55

In a manner of speaking. I loaded a fedora cinnamon SD card to troubleshoot and then decided to try it for a bit.

I was able to boot manjaro xfce from an SD yesterday without issue. So I suspect that a nuke and pave would have solved the problem.

56

Hi. I’m trying to log in with Xfce 20.10 release on Rockpi4. After updating the system, when I reboot, I am left with the manjaro icon without being able to start desktop. Before the first reboot, reach to get this information:

System status lightdm.service - Light Display Manager
Loaded: loaded (/usr/lib/systemd/system/lightdm.service; enabled; vendor preset: disabled)
Active: active (running) since Tue 2020-11-17 19:22:17 -03; 17min ago
Docs: man:lightdm(1)
Main PID: 648 (lightdm)
Tasks: 4 (limit: 4461)
Memory: 148.6M
CGroup: /system.slice/lightdm.service
├─648 /usr/bin/lightdm
└─654 /usr/lib/Xorg :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch

nov 17 19:22:17 GG systemd[1]: Starting Light Display Manager…
nov 17 19:22:17 GG lightdm[648]: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not prov>
nov 17 19:22:17 GG systemd[1]: Started Light Display Manager.
nov 17 19:22:18 GG lightdm[669]: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not prov>
nov 17 19:22:18 GG lightdm[669]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=972) by (uid=0)
nov 17 19:22:24 GG lightdm[718]: pam_systemd_home(lightdm:account): Not a user managed by systemd-homed: No home for user gg known
nov 17 19:22:24 GG lightdm[718]: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not prov>
nov 17 19:22:25 GG lightdm[648]: g_dbus_connection_call_sync_internal: assertion ‘G_IS_DBUS_CONNECTION (connection)’ failed
nov 17 19:22:25 GG lightdm[718]: pam_unix(lightdm:session): session opened for user gg(uid=1000) by (uid=0)

57

I have the same problem. I’m using Raspberry Pi 4 4GB, KDE desktop, and an SSD as both boot and root partition. It’s stuck at either “started hostname service”, “starting network manager script dispatcher service” or “started network manager script dispatcher service”

@Darksky This is my config.txt:

gpu_mem=64
initramfs initramfs-linux.img followkernel
kernel=kernel8.img
arm_64bit=1
enable_gic=1
disable_overscan=1

dtparam=audio=on
hdmi_drive=2

dtoverlay=vc4-fkms-v3d
max_framebuffers=2

over_voltage=6
arm_freq=2000

hdmi_mode:0=82
hdmi_group:0=2
hdmi_force_mode:0=1
hdmi_ignore_edid:0=0xa5000080
58

I have not tested on the pi4 4G. Will do now…

59

Many thanks for your time! Although I cannot go into desktop, I could SSH into it so I can start services all fine. So it’s not an urgent issue to fix :slight_smile:

60

I am at a loss right now. My pi4 4G booted ok also. Do you all have the new firmware-raspberrypi in the unstable branch?

61

I’m not sure… could you please give me a command to check and I’ll paste the output here?