https://bugs.kde.org/show_bug.cgi?id=399981
--- Comment #73 from Wyatt Childers <dark...@nearce.com> --- (In reply to lega99 from comment #72) > (In reply to Nate Graham from comment #70) > > The stakes are a good bit higher than just you not being able to use > > Discover for 12 more days: the next version of Debian Stable is going to > > ship with Plasma 5.14.5, which means Discover 5.14.5, which means that all > > the Debian users are going to be exposed to this issue if we can't provide a > > hotfix. That's why I'm asking for testing--so we can know if the proposed > > fix works. > I am a retired but I remember when Kali Distribution users were begging to > be allowed to work with Dolphin as root, they were rejected, as we all know > Kali is based on Debian. Then Kali users got advice from Plasma developer to > do it themselves. What? > The stakes are a good bit higher than just you not being able to use > Discover for 12 more days: the next version of Debian Stable is going to > ship with Plasma 5.14.5, which means Discover 5.14.5, which means that all > the Debian users are going to be exposed to this issue if we can't provide a > hotfix. That's why I'm asking for testing--so we can know if the proposed > fix works. Unfortunately I can't, no longer have the issue as I got the updated packages from neon developer edition. > The problem persists on my system but unfortunately I don't know how to > compile source code reverting a commit. :( Do you know how to compile from source? If it's just the reverting a commit part, that's relatively simple. You just go to the directory where you've got a copy of the source code and run `git revert <commit>` or in this case `git revert 2bd91b93357318c4f7dd96b2f6e7a07dd74494c8`. -- You are receiving this mail because: You are watching all bug changes.
