I think my issue is related with how Acer’s UEFI handles efi files.

I removed the label using gparted and then confirmed the changes and rebooted, however the results are still the same. I am now testing the solution in the askubuntu thread you shared.

I added EFI label to the EFI partition. At least it shows that tag in gparted.

sda is the USB stick with currently live booted Fedora KDE. mmcblk1 is the internal disk I want to install on.

Disk /dev/sda: 7.45 GiB, 8002732032 bytes, 15630336 sectors
Disk model: Cruzer Blade    
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: EB4BE656-6730-46CE-819A-784A2C115F93

Device       Start     End Sectors  Size Type
/dev/sda1       64 5454691 5454628  2.6G Microsoft basic data
/dev/sda2  5454692 5480551   25860 12.6M EFI System
/dev/sda3  5480552 5481151     600  300K Microsoft basic data


Disk /dev/mmcblk1: 116.48 GiB, 125069950976 bytes, 244277248 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C75BAF61-B578-41D5-8C6C-8505ABF109A8

Device           Start       End   Sectors  Size Type
/dev/mmcblk1p1    2048   1050623   1048576  512M EFI System
/dev/mmcblk1p2 1050624   9439231   8388608    4G Linux swap
/dev/mmcblk1p3 9439232 244275199 234835968  112G Linux filesystem


Disk /dev/mmcblk1boot0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mmcblk1boot1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop0: 2.43 GiB, 2607599616 bytes, 5092968 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/zram0: 3.66 GiB, 3930062848 bytes, 959488 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Here’s blkid output:

/dev/sda1: BLOCK_SIZE="2048" UUID="2024-10-24-15-05-12-00" LABEL="Fedora-KDE-Live-41-1-4" TYPE="iso9660" PARTLABEL="ISO9660" PARTUUID="eb4be656-6730-46ce-819b-784a2c115f93"

I know that this is not a Linux specific problem either, however I didn’t know where else to ask.

AFAIK on most distros and desktop environments the default file manager can read NTFS partitions without any further setup needed.

I dual boot Fedora with secure boot enabled for half a year already on my notebook with exactly 0 problems. Did few Windows updates already.

One of the few supporrting extensions on mobile and also you can move the toolbar to bottom to reach it with your thumb like a normal human and do not have to lift your hand to reach it like in Chrome mobile?

I don’t know what everybody sees in circle to search. Isn’t it just Google Lens which you can get on any other phone? I can make a screenshot and share ot with Google Lens to get the same result right?

I actually found Cinnamon to be more resource intensive than Gnome on most computers.

When excalidraw was mentioned in another comment I think it would also be worth to mention tldraw even though I don’t kniw whether it can be counted as an replacement since I never used draw.io.

https://github.com/tldraw/tldraw

Oh boy you’re gonna love YTDLnis https://github.com/deniscerri/ytdlnis

The Xiaomi Android One line-up was unlockable without any hassle, but is long time discontinued. I used to use the Mi A2 lite as my main phone and you could just unlock it yourself offline. Only thing blocking you from doing it was the OEM unlocking toggle in developer settings. I still have the phone and it is running Android 14 like a charm.

RCS is an open standard, but Google’s implementation of it isn’t AFAIK. That’s why there exist no 3rd party RCS client outside of those praised by Google.

Change for the sake of change. At least it seems to be in a good direction.

I don’t understand why the control panel UI wasn’t modernized instead? Would that really be unfeasible? I think it still might have been less work than to maintain 2 coexistent “settings/control panel” apps and migrate from one to another. Sometimes you have to throw out the old code base and start from scratch. But if you do so shouldn’t you rather distrubute the result when your finished and not in a half-baked compromise-like state?

deleted by creator

they never worked very reliably in my experience.

It works perfectly on my phone (Poco X3 NFC). It is probably different from phone to phone.

deleted by creator

On Android, from FDroid you can install an app called Seal

I like ytdlnis more.