[Bug 189779] New: Improve KMail's filters warning (on online IMAP account)
https://bugs.kde.org/show_bug.cgi?id=189779 Summary: Improve KMail's filters warning (on online IMAP account) Product: kmail Version: unspecified Platform: SuSE RPMs OS/Version: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: filtering AssignedTo: kdepim-bugs@kde.org ReportedBy: michal.vysko...@gmail.com Version:(using KDE 4.2.2) OS:Linux Installed from:SuSE RPMs KMail shows a warning if any of it's filters targets on online IMAP account. But this message is displayed even if no one of those filters has 'Apply this filter to incoming messages' active, or all filters has 'from all but online IMAP accounts' selected. KMail could check those circumstances. -- 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 189767] kmail goes unresponsive when moving many mails from one disconnected imap folder to another one
https://bugs.kde.org/show_bug.cgi?id=189767 --- Comment #1 from Tamás Németh 2009-04-16 08:46:51 --- I've forgotten to mention that I use Courier IMAP server. -- 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 189778] New: Sent folder does not have a different icon, showing its special purpose (disconnected imap)
https://bugs.kde.org/show_bug.cgi?id=189778 Summary: Sent folder does not have a different icon, showing its special purpose (disconnected imap) Product: kmail Version: unspecified Platform: SuSE RPMs OS/Version: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: n...@titanic.nyme.hu Version:(using KDE 4.2.2) OS:Linux Installed from:SuSE RPMs I use disconnected imap, sent items are stored in the imap folder "Sent" (courier imap). Although it's a special folder, it looks like any other general folder, except that it's placed directly under the INBOX. It should have a similar (or the same) icon as the local sent items folder. -- 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 189773] New: sudden crash when doing a search in local folders
https://bugs.kde.org/show_bug.cgi?id=189773 Summary: sudden crash when doing a search in local folders Product: kontact Version: 1.4.2 Platform: Debian testing OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: lepelerin2...@yahoo.com Version: 1.4.2 (using KDE 3.5.10) OS:Linux Installed from:Debian testing/unstable Packages while doing a search in local folders kontact crashed. Application: Kontact (kontact), signal SIGSEGV Thread 1 (Thread 0xb4a94700 (LWP 4000)): [KCrash Handler] #6 KMail::MessageListView::Widget::getSelectionStats (this=0x98d02f8, selectedsernu...@0xbfa2a568, selectedvisiblesernu...@0xbfa2a564, allSelectedBelongToSameThread=0xbfa2a56f, includeCollapsedChildren=) at ../../kmail/messagelistview/widget.cpp:579 #7 0xb18a7ca6 in KMail::MessageListView::Pane::getSelectionStats (this=0x99b, selectedsernu...@0xbfa2a568, selectedvisiblesernu...@0xbfa2a564, allSelectedBelongToSameThread=0xbfa2a56f, includeCollapsedChildren=) at ../../kmail/messagelistview/pane.cpp:578 #8 0xb17604e7 in KMMainWidget::updateMessageActions (this=0x9a08bc0) at ../../kmail/kmmainwidget.cpp:4289 #9 0xb177b998 in KMMainWidget::qt_metacall (this=0x9a08bc0, _c=QMetaObject::InvokeMetaMethod, _id=20, _a=0xbfa2a638) at ./kmmainwidget.moc:363 #10 0xb770bbe0 in QMetaObject::activate (sender=0x9acdab8, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3031 #11 0xb770c962 in QMetaObject::activate (sender=0x9acdab8, m=0xb77da0c4, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3101 #12 0xb7746867 in QTimer::timeout (this=0x9acdab8) at .moc/release-shared/moc_qtimer.cpp:126 #13 0xb771258e in QTimer::timerEvent (this=0x9acdab8, e=0xbfa2aacc) at kernel/qtimer.cpp:257 #14 0xb77066bf in QObject::event (this=0x9acdab8, e=0xbfa2aacc) at kernel/qobject.cpp:1120 #15 0xb6dec79c in QApplicationPrivate::notify_helper (this=0x952a448, receiver=0x9acdab8, e=0xbfa2aacc) at kernel/qapplication.cpp:3803 #16 0xb6df461e in QApplication::notify (this=0xbfa2ae7c, receiver=0x9acdab8, e=0xbfa2aacc) at kernel/qapplication.cpp:3393 #17 0xb7bd5b7d in KApplication::notify (this=0xbfa2ae7c, receiver=0x9acdab8, event=0xbfa2aacc) at ../../kdeui/kernel/kapplication.cpp:307 #18 0xb76f70e1 in QCoreApplication::notifyInternal (this=0xbfa2ae7c, receiver=0x9acdab8, event=0xbfa2aacc) at kernel/qcoreapplication.cpp:587 #19 0xb7725041 in QTimerInfoList::activateTimers (this=0x952d334) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:209 #20 0xb7721690 in timerSourceDispatch (source=0x952d300) at kernel/qeventdispatcher_glib.cpp:160 #21 0xb53f5848 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #22 0xb53f8dab in ?? () from /usr/lib/libglib-2.0.so.0 #23 0x0952c690 in ?? () #24 0x in ?? () -- 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 189769] New: kmail doesn't detect the state of a networkmanager controlled network
https://bugs.kde.org/show_bug.cgi?id=189769 Summary: kmail doesn't detect the state of a networkmanager controlled network Product: kmail Version: unspecified Platform: SuSE RPMs OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: n...@titanic.nyme.hu Version:(using KDE 4.2.2) OS:Linux Installed from:SuSE RPMs When my networkmanager controlled network goes down, kmail remains in online state. Firefox (and kmail in kde3 as far as I can remember) automatically changes its state to offline and back to online as networkmanager swithes to offline and back. In addition to this, even after switched to offline state manually, after some minutes, kmail starts to complain about an inexpectedly closed connection to the server. Why does it have open connections to the server when it's in disconnected state? Why doesn't it close all the connections then? -- 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 189767] New: kmail goes unresponsive when moving many mails from one disconnected imap folder to another one
https://bugs.kde.org/show_bug.cgi?id=189767 Summary: kmail goes unresponsive when moving many mails from one disconnected imap folder to another one Product: kmail Version: unspecified Platform: SuSE RPMs OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: n...@titanic.nyme.hu Version:(using KDE 4.2.2) OS:Linux Installed from:SuSE RPMs I sorted the mails by sender in the INBOX (which contains more than 16000 messages), selected about 50 consecutive mails, and stared to move the to another folder. Kmail wrote "Moving messages..." onto the status field (bottom left corner of the window), but the it started to use the hard drive heavily, get unresponsive (compiz made it gray), and virtually did nothing, not even showing a progress bar. I killed it, and realized, that it was trying to copy ALL the messages (not just the selected ones) from the INBOX to the destination folder, or something like that, at least the local copy of the destination dimap folder contained thousands of mails after killing 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 188931] kmail fails to verify signature with RFC 3156 encrypted+signed mails
https://bugs.kde.org/show_bug.cgi?id=188931 Raimar Sandner changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||FIXED --- Comment #2 from Raimar Sandner 2009-04-16 01:09:44 --- Seems to be fixed in kde-4.2.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 189601] printing option: "calendar week"
https://bugs.kde.org/show_bug.cgi?id=189601 Allen Winter changed: What|Removed |Added Component|calender|printing Version|unspecified |SVN trunk (KDE 4) Product|kmail |korganizer --- Comment #1 from Allen Winter 2009-04-16 00:32:30 --- reassigning to KOrganizer -- 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 189759] New: printing message directly from the composer prints headers, but an empty body
https://bugs.kde.org/show_bug.cgi?id=189759 Summary: printing message directly from the composer prints headers, but an empty body Product: kmail Version: unspecified Platform: SuSE RPMs OS/Version: unspecified Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: rei...@imageware.de Version:(using KDE 4.2.2) Installed from:SuSE RPMs Printing a message directly from the compose shows headers all right, but the body is always empty. This can be reproduced for a single message several times in a row and for each message that is composed. The printout is ok if the message has been stored to the drafts folder once or has been sent and is selected again from the sent messages folder. -- 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 188271] Cannot logon to newsgroup
https://bugs.kde.org/show_bug.cgi?id=188271 --- Comment #9 from Russ Fineman 2009-04-15 23:55:22 --- Just installed KDE 4.2.2 on one of my systems with Knode (kde4-knode-4.2.2-107.6). Still get the Mode Reader command error with this new version. Only occurs on news group that needs authentication. -- 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 171157] when answering mails adressed to my second email address, kget puts my first email adress in the CC field
https://bugs.kde.org/show_bug.cgi?id=171157 Oliver Putz changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |INVALID --- Comment #3 from Oliver Putz 2009-04-15 22:00:29 --- Hi! I was just going to write that I can still reproduce the problem. However, as embarrassing as it is, I just found out that what I described as a bug was a feature! (I just now realized that the described behavior only happens when I reply to a mail by hitting "a"... Just that "a" isn't the shortcut for a simple reply, but for a reply all... [which have the same behavior if you get mails addressed to the email address you configured in KMail]) Biig sorry for the noise this report created... -- 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 185163] kmail message thread by subject
https://bugs.kde.org/show_bug.cgi?id=185163 --- Comment #4 from Musthafa Meeran 2009-04-15 20:46:22 --- Reindexing & Refreshing the IMAP cache didn't help, still the same issue is there. I see in the 'Customize Message Aggregation Modes'->'Groups, Threads and Sorting' that, for Threading "Perfect, by References and by Subject" is chosen by default. I think, if there is an option to choose only based on Subject, then it might group those unthreaded messages also. I am not sure.. just guessing. Could you please help me out with this? Thanks a lot... -- 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 189724] New: attachements are saved with zero size
https://bugs.kde.org/show_bug.cgi?id=189724 Summary: attachements are saved with zero size Product: kmail Version: unspecified Platform: Gentoo Packages OS/Version: unspecified Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: or...@freehackers.org Version:(using KDE 4.2.2) Installed from:Gentoo Packages It currently happends with KDE 4.2.2, but it has been here for very long. Did not report previously as it seems such an obvious and big bug... So, most of the times (but not always, i would say it bugs 90% of the time), when i RMB on an attachement in the message window, and ask to save it, the file is created, but totally empty: -rw-r--r-- 1 orzel users0 2009-04-15 17:11 MyAttachement I've tried to understand the difference when it works and when it does nto work, but couldn't find any pattern. To solve this, i go the attachement sub-window (very bottom) and use the rmb entry "save all attachements...". The it mostly works Btw (I dont have time to report all kmail bugs), but the message window is completely white after this. Whether the attachement was saved or not, whether i use the first method or the second one... The window displaying the message is all blank. I need to click on another message in the message list, and then again on the original message to have the content displayed. After thi -- 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 186190] Using filters causes Korganizer to crush or they simple don't work
https://bugs.kde.org/show_bug.cgi?id=186190 Alex Back changed: What|Removed |Added CC||alex.b...@gmx.de --- Comment #3 from Alex Back 2009-04-15 15:30:17 --- I guess I'm confronting the same issue here. It happens whenever I add a new filter and then try to apply it afterwards. Fedora Core 10, KDE 4.2.1 Here's my backtrace (hope this will help you further, since I have debugging package installed) --snip-- Application: KOrganizer (korganizer), signal SIGSEGV [Current thread is 1 (Thread 0xb7f70770 (LWP 3382))] Thread 1 (Thread 0xb7f70770 (LWP 3382)): [KCrash Handler] #6 0x005a1b3e in KOTodoModel::moveIfParentChanged (this=0xa02fec8, curNode=0xa417c10, todo=0xa41c8e8, addParentIfMissing=true) at /usr/src/debug/kdepim-4.2.1/korganizer/views/todoview/kotodomodel.cpp:378 #7 0x005a277a in KOTodoModel::reloadTodos (this=0xa02fec8) at /usr/src/debug/kdepim-4.2.1/korganizer/views/todoview/kotodomodel.cpp:254 #8 0x005aa6a0 in KOTodoView::updateView (this=0xa0070b0) at /usr/src/debug/kdepim-4.2.1/korganizer/views/todoview/kotodoview.cpp:354 #9 0x005c7b5e in CalendarView::updateView (this=0x91f6830, sta...@0x92dc4cc, e...@0x92dc4cc, updateTodos=true) at /usr/src/debug/kdepim-4.2.1/korganizer/calendarview.cpp:815 #10 0x005c98fd in CalendarView::updateView (this=0x91f6830) at /usr/src/debug/kdepim-4.2.1/korganizer/calendarview.cpp:826 #11 0x005c7722 in CalendarView::filterActivated (this=0x91f6830, filterNo=4) at /usr/src/debug/kdepim-4.2.1/korganizer/calendarview.cpp:1738 #12 0x005d4dc6 in CalendarView::qt_metacall (this=0x91f6830, _c=QMetaObject::InvokeMetaMethod, _id=172, _a=0xbfeaa0cc) at /usr/src/debug/kdepim-4.2.1/i386-redhat-linux-gnu/korganizer/calendarview.moc:567 #13 0x01658750 in QMetaObject::activate (sender=0xa2fe2e0, from_signal_index=24, to_signal_index=24, argv=0xbfeaa0cc) at kernel/qobject.cpp:3031 #14 0x016594d2 in QMetaObject::activate (sender=0xa2fe2e0, m=0xfc0cb8, local_signal_index=1, argv=0xbfeaa0cc) at kernel/qobject.cpp:3101 #15 0x00d16823 in KSelectAction::triggered (this=0xa2fe2e0, _t1=4) at /usr/src/debug/kdelibs-4.2.1/i386-redhat-linux-gnu/kdeui/kselectaction.moc:165 #16 0x00d1829f in KSelectAction::actionTriggered (this=0xa2fe2e0, action=0xa65df48) at /usr/src/debug/kdelibs-4.2.1/kdeui/actions/kselectaction.cpp:312 #17 0x00d19564 in KSelectAction::qt_metacall (this=0xa2fe2e0, _c=QMetaObject::InvokeMetaMethod, _id=3, _a=0xbfeaa21c) at /usr/src/debug/kdelibs-4.2.1/i386-redhat-linux-gnu/kdeui/kselectaction.moc:104 #18 0x01658750 in QMetaObject::activate (sender=0xa2fe6b8, from_signal_index=4, to_signal_index=4, argv=0xbfeaa21c) at kernel/qobject.cpp:3031 #19 0x016594d2 in QMetaObject::activate (sender=0xa2fe6b8, m=0x1fe8c84, local_signal_index=0, argv=0xbfeaa21c) at kernel/qobject.cpp:3101 #20 0x01832833 in QActionGroup::triggered (this=0xa2fe6b8, _t1=0xa65df48) at .moc/release-shared/moc_qactiongroup.cpp:138 #21 0x018330e8 in QActionGroupPrivate::_q_actionTriggered (this=0xa2fe6c8) at kernel/qactiongroup.cpp:83 #22 0x018332fe in QActionGroup::qt_metacall (this=0xa2fe6b8, _c=QMetaObject::InvokeMetaMethod, _id=7, _a=0xbfeaa35c) at .moc/release-shared/moc_qactiongroup.cpp:94 #23 0x01658750 in QMetaObject::activate (sender=0xa65df48, from_signal_index=5, to_signal_index=6, argv=0xbfeaa35c) at kernel/qobject.cpp:3031 #24 0x01658b50 in QMetaObject::activate (sender=0xa65df48, m=0x1fe8c00, from_local_signal_index=1, to_local_signal_index=2, argv=0xbfeaa35c) at kernel/qobject.cpp:3121 #25 0x0182dcf1 in QAction::triggered (this=0xa65df48, _t1=true) at .moc/release-shared/moc_qaction.cpp:216 #26 0x0182e65f in QAction::activate (this=0xa65df48, event=QAction::Trigger) at kernel/qaction.cpp:1125 #27 0x01c0a7c4 in QMenuPrivate::activateAction (this=0xa2fe818, action=0xa65df48, action_e=QAction::Trigger, self=true) at widgets/qmenu.cpp:1002 #28 0x01c0b252 in QMenu::mouseReleaseEvent (this=0xa301710, e=0xbfeaaa38) at widgets/qmenu.cpp:2169 #29 0x00ec61b5 in KMenu::mouseReleaseEvent (this=0xa301710, e=0xbfeaaa38) at /usr/src/debug/kdelibs-4.2.1/kdeui/widgets/kmenu.cpp:454 #30 0x0188c052 in QWidget::event (this=0xa301710, event=0xbfeaaa38) at kernel/qwidget.cpp:7163 #31 0x01c0d549 in QMenu::event (this=0xa301710, e=0xbfeaaa38) at widgets/qmenu.cpp:2265 #32 0x01833fec in QApplicationPrivate::notify_helper (this=0x91ac550, receiver=0xa301710, e=0xbfeaaa38) at kernel/qapplication.cpp:3803 #33 0x0183c7e1 in QApplication::notify (this=0xbfeac3ac, receiver=0xa301710, e=0xbfeaaa38) at kernel/qapplication.cpp:3528 #34 0x00de70fd in KApplication::notify (this=0xbfeac3ac, receiver=0xa301710, event=0xbfeaaa38) at /usr/src/debug/kdelibs-4.2.1/kdeui/kernel/kapplication.cpp:307 #35 0x01643b21 in QCoreApplication::notifyInternal (this=0xbfeac3ac, receiver=0xa301710, event=0xbfeaaa38) at kernel/qcoreapplication.cpp:587 #36 0x0183ba6e in QCoreAp
[Bug 151970] crash when moving stuff from inbox to folders (both IMAP)
https://bugs.kde.org/show_bug.cgi?id=151970
Ruchir Brahmbhatt changed:
What|Removed |Added
Status|NEEDSINFO |NEW
Resolution|WAITINGFORINFO |
Ever Confirmed|0 |1
--- Comment #5 from Ruchir Brahmbhatt
2009-04-15 12:03:56 ---
I could just reproduced on kmail 1.11.2.
Account: Gmail IMAP.
Steps:
1. Move one mail from inbox to other folder(0test in my case) using drag/drop.
2. Move another mail from inbox to other folder(0test in my case) using right
click.
3. Repeat step 1. Boom.
Backtrace:
Application: KMail (kmail), signal SIGSEGV
[?1034h[Thread debugging using libthread_db enabled]
[Current thread is 1 (Thread 0xb3b20700 (LWP 16460))]
Thread 1 (Thread 0xb3b20700 (LWP 16460)):
[KCrash Handler]
#6 KMail::FolderJob::msgList (this=0x88ef078) at
/usr/include/QtCore/qatomic_i386.h:116
#7 0xb743973b in KMAcctImap::ignoreJobsForMessage (this=0x8211480,
msg=0x8aa0cc0) at /usr/src/debug/kdepim-4.2.2/kmail/kmacctimap.cpp:215
#8 0xb744dee5 in KMFolderImap::ignoreJobsForMessage (this=0x822ea30,
msg=0x8aa0cc0) at /usr/src/debug/kdepim-4.2.2/kmail/kmfolderimap.cpp:1562
#9 0xb7547814 in KMMoveCommand::execute (this=0x8aa9bb0) at
/usr/src/debug/kdepim-4.2.2/kmail/kmcommands.cpp:2086
#10 0xb7535c12 in KMCommand::slotPostTransfer (this=0x8aa9bb0,
result=KMCommand::OK) at /usr/src/debug/kdepim-4.2.2/kmail/kmcommands.cpp:276
#11 0xb753fd94 in KMCommand::qt_metacall (this=0x8aa9bb0,
_c=QMetaObject::InvokeMetaMethod, _id=5, _a=0xbfb640cc) at
/usr/src/debug/kdepim-4.2.2/build/kmail/kmcommands.moc:86
#12 0xb754028a in KMMoveCommand::qt_metacall (this=0x8aa9bb0,
_c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbfb640cc) at
/usr/src/debug/kdepim-4.2.2/build/kmail/kmcommands.moc:1662
#13 0xb6a5ec88 in QMetaObject::activate (sender=0x8aa9bb0, from_signal_index=4,
to_signal_index=4, argv=0xbfb640cc) at kernel/qobject.cpp:3069
#14 0xb6a60412 in QMetaObject::activate (sender=0x8aa9bb0, m=0xb79269d4,
local_signal_index=0, argv=0xbfb640cc) at kernel/qobject.cpp:3143
#15 0xb7531773 in KMCommand::messagesTransfered (this=0x8aa9bb0,
_t1=KMCommand::OK) at
/usr/src/debug/kdepim-4.2.2/build/kmail/kmcommands.moc:100
#16 0xb7549b94 in KMCommand::transferSelectedMsgs (this=0x8aa9bb0) at
/usr/src/debug/kdepim-4.2.2/kmail/kmcommands.cpp:370
#17 0xb7549d83 in KMCommand::slotStart (this=0x8aa9bb0) at
/usr/src/debug/kdepim-4.2.2/kmail/kmcommands.cpp:268
#18 0xb753fda3 in KMCommand::qt_metacall (this=0x8aa9bb0,
_c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbfb642a8) at
/usr/src/debug/kdepim-4.2.2/build/kmail/kmcommands.moc:85
#19 0xb754028a in KMMoveCommand::qt_metacall (this=0x8aa9bb0,
_c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbfb642a8) at
/usr/src/debug/kdepim-4.2.2/build/kmail/kmcommands.moc:1662
#20 0xb6a5ec88 in QMetaObject::activate (sender=0x88ef110, from_signal_index=4,
to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3069
#21 0xb6a60412 in QMetaObject::activate (sender=0x88ef110, m=0xb6b3e908,
local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3143
#22 0xb6a640f7 in QSingleShotTimer::timeout (this=0x88ef110) at
.moc/release-shared/qtimer.moc:76
#23 0xb6a6421c in QSingleShotTimer::timerEvent (this=0x88ef110) at
kernel/qtimer.cpp:298
#24 0xb6a5912f in QObject::event (this=0x88ef110, e=0xbfb64750) at
kernel/qobject.cpp:1082
#25 0xb5ef8eec in QApplicationPrivate::notify_helper (this=0x8078470,
receiver=0x88ef110, e=0xbfb64750) at kernel/qapplication.cpp:4084
#26 0xb5f011ae in QApplication::notify (this=0xbfb64a98, receiver=0x88ef110,
e=0xbfb64750) at kernel/qapplication.cpp:3631
#27 0xb7d32ded in KApplication::notify (this=0xbfb64a98, receiver=0x88ef110,
event=0xbfb64750) at
/usr/src/debug/kdelibs-4.2.2/kdeui/kernel/kapplication.cpp:307
#28 0xb6a489db in QCoreApplication::notifyInternal (this=0xbfb64a98,
receiver=0x88ef110, event=0xbfb64750) at kernel/qcoreapplication.cpp:602
#29 0xb6a78026 in QTimerInfoList::activateTimers (this=0x807ab7c) at
kernel/qcoreapplication.h:213
#30 0xb6a744d0 in timerSourceDispatch (source=0x807ab48) at
kernel/qeventdispatcher_glib.cpp:164
#31 0xb42c9d88 in IA__g_main_context_dispatch (context=0x807a290) at
gmain.c:1814
#32 0xb42cd2fb in g_main_context_iterate (context=0x807a290, block=1,
dispatch=1, self=0x8078248) at gmain.c:2448
#33 0xb42cd478 in IA__g_main_context_iteration (context=0x807a290, may_block=1)
at gmain.c:2511
#34 0xb6a74428 in QEventDispatcherGlib::processEvents (this=0x805d8d0, flags={i
= -1078572808}) at kernel/qeventdispatcher_glib.cpp:323
#35 0xb5f98ac5 in QGuiEventDispatcherGlib::processEvents (this=0x805d8d0,
flags={i = -1078572760}) at kernel/qguieventdispatcher_glib.cpp:202
#36 0xb6a46ffa in QEventLoop::processEvents (this=0xbfb649a0, flags={i =
-1078572696}) at kernel/qeventloop.cpp
[Bug 152504] Crash when sending mail from browser
https://bugs.kde.org/show_bug.cgi?id=152504 --- Comment #4 from Ruchir Brahmbhatt 2009-04-15 11:49:41 --- Just tried same on kmail 1.11.2 but can't reproduce. -- 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 100786] Apply filters to folders other than INBOX on dimap
https://bugs.kde.org/show_bug.cgi?id=100786 Christof Schulze changed: What|Removed |Added CC||christof.schu...@gmx.net --- Comment #5 from Christof Schulze 2009-04-15 11:45:21 --- *** Bug 160960 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 160960] for dimap filter for (all incoming mail" are only applied to "all incoming mail in inbox-folder" not its subfolders
https://bugs.kde.org/show_bug.cgi?id=160960 Christof Schulze changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||DUPLICATE --- Comment #2 from Christof Schulze 2009-04-15 11:45:20 --- it seems to be - closing *** This bug has been marked as a duplicate of bug 100786 *** -- 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 189705] New: click on search result doesn't select this email
https://bugs.kde.org/show_bug.cgi?id=189705 Summary: click on search result doesn't select this email Product: kmail Version: 1.11.2 Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: s...@gmx.de Version: 1.11.2 (using 4.2.2 (KDE 4.2.2) "release 111", KDE:KDE4:Factory:Desktop / openSUSE_11.1) Compiler: gcc OS:Linux (x86_64) release 2.6.27.21-0.1-default If I search for a email and select one of the result list. kmail view this email but doesn't select this in my inbox list. Now, if I want to reply this email, he doesn't use the right one. -- 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 189703] New: Auto spell check option before sending
https://bugs.kde.org/show_bug.cgi?id=189703 Summary: Auto spell check option before sending Product: kmail Version: 1.10.3 Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: gen37...@yahoo.co.uk Version: 1.10.3 (using 4.1.3 (KDE 4.1.3), Mandriva Linux release 2009.0 (Official) for i586) Compiler: gcc OS:Linux (i686) release 2.6.27.19-desktop586-1mnb Most email packages have an option to automatically do a spell check when you press 'send'. This can be an extremely useful function and can avoid the risk of accidentally sending an email full of spelling misteaks. -- 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 188641] kontact crashes in background with signal 6
https://bugs.kde.org/show_bug.cgi?id=188641 --- Comment #3 from Jens Schmidt 2009-04-15 10:03:38 --- Created an attachment (id=32849) --> (http://bugs.kde.org/attachment.cgi?id=32849) kcrash backtrace with "kdepim-dbg" KCrash Backtrace, after Kontact-Crash. "kdepim-dbg" is installed. Just added the same Attachement at Bug 187736. Just a Question: Why i didnt find "#188641" at "Search Existing-Report", only at "Check for Duplicate Bugs"? -- 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 187736] Kontact (kontact) crashed and caused the signal 6 (SIGABRT)
https://bugs.kde.org/show_bug.cgi?id=187736 --- Comment #1 from Jens Schmidt 2009-04-15 09:55:56 --- Created an attachment (id=32848) --> (http://bugs.kde.org/attachment.cgi?id=32848) kcrash backtrace with "kdepim-dbg" KCrash Backtrace after crashed kontact (with installed package "kdepim-dbg"). -- 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 189698] New: kontact crashes switching applications
https://bugs.kde.org/show_bug.cgi?id=189698 Summary: kontact crashes switching applications Product: kontact Version: 1.2.9 Platform: SuSE RPMs OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: r...@fietze-home.de Version: 1.2.9 (using KDE 3.5.10) OS:Linux Installed from:SuSE RPMs Kontact crashes e.g. when switching from kmail to korganizer. This happens multiple times a day. System configuration startup check disabled. [Thread debugging using libthread_db enabled] [New Thread 0x7fe25b6f2710 (LWP 17279)] [New Thread 0x4357e950 (LWP 17283)] [New Thread 0x42d7d950 (LWP 17282)] [New Thread 0x4257c950 (LWP 17281)] [New Thread 0x41d7b950 (LWP 17280)] [KCrash handler] #5 0x01c93230 in ?? () #6 0x7fe25877e5d5 in QApplication::internalNotify () from /usr/lib/qt3/lib64/libqt-mt.so.3 #7 0x7fe25877f3ba in QApplication::notify () from /usr/lib/qt3/lib64/libqt-mt.so.3 #8 0x7fe259317952 in KApplication::notify (this=0x7fff63739960, receiver=0x24e32c0, event=0x7fff63738e70) at ./kdecore/kapplication.cpp:552 #9 0x7fe25880f074 in QWidget::setFocus () from /usr/lib/qt3/lib64/libqt-mt.so.3 #10 0x7fe25877f4ed in QApplication::notify () from /usr/lib/qt3/lib64/libqt-mt.so.3 #11 0x7fe259317952 in KApplication::notify (this=0x7fff63739960, receiver=0x24e32c0, event=0x7fff637391e0) at ./kdecore/kapplication.cpp:552 #12 0x7fe25871cd0a in QETWidget::translateMouseEvent () from /usr/lib/qt3/lib64/libqt-mt.so.3 #13 0x7fe25871ba7e in QApplication::x11ProcessEvent () from /usr/lib/qt3/lib64/libqt-mt.so.3 #14 0x7fe25872e80a in QEventLoop::processEvents () from /usr/lib/qt3/lib64/libqt-mt.so.3 #15 0x7fe258795109 in QEventLoop::enterLoop () from /usr/lib/qt3/lib64/libqt-mt.so.3 #16 0x7fe258794f92 in QEventLoop::exec () from /usr/lib/qt3/lib64/libqt-mt.so.3 #17 0x00418ab5 in main (argc=, argv=0x7fff63739d38) at /usr/src/debug/kdepim-3.5.10/kontact/src/main.cpp:163 -- 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 189696] New: Kmail doesn't synchronize marks of read messages with Imap and labels (gmail)
https://bugs.kde.org/show_bug.cgi?id=189696 Summary: Kmail doesn't synchronize marks of read messages with Imap and labels (gmail) Product: kmail Version: 1.11.2 Platform: Slackware Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: ferri...@gmail.com Version: 1.11.2 (using KDE 4.2.2) OS:Linux Installed from:Slackware Packages I use gmail with Imap, and I've created a set of labels to manage various kind of e-mails that I'm receiving. In example, I've set up a "kde" label to organize e-mails coming from a kde mailing list. Gmail can shows these labels as separate folders. Kmail, rightly, shows a folder for each label, i.e. one called "kde" in the folderlist. When a new e-mail arrives, the unread emails count is showed both in the general Inbox folder and in the kde folder. Let us suppose I've received a new e-mail: now I read it opening the general inbox, and then, if I open the kde folder, I can see it marked as read. But the inverse path doesn't work: if I read this email in the kde folder for the first time, when I open the inbox, I see it as unread. This is a problem of kmail, because I've checked through the webmail that the message is correctly marked as read. -- 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
