[Bug 273949] Akonadi Resource always seen as readonly
https://bugs.kde.org/show_bug.cgi?id=273949 --- Comment #46 from Orion --- well, the Contacts issue is sort of "off-bug" but a comment I found on kdeforums hint that autocompletion has been disabled in 4.8.x due to some coding problem. See here http://forum.kde.org/viewtopic.php?f=215&t=100742 I can not vouch for the truth of this but I have tried various 4.8.x installs and found that autocompletion is gone. So I stay on 4.7.4 myself and hope for 4.9 to fix this -- 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 298322] Kmail crash when mark some html mails as read
https://bugs.kde.org/show_bug.cgi?id=298322 Laurent Montel changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||mon...@kde.org Resolution|--- |DUPLICATE --- Comment #1 from Laurent Montel --- *** This bug has been marked as a duplicate of bug 286307 *** -- 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 286307] Kmail crash (QNetworkAccessHttpBackend::replyDownloadMetaData, QNetworkAccessHttpBackend::qt_static_metacall, QObject::event)
https://bugs.kde.org/show_bug.cgi?id=286307 Laurent Montel changed: What|Removed |Added CC||mmes...@gmail.com --- Comment #128 from Laurent Montel --- *** Bug 298322 has been marked as a duplicate of 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 298328] New: Crash on Kontact Startup
https://bugs.kde.org/show_bug.cgi?id=298328 Bug ID: 298328 Severity: crash Version: 4.8.2 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Crash on Kontact Startup Classification: Unclassified OS: Linux Reporter: k...@kitterman.com 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-23-generic-pae i686 Distribution: Ubuntu precise (development branch) -- Information about the crash: - What I was doing when the application crashed: Crash was immediately on startup before I even saw the U/I start to draw. Akonadi was in a stopped state when Kontact was launched. The backtrace seems similar, but not identical to the backtrace in the suggested dupe. I'm not enough of an expert at reading backtraces to know if it's a dupe or not. -- 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 0xb210f980 (LWP 2789))] Thread 4 (Thread 0xafaf9b40 (LWP 2790)): #0 0xb76e4424 in __kernel_vsyscall () #1 0xb391896b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0 #2 0xb601d3dc in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6 #3 0xb579b263 in WTF::TCMalloc_PageHeap::scavengerThread (this=0xb5ec7940) at wtf/FastMalloc.cpp:2495 #4 0xb579b37f in WTF::TCMalloc_PageHeap::runScavengerThread (context=0xb5ec7940) at wtf/FastMalloc.cpp:1618 #5 0xb3914d4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #6 0xb600face in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 3 (Thread 0xaf1d8b40 (LWP 2791)): #0 0xb3666dcd in clock_gettime () from /lib/i386-linux-gnu/librt.so.1 #1 0xb6276315 in do_gettime (frac=0xaf1d8040, sec=0xaf1d8038) at tools/qelapsedtimer_unix.cpp:123 #2 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #3 0xb6360226 in QTimerInfoList::updateCurrentTime (this=0xae802074) at kernel/qeventdispatcher_unix.cpp:343 #4 0xb635fe16 in timerSourceCheckHelper (src=0xae802040) at kernel/qeventdispatcher_glib.cpp:150 #5 timerSourceCheckHelper (src=0xae802040) at kernel/qeventdispatcher_glib.cpp:144 #6 0xb3841a6b in g_main_context_check () from /lib/i386-linux-gnu/libglib-2.0.so.0 #7 0xb3842002 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #8 0xb38421c1 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #9 0xb635f8e7 in QEventDispatcherGlib::processEvents (this=0xae800468, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #10 0xb632b50d in QEventLoop::processEvents (this=0xaf1d8270, flags=...) at kernel/qeventloop.cpp:149 #11 0xb632b7a9 in QEventLoop::exec (this=0xaf1d8270, flags=...) at kernel/qeventloop.cpp:204 #12 0xb621494c in QThread::exec (this=0x95f1190) at thread/qthread.cpp:501 #13 0xb6214a3b in QThread::run (this=0x95f1190) at thread/qthread.cpp:568 #14 0xb6217de0 in QThreadPrivate::start (arg=0x95f1190) at thread/qthread_unix.cpp:298 #15 0xb3914d4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #16 0xb600face in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 2 (Thread 0xac565b40 (LWP 2811)): #0 0xb3666dcd in clock_gettime () from /lib/i386-linux-gnu/librt.so.1 #1 0xb6276315 in do_gettime (frac=0xac564fb0, sec=0xac564fa8) at tools/qelapsedtimer_unix.cpp:123 #2 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #3 0xb6360226 in QTimerInfoList::updateCurrentTime (this=0xabc02074) at kernel/qeventdispatcher_unix.cpp:343 #4 0xb636057a in QTimerInfoList::timerWait (this=0xabc02074, tm=...) at kernel/qeventdispatcher_unix.cpp:450 #5 0xb635ee23 in timerSourcePrepareHelper (src=, timeout=0xac5650bc) at kernel/qeventdispatcher_glib.cpp:136 #6 0xb635eebd in timerSourcePrepare (source=0xabc02040, timeout=) at kernel/qeventdispatcher_glib.cpp:169 #7 0xb3841762 in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #8 0xb3841f6f in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #9 0xb38421c1 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #10 0xb635f8e7 in QEventDispatcherGlib::processEvents (this=0xabc00468, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #11 0xb632b50d in QEventLoop::processEvents (this=0xac565240, flags=...) at kernel/qeventloop.cpp:149 #12 0xb632b7a9 in QEventLoop::exec (this=0xac565240, flags=...) at kernel/qeventloop.cpp:204 #13 0xb621494c in QThread::exec (this=0x9a73f30) at thread/qthread.cpp:501 #14 0xb6308b5d in QInotifyFileSystemWatcherEngine::run (this=0x9a73f30) at io/qfilesystemwatcher_inotify.cpp:248 #15 0xb6217de0 in QThreadPrivate::start (arg=0x9a73f30) at thread/qthread_unix.cpp:298 #16 0xb3914d4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #17 0xb600face in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 1 (Thread
[Bug 298327] New: Crash when adding a link
https://bugs.kde.org/show_bug.cgi?id=298327 Bug ID: 298327 Severity: crash Version: 4.8.2 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Crash when adding a link Classification: Unclassified OS: Linux Reporter: meer...@interia.eu Hardware: openSUSE RPMs Status: UNCONFIRMED Component: general Product: akregator Application: akregator (4.8.2) KDE Platform Version: 4.8.2 (4.8.2) "release 491" Qt Version: 4.8.1 Operating System: Linux 3.1.9-1.4-default x86_64 Distribution: "openSUSE 12.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I tried to add the following web link to the Akregator. Link: http://feeds.feedburner.com/niebezpiecznik?format=xml -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault [Current thread is 1 (Thread 0x7f8588365760 (LWP 4974))] Thread 2 (Thread 0x7f8562f85700 (LWP 5937)): #0 0x7fffb214d98f in clock_gettime () #1 0x7f857f2fed9a in clock_gettime () from /lib64/librt.so.1 #2 0x7f85866a7f64 in do_gettime (frac=0x7f8562f84b78, sec=0x7f8562f84b70) at tools/qelapsedtimer_unix.cpp:123 #3 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #4 0x7f858677ea4d in QTimerInfoList::updateCurrentTime (this=0x7f85580020d0) at kernel/qeventdispatcher_unix.cpp:343 #5 0x7f858677ed83 in QTimerInfoList::timerWait (this=0x7f85580020d0, tm=...) at kernel/qeventdispatcher_unix.cpp:450 #6 0x7f858677d7bc in timerSourcePrepareHelper (src=, timeout=0x7f8562f84c5c) at kernel/qeventdispatcher_glib.cpp:136 #7 0x7f858677d865 in timerSourcePrepare (source=, timeout=) at kernel/qeventdispatcher_glib.cpp:169 #8 0x7f857f049b22 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #9 0x7f857f04a92d in ?? () from /usr/lib64/libglib-2.0.so.0 #10 0x7f857f04af59 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #11 0x7f858677e2e6 in QEventDispatcherGlib::processEvents (this=0x7f85580008c0, flags=) at kernel/qeventdispatcher_glib.cpp:426 #12 0x7f858674e012 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #13 0x7f858674e267 in QEventLoop::exec (this=0x7f8562f84df0, flags=...) at kernel/qeventloop.cpp:204 #14 0x7f858664e547 in QThread::exec (this=) at thread/qthread.cpp:501 #15 0x7f858672ddff in QInotifyFileSystemWatcherEngine::run (this=0x1f58ba0) at io/qfilesystemwatcher_inotify.cpp:248 #16 0x7f858665156b in QThreadPrivate::start (arg=0x1f58ba0) at thread/qthread_unix.cpp:298 #17 0x7f85803c0f05 in start_thread () from /lib64/libpthread.so.0 #18 0x7f8584ea210d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f8588365760 (LWP 4974)): [KCrash Handler] #6 isEmpty (this=0xa5) at /usr/include/QtCore/qhash.h:297 #7 Akregator::Feed::findArticle (this=, guid=...) at /usr/src/debug/kdepim-4.8.2/akregator/src/feed.cpp:214 #8 0x7f85878409c2 in Akregator::FeedList::findArticle (this=, feedURL=, guid=...) at /usr/src/debug/kdepim-4.8.2/akregator/src/feedlist.cpp:340 #9 0x7f85716b449c in (anonymous namespace)::articleForIndex (index=..., feedList=0x1357d90) at /usr/src/debug/kdepim-4.8.2/akregator/src/selectioncontroller.cpp:53 #10 0x7f85716b45d6 in Akregator::SelectionController::currentArticle (this=0x7fb210) at /usr/src/debug/kdepim-4.8.2/akregator/src/selectioncontroller.cpp:148 #11 0x7f85716b4cb7 in Akregator::SelectionController::articleSelectionChanged (this=0x7fb210) at /usr/src/debug/kdepim-4.8.2/akregator/src/selectioncontroller.cpp:283 #12 0x7f85867630f1 in QMetaObject::activate (sender=0x18312e0, m=, local_signal_index=, argv=0x7fffb2059fa0) at kernel/qobject.cpp:3556 #13 0x7f8585dcd557 in QItemSelectionModel::selectionChanged (this=, _t1=, _t2=) at .moc/release-shared/moc_qitemselectionmodel.cpp:166 #14 0x7f8585dd33b4 in QItemSelectionModel::emitSelectionChanged (this=0x18312e0, newSelection=..., oldSelection=...) at itemviews/qitemselectionmodel.cpp:1544 #15 0x7f8585dd4341 in QItemSelectionModel::select (this=0x18312e0, selection=, command=...) at itemviews/qitemselectionmodel.cpp:1110 #16 0x7f8585dbebd5 in QTreeViewPrivate::select (this=0x916fb0, topIndex=, bottomIndex=, command=...) at itemviews/qtreeview.cpp:3703 #17 0x7f8585dbf912 in QTreeView::setSelection (this=, rect=, command=...) at itemviews/qtreeview.cpp:2317 #18 0x7f8585d7bdea in QAbstractItemView::mousePressEvent (this=0x916f40, event=) at itemviews/qabstractitemview.cpp:1690 #19 0x7f85716bc9d6 in Akregator::ArticleListView::mousePressEvent (this=0x916f40, ev=0x7fffb205b5b0) at /usr/src/debug/kdepim-4.8.2/akregator/src/articlelistview.cpp:400 #20 0x7f85858a5ac9 in QWidget::event (this=0x916f40, event=0x7fffb205b5b0) at kernel/qwidget.cpp:8358 #21 0x7f8585c60fb6 in QFrame::event (this=0x916f40, e=0x7fffb205b5b0) at widgets/qframe.cpp:557 #22 0x7f8585d7557
[Bug 298326] New: Crash after resume/failed to connect
https://bugs.kde.org/show_bug.cgi?id=298326 Bug ID: 298326 Severity: crash Version: 4.8 Priority: NOR CC: kdepim-bugs@kde.org, vkra...@kde.org Assignee: er...@kde.org Summary: Crash after resume/failed to connect Classification: Unclassified OS: Linux Reporter: k...@kitterman.com Hardware: Ubuntu Packages Status: UNCONFIRMED Component: IMAP resource Product: Akonadi Application: akonadi_imap_resource (4.8) KDE Platform Version: 4.8.2 (4.8.2) Qt Version: 4.8.1 Operating System: Linux 3.2.0-23-generic-pae i686 Distribution: Ubuntu precise (development branch) -- Information about the crash: - What I was doing when the application crashed: I had just resumed and got a dialogue that Kmail was unable to connect. I tried to enter the password manually after the resource in question was restarted and it crashed again. The crash can be reproduced some of the time. -- Backtrace: Application: IMAP Account 1 of type IMAP E-Mail Server (akonadi_imap_resource), signal: Segmentation fault Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0xb49c1980 (LWP 7181))] Thread 2 (Thread 0xb2191b40 (LWP 7196)): #0 0xb5457770 in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #1 0xb5457f6f in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0xb54581c1 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb73138e7 in QEventDispatcherGlib::processEvents (this=0xb18bcd08, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0xb72df50d in QEventLoop::processEvents (this=0xb2191240, flags=...) at kernel/qeventloop.cpp:149 #5 0xb72df7a9 in QEventLoop::exec (this=0xb2191240, flags=...) at kernel/qeventloop.cpp:204 #6 0xb71c894c in QThread::exec (this=0x8973da0) at thread/qthread.cpp:501 #7 0xb72bcb5d in QInotifyFileSystemWatcherEngine::run (this=0x8973da0) at io/qfilesystemwatcher_inotify.cpp:248 #8 0xb71cbde0 in QThreadPrivate::start (arg=0x8973da0) at thread/qthread_unix.cpp:298 #9 0xb557ed4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #10 0xb5717ace in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 1 (Thread 0xb49c1980 (LWP 7181)): [KCrash Handler] #7 0x in ?? () #8 0xb72f8fb0 in QObject::connect (sender=0x893d420, signal=0x80acc64 "2stateChanged(KIMAP::Session::State,KIMAP::Session::State)", receiver=0x8939418, method=0x80acc20 "1onSessionStateChanged(KIMAP::Session::State,KIMAP::Session::State)", type=Qt::AutoConnection) at kernel/qobject.cpp:2551 #9 0x0809b1e8 in SessionPool::onPasswordRequestDone (this=0x8939418, resultType=0, password=...) at ../../../resources/imap/sessionpool.cpp:335 #10 0x0809ce10 in SessionPool::qt_static_metacall (_o=0x8939418, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbfcd9254) at ./sessionpool.moc:94 #11 0xb72f76b1 in QMetaObject::activate (sender=0x89340e0, m=0x80aa7e0, local_signal_index=0, argv=0xbfcd9254) at kernel/qobject.cpp:3547 #12 0x0808713f in PasswordRequesterInterface::done (this=0x89340e0, _t1=0, _t2=...) at ./passwordrequesterinterface.moc:118 #13 0x08064b00 in SettingsPasswordRequester::onPasswordRequestCompleted (this=0x89340e0, password=..., userRejected=false) at ../../../resources/imap/settingspasswordrequester.cpp:89 #14 0xb72f76b1 in QMetaObject::activate (sender=0x89371c0, m=0x80a3e20, local_signal_index=0, argv=0xbfcd9374) at kernel/qobject.cpp:3547 #15 0x08063587 in Settings::passwordRequestCompleted (this=0x89371c0, _t1=..., _t2=false) at ./settings.moc:124 #16 0x08063aa6 in Settings::onDialogFinished (this=0x89371c0, result=1) at ../../../resources/imap/settings.cpp:164 #17 0x08063cf9 in Settings::qt_static_metacall (_o=0x89371c0, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0xbfcd94b8) at ./settings.moc:74 #18 0xb72f76b1 in QMetaObject::activate (sender=0x896c548, m=0xb714e2c8, local_signal_index=0, argv=0xbfcd94b8) at kernel/qobject.cpp:3547 #19 0xb6d1e815 in QDialog::finished (this=0x896c548, _t1=1) at .moc/release-shared/moc_qdialog.cpp:153 #20 0xb6d1e909 in QDialog::done (this=0x896c548, r=1) at dialogs/qdialog.cpp:597 #21 0xb6d1d0ea in QDialog::accept (this=0x896c548) at dialogs/qdialog.cpp:612 #22 0xb5cf9f3f in KPasswordDialog::KPasswordDialogPrivate::actuallyAccept (this=0x8967630) at ../../kdeui/dialogs/kpassworddialog.cpp:404 #23 0xb5cfa053 in KPasswordDialog::qt_static_metacall (_o=0x896c548, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0x8974ed8) at ./kpassworddialog.moc:62 #24 0xb72f2c01 in QMetaCallEvent::placeMetaCall (this=0x896d1c0, object=0x896c548) at kernel/qobject.cpp:525 #25 0xb72fbc7b in QObject::event (this=0x896c548, e=0x896d1c0) at kernel/qobject.cpp:1195 #26 0xb6825e62 in QWidget::event (this=0x896c548, event=0x896d1c0) at kernel/qwidget.cpp:8821 #27 0xb67cbed4 in notify_helper (e=0x896d1c0, receiver=0x896c548, this=0x87f2058) at kernel/qapplication.cpp:455
[Bug 273949] Akonadi Resource always seen as readonly
https://bugs.kde.org/show_bug.cgi?id=273949 --- Comment #45 from Simon Bühler --- yep, i reported this nearly a year ago and still nothing - whats the whole point of bugreports then? its a shame that kdepim gets no developer love, some akonadi and nepomuk hype but failing in very basic use cases, unlike -- 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 298322] New: Kmail crash when mark some html mails as read
https://bugs.kde.org/show_bug.cgi?id=298322 Bug ID: 298322 Severity: crash Version: 4.8.2 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kmail crash when mark some html mails as read Classification: Unclassified OS: Linux Reporter: mmes...@gmail.com Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kmail2 Application: kmail (4.8.2) KDE Platform Version: 4.8.2 (4.8.2) Qt Version: 4.8.1 Operating System: Linux 3.2.0-23-generic x86_64 Distribution: Ubuntu precise (development branch) -- Information about the crash: - What I was doing when the application crashed: I was marking several html mails as marked, using a custom key shortcut. The crash can be reproduced some of the time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6a6d0e37c0 (LWP 2723))] Thread 5 (Thread 0x7f6a4aafe700 (LWP 2731)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f6a5f3d9dec in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f6a5f3d9f19 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f6a67f0be9a in start_thread (arg=0x7f6a4aafe700) at pthread_create.c:308 #4 0x7f6a6a43c4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 4 (Thread 0x7f6a4a1fd700 (LWP 2732)): #0 0x7f6a6a430b03 in __GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f6a62ce5ff6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6a62ce6124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6a6adc7426 in QEventDispatcherGlib::processEvents (this=0x7f6a440008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f6a6ad96c82 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f6a6ad96ed7 in QEventLoop::exec (this=0x7f6a4a1fcdc0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f6a6ac95fa7 in QThread::exec (this=) at thread/qthread.cpp:501 #7 0x7f6a6ac98fcb in QThreadPrivate::start (arg=0x1b757e0) at thread/qthread_unix.cpp:298 #8 0x7f6a67f0be9a in start_thread (arg=0x7f6a4a1fd700) at pthread_create.c:308 #9 0x7f6a6a43c4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #10 0x in ?? () Thread 3 (Thread 0x7f6a0316f700 (LWP 2737)): #0 0x7f6a67f0df69 in __pthread_mutex_lock (mutex=0x7f69f4000a60) at pthread_mutex_lock.c:92 #1 0x7f6a62d21561 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6a62ce58c8 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6a62ce5f96 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f6a62ce6124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f6a6adc7426 in QEventDispatcherGlib::processEvents (this=0x7f69f40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0x7f6a6ad96c82 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #7 0x7f6a6ad96ed7 in QEventLoop::exec (this=0x7f6a0316ed90, flags=...) at kernel/qeventloop.cpp:204 #8 0x7f6a6ac95fa7 in QThread::exec (this=) at thread/qthread.cpp:501 #9 0x7f6a6ad769ff in QInotifyFileSystemWatcherEngine::run (this=0x1de6920) at io/qfilesystemwatcher_inotify.cpp:248 #10 0x7f6a6ac98fcb in QThreadPrivate::start (arg=0x1de6920) at thread/qthread_unix.cpp:298 #11 0x7f6a67f0be9a in start_thread (arg=0x7f6a0316f700) at pthread_create.c:308 #12 0x7f6a6a43c4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #13 0x in ?? () Thread 2 (Thread 0x7f6a03fff700 (LWP 10624)): #0 0x7f6a67f0f05d in __pthread_mutex_unlock_usercnt (mutex=, decr=) at pthread_mutex_unlock.c:52 #1 __pthread_mutex_unlock (mutex=0x7f69fc2dabf0) at pthread_mutex_unlock.c:290 #2 0x7f6a62d21591 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6a62ce5713 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f6a62ce5f1b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f6a62ce6124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f6a6adc7426 in QEventDispatcherGlib::processEvents (this=0x7f69fc27d310, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #7 0x7f6a6ad96c82 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #8 0x7f6a6ad96ed7 in QEventLoop::exec (this=0x7f6a03ffed90, flags=...) at kernel/qeventloop.cpp:204 #9 0x7f6a6ac95fa7 in QThread::exec (this=) at thread/qthread.cpp:501 #10 0x7f6a6ad769ff in QInotifyFileSystemWatcherEngine::run (this=0x6
[Bug 298320] New: kontact crashes while deleting email
https://bugs.kde.org/show_bug.cgi?id=298320 Bug ID: 298320 Severity: crash Version: 4.8.1 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: kontact crashes while deleting email Classification: Unclassified OS: Linux Reporter: kdeb...@roeleboel.com Hardware: Fedora RPMs Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.8.1) KDE Platform Version: 4.8.1 (4.8.1) Qt Version: 4.8.0 Operating System: Linux 3.3.1-5.fc16.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: I was deleting a lot of emails, one by one, and kontact crashes after you delete a yet unknown number of emails (I can repeat this every time i delete a lot of messages in succession) The crash can be reproduced some of the time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 82T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7f33277e4840 (LWP 1928))] Thread 9 (Thread 0x7f331b08e700 (LWP 1936)): #0 0x00390cebd7bd in nanosleep () at ../sysdeps/unix/syscall-template.S:82 #1 0x00390cebd65c in __sleep (seconds=0) at ../sysdeps/unix/sysv/linux/sleep.c:138 #2 0x00319c1b8547 in WTF::TCMalloc_PageHeap::scavengerThread (this=0x319cb7cc20) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:2499 #3 0x00319c1b8819 in WTF::TCMalloc_PageHeap::runScavengerThread (context=) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:1618 #4 0x00390d607d90 in start_thread (arg=0x7f331b08e700) at pthread_create.c:309 #5 0x00390cef0f5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 8 (Thread 0x7f331a77d700 (LWP 1938)): #0 0x00390cee85c3 in __GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x00390ee44fd8 in g_main_context_poll (n_fds=1, fds=0x7f33140013e0, priority=, timeout=8855, context=0x7f33140009a0) at gmain.c:3402 #2 g_main_context_iterate (context=0x7f33140009a0, block=, dispatch=1, self=) at gmain.c:3084 #3 0x00390ee4549c in g_main_context_iteration (context=0x7f33140009a0, may_block=1) at gmain.c:3152 #4 0x00327ffa7dc6 in QEventDispatcherGlib::processEvents (this=0x7f33140008c0, flags=) at kernel/qeventdispatcher_glib.cpp:426 #5 0x00327ff78182 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #6 0x00327ff783d7 in QEventLoop::exec (this=0x7f331a77cd40, flags=...) at kernel/qeventloop.cpp:204 #7 0x00327fe78b27 in QThread::exec (this=) at thread/qthread.cpp:501 #8 0x00327fe7bb6b in QThreadPrivate::start (arg=0xba1ce0) at thread/qthread_unix.cpp:298 #9 0x00390d607d90 in start_thread (arg=0x7f331a77d700) at pthread_create.c:309 #10 0x00390cef0f5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 7 (Thread 0x7f32c234d700 (LWP 2510)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:216 #1 0x00327fe7bfdf in wait (time=3, this=0x141d0e0) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=, mutex=0x141d088, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x00327fe6f5af in QThreadPoolThread::run (this=0x142f550) at concurrent/qthreadpool.cpp:141 #4 0x00327fe7bb6b in QThreadPrivate::start (arg=0x142f550) at thread/qthread_unix.cpp:298 #5 0x00390d607d90 in start_thread (arg=0x7f32c234d700) at pthread_create.c:309 #6 0x00390cef0f5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 6 (Thread 0x7f32bbfff700 (LWP 2515)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:216 #1 0x00327fe7bfdf in wait (time=3, this=0x23dcc10) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=, mutex=0x23dcb88, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x00327fe6f5af in QThreadPoolThread::run (this=0x23ddb00) at concurrent/qthreadpool.cpp:141 #4 0x00327fe7bb6b in QThreadPrivate::start (arg=0x23ddb00) at thread/qthread_unix.cpp:298 #5 0x00390d607d90 in start_thread (arg=0x7f32bbfff700) at pthread_create.c:309 #6 0x00390cef0f5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 5 (Thread 0x7f32bb7fe700 (LWP 2548)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:216 #1 0x00327fe7bfdf in wait (time=3, this=0x7f32c4002510) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=, mutex=0x7f32c40037f8, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x00327fe6f5af in QThreadPoolThread::run (this=0x7f32a8011a20) at concurrent/qthreadpool.cpp:141 #4 0x00327fe7bb6b in QThreadPrivate::start (arg=0x7f32a8011a20) at thread/qthread_unix.cpp:298 #5 0x0
[Bug 273949] Akonadi Resource always seen as readonly
https://bugs.kde.org/show_bug.cgi?id=273949 Eggert Ehmke changed: What|Removed |Added CC||eggert.eh...@berlin.de --- Comment #44 from Eggert Ehmke --- I have 4.8.2 (Gentoo) and followed the above advices. Still no success. This is ridiculous. -- 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 298314] [kcm] database driver dropdown menu always lists mysql and postgresql regardless of what backends are actually installed
https://bugs.kde.org/show_bug.cgi?id=298314 JR changed: What|Removed |Added CC||zor...@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 298314] [kcm] database driver dropdown menu always lists mysql and postgresql regardless of what backends are actually installed
https://bugs.kde.org/show_bug.cgi?id=298314 --- Comment #1 from JR --- Created attachment 70458 --> https://bugs.kde.org/attachment.cgi?id=70458&action=edit Screenshot showing how the kcm is not aware of installed backends -- 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 298314] New: [kcm] database driver dropdown menu always lists mysql and postgresql regardless of what backends are actually installed
https://bugs.kde.org/show_bug.cgi?id=298314
Bug ID: 298314
Severity: normal
Version: unspecified
Priority: NOR
Assignee: kdepim-bugs@kde.org
Summary: [kcm] database driver dropdown menu always lists mysql
and postgresql regardless of what backends are
actually installed
Classification: Unclassified
OS: Linux
Reporter: zor...@gmail.com
Hardware: Ubuntu Packages
Status: UNCONFIRMED
Component: general
Product: Akonadi
Kubuntu 12.04b amd64, KDE 4.8.2 packages from Kubuntu PPAs.
In the Server Configuration tab in the Akonadi kcm, there's a dropdown list
where you can choose what backend it should use to store its database. In the
(K)ubuntu repositories, there are packages for MySQL, PostgreSQL, SQLite and
ODBC backends (akonadi-server-{mysql,postgresql,sqlite,odbc}).
The kcm always offers to only pick between mysql and postgresql, regardless of
what backends are actually available. This is even if the postgresql backend is
not installed at all. Other backends are never listed.
Reproducible: Always
Steps to Reproduce:
1. Install the SQLite backend
2. Remove the PostgreSQL backend
3. kbuildsycoca4
4. kcmshell4 akonadi
5. Open Server Configuration tab and view the Database driver alternatives
Actual Results:
6. The drop-down menu lists MySQL and PostgreSQL, despite the latter not being
installed at all and without mention of SQLite
Expected Results:
6. The drop-down menu should list the installed MySQL and SQLite backends
I tested this on two different machines and on a new user. Also worthy of
mention is that Akonadi is packaged in Kubuntu with the mysql backend as a hard
dependency.
I did manage to get it to switch to sqlite by manually modifying the [%General]
section of ~/.config/akonadi/akonadiserverrc;
>[%General]
>Driver=QSQLITE3
Opening the kcm now the Database driver menu shows as having an empty
selection, and expanding the menu it still lists mysql and postgresql.
--
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 298313] New: kontact crash when re-opening mail "stuck" in outbox
https://bugs.kde.org/show_bug.cgi?id=298313 Bug ID: 298313 Severity: crash Version: 4.8.2 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: kontact crash when re-opening mail "stuck" in outbox Classification: Unclassified OS: Linux Reporter: dilfri...@gentoo.org Hardware: Compiled Sources Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.8.2) KDE Platform Version: 4.8.2 (4.8.2) (Compiled from sources) Qt Version: 4.8.1 Operating System: Linux 3.2.2-hardened-r1 x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: Tried to send an e-mail to many recipients. One of the addresses was incorrect, and the mail server refused it, so it remained in the outbox. Doubleclicked on it to edit, and kontact crashed. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0x360b118c760 (LWP 31583))] Thread 4 (Thread 0x3609690b700 (LWP 31584)): #0 pthread_cond_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x0360ad77d8a4 in scavengerThread (this=0x360ae12aec0) at wtf/FastMalloc.cpp:2495 #2 WTF::TCMalloc_PageHeap::runScavengerThread (context=0x360ae12aec0) at wtf/FastMalloc.cpp:1618 #3 0x0360a8b21c5c in start_thread (arg=0x3609690b700) at pthread_create.c:301 #4 0x0360ae4889cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 3 (Thread 0x3609600a700 (LWP 31585)): #0 0x0360ae47fd13 in *__GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x0360a7947028 in g_main_context_poll (n_fds=1, fds=0x360900021f0, timeout=-1, context=0x3609970, priority=) at gmain.c:3402 #2 g_main_context_iterate (context=0x3609970, block=1, dispatch=1, self=) at gmain.c:3084 #3 0x0360a7947531 in g_main_context_iteration (context=0x3609970, may_block=1) at gmain.c:3152 #4 0x0360af9f9e7f in QEventDispatcherGlib::processEvents (this=0x3c1be0d020, flags=) at kernel/qeventdispatcher_glib.cpp:424 #5 0x0360af9c1cd2 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #6 0x0360af9c20b5 in QEventLoop::exec (this=0x36096009e10, flags=...) at kernel/qeventloop.cpp:204 #7 0x0360af89c5f8 in QThread::exec (this=) at thread/qthread.cpp:501 #8 0x0360af89f503 in QThreadPrivate::start (arg=0x3c1be0cb40) at thread/qthread_unix.cpp:298 #9 0x0360a8b21c5c in start_thread (arg=0x3609600a700) at pthread_create.c:301 #10 0x0360ae4889cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 2 (Thread 0x36082606700 (LWP 4010)): #0 0x0360ae482263 in select () at ../sysdeps/unix/syscall-template.S:82 #1 0x0360af99a10c in QProcessManager::run (this=0x360afd35d40) at io/qprocess_unix.cpp:245 #2 0x0360af89f503 in QThreadPrivate::start (arg=0x360afd35d40) at thread/qthread_unix.cpp:298 #3 0x0360a8b21c5c in start_thread (arg=0x36082606700) at pthread_create.c:301 #4 0x0360ae4889cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 1 (Thread 0x360b118c760 (LWP 31583)): [KCrash Handler] #6 QCoreApplication::postEvent (receiver=0x3c1e43ffb0, event=0x3c1e5b3370, priority=0) at kernel/qcoreapplication.cpp:1273 #7 0x0360af9dbf56 in QObject::event (this=0x3c1e43ffb0, e=) at kernel/qobject.cpp:1195 #8 0x0360aec3ca64 in QApplicationPrivate::notify_helper (this=0x3c1bc3ff70, receiver=0x3c1e43ffb0, e=0x3c1f97fa50) at kernel/qapplication.cpp:4554 #9 0x0360aec41c2b in QApplication::notify (this=, receiver=0x3c1e43ffb0, e=0x3c1f97fa50) at kernel/qapplication.cpp:4415 #10 0x0360b04ecb66 in KApplication::notify (this=0x3cb08df6240, receiver=0x3c1e43ffb0, event=0x3c1f97fa50) at /opt/virtual/tmp-portage/portage/kde-base/kdelibs-4.8.2/work/kdelibs-4.8.2/kdeui/kernel/kapplication.cpp:311 #11 0x0360af9c31eb in QCoreApplication::notifyInternal (this=0x3cb08df6240, receiver=0x3c1e43ffb0, event=0x3c1f97fa50) at kernel/qcoreapplication.cpp:876 #12 0x0360af9c70a7 in sendEvent (event=0x3c1f97fa50, receiver=0x3c1e43ffb0) at kernel/qcoreapplication.h:231 #13 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x3c1bc0bb40) at kernel/qcoreapplication.cpp:1500 #14 0x0360af9f9c87 in sendPostedEvents () at kernel/qcoreapplication.h:236 #15 postEventSourceDispatch (s=) at kernel/qeventdispatcher_glib.cpp:279 #16 0x0360a7946ada in g_main_dispatch (context=0x3c1bc428e0) at gmain.c:2441 #17 g_main_context_dispatch (context=0x3c1bc428e0) at gmain.c:3011 #18 0x0360a7947308 in g_main_context_iterate (context=0x3c1bc428e0, block=1, dispatch=1, self=) at gmain.c:3089 #19 0x0360a7947531 in g_main_context_iteration (context=0x3c1bc428e0, may_block=1) at gmain.c:3152 #20 0x0360af9f9e7f in QEventDispatcherGlib::processEvents (this=0x3c1bc
[Bug 259949] Kmail does not use all addressbooks for autocompletion
https://bugs.kde.org/show_bug.cgi?id=259949 --- Comment #97 from Joachim Wilke --- Chakra Linux with KMail 4.8.2 and akonadi 1.7.2. After upgrading akonadi from 1.7.1 to 1.7.2 and purging the nepomuk database in ~/.kde4/share/apps/nepomuk address completion works like described in comment #96. Also searching messages in KMail works now. In System Settings -> Configure KDE Resources I have *not* set up akonadi-resource as the default contact resource. -- 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 298308] New: rep; yed flag(icon) not set on server but forwarded is set correctly
https://bugs.kde.org/show_bug.cgi?id=298308 Bug ID: 298308 Severity: normal Version: unspecified Priority: NOR CC: kdepim-bugs@kde.org, vkra...@kde.org Assignee: er...@kde.org Summary: rep;yed flag(icon) not set on server but forwarded is set correctly Classification: Unclassified OS: Linux Reporter: simion...@gmail.com Hardware: Ubuntu Packages Status: UNCONFIRMED Component: IMAP resource Product: Akonadi If i reply to an email and then check the email from thunderbird or other email app on other computer the reply flag is missing from the email. Forward works fine. Reproducible: Always Steps to Reproduce: 1.Reply to an email 2.Login from other computer or from Thunderbird or other Mail application 3.Check if you can see that a reply was sent to that previous 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 277770] KMail2 is slow when accessing messages in folder
https://bugs.kde.org/show_bug.cgi?id=20 --- Comment #20 from Alexandre Bonneau --- I don't know exactly what I did, but after fiddling with the folder options I talked about in the previous comment, the slowness has disappeared (again). It now takes between instant and ~2 seconds to display any mail content, even in the big folders. Perhaps a configuration file hasn't been correctly written during update ? My options are the same as before, but without any problem now. I hope that answer could help people experiencing this kind of 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 298128] Kontact crashes after crash of korgac
https://bugs.kde.org/show_bug.cgi?id=298128 Christophe Giboudeaux changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christophe Giboudeaux --- *** This bug has been marked as a duplicate of bug 272236 *** -- 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 246027] Kmail stoped with: KMail encountered a fatal error and will terminate now. The error was: Timeout trying to get lock."
https://bugs.kde.org/show_bug.cgi?id=246027 --- Comment #14 from Christophe Giboudeaux --- tried again later to wipe everything again, and this time, it worked flawlessly. The only (notable) difference between both experiments is the local folders behaviour. On the first attempt, the 'Draft' folder wasn't created. -- 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 298282] Bug with a feeds
https://bugs.kde.org/show_bug.cgi?id=298282 --- Comment #2 from BRULE Herman --- I use akregator 4.8.2 into KDE 4.8.2. All other feeds work perfectly. (I have 200 feeds + or -). -- 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 298282] Bug with a feeds
https://bugs.kde.org/show_bug.cgi?id=298282 --- Comment #1 from Christophe Giboudeaux --- Works perfectly here. Which akregator version do you use ? -- 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 273949] Akonadi Resource always seen as readonly
https://bugs.kde.org/show_bug.cgi?id=273949 --- Comment #43 from Robert Riemann --- Has this been resolved in 4.8.2? I'm still having problems with my contacts resources. -- 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 296896] KMail crashes when clicking a mail
https://bugs.kde.org/show_bug.cgi?id=296896 Robert Riemann changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from Robert Riemann --- Seems to be resolved in KDE 4.8.2. -- 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 297615] Akonadi asks for wallet password even though no kmail2 has not been started
https://bugs.kde.org/show_bug.cgi?id=297615 --- Comment #2 from Paul Gover --- (In reply to comment #0) I said: > ... > It may be irrelevant, but something strange is also happening related to the > chromium web browser. I let it store its web passwords in the KDE wallet > (it creates a binary store, called "Chrome form data"). If chromium is > running before I start kmail2, and if chromium has already asked for the > wallet password, then starting kmail2 does NOT ask for a wallet password, > and kmail2 happily retrieves my email. I presume chromium is doing > something naughty here, and not scoping its use of the wallet properly. > ... It's been pointed out to me that this behaviour can be changed by editing the [Auto Allow] stanza in ~/.kde4/share/config/kwalletrc, and I'd probably caused kwallet to include "chromium" in that stanza some time ago. So the paragraph above was indeed irrelevant. The main bug described remains. -- 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 258171] Annoyed by 'Nepomuk Indexing Disabled - Akonadi Agent' message
https://bugs.kde.org/show_bug.cgi?id=258171 Peter Ambroz changed: What|Removed |Added CC||c...@gjh.sk --- Comment #76 from Peter Ambroz --- OK, this just can't be responsibility of one developer, who thinks that we must use nepomuk. bug is not fixed. fixing of this bug involves an option for user to disable notifications. I don't want to disable apps. I want to disable the notification. We aren't using MS windows, which forces users to do everything it says, are we? Linux should be about choices. I don't mean "choose gnome if you don't like nepomuk notifications". I mean "choose not to receive notifications and continue to use otherwise very fine K Destkop Environment".. consider this please. -- 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 298283] New: Kmail segfault when closed after a new mail account was added(?).
https://bugs.kde.org/show_bug.cgi?id=298283 Bug ID: 298283 Severity: crash Version: 4.8.1 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kmail segfault when closed after a new mail account was added(?). Classification: Unclassified OS: Linux Reporter: marekpasnikow...@interia.eu Hardware: Fedora RPMs Status: UNCONFIRMED Component: general Product: kmail2 Application: kmail (4.8.1) KDE Platform Version: 4.8.1 (4.8.1) Qt Version: 4.8.0 Operating System: Linux 3.3.1-5.fc16.i686.PAE i686 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: I closed KMail through the menu option. Earlier I had added a new mail account. - Custom settings of the application: The added mail domain is a custom one. This was my first attempt to create my own mailbox, I am not even sure, if all options were set right, thus the bug may sit in the wrong configuration. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib/libthread_db.so.1". [Current thread is 1 (Thread 0xb7726780 (LWP 9860))] Thread 3 (Thread 0xb38ffb40 (LWP 12894)): #0 0xb7770424 in __kernel_vsyscall () #1 0x4317485c in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i486/pthread_cond_wait.S:172 #2 0x47f919a3 in WTF::TCMalloc_PageHeap::scavengerThread (this=0x486b6fe0) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:2495 #3 0x47f91ac0 in WTF::TCMalloc_PageHeap::runScavengerThread (context=0x486b6fe0) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:1618 #4 0x43170cd3 in start_thread (arg=0xb38ffb40) at pthread_create.c:309 #5 0x430a6a2e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:133 Thread 2 (Thread 0xb2ffeb40 (LWP 12895)): #0 0x431d7001 in __GI_clock_gettime (clock_id=1, tp=0xb2ffdfb8) at ../sysdeps/unix/clock_gettime.c:116 #1 0x4201ee06 in do_gettime (frac=0xb2ffdfb0, sec=0xb2ffdfa8) at tools/qelapsedtimer_unix.cpp:123 #2 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #3 0x42108bf7 in QTimerInfoList::updateCurrentTime (this=0xb2601abc) at kernel/qeventdispatcher_unix.cpp:343 #4 0x42108f5b in QTimerInfoList::timerWait (this=0xb2601abc, tm=...) at kernel/qeventdispatcher_unix.cpp:450 #5 0x421077a3 in timerSourcePrepareHelper (src=, timeout=0xb2ffe09c) at kernel/qeventdispatcher_glib.cpp:136 #6 0x433d8c4c in g_main_context_prepare (context=0xb26004e0, priority=0xb2ffe0f8) at gmain.c:2762 #7 0x433d9a08 in g_main_context_iterate (context=0xb26004e0, block=1, dispatch=1, self=0xb2600d70) at gmain.c:3069 #8 0x433da01f in g_main_context_iteration (context=0xb26004e0, may_block=1) at gmain.c:3152 #9 0x42108317 in QEventDispatcherGlib::processEvents (this=0xb2600468, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #10 0x420d44ee in QEventLoop::processEvents (this=0xb2ffe230, flags=...) at kernel/qeventloop.cpp:149 #11 0x420d4799 in QEventLoop::exec (this=0xb2ffe230, flags=...) at kernel/qeventloop.cpp:204 #12 0x41fbcb2c in QThread::exec (this=0xa2ab9b8) at thread/qthread.cpp:501 #13 0x41fbcc1c in QThread::run (this=0xa2ab9b8) at thread/qthread.cpp:568 #14 0x41fc00b1 in QThreadPrivate::start (arg=0xa2ab9b8) at thread/qthread_unix.cpp:298 #15 0x43170cd3 in start_thread (arg=0xb2ffeb40) at pthread_create.c:309 #16 0x430a6a2e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:133 Thread 1 (Thread 0xb7726780 (LWP 9860)): [KCrash Handler] #7 MailTransport::Transport::setPassword (this=0x995c890, passwd=...) at /usr/src/debug/kdepimlibs-4.8.1/mailtransport/transport.cpp:75 #8 0x44eef4d1 in MailTransport::Transport::readPassword (this=0x995c890) at /usr/src/debug/kdepimlibs-4.8.1/mailtransport/transport.cpp:318 #9 0x44eefd1c in qt_static_metacall (_id=0, _o=0x995c890, _c=, _a=) at /usr/src/debug/kdepimlibs-4.8.1/i686-redhat-linux-gnu/mailtransport/transport.moc:49 #10 MailTransport::Transport::qt_static_metacall (_o=0x995c890, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x995c178) at /usr/src/debug/kdepimlibs-4.8.1/i686-redhat-linux-gnu/mailtransport/transport.moc:43 #11 0x420e7752 in QMetaCallEvent::placeMetaCall (this=0x995c0c8, object=0x995c890) at kernel/qobject.cpp:525 #12 0x420f042b in QObject::event (this=0x995c890, e=0x995c0c8) at kernel/qobject.cpp:1195 #13 0x41155134 in notify_helper (e=0x995c0c8, receiver=0x995c890, this=0x9781a68) at kernel/qapplication.cpp:4550 #14 QApplicationPrivate::notify_helper (this=0x9781a68, receiver=0x995c890, e=0x995c0c8) at kernel/qapplication.cpp:4522 #15 0x4115a5d3 in QApplication::notify (this=0x995c0c8, receiver=0x995c890, e=0x995c0c8) at kernel/qapplication.cpp:4279 #16 0x42729122 in KApplication::notify (this=0xbff5654c, receiver=0x995c890, event=0x995c0c8) at /usr/src/debug/kdelibs-4.8.1/kdeui/kernel/kapplication.cpp:311 #17 0x420d55fe in QCoreApplication::notifyInternal (this=0x
[Bug 298280] Setting folder properties results in "Error while writing annotations for (foldername), server replied NO Permission"
https://bugs.kde.org/show_bug.cgi?id=298280 Mathias Homann changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #1 from Mathias Homann --- Updating the imap server to a recent verion solved this. -- 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 298282] New: Bug with a feeds
https://bugs.kde.org/show_bug.cgi?id=298282 Bug ID: 298282 Severity: normal URL: http://www.minecraftforum.net/rss/writ/1-news/ Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Bug with a feeds Classification: Unclassified OS: Linux Reporter: alpha_one_...@first-world.info Hardware: Other Status: UNCONFIRMED Component: feed parser Product: akregator Hello, with this feeds: http://www.minecraftforum.net/rss/writ/1-news/ I need restart akregator to fetch the feed, and it feetch as double entry. Can you fix that's? Thanks Reproducible: Always -- 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 298280] New: Setting folder properties results in "Error while writing annotations for (foldername), server replied NO Permission"
https://bugs.kde.org/show_bug.cgi?id=298280 Bug ID: 298280 Severity: normal Version: 4.8.2 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Setting folder properties results in "Error while writing annotations for (foldername), server replied NO Permission" Classification: Unclassified OS: Linux Reporter: ad...@eregion.de Hardware: openSUSE RPMs Status: UNCONFIRMED Component: folders Product: kmail2 I'm trying to set some folder properties in kmail2, and I get popups saying the following: "ad...@eregion.de: Fehler beim Schreiben einiger Annotationen für "buildservice" auf dem IMAP-Server. SetAnnotation failed, server replied: A000490 NO Permission denied". Is this from akonadis imap-like engine thing or from the actual imap server? Reproducible: Always Steps to Reproduce: 1. try to set folder properties Actual Results: error message like described above Expected Results: properties are properly stored the folders also have lost their "identity" settings. -- 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 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 CC||mon...@kde.org Component|general |general Version|1.13.5 |4.9 pre Product|kmail |kmail2 --- Comment #1 from Laurent Montel --- put in kmail2. I like this feature -- 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
