evolution crashes when create a new imap-folder

Bug #1315618 reported by Jörg Frings-Fürst
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

On create a new imap-folder evolution crashes directly after pressing button.

Imap-Server dovecot 1:2.0.19-0ubuntu2 at ubuntu 12.04

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: evolution 3.10.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
Uname: Linux 3.11.0-15-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Sat May 3 09:44:25 2014
InstallationDate: Installed on 2013-12-12 (141 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
ProcEnviron:
 LANGUAGE=de_DE
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: evolution
UpgradeStatus: Upgraded to trusty on 2014-04-18 (14 days ago)

Revision history for this message
Jörg Frings-Fürst (jff-de) wrote :
description: updated
Revision history for this message
Jörg Frings-Fürst (jff-de) wrote :

If I start evolution in a terminal I get:

####
(evolution:24561): GLib-CRITICAL **: Source ID 8176 was not found when attempting to remove it
Speicherzugriffsfehler (Speicherabzug geschrieben)
####

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in evolution (Ubuntu):
status: New → Confirmed
Revision history for this message
Dennis L. (dennis2society) wrote :

This is not limited to creating IMAP folders but happens for me when creating a local folder after pressing the "OK" button in the "Select folder name" dialog, too.
The console output says:
#######
(evolution:5121): GLib-CRITICAL **: Source ID 519 was not found when attempting to remove it
Segmentation fault (core dumped)
#######
After restarting evolution the recently created folder exists as expected.

Revision history for this message
Martijn Bastiaan (hmb1) wrote :

I've ran gdb to find out what causes the segmentation fault. It says:

Program received signal SIGSEGV, Segmentation fault.
folder_tree_maybe_expand_row (model=0x5555583b4080, tree_path=0x5555584d4890, iter=<optimized out>, folder_tree=0x5555584b0a60) at em-folder-tree.c:564
564 em-folder-tree.c: Bestand of map bestaat niet.

"Bestand of map bestaat niet" means "File or directory doesn't exist".

Revision history for this message
Martijn Bastiaan (hmb1) wrote :

The function crashes after it being called on line 1204:

handler_id = g_signal_connect (
    model, "loaded-row",
    G_CALLBACK (folder_tree_maybe_expand_row), object);

The variable `key` in the function has the following values before generating a segmentation fault:

1405275544.24245.2@deskei/INBOX
1405275544.24245.2@deskei/INBOX/Test
1405275544.24245.2@deskei/INBOX/Test2
1405275544.24245.2@deskei/INBOX/Test3
1405275544.24245.2@deskei/Drafts
1405275544.24245.2@deskei/Sent
1405275544.24245.2@deskei/Spam
1405275544.24245.2@deskei/Trash
1405275544.24245.2@deskei/.#evolution/Trash
1405275544.24245.2@deskei/.#evolution/Junk
vfolder/UNMATCHED
1405275544.24245.2@deskei/INBOX/Test4
1405275544.24245.2@deskei/INBOX/Test4
Segmentatiefout

The folders before 'vfolder/UNMATCHED' are existing folders, 'Test4' being the new one. As you can see, the only folder being check upon twice is 'Test4'. The folder does indeed not exist, but so do others:

martijn@deskei:~/.config/evolution/mail/folders$ ls
et-expanded-folder:__1405275544.24245.2_40deskei_Drafts
et-expanded-folder:__1405275544.24245.2_40deskei_INBOX
et-expanded-folder:__1405275544.24245.2_40deskei_INBOX_Test2
et-expanded-folder:__1405275544.24245.2_40deskei_INBOX_Test_Nested_box
et-expanded-folder:__1405275544.24245.2_40deskei_INBOX_Test_Nested_Geweten
et-expanded-folder:__1405275544.24245.2_40deskei_INBOX_Test_test

(Which displays non-existing [removed] folders?)

I'm not really sure what to check next: if a developer would like to lend a hand, please :)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.