https://bugs.kde.org/show_bug.cgi?id=479964
Reuben <k...@flavor8.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|RESOLVED |REOPENED
Resolution|DOWNSTREAM |---
--- Comment #8 from Reuben <k...@flavor8.com> ---
Sorry, but I question the "resolved downstream" status.
a) Have Kubuntu in fact resolved it? I don't see evidence of that, but great if
they have.
b) What percentage of KDE installs come through Kubuntu? ALL of these users are
probably still affected.
c) The new settings/verbiage/feature is KDE initiated. If your distributers
mess up the packaging, and you can't control the distributers, KDE can withdraw
the feature, or move it behind a setting in order to make it right for users.
I know you hate adding settings, but what's worse: a sizable percentage of your
users encountering a "KDE bug" or a setting for the probably sub 1% of users
who have fingerprint or smartcard auth hardware? The setting could even be
enabled by a wizard after the first login if you detect that this hardware
exists.
d) Finally, to expand on the above more generally, if your distributers are
leading to your software "having bugs" and can't be relied upon to package KDE
"properly" or "optimally", then set up a certification program. If Ubuntu loses
"KDE Certified" status on Kubuntu, they'll either stop shipping the variant or
throw some more resources at it to gain and keep certification. KDE is the
brand that matters to most of your users; they just want a reliable OS
underneath it, which is why Kubuntu has a sizable share, since traditionally
Ubuntu has been quite reliable.
--
You are receiving this mail because:
You are watching all bug changes.
