Summary: | digiKam crash, when starting panorama stitching | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Axel Krebs <axel.krebs> |
Component: | Plugin-Generic-Panorama | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | benjamin.girault, caulier.gilles |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 7.6.0 |
Description
Axel Krebs
2013-06-05 04:39:01 UTC
Are you trying to annoy me? You never answered to my comment on the previous bug report, yet having obviously read it, and you open a new bug report on the exact same bug! The only thing you will achieve is slow me down. *** This bug has been marked as a duplicate of bug 319882 *** Benjamin, Why should I annoy you"? When I experience an issue (bug or wish), I start a bug report. Sometimes there are "old" ones, I have forgotten some time ago. The first three or five new capabilities seem to be based on my "old" wishes, I have longtime forgotten. So please believe me, I consider _every_ time before bug-reporting if I have time and information enough to make to do so… Time is always short... OK? Axel --- Am 05.06.2013 10:43, schrieb Benjamin Girault: > https://bugs.kde.org/show_bug.cgi?id=320747 > > Benjamin Girault <benjamin.girault@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|UNCONFIRMED |RESOLVED > CC| |benjamin.girault@gmail.com > Resolution|--- |DUPLICATE > > --- Comment #1 from Benjamin Girault <benjamin.girault@gmail.com> --- > Are you trying to annoy me? You never answered to my comment on the previous > bug report, yet having obviously read it, and you open a new bug report on the > exact same bug! > > The only thing you will achieve is slow me down. > > *** This bug has been marked as a duplicate of bug 319882 *** > Starting a bug report is fine with me. What is not is the combination of two other things: reporting again the same bug only a few weeks (which is not "old") after the first one, and not answering to a comment on the first bug report. If you do not answer to a comment from a developper in a bug report you made, how can you expect that developper to address your problem? You should also understand that reporting again is not constructive. As you said, time is short, and that also applies to me. If you would have posted a comment on the first bug report, I would have been glad to answer you, now I really do not want to address your problem, which, by the way, is mostly likely an issue with your system, and I may just ignore it. I was and am not aware of that other bug-#, I deal with those issues late evening sometimes. And I am sorry if causing double or useless work. The only cause not to answer a developers remark I can imagine of is, that I do not see the remark as a demand for contribution or question. Whenever I can, I try to contribute. Will try to read more diligently remarks. OK? Axel P.S.: sometimes, I do relly not understand, what people want to express. --- Am 05.06.2013 21:53, schrieb Benjamin Girault: > https://bugs.kde.org/show_bug.cgi?id=320747 > > --- Comment #3 from Benjamin Girault <benjamin.girault@gmail.com> --- > Starting a bug report is fine with me. What is not is the combination of two > other things: reporting again the same bug only a few weeks (which is not > "old") after the first one, and not answering to a comment on the first bug > report. > > If you do not answer to a comment from a developper in a bug report you made, > how can you expect that developper to address your problem? You should also > understand that reporting again is not constructive. > > As you said, time is short, and that also applies to me. If you would have > posted a comment on the first bug report, I would have been glad to answer you, > now I really do not want to address your problem, which, by the way, is mostly > likely an issue with your system, and I may just ignore it. > Fixed with https://bugs.kde.org/show_bug.cgi?id=319882 |