Hmm, I can't say I've seen that before. However, it might be worthwhile trying to just boot a live ISO of GNOME (or any other DE) just to rule out a KDE issue. Then if that doesn't replicate the problem, try a live distro of something with a newer version of KDE (such as Fedora 39).
At the very least, that'll help narrow down where the problem might be coming from!
It's a shame that history has repeated itself with Implicit sync (AMD/Intel) vs Explicit Sync (Nvidia) - except this time Nvidia is still not going to go for Implicit sync (apparently due to the "unified architecture" of their driver, this would mean switching Windows over to implicit sync as well) so they're trying to get support for explicit syncing added into most of the compositors/XWayland.
That one flaw is what finally got me to pickup an AMD card this month. Due to the fact that Nvidia is the odd one out, the result is that when using apps through XWayland, you end up with random spots of the application displaying previous frames making it unusable for my case. Talk about a night and day difference that has been.
This is what I do, I can't speak for Mint's screenshot tool, but Spectacle for KDE will indeed freeze the whole screen after a set timer - allowing you to open context menus and whatnot. Then on the "frozen" image you can highlight only a specific section of the screen to screenshot, make annotations, etc.
Spectacle is one of the things I miss the most every time I try out GNOME again for a bit.
I mean, to play devil's advocate here - if functionality that you need is all of a sudden swept out from under you then it doesn't matter from an end user perspective if it's not the intended design for Wayland - to the user, Wayland is broken in that regard.
A better equivalent would be if an application you used every day for the last 10 years all of a sudden has an update that kills features you used because that's no longer part of the dev(s) vision. Or headphone jacks on phones. Or whatever that weird thing with Teslas where they disabled a sensor in an OTA update and replaced it with some other solution(?).
Or to modify the example you put, if Windows killed the cmd shell and only left powershell in a Windows Update.
I have an application that I need to use at work which will never fit Wayland's design, short of me either finding a new job, keeping a Windows install around, or using a really old version of Linux around in a VM when X11 has completely disappeared from all distros (which won't really work) - there will be nothing that I can do about it on the Wayland side because it's highly unlikely the devs will update it to be compatible (since it's a shock that they actually even had Linux support in the first place).
As it is, I currently just pop into an X11 session whenever I'm on working hours, it will suck that I can't do that with Fedora come next release when they completely drop X from the repos.
Plenty fair enough! I haven't used Geany in a long time, and never actually ended up trying it as a code editor (rather than just the every once in a while one-off-quick-texr-editor) unfortunately, otherwise I'd have tried to answer your question directly.
I do think that it's alright to only accept PRs, just so long as it's made a bit more clear. If I ever ran into a problem with Geany, I'd be completely unable to do anything as I have very little experience with C, let alone GTK and all of the other libraries along with it. I could learn right to effectively flip a few values or even maybe try to correct a basic logic issue - but that's about it.
That all being said, I hope someone is able to answer your question one way or another! Normally I'd recommend trying to reach out to the project's chat since they usually have an IRC channel, Matrix channel, or some other place - but in this specific case after seeing the issues you mentioned I'd definitely be hesitant to do that sadly...
I'm not much of a user in this regard, so I can only comment on the abstract of the question here - but over the last couple of months I started some new medication that caused this. I'd never remember dreaming for quite a while, and then all of a sudden I did start to have very vivid dreams.
They're not nightmares, thankfully - but certainly the ones that make you wake up and go "What the fuck???". Recently I had a dream about a game show being started in my house, and the game was very much a "You can't leave until you meet X goal".
Then there have been some dreams that were not necessarily odd, not bad, but not "good" I guess?
Last week I had a dream where my boss had asked me to start working again on a project that I lead that was dropped midway. When I woke up, since it was still fresh on my mind, I was very close to messaging my boss to see if he wanted to better set the goals and requirements for the project... Until I realized that the conversation about reopening the project never happened. Thankfully I did realize that, or else it would've been quite awkward...
That last one worried me a bit, because I really don't want to start having dreams that cause me to not be able to keep an accurate accounting of what is real and what isn't - but thankfully it hasn't reoccurred.
I've just somewhat woken up, and definitely had another "WTF" dream, though I am unsure of what it actually was about.
That's plenty fair enough, and I apologize for not looking into their issues to see what their receptiveness was like - I originally replied while I was at work and my break was unfortunately coming to an end or else I probably would've caught that and not mentioned it, whoops!
In retrospect I should've known, I forgot that Geany is a GNOME project and... well, they have a bit of a reputation for uh... let's just say that I myself am always hesitant to submit bug reports myself. It's a tough one, because I try to play devil's advocate on why they tend to be like that and had even commented yesterday on a video about GNOME devs always getting a lot of hostility. On one hand, there's certainly a reason why they tend to have that response, but it's still a bad sign when it starts to color their whole team since I know there are plenty of devs there who don't have that sort of response.
Either way, I apologize if it came off pushy - it was definitely intended to be more on the encouragement side of things rather than a firm "you must do it!" so I hope that's not how it translated to everyone else.
For what it's worth, I still believe that what you've run into is a bug based on my own guidelines of "it doesn't have to be a programatic bug and can wholly be a UX/expectation bug" - it doesn't seem that this dev has the same methodology which don't get me wrong, that's plenty fair enough - but they could've replied a bit more gracefully because otherwise it causes this exact problem, not only for Geany, but the entire open source world.
And if you really want even more barebones, you can just do git init --bare into a directory on your VPS, and then git clone user@your.ip.here:path/to/the/directory and use git as you would normally!
I can't speak for all developers, but personally I'd rather have a bug report that isn't actually a bug, but rather a user error over nothing at all. Because that means that my expectation of how others might use a feature could be incorrect which is a bug to me - just not a programmatic bug.
Some developers may of course not be as of appreciative of it, but I'd say so long as you have a cursory look at their issue tracker and no one else has reported it, then I'd say its worth it.
I love that the brain still relies on real-life data on the world it creates
I've heard that the brain isn't really capable of creating unique faces, so when you see people in a dream - even if they seem random to you, they're probably just someone you saw in passing (on the streets, online, etc) which is interesting!
Realistically there isn't a way to reliably test that theory, but it definitely makes sense to me at least.
It was gone from Plasma for a bit, however it'll be back in the next upcoming Plasma 6 release!