[Users] Only issue prevent claws-mail to be accepted in corporate

[wwp]

Hello J.,


On Wed, 28 Mar 2012 14:35:16 +0530 "J. Bakshi" <joydeep at infoservices.in ( àŠœà§ŸàŠŠà§€àŠª àŠ¬àŠ•àŠžà§€ )> wrote:

> On Wed, 28 Mar 2012 10:50:58 +0200
> wwp <subscript at free.fr> wrote:
> 
> > Hello J.,
> > 
> > 
> > On Wed, 28 Mar 2012 11:19:57 +0530 "J. Bakshi" <joydeep at infoservices.in ( àŠœà§ŸàŠŠà§€àŠª àŠ¬àŠ•àŠžà§€ )> wrote:
> > 
> > > On Tue, 27 Mar 2012 11:57:28 -0400
> > > Steve Litt <slitt at troubleshooters.com> wrote:
> > > 
> > > > On Tue, 27 Mar 2012 12:14:23 +0530
> > > > "J. Bakshi" <joydeep at infoservices.in ( জয়দীপ বকসী )> wrote:
> > > > 
> > > > > Dear list,
> > > > > 
> > > > > I have introduces CM (3.8.0) in our organization. The initial
> > > > > response was very good, specially the quick search abilities of CM
> > > > > draws everyone's attentions.
> > > > > 
> > > > > But soon users ( who are thunderbird users) have faced the well known
> > > > > problem of CM, the frozen and grayed out issue. Even some users
> > > > > complaint the CM was frozen when they were in middle of the writing
> > > > > urgent emails.
> > > > > 
> > > > > The same thing happens also during mail search. Is there any way to
> > > > > fix this very issue ?
> > > > > 
> > > > > BTW: I have faced the same problem during my writing of this very
> > > > > small email, because CM was downloading emails !!!
> > > > 
> > > > Hi J. Bakshi,
> > > > 
> > > > The way I minimize this inconvenience is to set Claws to download only
> > > > when I tell it to. That way it doesn't happen in the middle of writing
> > > > an email, and, for instance, they could download email just before a
> > > > bathroom break or a walk to the coffee pot.
> > > > 
> > > > The tougher problem is when you're three levels down in the menu system
> > > > and all of a sudden it appears to freeze hard. Now you and I both know
> > > > that what has happened is some Claws dialog, not currently in the
> > > > foreground, needs attention, but to the new Claws user the symptom
> > > > description would be "hung" or "froze". I had a particularly difficult
> > > > one of these last night when I clicked OK and everything grayed out. It
> > > > turned out that a value on the dialog was illegal and I had to go
> > > > change it, but the only indication to the user was everything grayed
> > > > out. I think the best strategy against this type of thing is an
> > > > education campaign -- once you've seen it for what it is, it doesn't
> > > > panic you.
> > > > 
> > > > I'm not saying that "just work with it" is an ideal solution, but
> > > > threaded programming is difficult, and if threading this program would
> > > > take a complete rewrite, I'd worry that the next version would have
> > > > serious bugs.
> > > > 
> > > > SteveT
> > > 
> > [snip]
> > > And home I need to kill the CM when it doesn't come back from its frozen state :-(
> > [snip]
> > 
> > You need to kill it, really?? What is it doing exactly when you say
> > it's freezing? If you kill it while it's working, you can be sure next
> > time it will try to do again what it was doing when you killed it.
> > I mean, killing CM while it works is not a good idea, but if you're
> > facing a specific technical freeze, you should harvest some information
> > so that we can debug the situation.
> > 
> > 
> > Regards,
> 
> Sure, next time I will start with with -debug and collect the
> information during that state and mail here.

That may sound obvious, but CM is not supposed to freeze, unless you're
fetching a large stuff and additionally running on a slow machine (or
if CPU is used by other applications). And even, the UI would become
less responsive, not frozen up to a point that CM is a zombie.


Regards,

-- 
wwp
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.claws-mail.org/pipermail/users/attachments/20120328/c7c0c603/attachment.sig>