First moments I was like: wait, it’s Jeffrey. But then!.. yeah, he looks so much Joffrey, lol!

I should have mentioned it more clearly that this could be a combination of bugs, not necessarily a Krita bug. Because this issue is not only with Krita, but many (or even all) XWayland apps. All Wine apps shared this too. So, the primary issue is that it needs XWayland instead of being Wayland-native.

I use Sway on Arch Linux, and Gnome on Fedora. I haven’t been doing anything on Fedora for years, as it’s a shared family computer and it has just one display. So, I expect it would be good there. To my memory, it was. I was trying various graphical things, even Photoshop and Illustrator with Wine, and they were mostly working too.

I think I could issue a DE for drawing sessions, when needed, if that solves the issue. So, thanks for mentioning that it’s issues-free on KDE. It’s more obvious to me now that actually Krita is a KDE thing, after all.

But, honestly, it feels the same as doing my hacky scripts to mitigate the bug. I’d love it to just work, that’s why I mention I hope it would be Wayland native one day.

I was worried there might be some weird bugs, as all my other clients are on v2. But so far, I haven’t noticed anything wrong.

So it’s purely some kind of a mix of cargo cult and just the will to have the newer updated software everywhere. That makes little practical sense, but I’m still with this illusion of newer = better, on a subconscious level, I think. Plus, I wasn’t sure everything is correct as it is not updated for a long time, I thought perhaps some Debian repos ingrained into my Fedora!

Wine was never developed by Epic, as far as I know. Wikipedia showed nothing about Epic, not a word.

Yeah, like, Blender devs being: ‘we implemented HDR on Linux. Windows? You can implement it yourself, if you want.’

Source: The real change log of some year or so ago, but I cannot find the link quickly. Here it states the Windows is supported too now.

What a nice way to say sudo rm -fr /

I can say about the stability, as I use Syncthing extensively and the version 2 since day one. It had the database issue, perhaps upon migration, which lead the program to crash on my Raspberry Pi 2B with 1 GB RAM. At some point I noticed the issue, removed the database and let it rebuilt it cleanly, which did the job and fixed the issue. Plus, I made a swap partition just in case. Haven’t seen any other issues after that. That was DietPi distro, based on Debian.

I had no issues like that on Arch, but my Arch desktops, laptops, and servers are more powerful, perhaps they handled the migration better. I expect that this was some bug that was fixed later. Fedora still syncs, but I wonder when would they update the repo, or if that’s me that wasn’t attentive somewhere and I need to change the repo. Maybe they follow the topic closer.

The window is unresponsive to clicks, so the mouse never works. You can drag it to the main laptop’s screen, but my laptop is small and the external screen is big, so it’s not useful to have such an app opened on a tiny screen. There are workarounds, but having a native Wayland app is just much more useful than hacking around. Last time I checked (was quite a long time ago, up to a year ago) the development wasn’t too focused on Wayland. I hope they’d do at some point, as overall Krita is good.

Really great advice, was thinking of that myself recently. I’m considering making some GUI apps to address my terminal journeys. While I enjoy terminal, not everyone should.

Oh Windows did mess with me a gazillion times in 2000s, when I was a poor kid with just one HDD, and tried to dual boot.

Uncle Ben taught me the hard way, through his nephew, Peter. I was still a kid, but I knew: big power, big responsibility.

I don’t understand why Syncthing is still not version 2 on Fedora. Did I do something wrong? Did the repo changed? Apart from that, I agree, I really like Fedora on systems where I don’t want to mess with the system. But I do want to mess with my systems, that’s the point of Linux for me now :)

I had this too, but I use ctrl + r all the time (with fzf), and really have no need for that many aliases.

My issue was that when run through XWayland, Krita would work only on the primary display (no concept of that in Wayland) with 0,0 coordinates. So, if I’m on a laptop, it would work only on the primary (laptop) screen, but not the external one. I have a script that reorganises my workspaces and makes the external display the primary one, then runs Krita. But it would never work on any other display, if I wanted to use that too, for some multi monitor setup.

I may want to try that again, perhaps that was some bug that was fixed. But I’m surely not going to use X instead of Wayland for Krita.

Last time I used it, it wasn’t ready for a Retina HiDPI screen (MacBooks since 2013), but I might want to double-check that. I remember the icons were pixelated. And I’m very sure it did not work on Wayland, which generates a bunch of weird bugs / issues for a multi-monitor setup. I never work with just one display. So, I can use it when I have to, but most times I prefer Gimp. Haven’t been opening Krita for over a year or so. Text editing is a gimp too. Apart from that, the interface wasn’t that bad as it is with Gimp, that’s for sure. Overall, I believe that’s actually a pretty nice program, Krita.

A friend advised me to sell mine when the GPU prices were crazy, I could get like $200 for it, or a bit more (years prior to that, I bought it for $150 from another friend, used, he tried to mine some Etherium with it). I was lazy, and perhaps the friend was right, I could buy something better for the price now. But I’m really satisfied with the card and feel no need to upgrade any time soon. Runs everything I want.

I do sudo pacman -Syu as a ritual each time when I start my computer or laptop. Like, the very first thing after the system is booted. So far so good, been doing that for 7 years.

Hey, I tried it. Is it only themes in the settings, or should I do something else. The interface became a bit more aesthetically appealing, so a nice work on that regard. But my pain point is the panels and their very weird behaviour (like you do resize and they are too much all the time). I expect you cannot address that with a theme.

I’m going to keep it, so I may comment more some days / weeks later, if you will.

That looks much better, I’m going to try it, thanks for sharing!

True. Yet, I hate it as a server too. I use it only on SBCs, but not pure Debian, but Armbian. Otherwise, on an X64 machine, I’d go with Arch.