On 06/10/2012 08:29 PM, Justin Wood (Callek) wrote: > NoOp wrote: >> The bug >> <https://bugzilla.mozilla.org/show_bug.cgi?id=736811> >> has been updated today. >> >> I can *easily* replicate in Thunderbird 13 as well. 6 machines, 4 >> distros, 4 linux desktops (GNOME 2, GNOME3, KDE, ICWM, and 2 Mozilla >> products (SeaMonkey 10 & Thunderbird 13). >> >> Again: I consider this bug to be a blocker for the next release >> (SeaMonkey 11.x). > > Ok that bug is currently "unconfirmed" and listed as Firefox, so even > though we both know it is gecko, are you able to reproduce in Firefox > (If so that will make next steps easier).
Actually I don't know it is gecko. If I knew what it was, I'd concentrate on that. As far as I can tell it's a mailnews issue. And no, I've not been able to reproduce in Firefox. However, we *both* know that this is a regression... right? Are you implying that a regression like this won't be fixed unless it can also be reproduced in Firefox? Would you like a new SeaMonkey + Thunderbird mailnews component bug? > > After than can you help identify when this problem first occurred (it > has "regression-window-wanted" listed) > > Lets start with this list: > > Does it occur in: > * Firefox 13 [ftp://ftp.mozilla.org/pub/mozilla.org/firefox/releases/13.0/] > * Firefox 12 [ftp://ftp.mozilla.org/pub/mozilla.org/firefox/releases/12.0/] > * ... major versions Let's start with this instead: ftp://ftp.mozilla.org/pub/mozilla.org/seamonkey/releases/2.9.1/ ftp://ftp.mozilla.org/pub/mozilla.org/seamonkey/releases/2.10/ ftp://ftp.mozilla.org/pub/mozilla.org/thunderbird/releases/12.0.1/ ftp://ftp.mozilla.org/pub/mozilla.org/thunderbird/releases/13.0/ > > Once you have a case of "Broken in major version [x] but works in major > version [x-1]" then I can assist you in drilling down further. Right... Broken in major version SeaMonkey 10.x (and Thunderbird 12.x) but works in major version SeaMonkey 2.9.x (and Thunderbird 13.x). Does that not work for you? > > Feel free to come on IRC (irc://irc.mozilla.org/seamonkey) and ask for > my help in drilling down the range, to a 24 hour period, so we can get a > better idea of what is wrong, specifically! > I've already spent a fair amount of time attempting to troubleshoot and update the bug report. I am happy to try different *user* scenarios, if asked. However I'm not inclined to evolve to IRC. If you'd like me to try something else, then comment in the bug report. Bottom line is that the dev list were made aware of this issue at 2.10b2 - before final 2.10b3/2.10 release. You folks ask users to test the betas... we do that. We report the issue, we tell you how it seriously affects our use... and you retort that it must also occur in a different component (browser - instead of mailnews) in order to get attention? Wrong bug report/component? Say so & I'll be happy to file a new SeaMonkey + Thunderbird mailnews component bug, or feel free to reassign to the correct component. In the interim I've blocked all of my linux customers from "upgrading" to SeaMonkey 2.10 (and now Thunderbird 13 as well). _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
