Barry writes:
The problem is no one is maintaining the X11 code.
All the people that used to work on X11 moved on to wayland
after it became very clear that X11’s design was preventing implementation
of features that end users wanted.
So if you stick on X11 you will be running code that is unm
Can anyone vouch for having a reliable, established, experience with
debuginfod?
My 'make check' runs valgrind a bunch of times. Right now, each invocation
is sitting and doing nothing for about ten minutes, before it apparently
times out downloading something from debuginfod.fedoraproject.
Am 17.04.24 um 17:51 schrieb Go Canes:
Step by step:
I recently had similar problems. These are the things to check:
o use blkid to get the current UUID(s)
The current UUIDs correspond to the ones in /etc/fstab, that hadn't been
changed btw.
o check /etc/kernel/cmdline if it exists - make sure
Am 17.04.24 um 18:45 schrieb Felix Miata:
Klaus-Peter Schrage via users composed on 2024-04-17 16:48 (UTC+0200):
After many years of maintaing dual boot setups (Fedora/Windows) my
harddisk layout got a bit confusing: Linux and Windows partition were
scattered on mainly two harddisks (all gpt).
On Fri, Apr 19, 2024 at 9:31 AM Klaus-Peter Schrage via users
wrote:
> But, as Felix had proposed in his post, I dived a bit deeper into
> efibootmgr (also new to me up to know), and found out that entries point
> to PARTUUIDs, in my case:
> FedoraHD(3,GPT,1ca6f5eb-cbea-11e9-a525-4ccc6ad8789c,0x24
