package sylpheed-claws-gtk2 severity 349815 important tags 349815 moreinfo unreproducibe thanks
On Wed, 25 Jan 2006 14:10:56 +0100 Martin Samuelsson <[EMAIL PROTECTED]> wrote: > Package: sylpheed-claws-gtk2 > Version: 1.9.100-2 > Severity: critical Inflating bug severity don't gets it solved faster. (Yes, I saw you already downgraded it to grave, but that is still inflated). Please read what severity means to Debian BTS: http://www.debian.org/Bugs/Developer.en.html#severities It's not a measure of how important the bug is for you, it has a quite different and precise meaning. > When composing a message in s-c-gtk2, it adds the full contents of the > last message read when sending it. > > Steps to reproduce: > > 1. Start sylpheed-claws-gtk2 > 2. Read a message > 3. Compose a message Sorry, not reproducible here. Can you provide more details about your config: type of accounts you're reading and composing, library versions (you should have used bugreport for this), any other detail about the system that make it different (custom kernel, custom libraries you may have). > Now, the message at the receiving end contains both the message sent > and the last mail read by the sending user. Since that can very > likely be revealing information for unintended eyes, that is of > course NOT acceptable. > > I understand that there probably is something in my environment that > triggers this bug, otherwise it would have already been reported. > However, the fact that a critical bug is hard to trigger does not > lower its severity. Don't mess your feelings about the bug with the BTS severity levels. Try to isolate what makes your environment different instead. > I'm not spending more time trying to hunt this down, because I'm not > willing to mess in my production environment. This is not the first time you report a bug and say you're not willing to help solving it. I don't figure out why do you think that attitude will encourage me to spend my free time in solving it for you. > This is not the first time I report an issue like this one. Please > look at #333498, which was closed without finding the actual cause. Certanly the cause was not found but the reason for closing is clearly stated as well as the actions you could have taken. > I might set up a test environment, with toy servers - if asked to. This is only valid if bug gets exposed in test environment too. Can you create a clean chroot in your problematic box and try inside? > Until this bug is properly fixed, I suggest the removal of the > package from testing. We don't hide problems by removing packages. Furthermore I have the sensation that the rest of Sylpheed-Claws users in testing won't agree with your suggestion :-P -- Ricardo Mones ~ The world will end in 5 minutes. Please log out. Unknown -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
