Chosen mirror on the list says it’s updated (United States), but Add/Remove Software states that the system is up to date with no updates. Refreshing manually doesn’t change anything.
I’m running on an RPI4 with the MATE desktop. The system was fully up-to-date till this morning.
I started the update, but got the following warning message:
unable to lock database
failed to synchronize dadabases
I cancelled the update. How can I resolve thiis issue?
I run Manjaro-ARM XFCE on a Raspberry Pi 400 from an SSD when I started to run the current update the following popped up on the screen:
The download and installation went just fine, even got the restart popup, and it restarted just fine. What does this mean and am I going to have any issues because of this?
Question 2: Ever since I did the mouse fix, I have lost the Manjaro loading splash screen. Is there any way to get that back and keep the fix?
I found the solution here:
https://forum.manjaro.org/t/gui-package-manager-unable-to-lock-database-failed-to-synchronize-databases-failed-to-synchronize-aur-database-no-lock-file-found/114741
Deleted db.lck in /var/tmp/pamac/dbs/
Everything ran as expected, without the warining, and no problems with the updated system.
Thank you for the fix. Glad to hear your update went as expected.
GT King Pro updated successfully to Arm-Stable-2022-0710. Gnome-linux-khadas-5.18.5-1.
On Gnome Wayland Session. The mouse movement is jerky or momentarily freezes whenever the mouse cursor/pointer crosses a Window Border.
This mouse movement aslo affect Firefox or Chromium streaming youtube video, whenever the mouse cursor/pointer move a cross a Window Border the video will momentarily freezes/jerk.
On Manjaro-Arm-KDE Plasma 5.25.2 Edition (Unstable Branch) with linux-khadas-5.18.5-1 kernel Wayland session does NOT have this issue.
It seems to only affect Gnome Wayland session and not on Gnome-Xorg session.
1 Like
Maybe it’s xwayland related. Does it happen on pure wayland applications too?
ibus-setup doesn’t start at startup.
Is Gnome-Terminal pure Wayland application?
On other distros on Gnome Wayland (example Fedora 36 Workstation Gnome) have the same issue with kernels 5.18.1 to 5.18.6. With kernel 5.18.9 NO more such momentarily freeze whenever the mouse cursor/pointer move across a Window Border. Basically it is related to early upstream kernel 5.18.y but seems to be resolved with kernel 5.18.9.
I install kernel linux-5.18.9-1 (from Stable Branch) on Manjaro-Arm-Gnome. The install went smoothly with NO errors.
Date: 2022-07-11 Time: 21:10
Manjaro-Arm-Gnome-linux-khadas-5.18.5-1
Install linux-5.18.9-1 to resolve the momentarily freeze of mouse cursor or jerky movement whenever the mouse cursor/pointer crosses a Window Border. On Gnome Wayland only. Does NOT affect KDE Plasma Wayland or Gnome-Xorg Sessions.
jflim@jflim-gtkpro sudo pacman -S linux
[sudo] password for jflim:
resolving dependencies...
looking for conflicting packages...
:: linux and linux-khadas are in conflict (kernel26). Remove linux-khadas? [y/N] y
Packages (2) linux-khadas-5.18.5-1 [removal] linux-5.18.9-1
Total Download Size: 53.94 MiB
Total Installed Size: 80.66 MiB
Net Upgrade Size: 7.24 MiB
:: Proceed with installation? [Y/n] Y
:: Retrieving packages...
linux-5.18.9-1-a... 53.9 MiB 1683 KiB/s 00:33 [######################] 100%
(1/1) checking keys in keyring [######################] 100%
(1/1) checking package integrity [######################] 100%
(1/1) loading package files [######################] 100%
(1/1) checking for file conflicts [######################] 100%
(2/2) checking available disk space [######################] 100%
:: Processing package changes...
(1/1) removing linux-khadas [######################] 100%
(1/1) installing linux [######################] 100%
Optional dependencies for linux
crda: to set the correct wireless channels of your country [installed]
:: Running post-transaction hooks...
(1/6) Arming ConditionNeedsUpdate...
(2/6) Updating module dependencies...
(3/6) Updating linux module dependencies...
(4/6) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
-> -k 5.18.9-1-MANJARO-ARM -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 5.18.9-1-MANJARO-ARM
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [plymouth]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
==> Image generation successful
(5/6) Updating uInitrd...
Image Name: uInitrd Image
Created: Mon Jul 11 21:02:32 2022
Image Type: AArch64 Linux RAMDisk Image (uncompressed)
Data Size: 8378347 Bytes = 8181.98 KiB = 7.99 MiB
Load Address: 00000000
Entry Point: 00000000
(6/6) Updating uImage...
Image Name: uImage
Created: Mon Jul 11 21:02:38 2022
Image Type: AArch64 Linux Kernel Image (uncompressed)
Data Size: 24390144 Bytes = 23818.50 KiB = 23.26 MiB
Load Address: 01080000
Entry Point: 01080000
jflim@jflim-gtkpro
But with the newly installed linux-5.18.9-1, Manjaro-Arm-Gnome NO Longer Boot Up. Cannot find or mount rootfs PARTUUID=f46886d7-02.
Had same issue the last time I tried to install kernel linux from Unstable Branch. This time it if from same Stable Branch.
Does this mean I can NO longer switch kernel from linux-khadas to linux?
Yeah, so it’s not xwayland related.
The GT King Pro is using the linux-khadas kernel for a reason. Likely because there’s not proper mainline support for it yet. Maybe linux-khadas can be updated to 5.18.9+ too soon, @spikerguy will know.
So the issue seems to be an upstream kernel issue, which could likely be fixed with kernel 5.18.9 and above.
I assume it no longer boots, because the the main kernel (linux) is missing some device specific stuff.
Until it gets investigated and fixed, yes.
1 Like
For your information, last year I had been using linux 5.14.y, 5.15.y before. No issue then. If not mistaken @spikerguy tested it on Unstable Branch and he had no issue with linux kernel on GT King Pro.
Thank you for your support.
It is fully supported but due to some config changes its not booting on linux
We’re looking into it.
1 Like
Since the last updates, I got the error that there were unmet dependencies.
could not satisfy dependencies:
- unable to satisfy dependency ‘edk2-ovmf’ required by qemu-system-x86
- unable to satisfy dependency ‘seabios’ required by qemu-system-x86
- unable to satisfy dependency ‘qemu-system-x86’ required by qemu-desktop
- unable to satisfy dependency ‘edk2-armvirt’ required by qemu-system-aarch64
- unable to satisfy dependency ‘qemu-system-aarch64’ required by qemu-emulators-full
As a last resort I removed qemu, libvirt and vmm.
As I went through my notes to install it again, I see I installed the package qemu, which seems to be gone now. That would explain the dependencies error.
Total CPU usage plasmoid remains unusable on RPI4 here.
Hi @spikerguy,
Your new linux-5.18.10-2 resolved the issue. I can now boot up with linux-5.18.10-2 and also it resolved the momentarily freeze whenever the mouse cursor/pointer moves across Window Border on Gnome Wayland.
Thank you for your great support. Look forward to the release of linux-khadas-5.18.10.
2 Likes
Running Xfce4 on Raspberry Pi 400, was using FKMS video driver before the 22.06 update, but got the well known very bad mouse lag and had to switch over to KMS.
After that HDMI display sleep is not working.
With DPMS enabled, any screensaver/power management sleep mode makes the display go blank, lose video signal and eventually go to sleep. Immediately when the display would go to sleep, the video driver wakes up again. Seems like there is some new input event that triggers a wakeup when the display goes to sleep.
There is no observable difference between forcing different sleep modes with
xset dpms force (standby|suspend|off)
With DPMS disabled, sleep modes just blanks display with backlight on, as expected, because no DPMS signalling is asking it to power down.
Going back to the FKMS driver, DPMS sleep works as expected, but that’s not really an option given the severe performance issues.
On PinePhone I had to downgrade chatty to version 0.6.6-1 as when I received an SMS the chatty crashed and didn’t start anymore. Found existing issues:
EDIT: and issue seems to be fixed in the package version 0.6.7-2 which is now available in the repository.
I run Manjaro-ARM XFCE on a Raspberry Pi 400 from an SSD. Ever since I did the mouse fix, I have lost the Manjaro loading splash screen. Is there any way to get that back and keep the fix?
EDIT I’m using Pinebook Pro and I managed to fix the problem by switching mesa package from mesa-git to stable mesa from the official repo 
Hi
Since the update I’m having problems with running gnome-shell
ibmutter-Message: 16:39:30.399: Running GNOME Shell (using mutter 42.3) as a X11 window and compositing manager
libEGL warning: DRI2: failed to authenticate
libEGL warning: MESA-LOADER: failed to open swrast: /usr/lib/libLLVM-13.so: version `LLVM_13' not found (required by /usr/lib/dri/swrast_dri.so) (search paths /usr/lib/dri, suffix _dri)
Failed to setup: Unable to initialize the Clutter backend: no available drivers found.
I’m able to start some gnome applications like nautilus or gnome-control-center through Openbox but that’s it.