Bug 20970

(In reply to Alberto Girlando from comment #0)

> 
> Steps to Reproduce:
> 1. Install 3.15 over the Mageia 5.1 version

Are you saying that it wasn't autmatically upgraded when you upgraded to Mageia6RC?

> 2. Launch claws-mail
> 3.Segmentation fault.


Assigning to the registered maintainer for claws-mail

CC: (none) => marja11
Keywords: (none) => NEEDINFO
Assignee: bugsquad => julien.moragny

No. It was upgraded during the process, but then gave segmentation fault when I tried to open. I then disinstalled it, and installed again with all the plugins (only a few were installed during the upgrade to Mageia6 RC, and I did not remember which one I had installed before), but I got segmentation fault again.

Same problem, only after upgrade from 5.1 to 6.0.

$ rpm -q claws-mail
claws-mail-3.15.0-4.mga6
$ claws-mail --version
Claws Mail version 3.15.0

Steps to reproduce:

1) Upgrade from Mageia 5.1 with existing user ~/.claws-mail directory, presumably with at least one account being an IMAP connection.

2) Launch claws-mail

3) Sementation fault (core dumped)

$ claws-mail
                                                                                                     
(claws-mail:5709): Claws-Mail-CRITICAL **: imap_item_get_path: assertion 'folder_path != NULL' failed
folder.c:3967 Condition path != NULL failed                                                          
traceback:                                                                                           
0:      claws-mail() [0x48c7f0]                                                                      
1:      claws-mail() [0x48f5bc]                                                                      
2:      claws-mail(folder_item_get_msg_list+0x50) [0x48fdb0]                                         
3:      claws-mail() [0x498700]                                                                      
4:      claws-mail() [0x498d47]                                                                      
5:      claws-mail(gtk_sctree_insert_gnode+0xf7) [0x627917]
6:      claws-mail(gtk_sctree_insert_gnode+0x199) [0x6279b9]
7:      claws-mail(folderview_set+0x219) [0x49ada9]
8:      claws-mail() [0x49aff8]
9:      claws-mail() [0x5cf1c0]
10:     /lib64/libglib-2.0.so.0(g_hook_list_marshal+0x54) [0x7f3ebeec2874]
11:     claws-mail(hooks_invoke+0x44) [0x5cf804]
12:     claws-mail(folder_add+0x9e) [0x48a04e]
13:     claws-mail(folder_read_list+0x68) [0x48dac8]
14:     claws-mail(main+0xbe1) [0x448fd1]
15:     /lib64/libc.so.6(__libc_start_main+0xf0) [0x7f3ebdc68600]
16:     claws-mail(_start+0x29) [0x44ad59]


(claws-mail:5709): Claws-Mail-CRITICAL **: imap_item_get_path: assertion 'folder_path != NULL' failed
folder.c:3991 Condition path != NULL failed
traceback:
0:      claws-mail() [0x48ca70]
1:      claws-mail() [0x48f5cc]
2:      claws-mail(folder_item_get_msg_list+0x50) [0x48fdb0]
3:      claws-mail() [0x498700]
4:      claws-mail() [0x498d47]
5:      claws-mail(gtk_sctree_insert_gnode+0xf7) [0x627917]
6:      claws-mail(gtk_sctree_insert_gnode+0x199) [0x6279b9]
7:      claws-mail(folderview_set+0x219) [0x49ada9]
8:      claws-mail() [0x49aff8]
9:      claws-mail() [0x5cf1c0]
10:     /lib64/libglib-2.0.so.0(g_hook_list_marshal+0x54) [0x7f3ebeec2874]
11:     claws-mail(hooks_invoke+0x44) [0x5cf804]
12:     claws-mail(folder_add+0x9e) [0x48a04e]
13:     claws-mail(folder_read_list+0x68) [0x48dac8]
14:     claws-mail(main+0xbe1) [0x448fd1]
15:     /lib64/libc.so.6(__libc_start_main+0xf0) [0x7f3ebdc68600]
16:     claws-mail(_start+0x29) [0x44ad59]

