Hello. On 28 February 2013 12:43, Ricardo Mones <[email protected]> wrote: >> Sorry, I disagree. It's reproducible always.
> Not on other systems. That's what unreproducible means: other people > don't see the same. Nobody says you don't have the problem or cannot > reproduce it. I know what unreproducible means. Probably, you didn't try hard enough :) When I said it's reproducible here always, I meant if you try to simulate the situation closer to mine you *will* get this. >> Also, it's not minor bug, as it requires restart to fix it. >> It'd like to retag it. > You said simply re-editing the message suffices for it to work. That's > a very simple workaround, not a "restart". It only happens on specific > server situations (expired certificates) and very specific user behaviour > (the user ignores/forgets to answer the dialog). All of this, IMHO, qualifies > it more as a minor bug than a normal bug. Well, by bad: it's actually exactly otherwise: restart doesn't help, which indicates there's certainly a bug. Also, I guess it may be reproduced without expired certificates; I will try that later. Also, a checkbox “remember my choice” would be useful. >> > This looks like a corner case, as the usual is to answer the dialog >> > when shown. >> Well, it's not. I can't answer a dialog I don't see, and usually right >> after sending the message I switch away to a different desktop/screen >> tag, and the dialog apparently doesn't have 'urgent' flag set. > Dialog urgency hint is a different problem, unrelated to the sending > failure when the connection times out. Can you please file a different bug > for that? Well this is indeed a minor problem, I wouldn't mind that if that didn't bring this bug to the surface. -- WBR, Andrew -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
