https://bugs.kde.org/show_bug.cgi?id=450175
--- Comment #5 from Nate Graham <n...@kde.org> --- The GTK bug tracker is here https://gitlab.gnome.org/GNOME/gtk/-/issues/ Side note: > I noticed it months ago but didn't care to report it. Since this was so > obvious, I assumed that lots > of people will bug you about it. It's quite common for people to think that the bugs affecting them are so obvious that *someone* else must have noticed and started to work on a fix, but this is often not the case because the triggers for a bug--even a severe one--often depend quite heavily on one's setup. What settings you use, what environment variables are set (as in this case), which rendering backend is in use, what GPU hardware you have, what version of the graphics drivers and kernel you have, and so on. The list can seem endless. This is why it's a good idea to report every bug you encounter. Quite often, the developers have never seen it before and may be completely unaware that any users are experiencing it. Second side note: I searched through the entire KDE codebase and did not find a single piece of code that looks at the value of GTK_USE_PORTAL, so I feel even more confident in saying that this is a GTK or GNOME bug of some sort. KDE's codebase is quite literally totally ignorant of whether that option is set or not; we don't do anything different at all. So the difference must be coming from the GTK or GNOME side. Now it's possible that setting that variable triggers behavior in their code that then in turn triggers some other behavior in our code that causes the bug, but unfortunately there's no way for us to know this without either the GTK or GNOME developers telling us this, or one of us being able to reproduce the issue, which so far, we can't. -- You are receiving this mail because: You are watching all bug changes.
