[Users] Cannot edit in the compose window

[sylpheed at 911networks.com]

On Mon, 13 May 2019 12:55:42 -0700
Lyle Bickley <lbickley at bickleywest.com> wrote:

>I've been and OpenSUSE user and Claws user for years and haven't
>experienced your issue. (I'm currently running the latest updates of
>OpenSUSE):
>
>Claws Mail
>version 3.17.3git172
>
>OpenSUSE Leap 15.0
>GTK+ 2.24.32 / GLib 2.54.3
>Locale: C (charset: US-ASCII)
>Operating System: Linux 4.12.14-lp150.12.58-default (x86_64)

I'm back almost.

After my backup, wipe everything and installed: leap 15.0 (current)
but CM is back to 3.16.0 and I get the following error message:

https://i.imgur.com/V7vHZQ9.png

CM seems to be working, but how do I fix this. It shows up 4 times
before I get in CM.


Thanks

Syv 

>
>Best,
>Lyle
>--
>
>On Mon, 13 May 2019 21:50:58 +0200
>Andrej Kacian <ticho at claws-mail.org> wrote:
>
>> On Mon, 13 May 2019 12:24:38 -0700
>> sylpheed at 911networks.com wrote:
>>   
>> > CM 3.17.3 & I'm on Opensuse tumbleweed for almost 2 weeks. 
>> > 
>> > Suddenly this morning I cannot use the compose window, everything
>> > is frozen!
>> > 
>> > I can't type, nothing but when I clicked on edit external, 
>> > the changes were in the temp file. 
>> > 
>> > I'm typing this message in vim. Then almost all my changes show
>> > in CM. The blank lines do not show up:
>> > 
>> > https://i.imgur.com/6X5voz2.png
>> > 
>> > Obviously it's a suse problem, since CM hasn't changed in the
>> > last month
>> > 
>> > Any suggestion on what to track?    
>> 
>> I would start by remembering when was the last time the compose
>> window worked, and looking at update log (Suse's zypper should
>> have a rather neat log of what was updated and when, IIRC).
>> Probably some package got updated to a version that doesn't play
>> well with the program.
>> 
>> Does this problem persist after you exit Claws Mail and start it
>> again? If so, is there any text output when you run it in a
>> terminal and try to use the compose window?
>> 
>> I doubt we'll see anything interesting in the --debug output, this
>> seems to be a problem somewhere on lower level, between the X
>> server and GTK.
>> 
>> Regards,  
>
>
>
>-- 
>73   NM6Y
>Bickley Consulting West Inc.
>https://bickleywest.com
>
>"Black holes are where God is dividing by zero"
>_______________________________________________
>Users mailing list
>Users at lists.claws-mail.org
>https://lists.claws-mail.org/cgi-bin/mailman/listinfo/users


-- 
sknahT

vyS