msgcache.c:586 Condition cache_file != NULL failed
traceback:
0:      claws-mail(msgcache_read_cache+0xdde) [0x4e30ae]
1:      claws-mail() [0x48f5e8]
2:      claws-mail(folder_item_get_msg_list+0x50) [0x48fdb0]
3:      claws-mail() [0x498700]
4:      claws-mail() [0x498d47]
5:      claws-mail(gtk_sctree_insert_gnode+0xf7) [0x627917]
6:      claws-mail(gtk_sctree_insert_gnode+0x199) [0x6279b9]
7:      claws-mail(folderview_set+0x219) [0x49ada9]
8:      claws-mail() [0x49aff8]
9:      claws-mail() [0x5cf1c0]
10:     /lib64/libglib-2.0.so.0(g_hook_list_marshal+0x54) [0x7f3ebeec2874]
11:     claws-mail(hooks_invoke+0x44) [0x5cf804]
12:     claws-mail(folder_add+0x9e) [0x48a04e]
13:     claws-mail(folder_read_list+0x68) [0x48dac8]
14:     claws-mail(main+0xbe1) [0x448fd1]
15:     /lib64/libc.so.6(__libc_start_main+0xf0) [0x7f3ebdc68600]
16:     claws-mail(_start+0x29) [0x44ad59]


(claws-mail:5709): Claws-Mail-CRITICAL **: imap_item_get_path: assertion 'folder_path != NULL' failed
Segmentation fault (core dumped)

CC: (none) => kbulgrien
Version: Cauldron => 6

ALL the claws-mail-plugins need to be updated to Mga6 Before you try to launch Claws-mail, if not this can|will cause claws to crash.
(short reason, you are trying to load a plugin that was built for a different version of claws)

If not already done add a Mga6 mirror to media sources and use 
urpmi --auto-select  to upgrade those plugins that were not included in the Mga6 iso.
Then launch claws.

CC: (none) => cae

In my case, it was a FRESH INSTALL with only /home and /usr/local preserved from the Mageia 5.1 installation.

Removing the .claws-mail folder avoids the segmentation fault, but also it is avoided by removing the ~/.claws-mail/accountrc file - though of course this is not a solution as the accounts are intrinsic to using the mail store.

$ mv ~/.claws-mail/accountrc ~/.claws-mail/accountrc.orig
$ claws-mail

(claws-mail:985): Claws-Mail-WARNING **: account_id: 2 not found

(claws-mail:985): Claws-Mail-WARNING **: account_id: 4 not found

(claws-mail:985): Claws-Mail-WARNING **: account_id: 5 not found

(claws-mail:985): Claws-Mail-WARNING **: account_id: 7 not found

The Mageia 5.1 installation had the following packages:

$ grep claws rpms.txt
claws-mail-3.11.1-3.1.mga5
claws-mail-tnef_parse-plugin-3.11.1-3.1.mga5
claws-mail-tools-3.11.1-3.1.mga5
clawsker-0.7.12-3.mga5

The Mageia 6 installation has:

$ rpm -qa | grep claws

clawsker-1.1.0-1.mga6
claws-mail-3.15.0-4.mga6
claws-mail-tools-3.15.0-4.mga6

Could you attach the output of

diff -u ~/.claws-mail/accountrc ~/.claws-mail/accountrc.orig

Well, it's not quite that simple.  I renamed the accountrc file to "delete" it.  I haven't set up all the accounts yet, so there is nothing useful to diff without creating manually creating a new file by attempting to set up accounts in the same order they were in the old file.

That said, I did set up a POP account and it worked, so I then I replaced it with the POP account from the accountrc.orig file and it worked... I guess that means I can edit in the accounts one by one to see which ones crash the client, and then try to re-establish the account through the UI... Nope... Copying in the old accountrc doesn't crash the client anymore, but the accounts aren't visible so removing accountrc caused something else to change.

folderlist.xml has differences and re-adding missing pieces of it causes the crash to recur, but at this time I'm not yet sure what to make of things.  All the folders that cause the crash are for imap accounts.

I am able to get an IMAP account functional by setting the account back up manually.  I guess perhaps with this, some key difference could be searched for.

I confirm Kevin findings. In new installation from Mageia 5.1 to Mageia 6 (I have two computers) claws-mail crashes unless you at least remove accountrc from .claws-mail. I tried to use accountrc from previous installation, so the system did not crash, but when I tried to edit account, it made strange things, then crashed. Since I need a working mail client, I copied old .claws-mail with a different name, started new accounts, copied the addressbook and calendar from old .claws-mail, and everything was OK (for IMAP accounts). I suspect that the problem came along since in Mageia 5.1 claws-mail was at version 3.11 or so, then in Mageia 6 it stepped to 3.15. Perhaps the bug should be reported directly to claws (or search there).
Sorry for not being able to help more.

Hello,

just came back from vacation so I can now look at this.

I managed to pinpoint that a previous version (3.14.0 at least) of claws change some options in files accountrc and clawsrc and 3.15.0 refuse to start if this new value/options are not present.

On my profile, I seems to needs only 2 modifications 

For accountrc, in each imap account "protocol=3" needs to become "protocol=1"

