https://bugs.kde.org/show_bug.cgi?id=496597
--- Comment #5 from John Kizer <john.ki...@proton.me> --- (In reply to Alex from comment #4) > I'd rather wait until Debian (finally ...) gets 6.x into testing and then > report in back here, working indirect through distro maintainers proved to > slow things down unnecessary. > > Did you test it and have reason to believe it was fixed in more recent > versions? > It is not that important for me right now, but I think if the bug is still > present in current versions, it should be addressed. The intent of Debian's model is to have everything work through their maintainers, though - the perceived slowness there is necessary in their approach so that their team can arrange the whole operating system together as they see fit. So, if it doesn't go through their maintainers, then it may never get fixed in the Debian version you're using as they are generally not adopting new upstream versions of KDE software (they generally only "pull" individual patches as they see fit, rather than whole new versions of KDE software getting "pushed"). I appreciate your looking toward the future of the software - when using Debian, the best way to test how current versions are working and report upstream bugs would likely be to use a Flatpak version (which is in sync with the most current release) and test it there, rather than any Debian-packaged versions. If the same behavior exhibits itself in the Flatpak, then this would definitely make sense to re-open based on the current software version. -- You are receiving this mail because: You are watching all bug changes.
