https://bugs.kde.org/show_bug.cgi?id=425154
--- Comment #5 from Adam Fontenot <adam.m.fontenot+...@gmail.com> --- I think the big advantage of (2) is that even if a user doesn't understand where the problem came from, or even if KDE isn't at fault (suppose some misbehaving application adds itself to application/octet-stream), the user is likely to solve the problem on their own if we implement this. Perhaps instead of (1) there's some way of at least indicating to the user that the association is inherited. As it stands, all the associations look exactly the same and that's confusing, even to power users. Thanks for the multiple inheritance fix. I look forward to seeing that improvement with the next release. -- You are receiving this mail because: You are watching all bug changes.