For clawsrc, you need to add "config_version=2" just below [Common] at the start of the file.

Can you confirm my findings ?

thanks

Status: NEW => ASSIGNED

Here is the upstream bug:
http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=3855

I can confirm that changing "protocol=3" to "protocol=1" in accountrc and adding "config_version=2" just below [Common] in clawsrc does, in fact, correct the startup problem.

I backed up my original .claws-mail directory at the time I experienced the issue, so still had the malfunctioning workspace to test with.

Hello,

I just pushed a fix to cauldron and updates_testing for 6.
Here is a tentative advisory :

====================================

Updated claws-mail package fix update problem with existing profile

After the update of claws-mail 3.11 (MGA5) to 3.15.0 (MGA6), claws-mail crash with a segmentation fault when launched with an existing profile (bug MGA#20970).

This update fix the crash.

References :
https://bugs.mageia.org/show_bug.cgi?id=20970
http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=3855

==================================

Updated packages in core/updates_testing:
==================================
claws-mail-3.15.0-4.1.mga6
claws-mail-acpi-plugin-3.15.0-4.1.mga6
claws-mail-address_keeper-plugin-3.15.0-4.1.mga6
claws-mail-archive-plugin-3.15.0-4.1.mga6
claws-mail-attachwarner-plugin-3.15.0-4.1.mga6
claws-mail-att_remover-plugin-3.15.0-4.1.mga6
claws-mail-bogofilter-plugin-3.15.0-4.1.mga6
claws-mail-bsfilter-plugin-3.15.0-4.1.mga6
claws-mail-clamd-plugin-3.15.0-4.1.mga6
claws-mail-debuginfo-3.15.0-4.1.mga6
claws-mail-devel-3.15.0-4.1.mga6
claws-mail-fancy-plugin-3.15.0-4.1.mga6
claws-mail-fetchinfo-plugin-3.15.0-4.1.mga6
claws-mail-gdata-plugin-3.15.0-4.1.mga6
claws-mail-libravatar-plugin-3.15.0-4.1.mga6
claws-mail-mailmbox-plugin-3.15.0-4.1.mga6
claws-mail-managesieve-plugin-3.15.0-4.1.mga6
claws-mail-newmail-plugin-3.15.0-4.1.mga6
claws-mail-notification-plugin-3.15.0-4.1.mga6
claws-mail-pdf_viewer-plugin-3.15.0-4.1.mga6
claws-mail-perl-plugin-3.15.0-4.1.mga6
claws-mail-pgpcore-plugin-3.15.0-4.1.mga6
claws-mail-pgpinline-plugin-3.15.0-4.1.mga6
claws-mail-pgpmime-plugin-3.15.0-4.1.mga6
claws-mail-plugins-3.15.0-4.1.mga6
claws-mail-python-plugin-3.15.0-4.1.mga6
claws-mail-rssyl-plugin-3.15.0-4.1.mga6
claws-mail-smime-plugin-3.15.0-4.1.mga6
claws-mail-spamassassin-plugin-3.15.0-4.1.mga6
claws-mail-spam_report-plugin-3.15.0-4.1.mga6
claws-mail-tools-3.15.0-4.1.mga6
claws-mail-vcalendar-plugin-3.15.0-4.1.mga6
claws-mail-vcalendar-plugin-devel-3.15.0-4.1.mga6

Source RPMs: 
claws-mail-3.15.0-4.1.mga6.src.rpm

Created attachment 9600 [details]
dummy profile

A dummy profile to test the fix

Hello QA,

I just pushed a fix for a crash in claws-mail after upgrade from MGA5 to MGA6.

here (mga6 64 bits) the fix works.

I uploaded a dummy profile produced with mga5 which exhibit the crash.

How to test :
- backup your existing profile folder ($HOME/.claws-mail) and replace it with the folder inside the tarball
- launch claws-mail, on command line, it should crash with a trace similar to comment 3
- update with claws-mail from updates_testing
- launch claws-mail, it shouldn't crash anymore.

Thanks
regards

Julien

Keywords: NEEDINFO => (none)
Assignee: julien.moragny => qa-bugs

Tested on a new installation of Mageia 6 on my last (32 bit) computer. I installed Mageia 6 (fresh instalment by saving the /home directory, the computer has too little disk space to make the upgrade). Claws-mail crashed, as expected. Then I tested Julien fix: I enabled update-testing, installed the new version, and run again... Everything OK, no problems (I had four e-mail boxes, all with IMAP).

So perhaps the bug is fixed. Thank Julien.

Testing Mageia 6 x64
Following instructions from Comment 16, using the test .claws/ (dummy profile) given in the attachment (9600). Thank you Julien for these, a great help.

Claws-mail was already installed (but never yet used) as part of my M6 Classic installation. I added the very necessary claws-mail-fancy-plugin (which pulled in about 128 packages!).
At this point, without having ever started claws-mail, there was no ~/.claws-mail/ directory. I created this by downloading the attached test so-called profile and unpacking it as ~/.claws/mail/ .

BEFORE update:
 claws-mail-3.15.0-4.mga6
 claws-mail-bogofilter-plugin-3.15.0-4.mga6
 claws-mail-fancy-plugin-3.15.0-4.mga6
 claws-mail-pgpcore-plugin-3.15.0-4.mga6
 claws-mail-pgpmime-plugin-3.15.0-4.mga6

 $ claws-mail
Gtk-Message: Failed to load module "canberra-gtk-module"
(claws-mail:25988): Claws-Mail-WARNING **: couldn't read password store from file: Failed to open file “/home/lewis/.claws-mail/passwordstorerc”: No such file or directory

(claws-mail:25988): Claws-Mail-CRITICAL **: imap_item_get_path: assertion 'folder_path != NULL' failed
folder.c:3967 Condition path != NULL failed
traceback:
...
(claws-mail:25988): Claws-Mail-CRITICAL **: imap_item_get_path: assertion 'folder_path != NULL' failed
folder.c:3991 Condition path != NULL failed
traceback:
...
msgcache.c:586 Condition cache_file != NULL failed
traceback:
...
(claws-mail:25988): Claws-Mail-CRITICAL **: imap_item_get_path: assertion 'folder_path != NULL' failed
Segmentation fault (core dumped)

As predicted as per Comment 3.
-----------------------------
AFTER the update:
 claws-mail-3.15.0-4.1.mga6
 claws-mail-bogofilter-plugin-3.15.0-4.1.mga6
 claws-mail-fancy-plugin-3.15.0-4.mga6        ***
 claws-mail-pgpcore-plugin-3.15.0-4.1.mga6
 claws-mail-pgpmime-plugin-3.15.0-4.1.mga6
Note that the 'fancy' plugin, although listed in Comment 14, was *not* shown in Updates Testing, so not updated. Reason for 'feedback'.
                                    --------------------
 $ claws-mail
Gtk-Message: Failed to load module "canberra-gtk-module"

(claws-mail:30044): Claws-Mail-WARNING **: couldn't read password store from file: Failed to open file “/home/lewis/.claws-mail/passwordstorerc”: No such file or directory
 $
and it popped up the correct GUI with "dummy claws" title.
So the update basically works. OK except for doubt about the fancy plugin.
--------------
I then removed the test ~/.claws/ tree, and linked instead my real Mageia 5 .claws/ directory.
$ ls -al
drwx------ 10 lewis lewis  4096 Aws  22 21:48 .claws-mail/
$ rm -rf .claws-mail/
$ ln -s /mnt/common/conf/.claws-mail/ .claws-mail
$ ls -al
lrwxrwxrwx  1 lewis lewis    29 Aws  22 21:51 .claws-mail -> /mnt/common/conf/.claws-mail/
Daring: launched Claws-mail from the menu, and it seems to basically work. I am glad not to have done this before the update.
BUT the fancy plugin is not showing at all, nor of course happening. So the feedback query about it matters.
--------------------------------
Also, a new fault I noticed during M6 testing: when going through the Inbox, when you delete a message, it skips back to the previous already-read one rather than advancing to the next unread one. This is very annoying. Should I raise a bug for it?

Whiteboard: (none) => feedback
CC: (none) => lewyssmith

M6/64
'Fancy' plugin problem solved, so feedback removed.
Having poked around at what is in Updates Testing for claws-mail-3.15.0-4.1.mga6 & all its plugins against what I had installed, I discovered that I had the *32-bit* version  of the 'fancy' plugin.
I removed that, and installed from issued repos:
 claws-mail-fancy-plugin-3.15.0-4.mga6.x86_64.rpm
which was immediately effective in Claws-Mail.

Updated that to :  claws-mail-fancy-plugin-3.15.0-4.1.mga6
which corrects my AFTER pkg list in Comment 18. And Claws-Mail still works fine.
So OK at last; and validating as this is M6 only. Advisory from Comment 14.

I will raise a new bug for the unhelpful 'delete message' annoyance.

Whiteboard: feedback => MGA6-64-OK advisory
Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs

An update for this issue has been pushed to the Mageia Updates repository.

http://advisories.mageia.org/MGAA-2017-0068.html

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED