[Bug 299539] New: kontact crashes soon after starting
https://bugs.kde.org/show_bug.cgi?id=299539 Bug ID: 299539 Severity: crash Version: 4.8.3 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: kontact crashes soon after starting Classification: Unclassified OS: Linux Reporter: ke...@kde.org Hardware: Ubuntu Packages Status: NEW Component: general Product: kontact Application: kontact (4.8.3) KDE Platform Version: 4.8.3 (4.8.3) Qt Version: 4.8.1 Operating System: Linux 3.2.0-24-generic x86_64 Distribution: Ubuntu 12.04 LTS -- Information about the crash: - What I was doing when the application crashed: if i delete all of akonadi data i can get kontact to run about 2 or 3 times after before it starts crashing within about a minute of starting The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5fc86ec7c0 (LWP 3983))] Thread 4 (Thread 0x7f5fabc8b700 (LWP 3984)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f5fc4ef0dec in WTF::TCMalloc_PageHeap::scavengerThread (this=0x7f5fc58b9de0) at wtf/FastMalloc.cpp:2495 #2 0x7f5fc4ef0f19 in WTF::TCMalloc_PageHeap::runScavengerThread (context=) at wtf/FastMalloc.cpp:1618 #3 0x7f5fc03b6e9a in start_thread (arg=0x7f5fabc8b700) at pthread_create.c:308 #4 0x7f5fc5c224bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 3 (Thread 0x7f5fab38a700 (LWP 3985)): #0 0x7fff667c38de in ?? () #1 0x7f5fbe71a15d in __GI_clock_gettime (clock_id=, tp=) at ../sysdeps/unix/clock_gettime.c:116 #2 0x7f5fc62bfbb4 in do_gettime (frac=0x7f5fab389be8, sec=0x7f5fab389be0) at tools/qelapsedtimer_unix.cpp:123 #3 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #4 0x7f5fc6397b8d in QTimerInfoList::updateCurrentTime (this=0x7f5fa4002860) at kernel/qeventdispatcher_unix.cpp:343 #5 0x7f5fc6397841 in timerSourceCheckHelper (src=) at kernel/qeventdispatcher_glib.cpp:150 #6 timerSourceCheckHelper (src=) at kernel/qeventdispatcher_glib.cpp:144 #7 0x7f5fbfee9a33 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f5fbfee9f96 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7f5fbfeea124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7f5fc6397426 in QEventDispatcherGlib::processEvents (this=0x7f5fa40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #11 0x7f5fc6366c82 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #12 0x7f5fc6366ed7 in QEventLoop::exec (this=0x7f5fab389dc0, flags=...) at kernel/qeventloop.cpp:204 #13 0x7f5fc6265fa7 in QThread::exec (this=) at thread/qthread.cpp:501 #14 0x7f5fc6268fcb in QThreadPrivate::start (arg=0x7bb280) at thread/qthread_unix.cpp:298 #15 0x7f5fc03b6e9a in start_thread (arg=0x7f5fab38a700) at pthread_create.c:308 #16 0x7f5fc5c224bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #17 0x in ?? () Thread 2 (Thread 0x7f5f50b86700 (LWP 4000)): #0 0x7f5fc03b8f69 in __pthread_mutex_lock (mutex=0x7f5f44000a60) at pthread_mutex_lock.c:92 #1 0x7f5fbff25561 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5fbfee9729 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5fbfee9f1b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f5fbfeea124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f5fc6397426 in QEventDispatcherGlib::processEvents (this=0x7f5f440008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0x7f5fc6366c82 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #7 0x7f5fc6366ed7 in QEventLoop::exec (this=0x7f5f50b85d90, flags=...) at kernel/qeventloop.cpp:204 #8 0x7f5fc6265fa7 in QThread::exec (this=) at thread/qthread.cpp:501 #9 0x7f5fc63469ff in QInotifyFileSystemWatcherEngine::run (this=0x19e7570) at io/qfilesystemwatcher_inotify.cpp:248 #10 0x7f5fc6268fcb in QThreadPrivate::start (arg=0x19e7570) at thread/qthread_unix.cpp:298 #11 0x7f5fc03b6e9a in start_thread (arg=0x7f5f50b86700) at pthread_create.c:308 #12 0x7f5fc5c224bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #13 0x in ?? () Thread 1 (Thread 0x7f5fc86ec7c0 (LWP 3983)): [KCrash Handler] #6 0x7f5fc5b66445 in __GI_raise (sig=) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #7 0x7f5fc5b69bab in __GI_abort () at abort.c:91 #8 0x7f5fc5ba3e2e in __libc_message (do_abort=2, fmt=0x7f5fc5cac0d0 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:201 #9 0x7f5fc5bae626 in malloc_
[Bug 259784] It would be nice to be able to print only highlighted parts of an email
https://bugs.kde.org/show_bug.cgi?id=259784 Laurent Montel changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Version Fixed In||4.9 Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kdep ||im/d46bd541d8d21bf0291c3a3b ||9c1a5c2bea73450e --- Comment #2 from Laurent Montel --- Git commit d46bd541d8d21bf0291c3a3b9c1a5c2bea73450e by Montel Laurent. Committed on 07/05/2012 at 08:48. Pushed by mlaurent into branch 'master'. Fix Bug 259784 - It would be nice to be able to print only highlighted parts of an email FIXED-IN: 4.9 M +4-0kmail/configuredialog.cpp M +4-0kmail/kmail.kcfg.cmake M +15 -1kmail/kmcommands.cpp M +11 -0kmail/kmcommands.h M +40 -2kmail/kmreaderwin.cpp M +5-1kmail/kmreaderwin.h M +10 -9kmail/messageactions.cpp M +0-1kmail/messageactions.h M +14 -7kmail/ui/miscpagemaintab.ui http://commits.kde.org/kdepim/d46bd541d8d21bf0291c3a3b9c1a5c2bea73450e -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 193514] Crash when activating plugin [[Kontact::Plugin::identifier], Kontact::MainWindow::activatePluginModule, Kontact::MainWindow::setActivePluginModule, KontactApp::newInstance]
https://bugs.kde.org/show_bug.cgi?id=193514 --- Comment #203 from RunetMember --- Created attachment 70914 --> https://bugs.kde.org/attachment.cgi?id=70914&action=edit New crash information added by DrKonqi kontact (4.8.3) on KDE Platform 4.8.3 (4.8.3) using Qt 4.8.1 - What I was doing when the application crashed: > and Akregaror which seems to cause this -- as it has done before. That > particular crash happened after I subscribed to a RSS feed Same for me on 4.8.3. -- Backtrace (Reduced): #6 QString (other=, this=0x7fff8423a390) at /usr/include/qt4/QtCore/qstring.h:725 #7 KontactInterface::Plugin::identifier (this=0xffc29a90ffcda29b) at ../../kontactinterface/plugin.cpp:101 #8 0x7f976ca2357f in activateInitialPluginModule (this=0x1ae9c80) at ../../../kontact/src/mainwindow.cpp:320 #9 Kontact::MainWindow::activateInitialPluginModule (this=0x1ae9c80) at ../../../kontact/src/mainwindow.cpp:315 #10 0x0040410a in KontactApp::newInstance (this=0x7fff8423b550) at ../../../kontact/src/main.cpp:147 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 193514] Crash when activating plugin [[Kontact::Plugin::identifier], Kontact::MainWindow::activatePluginModule, Kontact::MainWindow::setActivePluginModule, KontactApp::newInstance]
https://bugs.kde.org/show_bug.cgi?id=193514 RunetMember changed: What|Removed |Added CC||runetmem...@gmail.com -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 296036] Local Folders: Error: Unsupported type.
https://bugs.kde.org/show_bug.cgi?id=296036 --- Comment #2 from Matthias --- After every mail i sent i see this error message: http://img696.imageshack.us/img696/763/localfolders.png Behind that error is the "E-Mail successfully sent" window. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 299397] Kontact crash whenn I select an other e-mail (Kubuntu 12.04)
https://bugs.kde.org/show_bug.cgi?id=299397 --- Comment #2 from Thomas Pietrowski --- Created attachment 70903 --> https://bugs.kde.org/attachment.cgi?id=70903&action=edit New crash information added by DrKonqi kontact (4.8.2) on KDE Platform 4.8.2 (4.8.2) using Qt 4.8.1 - What I was doing when the application crashed: Happend while trying to open or remove a mail from Kontact (KMail). -- Backtrace (Reduced): #6 QNetworkAccessHttpBackend::replyDownloadMetaData (this=0x4690990, hm=..., sc=, rp=..., pu=, db=..., contentLength=-1) at access/qnetworkaccesshttpbackend.cpp:827 #7 0x7f5d9d68c709 in QNetworkAccessHttpBackend::qt_static_metacall (_o=0x4690990, _c=, _id=, _a=) at .moc/release-shared/moc_qnetworkaccesshttpbackend_p.cpp:91 #8 0x7f5da2780446 in QObject::event (this=0x4690990, e=) at kernel/qobject.cpp:1195 #9 0x7f5da315b894 in notify_helper (e=0x7f5d2c014ae0, receiver=0x4690990, this=0x1dda420) at kernel/qapplication.cpp:4559 #10 QApplicationPrivate::notify_helper (this=0x1dda420, receiver=0x4690990, e=0x7f5d2c014ae0) at kernel/qapplication.cpp:4531 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 299397] Kontact crash whenn I select an other e-mail (Kubuntu 12.04)
https://bugs.kde.org/show_bug.cgi?id=299397 Thomas Pietrowski changed: What|Removed |Added CC||thopie...@googlemail.com -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 299482] groupdav calendar sync fails with "unknown error code 0"
https://bugs.kde.org/show_bug.cgi?id=299482 philippe.cat...@unibas.ch changed: What|Removed |Added CC||philippe.cat...@unibas.ch --- Comment #1 from philippe.cat...@unibas.ch --- I have exactly the same problem. Since upgrading to KDE 4.8.3 I get this error whenever akondi checks for updates. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 282891] searching is severely broken (contains multiple reports)
https://bugs.kde.org/show_bug.cgi?id=282891 Andrew Gaydenko changed: What|Removed |Added CC|a...@gaydenko.com | -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 282891] searching is severely broken (contains multiple reports)
https://bugs.kde.org/show_bug.cgi?id=282891 Mark Fraser changed: What|Removed |Added CC||k...@mfraz.orangehome.co.uk --- Comment #7 from Mark Fraser --- I've upgraded to Kubuntu 12.04 with KDE 4.8.3 and I'm still getting this error. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 299497] New: 'remove attachment' removes all hints that there was an attachment!
https://bugs.kde.org/show_bug.cgi?id=299497 Bug ID: 299497 Severity: normal Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: 'remove attachment' removes all hints that there was an attachment! Classification: Unclassified OS: Linux Reporter: axel.br...@gmx.de Hardware: openSUSE RPMs Status: UNCONFIRMED Component: commands and actions Product: kmail2 Running KDE 4.8.2, if you remove an attachment from a mail, it is not visible anymore that there was every an attachment. This prevents traceability Reproducible: Always Steps to Reproduce: 1. Remove attachment from a mail 2. 3. Actual Results: Nothing is displayed in the message that there was ever an attachment on the mail Expected Results: in KMail1, a line The attachment was removed is displayed. that should be in KMail2 as well -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 299495] New: Kmail (Kontact) crashed while moving Inbox-subfolders
https://bugs.kde.org/show_bug.cgi?id=299495 Bug ID: 299495 Severity: crash Version: 4.8.2 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kmail (Kontact) crashed while moving Inbox-subfolders Classification: Unclassified OS: Linux Reporter: andreas.hen...@hotmail.de Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.8.2) KDE Platform Version: 4.8.2 (4.8.2) Qt Version: 4.8.1 Operating System: Linux 3.2.0-24-generic-pae i686 Distribution: Ubuntu 12.04 LTS -- Information about the crash: - What I was doing when the application crashed: I have setted up just kmail, and created some inbox-subfolders. While I moved two of them, kmail (kontact) crashed immediately. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0xb2157980 (LWP 3077))] Thread 4 (Thread 0xaf8bfb40 (LWP 3078)): #0 0xb7727424 in __kernel_vsyscall () #1 0xb396096b in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:169 #2 0xb60653dc in __pthread_cond_wait (cond=0xb5f14a30, mutex=0xb5f14a18) at forward.c:139 #3 0xb57e3263 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #4 0xb57e337f in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #5 0xb395cd4c in start_thread (arg=0xaf8bfb40) at pthread_create.c:308 #6 0xb6057ace in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 3 (Thread 0xaef96b40 (LWP 3079)): #0 0xb7727424 in __kernel_vsyscall () #1 0xb6049380 in __GI___poll (fds=0xae600df0, nfds=1, timeout=7623) at ../sysdeps/unix/sysv/linux/poll.c:87 #2 0xb3897a3b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb388a06e in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb388a1c1 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0xb63a78e7 in QEventDispatcherGlib::processEvents (this=0xae600468, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0xb637350d in QEventLoop::processEvents (this=0xaef96270, flags=...) at kernel/qeventloop.cpp:149 #7 0xb63737a9 in QEventLoop::exec (this=0xaef96270, flags=...) at kernel/qeventloop.cpp:204 #8 0xb625c94c in QThread::exec (this=0x83a4ec0) at thread/qthread.cpp:501 #9 0xb625ca3b in QThread::run (this=0x83a4ec0) at thread/qthread.cpp:568 #10 0xb625fde0 in QThreadPrivate::start (arg=0x83a4ec0) at thread/qthread_unix.cpp:298 #11 0xb395cd4c in start_thread (arg=0xaef96b40) at pthread_create.c:308 #12 0xb6057ace in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 2 (Thread 0xac17db40 (LWP 3340)): #0 0xb63a8506 in QTimerInfoList::repairTimersIfNeeded (this=0x8b7a59c) at kernel/qeventdispatcher_unix.cpp:402 #1 0xb63a8591 in QTimerInfoList::timerWait (this=0x8b7a59c, tm=...) at kernel/qeventdispatcher_unix.cpp:451 #2 0xb63a6e23 in timerSourcePrepareHelper (src=, timeout=0xac17d0bc) at kernel/qeventdispatcher_glib.cpp:136 #3 0xb63a6ebd in timerSourcePrepare (source=0x8b7a568, timeout=) at kernel/qeventdispatcher_glib.cpp:169 #4 0xb3889762 in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0xb3889f6f in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #6 0xb388a1c1 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #7 0xb63a78e7 in QEventDispatcherGlib::processEvents (this=0x88086c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #8 0xb637350d in QEventLoop::processEvents (this=0xac17d240, flags=...) at kernel/qeventloop.cpp:149 #9 0xb63737a9 in QEventLoop::exec (this=0xac17d240, flags=...) at kernel/qeventloop.cpp:204 #10 0xb625c94c in QThread::exec (this=0x894d4c0) at thread/qthread.cpp:501 #11 0xb6350b5d in QInotifyFileSystemWatcherEngine::run (this=0x894d4c0) at io/qfilesystemwatcher_inotify.cpp:248 #12 0xb625fde0 in QThreadPrivate::start (arg=0x894d4c0) at thread/qthread_unix.cpp:298 #13 0xb395cd4c in start_thread (arg=0xac17db40) at pthread_create.c:308 #14 0xb6057ace in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 1 (Thread 0xb2157980 (LWP 3077)): [KCrash Handler] #7 QModelIndex (other=..., this=0xbfa803b0) at ../../include/QtCore/../../src/corelib/kernel/qabstractitemmodel.h:65 #8 QSortFilterProxyModel::parent (this=0x8570838, child=...) at itemviews/qsortfilterproxymodel.cpp:1659 #9 0xb7415e28 in parent (this=0xbfa80400) at /usr/include/qt4/QtCore/qabstractitemmodel.h:393 #10 KIdentityProxyModel::parent (this=0x8673bd8, child=...) at ../../kdeui/itemviews/kidentityproxymodel.cpp:358 #11 0xb7415e28 in parent (this=0xbfa80460) at /usr/include/qt4/QtCore/qabstractitemmodel.h:393 #12 KIdentityProxyModel::parent (this=0x840f898, child=...) at ../../kdeui/itemviews/kidentityproxymodel.cpp:358 #13 0xb4526dd3 in sibling (acolumn=, arow=, this=) at /usr/include/qt4/QtCo
[Bug 299490] Akregator crashin consistently after extened period idle
https://bugs.kde.org/show_bug.cgi?id=299490 Jekyll Wu changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||adap...@gmail.com Resolution|--- |DUPLICATE --- Comment #1 from Jekyll Wu --- *** This bug has been marked as a duplicate of bug 294707 *** -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 299490] New: Akregator crashin consistently after extened period idle
https://bugs.kde.org/show_bug.cgi?id=299490 Bug ID: 299490 Severity: crash Version: 4.8.2 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Akregator crashin consistently after extened period idle Classification: Unclassified OS: Linux Reporter: k...@itr.no Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: akregator Application: akregator (4.8.2) KDE Platform Version: 4.8.2 (4.8.2) Qt Version: 4.8.1 Operating System: Linux 3.0.0-17-generic i686 Distribution: Ubuntu 11.10 -- Information about the crash: - What I was doing when the application crashed: Nothing, machine left idel over night, found akregator crashed in the morning. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault [Current thread is 1 (Thread 0xb7739730 (LWP 5175))] Thread 7 (Thread 0xaf222b70 (LWP 5188)): #0 0x00ef6d10 in clock_gettime () from /lib/i386-linux-gnu/librt.so.1 #1 0x04ad03a5 in do_gettime (frac=0xaf221f30, sec=0xaf221f28) at tools/qelapsedtimer_unix.cpp:123 #2 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #3 0x04bba3d6 in QTimerInfoList::updateCurrentTime (this=0xbbb8e84) at kernel/qeventdispatcher_unix.cpp:343 #4 0x04bba72a in QTimerInfoList::timerWait (this=0xbbb8e84, tm=...) at kernel/qeventdispatcher_unix.cpp:450 #5 0x04bb8f43 in timerSourcePrepareHelper (src=, timeout=0xaf22203c) at kernel/qeventdispatcher_glib.cpp:136 #6 0x04bb8fdd in timerSourcePrepare (source=0xbbb8e50, timeout=) at kernel/qeventdispatcher_glib.cpp:169 #7 0x03d6988c in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #8 0x03d6a637 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #9 0x03d6ac2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #10 0x04bb9a97 in QEventDispatcherGlib::processEvents (this=0xa7211f8, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #11 0x04b855ed in QEventLoop::processEvents (this=0xaf2221d0, flags=...) at kernel/qeventloop.cpp:149 #12 0x04b85889 in QEventLoop::exec (this=0xaf2221d0, flags=...) at kernel/qeventloop.cpp:204 #13 0x04a6e9dc in QThread::exec (this=0xacd09f0) at thread/qthread.cpp:501 #14 0x04b62b5d in QInotifyFileSystemWatcherEngine::run (this=0xacd09f0) at io/qfilesystemwatcher_inotify.cpp:248 #15 0x04a71e70 in QThreadPrivate::start (arg=0xacd09f0) at thread/qthread_unix.cpp:298 #16 0x03ea49cd in ?? () from /usr/lib/nvidia-current/libGL.so.1 #17 0x00dc046e in clone () from /lib/i386-linux-gnu/libc.so.6 Backtrace stopped: Not enough registers or memory available to unwind further Thread 6 (Thread 0xb10f7b70 (LWP 28983)): #0 0x002ed416 in __kernel_vsyscall () #1 0x01ea1a5c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0 #2 0x00dce09c in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6 #3 0xb4892883 in WTF::TCMalloc_PageHeap::scavengerThread (this=0xb4fae340) at wtf/FastMalloc.cpp:2495 #4 0xb489299f in WTF::TCMalloc_PageHeap::runScavengerThread (context=0xb4fae340) at wtf/FastMalloc.cpp:1618 #5 0x03ea49cd in ?? () from /usr/lib/nvidia-current/libGL.so.1 #6 0x00dc046e in clone () from /lib/i386-linux-gnu/libc.so.6 Backtrace stopped: Not enough registers or memory available to unwind further Thread 5 (Thread 0xaea21b70 (LWP 29040)): #0 0x00ef6d10 in clock_gettime () from /lib/i386-linux-gnu/librt.so.1 #1 0x04ad03a5 in do_gettime (frac=0xaea20fc0, sec=0xaea20fb8) at tools/qelapsedtimer_unix.cpp:123 #2 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #3 0x04bba3d6 in QTimerInfoList::updateCurrentTime (this=0xb1100afc) at kernel/qeventdispatcher_unix.cpp:343 #4 0x04bb9fc6 in timerSourceCheckHelper (src=0xb1100ac8) at kernel/qeventdispatcher_glib.cpp:150 #5 timerSourceCheckHelper (src=0xb1100ac8) at kernel/qeventdispatcher_glib.cpp:144 #6 0x03d69f24 in g_main_context_check () from /lib/i386-linux-gnu/libglib-2.0.so.0 #7 0x03d6a8f0 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #8 0x03d6ac2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #9 0x04bb9a97 in QEventDispatcherGlib::processEvents (this=0x9c31330, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #10 0x04b855ed in QEventLoop::processEvents (this=0xaea21200, flags=...) at kernel/qeventloop.cpp:149 #11 0x04b85889 in QEventLoop::exec (this=0xaea21200, flags=...) at kernel/qeventloop.cpp:204 #12 0x04a6e9dc in QThread::exec (this=0xbd29df8) at thread/qthread.cpp:501 #13 0x04a6eacb in QThread::run (this=0xbd29df8) at thread/qthread.cpp:568 #14 0x04a71e70 in QThreadPrivate::start (arg=0xbd29df8) at thread/qthread_unix.cpp:298 #15 0x03ea49cd in ?? () from /usr/lib/nvidia-current/libGL.so.1 #16 0x00dc046e in clone () from /lib/i386-linux-gnu/libc.so.6 Backtrace stopped: Not enough registers or memory available to unwind further Thread 4 (Thread 0xaddb7b70 (LWP 29926)): #0 0x002ed416 in __kernel_vsyscall () #1 0x01e
[Bug 280761] crash after entering sieve password during fetch mail
https://bugs.kde.org/show_bug.cgi?id=280761 --- Comment #5 from Dennis Schridde --- Created attachment 70892 --> https://bugs.kde.org/attachment.cgi?id=70892&action=edit New crash information added by DrKonqi kontact (4.8.3) on KDE Platform 4.8.3 (4.8.3) using Qt 4.8.1 The issue persists in KDE 4.8.3. - What I was doing when the application crashed: Same thing as last time: Using Kontact/KMail with Sieve, waiting after starting Kontact while ignoring the KWallet password dialogue, Sieve password dialogue pops up, I enter my password and Kontact crashes. -- Backtrace (Reduced): #6 0x003ea1131231 in QUrl::setUserName(QString const&) () from /usr/lib64/qt4/libQtCore.so.4 #7 0x003eb7206904 in KManageSieve::Session::saslInteract (this=0x16f4bc0, in=0x1824180) at /var/tmp/portage/kde-base/kmail-4.8.3/work/kmail-4.8.3/libksieve/kmanagesieve/session.cpp:448 #8 0x003eb7207694 in KManageSieve::Session::startAuthentication (this=0x16f4bc0) at /var/tmp/portage/kde-base/kmail-4.8.3/work/kmail-4.8.3/libksieve/kmanagesieve/session.cpp:375 #9 0x003eb72087d1 in KManageSieve::Session::processResponse (this=0x16f4bc0, response=..., data=...) at /var/tmp/portage/kde-base/kmail-4.8.3/work/kmail-4.8.3/libksieve/kmanagesieve/session.cpp:190 #10 0x003eb72099f5 in KManageSieve::Session::dataReceived (this=0x16f4bc0) at /var/tmp/portage/kde-base/kmail-4.8.3/work/kmail-4.8.3/libksieve/kmanagesieve/session.cpp:134 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 299483] New: akonadi crashes when ~/.local is a symlink
https://bugs.kde.org/show_bug.cgi?id=299483
Bug ID: 299483
Severity: normal
Version: unspecified
Priority: NOR
Assignee: kdepim-bugs@kde.org
Summary: akonadi crashes when ~/.local is a symlink
Classification: Unclassified
OS: Linux
Reporter: tnem...@free.fr
Hardware: Ubuntu Packages
Status: UNCONFIRMED
Component: server
Product: Akonadi
I had found I had no contact list in the address book at startup. It happened
to be because
of ~/.local was a symlink and akonadi could not start. When I moved the real
directory into
place, akonadi could start.
Reproducible: Always
Steps to Reproduce:
1. akonadictl stop (or just after a clean installation)
2. mv ~/.local /somewhere/else/on/your/drive
3. ln -s /somewhere/else/on/your/drive/.local
4. akonatictl start
Actual Results:
akonadi could not start :
Test 15: ERROR
Current Akonadi server error log found.
Details: The Akonadi server reported errors during its current startup. The log
can be found in /home/thomas/.local/share/akonadi/akonadiserver.error.
File content of '/home/thomas/.local/share/akonadi/akonadiserver.error':
Database process exited unexpectedly during initial connection!
executable: "/usr/sbin/mysqld-akonadi"
arguments: ("--defaults-file=/home/thomas/.local/share/akonadi/mysql.conf",
"--datadir=/home/thomas/.local/share/akonadi/db_data/",
"--socket=/home/thomas/.local/share/akonadi/socket-cixi/mysql.socket")
stdout: ""
stderr: "Could not open required defaults file:
/home/thomas/.local/share/akonadi/mysql.conf
Fatal error in defaults handling. Program aborted
"
exit code: 1
process error: "Unknown error"
"[
0: akonadiserver() [0x805d566]
1: akonadiserver() [0x805d821]
2: [0xb7745400]
3: [0xb7745424]
4: /lib/i386-linux-gnu/libc.so.6(gsignal+0x4f) [0xb6e1b1ef]
5: /lib/i386-linux-gnu/libc.so.6(abort+0x175) [0xb6e1e835]
6:
/usr/lib/i386-linux-gnu/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x136)
[0xb74ac616]
7: akonadiserver() [0x805f9d8]
8: /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xc9)
[0xb7555e59]
9: /usr/lib/i386-linux-gnu/libQtCore.so.4(+0x112c7d) [0xb7562c7d]
10: /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x3e)
[0xb756c7ce]
11: akonadiserver() [0x8056b35]
12: akonadiserver() [0x80ea505]
13: akonadiserver() [0x80607c9]
14: akonadiserver() [0x8061f51]
15: akonadiserver() [0x8063716]
16: akonadiserver() [0x8055fe0]
17: /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0xb6e064d3]
18: akonadiserver() [0x80569d1]
]
"
Expected Results:
Akonadi should have starter normaly
--
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs
