https://bugs.kde.org/show_bug.cgi?id=234080
--- Comment #4 from kavol <kavol seznam cz> 2010-04-13 16:44:36 --- (In reply to comment #3) > There is nothing to explain, this is a bug tracker not a user forum! then why do you keep prolonging the offtopic discussion? > > sometimes, people just need kicking in the ass ... > Well, then you are at the wrong place, we like neither ass kicking nor > impolite > people... > Do not expect any help in this case now, that is funny :-) you (the KDE developer community as a whole) started to misbehave, treat users bad, causing harm to millions of people(*), acting like gods, laughing into users faces, accusing the distributors and hardware/drivers vendors of your own faults etc. now when an user strikes back (not much to do, I can't break your machine just like you've broken mine, so just verbally), you play the most aggrieved person in the world that's what I call hypocrisy :-) (*) for example I've just read recently that Fedora is estimated to 24M installations, and KDE is not just 1% minority ... > > > Which kind of resource? 'Traditional Addressbook' or 'vCard file' > > > resource? > > > > I don't remember ... the one that allowed me to use single .vcf > Then you should maybe remove the resource you've added and add a 'vCard file' > resource... from you previous description it sounds like you've added the > former which is known to be buggy. ok, I've tried so, adding a vCard file resource seems to work => keeping the bug closed if this is the only supported way to use .vcf ... but creating bug #234259 to get rid of the unsupported way > > > The former shouldn't be used anymore. > > > > why is it present then? > For most users/distribution/kde version combination this resource works > without > problems. this sounds like "when there is full moon and the night is not cloudy and you stand on your left leg ..." note that I've tried bug #234259 on Fedora 13 with KDE 4.4.2 ... > Well, if I (the developer) can't reproduce it, I have no way to fix it... simply not true ... > Commits to KAddressBook are irrelevant here, the behavior is caused by the > resource, which is a completely different code base. if that was clear then the bug should have been reassigned in the first place; users are not expected to understand code hierarchy ... > > > No reason to cry, Akonadi contains a cache, so you see the cached data. > > > > no, I just see shit! > So it is brown and smells bad? well, I know that KDE developers expect everyone to have the latest&greatest hardware, but I still don't own a scent delivery system, so I can't tell, sorry > > the purpose of cache is to speed up access, not to keep completely different > > set of data > It doesn't keep completely different set of data, the data of the cache just > have not be written back to the original source (aka vCard file). ... which in other words means that the original source has completely different set of data; wasn't that an oxymoron? anyways, thankyou for leading me to a workaround for this bug I won't reopen it again, as stated above, I won't force fixing a bug in a component which is no longer supported - even if proper action would be to reopen and then let the owner to close this as WONTFIX (you choose wrong resolution intentionally to have nicer statistics? - seems like a trend these days, nobody dares to use WONTFIX, I'm getting INVALID/NOTABUG on obvious problems a lot recently ...) -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You are the assignee for the bug. _______________________________________________ Kdepim-bugs mailing list [email protected] https://mail.kde.org/mailman/listinfo/kdepim-bugs
