[Users] Cannot edit in the compose window

[H.Merijn Brand]

On Mon, 13 May 2019 21:28:35 -0700, sylpheed at 911networks.com wrote:

> 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

So you are running a self-compiled claws-mail, as the most recent from
openSUSE Leap 15.0 is 3.16.0-lp150.2.3.1

> > 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)  

That is the most recent leap 15.0 kernel

> 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

That is not an error, but a warning.

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

If you build from git, you are obviously familiar with reading sources.

$ ack 'Your Claws Mail configuration'

would have shown you that the message is issued from
src/prefs_migration.c line 51, where you can see that
CLAWS_CONFIG_VERSION was checked, which is currently
defined to 3 in src/prefs_common.h

$ cd ~/.claws-mail
$ grep config_version *rc | sort -u
accountrc:config_version=3
clawsrc:config_version=3
folderitemrc:config_version=-1
passwordstorerc:[config_version:3]

Does that show you anything weird?

Do *NOT* edit those files while Claws-Mail is running. Close CM and
then edit if you think you spotted the problem(s)

> 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:
> >>     
>  [...]  
> >> 
> >> 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.

-- 
H.Merijn Brand  http://tux.nl   Perl Monger  http://amsterdam.pm.org/
using perl5.00307 .. 5.29   porting perl5 on HP-UX, AIX, and openSUSE
http://mirrors.develooper.com/hpux/        http://www.test-smoke.org/
http://qa.perl.org   http://www.goldmark.org/jeff/stupid-disclaimers/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.claws-mail.org/pipermail/users/attachments/20190514/8c2ac14a/attachment.sig>