[Bug 234508] New: Add clickable function to icon in New/Unread column
https://bugs.kde.org/show_bug.cgi?id=234508 Summary: Add clickable function to icon in New/Unread column Product: kmail Version: 1.13.2 Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: mur...@gmail.com Version: 1.13.2 (using 4.4.2 (KDE 4.4.2), Kubuntu packages) Compiler: cc OS:Linux (x86_64) release 2.6.32-20-generic Very often I need quickly change Read/Unread status of message, with one mouse click. It done very good in Thunderbird - I can point to string with message (without selecting) and width one click on read status column can change read/unread status. But in kmail I must do 2 actions: select message and press hotkey/menuitem/toolbar. Will be good to have a function to change read/unread status like the Important icon in column, with one mouse click I can change this status. -- 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 234136] Nothing works with my GNU Gpg4Win copy on my Desktop
https://bugs.kde.org/show_bug.cgi?id=234136 gess...@ukaachen.de changed: What|Removed |Added CC||gess...@ukaachen.de -- 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 234515] New: Crashed when closing a message window
https://bugs.kde.org/show_bug.cgi?id=234515 Summary: Crashed when closing a message window Product: kmail Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: rstave...@seseit.com Application that crashed: kmail Version of the application: 1.12.2 KDE Version: 4.3.2 (KDE 4.3.2) Qt Version: 4.5.2 Operating System: Linux 2.6.31-20-generic i686 Distribution: Ubuntu 9.10 What I was doing when the application crashed: I clicked the close button on a message and KMail crashed immediately. I have not seen this happen before. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #6 0x011476fb in QListData::begin (this=0x85a2560, msg=0x95ff138) at ./kmacctimap.moc:96 #7 QListKMMessage*::begin (this=0x85a2560, msg=0x95ff138) at /usr/include/qt4/QtCore/qlist.h:237 #8 QListKMMessage*::first (this=0x85a2560, msg=0x95ff138) at /usr/include/qt4/QtCore/qlist.h:252 #9 KMAcctImap::ignoreJobsForMessage (this=0x85a2560, msg=0x95ff138) at ../../kmail/kmacctimap.cpp:215 #10 0x0115ea63 in KMFolderImap::ignoreJobsForMessage (this=0x8531148, msg=0x95ff138) at ../../kmail/kmfolderimap.cpp:1564 #11 0x0127935c in KMMoveCommand::execute (this=0x94e1ec8) at ../../kmail/kmcommands.cpp:2095 #12 0x0125dba2 in KMCommand::slotPostTransfer (this=0x94e1ec8, result=KMCommand::OK) at ../../kmail/kmcommands.cpp:274 #13 0x0126815f in KMCommand::qt_metacall (this=0x94e1ec8, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbfb5c728) at ./kmcommands.moc:87 #14 0x0127a5fa in KMMoveCommand::qt_metacall (this=0x94e1ec8, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbfb5c728) at ./kmcommands.moc:1706 #15 0x0127a6c2 in KMTrashMsgCommand::qt_metacall (this=0x94e1ec8, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbfb5c728) at ./kmcommands.moc:1758 #16 0x004ad263 in QMetaObject::activate (sender=0x94e1ec8, from_signal_index=4, to_signal_index=4, argv=0xbfb5c728) at kernel/qobject.cpp:3113 #17 0x004adec2 in QMetaObject::activate (sender=0x94e1ec8, m=0x1696634, local_signal_index=0, argv=0xbfb5c728) at kernel/qobject.cpp:3187 #18 0x01259bd3 in KMCommand::messagesTransfered (this=0x94e1ec8, _t1=KMCommand::OK) at ./kmcommands.moc:102 #19 0x01277156 in KMCommand::transferSelectedMsgs (this=0x94e1ec8) at ../../kmail/kmcommands.cpp:368 #20 0x012773a2 in KMCommand::slotStart (this=0x94e1ec8) at ../../kmail/kmcommands.cpp:266 #21 0x0126813b in KMCommand::qt_metacall (this=0x94e1ec8, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbfb5c94c) at ./kmcommands.moc:86 #22 0x0127a5fa in KMMoveCommand::qt_metacall (this=0x94e1ec8, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbfb5c94c) at ./kmcommands.moc:1706 #23 0x0127a6c2 in KMTrashMsgCommand::qt_metacall (this=0x94e1ec8, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbfb5c94c) at ./kmcommands.moc:1758 #24 0x004ad263 in QMetaObject::activate (sender=0x9726fa8, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113 #25 0x004adec2 in QMetaObject::activate (sender=0x9726fa8, m=0x587908, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187 #26 0x004b2387 in QSingleShotTimer::timeout (this=0x9726fa8) at .moc/release-shared/qtimer.moc:76 #27 0x004b249c in QSingleShotTimer::timerEvent (this=0x9726fa8) at kernel/qtimer.cpp:298 #28 0x004a73bf in QObject::event (this=0x9726fa8, e=0xbfb5cde0) at kernel/qobject.cpp:1075 #29 0x017c4f54 in QApplicationPrivate::notify_helper (this=0x83ef628, receiver=0x9726fa8, e=0xbfb5cde0) at kernel/qapplication.cpp:4056 #30 0x017cc67c in QApplication::notify (this=0xbfb5d1e0, receiver=0x9726fa8, e=0xbfb5cde0) at kernel/qapplication.cpp:3603 #31 0x00d3bbfa in KApplication::notify (this=0xbfb5d1e0, receiver=0x9726fa8, event=0xbfb5cde0) at ../../kdeui/kernel/kapplication.cpp:302 #32 0x004976cb in QCoreApplication::notifyInternal (this=0xbfb5d1e0, receiver=0x9726fa8, event=0xbfb5cde0) at kernel/qcoreapplication.cpp:610 #33 0x004c47ce in QCoreApplication::sendEvent (this=0x83dcd34) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #34 QTimerInfoList::activateTimers (this=0x83dcd34) at kernel/qeventdispatcher_unix.cpp:572 #35 0x004c20e0 in timerSourceDispatch (source=0x83dcd00) at kernel/qeventdispatcher_glib.cpp:165 #36 0x03014e88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #37 0x03018730 in ?? () from /lib/libglib-2.0.so.0 #38 0x03018863 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #39 0x004c202c in QEventDispatcherGlib::processEvents (this=0x83b3180, flags=...) at kernel/qeventdispatcher_glib.cpp:327 #40 0x01865be5 in QGuiEventDispatcherGlib::processEvents (this=0x83b3180, flags=...) at kernel/qguieventdispatcher_glib.cpp:202 #41 0x00495c79 in QEventLoop::processEvents (this=0xbfb5d0a4, flags=) at kernel/qeventloop.cpp:149 #42 0x004960ca in QEventLoop::exec
[Bug 234518] New: [Kubuntu Lucid] Kontact crashed after adding new account
https://bugs.kde.org/show_bug.cgi?id=234518 Summary: [Kubuntu Lucid] Kontact crashed after adding new account Product: kontact Version: 4.4.2 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: matej...@gmail.com Application: kontact (4.4.2) KDE Platform Version: 4.4.2 (KDE 4.4.2) Qt Version: 4.6.2 Operating System: Linux 2.6.32-21-generic x86_64 Distribution: Ubuntu lucid (development branch) -- Information about the crash: After clean installation I added new Disconnected IMAP account to Kontact. Kontact crashed after closing the configuration window. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0x7fe78ddca780 (LWP 16337))] Thread 2 (Thread 0x7fe76b364710 (LWP 16342)): #0 0x7fe78ae97f93 in *__GI___poll (fds=value optimized out, nfds=value optimized out, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7fe7839cd4a9 in ?? () from /lib/libglib-2.0.so.0 #2 0x7fe7839cd8fc in g_main_context_iteration () from /lib/libglib-2.0.so.0 #3 0x7fe78c282566 in QEventDispatcherGlib::processEvents (this=0x1446770, flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:414 #4 0x7fe78c257992 in QEventLoop::processEvents (this=value optimized out, flags=) at kernel/qeventloop.cpp:149 #5 0x7fe78c257d6c in QEventLoop::exec (this=0x7fe76b363d90, flags=) at kernel/qeventloop.cpp:201 #6 0x7fe78c161d59 in QThread::exec (this=value optimized out) at thread/qthread.cpp:487 #7 0x7fe78c238178 in QInotifyFileSystemWatcherEngine::run (this=0x1416950) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x7fe78c164775 in QThreadPrivate::start (arg=0x1416950) at thread/qthread_unix.cpp:248 #9 0x7fe785f439ca in start_thread (arg=value optimized out) at pthread_create.c:300 #10 0x7fe78aea46dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 1 (Thread 0x7fe78ddca780 (LWP 16337)): [KCrash Handler] #5 0x7fe773061a76 in MailTransport::AddTransportDialog::accept (this=0x26de0e0) at ../../mailtransport/addtransportdialog.cpp:139 #6 0x7fe78cbb14c5 in KDialog::slotButtonClicked (this=0x26de0e0, button=4) at ../../kdeui/dialogs/kdialog.cpp:863 #7 0x7fe78cbb3329 in KDialog::qt_metacall (this=0x26de0e0, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff9bfa5580) at ./kdialog.moc:190 #8 0x7fe7730618a8 in MailTransport::AddTransportDialog::qt_metacall (this=0xaf6e50, _c=2616873344, _id=-1940467456, _a=0x1) at ./addtransportdialog.moc:68 #9 0x7fe78c26be3f in QMetaObject::activate (sender=0x327a7a8, m=value optimized out, local_signal_index=value optimized out, argv=0x1) at kernel/qobject.cpp:3293 #10 0x7fe78c27115e in QSignalMapper::mapped (this=0xaf6e50, _t1=4) at .moc/release-shared/moc_qsignalmapper.cpp:101 #11 0x7fe78c272372 in QSignalMapper::map (this=0x327a7a8, sender=0x3287cb0) at kernel/qsignalmapper.cpp:266 #12 0x7fe78c2725f0 in QSignalMapper::qt_metacall (this=0x327a7a8, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff9bfa5710) at .moc/release-shared/moc_qsignalmapper.cpp:87 #13 0x7fe78c26be3f in QMetaObject::activate (sender=0x3287cb0, m=value optimized out, local_signal_index=value optimized out, argv=0x1) at kernel/qobject.cpp:3293 #14 0x7fe78bcad5f2 in QAbstractButton::clicked (this=0xaf6e50, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:206 #15 0x7fe78b9c786b in QAbstractButtonPrivate::emitClicked (this=0x30fe000) at widgets/qabstractbutton.cpp:546 #16 0x7fe78b9c870b in QAbstractButtonPrivate::click (this=0x30fe000) at widgets/qabstractbutton.cpp:539 #17 0x7fe78b9c897c in QAbstractButton::mouseReleaseEvent (this=0x3287cb0, e=0x7fff9bfa6060) at widgets/qabstractbutton.cpp:1121 #18 0x7fe78b668582 in QWidget::event (this=0x3287cb0, event=0x7fff9bfa6060) at kernel/qwidget.cpp:7998 #19 0x7fe78b61222c in QApplicationPrivate::notify_helper (this=0xa2ed30, receiver=0x3287cb0, e=0x7fff9bfa6060) at kernel/qapplication.cpp:4300 #20 0x7fe78b618ecb in QApplication::notify (this=0x7fff9bfa8620, receiver=0x3287cb0, e=0x7fff9bfa6060) at kernel/qapplication.cpp:3865 #21 0x7fe78cc41526 in KApplication::notify (this=0x7fff9bfa8620, receiver=0x3287cb0, event=0x7fff9bfa6060) at ../../kdeui/kernel/kapplication.cpp:302 #22 0x7fe78c25906c in QCoreApplication::notifyInternal (this=0x7fff9bfa8620, receiver=0x3287cb0, event=0x7fff9bfa6060) at kernel/qcoreapplication.cpp:704 #23 0x7fe78b6180ae in QCoreApplication::sendEvent (receiver=0x3287cb0, event=0x7fff9bfa6060, alienWidget=0x3287cb0, nativeWidget=0x26de0e0, buttonDown=value optimized out, lastMouseReceiver=value optimized out, spontaneous=true) at
[Bug 234519] New: kontact crash after it show Unable to complete LIST operation
https://bugs.kde.org/show_bug.cgi?id=234519 Summary: kontact crash after it show Unable to complete LIST operation Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: andras.ka...@cert-hungary.hu Application that crashed: kontact Version of the application: 4.3.2 KDE Version: 4.3.2 (KDE 4.3.2) Qt Version: 4.5.2 Operating System: Linux 2.6.31-20-generic x86_64 Distribution: Ubuntu 9.10 What I was doing when the application crashed: kontact is crashing after kmail is trying to download mails from POP3 account and it shows Unable to complete LIST operation -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #5 0x7f3966355758 in KIO::Slave::deref() () from /usr/lib/libkio.so.5 #6 0x7f3966356159 in KIO::Slave::gotInput() () from /usr/lib/libkio.so.5 #7 0x7f396635826c in KIO::Slave::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkio.so.5 #8 0x7f3967e46ddc in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4 #9 0x7f3966272f57 in ?? () from /usr/lib/libkio.so.5 #10 0x7f396627307d in KIO::Connection::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkio.so.5 #11 0x7f3967e410f9 in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4 #12 0x7f3968751efc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #13 0x7f39687591ce in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #14 0x7f3969388ab6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #15 0x7f3967e31c2c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #16 0x7f3967e3280a in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4 #17 0x7f3967e5a533 in ?? () from /usr/lib/libQtCore.so.4 #18 0x7f39616acbce in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #19 0x7f39616b0598 in ?? () from /lib/libglib-2.0.so.0 #20 0x7f39616b06c0 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #21 0x7f3967e5a1a6 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #22 0x7f39687e64be in ?? () from /usr/lib/libQtGui.so.4 #23 0x7f3967e30532 in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #24 0x7f3967e30904 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #25 0x7f3967e32ab9 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #26 0x00403f47 in _start () 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 234522] New: Akonadi crash when trying to add event in akonadi_gcal resource
https://bugs.kde.org/show_bug.cgi?id=234522 Summary: Akonadi crash when trying to add event in akonadi_gcal resource Product: Akonadi Version: unspecified Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Google Resource AssignedTo: savag...@yahoo.com ReportedBy: mur...@gmail.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.32-21-generic x86_64 Distribution: Ubuntu lucid (development branch) -- Information about the crash: The resource was successfully created with akonadi, but when I try to add some event to it, every time I got this crash. The crash can be reproduced every time. -- Backtrace: Application: Akonadi Resource (akonadi_gcal_resource), signal: Segmentation fault [Current thread is 1 (Thread 0x7f8b0beb6780 (LWP 3451))] Thread 2 (Thread 0x7f8af6b4c710 (LWP 3454)): #0 0x7f8b081d9f93 in *__GI___poll (fds=value optimized out, nfds=value optimized out, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f8b067564a9 in ?? () from /lib/libglib-2.0.so.0 #2 0x7f8b067568fc in g_main_context_iteration () from /lib/libglib-2.0.so.0 #3 0x7f8b0b631566 in QEventDispatcherGlib::processEvents (this=0xd227b0, flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:414 #4 0x7f8b0b606992 in QEventLoop::processEvents (this=value optimized out, flags=) at kernel/qeventloop.cpp:149 #5 0x7f8b0b606d6c in QEventLoop::exec (this=0x7f8af6b4bd90, flags=) at kernel/qeventloop.cpp:201 #6 0x7f8b0b510d59 in QThread::exec (this=value optimized out) at thread/qthread.cpp:487 #7 0x7f8b0b5e7178 in QInotifyFileSystemWatcherEngine::run (this=0xd19a20) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x7f8b0b513775 in QThreadPrivate::start (arg=0xd19a20) at thread/qthread_unix.cpp:248 #9 0x7f8b0b2839ca in start_thread (arg=value optimized out) at pthread_create.c:300 #10 0x7f8b081e66dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 1 (Thread 0x7f8b0beb6780 (LWP 3451)): [KCrash Handler] #5 *__GI___libc_free (mem=0x20) at malloc.c:3709 #6 0x7f8b05a19c59 in icalmemory_add_tmp_buffer () from /usr/lib/libical.so.0 #7 0x7f8b05a1c861 in icalproperty_get_parameter_as_string () from /usr/lib/libical.so.0 #8 0x7f8b0a63b3c7 in KCal::ICalFormatImpl::readIncidence (this=0xd1fdd0, parent=0x127ca00, incidence=0x127bc30, tzlist=0xe8d610) at ../../kcal/icalformat_p.cpp:1523 #9 0x7f8b0a63b6e4 in KCal::ICalFormatImpl::readEvent (this=0xd1fdd0, vevent=0x127ca00, tzlist=value optimized out) at ../../kcal/icalformat_p.cpp:1122 #10 0x7f8b0a63c73e in KCal::ICalFormatImpl::populate (this=0xd1fdd0, cal=0x7fff7c509b20, calendar=0xe845b0) at ../../kcal/icalformat_p.cpp:2476 #11 0x7f8b0a62ed92 in KCal::ICalFormat::fromRawString (this=0x126f6a8, cal=0x7fff7c509b20, string=value optimized out) at ../../kcal/icalformat.cpp:188 #12 0x7f8b0a62df60 in KCal::ICalFormat::fromString (this=0x126f6a8, cal=0x7fff7c509b20, string=value optimized out) at ../../kcal/icalformat.cpp:148 #13 0x7f8b0a62e5b5 in KCal::ICalFormat::fromString (this=value optimized out, string=...) at ../../kcal/icalformat.cpp:208 #14 0x7f8af6148ca4 in ?? () from /usr/lib/kde4/akonadi_serializer_kcal.so #15 0x7f8b0ba1414a in Akonadi::ItemSerializer::deserialize (item=..., label=..., data=..., version=0) at ../../akonadi/itemserializer.cpp:237 #16 0x7f8b0ba14794 in Akonadi::ItemSerializer::deserialize (item=..., label=..., data=..., version=0, external=value optimized out) at ../../akonadi/itemserializer.cpp:229 #17 0x7f8b0ba391ee in Akonadi::ProtocolHelper::parseItemFetchResult (lineTokens=value optimized out, item=value optimized out) at ../../akonadi/protocolhelper.cpp:352 #18 0x7f8b0ba0b8ff in Akonadi::ItemFetchJob::doHandleResponse (this=value optimized out, tag=value optimized out, data=...) at ../../akonadi/itemfetchjob.cpp:173 #19 0x7f8b0ba2115e in Akonadi::JobPrivate::handleResponse (this=value optimized out, tag=..., data=...) at ../../akonadi/job.cpp:72 #20 0x7f8b0ba4ed08 in Akonadi::SessionPrivate::dataReceived (this=0xe1ba90) at ../../akonadi/session.cpp:121 #21 0x7f8b0ba4f535 in Akonadi::Session::qt_metacall (this=0xe02290, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff7c50a3e0) at ./session.moc:87 #22 0x7f8b0b61ae3f in QMetaObject::activate (sender=0xe046a0, m=value optimized out, local_signal_index=value optimized out, argv=0x7f8b0b495280) at kernel/qobject.cpp:3293 #23 0x7f8b0b665488 in QIODevice::qt_metacall (this=0xe046a0, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff7c50a520) at .moc/release-shared/moc_qiodevice.cpp:77 #24
[Bug 188142] Kmail crash (SIGSEGV) when opening attachment [KMHandleAttachmentCommand::slotStart]
https://bugs.kde.org/show_bug.cgi?id=188142 --- Comment #27 from Diego panda84 inwind it 2010-04-16 11:39:10 --- Created an attachment (id=42818) -- (http://bugs.kde.org/attachment.cgi?id=42818) New crash information added by DrKonqi I was trying to open an attachment stored on IMAP. -- 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 234523] New: drag message with right click to ask for action
https://bugs.kde.org/show_bug.cgi?id=234523 Summary: drag message with right click to ask for action Product: kmail Version: unspecified Platform: openSUSE RPMs OS/Version: unspecified Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: silver.salo...@gmail.com Version:(using KDE 4.4.2) Installed from:openSUSE RPMs There is a default action (move or copy) for dragging messages to folders, but when it's set, the other action cannot be accessed otherwise than selecting it from menus (which is a quite time-consuming task). I suggest making possible to drag messages with right click (if it's possible in KDE) and then ask for the action (as it's done in Windows when dragging files). -- 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 234376] kontact/kadr akonadi? Problems to add/show new contacts, additional errors in calendar
https://bugs.kde.org/show_bug.cgi?id=234376 Andreas Kahnt andreas.ka...@gmx.de changed: What|Removed |Added CC||andreas.ka...@gmx.de --- Comment #1 from Andreas Kahnt andreas kahnt gmx de 2010-04-16 12:56:43 --- After a reboot: - I only get this error if I edit one of the contacts I created before the reboot: Unable to write to file '/home/aka/.local/share/contacts//': Unknown error - There are no other errors and - I can export the two contacts. -- 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 234540] New: Kontact crashes after entering KWallet password
https://bugs.kde.org/show_bug.cgi?id=234540 Summary: Kontact crashes after entering KWallet password Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: dr.allc...@gmx.de Application that crashed: kontact Version of the application: 4.3.5 KDE Version: 4.3.5 (KDE 4.3.5) Qt Version: 4.5.2 Operating System: Linux 2.6.31-21-generic x86_64 Distribution: Ubuntu 9.10 What I was doing when the application crashed: - Directly after entering the password for the KWallet the application crashes. - The crash happens under Gnome as well as under KDE. - Kontact was opened and the machine needed a restart because of updates. Since I have done this I could not start Kontact anymore List of installed updates: Commit Log for Sat Apr 10 10:45:31 2010 Upgraded the following packages: firefox (3.5.8+build1+nobinonly-0ubuntu0.9.10.1) to 3.5.9+nobinonly-0ubuntu0.9.10.1 firefox-3.0 (3.5.8+build1+nobinonly-0ubuntu0.9.10.1) to 3.5.9+nobinonly-0ubuntu0.9.10.1 firefox-3.0-gnome-support (3.5.8+build1+nobinonly-0ubuntu0.9.10.1) to 3.5.9+nobinonly-0ubuntu0.9.10.1 firefox-3.5 (3.5.8+build1+nobinonly-0ubuntu0.9.10.1) to 3.5.9+nobinonly-0ubuntu0.9.10.1 firefox-3.5-branding (3.5.8+build1+nobinonly-0ubuntu0.9.10.1) to 3.5.9+nobinonly-0ubuntu0.9.10.1 firefox-3.5-gnome-support (3.5.8+build1+nobinonly-0ubuntu0.9.10.1) to 3.5.9+nobinonly-0ubuntu0.9.10.1 firefox-gnome-support (3.5.8+build1+nobinonly-0ubuntu0.9.10.1) to 3.5.9+nobinonly-0ubuntu0.9.10.1 libnss3-0d (3.12.3.1-0ubuntu2) to 3.12.6-0ubuntu0.9.10.1 libnss3-1d (3.12.3.1-0ubuntu2) to 3.12.6-0ubuntu0.9.10.1 libnss3-1d-dbg (3.12.3.1-0ubuntu2) to 3.12.6-0ubuntu0.9.10.1 xulrunner-1.9.1 (1.9.1.8+build1+nobinonly-0ubuntu0.9.10.1) to 1.9.1.9+nobinonly-0ubuntu0.9.10.1 xulrunner-1.9.1-gnome-support (1.9.1.8+build1+nobinonly-0ubuntu0.9.10.1) to 1.9.1.9+nobinonly-0ubuntu0.9.10.1 -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault The current source language is auto; currently c. [KCrash Handler] #5 QString (this=0x0) at /usr/include/qt4/QtCore/qstring.h:711 #6 KIO::Slave::slaveProtocol (this=0x0) at ../../kio/kio/slave.cpp:189 #7 0x7f1153bcd41f in KIO::SchedulerPrivate::assignJobToSlave (this=0x24fd5b0, slave=0x0, job=0x33bf370) at ../../kio/kio/scheduler.cpp:958 #8 0x7f113f7f789a in KMail::SearchJob::searchCompleteFolder (this=0x32f3fa0) at ../../kmail/searchjob.cpp:95 #9 0x7f113f61dd7f in KMFolderImap::search (this=0x2899a20, pattern=0x2b5a370) at ../../kmail/kmfolderimap.cpp:2412 #10 0x7f113f75c107 in KMSearch::slotProcessNextBatch (this=0x297b140) at ../../kmail/kmfoldersearch.cpp:272 #11 0x7f113f760560 in KMSearch::qt_metacall (this=0x297b140, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fffa6ddad80) at ./kmfoldersearch.moc:79 #12 0x7f11556c3ddc in QMetaObject::activate (sender=0x2b56e40, from_signal_index=value optimized out, to_signal_index=value optimized out, argv=0x0) at kernel/qobject.cpp:3113 #13 0x7f11556bdd83 in QObject::event (this=0x2b56e40, e=0x0) at kernel/qobject.cpp:1075 #14 0x7f1155fd2efc in QApplicationPrivate::notify_helper (this=0x2186850, receiver=0x2b56e40, e=0x7fffa6ddb380) at kernel/qapplication.cpp:4056 #15 0x7f1155fda1ce in QApplication::notify (this=0x7fffa6dde340, receiver=0x2b56e40, e=0x7fffa6ddb380) at kernel/qapplication.cpp:4021 #16 0x7f1156c09f46 in KApplication::notify (this=0x7fffa6dde340, receiver=0x2b56e40, event=0x7fffa6ddb380) at ../../kdeui/kernel/kapplication.cpp:302 #17 0x7f11556aec2c in QCoreApplication::notifyInternal (this=0x7fffa6dde340, receiver=0x2b56e40, event=0x7fffa6ddb380) at kernel/qcoreapplication.cpp:610 #18 0x7f11556d9862 in QCoreApplication::sendEvent (this=0x2181400) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #19 QTimerInfoList::activateTimers (this=0x2181400) at kernel/qeventdispatcher_unix.cpp:572 #20 0x7f11556d725d in timerSourceDispatch (source=value optimized out) at kernel/qeventdispatcher_glib.cpp:165 #21 0x7f114ef27bce in g_main_dispatch (context=0x2189520) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:1960 #22 IA__g_main_context_dispatch (context=0x2189520) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2513 #23 0x7f114ef2b598 in g_main_context_iterate (context=0x2189520, block=value optimized out, dispatch=value optimized out, self=value optimized out) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2591 #24 0x7f114ef2b6c0 in IA__g_main_context_iteration (context=0x2189520, may_block=1) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2654 #25 0x7f11556d71a6 in QEventDispatcherGlib::processEvents (this=0x214ecb0, flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:327 #26 0x7f11560674be in
[Bug 166653] Index files recreated on startup and mail check
https://bugs.kde.org/show_bug.cgi?id=166653 --- Comment #26 from ralfgesellensetter ralf skolelinux de 2010-04-16 15:52:40 --- This bug is open for months, now, there are dozens of duplicates reported on current versions of kmail. Are there any official patches/fixes? Is there a button to rebuild indices globally (for all folders - I have many) - *WITHOUT* losing tags/markers? It is quite annoying that rebuilding the index will destroy all tagging and possibly read messages that are to be kept (by policy) might get lost because unread messages 1 year old are deleted by local policy... I also noticed, that while there is background activity, it is hard to find out, what kmail is actually doing. And some actions (like highligthing message headers while hoovering over them) are more responsive than others (like displaying message bodies which can take several minutes). BTW: version 4:4.3.4-2 http://ftp.us.debian.org sid/main Packages -- 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 166653] Index files recreated on startup and mail check
https://bugs.kde.org/show_bug.cgi?id=166653 --- Comment #27 from Axel Schmidt axel asc-computer com 2010-04-16 16:21:28 --- Now i think it not really a bug of kmail because, since my last post in november, i updating the linux kernel from Linux 2.6.31-14-generic x86_64 to Linux 2.6.31-20-generic #58-Ubuntu SMP x86_64 GNU/Linux and now i have no problems with kmail anymore! :) Everthing works fine and fast(!) and startup of kmail needs only seconds without creating any index! So it is perhaps a bug of the kernel or combination of kernel and kmail... Best regards, Axel Schmidt -- 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 234376] kontact/kadr akonadi? Problems to add/show new contacts, additional errors in calendar
https://bugs.kde.org/show_bug.cgi?id=234376 Tobias Koenig to...@kde.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||WORKSFORME --- Comment #2 from Tobias Koenig tokoe kde org 2010-04-16 17:10:52 --- Hej, it seems your files in $HOME/.local/share/contacts/ are messed up somehow and do not contain valid vCards. Have you copied in there files manually? To solve this issue I'd recommend to first remove the 'Personal Contacts' address book from KAddressBook, then inspecting each file in $HOME/.local/share/contacts whether it contains a valid vCard and removing all files that do not. Note that the names of the file must be the UIDs of the vCards they contain. After the cleanup you can add the 'Personal Contacts' resource again and everything should work as expected. Ciao, Tobias -- 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 234349] Changes to telephone types in contacts are not saved
https://bugs.kde.org/show_bug.cgi?id=234349 --- Comment #3 from Tobias Koenig tokoe kde org 2010-04-16 17:13:07 --- You can take the change from the SVN revision mentioned above and compile kdepimlibs yourself. An easy workaround however is to not only change the type of the phone number but also the phone number itself (e.g. removing last digit and adding it again). This will trigger the save of both, type and number. -- 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 234430] Addressbook looses contacts after certain time
https://bugs.kde.org/show_bug.cgi?id=234430 --- Comment #1 from Tobias Koenig tokoe kde org 2010-04-16 17:15:42 --- Hej, do you see any error messages on the console? Or can you try to start 'akonadiconsole' together with kaddressbook and let it run the same time as kaddressbook, and as soon as kaddressbook stops to work check whether akonadiconsole shows the same behavior? I suspect it might be some timeout in the connection to MySQL daemon or something like that... Ciao, Tobias -- 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 234376] kontact/kadr akonadi? Problems to add/show new contacts, additional errors in calendar
https://bugs.kde.org/show_bug.cgi?id=234376 --- Comment #3 from Andreas Kahnt andreas kahnt gmx de 2010-04-16 18:01:57 --- I've nothing done manually in this dir. The two vcard files for the contacts I added were not in this dir. I added them using the export I did. Then I reactivated the address book as you described - there are NO errors. Thank you! -- 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 234495] gcal does not use username and password saved in kwallet after akonadi restart
https://bugs.kde.org/show_bug.cgi?id=234495 yartsa yar...@clovermail.net changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||WORKSFORME --- Comment #2 from yartsa yartsa clovermail net 2010-04-16 18:28:14 --- I cannot seem to reproduce this anymore, so I change the status to resolved. The fields are empty but the calendars get synced without need to refill the account info. Sorry for waste of space... :) I'll come back to this if the situation reverts back to what it was, for some reason. -- 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 234556] New: ran Kontact as first application on startup. Saved an email message and Kontact crashed. Kontact often crashes, most often when I open Dolphin
https://bugs.kde.org/show_bug.cgi?id=234556 Summary: ran Kontact as first application on startup. Saved an email message and Kontact crashed. Kontact often crashes, most often when I open Dolphin Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: ke...@online.no Application that crashed: kontact Version of the application: 4.3.5 KDE Version: 4.3.5 (KDE 4.3.5) Qt Version: 4.5.2 Operating System: Linux 2.6.31-20-generic i686 Distribution: Ubuntu 9.10 What I was doing when the application crashed: I had just started Karmic and entered password to Wallet for access to WIFI and Kontact. I had not started any other applications. I launched Kontact email. Viewing email, I tried to save a message (ctrl+S) was unsure about what folder to save to, so I cancelled save. Then I saved again and Kontact crashed. However the crashes usually occur as I open Dolphin to look for a file. Could there be some issue between Kontact and file manager functions? -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #6 0x08d95ce3 in KMail::MessageListView::Widget::getSelectionStats (this=0x979aab0, selectedSernums=..., selectedVisibleSernums=..., allSelectedBelongToSameThread=0xbfc46a9f, includeCollapsedChildren=value optimized out) at ../../kmail/messagelistview/widget.cpp:580 #7 0x08d8e316 in KMail::MessageListView::Pane::getSelectionStats (this=0x9805de8, selectedSernums=..., selectedVisibleSernums=..., allSelectedBelongToSameThread=0xbfc46a9f, includeCollapsedChildren=6) at ../../kmail/messagelistview/pane.cpp:622 #8 0x08c3e51c in KMMainWidget::updateMessageActions (this=0x98094e0) at ../../kmail/kmmainwidget.cpp:4274 #9 0x08c58052 in KMMainWidget::qt_metacall (this=0x98094e0, _c=QMetaObject::InvokeMetaMethod, _id=21, _a=0xbfc46b7c) at ./kmmainwidget.moc:367 #10 0x008f6263 in QMetaObject::activate (sender=0x9b87080, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113 #11 0x008f6ec2 in QMetaObject::activate (sender=0x9b87080, m=0x9d1904, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187 #12 0x00930667 in QTimer::timeout (this=0x9b87080) at .moc/release-shared/moc_qtimer.cpp:128 #13 0x008fb9ae in QTimer::timerEvent (this=0x9b87080, e=0xbfc47010) at kernel/qtimer.cpp:261 #14 0x008f03bf in QObject::event (this=0x9b87080, e=0xbfc47010) at kernel/qobject.cpp:1075 #15 0x01013f54 in QApplicationPrivate::notify_helper (this=0x93ad018, receiver=0x9b87080, e=0xbfc47010) at kernel/qapplication.cpp:4056 #16 0x0101b67c in QApplication::notify (this=0xbfc47374, receiver=0x9b87080, e=0xbfc47010) at kernel/qapplication.cpp:3603 #17 0x00bc225a in KApplication::notify (this=0xbfc47374, receiver=0x9b87080, event=0xbfc47010) at ../../kdeui/kernel/kapplication.cpp:302 #18 0x008e06cb in QCoreApplication::notifyInternal (this=0xbfc47374, receiver=0x9b87080, event=0xbfc47010) at kernel/qcoreapplication.cpp:610 #19 0x0090d7ce in QCoreApplication::sendEvent (this=0x93a2e34) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #20 QTimerInfoList::activateTimers (this=0x93a2e34) at kernel/qeventdispatcher_unix.cpp:572 #21 0x0090b0e0 in timerSourceDispatch (source=0x93a2e00) at kernel/qeventdispatcher_glib.cpp:165 #22 0x08822e88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #23 0x08826730 in ?? () from /lib/libglib-2.0.so.0 #24 0x08826863 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #25 0x0090b02c in QEventDispatcherGlib::processEvents (this=0x93819f8, flags=...) at kernel/qeventdispatcher_glib.cpp:327 #26 0x010b4be5 in QGuiEventDispatcherGlib::processEvents (this=0x93819f8, flags=...) at kernel/qguieventdispatcher_glib.cpp:202 #27 0x008dec79 in QEventLoop::processEvents (this=0xbfc472d4, flags=) at kernel/qeventloop.cpp:149 #28 0x008df0ca in QEventLoop::exec (this=0xbfc472d4, flags=...) at kernel/qeventloop.cpp:201 #29 0x008e153f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #30 0x01013dd7 in QApplication::exec () at kernel/qapplication.cpp:3525 #31 0x0804b4e6 in main (argc=1, argv=0xbfc47594) at ../../../kontact/src/main.cpp:218 This bug may be a duplicate of or related to bug 189773 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 234558] New: german translation: Filter einrichten - Alle der Folgenden müssen zutreffen
https://bugs.kde.org/show_bug.cgi?id=234558 Summary: german translation: Filter einrichten - Alle der Folgenden müssen zutreffen 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: st.m...@web.de Version: 1.13.2 (using 4.4.2 (KDE 4.4.2), Kubuntu packages) Compiler: cc OS:Linux (x86_64) release 2.6.32-21-generic In the german menue for creating filters you can choose between X Alle Folgenden müssen zutreffen and x Alle der Folgenden müssen zutreffen. The meaning of both are the same. The second choise Alle der folgenden müssen zutrefen should read Nur einer der folgenden Filter muss zutrefen . -- 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 234558] german translation: Filter einrichten - Alle der Folgenden müssen zutreffen
https://bugs.kde.org/show_bug.cgi?id=234558 St Mase st.m...@web.de changed: What|Removed |Added Keywords||usability -- 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 234559] New: kontact crashes when ctrl+q on multiple emails
https://bugs.kde.org/show_bug.cgi?id=234559 Summary: kontact crashes when ctrl+q on multiple emails Product: kontact Version: 4.4.2 Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: wuseldu...@yahoo.de Application: kontact (4.4.2) KDE Platform Version: 4.4.2 (KDE 4.4.2) (Compiled from sources) Qt Version: 4.6.2 Operating System: Linux 2.6.33-gentoo-r1 x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: i was tryint to set several emails as read at once. kmail crashed without setting the messages as read. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #5 Kontact::MainWindow::activateInitialPluginModule (this=0x120bf70) at /var/tmp/portage/kde-base/kontact-4.4.2/work/kontact-4.4.2/kontact/src/mainwindow.cpp:289 #6 0x0040477a in KontactApp::newInstance (this=0x7fffa2880eb0) at /var/tmp/portage/kde-base/kontact-4.4.2/work/kontact-4.4.2/kontact/src/main.cpp:149 #7 0x7f9c4d610cd6 in KUniqueApplicationAdaptor::newInstance (this=0x12dcea0, asn_id=value optimized out, args=...) at /var/tmp/portage/kde-base/kdelibs-4.4.2/work/kdelibs-4.4.2/kdeui/kernel/kuniqueapplication.cpp:454 #8 0x7f9c4d611316 in KUniqueApplicationAdaptor::qt_metacall (this=0x12dcea0, _c=QMetaObject::InvokeMetaMethod, _id=26653696, _a=0x7fffa287fec0) at /var/tmp/portage/kde-base/kdelibs-4.4.2/work/kdelibs-4.4.2_build/kdeui/kuniqueapplication_p.moc:81 #9 0x7f9c4a0cd2f1 in QDBusConnectionPrivate::deliverCall (this=value optimized out, object=value optimized out, msg=value optimized out, metaTypes=..., slotIdx=value optimized out) at qdbusintegrator.cpp:904 #10 0x7f9c4a0ce4f3 in QDBusConnectionPrivate::activateCall (this=value optimized out, object=0x12dcea0, flags=337, msg=...) at qdbusintegrator.cpp:816 #11 0x7f9c4a0cef6d in QDBusConnectionPrivate::activateObject (this=value optimized out, node=value optimized out, msg=..., pathStartPos=value optimized out) at qdbusintegrator.cpp:1364 #12 0x7f9c4a0cf208 in QDBusActivateObjectEvent::placeMetaCall (this=0x1c02d30) at qdbusintegrator.cpp:1477 #13 0x7f9c4bfc52c9 in QObject::event (this=0x7fffa2880eb0, e=0x1c02d30) at kernel/qobject.cpp:1240 #14 0x7f9c4c4909dd in QApplication::event (this=0x7fffa2880eb0, e=0x1c02d30) at kernel/qapplication.cpp:2353 #15 0x7f9c4c48c7bc in QApplicationPrivate::notify_helper (this=0x11fcad0, receiver=0x7fffa2880eb0, e=0x1c02d30) at kernel/qapplication.cpp:4300 #16 0x7f9c4c492e0b in QApplication::notify (this=0x7fffa2880eb0, receiver=0x7fffa2880eb0, e=0x1c02d30) at kernel/qapplication.cpp:4183 #17 0x7f9c4d609b36 in KApplication::notify (this=0x7fffa2880eb0, receiver=0x7fffa2880eb0, event=0x1c02d30) at /var/tmp/portage/kde-base/kdelibs-4.4.2/work/kdelibs-4.4.2/kdeui/kernel/kapplication.cpp:302 #18 0x7f9c4bfb567b in QCoreApplication::notifyInternal (this=0x7fffa2880eb0, receiver=0x7fffa2880eb0, event=0x1c02d30) at kernel/qcoreapplication.cpp:704 #19 0x7f9c4bfb7dc6 in QCoreApplication::sendEvent (receiver=0x0, event_type=value optimized out, data=0x11d4ea0) at kernel/qcoreapplication.h:215 #20 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=value optimized out, data=0x11d4ea0) at kernel/qcoreapplication.cpp:1345 #21 0x7f9c4bfdeef3 in QCoreApplication::sendPostedEvents (s=value optimized out) at kernel/qcoreapplication.h:220 #22 postEventSourceDispatch (s=value optimized out) at kernel/qeventdispatcher_glib.cpp:276 #23 0x7f9c44c0c58d in g_main_dispatch (context=0x120f920) at gmain.c:1960 #24 IA__g_main_context_dispatch (context=0x120f920) at gmain.c:2513 #25 0x7f9c44c0ff48 in g_main_context_iterate (context=0x120f920, block=value optimized out, dispatch=value optimized out, self=value optimized out) at gmain.c:2591 #26 0x7f9c44c10070 in IA__g_main_context_iteration (context=0x120f920, may_block=1) at gmain.c:2654 #27 0x7f9c4bfdea33 in QEventDispatcherGlib::processEvents (this=0x11d46a0, flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:412 #28 0x7f9c4c53a9fe in QGuiEventDispatcherGlib::processEvents (this=0x120bf70, flags=value optimized out) at kernel/qguieventdispatcher_glib.cpp:204 #29 0x7f9c4bfb3fd2 in QEventLoop::processEvents (this=value optimized out, flags=) at kernel/qeventloop.cpp:149 #30 0x7f9c4bfb43a4 in QEventLoop::exec (this=0x7fffa2880df0, flags=) at kernel/qeventloop.cpp:201 #31 0x7f9c4bfb808b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981 #32 0x00403f44 in main (argc=value optimized out, argv=value optimized out) at /var/tmp/portage/kde-base/kontact-4.4.2/work/kontact-4.4.2/kontact/src/main.cpp:224 Possible duplicates by query: bug 234169, bug 233509, bug 231229, bug 226815, bug 223117. Reported
[Bug 226380] nice contact groups are not available in kmail
https://bugs.kde.org/show_bug.cgi?id=226380 --- Comment #3 from Tristan Miller psychonaut nothingisreal com 2010-04-16 23:43:36 --- By the way, the bug is still present in KDE 4.4.2. -- 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 234577] New: KMail crashed after reading/deleting mails via IMAP
https://bugs.kde.org/show_bug.cgi?id=234577 Summary: KMail crashed after reading/deleting mails via IMAP Product: kontact Version: 4.4.2 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: beneri...@gmail.com Application: kontact (4.4.2) KDE Platform Version: 4.4.2 (KDE 4.4.2) Qt Version: 4.6.2 Operating System: Linux 2.6.32-21-generic x86_64 Distribution: Ubuntu lucid (development branch) -- Information about the crash: I read and deleted some emails via IMAP. At some point KMail crashed. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0x7f1585088780 (LWP 18902))] Thread 2 (Thread 0x7f155da73710 (LWP 18928)): #0 0x7f157ac99650 in g_poll () from /lib/libglib-2.0.so.0 #1 0x7f157ac8c4a9 in ?? () from /lib/libglib-2.0.so.0 #2 0x7f157ac8c8fc in g_main_context_iteration () from /lib/libglib-2.0.so.0 #3 0x7f1583541566 in QEventDispatcherGlib::processEvents (this=0x228ed80, flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:414 #4 0x7f1583516992 in QEventLoop::processEvents (this=value optimized out, flags=) at kernel/qeventloop.cpp:149 #5 0x7f1583516d6c in QEventLoop::exec (this=0x7f155da72d90, flags=) at kernel/qeventloop.cpp:201 #6 0x7f1583420d59 in QThread::exec (this=value optimized out) at thread/qthread.cpp:487 #7 0x7f15834f7178 in QInotifyFileSystemWatcherEngine::run (this=0x21b0200) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x7f1583423775 in QThreadPrivate::start (arg=0x21b0200) at thread/qthread_unix.cpp:248 #9 0x7f157d2029ca in start_thread (arg=value optimized out) at pthread_create.c:300 #10 0x7f15821636dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 1 (Thread 0x7f1585088780 (LWP 18902)): [KCrash Handler] #5 QBasicAtomicInt::ref (this=0x2ed73b0) at /usr/include/qt4/QtCore/qatomic_x86_64.h:121 #6 QList (this=0x2ed73b0) at /usr/include/qt4/QtCore/qlist.h:114 #7 KMail::FolderJob::msgList (this=0x2ed73b0) at ../../kmail/folderjob.cpp:120 #8 0x7f156b318793 in KMAcctImap::ignoreJobsForMessage (this=0x1d7e0d0, msg=0x2e7cc10) at ../../kmail/kmacctimap.cpp:217 #9 0x7f156b429d27 in KMMoveCommand::execute (this=0x2e82450) at ../../kmail/kmcommands.cpp:2192 #10 0x7f156b41b4fa in KMCommand::slotPostTransfer (this=0x2e82450, result=KMCommand::OK) at ../../kmail/kmcommands.cpp:291 #11 0x7f156b424e33 in KMCommand::qt_metacall (this=0x2e82450, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fffb5e83960) at ./kmcommands.moc:93 #12 0x7f156b4250e0 in KMMoveCommand::qt_metacall (this=0x7fffb5e83560, _c=49116080, _id=9, _a=0x2ec90) at ./kmcommands.moc:1971 #13 0x7f158352ae3f in QMetaObject::activate (sender=0x2e82450, m=value optimized out, local_signal_index=value optimized out, argv=0x2ec90) at kernel/qobject.cpp:3293 #14 0x7f156b4161ce in KMCommand::messagesTransfered (this=0x7fffb5e83560, _t1=KMCommand::OK) at ./kmcommands.moc:108 #15 0x7f156b42c7fc in KMCommand::transferSelectedMsgs (this=0x2e82450) at ../../kmail/kmcommands.cpp:389 #16 0x7f156b42ca08 in KMCommand::slotStart (this=0x2e82450) at ../../kmail/kmcommands.cpp:283 #17 0x7f156b424e16 in KMCommand::qt_metacall (this=0x2e82450, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fffb5e83bc0) at ./kmcommands.moc:92 #18 0x7f156b4250e0 in KMMoveCommand::qt_metacall (this=0x7fffb5e83560, _c=49116080, _id=9, _a=0x2ec90) at ./kmcommands.moc:1971 #19 0x7f158352ae3f in QMetaObject::activate (sender=0x20d7e20, m=value optimized out, local_signal_index=value optimized out, argv=0x2ec90) at kernel/qobject.cpp:3293 #20 0x7f158353265f in QSingleShotTimer::timerEvent (this=0x20d7e20) at kernel/qtimer.cpp:308 #21 0x7f1583527a63 in QObject::event (this=0x20d7e20, e=0x7fffb5e84320) at kernel/qobject.cpp:1212 #22 0x7f15828d122c in QApplicationPrivate::notify_helper (this=0x16e15b0, receiver=0x20d7e20, e=0x7fffb5e84320) at kernel/qapplication.cpp:4300 #23 0x7f15828d76fb in QApplication::notify (this=0x7fffb5e84680, receiver=0x20d7e20, e=0x7fffb5e84320) at kernel/qapplication.cpp:4183 #24 0x7f1583f00526 in KApplication::notify (this=0x7fffb5e84680, receiver=0x20d7e20, event=0x7fffb5e84320) at ../../kdeui/kernel/kapplication.cpp:302 #25 0x7f158351806c in QCoreApplication::notifyInternal (this=0x7fffb5e84680, receiver=0x20d7e20, event=0x7fffb5e84320) at kernel/qcoreapplication.cpp:704 #26 0x7f1583544d42 in QCoreApplication::sendEvent (this=0x16e6440) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #27 QTimerInfoList::activateTimers (this=0x16e6440) at kernel/qeventdispatcher_unix.cpp:603 #28 0x7f1583541824 in timerSourceDispatch (source=value optimized
[Bug 234583] New: Crashed when sending an email after being asked for the outgoing password.
https://bugs.kde.org/show_bug.cgi?id=234583 Summary: Crashed when sending an email after being asked for the outgoing password. Product: kontact Version: 4.4.2 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: laurent.gandil...@gmail.com Application: kontact (4.4.2) KDE Platform Version: 4.4.2 (KDE 4.4.2) Qt Version: 4.6.2 Operating System: Linux 2.6.32-21-generic i686 Distribution: Ubuntu lucid (development branch) -- Information about the crash: 1-I tried to send an email but no outgoing accounts were setup yet. (I had an error message saying that I needed to setup an outgoing account first.) -- My email was saved into the outbox. 2-I set-up the outgoing account and tried again (right click on outbox and send Queued Messages) This time, my identity was not correct, so I had to fill in my email address. 3-Right after last step, I did try to send my message again (right click on outbox and send Queud Messages). I was asked for my password to send the message (that was the first time). I entered it, clicked OK and that's where kontact crashed. I did turn on the application again, my email was still in the outbox, I sent it and it worked. The crash does not seem to be reproducible. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0xb76df990 (LWP 3791))] Thread 2 (Thread 0xb148eb70 (LWP 3884)): #0 0x084b6e16 in clock_gettime () from /lib/tls/i686/cmov/librt.so.1 #1 0x011576fb in qt_gettime () at kernel/qcore_unix.cpp:111 #2 0x0115c825 in QTimerInfoList::updateCurrentTime (this=0x95ad37c) at kernel/qeventdispatcher_unix.cpp:340 #3 0x0115c86a in QTimerInfoList::timerWait (this=0x95ad37c, tm=...) at kernel/qeventdispatcher_unix.cpp:443 #4 0x0115a818 in timerSourcePrepareHelper (src=value optimized out, timeout=0xb148e0ac) at kernel/qeventdispatcher_glib.cpp:136 #5 0x0115a8a5 in timerSourcePrepare (source=0x0, timeout=0x84baff4) at kernel/qeventdispatcher_glib.cpp:169 #6 0x01e41aca in g_main_context_prepare () from /lib/libglib-2.0.so.0 #7 0x01e41ee9 in ?? () from /lib/libglib-2.0.so.0 #8 0x01e424b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #9 0x0115a60f in QEventDispatcherGlib::processEvents (this=0x8a02680, flags=...) at kernel/qeventdispatcher_glib.cpp:414 #10 0x0112d059 in QEventLoop::processEvents (this=0xb148e270, flags=) at kernel/qeventloop.cpp:149 #11 0x0112d4aa in QEventLoop::exec (this=0xb148e270, flags=...) at kernel/qeventloop.cpp:201 #12 0x010295a8 in QThread::exec (this=0x95ae2b0) at thread/qthread.cpp:487 #13 0x0110cc1b in QInotifyFileSystemWatcherEngine::run (this=0x95ae2b0) at io/qfilesystemwatcher_inotify.cpp:248 #14 0x0102c32e in QThreadPrivate::start (arg=0x95ae2b0) at thread/qthread_unix.cpp:248 #15 0x028e196e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #16 0x00e779de in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 1 (Thread 0xb76df990 (LWP 3791)): [KCrash Handler] #6 0x0298c934 in MailTransport::AddTransportDialog::accept (this=0x9744ef0) at ../../mailtransport/addtransportdialog.cpp:139 #7 0x00251443 in KDialog::slotButtonClicked (this=0x9744ef0, button=4) at ../../kdeui/dialogs/kdialog.cpp:863 #8 0x00253559 in KDialog::qt_metacall (this=0x9744ef0, _c=QMetaObject::InvokeMetaMethod, _id=33, _a=0xbf833e08) at ./kdialog.moc:190 #9 0x0298c76a in MailTransport::AddTransportDialog::qt_metacall (this=0x9744ef0, _c=QMetaObject::InvokeMetaMethod, _id=69, _a=0xbf833e08) at ./addtransportdialog.moc:68 #10 0x01133c9a in QMetaObject::metacall (object=0x9744ef0, cl=QMetaObject::ReadProperty, idx=69, argv=0xbf833e08) at kernel/qmetaobject.cpp:237 #11 0x011423d5 in QMetaObject::activate (sender=0x964e688, m=0x12410f8, local_signal_index=0, argv=0xbf833e08) at kernel/qobject.cpp:3293 #12 0x01147b13 in QSignalMapper::mapped (this=0x964e688, _t1=4) at .moc/release-shared/moc_qsignalmapper.cpp:101 #13 0x01148d8d in QSignalMapper::map (this=0x964e688, sender=0x93b2970) at kernel/qsignalmapper.cpp:266 #14 0x01148f6e in QSignalMapper::map (this=0x964e688) at kernel/qsignalmapper.cpp:257 #15 0x0114903b in QSignalMapper::qt_metacall (this=0x964e688, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbf833fa8) at .moc/release-shared/moc_qsignalmapper.cpp:87 #16 0x01133c9a in QMetaObject::metacall (object=0x964e688, cl=QMetaObject::ReadProperty, idx=8, argv=0xbf833fa8) at kernel/qmetaobject.cpp:237 #17 0x011423d5 in QMetaObject::activate (sender=0x93b2970, m=0x4d398c4, local_signal_index=2, argv=0xbf833fa8) at kernel/qobject.cpp:3293 #18 0x04b29479 in QAbstractButton::clicked (this=0x93b2970, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:206 #19 0x04808ea9
[Bug 169646] Kmail crashes when applying filter with no rules
https://bugs.kde.org/show_bug.cgi?id=169646 Siu Chung (Clement) Cheung clement...@gmail.com changed: What|Removed |Added CC||clement...@gmail.com --- Comment #4 from Siu Chung (Clement) Cheung clement cc gmail com 2010-04-17 05:41:45 --- This bug is still happening. kmail 1.13.2 KDE 4.4.2 linux kernel 2.6.33-gentoo-r1 (x86_64) Gentoo packages. Interestingly, my other setup with 32-bit linux on Sabayon Linux doesn't crash using exact same rule. Not sure why. Backtrace: Thread 1 (Thread 0x7f457240c750 (LWP 11155)): [KCrash Handler] #5 0x7f4570dbfb62 in KMail::ActionScheduler::actionMessage(KMFilterAction::ReturnCode) () from /usr/lib64/libkmailprivate.so.4 #6 0x7f4570dbfe1a in KMail::ActionScheduler::filterMessage() () from /usr/lib64/libkmailprivate.so.4 #7 0x7f4570dc05ba in KMail::ActionScheduler::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkmailprivate.so.4 #8 0x7f456ccb7147 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4 #9 0x7f456ccb3bd3 in QObject::event(QEvent*) () from /usr/lib64/qt4/libQtCore.so.4 Liberal sprinkling of debug statements in the area reveals that the variable action is pointing at 0x21, an invalid but non-zero address which passes the mFilterAction check in actionMessage(). This causes a segfault when accessed later. How does that happen? Here's the current code that checks for the end of the action list: 498 KMFilterAction *action = mFilterAction; 499 // mFilterAction = (*mFilterIt).actions()-next(); 500 if ( ++mFilterActionIt == (*mFilterIt)-actions()-end() ) 501 mFilterAction = 0; 502 else mFilterAction = (*mFilterActionIt); 503 action-processAsync( *mMessageIt ); 504 } The problem is we're checking if the *NEXT* action is the end. What about the *CURRENT* one? Sure it's supposed to be already checked when we advance the pointer there. Except that the first action isn't assigned by this iterator advancing code. It's initialized in filterMessage(): mFilterActionIt = (*mFilterIt)-actions()-begin(); mFilterAction = (*mFilterActionIt); actionMessage(); What's happening here is that begin() == end() since the list is empty. We didn't verify that mFilterActionIt isn't end (and therefore invalid) before dereferencing it. Since this is an iterator, not a pointer, we won't crash -- yet. But mFilterAction will get random garbage. If said random garbage happens to be non-zero, actionMessage() will then try to dereference it as a pointer and hence the crash. -- 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 169646] Kmail crashes when applying filter with no rules
https://bugs.kde.org/show_bug.cgi?id=169646 --- Comment #6 from Siu Chung (Clement) Cheung clement cc gmail com 2010-04-17 05:54:55 --- As a temporary work around, people like me who need this to set a stop processing here rule with no action and matching sender = my_b...@my_company.com to make sure important messages doesn't get filtered can assign a sound as action. That action will have no effect except being extremely irritating when a whole bunch of messages matching the rule arrives. This can be avoided by recording a wav file of silence and using it as the action. -- 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
