[Bug 257815] New: Kontact crashed on startup with IMAP accounts enabled.

Daniel Molina Wegener dmw at coder.cl
Wed Nov 24 19:13:15 GMT 2010


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

           Summary: Kontact crashed on startup with IMAP accounts enabled.
           Product: kontact
           Version: unspecified
          Platform: Ubuntu Packages
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: kdepim-bugs at kde.org
        ReportedBy: dmw at coder.cl


Application: kontact (4.4.6)
KDE Platform Version: 4.5.1 (KDE 4.5.1)
Qt Version: 4.7.0
Operating System: Linux 2.6.35-23-generic-pae i686
Distribution: Ubuntu 10.10

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

I've just restarted Kontact and it crashed. I think that it was caused since it
has tried to open IMAP folders.

- Custom settings of the application:

I have about 4 IMAP accounts, for different domains. Two of them at Google
Mail.

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[Current thread is 1 (Thread 0xb3097730 (LWP 29560))]

Thread 2 (Thread 0xaa704b70 (LWP 29581)):
#0  0xb786f424 in __kernel_vsyscall ()
#1  0xb5f90df6 in __poll (fds=0xb6028ff4, nfds=1, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:87
#2  0xb41d5a1b in g_poll () from /lib/libglib-2.0.so.0
#3  0xb41c843c in ?? () from /lib/libglib-2.0.so.0
#4  0xb41c8848 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#5  0xb62aa59f in QEventDispatcherGlib::processEvents (this=0xa4aeb88,
flags=...) at kernel/qeventdispatcher_glib.cpp:417
#6  0xb627a609 in QEventLoop::processEvents (this=0xaa704270, flags=) at
kernel/qeventloop.cpp:149
#7  0xb627aa8a in QEventLoop::exec (this=0xaa704270, flags=...) at
kernel/qeventloop.cpp:201
#8  0xb6176b7e in QThread::exec (this=0xa84fa50) at thread/qthread.cpp:490
#9  0xb625935b in QInotifyFileSystemWatcherEngine::run (this=0xa84fa50) at
io/qfilesystemwatcher_inotify.cpp:248
#10 0xb6179df9 in QThreadPrivate::start (arg=0xa84fa50) at
thread/qthread_unix.cpp:266
#11 0xb44c3cc9 in start_thread (arg=0xaa704b70) at pthread_create.c:304
#12 0xb5f9f6be in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb3097730 (LWP 29560)):
[KCrash Handler]
#7  Kontact::MainWindow::activateInitialPluginModule (this=0x9e8c9f8) at
../../../kontact/src/mainwindow.cpp:289
#8  0xb782e814 in Kontact::MainWindow::setInitialActivePluginModule
(this=0x9e8c9f8, module=...) at ../../../kontact/src/mainwindow.cpp:266
#9  0x0804b9ef in KontactApp::newInstance (this=0xbfb4aee4) at
../../../kontact/src/main.cpp:149
#10 0xb72e0800 in KUniqueApplicationAdaptor::newInstance (this=0x9da3308,
asn_id=..., args=...) at ../../kdeui/kernel/kuniqueapplication.cpp:440
#11 0xb72e0f62 in KUniqueApplicationAdaptor::qt_metacall (this=0x9da3308,
_c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfb4a42c) at
./kuniqueapplication_p.moc:81
#12 0xb54ca9dc in QDBusConnectionPrivate::deliverCall (this=0x9d88880,
object=0x9da3308, msg=..., metaTypes=..., slotIdx=4) at qdbusintegrator.cpp:919
#13 0xb54cbd25 in QDBusConnectionPrivate::activateCall (this=0x9d88880,
object=0x9da3308, flags=337, msg=...) at qdbusintegrator.cpp:829
#14 0xb54cc770 in QDBusConnectionPrivate::activateObject (this=0x9d88880,
node=..., msg=..., pathStartPos=16) at qdbusintegrator.cpp:1379
#15 0xb54cca2a in QDBusActivateObjectEvent::placeMetaCall (this=0xa2ea290) at
qdbusintegrator.cpp:1493
#16 0xb628e6a2 in QObject::event (this=0xbfb4aee4, e=0xbfb4a17f) at
kernel/qobject.cpp:1219
#17 0xb627b9db in QCoreApplication::event (this=0xbfb4aee4, e=0xa2ea290) at
kernel/qcoreapplication.cpp:1561
#18 0xb67664d4 in QApplication::event (this=0xbfb4aee4, e=0xa2ea290) at
kernel/qapplication.cpp:2439
#19 0xb6762fdc in QApplicationPrivate::notify_helper (this=0x9d92328,
receiver=0xbfb4aee4, e=0xa2ea290) at kernel/qapplication.cpp:4396
#20 0xb676904e in QApplication::notify (this=0xbfb4aee4, receiver=0xbfb4aee4,
e=0xa2ea290) at kernel/qapplication.cpp:3798
#21 0xb72d868a in KApplication::notify (this=0xbfb4aee4, receiver=0xbfb4aee4,
event=0xa2ea290) at ../../kdeui/kernel/kapplication.cpp:310
#22 0xb627bb3b in QCoreApplication::notifyInternal (this=0xbfb4aee4,
receiver=0xbfb4aee4, event=0xa2ea290) at kernel/qcoreapplication.cpp:732
#23 0xb627ed8b in sendEvent (receiver=0x0, event_type=0, data=0x9d6fed0) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#24 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0,
data=0x9d6fed0) at kernel/qcoreapplication.cpp:1373
#25 0xb627ef4d in QCoreApplication::sendPostedEvents (receiver=0x0,
event_type=0) at kernel/qcoreapplication.cpp:1266
#26 0xb62aaa74 in sendPostedEvents (s=0x9d97d78) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#27 postEventSourceDispatch (s=0x9d97d78) at
kernel/qeventdispatcher_glib.cpp:277
#28 0xb41c4855 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#29 0xb41c8668 in ?? () from /lib/libglib-2.0.so.0
#30 0xb41c8848 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#31 0xb62aa565 in QEventDispatcherGlib::processEvents (this=0x9d6fb90,
flags=...) at kernel/qeventdispatcher_glib.cpp:415
#32 0xb6824be5 in QGuiEventDispatcherGlib::processEvents (this=0x9d6fb90,
flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#33 0xb627a609 in QEventLoop::processEvents (this=0xbfb4ae44, flags=) at
kernel/qeventloop.cpp:149
#34 0xb627aa8a in QEventLoop::exec (this=0xbfb4ae44, flags=...) at
kernel/qeventloop.cpp:201
#35 0xb627f00f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#36 0xb6761e07 in QApplication::exec () at kernel/qapplication.cpp:3672
#37 0x0804b132 in main (argc=1, argv=0xbfb4b104) at
../../../kontact/src/main.cpp:224

This bug may be a duplicate of or related to bug 193514.

Possible duplicates by query: bug 256827, bug 256085, bug 256028, bug 255142,
bug 247559.

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 Kdepim-bugs mailing list