Bug 292516 - KMail2 IMAP accounts keep crashing and loosing email content
Summary: KMail2 IMAP accounts keep crashing and loosing email content
Status: RESOLVED FIXED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.7
Platform: openSUSE Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-26 21:03 UTC by Otter
Modified: 2016-09-25 16:06 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Otter 2012-01-26 21:03:29 UTC
Version:           4.7 (using KDE 4.7.4) 
OS:                Linux

the following is showing up for one IMAP account.

KCrash: Application 'akonadi_imap_resource' crashing...                                                                                              
KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from kdeinit                                                                             
sock_file=/home/chrisg/.kde4/socket-linux-5xzp.site/kdeinit4__0                                                                                      
void Akonadi::NotificationSource::serviceUnregistered(const QString&) Notification source "akonadi_imap_resource_11" now serving: ()                 
void Akonadi::NotificationSource::unsubscribe() "akonadi_imap_resource_11"                                                                           
Lost connection to resource "org.freedesktop.Akonadi.Resource.akonadi_imap_resource_11" , discarding cached interface                                
QSocketNotifier: Invalid socket 14 and type 'Read', disabling...                                                                                     
The stream parser raised an exception: Unable to read more data                                                                                      
ProcessControl: Application '/usr/bin/akonadi_imap_resource' returned with exit code 253 (Unknown error)                                             
Database "akonadi" opened using driver "QMYSQL" 

               
Is this fixable or do I have to wait for 4.8?  

I will apologize right up front for saying this.  I know the developers are working hard on many issues.  The release of KMail2 in to the wild seems to have been premature.  Please, please, if something new say a major change of structure (such as Kmail2) is going to be released on an unsuspecting and trusting public do some more testing.  Don't assume anything about the end user's skills or experience.  Please don't give the condescending remarks about using unstable software/user beware.  The stable releases across most distributions seem to be reporting problems so the use of unstable software is not the issue.

Reproducible: Always

Steps to Reproduce:
Just start Kmail or Kontact.

Actual Results:  
bug crash with the following:

Executable: akonadi_imap_resource PID: 20161 Signal: Segmentation fault (11)

QSocketNotifier: Invalid socket 12 and type 'Read', disabling...
The stream parser raised an exception: Unable to read more data 
ProcessControl: Application '/usr/bin/akonadi_imap_resource' returned with exit code 253 (Unknown error)
Database "akonadi" opened using driver "QMYSQL" 


Expected Results:  
receive email without crashes.  

Obviously very frustrated.  Just want to find some help on getting this to work.
Comment 1 Freek de Kruijf 2014-08-10 21:04:08 UTC
Application: akonadi_imap_resource (4.13)
KDE Platform Version: 4.13.80
Qt Version: 4.8.6
Operating System: Linux 3.16.0-rc7-2-desktop x86_64
Distribution: "openSUSE 20140807 (Harlequin) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:

Just started Kontact and entered the password for KWallet

The crash can be reproduced every time.

-- Backtrace:
Application: IMAP-eik van type IMAP E-Mail Server (akonadi_imap_resource), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
To enable execution of this file add
	add-auto-load-safe-path /usr/lib64/libstdc++.so.6.0.19-gdb.py
line to your configuration file "/home/freek/.gdbinit".
To completely disable this security protection add
	set auto-load safe-path /
line to your configuration file "/home/freek/.gdbinit".
For more information about this security protection see the
"Auto-loading safe path" section in the GDB manual.  E.g., run from the shell:
	info "(gdb)Auto-loading safe path"
[KCrash Handler]
#5  0x0000000000450a44 in SessionPool::cancelPasswordRequests (this=<optimized out>) at /usr/src/debug/kdepim-runtime-4.13.80/resources/imap/sessionpool.cpp:71
#6  0x00000000004321f7 in ImapResourceBase::doSetOnline (this=0xcb5300, online=<optimized out>) at /usr/src/debug/kdepim-runtime-4.13.80/resources/imap/imapresourcebase.cpp:554
#7  0x00007f3214a286b1 in Akonadi::AgentBase::setOnlineInternal (this=0xcb5300, state=false) at /usr/src/debug/kdepimlibs-4.13.80/akonadi/agentbase.cpp:965
#8  0x000000000042a934 in ImapResourceBase::ImapResourceBase (this=0xcb5300, id=...) at /usr/src/debug/kdepim-runtime-4.13.80/resources/imap/imapresourcebase.cpp:145
#9  0x000000000041a2a0 in ImapResource::ImapResource (this=0xcb5300, id=...) at /usr/src/debug/kdepim-runtime-4.13.80/resources/imap/imapresource.cpp:37
#10 0x000000000041a03a in Akonadi::ResourceBase::init<ImapResource> (argc=<optimized out>, argv=<optimized out>) at /usr/include/akonadi/resourcebase.h:184
#11 0x00007f32108b8b05 in __libc_start_main () from /lib64/libc.so.6
#12 0x0000000000419f14 in _start () at ../sysdeps/x86_64/start.S:122

Rapporteer aan https://bugs.kde.org/
Comment 2 Denis Kurz 2016-09-24 18:12:29 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 3 Freek de Kruijf 2016-09-25 16:06:00 UTC
Does not happen anymore. Is no longer reproducible. Consider it fixed.