today's pet peeve: kicker bug reports that don't come with kicker configuration files.
when one of these rolls in i'll spend a few minutes trying to nail down the configuration based on descriptions (slow and very error prone) or screen shots (not fast and not quite as error prone) only to find that i can't reproduce the problem. so then i ask for a config file and when i use that exact config, i can then reproduce the problem.
if more reporters would attach their kicker config by default they wouldn't have to do as much describing and i'd be able to fix things faster and (more importantly to me ;) with less aggravation.
so if you are reporting a kicker bug, please think about attaching your kickerrc =)
Subscribe to:
Post Comments (Atom)
5 comments:
The situation is worse in amaroK. Character encodings of tags, different sound cards, accessing files in different ways, varying levels on Internet connectivity, various (sometimes conflicting) library versions etc. etc. Sometimes people would have to send you their computer for it to actually be reproduced. :P
I wonder if NX might be helpful in situations like this. Mind you, I suppose most bugs of this type aren't prolific enough/important enough to warrant such extreme measures, especially if the end result is a developer fixing a users own configuration rather than finding a real bug.
Informative KDE blog.
Might be easier if ~/.kde was sane and had an intuitive way of storing configuration files so people would know what to send you ;)
Post a Comment