Bug 101395 - If bug 75202 is fixed then I am a walrus and there is something seriously wrong with how you process bugs.
Summary: If bug 75202 is fixed then I am a walrus and there is something seriously wro...
Status: RESOLVED NOT A BUG
Alias: None
Product: bugs.kde.org
Classification: Websites
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: kde-www mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-12 23:11 UTC by Robert Persson
Modified: 2005-03-12 23:35 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Persson 2005-03-12 23:11:18 UTC
Version:            (using KDE KDE 3.3.2)
Installed from:    Gentoo Packages
OS:                Linux

Bug 75202 is marked as resolved when it quite plainly is not. Resolved would mean that no user would find that instances of konqueror loaded by default that they couldn't even see were preventing them from using their cd or dvd drive properly.

Resolved does not mean that, by going to some obscure web page they don't even know about, novice users will find a workaround for a problem they might not even understand well enough to express as a google query.

The KDE bug crunchers must understand that workarounds are most definitely not solutions.  No mattter how clever the hacks, KDE cannot be a useful environment for non-nerds if it behaves in counter-intuitive and unpredictable ways.

So the bug is: The KDE bug handling system is out of touch with reality.
Comment 1 Maksim Orlovich 2005-03-12 23:17:44 UTC
Sorry, we do not magically make versions released before the fix was done have the fix
Comment 2 Dirk Mueller 2005-03-12 23:20:05 UTC
just have a look at http://bugs.kde.org/show_bug.cgi?id=78322
Comment 3 Robert Persson 2005-03-12 23:31:58 UTC
The bug was marked as resolved over a year ago.  If it was then the fix should have appeared in KDE 3.3.2, but it hasn't. Therefore it is not resolved.  Therefore there is something amiss with the bug handling system, which is precisely the problem I have reported here.
Comment 4 Thiago Macieira 2005-03-12 23:35:53 UTC
Bug 78332 isn't closed.