Changes for page Desktop
Last modified by Alexandru Pentilescu on 2025/06/27 19:04
From version 7.1
edited by Alexandru Pentilescu
on 2024/08/18 11:47
on 2024/08/18 11:47
Change comment:
Attachment Screenshot_20240818_144411.png moved to scaling X11.png.
To version 10.1
edited by Alexandru Pentilescu
on 2025/05/11 13:22
on 2025/05/11 13:22
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -23,6 +23,20 @@ 23 23 == Solution == 24 24 The cause was having the wallpaper set to Hunyango. Apparently that wallpaper required constant buffering or inefficient allocation every minute or so, since it was in a permanent loop. Reported the bug to KDE devs, so maybe this will get fixed, eventually. 25 25 26 += Linux not booting up from GRUB screen after installing a kernel update = 27 + 28 +== Description == 29 +Title says it all. Trying to boot from the latest Linux kernel image from GRUB will prompt an error screen saying something along the lines of "Could not find initramfs-6.12.5-200.img", shortly before a new screen containing a kernel panic will appear. Cause is known. Maybe an incomplete update happened? 30 + 31 +== Solution == 32 +Run the following command to solve the problem: 33 + 34 +{{code language="bash"}} 35 +sudo dracut --kver 6.12.5-200.fc41.x86_64 --force 36 +{{/code}} 37 + 38 +Obviously you'll have to replace the kernel version with the one that is not booting correctly. 39 + 26 26 = X11 apps like Bisq having a very small font on Hi-resolution KDE desktop = 27 27 28 28 == Description == ... ... @@ -31,5 +31,20 @@ 31 31 == Solution == 32 32 KDE Plasma offers a solution to this by under Display Configuration settings. Over there, you'll have an option of how to treat Legacy applications (X11). Under that setting, you have to manually choose "Scaled by the system". That will force the system to manually magnify the X11 applications automatically in the future. 33 33 34 -[[image:scaling X11.jpg]] 48 +[[image:scaling X11.png]] 49 + 50 += Monero GUI keeps rescanning the full blockchain every time you open it = 51 +== Description == 52 +When you open the Monero GUI, it keeps rescanning the full blockchain from scratch after every system reboot. There is clearly no persistence being stored on the drive, which indicates a permission problem. Moreover, when you go to Settings -> Info, you will see that the Wallet path is always under /run/user/... which is strange, since the wallet file is under my home directory. This needs fixing. 53 + 54 +== Solution == 55 +I fixed this by rewriting the permissions for the flatpak of the Monero GUI app to explicitly have access to my directory path under my home directory. I did it as such: 56 + 57 +{{code language="bash"}} 58 +sudo flatpak override org.getmonero.Monero --filesystem=/home/alex/Monero/wallets/ 59 +{{/code}} 60 + 61 +Under that path, I store both of my wallets: py P2Pool Monero wallet as well as my personal Monero wallet. Please note that you need sudo permissions to make this work. 62 + 63 +Good luck :) 35 35 )))