[Bug 232655] New: kontact: categories missing and more hints
https://bugs.kde.org/show_bug.cgi?id=232655 Summary: kontact: categories missing and more hints Product: kontact Version: 4.4.1 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: andreas.ka...@gmx.de Version: 4.4.1 (using KDE 4.4.1) OS:Linux Installed from:Ubuntu Packages kontact, addressbook: - categories missing - change of visible name does not change display name in address field (small bug) - cannot delete phone numbers to less than three - modal dialogs are unconvenient for information adjustment between address entries - switch focus to a search field: if at this moment the string is completely selected it would improve usability = to enter a new search string there is no need for a special action to delete the old content - mark found search string in contact display make it easier to know why a special contact is displayed - focus handling inconsistent: input search string, enter, arrow-down == nothing visual happen (*1), next arrow-down = select next contact entry. Expectation: first arrow down should select the next entry. *1: if selection doesn't change and a contact below the first is already selected, the first contact becomes selected with the first arrow-down - expectation: reselect to the first contact when search is executed and the old selection is defunct mail: - switch mail by keyboard is inconsisten: arrow-up/-down if focus in mail selection frame (upper right) or mailbox tree frame (left) does not select between mails/boxes. Expectation: if focus in that frame arrow-up/-down should move selection in that frame. Focus should turned round with tab key. If focus is not in a frame where arrow-up/-down makes sense, the current handling of arrow and page keys is good. Tab key should reduce to frame and menu/function handling kalendar: - focus/keyboard handling needs lot of improvement Happy hacking, Andi -- 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 229553] Inlining or attaching Image from Clipboard causes Kontact to crash [QMimeData::hasImage, KPIMTextEdit::TextEdit::insertFromMimeData, KMComposerEditor::insertFromMimeData]
https://bugs.kde.org/show_bug.cgi?id=229553 Kapcsándi István istvan.kapcsa...@gmail.com changed: What|Removed |Added CC||istvan.kapcsa...@gmail.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 229553] Inlining or attaching Image from Clipboard causes Kontact to crash [QMimeData::hasImage, KPIMTextEdit::TextEdit::insertFromMimeData, KMComposerEditor::insertFromMimeData]
https://bugs.kde.org/show_bug.cgi?id=229553 --- Comment #3 from Kapcsándi István istvan kapcsandi gmail com 2010-03-30 09:22:02 --- Created an attachment (id=42372) -- (http://bugs.kde.org/attachment.cgi?id=42372) New crash information added by DrKonqi Steps to reproduce: 1. take a snapshot with ksnapshot 2. click on 'copy to clipboard' 3. go to kmail, create a new mail 4. paste the image into the mail as inline or as attachment. Last step cause kmail 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 232674] New: kontact address: vcf import of a vcf exported entry cause a duplicate
https://bugs.kde.org/show_bug.cgi?id=232674 Summary: kontact address: vcf import of a vcf exported entry cause a duplicate Product: kontact Version: 4.4.1 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: andreas.ka...@gmx.de Version: 4.4.1 (using KDE 4.4.1) OS:Linux Installed from:Ubuntu Packages vcf export exports a uid for each entry. Import therefor should avoid duplicate generation if uid is same - but it creates a duplicate. -- 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 232678] New: Crashes when filtering messages on imap
https://bugs.kde.org/show_bug.cgi?id=232678 Summary: Crashes when filtering messages on imap Product: kmail Version: 1.12.4 Platform: Debian testing OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: robert.wohl...@gmx.de Version: 1.12.4 (using KDE 4.3.4) OS:Linux Installed from:Debian testing/unstable Packages I have two different imap servers. One is gmail and the other one is a intranet server with cyrus2.2. My filter settings first check if the mail is from the imap account at gmail. If this is true then we stop processing there (just a check for = 0 bytes and in advanced tab that we only do that for gmai-imap). The other filter just check for different criterias to sort them in the right folders - like spam assasin and clamav. Now I get a mail from gmail imap and kmail crashes with following backtrace: Program received signal SIGSEGV, Segmentation fault. #0 KMail::ActionScheduler::actionMessage (this=value optimized out, res=value optimized out) at ../../kmail/actionscheduler.cpp:675 action = value optimized out msg = value optimized out #1 0x003694207e09 in KMail::ActionScheduler::filterMessage (this=value optimized out) at ../../kmail/actionscheduler.cpp:648 No locals. #2 0x0036942081c4 in KMail::ActionScheduler::qt_metacall (this=value optimized out, _c=value optimized out, _id=value optimized out, _a=value optimized out) at ./actionscheduler.moc:124 No locals. #3 0x0039e1f66df2 in QMetaObject::activate (sender=value optimized out, from_signal_index=value optimized out, to_signal_index=value optimized out, argv=value optimized out) at kernel/qobject.cpp:3112 previousSender = value optimized out method = value optimized out currentSender = Could not find the frame base for QMetaObject::activate(QObject*, int, int, void**). Or the longer (non bt-full): #0 KMail::ActionScheduler::actionMessage (this=value optimized out, res=value optimized out) at ../../kmail/actionscheduler.cpp:675 #1 0x003694207e09 in KMail::ActionScheduler::filterMessage (this=value optimized out) at ../../kmail/actionscheduler.cpp:648 #2 0x0036942081c4 in KMail::ActionScheduler::qt_metacall (this=value optimized out, _c=value optimized out, _id=value optimized out, _a=value optimized out) at ./actionscheduler.moc:124 #3 0x0039e1f66df2 in QMetaObject::activate (sender=value optimized out, from_signal_index=value optimized out, to_signal_index=value optimized out, argv=value optimized out) at kernel/qobject.cpp:3112 #4 0x0039e1f61353 in QObject::event (this=value optimized out, e=value optimized out) at kernel/qobject.cpp:1074 #5 0x0039e25d801d in QApplicationPrivate::notify_helper (this=value optimized out, receiver=value optimized out, e=value optimized out) at kernel/qapplication.cpp:4065 #6 0x0039e25e007a in QApplication::notify (this=value optimized out, receiver=value optimized out, e=value optimized out) at kernel/qapplication.cpp:4030 #7 0x0039e4a22de6 in KApplication::notify (this=value optimized out, receiver=value optimized out, event=value optimized out) at ../../kdeui/kernel/kapplication.cpp:302 #8 0x0039e1f51c9c in QCoreApplication::notifyInternal (this=value optimized out, receiver=value optimized out, event=value optimized out) at kernel/qcoreapplication.cpp:610 #9 0x0039e1f7e2c6 in QCoreApplication::sendEvent (this=value optimized out) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #10 QTimerInfoList::activateTimers (this=value optimized out) at kernel/qeventdispatcher_unix.cpp:580 #11 0x0039e1f7a658 in timerSourceDispatch (source=value optimized out) at kernel/qeventdispatcher_glib.cpp:184 #12 idleTimerSourceDispatch (source=value optimized out) at kernel/qeventdispatcher_glib.cpp:231 #13 0x003ce243b90e in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #14 0x003ce243f2c8 in ?? () from /lib/libglib-2.0.so.0 #15 0x003ce243f3f0 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #16 0x0039e1f7a39c in QEventDispatcherGlib::processEvents (this=value optimized out, flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:407 #17 0x0039e266ef1f in QGuiEventDispatcherGlib::processEvents (this=value optimized out, flags=value optimized out) at kernel/qguieventdispatcher_glib.cpp:202 #18 0x0039e1f50562 in QEventLoop::processEvents (this=value optimized out, flags=value optimized out) at kernel/qeventloop.cpp:149 #19 0x0039e1f50934 in QEventLoop::exec (this=value optimized out, flags=value optimized out) at kernel/qeventloop.cpp:201 #20 0x0039e1f52ba4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #21 0x00402fa9 in main (argc=value optimized out, argv=value optimized out) at
[Bug 232683] New: kontact crashes on startup (usually only the first time), korganizer already in system tray
https://bugs.kde.org/show_bug.cgi?id=232683 Summary: kontact crashes on startup (usually only the first time), korganizer already in system tray Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: sed...@alice.it 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-pae i686 Distribution: Ubuntu 9.10 What I was doing when the application crashed: Kontact crashes when i launch it clicking on its icon. It usually happens from the second time that i launch it, during the current session. When i try to launch it again it suddendly after, it goes well. If it might help: i have Korganizer and Knotes in the system tray (autostart). -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #6 0xb779b1fc in QString (this=0xa1f8220) at /usr/include/qt4/QtCore/qstring.h:711 #7 Kontact::Plugin::identifier (this=0xa1f8220) at ../../kontactinterfaces/plugin.cpp:97 #8 0xb77b550e in Kontact::MainWindow::activatePluginModule (this=0x9f74ac8) at ../../../kontact/src/mainwindow.cpp:303 #9 0xb77b55c4 in Kontact::MainWindow::setActivePluginModule (this=0x9f74ac8, module=...) at ../../../kontact/src/mainwindow.cpp:281 #10 0x0804bd0f in KontactApp::newInstance (this=0xbfb938b4) at ../../../kontact/src/main.cpp:147 #11 0xb74bf380 in KUniqueApplicationAdaptor::newInstance (this=0x9ef6d68, asn_id=..., args=...) at ../../kdeui/kernel/kuniqueapplication.cpp:459 #12 0xb74bfa92 in KUniqueApplicationAdaptor::qt_metacall (this=0x9ef6d68, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfb92edc) at ./kuniqueapplication_p.moc:75 #13 0xb58c77b4 in QDBusConnectionPrivate::deliverCall (this=0x9e74c90, object=0x9ef6d68, msg=..., metaTypes=..., slotIdx=4) at qdbusintegrator.cpp:891 #14 0xb58c89c5 in QDBusConnectionPrivate::activateCall (this=0x9e74c90, object=0x9ef6d68, flags=337, msg=...) at qdbusintegrator.cpp:803 #15 0xb58c9234 in QDBusConnectionPrivate::activateObject (this=0x9e74c90, node=..., msg=..., pathStartPos=16) at qdbusintegrator.cpp:1347 #16 0xb58c94da in QDBusActivateObjectEvent::placeMetaCall (this=0xc22a868) at qdbusintegrator.cpp:1464 #17 0xb661b5fe in QObject::event (this=0xbfb938b4, e=0xc22a868) at kernel/qobject.cpp: #18 0xb660affb in QCoreApplication::event (this=0xbfb938b4, e=0xc22a868) at kernel/qcoreapplication.cpp:1434 #19 0xb6a6d9a6 in QApplication::event (this=0xbfb938b4, e=0xc22a868) at kernel/qapplication.cpp:2317 #20 0xb6a67f54 in QApplicationPrivate::notify_helper (this=0x9e8cad8, receiver=0xbfb938b4, e=0xc22a868) at kernel/qapplication.cpp:4056 #21 0xb6a6f67c in QApplication::notify (this=0xbfb938b4, receiver=0xbfb938b4, e=0xc22a868) at kernel/qapplication.cpp:3603 #22 0xb74b7bfa in KApplication::notify (this=0xbfb938b4, receiver=0xbfb938b4, event=0xc22a868) at ../../kdeui/kernel/kapplication.cpp:302 #23 0xb660b6cb in QCoreApplication::notifyInternal (this=0xbfb938b4, receiver=0xbfb938b4, event=0xc22a868) at kernel/qcoreapplication.cpp:610 #24 0xb660c2b2 in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x9e5c820) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #25 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x9e5c820) at kernel/qcoreapplication.cpp:1247 #26 0xb660c47d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140 #27 0xb66363ff in QCoreApplication::sendPostedEvents (s=0x9e8a390) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218 #28 postEventSourceDispatch (s=0x9e8a390) at kernel/qeventdispatcher_glib.cpp:210 #29 0xb4900e88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #30 0xb4904730 in ?? () from /lib/libglib-2.0.so.0 #31 0xb4904863 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #32 0xb663602c in QEventDispatcherGlib::processEvents (this=0x9e5c9f8, flags=...) at kernel/qeventdispatcher_glib.cpp:327 #33 0xb6b08be5 in QGuiEventDispatcherGlib::processEvents (this=0x9e5c9f8, flags=...) at kernel/qguieventdispatcher_glib.cpp:202 #34 0xb6609c79 in QEventLoop::processEvents (this=0xbfb93814, flags=) at kernel/qeventloop.cpp:149 #35 0xb660a0ca in QEventLoop::exec (this=0xbfb93814, flags=...) at kernel/qeventloop.cpp:201 #36 0xb660c53f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #37 0xb6a67dd7 in QApplication::exec () at kernel/qapplication.cpp:3525 #38 0x0804b4e6 in main (argc=1, argv=0xbfb93ad4) 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.
[Bug 193514] Crash when activating plugin [[Kontact::Plugin::identifier], Kontact::MainWindow::activatePluginModule, Kontact::MainWindow::setActivePluginModule, KontactApp::newInstance]
https://bugs.kde.org/show_bug.cgi?id=193514 Christophe Giboudeaux cgiboude...@gmail.com changed: What|Removed |Added CC||sed...@alice.it --- Comment #83 from Christophe Giboudeaux cgiboudeaux gmail com 2010-03-30 12:48:54 --- *** Bug 232683 has been marked as a duplicate of this 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 232683] kontact crashes on startup (usually only the first time), korganizer already in system tray
https://bugs.kde.org/show_bug.cgi?id=232683 Christophe Giboudeaux cgiboude...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||DUPLICATE --- Comment #1 from Christophe Giboudeaux cgiboudeaux gmail com 2010-03-30 12:48:54 --- *** This bug has been marked as a duplicate of bug 193514 *** -- 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 232678] Crashes when filtering messages on imap
https://bugs.kde.org/show_bug.cgi?id=232678 --- Comment #1 from Robert Wohlrab robert wohlrab gmx de 2010-03-30 12:59:11 --- Just build everything with debug and -O0. Program received signal SIGSEGV, Segmentation fault. 0x7784e8a0 in KMail::ActionScheduler::actionMessage (this=0x1868fa0, res=KMFilterAction::GoOn) at ../../kmail/actionscheduler.cpp:675 675 action-processAsync( msg ); Just received a message on gmail imap and that is the backtrace: #0 0x7784e8a0 in KMail::ActionScheduler::actionMessage (this=0x1868fa0, res=KMFilterAction::GoOn) at ../../kmail/actionscheduler.cpp:675 action = 0x41 msg = 0x69d6a0 #1 0x7784e6ad in KMail::ActionScheduler::filterMessage (this=0x1868fa0) at ../../kmail/actionscheduler.cpp:648 No locals. #2 0x778505aa in KMail::ActionScheduler::qt_metacall (this=0x1868fa0, _c=QMetaObject::InvokeMetaMethod, _id=17, _a=0x7fffd3d0) at ./actionscheduler.moc:124 No locals. #3 0x0039e1f66df2 in QMetaObject::activate (sender=value optimized out, from_signal_index=value optimized out, to_signal_index=value optimized out, argv=value optimized out) at kernel/qobject.cpp:3112 previousSender = value optimized out method = value optimized out currentSender = Could not find the frame base for QMetaObject::activate(QObject*, int, int, void**). Simple backtrace: #0 0x7784e8a0 in KMail::ActionScheduler::actionMessage (this=0x1868fa0, res=KMFilterAction::GoOn) at ../../kmail/actionscheduler.cpp:675 #1 0x7784e6ad in KMail::ActionScheduler::filterMessage (this=0x1868fa0) at ../../kmail/actionscheduler.cpp:648 #2 0x778505aa in KMail::ActionScheduler::qt_metacall (this=0x1868fa0, _c=QMetaObject::InvokeMetaMethod, _id=17, _a=0x7fffd3d0) at ./actionscheduler.moc:124 #3 0x0039e1f66df2 in QMetaObject::activate (sender=value optimized out, from_signal_index=value optimized out, to_signal_index=value optimized out, argv=value optimized out) at kernel/qobject.cpp:3112 #4 0x0039e1f61353 in QObject::event (this=value optimized out, e=value optimized out) at kernel/qobject.cpp:1074 #5 0x0039e25d801d in QApplicationPrivate::notify_helper (this=value optimized out, receiver=value optimized out, e=value optimized out) at kernel/qapplication.cpp:4065 #6 0x0039e25e007a in QApplication::notify (this=value optimized out, receiver=value optimized out, e=value optimized out) at kernel/qapplication.cpp:4030 #7 0x0039e4a22de6 in KApplication::notify (this=value optimized out, receiver=value optimized out, event=value optimized out) at ../../kdeui/kernel/kapplication.cpp:302 #8 0x0039e1f51c9c in QCoreApplication::notifyInternal (this=value optimized out, receiver=value optimized out, event=value optimized out) at kernel/qcoreapplication.cpp:610 #9 0x0039e1f7e2c6 in QCoreApplication::sendEvent (this=value optimized out) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #10 QTimerInfoList::activateTimers (this=value optimized out) at kernel/qeventdispatcher_unix.cpp:580 #11 0x0039e1f7a658 in timerSourceDispatch (source=value optimized out) at kernel/qeventdispatcher_glib.cpp:184 #12 idleTimerSourceDispatch (source=value optimized out) at kernel/qeventdispatcher_glib.cpp:231 #13 0x003ce243b90e in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #14 0x003ce243f2c8 in ?? () from /lib/libglib-2.0.so.0 #15 0x003ce243f3f0 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #16 0x0039e1f7a39c in QEventDispatcherGlib::processEvents (this=value optimized out, flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:407 #17 0x0039e266ef1f in QGuiEventDispatcherGlib::processEvents (this=value optimized out, flags=value optimized out) at kernel/qguieventdispatcher_glib.cpp:202 #18 0x0039e1f50562 in QEventLoop::processEvents (this=value optimized out, flags=value optimized out) at kernel/qeventloop.cpp:149 #19 0x0039e1f50934 in QEventLoop::exec (this=value optimized out, flags=value optimized out) at kernel/qeventloop.cpp:201 #20 0x0039e1f52ba4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #21 0x0040364b in main (argc=2, argv=0x7fffe078) at ../../kmail/main.cpp:146 -- 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 226242] Kontact freezes after adding event to calendar through Akonadi Google Connector
https://bugs.kde.org/show_bug.cgi?id=226242 --- Comment #4 from Tassilo Horn tassilo member fsf org 2010-03-30 13:01:26 --- Bug 221445 is also related, or maybe this bug is a duplicate of 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 226636] kontact freezes when adding new event after using summary view
https://bugs.kde.org/show_bug.cgi?id=226636 --- Comment #5 from Tassilo Horn tassilo member fsf org 2010-03-30 13:02:40 --- Related (or duplicates) seem to be bug 221445 and bug 226242. -- 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 232678] Crashes when filtering messages on imap
https://bugs.kde.org/show_bug.cgi?id=232678 --- Comment #2 from Robert Wohlrab robert wohlrab gmx de 2010-03-30 13:05:21 --- It doesn't seem to happen when I receive a message in the cyrus2.2 imapd. My first configuration was pop3 on the intranet server and imap with the gmail server. But since the configuration of the intranet server was changed, I have to use imap on them. I had never such problems when the the intranet server was pop3 - but it confuses me that it crashes now when the filter runs on the gmail imap stuff (or better: should stop to process the filter list when it runs over the first filter rule). I can recreate the crash without any problems when I receive a message on gmail, but not with the intranet/cyrus2.2 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 232700] New: Kmail crashes when re-doing search on an existing search folder
https://bugs.kde.org/show_bug.cgi?id=232700 Summary: Kmail crashes when re-doing search on an existing search folder Product: kmail Version: 1.13.1 Platform: openSUSE RPMs OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: peeb...@gmail.com Application: kmail (1.13.1) KDE Platform Version: 4.4.1 (KDE 4.4.1) release 227 Qt Version: 4.6.2 Operating System: Linux 2.6.31.12-0.1-desktop i686 Distribution: openSUSE 11.2 (i586) -- Information about the crash: Often,kmail fails to update the search folder on a local folder.I select 'find messages' and start a re-search.Kmail crashes. This crash happens most of the times.But there are occassions when kmail does not crash. Also,when I go to find message dialog from an existing 'search folder',I expect to see the original search condition in the dialog.I never see that. The crash can be reproduced some of the time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #6 KMail::MessageListView::Widget::getSelectionStats (this=0x8264ca8, selectedSernums=..., selectedVisibleSernums=..., allSelectedBelongToSameThread=0xbffaf32f, includeCollapsedChildren=value optimized out) at /usr/src/debug/kdepim-4.4.1/kmail/messagelistview/widget.cpp:594 #7 0xb6eaa0b8 in KMail::MessageListView::Pane::getSelectionStats (this=0x83291c8, selectedSernums=..., selectedVisibleSernums=..., allSelectedBelongToSameThread=0xbffaf32f, includeCollapsedChildren= true) at /usr/src/debug/kdepim-4.4.1/kmail/messagelistview/pane.cpp:646 #8 0xb6d56bd7 in KMMainWidget::updateMessageActions (this=0x83276c0) at /usr/src/debug/kdepim-4.4.1/kmail/kmmainwidget.cpp:4226 #9 0xb6d6f61d in KMMainWidget::qt_metacall (this=0x83276c0, _c=InvokeMetaMethod, _id=21, _a=0xbffaf41c) at /usr/src/debug/kdepim-4.4.1/build/kmail/kmmainwidget.moc:375 #10 0xb670814d in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/libQtCore.so.4 #11 0xb6716faa in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #12 0xb676a3d5 in QTimer::timeout() () from /usr/lib/libQtCore.so.4 #13 0xb671f306 in QTimer::timerEvent(QTimerEvent*) () from /usr/lib/libQtCore.so.4 #14 0xb6713ab4 in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4 #15 0xb5c2b3fc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #16 0xb5c32248 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #17 0xb7533b81 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #18 0xb6702dde in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #19 0xb6732ffe in ?? () from /usr/lib/libQtCore.so.4 #20 0xb672fc62 in ?? () from /usr/lib/libQtCore.so.4 #21 0xb3d8e4c2 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #22 0xb3d91d98 in ?? () from /usr/lib/libglib-2.0.so.0 #23 0xb3d91ebe in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #24 0xb672f931 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #25 0xb5cebe0a in ?? () from /usr/lib/libQtGui.so.4 #26 0xb670144d in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #27 0xb6701899 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #28 0xb6705a10 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #29 0xb5c2b4a4 in QApplication::exec() () from /usr/lib/libQtGui.so.4 #30 0x0804ab1e in main (argc=3, argv=0xbffaff24) at /usr/src/debug/kdepim-4.4.1/kmail/main.cpp:156 Possible duplicates by query: bug 232468, bug 230934, bug 229253, bug 223084, bug 218693. 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 232700] Kmail crashes when re-doing search on an existing search folder
https://bugs.kde.org/show_bug.cgi?id=232700 Christophe Giboudeaux cgiboude...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||DUPLICATE --- Comment #1 from Christophe Giboudeaux cgiboudeaux gmail com 2010-03-30 15:22:19 --- *** This bug has been marked as a duplicate of bug 230934 *** -- 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 230934] First search became weird, then kmail went down
https://bugs.kde.org/show_bug.cgi?id=230934 Christophe Giboudeaux cgiboude...@gmail.com changed: What|Removed |Added CC||peeb...@gmail.com --- Comment #3 from Christophe Giboudeaux cgiboudeaux gmail com 2010-03-30 15:22:19 --- *** Bug 232700 has been marked as a duplicate of this 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 232702] New: Akonadi fails self-test, takes kmail out
https://bugs.kde.org/show_bug.cgi?id=232702 Summary: Akonadi fails self-test, takes kmail out Product: kmail Version: 1.13.1 Platform: Fedora RPMs OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: he...@starband.net Version: 1.13.1 (using KDE 4.4.1) OS:Linux Installed from:Fedora RPMs Akonadi fails self test when starting kmail after a fresh boot. Clicking Close on the Akonadi Server-Self test window closes kmail, too. Restarting kmail is usually successful. Self-test report: Akonadi Server Self-Test Report === Test 1: SUCCESS Database driver found. Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi server configuration and was found on your system. File content of '/home/cheiny/.config/akonadi/akonadiserverrc': [%General] Driver=QMYSQL SizeThreshold=4096 ExternalPayload=false [QMYSQL] Name=akonadi Host= User= Password= Options=UNIX_SOCKET=/home/cheiny/.local/share/akonadi/db_misc/mysql.socket ServerPath=/usr/libexec/mysqld StartServer=true [Debug] Tracer=null Test 2: SUCCESS MySQL server found. Details: You currently have configured Akonadi to use the MySQL server '/usr/libexec/mysqld'. Make sure you have the MySQL server installed, set the correct path and ensure you have the necessary read and execution rights on the server executable. The server executable is typically called 'mysqld', its locations varies depending on the distribution. Test 3: SUCCESS MySQL server is executable. Details: MySQL server found: /usr/libexec/mysqld Ver 5.1.44 for redhat-linux-gnu on x86_64 (Source distribution) Test 4: ERROR MySQL server log contains errors. Details: The MySQL server error log file apos;a href='/home/cheiny/.local/share/akonadi/db_data/mysql.err'/home/cheiny/.local/share/akonadi/db_data/mysql.err/aapos; contains errors. File content of '/home/cheiny/.local/share/akonadi/db_data/mysql.err': 100330 6:13:34 [Note] Plugin 'ndbcluster' is disabled. 100330 6:13:39 InnoDB: Started; log sequence number 0 6259251 100330 6:13:41 [Warning] Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without them 100330 6:13:41 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist 100330 6:13:41 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.44-log' socket: '/home/cheiny/.local/share/akonadi/db_misc/mysql.socket' port: 0 Source distribution Test 5: SUCCESS MySQL server default configuration found. Details: The default configuration for the MySQL server was found and is readable at a href='/etc/akonadi/mysql-global.conf'/etc/akonadi/mysql-global.conf/a. File content of '/etc/akonadi/mysql-global.conf': # # Global Akonadi MySQL server settings, # These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf # # Based on advice by Kris Köhntopp k...@mysql.com # [mysqld] skip_grant_tables skip_networking # strict query parsing/interpretation # TODO: make Akonadi work with those settings enabled #sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat #sql_mode=strict_trans_tables # use InnoDB for transactions and better crash recovery default_storage_engine=innodb # case-insensitive table names, avoids trouble on windows lower_case_table_names=1 character_set_server=latin1 collation_server=latin1_general_ci table_cache=200 thread_cache_size=3 log_bin=mysql-bin expire_logs_days=3 #sync_bin_log=0 # error log file name, relative to datadir log_error=mysql.err log_warnings=2 # log all queries, useful for debugging but generates an enormous amount of data #log=mysql.full # log queries slower than n seconds, log file name relative to datadir (for debugging only) #log_slow_queries=mysql.slow #long_query_time=1 # log queries not using indices, debug only, disable for production use #log_queries_not_using_indexes=1 # maximum blob size max_allowed_packet=32M max_connections=256 # makes sense when having the same query multiple times # makes no sense with prepared statements and/or transactions query_cache_type=0 query_cache_size=0 innodb_file_per_table=1 innodb_log_buffer_size=1M innodb_additional_mem_pool_size=1M # messure database size and adjust # SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in (mysql, information_schema); innodb_buffer_pool_size=80M # size of average write burst, keep Innob_log_waits small, keep Innodb_buffer_pool_wait_free small (see show global status like inno%, show global variables) innodb_log_file_size=8M innodb_flush_log_at_trx_commit=2
[Bug 232708] New: import and accepting fell Kontact
https://bugs.kde.org/show_bug.cgi?id=232708 Summary: import and accepting fell Kontact Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: adolfobana...@gmail.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.2 Operating System: Linux 2.6.31-20-generic x86_64 Distribution: Ubuntu 9.10 What I was doing when the application crashed: I was working in support of Dolphin for recovery my background contacts (. Vcf file) and selecting a file from dolphin it asked if I wanted to import and to accept Kontact crash -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault The current source language is auto; currently c. [KCrash Handler] #5 QListData::size (this=0x4040500) at /usr/include/qt4/QtCore/qlist.h:87 #6 QListQByteArray::count (this=0x4040500) at /usr/include/qt4/QtCore/qlist.h:250 #7 KCmdLineArgs::count (this=0x4040500) at ../../kdecore/kernel/kcmdlineargs.cpp:1530 #8 0x7f190d97efa6 in KABCore::handleCommandLine (this=value optimized out) at ../../kaddressbook/kabcore.cpp:1558 #9 0x7f190dbf6a78 in CoreAdaptor::qt_metacall (this=0x424f960, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff89613ee0) at kaddressbookpartadaptor.moc:104 #10 0x7f19376b0ad4 in QDBusConnectionPrivate::deliverCall (this=value optimized out, object=value optimized out, msg=value optimized out, metaTypes=..., slotIdx=value optimized out) at qdbusintegrator.cpp:891 #11 0x7f19376b1c69 in QDBusConnectionPrivate::activateCall (this=value optimized out, object=0x424f960, flags=273, msg=...) at qdbusintegrator.cpp:796 #12 0x7f19376b2547 in QDBusConnectionPrivate::activateObject (this=value optimized out, node=..., msg=value optimized out, pathStartPos=value optimized out) at qdbusintegrator.cpp:1347 #13 0x7f19376b2f11 in QDBusConnectionPrivate::handleObjectCall (this=value optimized out, msg=value optimized out) at qdbusintegrator.cpp:1443 #14 0x7f19376b3305 in QDBusConnectionPrivate::handleMessage (this=value optimized out, amsg=...) at qdbusintegrator.cpp:535 #15 0x7f19376b35dd in QDBusConnectionPrivate::sendWithReplyLocal (this=0x13ded90, message=...) at qdbusintegrator.cpp:1797 #16 0x7f19376b43bb in QDBusConnectionPrivate::sendWithReplyAsync (this=0x13ded90, message=..., timeout=value optimized out) at qdbusintegrator.cpp:1832 #17 0x7f193769d5d0 in QDBusConnection::asyncCall (this=value optimized out, message=..., timeout=563920) at qdbusconnection.cpp:542 #18 0x7f19376bbefb in QDBusAbstractInterface::asyncCallWithArgumentList (this=value optimized out, method=..., args=value optimized out) at qdbusabstractinterface.cpp:430 #19 0x7f192003ea7a in OrgKdeKAddressbookCoreInterface::handleCommandLine (this=value optimized out) at ./coreinterface.h:62 #20 KABUniqueAppHandler::newInstance (this=value optimized out) at ../../../../kontact/plugins/kaddressbook/kaddressbook_plugin.cpp:210 #21 0x7f193b2280f9 in Kontact::UniqueAppHandler::newInstance (this=0x1a51270, asn_id=value optimized out, args=...) at ../../kontactinterfaces/uniqueapphandler.cpp:128 #22 0x7f193b228164 in Kontact::UniqueAppHandler::qt_metacall (this=0x1a51270, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fff89614e60) at ./uniqueapphandler.moc:73 #23 0x7f19376b0ad4 in QDBusConnectionPrivate::deliverCall (this=value optimized out, object=value optimized out, msg=value optimized out, metaTypes=..., slotIdx=value optimized out) at qdbusintegrator.cpp:891 #24 0x7f19376b1c69 in QDBusConnectionPrivate::activateCall (this=value optimized out, object=0x1a51270, flags=272, msg=...) at qdbusintegrator.cpp:796 #25 0x7f19376b22d5 in QDBusConnectionPrivate::activateObject (this=value optimized out, node=..., msg=value optimized out, pathStartPos=value optimized out) at qdbusintegrator.cpp:1370 #26 0x7f19376b27c8 in QDBusActivateObjectEvent::placeMetaCall (this=0x3ff6910) at qdbusintegrator.cpp:1464 #27 0x7f19395900f9 in QObject::event (this=0x1a51270, e=0x3ff6910) at kernel/qobject.cpp: #28 0x7f1939ea0efc in QApplicationPrivate::notify_helper (this=0x1400a30, receiver=0x1a51270, e=0x3ff6910) at kernel/qapplication.cpp:4056 #29 0x7f1939ea81ce in QApplication::notify (this=0x7fff89615a70, receiver=0x1a51270, e=0x3ff6910) at kernel/qapplication.cpp:4021 #30 0x7f193aad7ab6 in KApplication::notify (this=0x7fff89615a70, receiver=0x1a51270, event=0x3ff6910) at ../../kdeui/kernel/kapplication.cpp:302 #31 0x7f1939580c2c in QCoreApplication::notifyInternal (this=0x7fff89615a70, receiver=0x1a51270, event=0x3ff6910) at kernel/qcoreapplication.cpp:610 #32 0x7f193958180a in QCoreApplication::sendEvent (receiver=0x0, event_type=value
[Bug 232708] import and accepting fell Kontact
https://bugs.kde.org/show_bug.cgi?id=232708 Christophe Giboudeaux cgiboude...@gmail.com changed: What|Removed |Added CC||to...@kde.org -- 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 232702] Akonadi fails self-test, takes kmail out
https://bugs.kde.org/show_bug.cgi?id=232702 Nicolas Lécureuil nlecure...@mandriva.com changed: What|Removed |Added CC||nlecure...@mandriva.com --- Comment #1 from Nicolas Lécureuil nlecureuil mandriva com 2010-03-30 18:02:43 --- i don't reproduce anymore but it really seems that we need to execute mysql_update too. -- 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 232728] New: items in read-only resource are editable
https://bugs.kde.org/show_bug.cgi?id=232728 Summary: items in read-only resource are editable Product: kaddressbook Version: unspecified Platform: Compiled Sources OS/Version: unspecified Status: NEW Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: wstephen...@kde.org CC: to...@kde.org Version:(using Devel) Installed from:Compiled sources If a resource is read-only: Expected behaviour: * Edit Contact... action is disabled * Double click on contact does not trigger action Observed behaviour: * Edit Contact... and double click both trigger the contact editor dialog * The dialog is empty -- 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 232741] New: my dns died so i can't reach my pop/smtp anymore. attempted to close kontact and crash
https://bugs.kde.org/show_bug.cgi?id=232741 Summary: my dns died so i can't reach my pop/smtp anymore. attempted to close kontact and 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: g.d...@z-c.it 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: my dns died so i can't reach my pop/smtp anymore. attempted to close kontact and crash -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #6 0x06eb56ad in KIO::Slave::deref() () from /usr/lib/libkio.so.5 #7 0x06eb5ec6 in KIO::Slave::gotInput() () from /usr/lib/libkio.so.5 #8 0x06eb8393 in KIO::Slave::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkio.so.5 #9 0x05506263 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4 #10 0x05506ec2 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #11 0x06dbf227 in KIO::Connection::readyRead() () from /usr/lib/libkio.so.5 #12 0x06dc0fee in ?? () from /usr/lib/libkio.so.5 #13 0x06dc111e in KIO::Connection::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkio.so.5 #14 0x054fef0b in QMetaCallEvent::placeMetaCall(QObject*) () from /usr/lib/libQtCore.so.4 #15 0x055005fe in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4 #16 0x00e2bf54 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #17 0x00e3367c in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #18 0x0032325a in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #19 0x054f06cb in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #20 0x054f12b2 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4 #21 0x054f147d in QCoreApplication::sendPostedEvents(QObject*, int) () from /usr/lib/libQtCore.so.4 #22 0x0551b3ff in ?? () from /usr/lib/libQtCore.so.4 #23 0x052afe88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #24 0x052b3730 in ?? () from /lib/libglib-2.0.so.0 #25 0x052b3863 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #26 0x0551b02c in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #27 0x00eccbe5 in ?? () from /usr/lib/libQtGui.so.4 #28 0x054eec79 in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #29 0x054ef0ca in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #30 0x054f153f in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #31 0x00e2bdd7 in QApplication::exec() () from /usr/lib/libQtGui.so.4 #32 0x0804b4e6 in _start () This bug may be a duplicate of or related to bug 219332 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 232741] my dns died so i can't reach my pop/smtp anymore. attempted to close kontact and crash
https://bugs.kde.org/show_bug.cgi?id=232741 Christophe Giboudeaux cgiboude...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||DUPLICATE --- Comment #1 from Christophe Giboudeaux cgiboudeaux gmail com 2010-03-30 19:49:22 --- *** This bug has been marked as a duplicate of bug 191589 *** -- 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 232751] New: searching in GMail IMAP fails
https://bugs.kde.org/show_bug.cgi?id=232751 Summary: searching in GMail IMAP fails Product: kmail Version: 1.13.2 Platform: openSUSE RPMs OS/Version: unspecified Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: silver.salo...@gmail.com Version: 1.13.2 (using KDE 4.4.1) Installed from:openSUSE RPMs I have added my GMail IMAP-account into KMail. Sometimes when I try to search from there (Inbox+subfolders), KMail reports: Error while searching. Searching of folder INBOX failed. The server returned: Could not parse command. After that I have occasional reports of the same thing. I don't think it's GMail's fault, because my wife uses her account on the same computer, but in Thunderbird and she never has any problems there, whereas I have multiple with KMail. -- 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 232047] Sometimes very high CPU-Consumption by XOrg and plasma-desktop 49-53% resp. 41-43%
https://bugs.kde.org/show_bug.cgi?id=232047 --- Comment #1 from Frans Leerink f leerink xs4all nl 2010-03-30 23:29:34 --- Hello, I have found out how to reproduce the high CPU consumptions by the 2 processes. It works as following: 1 I am reading in Kontact/kmail my mail messages in full screen window. After reading the mail I click closebutton (top right) By accident I click close again and that closes (unwanted) Kontact/Kmail 2 So I restart Kontact in the same desktop and that results in the 2 high CPU consumption processes. Only shutting down the system and start it again or the combined Restart version correct the high CPU consumption situation for the 2 mentioned processes. Hopefully this helps. Regards, Frans -- 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 232774] New: Email not shown for Google contacts with multiple e-mail addresses
https://bugs.kde.org/show_bug.cgi?id=232774 Summary: Email not shown for Google contacts with multiple e-mail addresses Product: kaddressbook Version: unspecified Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: l.plant...@cantab.net CC: to...@kde.org Version:(using KDE 4.4.1) OS:Linux Installed from:Ubuntu Packages I added an Akonadi Google Contacts Resource in the new KAddressBook, entered my details etc. I found that for any contact that has multiple e-mail addresses defined, none of the e-mail addresses show up at all. In vCard terms, the contact has multiple 'EMAIL;TYPE=INTERNET:' fields (when I export my Google address book). Also, similarly, if a contact has multiple phone numbers, none of them show up. In this case, it can be different 'types' of number in the exported vCard e.g.: TEL;TYPE=CELL:snipped TEL;TYPE=PAGER:snipped -- 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 223463] Option to show message structure lost after restart
https://bugs.kde.org/show_bug.cgi?id=223463 Thomas McGuire mcgu...@kde.org changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Comment #2 from Thomas McGuire mcguire kde org 2010-03-31 00:57:19 --- Fixed today by Andras. -- 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 225416] Commits for handling drags lost in porting
https://bugs.kde.org/show_bug.cgi?id=225416 Thomas McGuire mcgu...@kde.org changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Comment #2 from Thomas McGuire mcguire kde org 2010-03-31 01:05:28 --- SVN commit 1109288 by tmcguire: Update documentation about dragging attachments. Also, fix two typos. Now the bug about attachment dragging can be closed. BUG: 225416 M +8 -3 viewer_p.h WebSVN link: http://websvn.kde.org/?view=revrevision=1109288 -- 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 223438] Metabug for KMail 2 release blockers
https://bugs.kde.org/show_bug.cgi?id=223438 Bug 223438 depends on bug 225416, which changed state. Bug 225416 Summary: Commits for handling drags lost in porting http://bugs.kde.org/show_bug.cgi?id=225416 What|Old Value |New Value Status|NEW |RESOLVED Resolution||FIXED -- 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 232782] New: Encapsulated message viewing broken
https://bugs.kde.org/show_bug.cgi?id=232782 Summary: Encapsulated message viewing broken Product: kdepim Version: 4.5 Platform: Unlisted Binaries OS/Version: Linux Status: NEW Keywords: akonadi-ports-regression Severity: normal Priority: NOR Component: messageviewer AssignedTo: kdepim-bugs@kde.org ReportedBy: mcgu...@kde.org CC: aman...@kde.org Blocks: 223438 KMail 1 had the ability to view encapsulated messages, i.e. messages that are added as an attachment to other messages. Viewing them could be started by two ways: Clicking the Encapsulated Message link in the reader Clicking on the message in the message structure viewer I think for the first one, a separate reader window was launched. This all currently does not work. Some other implementation details: - When hitting reply or forward while viewing the encapsulated message, the reply/forward would be based on the encapsulated message, not on the original message. - Deleting or editing attachments of the encapsulated message should save the changes back to the original message. The window that displays the encapsulated message and the widget that displayed the original message both need to be updated. This probably requires some work to clean up the places dealing with KMime::Message::Ptr and the places dealing with Akonadi::Item. The API documentation of ViewerPrivate should be extended to clearly explain this matter. Also make sure the following cases work: https://issues.kolab.org/issue3740 This was hacked to work in the KMail 1 version with r1010835, r1010840 and r1071368. Here, it should be done in a cleaner way. -- 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 223438] Metabug for KMail 2 release blockers
https://bugs.kde.org/show_bug.cgi?id=223438 Thomas McGuire mcgu...@kde.org changed: What|Removed |Added Depends on||232782 -- 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
