[kontact] [Bug 318653] New: Kontact crashed when resuming
https://bugs.kde.org/show_bug.cgi?id=318653 Bug ID: 318653 Summary: Kontact crashed when resuming Classification: Unclassified Product: kontact Version: 4.10.2 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: sti...@att.net Application: kontact (4.10.2) KDE Platform Version: 4.10.2 Qt Version: 4.8.4 Operating System: Linux 3.8.0-19-generic x86_64 Distribution: Ubuntu 13.04 -- Information about the crash: - What I was doing when the application crashed: Kontact was running. After some period of inactivity, KDE blanked the screen. When I moved the mouse, screen came back, but Kontact crashed. -- 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 0x7f91d01bc7c0 (LWP 2639))] Thread 5 (Thread 0x7f91b1fdc700 (LWP 2646)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f91cc940585 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f91cc9405d9 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f91c7396f8e in start_thread (arg=0x7f91b1fdc700) at pthread_create.c:311 #4 0x7f91cd738e1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 4 (Thread 0x7f91717d9700 (LWP 2704)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f91cc686a09 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f91cc96ecee in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f91c7396f8e in start_thread (arg=0x7f91717d9700) at pthread_create.c:311 #4 0x7f91cd738e1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 3 (Thread 0x7f915f960700 (LWP 3254)): #0 0x7f91cd72c3cd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f91c6cd41dc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f91c6cd4304 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f91ceb5e036 in QEventDispatcherGlib::processEvents (this=0x7f91580008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f91ceb2e38f in QEventLoop::processEvents (this=this@entry=0x7f915f95fd90, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f91ceb2e618 in QEventLoop::exec (this=this@entry=0x7f915f95fd90, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f91cea30410 in QThread::exec (this=this@entry=0x1137600) at thread/qthread.cpp:542 #7 0x7f91ceb0fedf in QInotifyFileSystemWatcherEngine::run (this=0x1137600) at io/qfilesystemwatcher_inotify.cpp:256 #8 0x7f91cea32bec in QThreadPrivate::start (arg=0x1137600) at thread/qthread_unix.cpp:338 #9 0x7f91c7396f8e in start_thread (arg=0x7f915f960700) at pthread_create.c:311 #10 0x7f91cd738e1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 2 (Thread 0x7f915e8d0700 (LWP 3261)): [KCrash Handler] #6 0x7f91cd676037 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #7 0x7f91cd679698 in __GI_abort () at abort.c:90 #8 0x7f91cd6b35ab in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f91cd7c6860 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:199 #9 0x7f91cd6bfa46 in malloc_printerr (ptr=0x1805290, str=0x7f91cd7c2852 "invalid fastbin entry (free)", action=3) at malloc.c:4902 #10 _int_free (av=, p=0x1805280, have_lock=0) at malloc.c:3758 #11 0x7f91cea7c488 in QString::free (d=0x1805290) at tools/qstring.cpp:1235 #12 0x7f91ca0acc89 in ~QString (this=0x293ac00, __in_chrg=) at ../../include/QtCore/../../src/corelib/tools/qstring.h:880 #13 QDBusMessagePrivate::~QDBusMessagePrivate (this=0x293abe0, __in_chrg=) at qdbusmessage.cpp:72 #14 0x7f91ca0acd9f in QDBusMessage::~QDBusMessage (this=0xa4f, __in_chrg=) at qdbusmessage.cpp:537 #15 0x7f91ca0a88ad in ~QDBusCallDeliveryEvent (this=0x24a0e50, __in_chrg=) at qdbusintegrator_p.h:93 #16 QDBusCallDeliveryEvent::~QDBusCallDeliveryEvent (this=0x24a0e50, __in_chrg=) at qdbusintegrator_p.h:93 #17 0x7f91ceb3317a in QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x1803170) at kernel/qcoreapplication.cpp:1586 #18 0x7f91ceb334a3 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1463 #19 0x7f91ceb5de83 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236 #20 postEventSourceDispatch (s=0x7f91500012d0) at kernel/qeventdispatcher_glib.cpp:279 #21 0x7f91c6cd3f05 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x0
[Bug 152823] "Use Fixed Font" should also affect headers
https://bugs.kde.org/show_bug.cgi?id=152823 Alexey Neyman changed: What|Removed |Added CC||sti...@att.net --- Comment #3 from Alexey Neyman --- It is still an issue with Kmail2 - "use fixed font" changes font for the message, but not the headers. Feel free to consider this a very low priority issue, though, kmail2 has a lot of more important shortcomings to address... :( -- 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 265653] Error after filter moves message to different folder
https://bugs.kde.org/show_bug.cgi?id=265653 --- Comment #4 from Alexey Neyman --- Created attachment 71337 --> https://bugs.kde.org/attachment.cgi?id=71337&action=edit Screenshot of error messages from KMail -- 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 265653] Error after filter moves message to different folder
https://bugs.kde.org/show_bug.cgi?id=265653 Alexey Neyman changed: What|Removed |Added CC||sti...@att.net --- Comment #3 from Alexey Neyman --- Seeing this error in KDE 4.8.3 (Kubuntu Precise) and saw it since 4.8.0. Please reopen this bug. -- 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 296294] New: kmail hangs on mutex in Nepomuk::ResourceManagerPrivate::allResourceDataOfType()
https://bugs.kde.org/show_bug.cgi?id=296294 Bug ID: 296294 Severity: crash Version: 4.8 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: kmail hangs on mutex in Nepomuk::ResourceManagerPrivate::allResourceDataOfType () Classification: Unclassified OS: Linux Reporter: sti...@att.net Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kmail2 It may be a duplicate of bug 291801, but that bug lacks any stacktrace to confirm it. Kmail (running as part of Kontact) sometimes hangs when switching between folders or switching to a different Kontact component; in the stack trace below, the hang was caused by switching from KMail component to Akregator. (gdb) bt #0 0xb7774424 in __kernel_vsyscall () #1 0xb609b8a7 in syscall () at ../sysdeps/unix/sysv/linux/i386/syscall.S:30 #2 0xb62a6638 in _q_futex (val2=0, addr2=0x0, timeout=0x0, val=2, op=0, addr=0xae96a7b0) at thread/qmutex_unix.cpp:99 #3 QMutexPrivate::wait (this=0xae96a7b0, timeout=-1) at thread/qmutex_unix.cpp:113 #4 0xb62a2038 in QMutex::lock (this=0xae9629e0) at thread/qmutex.cpp:164 #5 0xb364a980 in lockInline (this=0xae9629e0) at /usr/include/qt4/QtCore/qmutex.h:188 #6 QMutexLocker (m=0xae9629e0, this=) at /usr/include/qt4/QtCore/qmutex.h:109 #7 Nepomuk::ResourceData::constHasType (this=0xae9629b8, uri=...) at ../../nepomuk/core/resourcedata.cpp:248 #8 0xb365510e in Nepomuk::ResourceManagerPrivate::allResourceDataOfType (this=0x8586038, type=...) at ../../nepomuk/core/resourcemanager.cpp:129 #9 0xb365645d in Nepomuk::ResourceManager::allResourcesOfType (this=0x85872c8, type=...) at ../../nepomuk/core/resourcemanager.cpp:373 #10 0xb366a98a in Nepomuk::Tag::allTags () at ../../nepomuk/core/tag.cpp:130 #11 0xadbbc680 in KMail::TagActionManager::createActions() () from /usr/lib/libkmailprivate.so.4 #12 0xadc759c2 in ?? () from /usr/lib/kde4/kmailpart.so #13 0xb5f82a84 in customEvent (ev=0xbfc2d66c, this=0x83f2c88) at ../../kparts/part.cpp:319 #14 KParts::Part::customEvent (this=0x83f2c88, ev=0xbfc2d66c) at ../../kparts/part.cpp:303 #15 0xb63d740c in QObject::event (this=0x83f2c88, e=0xbfc2d66c) at kernel/qobject.cpp:1226 #16 0xb6924d24 in notify_helper (e=0xbfc2d66c, receiver=0x83f2c88, this=0x8110320) at kernel/qapplication.cpp:4555 #17 QApplicationPrivate::notify_helper (this=0x8110320, receiver=0x83f2c88, e=0xbfc2d66c) at kernel/qapplication.cpp:4527 #18 0xb692a15d in QApplication::notify (this=0xbfc2d66c, receiver=0x83f2c88, e=0xbfc2d66c) at kernel/qapplication.cpp:4284 #19 0xb74a7801 in KApplication::notify (this=0xbfc2ece4, receiver=0x83f2c88, event=0xbfc2d66c) at ../../kdeui/kernel/kapplication.cpp:311 #20 0xb63bc0ae in QCoreApplication::notifyInternal (this=0xbfc2ece4, receiver=0x83f2c88, event=0xbfc2d66c) at kernel/qcoreapplication.cpp:876 #21 0xb5f8f3a0 in sendEvent (event=0xbfc2d66c, receiver=) at /usr/include/qt4/QtCore/qcoreapplication.h:231 #22 KParts::MainWindow::createGUI (this=0x82000e0, part=0x8ab6640) at ../../kparts/mainwindow.cpp:101 #23 0xb7741d93 in Kontact::MainWindow::selectPlugin(KontactInterface::Plugin*) () from /usr/lib/libkontactprivate.so.4 #24 0xb7741084 in ?? () from /usr/lib/libkontactprivate.so.4 #25 0xb63d2de1 in QMetaObject::activate (sender=0x81f2120, m=0xb77536e4, local_signal_index=0, argv=0xbfc2d8f8) at kernel/qobject.cpp:3547 #26 0xb7744bb5 in ?? () from /usr/lib/libkontactprivate.so.4 #27 0xb63d2de1 in QMetaObject::activate (sender=0x81ff830, m=0xb77539dc, local_signal_index=0, argv=0xbfc2d9d8) at kernel/qobject.cpp:3547 #28 0xb77458b5 in ?? () from /usr/lib/libkontactprivate.so.4 #29 0xb7745941 in ?? () from /usr/lib/libkontactprivate.so.4 #30 0xb63d2de1 in QMetaObject::activate (sender=0x810ffc0, m=0xb72a8868, local_signal_index=1, argv=0xbfc2daf4) at kernel/qobject.cpp:3547 #31 0xb6f346fd in QItemSelectionModel::currentChanged (this=0x810ffc0, _t1=..., _t2=...) at .moc/release-shared/moc_qitemselectionmodel.cpp:173 #32 0xb6f3487c in QItemSelectionModel::setCurrentIndex (this=0x810ffc0, index=..., command=...) at itemviews/qitemselectionmodel.cpp:1175 #33 0xb6edc40d in QAbstractItemView::mousePressEvent (this=0x81ff830, event=0xbfc2e494) at itemviews/qabstractitemview.cpp:1682 #34 0xb697f488 in QWidget::event (this=0x81ff830, event=0xbfc2e494) at kernel/qwidget.cpp:8357 #35 0xb6d9c135 in QFrame::event (this=0x81ff830, e=0xbfc2e494) at widgets/qframe.cpp:557 #36 0xb6e2ee21 in QAbstractScrollArea::viewportEvent (this=0x81ff830, e=0xbfc2e494) at widgets/qabstractscrollarea.cpp:1043 #37 0xb6ed4cdc in QAbstractItemView::viewportEvent (this=0x81ff830, event=0xbfc2e494) at itemviews/qabstractitemview.cpp:1644 #38 0xb6e31546 in viewportEvent (this=, event=0xbfc2e494) at widgets/qabstractscrollarea_p.h:100 #39 eventFilter (e=0xbfc2e494, this=, o=) at widgets/qabstractscrollarea_p.h:116 #40 QAbstractScrollAreaFilte
[Bug 295656] Kmail crashes when deleting (moving to trash) e-mails
https://bugs.kde.org/show_bug.cgi?id=295656 --- Comment #1 from Alexey Neyman --- I wish DrKonqi would be able to submit all the information automatically, but it currently cannot log in to bugs.kde.org. -- 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 295656] New: Kmail crashes when deleting (moving to trash) e-mails
https://bugs.kde.org/show_bug.cgi?id=295656 Bug ID: 295656 Severity: grave Version: 4.8 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kmail crashes when deleting (moving to trash) e-mails Classification: Unclassified OS: Linux Reporter: sti...@att.net Hardware: Ubuntu Packages Status: UNCONFIRMED Component: commands and actions Product: kmail2 Created attachment 69444 --> https://bugs.kde.org/attachment.cgi?id=69444&action=edit Backtrace KMail crashes when I delete emails. Although I didn't find a reliable scenario which leads to a crash, I noted that changing the order in which emails are deleted sometime makes KMail succeed in deleting. E.g., if deleting emai A crashes KMail, then deleting email B and then email A sometimes would succeed. The backtrace is attached. It is probably different issue from the bug 295589 - different signal (SIGSEGV vs SIGABRT), and backtraces look different. -- 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 246297] New: Kontact crashed on exit
https://bugs.kde.org/show_bug.cgi?id=246297 Summary: Kontact crashed on exit Product: kontact Version: 4.4.2 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: sti...@att.net Application: kontact (4.4.2) KDE Platform Version: 4.4.2 (KDE 4.4.2) Qt Version: 4.6.2 Operating System: Linux 2.6.34-020634-generic i686 Distribution: Ubuntu 10.04 LTS -- Information about the crash: Tried to quit Kontact - clicked on akregator icon in systray and selected "Quit". It crashed. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0xb35b1990 (LWP 24938))] Thread 2 (Thread 0xaca6bb70 (LWP 24947)): #0 0xb43d2344 in __pthread_mutex_unlock_usercnt (mutex=0x94f3f9c, decr=) at pthread_mutex_unlock.c:52 #1 0xb5ef0be6 in pthread_mutex_unlock (mutex=0x94f3f9c) at forward.c:184 #2 0xb40e1098 in ?? () from /lib/libglib-2.0.so.0 #3 0xb40e14b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #4 0xb6c8b60f in QEventDispatcherGlib::processEvents (this=0x94f1a78, flags=...) at kernel/qeventdispatcher_glib.cpp:414 #5 0xb6c5e059 in QEventLoop::processEvents (this=0xaca6b270, flags=) at kernel/qeventloop.cpp:149 #6 0xb6c5e4aa in QEventLoop::exec (this=0xaca6b270, flags=...) at kernel/qeventloop.cpp:201 #7 0xb6b5a5a8 in QThread::exec (this=0x94f1b78) at thread/qthread.cpp:487 #8 0xb6c3dc1b in QInotifyFileSystemWatcherEngine::run (this=0x94f1b78) at io/qfilesystemwatcher_inotify.cpp:248 #9 0xb6b5d32e in QThreadPrivate::start (arg=0x94f1b78) at thread/qthread_unix.cpp:248 #10 0xb43ce96e in start_thread (arg=0xaca6bb70) at pthread_create.c:300 #11 0xb5ee3a4e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 1 (Thread 0xb35b1990 (LWP 24938)): [KCrash Handler] #6 QString::clear (this=0x8e42598, event=0xbfefb580) at /usr/include/qt4/QtCore/qstring.h:713 #7 KHTMLPart::handleMouseMoveEventDrag (this=0x8e42598, event=0xbfefb580) at ../../khtml/khtml_part.cpp:6310 #8 0xb58554cc in KHTMLPart::khtmlMouseMoveEvent (this=0x8e42598, event=0xbfefb580) at ../../khtml/khtml_part.cpp:6405 #9 0xb582f4af in KHTMLPart::customEvent (this=0x8e42598, event=0xbfefb580) at ../../khtml/khtml_part.cpp:5955 #10 0xb6c7045c in QObject::event (this=0x8e42598, e=0x0) at kernel/qobject.cpp:1279 #11 0xb61af4dc in QApplicationPrivate::notify_helper (this=0x860dd20, receiver=0x8e42598, e=0xbfefb580) at kernel/qapplication.cpp:4300 #12 0xb61b605e in QApplication::notify (this=0xbfefc724, receiver=0x8e42598, e=0xbfefb580) at kernel/qapplication.cpp:3704 #13 0xb71b0f2a in KApplication::notify (this=0xbfefc724, receiver=0x8e42598, event=0xbfefb580) at ../../kdeui/kernel/kapplication.cpp:302 #14 0xb6c5fa3b in QCoreApplication::notifyInternal (this=0xbfefc724, receiver=0x8e42598, event=0xbfefb580) at kernel/qcoreapplication.cpp:704 #15 0xb5826e31 in QCoreApplication::sendEvent (this=0x954e598, _mouse=0xbfefbe70) at /usr/include/qt4/QtCore/qcoreapplication.h:215 #16 KHTMLView::mouseMoveEvent (this=0x954e598, _mouse=0xbfefbe70) at ../../khtml/khtmlview.cpp:1551 #17 0xb620d69a in QWidget::event (this=0x954e598, event=0xbfefbe70) at kernel/qwidget.cpp:7983 #18 0xb6609fd3 in QFrame::event (this=0x954e598, e=0xbfefbe70) at widgets/qframe.cpp:557 #19 0xb582289c in KHTMLView::widgetEvent (this=0x954e598, e=0x0) at ../../khtml/khtmlview.cpp:2362 #20 0xb5822b95 in KHTMLView::eventFilter (this=0x954e598, o=0x995a328, e=0xbfefbe70) at ../../khtml/khtmlview.cpp:2207 #21 0xb6c5ecda in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=0x860dd20, receiver=0x995a328, event=0xbfefbe70) at kernel/qcoreapplication.cpp:819 #22 0xb61af4b9 in QApplicationPrivate::notify_helper (this=0x860dd20, receiver=0x995a328, e=0xbfefbe70) at kernel/qapplication.cpp:4296 #23 0xb61b69f7 in QApplication::notify (this=0xbfefc724, receiver=0x995a328, e=0xbfefbe70) at kernel/qapplication.cpp:3865 #24 0xb71b0f2a in KApplication::notify (this=0xbfefc724, receiver=0x995a328, event=0xbfefbe70) at ../../kdeui/kernel/kapplication.cpp:302 #25 0xb6c5fa3b in QCoreApplication::notifyInternal (this=0xbfefc724, receiver=0x995a328, event=0xbfefbe70) at kernel/qcoreapplication.cpp:704 #26 0xb61b5952 in QCoreApplication::sendEvent (receiver=0x995a328, event=0xbfefbe70, alienWidget=0x995a328, nativeWidget=0x860fcb8, buttonDown=0xb6af3058, lastMouseReceiver=..., spontaneous=true) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #27 QApplicationPrivate::sendMouseEvent (receiver=0x995a328, event=0xbfefbe70, alienWidget=0x995a328, nativeWidget=0x860fcb8, buttonDown=0xb6af3058, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:2965 #28 0xb6241088 in QETWidget::translateMouseEvent (this=0x860fcb8, event=0xbfefc38c) at kernel/qapplication_x11.cpp:4368 #29 0xb6240511 in QApplication:
[Bug 245593] New: Kontact crashed on exiting
https://bugs.kde.org/show_bug.cgi?id=245593 Summary: Kontact crashed on exiting Product: kontact Version: 4.4.2 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: sti...@att.net Application: kontact (4.4.2) KDE Platform Version: 4.4.2 (KDE 4.4.2) Qt Version: 4.6.2 Operating System: Linux 2.6.34-020634-generic i686 Distribution: Ubuntu 10.04 LTS -- Information about the crash: Kontact rarely (maybe 1 out of 10 times) crashes while exiting. Backtrace attached. The crash can be reproduced some of the time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0xb36c9990 (LWP 2562))] Thread 2 (Thread 0xabfc0b70 (LWP 2611)): #0 0xb4287e16 in *__GI_clock_gettime (clock_id=-1272397836, tp=0xabfbff98) at ../sysdeps/unix/clock_gettime.c:100 #1 0xb6da06fb in qt_gettime () at kernel/qcore_unix.cpp:111 #2 0xb6da5825 in QTimerInfoList::updateCurrentTime (this=0xae801924) at kernel/qeventdispatcher_unix.cpp:340 #3 0xb6da586a in QTimerInfoList::timerWait (this=0xae801924, tm=...) at kernel/qeventdispatcher_unix.cpp:443 #4 0xb6da3818 in timerSourcePrepareHelper (src=, timeout=0xabfc00ac) at kernel/qeventdispatcher_glib.cpp:136 #5 0xb6da38a5 in timerSourcePrepare (source=0x0, timeout=0xb428bff4) at kernel/qeventdispatcher_glib.cpp:169 #6 0xb41f8aca in g_main_context_prepare () from /lib/libglib-2.0.so.0 #7 0xb41f8ee9 in ?? () from /lib/libglib-2.0.so.0 #8 0xb41f94b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #9 0xb6da360f in QEventDispatcherGlib::processEvents (this=0xab88f80, flags=...) at kernel/qeventdispatcher_glib.cpp:414 #10 0xb6d76059 in QEventLoop::processEvents (this=0xabfc0270, flags=) at kernel/qeventloop.cpp:149 #11 0xb6d764aa in QEventLoop::exec (this=0xabfc0270, flags=...) at kernel/qeventloop.cpp:201 #12 0xb6c725a8 in QThread::exec (this=0xab51b90) at thread/qthread.cpp:487 #13 0xb6d55c1b in QInotifyFileSystemWatcherEngine::run (this=0xab51b90) at io/qfilesystemwatcher_inotify.cpp:248 #14 0xb6c7532e in QThreadPrivate::start (arg=0xab51b90) at thread/qthread_unix.cpp:248 #15 0xb44e696e in start_thread (arg=0xabfc0b70) at pthread_create.c:300 #16 0xb5ffba4e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 1 (Thread 0xb36c9990 (LWP 2562)): [KCrash Handler] #6 QString::clear (this=0xbeaa7d0, event=0xbff497a0) at /usr/include/qt4/QtCore/qstring.h:713 #7 KHTMLPart::handleMouseMoveEventDrag (this=0xbeaa7d0, event=0xbff497a0) at ../../khtml/khtml_part.cpp:6310 #8 0xb596d4cc in KHTMLPart::khtmlMouseMoveEvent (this=0xbeaa7d0, event=0xbff497a0) at ../../khtml/khtml_part.cpp:6405 #9 0xb59474af in KHTMLPart::customEvent (this=0xbeaa7d0, event=0xbff497a0) at ../../khtml/khtml_part.cpp:5955 #10 0xb6d8845c in QObject::event (this=0xbeaa7d0, e=0x0) at kernel/qobject.cpp:1279 #11 0xb62c74dc in QApplicationPrivate::notify_helper (this=0x9f6dcd0, receiver=0xbeaa7d0, e=0xbff497a0) at kernel/qapplication.cpp:4300 #12 0xb62ce05e in QApplication::notify (this=0xbff4a944, receiver=0xbeaa7d0, e=0xbff497a0) at kernel/qapplication.cpp:3704 #13 0xb72c8f2a in KApplication::notify (this=0xbff4a944, receiver=0xbeaa7d0, event=0xbff497a0) at ../../kdeui/kernel/kapplication.cpp:302 #14 0xb6d77a3b in QCoreApplication::notifyInternal (this=0xbff4a944, receiver=0xbeaa7d0, event=0xbff497a0) at kernel/qcoreapplication.cpp:704 #15 0xb593ee31 in QCoreApplication::sendEvent (this=0xc42c348, _mouse=0xbff4a090) at /usr/include/qt4/QtCore/qcoreapplication.h:215 #16 KHTMLView::mouseMoveEvent (this=0xc42c348, _mouse=0xbff4a090) at ../../khtml/khtmlview.cpp:1551 #17 0xb632569a in QWidget::event (this=0xc42c348, event=0xbff4a090) at kernel/qwidget.cpp:7983 #18 0xb6721fd3 in QFrame::event (this=0xc42c348, e=0xbff4a090) at widgets/qframe.cpp:557 #19 0xb593a89c in KHTMLView::widgetEvent (this=0xc42c348, e=0x0) at ../../khtml/khtmlview.cpp:2362 #20 0xb593ab95 in KHTMLView::eventFilter (this=0xc42c348, o=0xb410c60, e=0xbff4a090) at ../../khtml/khtmlview.cpp:2207 #21 0xb6d76cda in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=0x9f6dcd0, receiver=0xb410c60, event=0xbff4a090) at kernel/qcoreapplication.cpp:819 #22 0xb62c74b9 in QApplicationPrivate::notify_helper (this=0x9f6dcd0, receiver=0xb410c60, e=0xbff4a090) at kernel/qapplication.cpp:4296 #23 0xb62ce9f7 in QApplication::notify (this=0xbff4a944, receiver=0xb410c60, e=0xbff4a090) at kernel/qapplication.cpp:3865 #24 0xb72c8f2a in KApplication::notify (this=0xbff4a944, receiver=0xb410c60, event=0xbff4a090) at ../../kdeui/kernel/kapplication.cpp:302 #25 0xb6d77a3b in QCoreApplication::notifyInternal (this=0xbff4a944, receiver=0xb410c60, event=0xbff4a090) at kernel/qcoreapplication.cpp:704 #26 0xb62cd952 in QCoreApplication::sendEvent (receiver=0xb410c60, event=0xbff4a090, alienWidget=0xb41
[Bug 238702] Kontact crashed when clicking a a mail foder.
https://bugs.kde.org/show_bug.cgi?id=238702 --- Comment #1 from Alexey Neyman 2010-07-22 23:36:34 --- Created an attachment (id=49416) --> (http://bugs.kde.org/attachment.cgi?id=49416) New crash information added by DrKonqi Crash happened during the same operation (switching to another mail folder), although, judging by the backtrace, in a different destructor. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 238702] Kontact crashed when clicking a a mail foder.
https://bugs.kde.org/show_bug.cgi?id=238702 Alexey Neyman changed: What|Removed |Added CC||sti...@att.net -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 192104] Kleopatra does not import X.509 certificates if GPG Agent is not configured to allow clients to mark keys as trusted
https://bugs.kde.org/show_bug.cgi?id=192104 --- Comment #7 from Alexey Neyman 2010-06-29 07:28:37 --- I don't know if it helps: the same certificate can be imported by "gpgsm --import"; it then is printed by "gpgsm -k". However, kleopatra does not show it even after import to gpgsm. I thought kleopatra is just a frontend for GPG - why it cannot import the same certificate that gpgsm can? -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 192104] Kleopatra does not import X.509 certificates if GPG Agent is not configured to allow clients to mark keys as trusted
https://bugs.kde.org/show_bug.cgi?id=192104
Alexey Neyman changed:
What|Removed |Added
CC||sti...@att.net
--- Comment #6 from Alexey Neyman 2010-06-29 07:12:52 ---
Could this bug be confirmed?
I also see the same issue: Kleopatra fails to import X.509 certificate ("This
type of certificate (X.509) is not supported in this Kleopatra installation").
Suggested workaround (checking "allow clients to mark...") does not help.
Kubuntu 10.04, Kleopatra 2.0.12.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are on the CC list for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 152822] Duplicate entries in "Settings -> Configure Shortcuts"
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=152822 --- Additional Comments From alex.neyman mail ru 2007-11-24 15:51 --- Well, hopefully it is gone in the trunk then. Not that I configure shortcuts frequently so this bug isn't really much annoying. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 152823] New: "Use Fixed Font" doesn't affect headers
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=152823 Summary: "Use Fixed Font" doesn't affect headers Product: kmail Version: unspecified Platform: Fedora RPMs OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: alex.neyman mail ru Version:(using KDE KDE 3.5.8) Installed from:Fedora RPMs Bug 55607 made headers always be displayed with proportional font. IMHO, it looks just weird - to have a message partly displayed in proportional and partly in fixed. Could the original suggestion in that ticket be implemented (that is, to have 2 separate options for using fixed font, in header and in message)? ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 152822] Duplicate entries in "Settings -> Configure Shortcuts"
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=152822 --- Additional Comments From alex.neyman mail ru 2007-11-24 12:44 --- Created an attachment (id=22177) --> (http://bugs.kde.org/attachment.cgi?id=22177&action=view) Screenshot ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 152822] New: Duplicate entries in "Settings -> Configure Shortcuts"
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=152822 Summary: Duplicate entries in "Settings -> Configure Shortcuts" Product: kontact Version: unspecified Platform: Fedora RPMs OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: alex.neyman mail ru Version:(using KDE KDE 3.5.8) Installed from:Fedora RPMs This appears similar to Bug 67935, but that bug is marked as fixed long ago - while I see this issue in Fedora Core 8 (KDE 3.5.8). Please see attachment. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
