[Bug 288240] New: Importing of kmail mails into kmail2 crashes the application

vesselin at awcreator.com vesselin at awcreator.com
Mon Dec 5 01:53:20 GMT 2011


https://bugs.kde.org/show_bug.cgi?id=288240

           Summary: Importing of kmail mails into kmail2 crashes the
                    application
           Product: kde
           Version: unspecified
          Platform: unspecified
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: unassigned-bugs at kde.org
        ReportedBy: vesselin at awcreator.com


Application: kmailcvt (4.7.3)
KDE Platform Version: 4.7.3 (4.7.3)
Qt Version: 4.8.0
Operating System: Linux 3.1.2-1.fc16.i686.PAE i686
Distribution: "Fedora release 16 (Verne)"

-- Information about the crash:
- What I was doing when the application crashed:
I was not doing anything - I just started importing kmail mails into kmail2 and
left the converter running. No other desktop/console applications were active
at that time.

- Custom settings of the application:
Destination was set to "Local Folders", source (imported kmail) files were set
to:
/root/.kde/share/apps/kmail/mail/
Import type was set to Import kmail directory with folder structure.

The crash is repeatable and happens about 10-15 minutes after the importing has
started. About 6219 are imported and then the application just crashes.

The crash can be reproduced every time.

-- Backtrace:
Application: KMailCVT (kmailcvt), signal: Aborted
Using host libthread_db library "/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0xb77c1780 (LWP 5440))]

Thread 2 (Thread 0xb652ab40 (LWP 5443)):
#0  0x001a0c14 in __pthread_mutex_unlock_usercnt (mutex=0xb5c004e4, decr=1) at
pthread_mutex_unlock.c:53
#1  0x017febcf in g_main_context_prepare (context=0xb5c004e0,
priority=0xb652a0c8) at gmain.c:2744
#2  0x017ff998 in g_main_context_iterate (context=0xb5c004e0, block=1,
dispatch=1, self=0xb5c00d70) at gmain.c:3053
#3  0x017fffaf in g_main_context_iteration (context=0xb5c004e0, may_block=1) at
gmain.c:3136
#4  0x01e72c67 in QEventDispatcherGlib::processEvents (this=0xb5c00468,
flags=...) at kernel/qeventdispatcher_glib.cpp:426
#5  0x01e3ee4e in QEventLoop::processEvents (this=0xb652a200, flags=...) at
kernel/qeventloop.cpp:149
#6  0x01e3f0f9 in QEventLoop::exec (this=0xb652a200, flags=...) at
kernel/qeventloop.cpp:204
#7  0x01d28adc in QThread::exec (this=0x8825d68) at thread/qthread.cpp:501
#8  0x01e1bdde in QInotifyFileSystemWatcherEngine::run (this=0x8825d68) at
io/qfilesystemwatcher_inotify.cpp:248
#9  0x01d2c061 in QThreadPrivate::start (arg=0x8825d68) at
thread/qthread_unix.cpp:298
#10 0x0019dcd3 in start_thread (arg=0xb652ab40) at pthread_create.c:309
#11 0x00bfa51e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:133

Thread 1 (Thread 0xb77c1780 (LWP 5440)):
[KCrash Handler]
#7  0x003b3416 in __kernel_vsyscall ()
#8  0x00b3798f in __GI_raise (sig=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:64
#9  0x00b392d5 in __GI_abort () at abort.c:91
#10 0x008e974d in __gnu_cxx::__verbose_terminate_handler () at
../../../../libstdc++-v3/libsupc++/vterminate.cc:95
#11 0x008e74c4 in __cxxabiv1::__terminate (handler=0x8e9600
<__gnu_cxx::__verbose_terminate_handler()>) at
../../../../libstdc++-v3/libsupc++/eh_terminate.cc:40
#12 0x008e7500 in std::terminate () at
../../../../libstdc++-v3/libsupc++/eh_terminate.cc:50
#13 0x008e76a5 in __cxxabiv1::__cxa_rethrow () at
../../../../libstdc++-v3/libsupc++/eh_throw.cc:116
#14 0x01e3f3a5 in QEventLoop::exec (this=0xbfebd384, flags=...) at
kernel/qeventloop.cpp:218
#15 0x01e4429b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#16 0x05b0e835 in QApplication::exec () at kernel/qapplication.cpp:3779
#17 0x08050553 in main (argc=1, argv=0xbfebd574) at
/usr/src/debug/kdepim-4.7.3/kmailcvt/main.cpp:47

Possible duplicates by query: bug 287966, bug 286203, bug 285381, bug 284551,
bug 284118.

Reported using DrKonqi

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the Unassigned-bugs mailing list