it’s probably a file on the disk somewhere so try using the find command on / and filter name by *.icc extension. You should spot it from there.

It’s my personal top candidates in the order of my preference (best to worst) from my notes when I was researching this topic for my parents. (funnily enough, they ultimately settled on kdenlive, despite not being very computer proficient, because they found more step by step yt guides for what they wanted to do with it)

All still actively maintained.

I played around with each of those for a bit some time ago and they were quite similar, so you can pick by your personal preference.

https://www.openshot.org/

https://flathub.org/en/apps/org.pitivi.Pitivi (there is still active development on their git, but for some reason the release is quite old)

https://www.shotcut.org/

https://jliljebl.github.io/flowblade

“people”

https://en.wikipedia.org/wiki/Autism

may present as […] lower-than-average intuitive perception of […] certain aspects of sarcasm

Interesting discussion, the opinions go both ways but the official ones seem to disregard some facts and base the decision on some arbitrary ones that were not listed in OPs linked article, which I find quite biased or at least untransparent.

You could have guessed from the context that it is another privacy focused messenger app

And no mention of threema even though it fulfills all their listed criteria

to me that smells like what I said in the other comment:

Wayland might be a bit stricter when it comes to following specs and not implementing hacky workarounds. (or it could always be a bug)

I feel like, if a cable is high quality and up to spec, it will work with wayland. But if the signal integrity is below spec, wayland might fall back to slower signaling while x11 is more lax and ignores the issue and so a worse cable still works even if unnoticably below spec quality. Or the 4k over hdmi 1.3 is some hack that x11 supports and wayland doesn’t because it’s out of spec.

But thats just a feeling. May be wrong.

Thanks for reporting back with your findings!

What distro btw?

afaik you just listed features that the printer I mentioned (or if I am wrong, other similar printers) supports

it’s my bad for not mentioning all possible workflows, I was just a bit lazy and thinking of my personal documents only, which do not work well with further smart automation, because my batches are highly irregular. So the more manual approach is the best for me currently. Maybe possible with some future AI integration.

please elaborate

Epson WorkForce DS‑730N

put 100 sheets on the tray, it scans them all and either puts them all into a single pdf or multiple pdfs. Then you split / merge them in software.

You could buy an automatic scanner that takes a stack of docs and dumps the files to a network share.

Thats very interesting.

Do you maybe know if your gnome system was using x11 and your kde one is using wayland? Wayland might be a bit stricter when it comes to following specs and not implementing hacky workarounds. (or it could always be a bug)

Oh and if you do try out other cables, give us an update. I’m curious if it will work.

The stuff you describe sounds like a cable timing issue. Not something you can fix in Linux. Think of it like the two devices trying to talk to each other on different frequencies and picking the highest res one that works. (so thats why they might get stuck on a random smaller one)

I had some examples like that in the past where some low quality or very long cables couldn’t reach it’s spec, even fresh out of the box, even on windows.

Oh, also I am pretty sure HDMI 1.3 does not do 4k at all. Either 1080 or 1440p was the spec limit.

If you can space the money for an experiment try an active DP 1.2 → HDMI 2.0 cable/adapter.

Maybe something like https://www.delock.com/produkt/85956/merkmale.html or Digitus branded. Depending on what known good cable manufacturer is available in your area.

You can mostly just copy your home partition/dir with something like rsync.

Step by step:

1. Install new distro, in the installer make sure to use the same username (otherwise there is some extra work involved but still doable)

2. start up new distro to make sure it works

3. reboot into old distro or into live linux

4. use rsync to copy olddistro/home/user to newdistro/home/user (you have to think about whether it makes sense to overwrite all files or if there is maybe some special exception somehow. Like there may be some idiomatic bashrc on one distro that does not work well with the other)

(I’ve done that multiple times now and there is some minor fixing involved sometimes, like with the bashrc example, but otherwise it’s super easy. If you ever get stuck just hit me up and I can hop on a Rustdesk/discord/whatever support session)

for me even typing “sudo pacman -Syu” is masochism compared to just pressing the “Update” button in the gui package manager.

I super agree. I try to do as much as possible on Linux via GUI because I can remember where a button is, but I can’t remember all the flags and parameter quirks of each command.

I just enjoy looking shit up for strangers on the internet and being a smartass …

# CUT (fast, keyframe-aligned, no re-encode)
ffmpeg -ss 00:01:30 -to 00:02:10 -i input.mp4 -c copy cut.mp4

# CUT (accurate, re-encode)
ffmpeg -i input.mp4 -ss 00:01:30 -to 00:02:10 -c:v libx264 -c:a aac cut.mp4


# MERGE / CONCATENATE (same codecs, no re-encode)
printf "file 'a.mp4'\nfile 'b.mp4'\n" > list.txt
ffmpeg -f concat -safe 0 -i list.txt -c copy merged.mp4


# MERGE (different formats, re-encode)
ffmpeg -i a.mp4 -i b.mp4 -filter_complex \
"[0:v][0:a][1:v][1:a]concat=n=2:v=1:a=1[v][a]" \
-map "[v]" -map "[a]" merged.mp4


# TRANSITION (video crossfade, keep audio from first clip)
ffmpeg -i a.mp4 -i b.mp4 -filter_complex \
"[0:v][1:v]xfade=transition=fade:duration=1:offset=4[v]" \
-map "[v]" -map 0:a transition.mp4


# ADD TEXT (overlay)
ffmpeg -i input.mp4 -vf \
"drawtext=text='Hello world':x=20:y=20:fontsize=32:fontcolor=white" \
-c:a copy text.mp4


# ADD AUDIO TRACK (replace existing audio)
ffmpeg -i input.mp4 -i music.mp3 \
-map 0:v -map 1:a -c:v copy -shortest out.mp4


# ADD AUDIO TRACK (mix with existing audio)
ffmpeg -i input.mp4 -i music.mp3 -filter_complex \
"[0:a][1:a]amix=inputs=2:duration=shortest[a]" \
-map 0:v -map "[a]" out.mp4


# CHANGE SPEED (2x video, drop audio)
ffmpeg -i input.mp4 -vf "setpts=0.5*PTS" -an fast.mp4


# SCALE / RESIZE
ffmpeg -i input.mp4 -vf scale=1280:720 resized.mp4


# SUBTITLES (burn in)
ffmpeg -i input.mp4 -vf subtitles=subs.srt out.mp4

Check out the docs for more https://ffmpeg.org/ffmpeg-doc.html