[kontact] [Bug 187303] Sorting of events is not in order
https://bugs.kde.org/show_bug.cgi?id=187303 Ritesh Raj Sarraf changed: What|Removed |Added Resolution|--- |WORKSFORME Status|CONFIRMED |RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[knode] [Bug 128848] KNode doesn't detect the signature delimiter when replying to GPG signed messages
https://bugs.kde.org/show_bug.cgi?id=128848 Ritesh Raj Sarraf changed: What|Removed |Added Resolution|--- |WORKSFORME Status|CONFIRMED |RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 206611] consistent shortcut interface for all pim apps
https://bugs.kde.org/show_bug.cgi?id=206611 Ritesh Raj Sarraf changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[knode] [Bug 188838] add newsgroup categorization under folders
https://bugs.kde.org/show_bug.cgi?id=188838 Ritesh Raj Sarraf changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[knode] [Bug 123808] knode message reply notification
https://bugs.kde.org/show_bug.cgi?id=123808 Ritesh Raj Sarraf changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[kdepimlibs] [Bug 177330] all rss applications use their own storage
https://bugs.kde.org/show_bug.cgi?id=177330 Ritesh Raj Sarraf changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 187303] Sorting of events is not in order
https://bugs.kde.org/show_bug.cgi?id=187303 --- Comment #5 from Ritesh Raj Sarraf --- (In reply to Denis Kurz from comment #4) > Actually, so do I, in version 5.3.2. Thanks for your feedback, Carioca 7 years in getting a bug confirmed. @Denis Kurz, your comment made this bug become confirmed. Now, was it you who confirmed it? Or its just that multiple users commenting on the bug auto confirmed it ? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 38711] Threads with unread messages should be highlighted
https://bugs.kde.org/show_bug.cgi?id=38711 --- Comment #20 from Ritesh Raj Sarraf --- (In reply to comment #19) > Thank you for your feature request. Kmail1 is currently unmaintained so we > are closing all wishes. Please feel free to reopen a feature request for > Kmail2 if it has not already been implemented. > Thank you for your understanding. This feature request is 10 yrs old and was never closed as invalid. That means, it is a valid request. Wouldn't it make sense to carry forward such valid requests to kmail2, instead of closing? -- 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 222757] kmail threading is broken
https://bugs.kde.org/show_bug.cgi?id=222757 --- Comment #6 from Ritesh Raj Sarraf 2011-12-14 06:18:30 --- Yes, that could have been the cause. My environment does have Exchange also. Thanks for the explanation. I don't have the permissions to change this bugzilla to a feature request, so I'll hope the kdepim folks would do it. -- 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 273949] Akonadi Resource always seen as readonly
https://bugs.kde.org/show_bug.cgi?id=273949 --- Comment #8 from Ritesh Raj Sarraf 2011-07-30 15:53:23 --- I badly wanted to play with kdepim and kmail2. The Maildir akonadi resource works. So I went ahead and added 5000 mails to the Maildir resource. Very disappointed to say that the performance is so terrible that you will find kmail2 completely unusable. And this is the Maildir/ resource. Don't expect much from the D[IMAP] resource. Devs: Is it usable for you? From what I concluded, it might take a long time to be in a good shape to be called usable. -- 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 273949] Akonadi Resource always seen as readonly
https://bugs.kde.org/show_bug.cgi?id=273949 Ritesh Raj Sarraf changed: What|Removed |Added CC||r...@researchut.com --- Comment #5 from Ritesh Raj Sarraf 2011-07-15 17:25:48 --- same issue. read-only akonadi resources. -- 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 247642] Plasma crash after adding a calendar event [null KCal::IncidenceBase::uid, Akonadi::Calendar::Private::removeItemFromMaps, Akonadi::Calendar::Private::itemsRemoved]
https://bugs.kde.org/show_bug.cgi?id=247642 --- Comment #19 from Ritesh Raj Sarraf 2010-12-13 08:24:54 --- Created an attachment (id=54483) --> (http://bugs.kde.org/attachment.cgi?id=54483) New crash information added by DrKonqi plasma-desktop (0.3) on KDE Platform 4.5.3 (KDE 4.5.3) using Qt 4.6.3 - What I was doing when the application crashed: Every morning I walke up and see that plasma has been reported as crashed -- Backtrace (Reduced): #6 QString (this=0x0) at /usr/include/qt4/QtCore/qstring.h:714 #7 KCal::IncidenceBase::uid (this=0x0) at ../../kcal/incidencebase.cpp:185 #8 0x7fdb20ce7a89 in Akonadi::Calendar::Private::removeItemFromMaps (this=, item=) at ../../../../../plasma/generic/dataengines/calendar/akonadi/calendar.cpp:424 #9 0x7fdb20ce89b3 in Akonadi::Calendar::Private::itemsRemoved (this=0x2fcc4a0, items=) at ../../../../../plasma/generic/dataengines/calendar/akonadi/calendar.cpp:453 #10 0x7fdb20ce9c36 in Akonadi::Calendar::Private::rowsAboutToBeRemoved (this=0x2fcc4a0, parent=, start=, end=) at ../../../../../plasma/generic/dataengines/calendar/akonadi/calendar.cpp:104 -- 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 247642] Plasma crash after adding a calendar event [null KCal::IncidenceBase::uid, Akonadi::Calendar::Private::removeItemFromMaps, Akonadi::Calendar::Private::itemsRemoved]
https://bugs.kde.org/show_bug.cgi?id=247642 Ritesh Raj Sarraf changed: What|Removed |Added CC||r...@researchut.com -- 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 255406] Kontact crashes when selecting Show Icons Only in sidebar
https://bugs.kde.org/show_bug.cgi?id=255406 --- Comment #1 from Ritesh Raj Sarraf 2010-10-28 08:34:50 --- Created an attachment (id=52932) --> (http://bugs.kde.org/attachment.cgi?id=52932) New crash information added by DrKonqi kontact (4.4.6) on KDE Platform 4.5.2 (KDE 4.5.2) using Qt 4.7.0 - What I was doing when the application crashed: Right click on Icons to select "Show Icons only" and kontact crashed. -- Backtrace (Reduced): #6 QModelIndex (this=0xaae3e0, child=...) at ../../include/QtCore/../../src/corelib/kernel/qabstractitemmodel.h:65 #7 QSortFilterProxyModel::parent (this=0xaae3e0, child=...) at itemviews/qsortfilterproxymodel.cpp:1656 #8 0x7facc36cceb3 in parent (this=) at kernel/qabstractitemmodel.h:389 #9 QPersistentModelIndex::parent (this=) at kernel/qabstractitemmodel.cpp:347 #10 0x7facc2fdd12f in parent (this=0xaaf840, index=...) at itemviews/qitemselectionmodel.h:78 -- 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 255406] Kontact crashes when selecting Show Icons Only in sidebar
https://bugs.kde.org/show_bug.cgi?id=255406 Ritesh Raj Sarraf changed: What|Removed |Added CC||r...@researchut.com -- 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 223245] KMail crash dragging multiple emails from one folder to another [MessageList::Core::Item::parent, MessageList::Core::Model::index, MessageList::Core::Item::parent, QModelIndex::parent]
https://bugs.kde.org/show_bug.cgi?id=223245 Ritesh Raj Sarraf changed: What|Removed |Added CC||r...@researchut.com -- 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 223245] KMail crash dragging multiple emails from one folder to another [MessageList::Core::Item::parent, MessageList::Core::Model::index, MessageList::Core::Item::parent, QModelIndex::parent]
https://bugs.kde.org/show_bug.cgi?id=223245 --- Comment #26 from Ritesh Raj Sarraf 2010-08-20 12:47:06 --- Created an attachment (id=50772) --> (http://bugs.kde.org/attachment.cgi?id=50772) New crash information added by DrKonqi the crash tirggered when deleting some of the old emails -- 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 247126] New: korganizer crash on exporting iCalendar
https://bugs.kde.org/show_bug.cgi?id=247126 Summary: korganizer crash on exporting iCalendar Product: kontact Version: 4.4.5 Platform: Debian testing OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: r...@researchut.com Application: kontact (4.4.5) KDE Platform Version: 4.4.5 (KDE 4.4.5) Qt Version: 4.6.3 Operating System: Linux 2.6.35-trunk-amd64 x86_64 Distribution: Debian GNU/Linux testing (squeeze) -- Information about the crash: korganizer crashed when trying to export a calendar item to send as an iCalendar The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0x7f890073b760 (LWP 18747))] Thread 2 (Thread 0x7f88d3fff710 (LWP 18794)): #0 0x7f88fd7cd8b3 in select () at ../sysdeps/unix/syscall-template.S:82 #1 0x7f88febade2d in QProcessManager::run (this=0x7f88feee9920) at io/qprocess_unix.cpp:245 #2 0x7f88feae2e35 in QThreadPrivate::start (arg=0x7f88feee9920) at thread/qthread_unix.cpp:248 #3 0x7f88f6db48ba in start_thread (arg=) at pthread_create.c:300 #4 0x7f88fd7d401d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 1 (Thread 0x7f890073b760 (LWP 18747)): [KCrash Handler] #5 memcpy () at ../sysdeps/x86_64/memcpy.S:161 #6 0x7f88feb276cb in replaceArgEscapes (s=, d=, field_width=, arg=, larg=, fillChar=...) at tools/qstring.cpp:6259 #7 0x7f88feb292ed in QString::arg (this=0x7fff637b2590, a=..., fieldWidth=0, fillChar=...) at tools/qstring.cpp:6319 #8 0x7f88ff09ab7e in KLocalizedString::subs (this=, a=..., fieldWidth=0, fillChar=) at ../../kdecore/localization/klocalizedstring.cpp:913 #9 0x7f88fac52603 in i18n (this=0x7fff637b2a60, event=0x5803f00) at /usr/include/klocalizedstring.h:613 #10 KCal::IncidenceFormatter::MailBodyVisitor::visit (this=0x7fff637b2a60, event=0x5803f00) at ../../kcal/incidenceformatter.cpp:2613 #11 0x7f88fac4bc16 in KCal::IncidenceFormatter::MailBodyVisitor::act (incidence=0x5803f00, spec=) at ../../kcal/incidenceformatter.cpp:2563 #12 KCal::IncidenceFormatter::mailBodyStr (incidence=0x5803f00, spec=) at ../../kcal/incidenceformatter.cpp:2692 #13 0x7f88d82fa85a in KOMailClient::mailTo (this=, incidence=0x5803f00, identity=, from=, bccMe=false, recipients=..., attachment=..., useSendmail=false) at ../../korganizer/komailclient.cpp:167 #14 0x7f88db508f0b in CalendarView::schedule_forward (this=0x42a8190, incidence=0x5803f00) at ../../korganizer/calendarview.cpp:1667 #15 0x7f88db50b859 in CalendarView::qt_metacall (this=0x42a8190, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff637b3090) at ./calendarview.moc:560 #16 0x7f88febe5346 in QMetaObject::activate (sender=0x4e7b630, m=, local_signal_index=, argv=0xfffa) at kernel/qobject.cpp:3295 #17 0x7f88fdf6c132 in QAction::triggered (this=0x7f884fa0402a, _t1=false) at .moc/release-shared/moc_qaction.cpp:263 #18 0x7f88fdf6e1ab in QAction::activate (this=0x4e7b630, event=) at kernel/qaction.cpp:1255 #19 0x7f88db54d3de in QAction::trigger (this=0x8cf9f60) at /usr/include/qt4/QtGui/qaction.h:218 #20 KOEventPopupMenu::forward (this=0x8cf9f60) at ../../korganizer/koeventpopupmenu.cpp:257 #21 0x7f88db54d68a in KOEventPopupMenu::qt_metacall (this=0x8cf9f60, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff637b3270) at ./koeventpopupmenu.moc:142 #22 0x7f88febe5346 in QMetaObject::activate (sender=0x5386a50, m=, local_signal_index=, argv=0xfffa) at kernel/qobject.cpp:3295 #23 0x7f88fdf6c132 in QAction::triggered (this=0x7f884fa0402a, _t1=false) at .moc/release-shared/moc_qaction.cpp:263 #24 0x7f88fdf6e1ab in QAction::activate (this=0x5386a50, event=) at kernel/qaction.cpp:1255 #25 0x7f88fe3ad981 in QMenuPrivate::activateCausedStack (this=, causedStack=..., action=0x5386a50, action_e=QAction::Trigger, self=true) at widgets/qmenu.cpp:1002 #26 0x7f88fe3b3512 in QMenuPrivate::activateAction (this=0x8cf9fe0, action=0x5386a50, action_e=QAction::Trigger, self=) at widgets/qmenu.cpp:1094 #27 0x7f88fdfc8602 in QWidget::event (this=0x8cf9f60, event=0x7fff637b3ea0) at kernel/qwidget.cpp:8044 #28 0x7f88fe3b570b in QMenu::event (this=0x8cf9f60, e=0x7fff637b3ea0) at widgets/qmenu.cpp:2421 #29 0x7f88fdf7232c in QApplicationPrivate::notify_helper (this=0x114cd70, receiver=0x8cf9f60, e=0x7fff637b3ea0) at kernel/qapplication.cpp:4302 #30 0x7f88fdf78fdb in QApplication::notify (this=0x7fff637b4a00, receiver=0x8cf9f60, e=0x7fff637b3ea0) at kernel/qapplication.cpp:3867 #31 0x7f88ff5ba836 in KApplication::notify (this=0x7fff637b4a00, receiver=0x8cf9f60, event=0x7fff637b3ea0) at ../../kdeui/kernel/kapplication.cpp:302 #32 0x7f88febd215c in QCoreApplication::notifyInternal (this=0x7fff637b4a00, rec
[Bug 244490] New: kontact crash while idle
https://bugs.kde.org/show_bug.cgi?id=244490 Summary: kontact crash while idle Product: kontact Version: 4.4.3 Platform: Debian testing OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: r...@researchut.com Application: kontact (4.4.3) KDE Platform Version: 4.4.4 (KDE 4.4.4) Qt Version: 4.6.3 Operating System: Linux 2.6.32-5+iwlagn.1-amd64 x86_64 Distribution: Debian GNU/Linux testing (squeeze) -- Information about the crash: Kontact lately has been showing occasional crashes while remaining idle. I am not very sure for the cause though. The only delta is that I have hand installed kcaldav. The crash can be reproduced some of the time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault The current source language is "auto; currently asm". [Current thread is 1 (Thread 0x7f566dae9760 (LWP 4159))] Thread 2 (Thread 0x7f56498f4710 (LWP 15177)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f563e0ad4e6 in WTF::TCMalloc_PageHeap::scavengerThread (this=0x7f563f071340) at ../JavaScriptCore/wtf/FastMalloc.cpp:2299 #2 0x7f563e0ad529 in WTF::TCMalloc_PageHeap::runScavengerThread (context=0x7f563f07f40c) at ../JavaScriptCore/wtf/FastMalloc.cpp:1433 #3 0x7f566416a8ba in start_thread (arg=) at pthread_create.c:300 #4 0x7f566ab8a01d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 1 (Thread 0x7f566dae9760 (LWP 4159)): [KCrash Handler] #5 0x7f5649d29a6a in KOAgendaItem::paintEvent (this=0x2a01180, ev=) at ../../korganizer/views/agendaview/koagendaitem.cpp:835 #6 0x7f566b37e1e2 in QWidget::event (this=0x2a01180, event=0x7fff41af16c0) at kernel/qwidget.cpp:8190 #7 0x7f5649d26710 in KOAgendaItem::event (this=0x2a01180, event=0x7fff41af16c0) at ../../korganizer/views/agendaview/koagendaitem.cpp:1359 #8 0x7f566b32832c in QApplicationPrivate::notify_helper (this=0x1716cd0, receiver=0x2a01180, e=0x7fff41af16c0) at kernel/qapplication.cpp:4302 #9 0x7f566b32e80b in QApplication::notify (this=0x7fff41af86c0, receiver=0x2a01180, e=0x7fff41af16c0) at kernel/qapplication.cpp:4185 #10 0x7f566c970436 in KApplication::notify (this=0x7fff41af86c0, receiver=0x2a01180, event=0x7fff41af16c0) at ../../kdeui/kernel/kapplication.cpp:302 #11 0x7f566bf8815c in QCoreApplication::notifyInternal (this=0x7fff41af86c0, receiver=0x2a01180, event=0x7fff41af16c0) at kernel/qcoreapplication.cpp:726 #12 0x7f566b3867dd in QCoreApplication::sendSpontaneousEvent (this=0xf913060, pdev=, rgn=..., offset=, flags=, sharedPainter=0x0, backingStore=0x195b0c0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218 #13 QWidgetPrivate::drawWidget (this=0xf913060, pdev=, rgn=..., offset=, flags=, sharedPainter=0x0, backingStore=0x195b0c0) at kernel/qwidget.cpp:5363 #14 0x7f566b387478 in QWidgetPrivate::paintSiblingsRecursive (this=, pdev=, siblings=..., index=7, rgn=, offset=, flags=4, sharedPainter=0x0, backingStore=0x195b0c0) at kernel/qwidget.cpp:5476 #15 0x7f566b3872a9 in QWidgetPrivate::paintSiblingsRecursive (this=, pdev=, siblings=..., index=13, rgn=, offset=, flags=4, sharedPainter=0x0, backingStore=0x195b0c0) at kernel/qwidget.cpp:5463 #16 0x7f566b3872a9 in QWidgetPrivate::paintSiblingsRecursive (this=, pdev=, siblings=..., index=14, rgn=, offset=, flags=4, sharedPainter=0x0, backingStore=0x195b0c0) at kernel/qwidget.cpp:5463 #17 0x7f566b38653a in QWidgetPrivate::drawWidget (this=0x3495580, pdev=, rgn=..., offset=, flags=, sharedPainter=0x0, backingStore=0x195b0c0) at kernel/qwidget.cpp:5412 #18 0x7f566b387478 in QWidgetPrivate::paintSiblingsRecursive (this=, pdev=, siblings=..., index=0, rgn=, offset=, flags=4, sharedPainter=0x0, backingStore=0x195b0c0) at kernel/qwidget.cpp:5476 #19 0x7f566b38653a in QWidgetPrivate::drawWidget (this=0x3494090, pdev=, rgn=..., offset=, flags=, sharedPainter=0x0, backingStore=0x195b0c0) at kernel/qwidget.cpp:5412 #20 0x7f566b387478 in QWidgetPrivate::paintSiblingsRecursive (this=, pdev=, siblings=..., index=2, rgn=, offset=, flags=4, sharedPainter=0x0, backingStore=0x195b0c0) at kernel/qwidget.cpp:5476 #21 0x7f566b38653a in QWidgetPrivate::drawWidget (this=0x3493700, pdev=, rgn=..., offset=, flags=, sharedPainter=0x0, backingStore=0x195b0c0) at kernel/qwidget.cpp:5412 #22 0x7f566b387478 in QWidgetPrivate::paintSiblingsRecursive (this=, pdev=, siblings=..., index=4, rgn=, offset=, flags=4, sharedPainter=0x0, backingStore=0x195b0c0) at kernel/qwidget.cpp:5476 #23 0x7f566b38653a in QWidgetPrivate::drawWidget (this=0x348ef80, pdev=, rgn=..., offset=, flags=, sharedPainter=0x0, backingStore=0x195b0c0) at kernel/qwidget.cpp:5412 #24 0x00
[Bug 234246] New: akonadi gcal resource crash on restart
https://bugs.kde.org/show_bug.cgi?id=234246 Summary: akonadi gcal resource crash on restart Product: Akonadi Version: unspecified Platform: Debian testing OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Google Resource AssignedTo: savag...@yahoo.com ReportedBy: r...@researchut.com CC: vkra...@kde.org, kdepim-bugs@kde.org Application: akonadi_gcal_resource (0.1) KDE Platform Version: 4.4.2 (KDE 4.4.2) Qt Version: 4.6.2 Operating System: Linux 2.6.33-ck1 x86_64 Distribution: Debian GNU/Linux testing (squeeze) -- Information about the crash: When I do an akonadi restart, the akonadi gcal resource keeps crashing persistently The crash can be reproduced every time. -- Backtrace: Application: Akonadi Resource (akonadi_gcal_resource), signal: Aborted [KCrash Handler] #5 0x7f65473eef45 in *__GI_raise (sig=) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #6 0x7f65473f1d80 in *__GI_abort () at abort.c:88 #7 0x7f6547c75355 in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/libstdc++.so.6 #8 0x7f6547c73786 in ?? () from /usr/lib/libstdc++.so.6 #9 0x7f6547c737b3 in std::terminate() () from /usr/lib/libstdc++.so.6 #10 0x7f6547c738ae in __cxa_throw () from /usr/lib/libstdc++.so.6 #11 0x7f654b00ffe2 in qBadAlloc () at global/qglobal.cpp:2004 #12 0x7f65481af138 in QX11PixmapData::toImage (this=0xb28810) at image/qpixmap_x11.cpp:1494 #13 0x7f65481969e0 in QPixmap::toImage (this=0x7fff8c8bf100) at image/qpixmap.cpp:486 #14 0x7f654961ffe3 in KPixmapCache::Private::writeData (this=0xaab810, key=, pix=) at ../../kdeui/util/kpixmapcache.cpp:1474 #15 0x7f6549620d0b in KPixmapCache::insert (this=0xaaca70, key=..., pix=...) at ../../kdeui/util/kpixmapcache.cpp:1440 #16 0x7f6549566a34 in KIconLoader::loadIcon (this=0x9c34a0, _name=, group=, size=128, state=, overlays=..., path_store=0x0, canReturnNull=true) at ../../kdeui/icons/kiconloader.cpp:1005 #17 0x7f6549566774 in KIconLoader::loadIcon (this=0x9c34a0, _name=, group=, size=128, state=, overlays=..., path_store=0x0, canReturnNull=false) at ../../kdeui/icons/kiconloader.cpp:1130 #18 0x7f654955ef5d in KIconEngine::pixmap (this=, size=..., mode=, state=) at ../../kdeui/icons/kiconengine.cpp:119 #19 0x7f6548166535 in QIcon::pixmap (this=, size=..., mode=4294967295, state=10) at image/qicon.cpp:669 #20 0x7f65481532e4 in QWidgetPrivate::setWindowIcon_sys (this=, forceReset=) at kernel/qwidget_x11.cpp:1458 #21 0x7f654810bf18 in QWidget::create (this=0xa8bed0, window=0, initializeWindow=, destroyOldWindow=) at kernel/qwidget.cpp:1351 #22 0x7f6548142c97 in setupOwner () at kernel/qclipboard_x11.cpp:131 #23 0x7f65481436b0 in QClipboard (this=0xa8b7e0, parent=0x13a) at kernel/qclipboard_x11.cpp:458 #24 0x7f65480b4b27 in QApplication::clipboard () at kernel/qapplication.cpp:3090 #25 0x7f65495a464e in KClipboardSynchronizer::Private::setupSignals (this=0x5997) at ../../kdeui/kernel/kclipboard.cpp:94 #26 0x7f65495a4bf2 in KClipboardSynchronizer (this=0xa8b6b0, parent=) at ../../kdeui/kernel/kclipboard.cpp:84 #27 0x7f65495a4ca4 in operator-> () at ../../kdeui/kernel/kclipboard.cpp:73 #28 operator KClipboardSynchronizer* () at ../../kdeui/kernel/kclipboard.cpp:73 #29 KClipboardSynchronizer::self () at ../../kdeui/kernel/kclipboard.cpp:74 #30 0x7f654959fa01 in KApplicationPrivate::init (this=0xa6f390, GUIenabled=true) at ../../kdeui/kernel/kapplication.cpp:463 #31 0x7f65495a1099 in KApplication (this=0x7fff8c8c0490, GUIenabled=) at ../../kdeui/kernel/kapplication.cpp:343 #32 0x00408cd7 in _start () Possible duplicates by query: bug 234075, bug 233701, bug 233296, bug 232805, bug 231592. Reported using DrKonqi -- 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 222757] kmail threading is broken
https://bugs.kde.org/show_bug.cgi?id=222757 Ritesh Raj Sarraf changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|INVALID | --- Comment #4 from Ritesh Raj Sarraf 2010-04-07 14:40:11 --- (In reply to comment #3) > Kmails threading is based on some kind of a thread-ID. Clients that reply to > an > email will copy this ID. kmail groups all mails with the same ID together. > There is no bug here. Could you please give it some more thought ? I don't know the very details of how threading is done but if the other clients are threading differently (and correctly), kmail should do the same. If kmail's threading is based on some kind of thread-ID, which is incorrect, then it should be fixed to be rebased on something else. Grouping 2 very different messages into one thread because both have the same Subject looks to be the wrong way of associating messages. -- 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 233524] New: cannot add tags to emails through filters
https://bugs.kde.org/show_bug.cgi?id=233524 Summary: cannot add tags to emails through filters Product: kmail Version: 1.13.2 Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: r...@researchut.com Version: 1.13.2 (using 4.4.2 (KDE 4.4.2), Debian packages) Compiler: cc OS:Linux (x86_64) release 2.6.32-4-amd64 So I create a bunch of rules "Filters" where in I mention that if a certain condition meets, try to "Tag" the message. But it looks like the tagging is not done. If I manually tag a message, it gets tagged. I can confirm that this is a bug as the subject described, because when I add a 2nd action to the same rule, the 2nd action (which in my case is to move the message to a different folder) does get executed. -- 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 230536] New: knode crashed on article delete
https://bugs.kde.org/show_bug.cgi?id=230536 Summary: knode crashed on article delete Product: kontact Version: 4.4.1 Platform: Debian testing OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: r...@researchut.com Application: kontact (4.4.1) KDE Platform Version: 4.4.1 (KDE 4.4.1) Qt Version: 4.6.2 Operating System: Linux 2.6.32-3-amd64 x86_64 Distribution: Debian GNU/Linux testing (squeeze) -- Information about the crash: I tried to delete some of the articles that were present in my "Sent" folder. As soon as I click on Okay, knode crashed The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault The current source language is "auto; currently c". [Current thread is 1 (Thread 0x7f4ac2a247f0 (LWP 14776))] Thread 3 (Thread 0x7f4a9e75b910 (LWP 21693)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:220 #1 0x7f4ac0dc7502 in QWaitConditionPrivate::wait (this=, mutex=0x34db4d0, time=3) at thread/qwaitcondition_unix.cpp:85 #2 QWaitCondition::wait (this=, mutex=0x34db4d0, time=3) at thread/qwaitcondition_unix.cpp:159 #3 0x7f4ac0dbc939 in QThreadPoolThread::run (this=0x34f5bb0) at concurrent/qthreadpool.cpp:140 #4 0x7f4ac0dc65d5 in QThreadPrivate::start (arg=0x34f5bb0) at thread/qthread_unix.cpp:248 #5 0x7f4ab8e9c73a in start_thread (arg=) at pthread_create.c:300 #6 0x7f4abfac569d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #7 0x in ?? () Thread 2 (Thread 0x7f4aa0713910 (LWP 24658)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:220 #1 0x7f4ac0dc7502 in QWaitConditionPrivate::wait (this=, mutex=0x34db4d0, time=3) at thread/qwaitcondition_unix.cpp:85 #2 QWaitCondition::wait (this=, mutex=0x34db4d0, time=3) at thread/qwaitcondition_unix.cpp:159 #3 0x7f4ac0dbc939 in QThreadPoolThread::run (this=0x4595130) at concurrent/qthreadpool.cpp:140 #4 0x7f4ac0dc65d5 in QThreadPrivate::start (arg=0x4595130) at thread/qthread_unix.cpp:248 #5 0x7f4ab8e9c73a in start_thread (arg=) at pthread_create.c:300 #6 0x7f4abfac569d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #7 0x in ?? () The current source language is "auto; currently asm". Thread 1 (Thread 0x7f4ac2a247f0 (LWP 14776)): [KCrash Handler] #5 KNArticle::listItem (this=0xaf21f50, l=..., del=) at ../../knode/knarticle.h:66 #6 KNFolder::removeArticles (this=0xaf21f50, l=..., del=) at ../../knode/knfolder.cpp:499 #7 0x7f4a95a85bfa in KNArticleManager::deleteArticles (this=, l=..., ask=) at ../../knode/knarticlemanager.cpp:595 #8 0x7f4a95ac3119 in KNMainWidget::slotArtDelete (this=0xd2b56f0) at ../../knode/knmainwidget.cpp:1897 #9 0x7f4a95ace6dd in KNMainWidget::qt_metacall (this=0xd2b56f0, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fffaaa3f430) at ./knmainwidget.moc:292 #10 0x7f4ac0ecdb1f in QMetaObject::activate (sender=0x9cc48b0, m=, local_signal_index=, argv=0x0) at kernel/qobject.cpp:3293 #11 0x7f4ac0253702 in QAction::triggered (this=0x51e48b0, _t1=false) at .moc/release-shared/moc_qaction.cpp:263 #12 0x7f4ac025577b in QAction::activate (this=0x9cc48b0, event=) at kernel/qaction.cpp:1255 #13 0x7f4ac069363d in QMenuPrivate::activateCausedStack (this=, causedStack=..., action=0x9cc48b0, action_e=QAction::Trigger, self=true) at widgets/qmenu.cpp:1011 #14 0x7f4ac06991ca in QMenuPrivate::activateAction (this=0x43df930, action=0x9cc48b0, action_e=QAction::Trigger, self=) at widgets/qmenu.cpp:1103 #15 0x7f4ac198305e in KMenu::mouseReleaseEvent (this=0xad430e0, e=0x0) at ../../kdeui/widgets/kmenu.cpp:471 #16 0x7f4ac02afbe2 in QWidget::event (this=0xad430e0, event=0x7fffaaa40200) at kernel/qwidget.cpp:7998 #17 0x7f4ac069b38b in QMenu::event (this=0xad430e0, e=0x7fffaaa40200) at widgets/qmenu.cpp:2414 #18 0x7f4ac02598fc in QApplicationPrivate::notify_helper (this=0x23f51f0, receiver=0xad430e0, e=0x7fffaaa40200) at kernel/qapplication.cpp:4300 #19 0x7f4ac02605bb in QApplication::notify (this=0x7fffaaa40d60, receiver=0xad430e0, e=0x7fffaaa40200) at kernel/qapplication.cpp:3865 #20 0x7f4ac18a7336 in KApplication::notify (this=0x7fffaaa40d60, receiver=0xad430e0, event=0x7fffaaa40200) at ../../kdeui/kernel/kapplication.cpp:302 #21 0x7f4ac0ebaddc in QCoreApplication::notifyInternal (this=0x7fffaaa40d60, receiver=0xad430e0, event=0x7fffaaa40200) at kernel/qcoreapplication.cpp:704 #22 0x7f4ac025f78e in QCoreApplication::sendEvent (receiver=0xad430e0, event=0x7fffaaa40200, alienWidget=0x0, nativeWidget=0xad430e0, buttonDown=, lastMouseReceiver=, spontaneous=true) at ../../include/QtCore/../../src/corelib/kernel/
[Bug 186502] Kmail crashes at startup / other situations (IMAP-cache related) [QTreeWidget*, KMMimePartTreeItem, partNode::fillMimePartTree, KMail::ObjectTreeParser::insertAndParseNewChildNode]
https://bugs.kde.org/show_bug.cgi?id=186502 --- Comment #44 from Ritesh Raj Sarraf 2010-03-09 05:23:40 --- Created an attachment (id=41467) --> (http://bugs.kde.org/attachment.cgi?id=41467) New crash information added by DrKonqi I started seeing this crash only with KDE 4.4.1. This repeatedly happens on certain email messages. -- 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 186502] Kmail crashes at startup / other situations (IMAP-cache related) [QTreeWidget*, KMMimePartTreeItem, partNode::fillMimePartTree, KMail::ObjectTreeParser::insertAndParseNewChildNode]
https://bugs.kde.org/show_bug.cgi?id=186502 Ritesh Raj Sarraf changed: What|Removed |Added CC||r...@researchut.com -- 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 226115] Use Virtuoso for Akonadi storage
https://bugs.kde.org/show_bug.cgi?id=226115 Ritesh Raj Sarraf changed: What|Removed |Added CC||r...@researchut.com --- Comment #1 from Ritesh Raj Sarraf 2010-02-10 08:52:58 --- Same should go for Amarok too. -- 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 225880] New: kontact crash while idle
https://bugs.kde.org/show_bug.cgi?id=225880 Summary: kontact crash while idle Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: r...@researchut.com Application that crashed: kontact Version of the application: 4.3.4 KDE Version: 4.3.4 (KDE 4.3.4) Qt Version: 4.5.3 Operating System: Linux 2.6.32-1-686 i686 Distribution: Debian GNU/Linux testing (squeeze) What I was doing when the application crashed: OS was under load as many resource hungry kde applications were run. kontact was idle and it crashed. Not sure if it can be reproduced again. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #6 QMutex::lock (this=0x3e4) at thread/qmutex.cpp:152 #7 0xb702de97 in QCoreApplication::postEvent (receiver=0xf4728e0, event=0xbe10888, priority=0) at kernel/qcoreapplication.cpp:1020 #8 0xb702e15c in QCoreApplication::postEvent (receiver=0xf4728e0, event=0xbe10888) at kernel/qcoreapplication.cpp:973 #9 0xb703d637 in QObject::deleteLater (this=0xf4728e0) at kernel/qobject.cpp:2018 #10 0xb0b0285b in KMail::ImapJob::slotGetMessageResult (this=0xf4728e0, job=0xb55f720) at ../../kmail/imapjob.cpp:478 #11 0xb0b071af in KMail::ImapJob::qt_metacall (this=0xf4728e0, _c=QMetaObject::InvokeMetaMethod, _id=12, _a=0xbfcc7c4c) at ./imapjob.moc:82 #12 0xb7043303 in QMetaObject::activate (sender=0xb55f720, from_signal_index=7, to_signal_index=7, argv=0xbfcc7c4c) at kernel/qobject.cpp:3112 #13 0xb7043f42 in QMetaObject::activate (sender=0xb55f720, m=0xb735d888, local_signal_index=3, argv=0xbfcc7c4c) at kernel/qobject.cpp:3186 #14 0xb71faa33 in KJob::result (this=0xb55f720, _t1=0xb55f720) at ./kjob.moc:188 #15 0xb71faed9 in KJob::emitResult (this=0xb55f720) at ../../kdecore/jobs/kjob.cpp:304 #16 0xb5a6cb15 in KIO::SimpleJob::slotFinished (this=0xb55f720) at ../../kio/kio/job.cpp:477 #17 0xb5a6d473 in KIO::TransferJob::slotFinished (this=0xb55f720) at ../../kio/kio/job.cpp:948 #18 0xb5a69a03 in KIO::TransferJob::qt_metacall (this=0xb55f720, _c=QMetaObject::InvokeMetaMethod, _id=7, _a=0xbfcc7e88) at ./jobclasses.moc:343 #19 0xb7043303 in QMetaObject::activate (sender=0xa236e58, from_signal_index=8, to_signal_index=8, argv=0x0) at kernel/qobject.cpp:3112 #20 0xb7043f42 in QMetaObject::activate (sender=0xa236e58, m=0xb5c13b84, local_signal_index=4, argv=0x0) at kernel/qobject.cpp:3186 #21 0xb5b32707 in KIO::SlaveInterface::finished (this=0xa236e58) at ./slaveinterface.moc:165 #22 0xb5b364b7 in KIO::SlaveInterface::dispatch (this=0xa236e58, _cmd=104, rawdata=...) at ../../kio/kio/slaveinterface.cpp:175 #23 0xb5b32be7 in KIO::SlaveInterface::dispatch (this=0xa236e58) at ../../kio/kio/slaveinterface.cpp:91 #24 0xb5b24bcd in KIO::Slave::gotInput (this=0xa236e58) at ../../kio/kio/slave.cpp:322 #25 0xb5b270b3 in KIO::Slave::qt_metacall (this=0xa236e58, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfcc8158) at ./slave.moc:76 #26 0xb7043303 in QMetaObject::activate (sender=0xc02e118, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3112 #27 0xb7043f42 in QMetaObject::activate (sender=0xc02e118, m=0xb5c104c0, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3186 #28 0xb5a30c07 in KIO::Connection::readyRead (this=0xc02e118) at ./connection.moc:86 #29 0xb5a32513 in KIO::ConnectionPrivate::dequeue (this=0xfd2df30) at ../../kio/kio/connection.cpp:82 #30 0xb5a328f6 in KIO::Connection::qt_metacall (this=0xc02e118, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x1058e318) at ./connection.moc:73 #31 0xb703cb0b in QMetaCallEvent::placeMetaCall (this=0xf3d50e8, object=0xc02e118) at kernel/qobject.cpp:477 #32 0xb703e5e0 in QObject::event (this=0xc02e118, e=0xf3d50e8) at kernel/qobject.cpp:1110 #33 0xb666da94 in QApplicationPrivate::notify_helper (this=0x916e710, receiver=0xc02e118, e=0xf3d50e8) at kernel/qapplication.cpp:4065 #34 0xb6675bee in QApplication::notify (this=0xbfcc89c4, receiver=0xc02e118, e=0xf3d50e8) at kernel/qapplication.cpp:3605 #35 0xb753662d in KApplication::notify (this=0xbfcc89c4, receiver=0xc02e118, event=0xf3d50e8) at ../../kdeui/kernel/kapplication.cpp:302 #36 0xb702e1eb in QCoreApplication::notifyInternal (this=0xbfcc89c4, receiver=0xc02e118, event=0xf3d50e8) at kernel/qcoreapplication.cpp:610 #37 0xb702ee2e in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x9147388) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #38 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x9147388) at kernel/qcoreapplication.cpp:1247 #39 0xb702f00d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140 #40 0xb670e3fe in QCoreApplication::sendPostedEvents (this=0x91470d8, flags=...) at ../../include/QtCore/../../src/corel
[Bug 222757] kmail threading is broken
https://bugs.kde.org/show_bug.cgi?id=222757 --- Comment #2 from Ritesh Raj Sarraf 2010-01-14 21:11:56 --- Another point to add to the screenshot in Comment #1 is that message threading is broken on another point also. The date. I sent a latest different "Hi" message on the 13th of Jan, 2010. The reply to it has been mis-grouped by kmail into the same old thread. -- 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 222757] kmail threading is broken
https://bugs.kde.org/show_bug.cgi?id=222757 --- Comment #1 from Ritesh Raj Sarraf 2010-01-14 21:09:07 --- Created an attachment (id=39899) --> (http://bugs.kde.org/attachment.cgi?id=39899) screenshot of problem As you can see in the screen shot, all messages with subject "Hi" as grouped together. In fact, I sent a "Hi" message to a different recipient. That message is also grouped into the same incorrect thread. -- 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 222757] New: kmail threading is broken
https://bugs.kde.org/show_bug.cgi?id=222757 Summary: kmail threading is broken Product: kmail Version: unspecified Platform: Debian testing OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: r...@researchut.com Version:(using KDE 4.3.4) OS:Linux Installed from:Debian testing/unstable Packages The kmail threading system looks to be weird. Any usual client (though I haven't used the other ones lately) seems to be threading messages based on its message headers, but in case of kmail, the threading seems to be done on the basis of subject keyword. If kmail finds a subject keyword match, it groups those messages into a single thread, which is wrong. For example, say, I send a "Hi" message to Person X 2 weeks ago. Now 2 weeks later, I send another "Hi" message to Person X. These 2 messages are unique. Right ? Kmail groups both these messages into a single thread. -- 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 211169] New: kontact kcal akonadi crash
https://bugs.kde.org/show_bug.cgi?id=211169 Summary: kontact kcal akonadi crash Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: r...@researchut.com Application that crashed: kontact Version of the application: 4.3.2 KDE Version: 4.3.2 (KDE 4.3.2) Qt Version: 4.5.3 Operating System: Linux 2.6.31-trunk-686 i686 Distribution: Debian GNU/Linux testing (squeeze) What I was doing when the application crashed: looks like it crashed in the way I tried to access the calendar resource. Here's my setup. To pull exchange calendar, I have a chrooted debian lenny install (kde 3). There korganizer has a file based resource to which it pulls and writes its calendar data. In kde4, akonadi takes that resource as a file based read-only resource. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #6 QHash::value (this=0x0, kresId=...) at /usr/include/qt4/QtCore/qhash.h:589 #7 SubResourceBase::mappedItem (this=0x0, kresId=...) at ../../../kresources/shared/subresourcebase.cpp:188 #8 0xad440953 in ResourcePrivateBase::prepareItemSaveContext (this=0xc6938b8, it=..., saveContext=...) at ../../../kresources/shared/resourceprivatebase.cpp:427 #9 0xad440b80 in ResourcePrivateBase::prepareItemSaveContext (this=0xc6938b8, saveContext=...) at ../../../kresources/shared/resourceprivatebase.cpp:401 #10 0xad442ba6 in ResourcePrivateBase::doSave (this=0xc6938b8) at ../../../kresources/shared/resourceprivatebase.cpp:161 #11 0xad422566 in KCal::ResourceAkonadi::doSave (this=0xc70d590, syncCache=false) at ../../../kresources/kcal/resourceakonadi.cpp:407 #12 0xb51c88ae in KCal::ResourceCalendar::save (this=0xc70d590, incidence=0x0) at ../../kcal/resourcecalendar.cpp:228 #13 0xb51dcced in KCal::CalendarResources::save (this=0xc0d8b88) at ../../kcal/calendarresources.cpp:365 #14 0xad68cbee in ActionManager::saveCalendar (this=0xc0c1968) at ../../korganizer/actionmanager.cpp:2041 #15 0xad68cce7 in ActionManager::checkAutoSave (this=0xc0c1968) at ../../korganizer/actionmanager.cpp:1328 #16 0xad68e061 in ActionManager::qt_metacall (this=0xc0c1968, _c=QMetaObject::InvokeMetaMethod, _id=64, _a=0xbf8dcb28) at ./actionmanager.moc:260 #17 0xb6efa303 in QMetaObject::activate (sender=0xcf12288, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3112 #18 0xb6efaf42 in QMetaObject::activate (sender=0xcf12288, m=0xb6fd6d84, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3186 #19 0xb6f35b37 in QTimer::timeout (this=0xcf12288) at .moc/release-shared/moc_qtimer.cpp:128 #20 0xb6f0065e in QTimer::timerEvent (this=0xcf12288, e=0xbf8dcfac) at kernel/qtimer.cpp:261 #21 0xb6ef539f in QObject::event (this=0xcf12288, e=0xbf8dcfac) at kernel/qobject.cpp:1074 #22 0xb6524a94 in QApplicationPrivate::notify_helper (this=0x8fe0b30, receiver=0xcf12288, e=0xbf8dcfac) at kernel/qapplication.cpp:4065 #23 0xb652cbee in QApplication::notify (this=0xbf8dd45c, receiver=0xcf12288, e=0xbf8dcfac) at kernel/qapplication.cpp:3605 #24 0xb73e70fd in KApplication::notify (this=0xbf8dd45c, receiver=0xcf12288, event=0xbf8dcfac) at ../../kdeui/kernel/kapplication.cpp:302 #25 0xb6ee51eb in QCoreApplication::notifyInternal (this=0xbf8dd45c, receiver=0xcf12288, event=0xbf8dcfac) at kernel/qcoreapplication.cpp:610 #26 0xb6f13e21 in QCoreApplication::sendEvent (this=0x8fe12c4) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #27 QTimerInfoList::activateTimers (this=0x8fe12c4) at kernel/qeventdispatcher_unix.cpp:580 #28 0xb6f13fcb in QEventDispatcherUNIX::processEvents (this=0x8fbd6e8, flags=...) at kernel/qeventdispatcher_unix.cpp:916 #29 0xb65c5496 in QEventDispatcherX11::processEvents (this=0x8fbd6e8, flags=...) at kernel/qeventdispatcher_x11.cpp:152 #30 0xb6ee383a in QEventLoop::processEvents (this=0xbf8dd2d0, flags=...) at kernel/qeventloop.cpp:149 #31 0xb6ee3c82 in QEventLoop::exec (this=0xbf8dd2d0, flags=...) at kernel/qeventloop.cpp:201 #32 0xb6ee60d9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #33 0xb6524917 in QApplication::exec () at kernel/qapplication.cpp:3525 #34 0x0804bd40 in main (argc=1, argv=0xbf8dd654) at ../../../kontact/src/main.cpp:218 Reported using DrKonqi -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 210942] New: Should knode be merged into kmail
https://bugs.kde.org/show_bug.cgi?id=210942 Summary: Should knode be merged into kmail Product: kmail Version: unspecified Platform: Debian testing OS/Version: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: r...@researchut.com Version:(using KDE 4.3.2) OS:Linux Installed from:Debian testing/unstable Packages While knode is still one of the best news clients, it now has started showing its age especially when compared to other KDE applications. Since kmail is going to be ported to akonadi now, I think this should be the right timing to make this wishlist. Keeping knode separate from kmail has banished it from having many of the enhancements that it could have had automatically. And there is no bad reason for that. kmail is a much more widely used application compared to knode. But still, IMO they could co-exist and leverage the enhancements together. For example: kmail received the latest new Fancy mail threading (which by the way is awesome). This feature could have been used by knode too, only if there were common. Also by separating them, we make users to remember 2 interfaces. Take this bug report as example. https://bugs.kde.org/show_bug.cgi?id=206610 Can we have a NNTP account type in kmail ? Perhaps, we could just add that and see the change. Eventually, if users completely switch to the NNTP resource in kmail, knode could just be retired. -- 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 207934] New: clicked on 'Reply' and kontact crashed
https://bugs.kde.org/show_bug.cgi?id=207934 Summary: clicked on 'Reply' and kontact crashed Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: r...@researchut.com Application that crashed: kontact Version of the application: 4.3.1 KDE Version: 4.3.1 (KDE 4.3.1) Qt Version: 4.5.2 Operating System: Linux 2.6.30-1-686 i686 Distribution: Debian GNU/Linux testing (squeeze) What I was doing when the application crashed: Kontact had been running for 24+ hrs. Just clicked on 'Reply' to reply a message and boom, kontact crashed -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0xb4935700 (LWP 25263))] Thread 2 (Thread 0xad2eeb90 (LWP 12404)): #0 0xb8068424 in __kernel_vsyscall () #1 0xb5252292 in pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_timedwait.S:179 #2 0xb6bdc8b4 in __pthread_cond_timedwait (cond=0x97915e0, mutex=0x97915c8, abstime=0xad2ee2bc) at forward.c:152 #3 0xb774e53c in QWaitConditionPrivate::wait (this=0x978be60, mutex=0x978be5c, time=3) at thread/qwaitcondition_unix.cpp:85 #4 QWaitCondition::wait (this=0x978be60, mutex=0x978be5c, time=3) at thread/qwaitcondition_unix.cpp:159 #5 0xb7743d3e in QThreadPoolThread::run (this=0x99003a8) at concurrent/qthreadpool.cpp:140 #6 0xb774d582 in QThreadPrivate::start (arg=0x99003a8) at thread/qthread_unix.cpp:188 #7 0xb524e4b5 in start_thread (arg=0xad2eeb90) at pthread_create.c:300 #8 0xb6bcda5e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 1 (Thread 0xb4935700 (LWP 25263)): [KCrash Handler] #6 0x0beae789 in ?? () #7 0xb134233b in KMCommand::qt_metacall (this=0xabf58f0, _c=QMetaObject::InvokeMetaMethod, _id=200363544, _a=0x4) at ./kmcommands.moc:86 #8 0xb1342a02 in KMReplyToCommand::qt_metacall (this=0xabf58f0, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbfcd49a8) at ./kmcommands.moc:844 #9 0xb7853b33 in QMetaObject::activate (sender=0xc35a2b8, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3112 #10 0xb7854782 in QMetaObject::activate (sender=0xc35a2b8, m=0xb792ede8, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3186 #11 0xb7859847 in QSingleShotTimer::timeout (this=0xc35a2b8) at .moc/release-shared/qtimer.moc:76 #12 0xb785996c in QSingleShotTimer::timerEvent (this=0xc35a2b8) at kernel/qtimer.cpp:298 #13 0xb784ebcf in QObject::event (this=0xc35a2b8, e=0xbfcd4e2c) at kernel/qobject.cpp:1074 #14 0xb6e7e814 in QApplicationPrivate::notify_helper (this=0x8cc7c98, receiver=0xc35a2b8, e=0xbfcd4e2c) at kernel/qapplication.cpp:4056 #15 0xb6e8697e in QApplication::notify (this=0xbfcd52dc, receiver=0xc35a2b8, e=0xbfcd4e2c) at kernel/qapplication.cpp:3603 #16 0xb7d3f4ad in KApplication::notify (this=0xbfcd52dc, receiver=0xc35a2b8, event=0xbfcd4e2c) at ../../kdeui/kernel/kapplication.cpp:302 #17 0xb783e9cb in QCoreApplication::notifyInternal (this=0xbfcd52dc, receiver=0xc35a2b8, event=0xbfcd4e2c) at kernel/qcoreapplication.cpp:610 #18 0xb786d361 in QCoreApplication::sendEvent (this=0x8cc847c) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #19 QTimerInfoList::activateTimers (this=0x8cc847c) at kernel/qeventdispatcher_unix.cpp:572 #20 0xb786d5fb in QEventDispatcherUNIX::processEvents (this=0x8ca46e8, flags=...) at kernel/qeventdispatcher_unix.cpp:908 #21 0xb6f1f166 in QEventDispatcherX11::processEvents (this=0x8ca46e8, flags=...) at kernel/qeventdispatcher_x11.cpp:152 #22 0xb783d01a in QEventLoop::processEvents (this=0xbfcd5150, flags=...) at kernel/qeventloop.cpp:149 #23 0xb783d462 in QEventLoop::exec (this=0xbfcd5150, flags=...) at kernel/qeventloop.cpp:201 #24 0xb783f8b9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #25 0xb6e7e697 in QApplication::exec () at kernel/qapplication.cpp:3525 #26 0x0804bd40 in main (argc=1, argv=0xbfcd54d4) at ../../../kontact/src/main.cpp:218 Reported using DrKonqi -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 207343] New: crash whey typing name
https://bugs.kde.org/show_bug.cgi?id=207343 Summary: crash whey typing name Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: r...@researchut.com Application that crashed: kontact Version of the application: 4.3.1 KDE Version: 4.3.1 (KDE 4.3.1) Qt Version: 4.5.2 Operating System: Linux 2.6.30-1-686 i686 Distribution: Debian GNU/Linux testing (squeeze) What I was doing when the application crashed: kontact crashed when I typed in a name in the To Field. I also have an LDAP account configured in my addressbook, which gets online queried, when typing the names -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #6 QListWidgetItem::text (this=0x8863fd8, adrs=...) at /usr/include/qt4/QtGui/qlistwidget.h:90 #7 KPIM::AddresseeLineEdit::slotLDAPSearchData (this=0x8863fd8, adrs=...) at ../../libkdepim/addresseelineedit.cpp:820 #8 0xb7e6b38a in KPIM::AddresseeLineEdit::qt_metacall (this=0x8863fd8, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbf91084c) at ./addresseelineedit.moc:95 #9 0xb12c538a in KMLineEdit::qt_metacall (this=0x8863fd8, _c=QMetaObject::InvokeMetaMethod, _id=84, _a=0xbf91084c) at ./kmlineeditspell.moc:68 #10 0xb1339f3a in RecipientLineEdit::qt_metacall (this=0x8863fd8, _c=QMetaObject::InvokeMetaMethod, _id=84, _a=0xbf91084c) at ./recipientseditor.moc:123 #11 0xb773db33 in QMetaObject::activate (sender=0x823e1f0, from_signal_index=5, to_signal_index=5, argv=0xbf91084c) at kernel/qobject.cpp:3112 #12 0xb773e782 in QMetaObject::activate (sender=0x823e1f0, m=0xb7eef248, local_signal_index=1, argv=0xbf91084c) at kernel/qobject.cpp:3186 #13 0xb7e6e613 in KPIM::LdapSearch::searchData (this=0x823e1f0, _t1=...) at ./ldapclient.moc:205 #14 0xb7e723af in KPIM::LdapSearch::slotDataTimer (this=0x823e1f0) at ../../libkdepim/ldapclient.cpp:465 #15 0xb7e7243d in KPIM::LdapSearch::finish (this=0x823e1f0) at ../../libkdepim/ldapclient.cpp:472 #16 0xb7e72480 in KPIM::LdapSearch::slotLDAPDone (this=0x8a517d0) at ../../libkdepim/ldapclient.cpp:454 #17 0xb7e753c3 in KPIM::LdapSearch::qt_metacall (this=0x823e1f0, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0xbf910968) at ./ldapclient.moc:184 #18 0xb773db33 in QMetaObject::activate (sender=0x823de88, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3112 #19 0xb773e782 in QMetaObject::activate (sender=0x823de88, m=0xb7eef238, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3186 #20 0xb7e6e747 in KPIM::LdapClient::done (this=0x823de88) at ./ldapclient.moc:103 #21 0xb7e6eeff in KPIM::LdapClient::slotDone (this=0x823de88) at ../../libkdepim/ldapclient.cpp:119 #22 0xb7e7296b in KPIM::LdapClient::qt_metacall (this=0x823de88, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbf910aec) at ./ldapclient.moc:92 #23 0xb773db33 in QMetaObject::activate (sender=0x8f7f188, from_signal_index=7, to_signal_index=7, argv=0xbf910aec) at kernel/qobject.cpp:3112 #24 0xb773e782 in QMetaObject::activate (sender=0x8f7f188, m=0xb7a50b48, local_signal_index=3, argv=0xbf910aec) at kernel/qobject.cpp:3186 #25 0xb78f43d3 in KJob::result (this=0x8f7f188, _t1=0x8f7f188) at ./kjob.moc:188 #26 0xb78f4879 in KJob::emitResult (this=0x8f7f188) at ../../kdecore/jobs/kjob.cpp:304 #27 0xb61517b5 in KIO::SimpleJob::slotFinished (this=0x8f7f188) at ../../kio/kio/job.cpp:477 #28 0xb6152113 in KIO::TransferJob::slotFinished (this=0x8f7f188) at ../../kio/kio/job.cpp:948 #29 0xb614e6a3 in KIO::TransferJob::qt_metacall (this=0x8f7f188, _c=QMetaObject::InvokeMetaMethod, _id=7, _a=0xbf910d28) at ./jobclasses.moc:343 #30 0xb773db33 in QMetaObject::activate (sender=0x8fcfa28, from_signal_index=8, to_signal_index=8, argv=0x0) at kernel/qobject.cpp:3112 #31 0xb773e782 in QMetaObject::activate (sender=0x8fcfa28, m=0xb62f8b84, local_signal_index=4, argv=0x0) at kernel/qobject.cpp:3186 #32 0xb6217437 in KIO::SlaveInterface::finished (this=0x8fcfa28) at ./slaveinterface.moc:165 #33 0xb621b1e7 in KIO::SlaveInterface::dispatch (this=0x8fcfa28, _cmd=104, rawdata=...) at ../../kio/kio/slaveinterface.cpp:175 #34 0xb6217917 in KIO::SlaveInterface::dispatch (this=0x8fcfa28) at ../../kio/kio/slaveinterface.cpp:91 #35 0xb62098fd in KIO::Slave::gotInput (this=0x8fcfa28) at ../../kio/kio/slave.cpp:322 #36 0xb620bde3 in KIO::Slave::qt_metacall (this=0x8fcfa28, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbf910ff8) at ./slave.moc:76 #37 0xb773db33 in QMetaObject::activate (sender=0x902f358, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3112 #38 0xb773e782 in QMetaObject::activate (sender=0x902f358, m=0xb62f54c0, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3186 #39 0xb6115937 in KIO::Connection::readyRead (this=0x902f358) at ./connection.moc:86 #40 0xb6117243 in KIO::ConnectionPrivat
[Bug 206611] New: consistent shortcut interface for all pim apps
https://bugs.kde.org/show_bug.cgi?id=206611 Summary: consistent shortcut interface for all pim apps Product: kontact Version: 4.3 Platform: Debian testing OS/Version: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: r...@researchut.com Version:(using KDE 4.3.1) OS:Linux Installed from:Debian testing/unstable Packages It would make more sense to have a consistent shortcut interface and behavior for the common tasks. Tasks like: * Collapse/Expand Threads * Next message * Next Thread et cetera. Currently different KDE PIM apps have different keys defined (which could be customized) and they behave in different manners. Best example would be Thread navigation in Kmail and Knode. In Knode Thread Collapse/Expand is there. With a different name though. 'T'. But with some deficiencies. Like, If I'm in the middle of the thread and hit 'T', only the messages below it get collapsed. Ideally, it should be collapsing the entire thread (just like how kmail does). -- 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 206610] provide shortcut for collapse/expand for each thread
https://bugs.kde.org/show_bug.cgi?id=206610 Ritesh Raj Sarraf changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||INVALID --- Comment #1 from Ritesh Raj Sarraf 2009-09-07 11:44:39 --- actually, it was there. With a different name though. 'T'. But with some deficiencies. Like, If I'm in the middle of the thread and hit 'T', only the messages below it get collapsed. Ideally, it should be collapsing the entire thread. I think it would be good if both knode and kmail (and maybe akregator), all share a common set of Shortcuts and Shortcut behavior. (Maybe I should file a feature request for that) -- 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 206610] New: provide shortcut for collapse/expand for each thread
https://bugs.kde.org/show_bug.cgi?id=206610 Summary: provide shortcut for collapse/expand for each thread Product: knode Version: unspecified Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: r...@researchut.com Version: 4.3.1 (using 4.3.1 (KDE 4.3.1), Debian packages) Compiler: cc OS:Linux (i686) release 2.6.30-1-686 The current Collapse/Expand shortcuts in Knode are for "All Threads". It would be good to have the same on a per-thread basis. -- 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 206440] New: kmail crash while opening an attachment
https://bugs.kde.org/show_bug.cgi?id=206440 Summary: kmail crash while opening an attachment Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: r...@researchut.com Application that crashed: kontact Version of the application: 4.3.1 KDE Version: 4.3.1 (KDE 4.3.1) Qt Version: 4.5.2 Operating System: Linux 2.6.30-custom i686 Distribution: Debian GNU/Linux testing (squeeze) What I was doing when the application crashed: I have an online imap (localhost) account configured. When I went to the next message (which has lots of attachments), while kmail was loading the mail, I clicked on one of the attachments. And then exactly, kontact crashed -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #6 DwString::c_str (this=0x9fc51a8, msg=0xa2e65c8, partSpecifier=...) at ../../mimelib/mimelib/string.h:618 #7 DwMessageComponent::partId (this=0x9fc51a8, msg=0xa2e65c8, partSpecifier=...) at ../../mimelib/mimelib/msgcmp.h:259 #8 KMLoadPartsCommand::slotPartRetrieved (this=0x9fc51a8, msg=0xa2e65c8, partSpecifier=...) at ../../kmail/kmcommands.cpp:2742 #9 0xb12125ad in KMLoadPartsCommand::qt_metacall (this=0x9fc51a8, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0xbfe389a8) at ./kmcommands.moc:1858 #10 0xb76fab33 in QMetaObject::activate (sender=0x9dc56d0, from_signal_index=5, to_signal_index=5, argv=0xbfe389a8) at kernel/qobject.cpp:3112 #11 0xb76fb782 in QMetaObject::activate (sender=0x9dc56d0, m=0xb16364d0, local_signal_index=1, argv=0xbfe389a8) at kernel/qobject.cpp:3186 #12 0xb1267649 in KMail::FolderJob::messageUpdated (this=0x9dc56d0, _t1=0xa2e65c8, _t2=...) at ./folderjob.moc:106 #13 0xb1273f1b in KMail::ImapJob::slotGetMessageResult (this=0x9dc56d0, job=0xa1f0bf8) at ../../kmail/imapjob.cpp:476 #14 0xb12784bc in KMail::ImapJob::qt_metacall (this=0x9dc56d0, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfe38b1c) at ./imapjob.moc:82 #15 0xb76fab33 in QMetaObject::activate (sender=0xa1f0bf8, from_signal_index=7, to_signal_index=7, argv=0xbfe38b1c) at kernel/qobject.cpp:3112 #16 0xb76fb782 in QMetaObject::activate (sender=0xa1f0bf8, m=0xb7a0db48, local_signal_index=3, argv=0xbfe38b1c) at kernel/qobject.cpp:3186 #17 0xb78b13d3 in KJob::result (this=0xa1f0bf8, _t1=0xa1f0bf8) at ./kjob.moc:188 #18 0xb78b1879 in KJob::emitResult (this=0xa1f0bf8) at ../../kdecore/jobs/kjob.cpp:304 #19 0xb610e7b5 in KIO::SimpleJob::slotFinished (this=0xa1f0bf8) at ../../kio/kio/job.cpp:477 #20 0xb610f113 in KIO::TransferJob::slotFinished (this=0xa1f0bf8) at ../../kio/kio/job.cpp:948 #21 0xb610b6a3 in KIO::TransferJob::qt_metacall (this=0xa1f0bf8, _c=QMetaObject::InvokeMetaMethod, _id=7, _a=0xbfe38d58) at ./jobclasses.moc:343 #22 0xb76fab33 in QMetaObject::activate (sender=0x973f840, from_signal_index=8, to_signal_index=8, argv=0x0) at kernel/qobject.cpp:3112 #23 0xb76fb782 in QMetaObject::activate (sender=0x973f840, m=0xb62b5b84, local_signal_index=4, argv=0x0) at kernel/qobject.cpp:3186 #24 0xb61d4437 in KIO::SlaveInterface::finished (this=0x973f840) at ./slaveinterface.moc:165 #25 0xb61d81e7 in KIO::SlaveInterface::dispatch (this=0x973f840, _cmd=104, rawdata=...) at ../../kio/kio/slaveinterface.cpp:175 #26 0xb61d4917 in KIO::SlaveInterface::dispatch (this=0x973f840) at ../../kio/kio/slaveinterface.cpp:91 #27 0xb61c68fd in KIO::Slave::gotInput (this=0x973f840) at ../../kio/kio/slave.cpp:322 #28 0xb61c8de3 in KIO::Slave::qt_metacall (this=0x973f840, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfe39028) at ./slave.moc:76 #29 0xb76fab33 in QMetaObject::activate (sender=0x9733fb8, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3112 #30 0xb76fb782 in QMetaObject::activate (sender=0x9733fb8, m=0xb62b24c0, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3186 #31 0xb60d2937 in KIO::Connection::readyRead (this=0x9733fb8) at ./connection.moc:86 #32 0xb60d4243 in KIO::ConnectionPrivate::dequeue (this=0x9733fc8) at ../../kio/kio/connection.cpp:82 #33 0xb60d4626 in KIO::Connection::qt_metacall (this=0x9733fb8, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0xa14e5e0) at ./connection.moc:73 #34 0xb76f433b in QMetaCallEvent::placeMetaCall (this=0x9fc6a78, object=0x9733fb8) at kernel/qobject.cpp:477 #35 0xb76f5e10 in QObject::event (this=0x9733fb8, e=0x9fc6a78) at kernel/qobject.cpp:1110 #36 0xb6d25814 in QApplicationPrivate::notify_helper (this=0x8bd9968, receiver=0x9733fb8, e=0x9fc6a78) at kernel/qapplication.cpp:4056 #37 0xb6d2d97e in QApplication::notify (this=0xbfe3999c, receiver=0x9733fb8, e=0x9fc6a78) at kernel/qapplication.cpp:3603 #38 0xb7be64ad in KApplication::notify (this=0xbfe3999c, receiver=0x9733fb8, event=0x9fc6a78) at ../../kdeui/kernel/kapplication.cpp:302 #39 0xb76e59cb in QCoreApplication::notifyInternal (this=0x
[Bug 113871] New mail Notification dialog
https://bugs.kde.org/show_bug.cgi?id=113871 --- Comment #7 from Ritesh Raj Sarraf 2009-08-31 10:43:57 --- Now that kmail supports IMAP IDLE, the "how to display many message pop-ups" problem will be solved. -- 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 59748] disable notification messages when IMAP server not reacheable
https://bugs.kde.org/show_bug.cgi?id=59748 --- Comment #5 from Ritesh Raj Sarraf 2009-08-31 10:42:07 --- How do I close it as a duplicate ? This issue is already fixed in #39097 -- 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 205067] New: todo crashed when marking it as 100% complete
https://bugs.kde.org/show_bug.cgi?id=205067 Summary: todo crashed when marking it as 100% complete Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: r...@researchut.com Application that crashed: kontact Version of the application: 4.3.0 KDE Version: 4.3.00 (KDE 4.3.0) Qt Version: 4.5.2 Operating System: Linux 2.6.30-custom i686 Distribution: Debian GNU/Linux testing (squeeze) What I was doing when the application crashed: I marked my ToDo item as 100% Complete. Add to Journal was also enabled. Clicking on Ok crashed kontact -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #6 0xacb11cc0 in KOTodoModel::moveIfParentChanged (this=0xc15c1a0, curNode=0x0, todo=0xb5b5000, addParentIfMissing=false) at /usr/include/qt4/QtCore/qabstractitemmodel.h:366 #7 0xacb14162 in KOTodoModel::processChange (this=0xc15c1a0, incidence=0xb5b5000, action=1) at ../../korganizer/views/todoview/kotodomodel.cpp:271 #8 0xacb1acfe in KOTodoView::changeIncidenceDisplay (this=0xcfee660, incidence=0xb5b5000, action=1) at ../../korganizer/views/todoview/kotodoview.cpp:406 #9 0xacb399ab in CalendarView::changeIncidenceDisplay (this=0xec19ca8, incidence=0xb5b5000, action=1) at ../../korganizer/calendarview.cpp:782 #10 0xacb44592 in CalendarView::incidenceChanged (this=0xec19ca8, oldIncidence=0xc986910, newIncidence=0xb5b5000, what=9) at ../../korganizer/calendarview.cpp:726 #11 0xacb448c3 in CalendarView::incidenceChanged (this=0xec19ca8, oldIncidence=0xc986910, newIncidence=0xb5b5000) at ../../korganizer/calendarview.cpp:667 #12 0xacb49b26 in CalendarView::qt_metacall (this=0xec19ca8, _c=QMetaObject::InvokeMetaMethod, _id=93, _a=0xbfd8fae8) at ./calendarview.moc:485 #13 0xb78cbb33 in QMetaObject::activate (sender=0xc24d7d8, from_signal_index=6, to_signal_index=6, argv=0xbfd8fae8) at kernel/qobject.cpp:3112 #14 0xb78cc782 in QMetaObject::activate (sender=0xc24d7d8, m=0xada6f19c, local_signal_index=2, argv=0xbfd8fae8) at kernel/qobject.cpp:3186 #15 0xada6e139 in KOrg::IncidenceChangerBase::incidenceChanged (this=0xc24d7d8, _t1=0xc986910, _t2=0xb5b5000) at ./incidencechangerbase.moc:108 #16 0xacbdcf19 in IncidenceChanger::changeIncidence (this=0xc24d7d8, oldinc=0xc986910, newinc=0xb5b5000, action=-1) at ../../korganizer/incidencechanger.cpp:276 #17 0xacb59cc8 in KOTodoEditor::processInput (this=0xd05ec50) at ../../korganizer/kotodoeditor.cpp:258 #18 0xacb547e9 in KOIncidenceEditor::slotButtonClicked (this=0xd05ec50, button=4) at ../../korganizer/koincidenceeditor.cpp:102 #19 0xb7d20332 in KDialog::qt_metacall (this=0xd05ec50, _c=QMetaObject::InvokeMetaMethod, _id=33, _a=0xbfd8fdcc) at ./kdialog.moc:184 #20 0xb7de58ea in KPageDialog::qt_metacall (this=0xd05ec50, _c=QMetaObject::InvokeMetaMethod, _id=69, _a=0xbfd8fdcc) at ./kpagedialog.moc:64 #21 0xacb550ba in KOIncidenceEditor::qt_metacall (this=0xd05ec50, _c=QMetaObject::InvokeMetaMethod, _id=69, _a=0xbfd8fdcc) at ./koincidenceeditor.moc:107 #22 0xacb5a27a in KOTodoEditor::qt_metacall (this=0xd05ec50, _c=QMetaObject::InvokeMetaMethod, _id=69, _a=0xbfd8fdcc) at ./kotodoeditor.moc:65 #23 0xb78cbb33 in QMetaObject::activate (sender=0xcf849f0, from_signal_index=4, to_signal_index=4, argv=0xbfd8fdcc) at kernel/qobject.cpp:3112 #24 0xb78cc782 in QMetaObject::activate (sender=0xcf849f0, m=0xb79a6d58, local_signal_index=0, argv=0xbfd8fdcc) at kernel/qobject.cpp:3186 #25 0xb78cf3a3 in QSignalMapper::mapped (this=0xcf849f0, _t1=4) at .moc/release-shared/moc_qsignalmapper.cpp:95 #26 0xb78cfc2d in QSignalMapper::map (this=0xcf849f0, sender=0xc237298) at kernel/qsignalmapper.cpp:266 #27 0xb78cfe1e in QSignalMapper::map (this=0xcf849f0) at kernel/qsignalmapper.cpp:257 #28 0xb78d06eb in QSignalMapper::qt_metacall (this=0xcf849f0, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbfd8ff4c) at .moc/release-shared/moc_qsignalmapper.cpp:81 #29 0xb78cbb33 in QMetaObject::activate (sender=0xc237298, from_signal_index=29, to_signal_index=30, argv=0xbfd8ff4c) at kernel/qobject.cpp:3112 #30 0xb78cbf60 in QMetaObject::activate (sender=0xc237298, m=0xb775f924, from_local_signal_index=2, to_local_signal_index=3, argv=0xbfd8ff4c) at kernel/qobject.cpp:3206 #31 0xb75789a1 in QAbstractButton::clicked (this=0xc237298, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:200 #32 0xb72a4379 in QAbstractButtonPrivate::emitClicked (this=0xd47bcc8) at widgets/qabstractbutton.cpp:543 #33 0xb72a5f64 in QAbstractButtonPrivate::click (this=0xd47bcc8) at widgets/qabstractbutton.cpp:536 #34 0xb72a61f6 in QAbstractButton::mouseReleaseEvent (this=0xc237298, e=0xbfd905ec) at widgets/qabstractbutton.cpp:1115 #35 0xb6f4c77b in QWidget::event (this=0xc237298, event=0xbfd905ec) at kernel/qwidget.cpp:7549 #36 0xb72a421e in QAbstractButton::ev
[Bug 67504] IMAP IDLE support for KMail
https://bugs.kde.org/show_bug.cgi?id=67504 Ritesh Raj Sarraf changed: What|Removed |Added CC||r...@researchut.com -- 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 39097] Better handling for error messages and dialogs
https://bugs.kde.org/show_bug.cgi?id=39097 --- Comment #37 from Ritesh Raj Sarraf 2009-07-08 04:58:40 --- (In reply to comment #36) > SVN commit 992911 by tmcguire: > > By default, use passive popups when you get an error when checking mail. > You can configure this in the notification dialog. > > BUG: 39097 > > > M +10 -3 imapaccountbase.cpp > M +5 -0 kmail.notifyrc > M +8 -1 popaccount.cpp > > > WebSVN link: http://websvn.kde.org/?view=rev&revision=992911 Thank you ** 100 -- 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 188838] New: add newsgroup categorization under folders
https://bugs.kde.org/show_bug.cgi?id=188838 Summary: add newsgroup categorization under folders Product: knode Version: unspecified Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: r...@researchut.com Version: 0.99.01 (using 4.2.1 (KDE 4.2.1), Debian packages) Compiler: cc OS:Linux (i686) release 2.6.29-custom Problem: Currently, in knode, a user can subscribe to newsgroups and rename the news group to his liking. If there are many news groups, the list becomes cluttered and it is difficult to focus on the high priority ones. One workaround I currently use is to rename news groups to something like N - NewsGroupName This helps me prioritize the news groups on the basis on N. Before I move further, I'd like the explain the wishlist first. Akregator has this feature where I can subscribe to hundreds of news feeds and categorize them under individual folders. Given the above problem statement, what I do in akregator is is that I add folders like 1 Priority, 2 Priority and so on. And now I had my favorite feeds to the relevant folders. Currently, I have 5 priority 1 feeds. All are high volume. To be fair that none of the priority 1 feeds get starved, I access the feeds from the "1 Priority" folder. This way I get a fair date wise feed list for all priority 1 feeds. This is a very cool feature. My wishlist request is to have a similar model in knode wherein we could add favorite newsgroups to individual folders and then get a collective listing of all news in the folder itself. -- 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 187303] Sorting of events is not in order
https://bugs.kde.org/show_bug.cgi?id=187303 --- Comment #1 from Ritesh Raj Sarraf 2009-03-16 13:29:02 --- Created an attachment (id=32164) --> (http://bugs.kde.org/attachment.cgi?id=32164) Kontact Summary Event Ordering Bug -- 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 187303] New: Sorting of events is not in order
https://bugs.kde.org/show_bug.cgi?id=187303 Summary: Sorting of events is not in order Product: kontact Version: unspecified Platform: Debian testing OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: summary AssignedTo: kdepim-bugs@kde.org ReportedBy: r...@researchut.com Version:(using KDE 4.2.1) OS:Linux Installed from:Debian testing/unstable Packages Events which has passed in the day should be shown faded. Also events should be properly sorted. That is not the case currently in Kontact's summary. I've attached the Screenshot which explains. An event, which was at 2:30 AM is still displayed after an event which was at 14:00 hrs. Both should be shown faded as they have already passed (you can term that a wishlist) the system time. -- 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 177330] all rss applications use their own storage
http://bugs.kde.org/show_bug.cgi?id=177330 --- Comment #4 from Ritesh Raj Sarraf 2009-02-11 20:44:18 --- (In reply to comment #3) > "As a user", you shouldn't have to care about how applications or widgets > store > their datas... > > This is clearly not a user question nor a bug. > I should. Duplication of data is something that affects the user also. Configuring the same rss sites at 3 different locations is not the right/smart thing. -- Configure bugmail: http://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 177330] all rss applications use their own storage
http://bugs.kde.org/show_bug.cgi?id=177330 Ritesh Raj Sarraf rrs researchut com changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|INVALID | --- Comment #2 from Ritesh Raj Sarraf 2009-02-11 13:37:18 --- It is already a messy situation currently with 4.2. There are 2 plasmoids and akregator, so a total of 3 apps, all storing rss feed source in different places. Before 4.x, Aaron had mentioned that all rss apps should have a common store. I'm not sure what happened to that thought. I'm re-opening it because, I as a User, can't see a better place to file bugs/wishlists, and track them. Please don't expect a user to track devel/core-devel. -- Configure bugmail: http://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: don't mark message as read in pop3 download
Looks like the KDE Bugzilla has some problems. I tried twice and was not able to report a bug. Use Case You download mails from a server using dimap. The server has auto-archiving enabled. This ends up with your dimap cache also having archived emails than having pristine copies of the email. Workaround Configure a POP3 account with the same server. Configure it to leave message on the server after download. This way you can have a pristine copy of the email while also access the email using dimap. Problem When POP3 fetches mails, it marks them as read. If then you see the message listing in dimap, you lost track of new unread messages. Wishlist Add an option for POP3 to "Leave messages as it is on the server". Example User Me. I use dimap with MS Exchange to be able to browse through my email messages. My Exchange server has an auto archive policy which archives old messages on the server after N days. This becomes a problem when I need to search an old email and I don't have the pristine copy in my dimap cache. As mentioned above, POP3 is a workaround for a scenario like this. But it mangles the state of messages on the server. Ritesh -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com "Necessity is the mother of invention." signature.asc Description: This is a digitally signed message part. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 165965] startup problems in kontact
http://bugs.kde.org/show_bug.cgi?id=165965 Ritesh Raj Sarraf rrs researchut com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||WORKSFORME --- Comment #6 from Ritesh Raj Sarraf 2008-12-16 11:30:30 --- I'm closing this bug as I don't see the problem with the latest KDEPIM. -- Configure bugmail: http://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 177893] long subjectline doesn't get a line break in the summary page
http://bugs.kde.org/show_bug.cgi?id=177893 --- Comment #1 from Ritesh Raj Sarraf 2008-12-16 11:28:53 --- Created an attachment (id=29375) --> (http://bugs.kde.org/attachment.cgi?id=29375) Kontact Ugly Summary -- Configure bugmail: http://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 177893] New: long subjectline doesn't get a line break in the summary page
http://bugs.kde.org/show_bug.cgi?id=177893 Summary: long subjectline doesn't get a line break in the summary page Product: kontact Version: unspecified Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: r...@researchut.com Version:(using Devel) OS:Linux Installed from:Compiled sources Someone send me a Meeting Request with a very long Subject Line. When that Meeting Request is reflect in my Kontact Summary Page, things look ugly. Attached screen shot will explain better. -- Configure bugmail: http://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 177330] New: all rss applications use their own storage
http://bugs.kde.org/show_bug.cgi?id=177330 Summary: all rss applications use their own storage Product: kdepimlibs Version: 4.1 Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: syndication AssignedTo: kdepim-bugs@kde.org ReportedBy: [EMAIL PROTECTED] Version:(using Devel) OS:Linux Installed from:Compiled sources Sorry if it is the wrong component. Some time back, it was told that all rss applications were going to use a common rss backend, probably libakregator or librss kind of thing. I just checked on KDE 4.2 Beta 1 and still all apps use their own rrs storage. This ends up requiring adding the same rss feed at multiple locations. The applications I checked include: * Akregator * RSSNow Plasmoid * News Plasmoid Is this feature been postponed to a future milestone ? -- Configure bugmail: http://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 170594] crash when selecting messages
http://bugs.kde.org/show_bug.cgi?id=170594 --- Comment #2 from Ritesh Raj Sarraf 2008-09-07 10:06:50 --- Okay! It looks like the crash is only triggered when selecting the email message which is a Microsoft Outlook Meeting Request. -- Configure bugmail: http://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 170594] crash when selecting messages
http://bugs.kde.org/show_bug.cgi?id=170594 --- Comment #1 from Ritesh Raj Sarraf 2008-09-07 09:57:43 --- Application: Kontact (kontact), signal SIGSEGV [Thread debugging using libthread_db enabled] [New Thread 0xb7f9a700 (LWP 5399)] [KCrash handler] #6 KCal::Incidence::revision (this=) at /tmp/buildd/kdepimlibs-4.1.1/kcal/incidence.cpp:322 #7 0xb4d6f3dc in format (this=0xa31d5a8, bodyPart=0xbfeca6b8, writer=0x9faee88) at /tmp/buildd/kdepim-4.1.1/plugins/kmail/bodypartformatter/text_calendar.cpp:163 #8 0x49d032d6 in KMail::ObjectTreeParser::parseObjectTree ( this=, node=) at /tmp/buildd/kdepim-4.1.1/kmail/objecttreeparser.cpp:267 #9 0x49d03f07 in KMail::ObjectTreeParser::stdChildHandling ( this=, child=) at /tmp/buildd/kdepim-4.1.1/kmail/objecttreeparser.cpp:1088 #10 0x49d04128 in KMail::ObjectTreeParser::processMultiPartAlternativeSubtype (this=, node=) at /tmp/buildd/kdepim-4.1.1/kmail/objecttreeparser.cpp:1130 #11 0x49d119fb in process (this=) at /tmp/buildd/kdepim-4.1.1/kmail/bodypartformatter.cpp:119 #12 0x49d03578 in KMail::ObjectTreeParser::parseObjectTree ( this=, node=) at /tmp/buildd/kdepim-4.1.1/kmail/objecttreeparser.cpp:289 #13 0x49b64d4f in KMReaderWin::parseMsg (this=, aMsg=) at /tmp/buildd/kdepim-4.1.1/kmail/kmreaderwin.cpp:1558 #14 0x49b5e370 in KMReaderWin::displayMessage (this=) at /tmp/buildd/kdepim-4.1.1/kmail/kmreaderwin.cpp:1489 #15 0x49b5e570 in KMReaderWin::updateReaderWin (this=) at /tmp/buildd/kdepim-4.1.1/kmail/kmreaderwin.cpp:1429 #16 0x49b644c0 in KMReaderWin::qt_metacall (this=, _c=, _id=, _a=) at /tmp/buildd/kdepim-4.1.1/obj-i486-linux-gnu/kmail/kmreaderwin.moc:162 #17 0x41831ed0 in QMetaObject::activate (sender=, from_signal_index=, to_signal_index=, argv=) at kernel/qobject.cpp:3016 #18 0x41832c52 in QMetaObject::activate (sender=, m=, local_signal_index=, argv=) at kernel/qobject.cpp:3086 #19 0x4186cbc7 in QTimer::timeout (this=) at .moc/release-shared/moc_qtimer.cpp:126 #20 0x4183887e in QTimer::timerEvent (this=, e=) at kernel/qtimer.cpp:263 #21 0x4182c9af in QObject::event (this=, e=) at kernel/qobject.cpp:1105 #22 0x41f19b8c in QApplicationPrivate::notify_helper ( this=, receiver=, e=) at kernel/qapplication.cpp:3800 #23 0x41f219fe in QApplication::notify (this=, receiver=, e=) at kernel/qapplication.cpp:3392 #24 0x4a5a297d in KApplication::notify (this=, receiver=, event=) at /tmp/buildd/kde4libs-4.1.1/kdeui/kernel/kapplication.cpp:311 #25 0x4181d3af in QCoreApplication::notifyInternal ( this=, receiver=, event=) at kernel/qcoreapplication.cpp:591 #26 0x4184b341 in QTimerInfoList::activateTimers (this=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #27 0x4184b5db in QEventDispatcherUNIX::processEvents ( this=, flags=) at kernel/qeventdispatcher_unix.cpp:899 #28 0x41fb3bc6 in QEventDispatcherX11::processEvents ( this=, flags=) at kernel/qeventdispatcher_x11.cpp:154 #29 0x4181ba7a in QEventLoop::processEvents (this=, flags=) at kernel/qeventloop.cpp:149 #30 0x4181bc3a in QEventLoop::exec (this=, flags=) at kernel/qeventloop.cpp:200 #31 0x4181e2f5 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:849 #32 0x41f19a07 in QApplication::exec () at kernel/qapplication.cpp:3330 #33 0x0804bdd2 in main (argc=1, argv=0xbfecb7c4) at /tmp/buildd/kdepim-4.1.1/kontact/src/main.cpp:218 #0 0xb7fcb424 in __kernel_vsyscall () -- Configure bugmail: http://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 170594] New: crash when selecting messages
http://bugs.kde.org/show_bug.cgi?id=170594 Summary: crash when selecting messages Product: kmail Version: unspecified Platform: Debian testing OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: [EMAIL PROTECTED] Version:(using KDE 4.1.1) OS:Linux Installed from:Debian testing/unstable Packages While trying to select message using Shift + Arrow, Kmail crashed. -- Configure bugmail: http://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 169310] New: kontact summary plugin doesn't respect korganizer's timezone settings
--- 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=169310 Summary: kontact summary plugin doesn't respect korganizer's timezone settings Product: kontact Version: unspecified Platform: Debian testing OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: rrs researchut com Version:(using KDE 4.1.0) Installed from:Debian testing/unstable Packages OS:Linux Korganizer has an option to define your timezone when your system clock uses UTC. For me, Korganizer is able to calculate the time properly for whatever timezone I've selected. But the same calendar events, in Kontact's Summary, are displayed in UTC. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 168991] line breaks are ignored when composing an html message
--- 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=168991 --- Additional Comments From rrs researchut com 2008-08-12 19:53 --- And this is not specific to signed messages. Unsigned messages also have the same problem. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 168991] line breaks are ignored when composing an html message
--- 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=168991 --- Additional Comments From rrs researchut com 2008-08-12 19:51 --- Created an attachment (id=26807) --> (http://bugs.kde.org/attachment.cgi?id=26807&action=view) kmail screenshot ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 168991] New: line breaks are ignored when composing an html message
--- 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=168991 Summary: line breaks are ignored when composing an html message Product: kmail Version: unspecified Platform: Debian testing OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: rrs researchut com Version:(using KDE 4.1.0) Installed from:Debian testing/unstable Packages OS:Linux When using kmail composer to compose an HTML message, when I display the email after it has been sent, I see no line breaks. And in fact when replying to html messages, things are much much more ugly. I'll try to provide more information ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 167896] kmail crash during setting changes in Composer window
--- 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=167896 --- Additional Comments From rrs researchut com 2008-07-31 21:47 --- Application: Kontact (kontact), signal SIGSEGV [Thread debugging using libthread_db enabled] [New Thread 0xb7fd0720 (LWP 11163)] [New Thread 0xb487ab90 (LWP 11186)] [KCrash handler] #6 0x41d762de in QTreeViewPrivate::rowsRemoved (this=, parent=, start=, end=, after=) at ../../include/QtCore/../../src/corelib/tools/qalgorithms.h:84 #7 0x41d76635 in QTreeView::rowsAboutToBeRemoved (this=) at itemviews/qtreeview.cpp:2425 #8 0x41d3e0ef in QAbstractItemView::qt_metacall (this=, _c=, _id=, _a=) at .moc/release-shared/moc_qabstractitemview.cpp:225 #9 0x41d8031a in QTreeView::qt_metacall (this=, _c=, _id=, _a=) at .moc/release-shared/moc_qtreeview.cpp:121 #10 0x41db88ea in QTreeWidget::qt_metacall (this=, _c=, _id=, _a=) at .moc/release-shared/moc_qtreewidget.cpp:123 #11 0x433dc6fa in KPIM::TreeWidget::qt_metacall (this=, _c=, _id=, _a=) at /tmp/buildd/kdepim-4.1.0/obj-i486-linux-gnu/libkdepim/moc_treewidget.cpp:63 #12 0x441d028a in KMMimePartTree::qt_metacall (this=, _c=, _id=, _a=) at /tmp/buildd/kdepim-4.1.0/obj-i486-linux-gnu/kmail/kmmimeparttree.moc:78 #13 0x412830c0 in QMetaObject::activate (sender=, from_signal_index=, to_signal_index=, argv=) at kernel/qobject.cpp:3010 #14 0x41283e42 in QMetaObject::activate (sender=, m=, local_signal_index=, argv=) at kernel/qobject.cpp:3080 #15 0x412bd0df in QAbstractItemModel::rowsAboutToBeRemoved (this=) at .moc/release-shared/moc_qabstractitemmodel.cpp:164 #16 0x41268f52 in QAbstractItemModel::beginRemoveRows ( this=, parent=, first=) at kernel/qabstractitemmodel.cpp:2121 #17 0x41daca59 in QTreeModel::beginRemoveItems (this=, parent=, row=, count=) at itemviews/qtreewidget.cpp:815 #18 0x41db125f in QTreeWidgetItem::takeChild (this=, index=) at itemviews/qtreewidget.cpp:1923 #19 0x441ce794 in KMMimePartTreeItem (this=, parent=, node=, description=, mimetype=, encoding=, size=, revertOrder=) at /tmp/buildd/kdepim-4.1.0/kmail/kmmimeparttree.cpp:393 #20 0x4420e8e4 in partNode::fillMimePartTree (this=, parentItem=, mimePartTree=, labelDescr=, labelCntType=, labelEncoding=, size=, revertOrder=) at /tmp/buildd/kdepim-4.1.0/kmail/partNode.cpp:505 #21 0x4420e98f in partNode::fillMimePartTree (this=, parentItem=, mimePartTree=, labelDescr=, labelCntType=, labelEncoding=, size=, revertOrder=) at /tmp/buildd/kdepim-4.1.0/kmail/partNode.cpp:517 #22 0x4405d0b4 in KMReaderWin::parseMsg (this=, aMsg=) at /tmp/buildd/kdepim-4.1.0/kmail/kmreaderwin.cpp:1530 #23 0x440569c0 in KMReaderWin::displayMessage (this=) at /tmp/buildd/kdepim-4.1.0/kmail/kmreaderwin.cpp:1486 #24 0x44056bc0 in KMReaderWin::updateReaderWin (this=) at /tmp/buildd/kdepim-4.1.0/kmail/kmreaderwin.cpp:1426 #25 0x44057679 in KMReaderWin::setMsg (this=, aMsg=, force=) at /tmp/buildd/kdepim-4.1.0/kmail/kmreaderwin.cpp:1228 #26 0x44048580 in KMReaderWin::update (this=, force=) at /tmp/buildd/kdepim-4.1.0/kmail/kmreaderwin.cpp:2430 #27 0x4404b454 in KMReaderWin::readConfig (this=) at /tmp/buildd/kdepim-4.1.0/kmail/kmreaderwin.cpp:942 #28 0x44252615 in KMMainWidget::readConfig (this=) at /tmp/buildd/kdepim-4.1.0/kmail/kmmainwidget.cpp:607 #29 0x44240254 in KMMainWidget::slotConfigChanged (this=) at /tmp/buildd/kdepim-4.1.0/kmail/kmmainwidget.cpp:1947 #30 0x4426a7bf in KMMainWidget::qt_metacall (this=, _c=, _id=, _a=) at /tmp/buildd/kdepim-4.1.0/obj-i486-linux-gnu/kmail/kmmainwidget.moc:464 #31 0x412830c0 in QMetaObject::activate (sender=, from_signal_index=, to_signal_index=, argv=) at kernel/qobject.cpp:3010 #32 0x41283e42 in QMetaObject::activate (sender=, m=, local_signal_index=, argv=) at kernel/qobject.cpp:3080 #33 0x4416c5b7 in KMKernel::configChanged (this=) at /tmp/buildd/kdepim-4.1.0/obj-i486-linux-gnu/kmail/kmkernel.moc:246 #34 0x4416cbda in KMKernel::slotConfigChanged (this=) at /tmp/buildd/kdepim-4.1.0/kmail/kmkernel.cpp:1914 #35 0x4417f1a5 in KMKernel::qt_metacall (this=, _c=, _id=, _a=) at /tmp/buildd/kdepim-4.1.0/obj-i486-linux-gnu/kmail/kmkernel.moc:226 #36 0x412830c0 in QMetaObject::activate (sender=, from_signal_index=, to_signal_index=, argv=) at kernel/qobject.cpp:3010 #37 0x41283e42 in QMetaObject::activate (sender=, m=, local_signal_index=, argv=) at kernel/qobject.cpp:3080 #38 0x42e81777 in KCMultiDialog::configCommitted (this=) at /tmp/buildd/kde4libs-4.1.0/obj-i486-linux-gnu/kutils/kcmultidialog.moc:101 #39 0x42e81bd3 in KCMultiDialogPrivate::apply (this=) at /tmp/buildd/kde4libs-4.1.0/kutils/kcmultidialog.
[Bug 167896] New: kmail crash during setting changes in Composer window
--- 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=167896 Summary: kmail crash during setting changes in Composer window Product: kmail Version: unspecified Platform: Debian testing OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: rrs researchut com Version:(using KDE 4.1.0) Installed from:Debian testing/unstable Packages OS:Linux kmail crashed for me when doing some Composer setting changes in Composer Settings window ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 167745] it's not possible to start kmail more than once in a kde session
--- 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=167745 rrs researchut com changed: What|Removed |Added CC||rrs researchut com --- Additional Comments From rrs researchut com 2008-07-31 20:27 --- I too am using Debian with KDE 4.1 and neither kmail nor kontact works for me. One KDE startup, kmail autostarts. Then I quit kmail. But the kmail process never dies. And then kontact can start, but I cannot open the kmail module in the kontact shell. It will always open externally. Only option left is to exit both kmail and kontact, and then manually pkill the kmail pid and then start kontact. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 167888] kontact crashed when running the anti-spam wizard
--- 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=167888 --- Additional Comments From rrs researchut com 2008-07-31 20:22 --- It is kmail that is crashing. Application: Kontact (kontact), signal SIGSEGV [Thread debugging using libthread_db enabled] [New Thread 0xb7f5e720 (LWP 7856)] [New Thread 0xb4a05b90 (LWP 7877)] [KCrash handler] #6 KMFilterMgr::appendFilters (this=, filters=, replaceIfNameExists=) at /usr/include/qt4/QtCore/qstring.h:676 #7 0x442bf358 in KMail::AntiSpamWizard::accept (this=) at /tmp/buildd/kdepim-4.1.0/kmail/antispamwizard.cpp:456 #8 0x41cdfd96 in QDialog::qt_metacall (this=, _c=, _id=, _a=) at .moc/release-shared/moc_qdialog.cpp:87 #9 0x4263f4ea in KDialog::qt_metacall (this=, _c=, _id=, _a=) at /tmp/buildd/kde4libs-4.1.0/obj-i486-linux-gnu/kdeui/kdialog.moc:142 #10 0x4270c33a in KPageDialog::qt_metacall (this=, _c=, _id=, _a=) at /tmp/buildd/kde4libs-4.1.0/obj-i486-linux-gnu/kdeui/kpagedialog.moc:63 #11 0x42628aea in KAssistantDialog::qt_metacall (this=, _c=, _id=, _a=) at /tmp/buildd/kde4libs-4.1.0/obj-i486-linux-gnu/kdeui/kassistantdialog.moc:63 #12 0x442c35da in KMail::AntiSpamWizard::qt_metacall ( this=, _c=, _id=, _a=) at /tmp/buildd/kdepim-4.1.0/obj-i486-linux-gnu/kmail/antispamwizard.moc:67 #13 0x412830c0 in QMetaObject::activate (sender=, from_signal_index=, to_signal_index=, argv=) at kernel/qobject.cpp:3010 #14 0x41283e42 in QMetaObject::activate (sender=, m=, local_signal_index=, argv=) at kernel/qobject.cpp:3080 #15 0x4263c4d7 in KDialog::user1Clicked (this=) at /tmp/buildd/kde4libs-4.1.0/obj-i486-linux-gnu/kdeui/kdialog.moc:229 #16 0x4263f20d in KDialog::slotButtonClicked (this=, button=) at /tmp/buildd/kde4libs-4.1.0/kdeui/dialogs/kdialog.cpp:860 #17 0x4263f554 in KDialog::qt_metacall (this=, _c=, _id=, _a=) at /tmp/buildd/kde4libs-4.1.0/obj-i486-linux-gnu/kdeui/kdialog.moc:181 #18 0x4270c33a in KPageDialog::qt_metacall (this=, _c=, _id=, _a=) at /tmp/buildd/kde4libs-4.1.0/obj-i486-linux-gnu/kdeui/kpagedialog.moc:63 #19 0x42628aea in KAssistantDialog::qt_metacall (this=, _c=, _id=, _a=) at /tmp/buildd/kde4libs-4.1.0/obj-i486-linux-gnu/kdeui/kassistantdialog.moc:63 #20 0x442c35da in KMail::AntiSpamWizard::qt_metacall ( this=, _c=, _id=, _a=) at /tmp/buildd/kdepim-4.1.0/obj-i486-linux-gnu/kmail/antispamwizard.moc:67 #21 0x412830c0 in QMetaObject::activate (sender=, from_signal_index=, to_signal_index=, argv=) at kernel/qobject.cpp:3010 #22 0x41283e42 in QMetaObject::activate (sender=, m=, local_signal_index=, argv=) at kernel/qobject.cpp:3080 #23 0x41286f53 in QSignalMapper::mapped (this=) at .moc/release-shared/moc_qsignalmapper.cpp:93 #24 0x412877dd in QSignalMapper::map (this=, sender=) at kernel/qsignalmapper.cpp:277 #25 0x412879ce in QSignalMapper::map (this=) at kernel/qsignalmapper.cpp:268 #26 0x4128829b in QSignalMapper::qt_metacall (this=, _c=, _id=, _a=) at .moc/release-shared/moc_qsignalmapper.cpp:80 #27 0x412830c0 in QMetaObject::activate (sender=, from_signal_index=, to_signal_index=, argv=) at kernel/qobject.cpp:3010 #28 0x412834c0 in QMetaObject::activate (sender=, m=, from_local_signal_index=, to_local_signal_index=, argv=) at kernel/qobject.cpp:3100 #29 0x41e5eea1 in QAbstractButton::clicked (this=) at .moc/release-shared/moc_qabstractbutton.cpp:185 #30 0x41bb4859 in QAbstractButtonPrivate::emitClicked ( this=) at widgets/qabstractbutton.cpp:543 #31 0x41bb63c4 in QAbstractButtonPrivate::click (this=) at widgets/qabstractbutton.cpp:536 #32 0x41bb6656 in QAbstractButton::mouseReleaseEvent ( this=, e=) at widgets/qabstractbutton.cpp:1112 #33 0x418d5572 in QWidget::event (this=, event=) at kernel/qwidget.cpp:6927 #34 0x41bb46fe in QAbstractButton::event (this=, e=) at widgets/qabstractbutton.cpp:1074 #35 0x41c5a640 in QPushButton::event (this=, e=) at widgets/qpushbutton.cpp:658 #36 0x4187d6ec in QApplicationPrivate::notify_helper ( this=, receiver=, e=) at kernel/qapplication.cpp:3772 #37 0x41885e71 in QApplication::notify (this=, receiver=, e=) at kernel/qapplication.cpp:3501 #38 0x426db5ed in KApplication::notify (this=, receiver=, event=) at /tmp/buildd/kde4libs-4.1.0/kdeui/kernel/kapplication.cpp:311 #39 0x4126e571 in QCoreApplication::notifyInternal ( this=, receiver=, event=) at kernel/qcoreapplication.cpp:587 #40 0x418850fe in QApplicationPrivate::sendMouseEvent ( receiver=, event=, alienWidget=, nativeWidget=, buttonDown=, lastMouseReceiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218 #41 0x418ee67d in QETWidget::translateMouseEvent (this=, event=) at kern
[Bug 167888] New: kontact crashed when running the anti-spam wizard
--- 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=167888 Summary: kontact crashed when running the anti-spam wizard Product: kontact Version: unspecified Platform: Debian testing OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: rrs researchut com Version:(using KDE 4.1.0) Installed from:Debian testing/unstable Packages OS:Linux When I ran the Anti-Spam wizard, after the spam wizard is run, I select a folder on a Disconnected IMAP account to store spam messages. As soon as I click Ok, Kontact crashes ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 165965] startup problems in kontact
--- 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=165965 --- Additional Comments From rrs researchut com 2008-07-31 08:23 --- rrs learner:~$ kontact kontact(10129) KWallet::Wallet::openWallet: Pass a valid window to KWallet::Wallet::openWallet(). kontact(10129) KDBusServiceStarter::findServiceFor: DBus service is available now, as "org.kde.kmail" kontact(10129) KDBusServiceStarter::findServiceFor: DBus service is available now, as "org.kde.kmail" kontact(10129) Kolab::Incidence::loadAttribute: Saving unhandled tag "inline-attachment" (10128)/: Communication problem with "kontact" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." " ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 165965] startup problems in kontact
--- 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=165965 --- Additional Comments From rrs researchut com 2008-07-31 07:46 --- I've re-installed KDE 4.1 and this issue is back again. On a fresh user account this issue is not seen. But for the user, which was running kDE3 earlier, this issue is there. I find the following in .xsession-errors rrs learner:~$ grep -i kmail .xsession-errors kopete(4599) KDBusServiceStarter::findServiceFor: DBus service is available now, as "org.kde.kmail" korgac(4629) KDBusServiceStarter::findServiceFor: DBus service is available now, as "org.kde.kmail" krunner(4533) KDBusServiceStarter::findServiceFor: DBus service is available now, as "org.kde.kmail" ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 165965] startup problems in kontact
--- 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=165965 --- Additional Comments From rrs researchut com 2008-07-08 17:22 --- rrs learner:~$ kontact kontact(28581) KWallet::Wallet::openWallet: Pass a valid window to KWallet::Wallet::openWallet(). kontact(28581) KDBusServiceStarter::findServiceFor: DBus service is available now, as "org.kde.kmail" kontact(28581) ViewManager::setActiveView: entering ViewManager::setActiveView kontact(28581) KStatusBar::removeItem: KStatusBar::removeItem: bad item id: 1 kontact(28581) KStatusBar::removeItem: KStatusBar::removeItem: bad item id: 2 kontact(28581) KStatusBar::removeItem: KStatusBar::removeItem: bad item id: 1 kontact(28581) KStatusBar::removeItem: KStatusBar::removeItem: bad item id: 2 kontact(28581) KDBusServiceStarter::findServiceFor: DBus service is available now, as "org.kde.kmail" kontact(28581) Kolab::Incidence::loadAttribute: Saving unhandled tag "inline-attachment" (28580)/: Communication problem with "kontact" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or thenetwork connection was broken." " ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 165965] startup problems in kontact
--- 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=165965
--- Additional Comments From rrs researchut com 2008-07-07 20:16 ---
Application: Kontact (kontact), signal SIGSEGV
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb4d54720 (LWP 7516)]
[New Thread 0xb07feb90 (LWP 7794)]
[KCrash handler]
#6 0xb708ac8f in KJob::kill (this=0x92e1fa8, verbosity=KJob::EmitResult)
at /tmp/buildd/kde4libs-4.0.84+svn828328/kdecore/jobs/kjob.cpp:106
#7 0xb7c80c62 in KAbstractWidgetJobTracker::slotStop (this=0x9acabf8,
job=0x92e1fa8)
at
/tmp/buildd/kde4libs-4.0.84+svn828328/kdeui/jobs/kabstractwidgetjobtracker.cpp:129
#8 0xb7c81942 in KWidgetJobTracker::Private::ProgressWidget::_k_stop (
this=0x9ca15f0)
at
/tmp/buildd/kde4libs-4.0.84+svn828328/kdeui/jobs/kwidgetjobtracker.cpp:629
#9 0xb7c82aab in KWidgetJobTracker::Private::ProgressWidget::qt_metacall (
this=0x9ca15f0, _c=QMetaObject::InvokeMetaMethod, _id=13, _a=0xbfab061c)
at
/tmp/buildd/kde4libs-4.0.84+svn828328/obj-i486-linux-gnu/kdeui/kwidgetjobtracker_p.moc:101
#10 0xb6ee0090 in QMetaObject::activate (sender=0x9cc7af0,
from_signal_index=29, to_signal_index=30, argv=0xbfab061c)
at kernel/qobject.cpp:3010
#11 0xb6ee0490 in QMetaObject::activate (sender=0x9cc7af0, m=0xb7aabc44,
from_local_signal_index=2, to_local_signal_index=3, argv=0xbfab061c)
at kernel/qobject.cpp:3100
#12 0xb78e2da1 in QAbstractButton::clicked (this=0x9cc7af0, _t1=false)
at .moc/release-shared/moc_qabstractbutton.cpp:185
#13 0xb7638789 in QAbstractButtonPrivate::emitClicked (this=0x9cc7b40)
at widgets/qabstractbutton.cpp:543
#14 0xb763a2f4 in QAbstractButtonPrivate::click (this=0x9cc7b40)
at widgets/qabstractbutton.cpp:536
#15 0xb763a586 in QAbstractButton::mouseReleaseEvent (this=0x9cc7af0,
e=0xbfab0cbc) at widgets/qabstractbutton.cpp:1112
#16 0xb73594f2 in QWidget::event (this=0x9cc7af0, event=0xbfab0cbc)
at kernel/qwidget.cpp:6927
#17 0xb763862e in QAbstractButton::event (this=0x9cc7af0, e=0xbfab0cbc)
at widgets/qabstractbutton.cpp:1074
#18 0xb76de570 in QPushButton::event (this=0x9cc7af0, e=0xbfab0cbc)
at widgets/qpushbutton.cpp:658
#19 0xb730166c in QApplicationPrivate::notify_helper (this=0x9061a28,
receiver=0x9cc7af0, e=0xbfab0cbc) at kernel/qapplication.cpp:3772
#20 0xb7309df1 in QApplication::notify (this=0xbfab158c, receiver=0x9cc7af0,
e=0xbfab0cbc) at kernel/qapplication.cpp:3501
#21 0xb7c8dfdd in KApplication::notify (this=0xbfab158c, receiver=0x9cc7af0,
event=0xbfab0cbc)
at /tmp/buildd/kde4libs-4.0.84+svn828328/kdeui/kernel/kapplication.cpp:311
#22 0xb6ecb541 in QCoreApplication::notifyInternal (this=0xbfab158c,
receiver=0x9cc7af0, event=0xbfab0cbc) at kernel/qcoreapplication.cpp:587
#23 0xb730907e in QApplicationPrivate::sendMouseEvent (receiver=0x9cc7af0,
event=0xbfab0cbc, alienWidget=0x9cc7af0, nativeWidget=0x9ca15f0,
buttonDown=0xb7ab77d0, lastMouseReceiver= 0xb7ab77d4)
at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#24 0xb73725fd in QETWidget::translateMouseEvent (this=0x9ca15f0,
event=0xbfab11ac) at kernel/qapplication_x11.cpp:4133
#25 0xb73713cf in QApplication::x11ProcessEvent (this=0xbfab158c,
event=0xbfab11ac) at kernel/qapplication_x11.cpp:3255
#26 0xb739ad14 in x11EventSourceDispatch (s=0x90645e0, callback=0,
user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:148
#27 0xb570c978 in IA__g_main_context_dispatch (context=0x9063a58)
at /build/buildd/glib2.0-2.16.3/glib/gmain.c:2009
#28 0xb570fbce in g_main_context_iterate (context=0x9063a58, block=1,
dispatch=1, self=0x9060808)
at /build/buildd/glib2.0-2.16.3/glib/gmain.c:2642
#29 0xb571011c in IA__g_main_context_iteration (context=0x9063a58,
may_block=1) at /build/buildd/glib2.0-2.16.3/glib/gmain.c:2705
#30 0xb6ef5b48 in QEventDispatcherGlib::processEvents (this=0x905ca78, flags=
{i = -1079307432}) at kernel/qeventdispatcher_glib.cpp:325
#31 0xb739a415 in QGuiEventDispatcherGlib::processEvents (this=0x905ca78,
flags={i = -1079307384}) at kernel/qguieventdispatcher_glib.cpp:204
#32 0xb6ec9c2a in QEventLoop::processEvents (this=0xbfab1400, flags=
{i = -1079307320}) at kernel/qeventloop.cpp:149
#33 0xb6ec9dea in QEventLoop::exec (this=0xbfab1400, flags={i = -1079307256})
at kernel/qeventloop.cpp:200
#34 0xb6ecc495 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845
#35 0xb73014e7 in QApplication::exec () at kernel/qapplication.cpp:3304
#36 0x0804bd9e in main (argc=1, argv=0xbfab1784)
at /tmp/buildd/kdepim-4.0.84/kontact/src/main.cpp:210
#37 0xb6b60450 in __libc_start_main () from /lib/i686/cmov/libc.so.6
#38 0x0804a511 in _start ()
#0 0xb7f98424 in __kernel_vsyscall ()
[Bug 165965] New: startup problems in kontact
--- 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=165965 Summary: startup problems in kontact Product: kontact Version: unspecified Platform: Debian testing OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: rrs researchut com Version:(using KDE 4.0.83) Installed from:Debian testing/unstable Packages OS:Linux Recent updates of KDE has caused kontact to not start (or start very late). There is some dbus connection error. But eventually I've also started seeing crashes. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 38711] Threads with unread messages should be highlighted
--- 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=38711 rrs researchut com changed: What|Removed |Added CC||rrs researchut com --- Additional Comments From rrs researchut com 2008-07-03 15:30 --- This issue is still present in the latest kmail from KDE 4.1 Beta2 ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 165540] konquer crash over night
--- 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=165540
--- Additional Comments From rrs researchut com 2008-07-01 22:15 ---
Application: Kontact (kontact), signal SIGSEGV
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb4d99720 (LWP 16031)]
[New Thread 0xb09dab90 (LWP 16054)]
[KCrash handler]
#6 QString::operator= (this=0xb594150, other= 0xbfdf59e8)
at ../../include/QtCore/../../src/corelib/arch/qatomic_i386.h:134
#7 0xb6ec8e1f in QUrlPrivate::parse (this=0xb594100,
parseOptions=QUrlPrivate::ParseAndSet) at io/qurl.cpp:220
#8 0xb6eccf80 in QUrl::host (this=0xbfdf5abc) at io/qurl.cpp:4247
#9 0xb6a440b5 in KIO::SchedulerPrivate::slotScheduleCoSlave (this=0xa17afe8)
at /tmp/buildd/kde4libs-4.0.84/kio/kio/scheduler.cpp:884
#10 0xb6a4871e in KIO::Scheduler::qt_metacall (this=0xa15a378,
_c=QMetaObject::InvokeMetaMethod, _id=10, _a=0xbfdf5ba8)
at /tmp/buildd/kde4libs-4.0.84/obj-i486-linux-gnu/kio/scheduler.moc:105
#11 0xb6f26090 in QMetaObject::activate (sender=0xa17b004,
from_signal_index=4, to_signal_index=4, argv=0x0)
at kernel/qobject.cpp:3010
#12 0xb6f26e12 in QMetaObject::activate (sender=0xa17b004, m=0xb6ff3ae4,
local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3080
#13 0xb6f60f07 in QTimer::timeout (this=0xa17b004)
at .moc/release-shared/moc_qtimer.cpp:126
#14 0xb6f2cabe in QTimer::timerEvent (this=0xa17b004, e=0xbfdf604c)
at kernel/qtimer.cpp:263
#15 0xb6f20b7f in QObject::event (this=0xa17b004, e=0xbfdf604c)
at kernel/qobject.cpp:1105
#16 0xb734766c in QApplicationPrivate::notify_helper (this=0x9d05888,
receiver=0xa17b004, e=0xbfdf604c) at kernel/qapplication.cpp:3772
#17 0xb734f43e in QApplication::notify (this=0xbfdf767c, receiver=0xa17b004,
e=0xbfdf604c) at kernel/qapplication.cpp:3366
#18 0xb7cd3c8d in KApplication::notify (this=0xbfdf767c, receiver=0xa17b004,
event=0xbfdf604c)
at /tmp/buildd/kde4libs-4.0.84/kdeui/kernel/kapplication.cpp:311
#19 0xb6f11541 in QCoreApplication::notifyInternal (this=0xbfdf767c,
receiver=0xa17b004, event=0xbfdf604c) at kernel/qcoreapplication.cpp:587
#20 0xb6f3f5b1 in QTimerInfoList::activateTimers (this=0x9d08614)
at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#21 0xb6f3bbf0 in timerSourceDispatch (source=0x9d085e0)
at kernel/qeventdispatcher_glib.cpp:166
#22 0xb5751978 in IA__g_main_context_dispatch (context=0x9d07a98)
at /build/buildd/glib2.0-2.16.3/glib/gmain.c:2009
#23 0xb5754bce in g_main_context_iterate (context=0x9d07a98, block=1,
dispatch=1, self=0x9d05a08)
at /build/buildd/glib2.0-2.16.3/glib/gmain.c:2642
#24 0xb575511c in IA__g_main_context_iteration (context=0x9d07a98,
may_block=1) at /build/buildd/glib2.0-2.16.3/glib/gmain.c:2705
#25 0xb6f3bb48 in QEventDispatcherGlib::processEvents (this=0x9d05850, flags=
{i = -1075879496}) at kernel/qeventdispatcher_glib.cpp:325
#26 0xb73e0415 in QGuiEventDispatcherGlib::processEvents (this=0x9d05850,
flags={i = -1075879448}) at kernel/qguieventdispatcher_glib.cpp:204
#27 0xb6f0fc2a in QEventLoop::processEvents (this=0xbfdf625c, flags=
{i = -1075879384}) at kernel/qeventloop.cpp:149
#28 0xb6f0fdea in QEventLoop::exec (this=0xbfdf625c, flags={i = -1075879324})
at kernel/qeventloop.cpp:200
#29 0xb77a92f7 in QDialog::exec (this=0xa0f4d38) at dialogs/qdialog.cpp:453
#30 0xb7c4b7d4 in KMessageBox::createKMessageBox (dialog=0xa0f4d38,
icon= 0xbfdf64a8, text= 0xbfdf66a0, strlist= 0xbfdf659c, ask= 0xbfdf64fc,
checkboxReturn=0xbfdf651b, options={i = -1075878748},
details= 0xbfdf64f4, notifyType=QMessageBox::Information)
at /tmp/buildd/kde4libs-4.0.84/kdeui/dialogs/kmessagebox.cpp:303
#31 0xb7c4c761 in KMessageBox::createKMessageBox (dialog=0xa0f4d38,
icon=QMessageBox::Information, text= 0xbfdf66a0, strlist= 0xbfdf659c,
ask= 0xbfdf64fc, checkboxReturn=0xbfdf651b, options={i = -1075878664},
details= 0xbfdf64f4)
at /tmp/buildd/kde4libs-4.0.84/kdeui/dialogs/kmessagebox.cpp:154
#32 0xb7c4edaf in KMessageBox::informationListWId (parent_id=73400321,
text= 0xbfdf66a0, strlist= 0xbfdf659c, caption= 0xbfdf6690,
dontShowAgainName= 0xbfdf6684, options={i = -1075878560})
at /tmp/buildd/kde4libs-4.0.84/kdeui/dialogs/kmessagebox.cpp:1000
#33 0xb7c4ef48 in KMessageBox::informationList (parent=0x9d49678,
text= 0xbfdf66a0, strlist= 0xbfdf659c, caption= 0xbfdf6690,
dontShowAgainName= 0xbfdf6684, options={i = -1075878504})
at /tmp/buildd/kde4libs-4.0.84/kdeui/dialogs/kmessagebox.cpp:967
#34 0xb7c4efa8 in KMessageBox::information (parent=0x9d49678,
text= 0xbfdf66a0, caption= 0xbfdf6690, dontShowAgainName= 0xbfdf6684,
options={i = -1075878272})
at /tmp/buildd/kde4libs-4.0.84/kdeui/dialogs/kmessagebox.cpp:954
#3
[Bug 165540] New: konquer crash over night
--- 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=165540 Summary: konquer crash over night Product: kontact Version: unspecified Platform: Debian testing OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: rrs researchut com Version:(using KDE 4.0.83) Installed from:Debian testing/unstable Packages OS:Linux Konqueror crashed for me over night. I wasn't doing anything because I was sleeping :-) In the morning, when I looked at my laptop, kontact had crashed. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 59748] disable notification messages when IMAP server not reacheable
--- 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=59748 --- Additional Comments From rrs researchut com 2008-03-24 09:39 --- Hi, Please. Can this be fixed with the 4.1 release ? ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
