[Bug 172717] New: kmail crash when moving (drag-drop) folders
http://bugs.kde.org/show_bug.cgi?id=172717
Summary: kmail crash when moving (drag-drop) folders
Product: kmail
Version: unspecified
Platform: RedHat RPMs
OS/Version: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: [EMAIL PROTECTED]
Version:(using KDE 4.1.2)
OS:Linux
Installed from:RedHat RPMs
Kmail crash when moving a nested folder by drag and drop into another folder. I
have maildir folders on local disk.
Backtrace:
Application: Kontact (kontact), signal SIGSEGV
[Thread debugging using libthread_db enabled]
[New Thread 0xb8099770 (LWP 16783)]
[New Thread 0xb48a1b90 (LWP 19845)]
[KCrash handler]
#6 0x65726874 in ?? ()
#7 0x00b960b8 in Q3ListView::contentsMousePressEventEx (this=0x9592930,
e=0xbfdce27c) at itemviews/q3listview.cpp:4155
#8 0x00b96714 in Q3ListView::contentsMousePressEvent (this=0x9592930,
e=0xbfdce27c) at itemviews/q3listview.cpp:4139
#9 0x0301654d in K3ListView::contentsMousePressEvent (
this=value optimized out, e=value optimized out)
at /usr/src/debug/kdelibs-4.1.2/kde3support/kdeui/k3listview.cpp:790
#10 0xb4f141c4 in KMFolderTree::contentsMousePressEvent (this=)
at /usr/src/debug/kdepim-4.1.2/kmail/kmfoldertree.cpp:1190
#11 0x00bf3ce1 in Q3ScrollView::viewportMousePressEvent (this=0x9592930,
e=0xbfdce828) at widgets/q3scrollview.cpp:1738
#12 0x00bf58c0 in Q3ScrollView::eventFilter (this=0x9592930, obj=0x9592f48,
e=0xbfdce828) at widgets/q3scrollview.cpp:1466
#13 0x00b910f6 in Q3ListView::eventFilter (this=0x9592930, o=0x9592f48,
e=0xbfdce828) at itemviews/q3listview.cpp:3771
#14 0xb4f137ea in KMFolderTree::eventFilter (this=value optimized out,
o=value optimized out, e=value optimized out)
at /usr/src/debug/kdepim-4.1.2/kmail/kmfoldertree.cpp:1814
#15 0x00f04e2a in QCoreApplicationPrivate::sendThroughObjectEventFilters (
this=0x8e386c0, receiver=0x9592f48, event=0xbfdce828)
at kernel/qcoreapplication.cpp:694
#16 0x010f5f6a in QApplicationPrivate::notify_helper (this=0x8e386c0,
receiver=0x9592f48, e=0xbfdce828) at kernel/qapplication.cpp:3799
#17 0x010fe7e1 in QApplication::notify (this=0xbfdcf0e8, receiver=0x9592f48,
e=0xbfdce828) at kernel/qapplication.cpp:3528
#18 0x02cc847d in KApplication::notify (this=value optimized out,
receiver=value optimized out, event=value optimized out)
at /usr/src/debug/kdelibs-4.1.2/kdeui/kernel/kapplication.cpp:311
#19 0x00f05c41 in QCoreApplication::notifyInternal (this=0xbfdcf0e8,
receiver=0x9592f48, event=0xbfdce828) at kernel/qcoreapplication.cpp:587
#20 0x010fda6e in QApplicationPrivate::sendMouseEvent (receiver=0x9592f48,
event=0xbfdce828, alienWidget=0x9592f48, nativeWidget=0x93ff960,
buttonDown=0x18c2b90, [EMAIL PROTECTED])
at ../../src/corelib/kernel/qcoreapplication.h:212
#21 0x01167f26 in QETWidget::translateMouseEvent (this=0x93ff960,
event=0xbfdcedfc) at kernel/qapplication_x11.cpp:4044
#22 0x011672ad in QApplication::x11ProcessEvent (this=0xbfdcf0e8,
event=0xbfdcedfc) at kernel/qapplication_x11.cpp:3040
#23 0x0118fa3c in x11EventSourceDispatch (s=0x8e39c38, callback=0,
user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:142
#24 0x05117008 in IA__g_main_context_dispatch (context=value optimized out)
at gmain.c:2012
#25 0x0511a6b3 in g_main_context_iterate (context=value optimized out,
block=value optimized out, dispatch=value optimized out, self=)
at gmain.c:2645
#26 0x0511a871 in IA__g_main_context_iteration (
context=value optimized out, may_block=value optimized out)
at gmain.c:2708
#27 0x00f30388 in QEventDispatcherGlib::processEvents (this=0x8e38778, flags=
{i = -1076039752}) at kernel/qeventdispatcher_glib.cpp:319
#28 0x0118f105 in QGuiEventDispatcherGlib::processEvents (this=0x8e38778,
flags={i = -1076039704}) at kernel/qguieventdispatcher_glib.cpp:198
#29 0x00f0432a in QEventLoop::processEvents (this=0xbfdcf060, flags=
{i = -1076039640}) at kernel/qeventloop.cpp:143
#30 0x00f044ea in QEventLoop::exec (this=0xbfdcf060, flags={i = -1076039576})
at kernel/qeventloop.cpp:194
#31 0x00f06b95 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845
#32 0x010f5e07 in QApplication::exec () at kernel/qapplication.cpp:3331
#33 0x0804be7f in main (argc=1, argv=0xbfdcf3e4)
at /usr/src/debug/kdepim-4.1.2/kontact/src/main.cpp:218
--
Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 172717] kmail crash when moving (drag-drop) folders
http://bugs.kde.org/show_bug.cgi?id=172717
--- Comment #1 from mstarkey wcsgabon org 2008-10-13 14:56:15 ---
Got it again, slightly different backtrace. NB I am using rpms from kde-redhat.
Best.
Application: Kontact (kontact), signal SIGSEGV
[Thread debugging using libthread_db enabled]
[New Thread 0xb8021770 (LWP 32199)]
[New Thread 0xb2128b90 (LWP 14673)]
[KCrash handler]
#6 0x0693ce99 in KMFolder::folderType (this=value optimized out)
at /usr/src/debug/kdepim-4.1.2/kmail/kmfolder.cpp:245
#7 0x068c7424 in KMFolderTree::doFolderSelected (this=value optimized out,
qlvi=value optimized out, keepSelection=value optimized out)
at /usr/src/debug/kdepim-4.1.2/kmail/kmfoldertree.cpp:1000
#8 0x068c8d64 in KMFolderTree::contentsMouseReleaseEvent (
this=value optimized out, me=value optimized out)
at /usr/src/debug/kdepim-4.1.2/kmail/kmfoldertree.cpp:1198
#9 0x00bf3c11 in Q3ScrollView::viewportMouseReleaseEvent (this=0x9642fc0,
e=0xbfd56158) at widgets/q3scrollview.cpp:1755
#10 0x00bf5890 in Q3ScrollView::eventFilter (this=0x9642fc0, obj=0x9644360,
e=0xbfd56158) at widgets/q3scrollview.cpp:1473
#11 0x00b910f6 in Q3ListView::eventFilter (this=0x9642fc0, o=0x9644360,
e=0xbfd56158) at itemviews/q3listview.cpp:3771
#12 0x068c27ea in KMFolderTree::eventFilter (this=value optimized out,
o=value optimized out, e=value optimized out)
at /usr/src/debug/kdepim-4.1.2/kmail/kmfoldertree.cpp:1814
#13 0x00f04e2a in QCoreApplicationPrivate::sendThroughObjectEventFilters (
this=0x8ebe6c0, receiver=0x9644360, event=0xbfd56158)
at kernel/qcoreapplication.cpp:694
#14 0x010f5f6a in QApplicationPrivate::notify_helper (this=0x8ebe6c0,
receiver=0x9644360, e=0xbfd56158) at kernel/qapplication.cpp:3799
#15 0x010fe7e1 in QApplication::notify (this=0xbfd56a18, receiver=0x9644360,
e=0xbfd56158) at kernel/qapplication.cpp:3528
#16 0x02cc847d in KApplication::notify (this=value optimized out,
receiver=value optimized out, event=value optimized out)
at /usr/src/debug/kdelibs-4.1.2/kdeui/kernel/kapplication.cpp:311
#17 0x00f05c41 in QCoreApplication::notifyInternal (this=0xbfd56a18,
receiver=0x9644360, event=0xbfd56158) at kernel/qcoreapplication.cpp:587
#18 0x010fda6e in QApplicationPrivate::sendMouseEvent (receiver=0x9644360,
event=0xbfd56158, alienWidget=0x9644360, nativeWidget=0x8f9a628,
buttonDown=0x18c2b90, [EMAIL PROTECTED])
at ../../src/corelib/kernel/qcoreapplication.h:212
#19 0x01167f26 in QETWidget::translateMouseEvent (this=0x8f9a628,
event=0xbfd5672c) at kernel/qapplication_x11.cpp:4044
#20 0x011672ad in QApplication::x11ProcessEvent (this=0xbfd56a18,
event=0xbfd5672c) at kernel/qapplication_x11.cpp:3040
#21 0x0118fa3c in x11EventSourceDispatch (s=0x8ebfc38, callback=0,
user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:142
#22 0x05117008 in IA__g_main_context_dispatch (context=value optimized out)
at gmain.c:2012
#23 0x0511a6b3 in g_main_context_iterate (context=value optimized out,
block=value optimized out, dispatch=value optimized out, self=)
at gmain.c:2645
#24 0x0511a871 in IA__g_main_context_iteration (
context=value optimized out, may_block=value optimized out)
at gmain.c:2708
#25 0x00f30388 in QEventDispatcherGlib::processEvents (this=0x8ebe778, flags=
{i = -1076533016}) at kernel/qeventdispatcher_glib.cpp:319
#26 0x0118f105 in QGuiEventDispatcherGlib::processEvents (this=0x8ebe778,
flags={i = -1076532968}) at kernel/qguieventdispatcher_glib.cpp:198
#27 0x00f0432a in QEventLoop::processEvents (this=0xbfd56990, flags=
{i = -1076532904}) at kernel/qeventloop.cpp:143
#28 0x00f044ea in QEventLoop::exec (this=0xbfd56990, flags={i = -1076532840})
at kernel/qeventloop.cpp:194
#29 0x00f06b95 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845
#30 0x010f5e07 in QApplication::exec () at kernel/qapplication.cpp:3331
#31 0x0804be7f in main (argc=1, argv=0xbfd56d14)
at /usr/src/debug/kdepim-4.1.2/kontact/src/main.cpp:218
--
Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 172717] kmail crash when moving (drag-drop) folders
http://bugs.kde.org/show_bug.cgi?id=172717
--- Comment #2 from mstarkey wcsgabon org 2008-10-13 19:22:23 ---
Another one doing the same thing - crash while moving nested folders but
slightly different trace. (can you tell that I am reorganising my emails?;-)).
Application: Kontact (kontact), signal SIGSEGV
[Thread debugging using libthread_db enabled]
[New Thread 0xb7fae770 (LWP 23056)]
[New Thread 0xb4b51b90 (LWP 30015)]
[KCrash handler]
#6 0x00f04249 in QEventLoop::exit (this=0x0, returnCode=0)
at ../../src/corelib/kernel/qeventloop.h:54
#7 0x01179514 in QDragManager::eventFilter (this=0x8f48a28, o=0x894f838,
e=0xbfee2bc8) at kernel/qdnd_x11.cpp:1299
#8 0x00f04ed4 in QCoreApplicationPrivate::sendThroughApplicationEventFilters
(this=0x807f6c0, receiver=0x894f838, event=0xbfee2bc8)
at kernel/qcoreapplication.cpp:676
#9 0x010f5f03 in QApplicationPrivate::notify_helper (this=0x807f6c0,
receiver=0x894f838, e=0xbfee2bc8) at kernel/qapplication.cpp:3778
#10 0x010fe7e1 in QApplication::notify (this=0xbfee6398, receiver=0x894f838,
e=0xbfee2bc8) at kernel/qapplication.cpp:3528
#11 0x02cc847d in KApplication::notify (this=value optimized out,
receiver=value optimized out, event=value optimized out)
at /usr/src/debug/kdelibs-4.1.2/kdeui/kernel/kapplication.cpp:311
#12 0x00f05c41 in QCoreApplication::notifyInternal (this=0xbfee6398,
receiver=0x894f838, event=0xbfee2bc8) at kernel/qcoreapplication.cpp:587
#13 0x010fda6e in QApplicationPrivate::sendMouseEvent (receiver=0x894f838,
event=0xbfee2bc8, alienWidget=0x87be758, nativeWidget=0x8113a88,
buttonDown=0x18c2b90, [EMAIL PROTECTED])
at ../../src/corelib/kernel/qcoreapplication.h:212
#14 0x01167f26 in QETWidget::translateMouseEvent (this=0x8113a88,
event=0xbfee319c) at kernel/qapplication_x11.cpp:4044
#15 0x011672ad in QApplication::x11ProcessEvent (this=0xbfee6398,
event=0xbfee319c) at kernel/qapplication_x11.cpp:3040
#16 0x0118fa3c in x11EventSourceDispatch (s=0x8080c38, callback=0,
user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:142
#17 0x05117008 in IA__g_main_context_dispatch (context=value optimized out)
at gmain.c:2012
#18 0x0511a6b3 in g_main_context_iterate (context=value optimized out,
block=value optimized out, dispatch=value optimized out, self=)
at gmain.c:2645
#19 0x0511a871 in IA__g_main_context_iteration (
context=value optimized out, may_block=value optimized out)
at gmain.c:2708
#20 0x00f30388 in QEventDispatcherGlib::processEvents (this=0x807f778, flags=
{i = -1074908328}) at kernel/qeventdispatcher_glib.cpp:319
#21 0x0118f105 in QGuiEventDispatcherGlib::processEvents (this=0x807f778,
flags={i = -1074908280}) at kernel/qguieventdispatcher_glib.cpp:198
#22 0x00f0432a in QEventLoop::processEvents (this=0x8a68460, flags=
{i = -1074908216}) at kernel/qeventloop.cpp:143
#23 0x00f044ea in QEventLoop::exec (this=0x8a68460, flags={i = -1074908104})
at kernel/qeventloop.cpp:194
#24 0x011774f0 in QDragManager::drag (this=0x8f48a28, o=0x8afbe48)
at kernel/qdnd_x11.cpp:1944
#25 0x0110935a in QDrag::exec (this=0x8afbe48, supportedActions=
{i = -1074907888}, defaultDropAction=Qt::IgnoreAction)
at kernel/qdrag.cpp:275
#26 0x00b56a9b in Q3DragObject::drag (this=0x8d2b128,
mode=Q3DragObject::DragDefault) at other/q3dragobject.cpp:397
#27 0x00b54e09 in Q3DragObject::drag (this=0x8d2b128)
at other/q3dragobject.cpp:267
#28 0x03015a74 in K3ListView::startDrag (this=value optimized out)
at /usr/src/debug/kdelibs-4.1.2/kde3support/kdeui/k3listview.cpp:1145
#29 0x03016383 in K3ListView::contentsMouseMoveEvent (
this=value optimized out, e=value optimized out)
at /usr/src/debug/kdelibs-4.1.2/kde3support/kdeui/k3listview.cpp:827
#30 0x00bf3a71 in Q3ScrollView::viewportMouseMoveEvent (this=0x87be068,
e=0xbfee3b78) at widgets/q3scrollview.cpp:1789
#31 0x00bf5832 in Q3ScrollView::eventFilter (this=0x87be068, obj=0x87be758,
e=0xbfee3b78) at widgets/q3scrollview.cpp:1487
#32 0x00b910f6 in Q3ListView::eventFilter (this=0x87be068, o=0x87be758,
e=0xbfee3b78) at itemviews/q3listview.cpp:3771
#33 0x0616f7ea in KMFolderTree::eventFilter (this=value optimized out,
o=value optimized out, e=value optimized out)
at /usr/src/debug/kdepim-4.1.2/kmail/kmfoldertree.cpp:1814
#34 0x00f04e2a in QCoreApplicationPrivate::sendThroughObjectEventFilters (
this=0x807f6c0, receiver=0x87be758, event=0xbfee3b78)
at kernel/qcoreapplication.cpp:694
#35 0x010f5f6a in QApplicationPrivate::notify_helper (this=0x807f6c0,
receiver=0x87be758, e=0xbfee3b78) at kernel/qapplication.cpp:3799
#36 0x010fe7e1 in QApplication::notify (this=0xbfee6398, receiver=0x87be758,
e=0xbfee3b78) at kernel/qapplication.cpp:3528
#37 0x02cc847d in KApplication::notify (this=value optimized out,
receiver=value optimized out, event=value optimized out)
at /usr/src/debug/kdelibs-4.1.2/kdeui/kernel/kapplication.cpp:311
#38
[Bug 172524] Kmail crashes without trace when typing in composer
http://bugs.kde.org/show_bug.cgi?id=172524 --- Comment #1 from mstarkey wcsgabon org 2008-10-12 10:42:28 --- Anyone got any thoughts on this? Its a bit of a showstopper, kmail crashing randomly and frequently like that. If people can give me guidance I am happy to spend sometime this weekend trying to get more info to help it get fixed, but I tried a backtrace, and not sure what else I can do? -- Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 167416] New: kmail crashes while checking mail.
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=167416 Summary: kmail crashes while checking mail. Product: kmail Version: SVN trunk (KDE 4) Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: mstarkey wcsgabon org kmail crashed whilst downloading emails from a Pop account. Seemingly random, I had no other kmail windows open. the download got to about 30% then crashed. On restart the emails came though without a problem. Sorry not very helpful, but here is the backtrace that might say something: Application: KMail (kmail), signal SIGSEGV Using host libthread_db library /lib/libthread_db.so.1. [Thread debugging using libthread_db enabled] [New Thread -1208281392 (LWP 2994)] [KCrash handler] #6 0x0020c1f1 in QUrl (this=0xbfdd06fc, other= 0x51) at io/qurl.cpp:3769 #7 0x0054f502 in KUrl (this=0xbfdd06fc, _u= 0x51) at /home/kde-devel/kde/src/kdelibs/kdecore/io/kurl.cpp:431 #8 0x03e7 in KIO::SchedulerPrivate::slotScheduleCoSlave (this=0x9b6dcb0) at /home/kde-devel/kde/src/kdelibs/kio/kio/scheduler.cpp:883 #9 0x03cd0024 in KIO::Scheduler::qt_metacall (this=0x9b79020, _c=QMetaObject::InvokeMetaMethod, _id=10, _a=0xbfdd07e4) at /home/kde-devel/kde/build/kdelibs/kio/scheduler.moc:105 #10 0x0026ae61 in QMetaObject::activate (sender=0x9b6dccc, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3007 #11 0x0026b2e3 in QMetaObject::activate (sender=0x9b6dccc, m=0x305b64, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3080 #12 0x002ab3bd in QTimer::timeout (this=0x9b6dccc) at .moc/debug-shared/moc_qtimer.cpp:126 #13 0x00275f56 in QTimer::timerEvent (this=0x9b6dccc, e=0xbfdd0df4) at kernel/qtimer.cpp:263 #14 0x0026a0e2 in QObject::event (this=0x9b6dccc, e=0xbfdd0df4) at kernel/qobject.cpp:1105 #15 0x0573ad07 in QApplicationPrivate::notify_helper (this=0x9a34948, receiver=0x9b6dccc, e=0xbfdd0df4) at kernel/qapplication.cpp:3772 #16 0x0573b020 in QApplication::notify (this=0xbfdd110c, receiver=0x9b6dccc, e=0xbfdd0df4) at kernel/qapplication.cpp:3366 #17 0x012e2275 in KApplication::notify (this=0xbfdd110c, receiver=0x9b6dccc, event=0xbfdd0df4) at /home/kde-devel/kde/src/kdelibs/kdeui/kernel/kapplication.cpp:311 #18 0x00256bb2 in QCoreApplication::notifyInternal (this=0xbfdd110c, receiver=0x9b6dccc, event=0xbfdd0df4) at kernel/qcoreapplication.cpp:583 #19 0x0025a63b in QCoreApplication::sendEvent (receiver=0x9b6dccc, event=0xbfdd0df4) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #20 0x00289045 in QTimerInfoList::activateTimers (this=0x9a37674) at kernel/qeventdispatcher_unix.cpp:563 #21 0x00286164 in timerSourceDispatch (source=0x9a37640) at kernel/qeventdispatcher_glib.cpp:166 #22 0x016cf1ac in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #23 0x016d25ef in ?? () from /lib/libglib-2.0.so.0 #24 0x016d2b55 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #25 0x00285be4 in QEventDispatcherGlib::processEvents (this=0x9a31550, flags= 0xbfdd0f68) at kernel/qeventdispatcher_glib.cpp:325 #26 0x057e2db4 in QGuiEventDispatcherGlib::processEvents (this=0x9a31550, flags= 0xbfdd0f98) at kernel/qguieventdispatcher_glib.cpp:204 #27 0x0025370e in QEventLoop::processEvents (this=0xbfdd1010, flags= 0xbfdd0fd4) at kernel/qeventloop.cpp:149 #28 0x0025394d in QEventLoop::exec (this=0xbfdd1010, flags= 0xbfdd1018) at kernel/qeventloop.cpp:196 #29 0x0025739b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845 #30 0x0573aa04 in QApplication::exec () at kernel/qapplication.cpp:3304 #31 0x0804b05c in main (argc=3, argv=0xbfdd11e4) at /home/kde-devel/kde/src/kdepim/kmail/main.cpp:146 #0 0x00110402 in __kernel_vsyscall () ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 162175] Kmail does not recognise/use the port number set in the smtp account settings dialog
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=162175 mstarkey wcsgabon org changed: What|Removed |Added Severity|normal |major Summary|Unable to send with uuplus |Kmail does not recognise/use |SMTP on localhost port 1025 |the port number set in the ||smtp account settings dialog --- Additional Comments From mstarkey wcsgabon org 2008-07-14 14:32 --- I'm no C++ expert, but from a bit of grepping in src/kdepim/kmail , it looks like the POP seetings dialog has code like this: mServerTest-setPort( encryptionType, mPop.ui.portEdit-value() ) where it is setting the port based on the value in the UI. On the other hand, the smtp equivalent (eg in AccountWizard::smtpCapabilities) just has : mTransport-setPort( useSSL ? 465 : 25 ); ie the port number is hardcoded to 465 or 25 depending on whether SSL is requested or not and it doesn't refer to the port number selected manually in the text box in the UI at all. Am I on the right track here? Looks like there is similar stuff for Imap (eg: account-setPort( useSSL ? 993 : 143 );) so anyone trying to use a non-standard port is out of luck. cheers M. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 162175] Kmail does not recognise/use the port number set in the smtp account settings dialog
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=162175 --- Additional Comments From mstarkey wcsgabon org 2008-07-14 14:32 --- To try and work out what is going on here, I fired up wireshark. With the host set to 'localhost' and the portnumber set to 1025 in the kmail accounts - smtp dialog, I click on 'check what the server supports'. The attached wireshark packet file shows the traffic generated. I'm not an expert but it looks like kmail is not using the port number that is set in the options dialog, but simply defaulting to the standard port 25. If I run the uuplus server on standard port 25 (requires running as root, which I don't want to do as a matter of course) then kmail connects without a problem. So it is clearly kmail not using the correct port number that creates the problem. I did this test with revision 830974. Thanks M. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 162175] Kmail does not recognise/use the port number set in the smtp account settings dialog
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=162175 --- Additional Comments From mstarkey wcsgabon org 2008-07-14 14:33 --- Created an attachment (id=26110) -- (http://bugs.kde.org/attachment.cgi?id=26110action=view) Wireshark capture file (packet data) showing that kmail does not use the port number set in the configuration dialog. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 166521] New: Allow default directory for saving attachments to be customised based on both sender and file-type
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=166521 Summary: Allow default directory for saving attachments to be customised based on both sender and file-type Product: kmail Version: SVN trunk (KDE 4) Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: mstarkey wcsgabon org It would be great to be able to set a parameter so that for example .pdf files from MyOnlineShop.com by default get saved to my Receipts directory, whilst all .jpg files from Spouse Home com get saved to Pictures/MyPersonalPictures for example. This would be a great productivity feature. Are there any plans to include something like this? How difficult would it be? cheers M. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 166530] New: Check mail on startup should be a per-Account setting
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=166530 Summary: Check mail on startup should be a per-Account setting Product: kmail Version: SVN trunk (KDE 4) Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: mstarkey wcsgabon org I have a number of remote mail accounts, some of them mailing lists with large numbers of messages. I am often using slow connections and I don't want kmail trying to download 100s of messages from these accounts. I work around by not checking anything on startup, but it would be nice if I could set it so only my primary accounts are checked automatically. Thanks M. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 166531] New: Add a Save and open option to the attachement right-click context menu
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=166531 Summary: Add a Save and open option to the attachement right- click context menu Product: kmail Version: SVN trunk (KDE 4) Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: mstarkey wcsgabon org At the moment, if you do Save as to save an attachment you then have to go and hunt for the file with dolphin to be able to open it. Alternatively, if you open the attachment with 'Open' it, it gets saved in /tmp with a funny name (eg attachment.xls_[JN1192]) so that when you Save as, you have to both rename the file to get rid of the extension AND find the right place to save it. So a 'Save and Open' option would be awesome! cheers M. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 166533] New: kmail crashes when opening a url received in an email
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=166533 Summary: kmail crashes when opening a url received in an email Product: kmail Version: SVN trunk (KDE 4) Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: mstarkey wcsgabon org In any email with a url, right-clicking on the URL and selection Open URL crashes kmail. Using revision 830974. Occurs with either html or plaintext mails. Backtrace below. cheers M. Application: KMail (kmail), signal SIGABRT Using host libthread_db library /lib/libthread_db.so.1. [Thread debugging using libthread_db enabled] [New Thread -1208490288 (LWP 3586)] [New Thread -1268221040 (LWP 16723)] [KCrash handler] #6 0x00110402 in __kernel_vsyscall () #7 0x02949690 in raise () from /lib/libc.so.6 #8 0x0294af91 in abort () from /lib/libc.so.6 #9 0x0015bbc9 in qt_message_output (msgType=QtFatalMsg, buf=0xbfb2a810 ASSERT: \!d-m_bFinished\ in file /home/kde-devel/kde/src/kdelibs/kio/kio/krun.cpp, line 1184) at global/qglobal.cpp:2058 #10 0x0015bc2d in qFatal (msg=0x2ac518 ASSERT: \%s\ in file %s, line %d) at global/qglobal.cpp:2260 #11 0x0015c093 in qt_assert (assertion=0x540f1f7 !d-m_bFinished, file=0x540e6d0 /home/kde-devel/kde/src/kdelibs/kio/kio/krun.cpp, line=1184) at global/qglobal.cpp:1828 #12 0x0531e330 in KRun::foundMimeType (this=0xa2d7910, type= 0xbfb2cc3c) at /home/kde-devel/kde/src/kdelibs/kio/kio/krun.cpp:1184 #13 0x05319154 in KRun::mimeTypeDetermined (this=0xa2d7910, mimeType= 0xbfb2cc3c) at /home/kde-devel/kde/src/kdelibs/kio/kio/krun.cpp:1115 #14 0x05319203 in KRun::slotScanMimeType (this=0xa2d7910, mimetype= 0xbfb2cc3c) at /home/kde-devel/kde/src/kdelibs/kio/kio/krun.cpp:1085 #15 0x0531e972 in KRun::qt_metacall (this=0xa2d7910, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbfb2ca38) at /home/kde-devel/kde/build/kdelibs/kio/krun.moc:81 #16 0x0026ae61 in QMetaObject::activate (sender=0xa7a95b8, from_signal_index=44, to_signal_index=44, argv=0xbfb2ca38) at kernel/qobject.cpp:3007 #17 0x0026b2e3 in QMetaObject::activate (sender=0xa7a95b8, m=0x542e450, local_signal_index=4, argv=0xbfb2ca38) at kernel/qobject.cpp:3080 #18 0x052aa189 in KIO::TransferJob::mimetype (this=0xa7a95b8, _t1=0xa7a95b8, _t2= 0xbfb2cc3c) at /home/kde-devel/kde/build/kdelibs/kio/jobclasses.moc:384 #19 0x052abdf2 in KIO::TransferJob::slotMimetype (this=0xa7a95b8, type= 0xbfb2cc3c) at /home/kde-devel/kde/src/kdelibs/kio/kio/job.cpp:1112 #20 0x052b5c3c in KIO::TransferJob::qt_metacall (this=0xa7a95b8, _c=QMetaObject::InvokeMetaMethod, _id=10, _a=0xbfb2cb8c) at /home/kde-devel/kde/build/kdelibs/kio/jobclasses.moc:339 #21 0x0026ae61 in QMetaObject::activate (sender=0xa3c39c8, from_signal_index=23, to_signal_index=23, argv=0xbfb2cb8c) at kernel/qobject.cpp:3007 #22 0x0026b2e3 in QMetaObject::activate (sender=0xa3c39c8, m=0x5430e84, local_signal_index=19, argv=0xbfb2cb8c) at kernel/qobject.cpp:3080 #23 0x0535c6ec in KIO::SlaveInterface::mimeType (this=0xa3c39c8, _t1= 0xbfb2cc3c) at /home/kde-devel/kde/build/kdelibs/kio/slaveinterface.moc:265 #24 0x0535f052 in KIO::SlaveInterface::dispatch (this=0xa3c39c8, _cmd=21, rawdata= 0xbfb2ccf4) at /home/kde-devel/kde/src/kdelibs/kio/kio/slaveinterface.cpp:285 #25 0x0535f691 in KIO::SlaveInterface::dispatch (this=0xa3c39c8) at /home/kde-devel/kde/src/kdelibs/kio/kio/slaveinterface.cpp:91 #26 0x05350d02 in KIO::Slave::gotInput (this=0xa3c39c8) at /home/kde-devel/kde/src/kdelibs/kio/kio/slave.cpp:319 #27 0x05352176 in KIO::Slave::qt_metacall (this=0xa3c39c8, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfb2cde4) at /home/kde-devel/kde/build/kdelibs/kio/slave.moc:75 #28 0x0026ae61 in QMetaObject::activate (sender=0xa5bd0c8, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3007 #29 0x0026b2e3 in QMetaObject::activate (sender=0xa5bd0c8, m=0x542dae0, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3080 #30 0x0527c74f in KIO::Connection::readyRead (this=0xa5bd0c8) at /home/kde-devel/kde/build/kdelibs/kio/connection.moc:84 #31 0x0527d743 in KIO::ConnectionPrivate::dequeue (this=0x9e4ad50) at /home/kde-devel/kde/src/kdelibs/kio/kio/connection.cpp:82 #32 0x0527e671 in KIO::Connection::qt_metacall (this=0xa5bd0c8, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0xa2b6040) at /home/kde-devel/kde/build/kdelibs/kio/connection.moc:72 #33 0x002654f6 in QMetaCallEvent::placeMetaCall (this=0xa3a71e8, object=0xa5bd0c8) at kernel/qobject.cpp:535 #34 0x0026a194 in QObject::event (this=0xa5bd0c8, e=0xa3a71e8) at kernel/qobject.cpp:1137 #35
[Bug 166534] New: kmail crashes when opening a url received in an email
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=166534 Summary: kmail crashes when opening a url received in an email Product: kmail Version: SVN trunk (KDE 4) Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: mstarkey wcsgabon org In any email with a url, right-clicking on the URL and selection Open URL crashes kmail. Using revision 830974. Occurs with either html or plaintext mails. Backtrace below. cheers M. Application: KMail (kmail), signal SIGABRT Using host libthread_db library /lib/libthread_db.so.1. [Thread debugging using libthread_db enabled] [New Thread -1208490288 (LWP 3586)] [New Thread -1268221040 (LWP 16723)] [KCrash handler] #6 0x00110402 in __kernel_vsyscall () #7 0x02949690 in raise () from /lib/libc.so.6 #8 0x0294af91 in abort () from /lib/libc.so.6 #9 0x0015bbc9 in qt_message_output (msgType=QtFatalMsg, buf=0xbfb2a810 ASSERT: \!d-m_bFinished\ in file /home/kde-devel/kde/src/kdelibs/kio/kio/krun.cpp, line 1184) at global/qglobal.cpp:2058 #10 0x0015bc2d in qFatal (msg=0x2ac518 ASSERT: \%s\ in file %s, line %d) at global/qglobal.cpp:2260 #11 0x0015c093 in qt_assert (assertion=0x540f1f7 !d-m_bFinished, file=0x540e6d0 /home/kde-devel/kde/src/kdelibs/kio/kio/krun.cpp, line=1184) at global/qglobal.cpp:1828 #12 0x0531e330 in KRun::foundMimeType (this=0xa2d7910, type= 0xbfb2cc3c) at /home/kde-devel/kde/src/kdelibs/kio/kio/krun.cpp:1184 #13 0x05319154 in KRun::mimeTypeDetermined (this=0xa2d7910, mimeType= 0xbfb2cc3c) at /home/kde-devel/kde/src/kdelibs/kio/kio/krun.cpp:1115 #14 0x05319203 in KRun::slotScanMimeType (this=0xa2d7910, mimetype= 0xbfb2cc3c) at /home/kde-devel/kde/src/kdelibs/kio/kio/krun.cpp:1085 #15 0x0531e972 in KRun::qt_metacall (this=0xa2d7910, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbfb2ca38) at /home/kde-devel/kde/build/kdelibs/kio/krun.moc:81 #16 0x0026ae61 in QMetaObject::activate (sender=0xa7a95b8, from_signal_index=44, to_signal_index=44, argv=0xbfb2ca38) at kernel/qobject.cpp:3007 #17 0x0026b2e3 in QMetaObject::activate (sender=0xa7a95b8, m=0x542e450, local_signal_index=4, argv=0xbfb2ca38) at kernel/qobject.cpp:3080 #18 0x052aa189 in KIO::TransferJob::mimetype (this=0xa7a95b8, _t1=0xa7a95b8, _t2= 0xbfb2cc3c) at /home/kde-devel/kde/build/kdelibs/kio/jobclasses.moc:384 #19 0x052abdf2 in KIO::TransferJob::slotMimetype (this=0xa7a95b8, type= 0xbfb2cc3c) at /home/kde-devel/kde/src/kdelibs/kio/kio/job.cpp:1112 #20 0x052b5c3c in KIO::TransferJob::qt_metacall (this=0xa7a95b8, _c=QMetaObject::InvokeMetaMethod, _id=10, _a=0xbfb2cb8c) at /home/kde-devel/kde/build/kdelibs/kio/jobclasses.moc:339 #21 0x0026ae61 in QMetaObject::activate (sender=0xa3c39c8, from_signal_index=23, to_signal_index=23, argv=0xbfb2cb8c) at kernel/qobject.cpp:3007 #22 0x0026b2e3 in QMetaObject::activate (sender=0xa3c39c8, m=0x5430e84, local_signal_index=19, argv=0xbfb2cb8c) at kernel/qobject.cpp:3080 #23 0x0535c6ec in KIO::SlaveInterface::mimeType (this=0xa3c39c8, _t1= 0xbfb2cc3c) at /home/kde-devel/kde/build/kdelibs/kio/slaveinterface.moc:265 #24 0x0535f052 in KIO::SlaveInterface::dispatch (this=0xa3c39c8, _cmd=21, rawdata= 0xbfb2ccf4) at /home/kde-devel/kde/src/kdelibs/kio/kio/slaveinterface.cpp:285 #25 0x0535f691 in KIO::SlaveInterface::dispatch (this=0xa3c39c8) at /home/kde-devel/kde/src/kdelibs/kio/kio/slaveinterface.cpp:91 #26 0x05350d02 in KIO::Slave::gotInput (this=0xa3c39c8) at /home/kde-devel/kde/src/kdelibs/kio/kio/slave.cpp:319 #27 0x05352176 in KIO::Slave::qt_metacall (this=0xa3c39c8, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfb2cde4) at /home/kde-devel/kde/build/kdelibs/kio/slave.moc:75 #28 0x0026ae61 in QMetaObject::activate (sender=0xa5bd0c8, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3007 #29 0x0026b2e3 in QMetaObject::activate (sender=0xa5bd0c8, m=0x542dae0, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3080 #30 0x0527c74f in KIO::Connection::readyRead (this=0xa5bd0c8) at /home/kde-devel/kde/build/kdelibs/kio/connection.moc:84 #31 0x0527d743 in KIO::ConnectionPrivate::dequeue (this=0x9e4ad50) at /home/kde-devel/kde/src/kdelibs/kio/kio/connection.cpp:82 #32 0x0527e671 in KIO::Connection::qt_metacall (this=0xa5bd0c8, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0xa2b6040) at /home/kde-devel/kde/build/kdelibs/kio/connection.moc:72 #33 0x002654f6 in QMetaCallEvent::placeMetaCall (this=0xa3a71e8, object=0xa5bd0c8) at kernel/qobject.cpp:535 #34 0x0026a194 in QObject::event (this=0xa5bd0c8, e=0xa3a71e8) at kernel/qobject.cpp:1137 #35
[Bug 166535] New: kmail crashes when opening a url received in an email
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=166535 Summary: kmail crashes when opening a url received in an email Product: kmail Version: SVN trunk (KDE 4) Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: mstarkey wcsgabon org In any email with a url, right-clicking on the URL and selection Open URL crashes kmail. Using revision 830974. Occurs with either html or plaintext mails. Backtrace below. cheers M. Application: KMail (kmail), signal SIGABRT Using host libthread_db library /lib/libthread_db.so.1. [Thread debugging using libthread_db enabled] [New Thread -1208490288 (LWP 3586)] [New Thread -1268221040 (LWP 16723)] [KCrash handler] #6 0x00110402 in __kernel_vsyscall () #7 0x02949690 in raise () from /lib/libc.so.6 #8 0x0294af91 in abort () from /lib/libc.so.6 #9 0x0015bbc9 in qt_message_output (msgType=QtFatalMsg, buf=0xbfb2a810 ASSERT: \!d-m_bFinished\ in file /home/kde-devel/kde/src/kdelibs/kio/kio/krun.cpp, line 1184) at global/qglobal.cpp:2058 #10 0x0015bc2d in qFatal (msg=0x2ac518 ASSERT: \%s\ in file %s, line %d) at global/qglobal.cpp:2260 #11 0x0015c093 in qt_assert (assertion=0x540f1f7 !d-m_bFinished, file=0x540e6d0 /home/kde-devel/kde/src/kdelibs/kio/kio/krun.cpp, line=1184) at global/qglobal.cpp:1828 #12 0x0531e330 in KRun::foundMimeType (this=0xa2d7910, type= 0xbfb2cc3c) at /home/kde-devel/kde/src/kdelibs/kio/kio/krun.cpp:1184 #13 0x05319154 in KRun::mimeTypeDetermined (this=0xa2d7910, mimeType= 0xbfb2cc3c) at /home/kde-devel/kde/src/kdelibs/kio/kio/krun.cpp:1115 #14 0x05319203 in KRun::slotScanMimeType (this=0xa2d7910, mimetype= 0xbfb2cc3c) at /home/kde-devel/kde/src/kdelibs/kio/kio/krun.cpp:1085 #15 0x0531e972 in KRun::qt_metacall (this=0xa2d7910, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbfb2ca38) at /home/kde-devel/kde/build/kdelibs/kio/krun.moc:81 #16 0x0026ae61 in QMetaObject::activate (sender=0xa7a95b8, from_signal_index=44, to_signal_index=44, argv=0xbfb2ca38) at kernel/qobject.cpp:3007 #17 0x0026b2e3 in QMetaObject::activate (sender=0xa7a95b8, m=0x542e450, local_signal_index=4, argv=0xbfb2ca38) at kernel/qobject.cpp:3080 #18 0x052aa189 in KIO::TransferJob::mimetype (this=0xa7a95b8, _t1=0xa7a95b8, _t2= 0xbfb2cc3c) at /home/kde-devel/kde/build/kdelibs/kio/jobclasses.moc:384 #19 0x052abdf2 in KIO::TransferJob::slotMimetype (this=0xa7a95b8, type= 0xbfb2cc3c) at /home/kde-devel/kde/src/kdelibs/kio/kio/job.cpp:1112 #20 0x052b5c3c in KIO::TransferJob::qt_metacall (this=0xa7a95b8, _c=QMetaObject::InvokeMetaMethod, _id=10, _a=0xbfb2cb8c) at /home/kde-devel/kde/build/kdelibs/kio/jobclasses.moc:339 #21 0x0026ae61 in QMetaObject::activate (sender=0xa3c39c8, from_signal_index=23, to_signal_index=23, argv=0xbfb2cb8c) at kernel/qobject.cpp:3007 #22 0x0026b2e3 in QMetaObject::activate (sender=0xa3c39c8, m=0x5430e84, local_signal_index=19, argv=0xbfb2cb8c) at kernel/qobject.cpp:3080 #23 0x0535c6ec in KIO::SlaveInterface::mimeType (this=0xa3c39c8, _t1= 0xbfb2cc3c) at /home/kde-devel/kde/build/kdelibs/kio/slaveinterface.moc:265 #24 0x0535f052 in KIO::SlaveInterface::dispatch (this=0xa3c39c8, _cmd=21, rawdata= 0xbfb2ccf4) at /home/kde-devel/kde/src/kdelibs/kio/kio/slaveinterface.cpp:285 #25 0x0535f691 in KIO::SlaveInterface::dispatch (this=0xa3c39c8) at /home/kde-devel/kde/src/kdelibs/kio/kio/slaveinterface.cpp:91 #26 0x05350d02 in KIO::Slave::gotInput (this=0xa3c39c8) at /home/kde-devel/kde/src/kdelibs/kio/kio/slave.cpp:319 #27 0x05352176 in KIO::Slave::qt_metacall (this=0xa3c39c8, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfb2cde4) at /home/kde-devel/kde/build/kdelibs/kio/slave.moc:75 #28 0x0026ae61 in QMetaObject::activate (sender=0xa5bd0c8, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3007 #29 0x0026b2e3 in QMetaObject::activate (sender=0xa5bd0c8, m=0x542dae0, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3080 #30 0x0527c74f in KIO::Connection::readyRead (this=0xa5bd0c8) at /home/kde-devel/kde/build/kdelibs/kio/connection.moc:84 #31 0x0527d743 in KIO::ConnectionPrivate::dequeue (this=0x9e4ad50) at /home/kde-devel/kde/src/kdelibs/kio/kio/connection.cpp:82 #32 0x0527e671 in KIO::Connection::qt_metacall (this=0xa5bd0c8, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0xa2b6040) at /home/kde-devel/kde/build/kdelibs/kio/connection.moc:72 #33 0x002654f6 in QMetaCallEvent::placeMetaCall (this=0xa3a71e8, object=0xa5bd0c8) at kernel/qobject.cpp:535 #34 0x0026a194 in QObject::event (this=0xa5bd0c8, e=0xa3a71e8) at kernel/qobject.cpp:1137 #35
[Bug 166523] Kmail SIGABRTs when changing various settings in configuration dialog
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=166523 --- Additional Comments From mstarkey wcsgabon org 2008-07-14 16:11 --- Hi, no I didn't. I compile kde4 following the instructions on http://techbase.kde.org/User:Dhaumann/Compiling_KDE4 . (I'm running Fedora 8 FWIW). I then log into a kde4 desktop with a desktop session with parameters as follows: Type=XSession Exec=$HOME/kde/kde4/bin/startkde At what point (and why) would I run kbuildsyscoca4? thanks M. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 166523] New: Kmail SIGABRTs when changing various settings in configuration dialog
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=166523 Summary: Kmail SIGABRTs when changing various settings in configuration dialog Product: kmail Version: SVN trunk (KDE 4) Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: mstarkey wcsgabon org Kmail's configuration dialogue seems to be pretty buggy. In this case I am trying to set kmail to use kate as an external editor. I click on the 'Use external editor instead of composer check box' and on clicking either Ok or Apply kmail crashes. Two backtraces - the first I get when I click 'OK' and the second if I click 'Apply'. If I click Ok, the option is NOT set when I restart, but if I click Apply, it is set. I also get a crash on changing other settings. The third backtrace below is trying to set the Check mail on startup parameter and occurs whenI click Apply. Looks pretty similar to the crash when trying to set the external editor. The fourth backtrace below (also looks similar is on trying to change the 'Prefer HTML mail' option. Please let me know how I can provide more information. Thanks M. First backtrace - changing the 'Use external editor' setting and clicking OK. Application: KMail (kmail), signal SIGABRT Using host libthread_db library /lib/libthread_db.so.1. [Thread debugging using libthread_db enabled] [New Thread -1208584496 (LWP 1192)] [New Thread -1278411888 (LWP 1239)] [KCrash handler] #6 0x00110402 in __kernel_vsyscall () #7 0x019d5690 in raise () from /lib/libc.so.6 #8 0x019d6f91 in abort () from /lib/libc.so.6 #9 0x019ce93e in __assert_fail () from /lib/libc.so.6 #10 0x00b89180 in AppearancePageHeadersTab::save (this=0x9fca4d8) at /home/kde-devel/kde/src/kdepim/kmail/configuredialog.cpp:1990 #11 0x00bb1a83 in ConfigModuleWithTabs::save (this=0xa002a58) at /home/kde-devel/kde/src/kdepim/kmail/configuredialog_p.cpp:422 #12 0x069bff2b in KCModuleProxy::save (this=0xa0ede58) at /home/kde-devel/kde/src/kdelibs/kutils/kcmoduleproxy.cpp:276 #13 0x069bb39e in KCMultiDialogPrivate::apply (this=0x9ddf4e0) at /home/kde-devel/kde/src/kdelibs/kutils/kcmultidialog.cpp:192 #14 0x069bb646 in KCMultiDialog::slotOkClicked (this=0xa0a8818) at /home/kde-devel/kde/src/kdelibs/kutils/kcmultidialog.cpp:227 #15 0x069bd0d7 in KCMultiDialog::qt_metacall (this=0xa0a8818, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0xbfbc3544) at /home/kde-devel/kde/build/kdelibs/kutils/kcmultidialog.moc:87 #16 0x00b9badc in ConfigureDialog::qt_metacall (this=0xa0a8818, _c=QMetaObject::InvokeMetaMethod, _id=78, _a=0xbfbc3544) at /home/kde-devel/kde/build/kdepim/kmail/configuredialog.moc:67 #17 0x0026ae61 in QMetaObject::activate (sender=0xa0a8818, from_signal_index=44, to_signal_index=44, argv=0x0) at kernel/qobject.cpp:3007 #18 0x0026b2e3 in QMetaObject::activate (sender=0xa0a8818, m=0x684b3c4, local_signal_index=9, argv=0x0) at kernel/qobject.cpp:3080 #19 0x0662f681 in KDialog::okClicked (this=0xa0a8818) at /home/kde-devel/kde/build/kdelibs/kdeui/kdialog.moc:247 #20 0x06630d99 in KDialog::slotButtonClicked (this=0xa0a8818, button=4) at /home/kde-devel/kde/src/kdelibs/kdeui/dialogs/kdialog.cpp:844 #21 0x066333d3 in KDialog::qt_metacall (this=0xa0a8818, _c=QMetaObject::InvokeMetaMethod, _id=33, _a=0xbfbc379c) at /home/kde-devel/kde/build/kdelibs/kdeui/kdialog.moc:181 #22 0x066fa726 in KPageDialog::qt_metacall (this=0xa0a8818, _c=QMetaObject::InvokeMetaMethod, _id=68, _a=0xbfbc379c) at /home/kde-devel/kde/build/kdelibs/kdeui/kpagedialog.moc:63 #23 0x069bd03d in KCMultiDialog::qt_metacall (this=0xa0a8818, _c=QMetaObject::InvokeMetaMethod, _id=68, _a=0xbfbc379c) at /home/kde-devel/kde/build/kdelibs/kutils/kcmultidialog.moc:77 #24 0x00b9badc in ConfigureDialog::qt_metacall (this=0xa0a8818, _c=QMetaObject::InvokeMetaMethod, _id=68, _a=0xbfbc379c) at /home/kde-devel/kde/build/kdepim/kmail/configuredialog.moc:67 #25 0x0026ae61 in QMetaObject::activate (sender=0x9ddf530, from_signal_index=4, to_signal_index=4, argv=0xbfbc379c) at kernel/qobject.cpp:3007 #26 0x0026b2e3 in QMetaObject::activate (sender=0x9ddf530, m=0x304ad8, local_signal_index=0, argv=0xbfbc379c) at kernel/qobject.cpp:3080 #27 0x0027210c in QSignalMapper::mapped (this=0x9ddf530, _t1=4) at .moc/debug-shared/moc_qsignalmapper.cpp:93 #28 0x002721ef in QSignalMapper::map (this=0x9ddf530, sender=0xa15e1a0) at kernel/qsignalmapper.cpp:277 #29 0x002722f0 in QSignalMapper::map (this=0x9ddf530) at kernel/qsignalmapper.cpp:268 #30 0x00272453 in QSignalMapper::qt_metacall (this=0x9ddf530, _c=QMetaObject::InvokeMetaMethod, _id=4, _a
[Bug 166024] New: Kmail +smtp incorrectly reports large emails unsent; sends them multiple times. Crashes on close.
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=166024 Summary: Kmail +smtp incorrectly reports large emails unsent; sends them multiple times. Crashes on close. Product: kmail Version: SVN trunk (KDE 4) Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: mstarkey wcsgabon org In recent builds of kde4, kmail blocks at around 90% on sending large (5-6Mb) messages via smtp. A dialogue pops up saying Mail not sent (Malformed address) and asks whether to continue or abort sending messages. However, the email IS sent, and since I try again, the recipient receives it multiple times. The cancel button won't stop the sending so have to close kmail, at which point it crashes (see backtrace below). This may be two different bugs, but I've been getting it repeatly for the last week, so wanted to report. The backtrace is from a build this morning of 827073. Application: KMail (kmail), signal SIGABRT Using host libthread_db library /lib/libthread_db.so.1. [Thread debugging using libthread_db enabled] [New Thread -1209219376 (LWP 3090)] [KCrash handler] #6 0x00110402 in __kernel_vsyscall () #7 0x02506690 in raise () from /lib/libc.so.6 #8 0x02507f91 in abort () from /lib/libc.so.6 #9 0x0015bbc9 in qt_message_output (msgType=QtFatalMsg, buf=0xbfd81ce0 ASSERT: \!transferInProgress( serNum )\ in file /home/kde-devel/kde/src/kdepim/kmail/messageproperty.cpp, line 161) at global/qglobal.cpp:2058 #10 0x0015bc2d in qFatal (msg=0x2ac518 ASSERT: \%s\ in file %s, line %d) at global/qglobal.cpp:2260 #11 0x0015c093 in qt_assert ( assertion=0xfd5279 !transferInProgress( serNum ), file=0xfd5240 /home/kde-devel/kde/src/kdepim/kmail/messageproperty.cpp, line=161) at global/qglobal.cpp:1828 #12 0x00c8cb06 in KMail::MessageProperty::forget (msgBase=0x9546e48) at /home/kde-devel/kde/src/kdepim/kmail/messageproperty.cpp:161 #13 0x00cef357 in ~KMMsgBase (this=0x9546e48) at /home/kde-devel/kde/src/kdepim/kmail/kmmsgbase.cpp:124 #14 0x00b49bdc in ~KMMessage (this=0x9546e48) at /home/kde-devel/kde/src/kdepim/kmail/kmmessage.cpp:225 #15 0x00cefb5a in KMMsgList::clear (this=0x9068280, doDelete=true, syncDict=false) at /home/kde-devel/kde/src/kdepim/kmail/kmmsglist.cpp:37 #16 0x00d55890 in KMFolderMaildir::close (this=0x9068230, aForced=true) at /home/kde-devel/kde/src/kdepim/kmail/kmfoldermaildir.cpp:259 #17 0x00c563b4 in KMFolder::close (this=0x9068488, owner=0xfea6b2 kmkernel, force=true) at /home/kde-devel/kde/src/kdepim/kmail/kmfolder.cpp:513 #18 0x00d6a666 in KMKernel::cleanup (this=0xbfd83ef0) at /home/kde-devel/kde/src/kdepim/kmail/kmkernel.cpp:1668 #19 0x0804b001 in main (argc=3, argv=0xbfd84074) at /home/kde-devel/kde/src/kdepim/kmail/main.cpp:132 #0 0x00110402 in __kernel_vsyscall () ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 165185] New: kmail crashes on 'send queued mail'
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=165185 Summary: kmail crashes on 'send queued mail' Product: kmail Version: SVN trunk (KDE 4) Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: mstarkey wcsgabon org I just updated my build this morning (rev: 825458), kmail now crashes every time I click on 'send queued mail'. Backtrace: Application: KMail (kmail), signal SIGABRT Using host libthread_db library /lib/libthread_db.so.1. [Thread debugging using libthread_db enabled] [New Thread -1209231664 (LWP 29188)] [New Thread -1271059568 (LWP 29294)] [KCrash handler] #6 0x00110402 in __kernel_vsyscall () #7 0x014d9690 in raise () from /lib/libc.so.6 #8 0x014daf91 in abort () from /lib/libc.so.6 #9 0x0015bbc9 in qt_message_output (msgType=QtFatalMsg, buf=0xbff1a2c0 ASSERT: \false\ in file /home/kde-devel/kde/src/kdepimlibs/mailtransport/transportmanager.cpp, line 233) at global/qglobal.cpp:2058 #10 0x0015bc2d in qFatal (msg=0x2ac518 ASSERT: \%s\ in file %s, line %d) at global/qglobal.cpp:2260 #11 0x0015c093 in qt_assert (assertion=0x7be524 false, file=0x7be3e8 /home/kde-devel/kde/src/kdepimlibs/mailtransport/transportmanager.cpp, line=233) at global/qglobal.cpp:1828 #12 0x007a9191 in MailTransport::TransportManager::createTransportJob ( this=0x91bea70, transport= 0xbff1c400) at /home/kde-devel/kde/src/kdepimlibs/mailtransport/transportmanager.cpp:233 #13 0x00caca1d in KMSender::doSendMsg (this=0x9283f98) at /home/kde-devel/kde/src/kdepim/kmail/kmsender.cpp:535 #14 0x00cade70 in KMSender::doSendQueued (this=0x9283f98, customTransport= 0xbff1c5cc) at /home/kde-devel/kde/src/kdepim/kmail/kmsender.cpp:251 #15 0x00cae60f in KMail::MessageSender::sendQueued (this=0x9283fa0, transport= 0xbff1c5cc) at /home/kde-devel/kde/src/kdepim/kmail/messagesender.h:77 #16 0x00e31f43 in KMMainWidget::slotSendQueued (this=0x933efc0) at /home/kde-devel/kde/src/kdepim/kmail/kmmainwidget.cpp:2016 #17 0x00e535d3 in KMMainWidget::qt_metacall (this=0x933efc0, _c=QMetaObject::InvokeMetaMethod, _id=98, _a=0xbff1c70c) at /home/kde-devel/kde/build/kdepim/kmail/kmmainwidget.moc:417 #18 0x0026ae61 in QMetaObject::activate (sender=0x96577e0, from_signal_index=5, to_signal_index=6, argv=0xbff1c70c) at kernel/qobject.cpp:3007 #19 0x0026b06a in QMetaObject::activate (sender=0x96577e0, m=0x36ffe60, from_local_signal_index=1, to_local_signal_index=2, argv=0xbff1c70c) at kernel/qobject.cpp:3100 #20 0x02ff3dca in QAction::triggered (this=0x96577e0, _t1=false) at .moc/debug-shared/moc_qaction.cpp:216 #21 0x02ff5cde in QAction::activate (this=0x96577e0, event=QAction::Trigger) at kernel/qaction.cpp:1119 #22 0x03422c4c in QMenuPrivate::activateAction (this=0x9b639f8, action=0x96577e0, action_e=QAction::Trigger, self=true) at widgets/qmenu.cpp:1005 #23 0x03425659 in QMenu::mouseReleaseEvent (this=0x9a91140, e=0xbff1cff4) at widgets/qmenu.cpp:2160 #24 0x0464e026 in KMenu::mouseReleaseEvent (this=0x9a91140, e=0xbff1cff4) at /home/kde-devel/kde/src/kdelibs/kdeui/widgets/kmenu.cpp:452 #25 0x0305ba43 in QWidget::event (this=0x9a91140, event=0xbff1cff4) at kernel/qwidget.cpp:6927 #26 0x03420862 in QMenu::event (this=0x9a91140, e=0xbff1cff4) at widgets/qmenu.cpp:2256 #27 0x02ffbd07 in QApplicationPrivate::notify_helper (this=0x9064948, receiver=0x9a91140, e=0xbff1cff4) at kernel/qapplication.cpp:3772 #28 0x02ffc88c in QApplication::notify (this=0xbff1eb9c, receiver=0x9a91140, e=0xbff1cff4) at kernel/qapplication.cpp:3501 #29 0x04584267 in KApplication::notify (this=0xbff1eb9c, receiver=0x9a91140, event=0xbff1cff4) at /home/kde-devel/kde/src/kdelibs/kdeui/kernel/kapplication.cpp:311 #30 0x00256bb2 in QCoreApplication::notifyInternal (this=0xbff1eb9c, receiver=0x9a91140, event=0xbff1cff4) at kernel/qcoreapplication.cpp:583 #31 0x03008165 in QCoreApplication::sendSpontaneousEvent (receiver=0x9a91140, event=0xbff1cff4) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218 #32 0x03002cb6 in QApplicationPrivate::sendMouseEvent (receiver=0x9a91140, event=0xbff1cff4, alienWidget=0x0, nativeWidget=0x9a91140, buttonDown=0x371e280, lastMouseReceiver= 0x371e284) at kernel/qapplication.cpp:2766 #33 0x03077817 in QETWidget::translateMouseEvent (this=0x9a91140, event=0xbff1d5d0) at kernel/qapplication_x11.cpp:4067 #34 0x03075512 in QApplication::x11ProcessEvent (this=0xbff1eb9c, event=0xbff1d5d0) at kernel/qapplication_x11.cpp:3133 #35 0x030a4560 in x11EventSourceDispatch (s=0x90676b0, callback=0, user_data=0x0) at kernel
[Bug 163159] Crashes when forwarding top message in a closed thread
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=163159 --- Additional Comments From mstarkey wcsgabon org 2008-06-09 23:42 --- I confirm fixed - thank you! ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 163674] New: Right clicking on a mis-spelled word should immediately give a list of alternative spellings
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=163674 Summary: Right clicking on a mis-spelled word should immediately give a list of alternative spellings Product: kmail Version: SVN trunk (KDE 4) Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: composer AssignedTo: kdepim-bugs kde org ReportedBy: mstarkey wcsgabon org Title says it all- at the moment it takes a right-click, a mouse movement, a right click a mouse-movement and a left click to correct a mis-spelled word. Why so many steps - better to right click and immediately have a list of alternative spellings available. That would make correcting a mistake - right-click, mouse-movement, left-click (assuming the correct spelling is found , which is often is). Would be nice... Thanks M. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 163159] Crashes when forwarding top message in a closed thread
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=163159 --- Additional Comments From mstarkey wcsgabon org 2008-06-08 17:24 --- Hi, Sorry if I wasn't clear - sending as a digest works fine. It is only when I want to send just the top message that I get the crash. If I forward a closed thread there is a dialog with two buttons - 'Send Digest' and 'Send'. Send Digest works fine, Send produces a crash. If I open the thread (click on the +) and forward, then it forwrds fine. HTH M. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 163159] New: kmail crashes when forwarding top message in a closed thread
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=163159 Summary: kmail crashes when forwarding top message in a closed thread Product: kmail Version: unspecified Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: mstarkey wcsgabon org Version:(using Devel) Installed from:Compiled sources OS:Linux I have kmail displaying messages in threaded mode. If I click on the top message of a closed thread and then forward (inline: Shift-F) it pops up a dialoge saying do I want to send it in digest form. If I click send in digest form, all is well. If I just click 'Send', kmail crashes. Below are part of the konsole output and a backtrace. Thanks for your help. kmail(8746) KMReaderWin::parseMsg: Finished parsing and displaying of message. kmail(8746)/kmail (storage internals) KMFolderMaildir::getDwString: KDE_fopen(abs_file= /home/kde-devel/.kde4/share/apps/kmail/mail/inbox/cur/1212503501.3313.iFmyK , r+) == stream == 0x9e6b2d8 kmail(8746)/kmail (storage internals) KMFolderMaildir::getDwString: fclose(mIndexStream = 0x9e6b2d8 ) kmail(8746)/kmail (storage internals) KMFolderMaildir::getDwString: KDE_fopen(abs_file= /home/kde-devel/.kde4/share/apps/kmail/mail/inbox/cur/1212504105.3313.lCU3F , r+) == stream == 0x9e7c580 kmail(8746)/kmail (storage internals) KMFolderMaildir::getDwString: fclose(mIndexStream = 0x9e7c580 ) kmail(8746)/kmail (storage internals) KMFolderMaildir::getDwString: KDE_fopen(abs_file= /home/kde-devel/.kde4/share/apps/kmail/mail/inbox/cur/1212511974.3313.Gz38v , r+) == stream == 0x9f2fa68 kmail(8746)/kmail (storage internals) KMFolderMaildir::getDwString: fclose(mIndexStream = 0x9f2fa68 ) kmail(8746)/kmail (storage internals) KMFolderMaildir::getDwString: KDE_fopen(abs_file= /home/kde-devel/.kde4/share/apps/kmail/mail/inbox/cur/1212511974.3313.5wbrT , r+) == stream == 0x9ea4ce0 kmail(8746)/kmail (storage internals) KMFolderMaildir::getDwString: fclose(mIndexStream = 0x9ea4ce0 ) kmail(8746)/kdeui (KNotification) KNotification::slotReceivedId: 0 kmail(8746)/kdeui (KNotification) KNotification::close: 0 kmail(8746)/kdeui (KNotification) KNotification::~KNotification: -2 kmail(8746) KMMessage::setCharset: Trying to set a charset for a non-textual mimetype. Fix this caller: [ 0: /home/kde-devel/kde/kde4/lib/libkdecore.so.5(_Z14kRealBacktracei+0x36) [0x5414cc] 1: /home/kde-devel/kde/kde4/lib/libkmailprivate.so.4 [0xb55ead] 2: /home/kde-devel/kde/kde4/lib/libkmailprivate.so.4 [0xb35a42] 3: /home/kde-devel/kde/kde4/lib/libkmailprivate.so.4(_ZN16KMForwardCommand7executeEv+0x1812) [0xe10818] 4: /home/kde-devel/kde/kde4/lib/libkmailprivate.so.4(_ZN9KMCommand16slotPostTransferENS_6ResultE+0x51) [0xe15145] ] *** KMail got signal 11 (Crashing) KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kmail path = unknown pid = 8746 sock_file=/home/kde-devel/.kde4/socket-moabi/kdeinit4_localhost_10 kdeinit4: Got EXEC_NEW '/home/kde-devel/kde/kde4/lib/kde4/libexec/drkonqi' from socket. kdeinit4: preparing to launch /home/kde-devel/kde/kde4/lib/kde4/libexec/drkonqi kio_pop3(9346) POP3Protocol::~POP3Protocol: kio_pop3(9347) POP3Protocol::~POP3Protocol: kio_pop3(9348) POP3Protocol::~POP3Protocol: kdeinit4: PID 9346 terminated. kdeinit4: PID 9348 terminated. kdeinit4: PID 9347 terminated. kmail(8746) KMReaderWin::parseMsg: Finished parsing and displaying of message. kmail(8746)/kmail (storage internals) KMFolderMaildir::getDwString: KDE_fopen(abs_file= /home/kde-devel/.kde4/share/apps/kmail/mail/inbox/cur/1212503501.3313.iFmyK , r+) == stream == 0x9e6b2d8 kmail(8746)/kmail (storage internals) KMFolderMaildir::getDwString: fclose(mIndexStream = 0x9e6b2d8 ) kmail(8746)/kmail (storage internals) KMFolderMaildir::getDwString: KDE_fopen(abs_file= /home/kde-devel/.kde4/share/apps/kmail/mail/inbox/cur/1212504105.3313.lCU3F , r+) == stream == 0x9e7c580 kmail(8746)/kmail (storage internals) KMFolderMaildir::getDwString: fclose(mIndexStream = 0x9e7c580 ) kmail(8746)/kmail (storage internals) KMFolderMaildir::getDwString: KDE_fopen(abs_file= /home/kde-devel/.kde4/share/apps/kmail/mail/inbox/cur/1212511974.3313.Gz38v , r+) == stream == 0x9f2fa68 kmail(8746)/kmail (storage internals) KMFolderMaildir::getDwString: fclose(mIndexStream = 0x9f2fa68 ) kmail(8746)/kmail (storage internals) KMFolderMaildir::getDwString: KDE_fopen(abs_file= /home/kde-devel/.kde4/share/apps/kmail/mail/inbox/cur/1212511974.3313.5wbrT , r+) == stream == 0x9ea4ce0
[Bug 162174] 100% CPU use when checking mail during sending another mail
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=162174 mstarkey wcsgabon org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||WORKSFORME --- Additional Comments From mstarkey wcsgabon org 2008-06-03 21:28 --- I updated to a recent build and this problem seems to have been solved. Closing. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 162175] Unable to send with uuplus SMTP on localhost port 1025
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=162175 --- Additional Comments From mstarkey wcsgabon org 2008-06-03 21:29 --- Note that this is a problem with the smtp server on localhost, not with the uuplus smtp programme. If I run uuplus smtp on another machine (physical or virtual), kmail connects just fine. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 162867] Crash when changing password in POP3 account
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=162867 --- Additional Comments From mstarkey wcsgabon org 2008-05-31 20:42 --- Here you go. Note that it seems to only happen when I am running kmail over ssh -X as in the techbase tutorial, and does not occur when I run a full Kde 4 desktop session. Thanks for your help. Application: KMail (kmail), signal SIGABRT [?1034hUsing host libthread_db library /lib/libthread_db.so.1. [Thread debugging using libthread_db enabled] [New Thread -1208232240 (LWP 3476)] [New Thread -1255236720 (LWP 3479)] [KCrash handler] #6 0x00110402 in __kernel_vsyscall () #7 0x02320690 in raise () from /lib/libc.so.6 #8 0x02321f91 in abort () from /lib/libc.so.6 #9 0x0015bbc9 in qt_message_output (msgType=QtFatalMsg, buf=0xbfa08c70 ASSERT failure in QVectorT::at: \index out of range\, file ../../include/QtCore/../../src/corelib/tools/qvector.h, line 323) at global/qglobal.cpp:2058 #10 0x0015bc2d in qFatal ( msg=0x2ac3bc ASSERT failure in %s: \%s\, file %s, line %d) at global/qglobal.cpp:2260 #11 0x0015bc72 in qt_assert_x (where=0x1eecf4a QVectorT::at, what=0x1eecf37 index out of range, file=0x1eecf00 ../../include/QtCore/../../src/corelib/tools/qvector.h, line=323) at global/qglobal.cpp:1836 #12 0x01db09eb in QVectorQTreeViewItem::at (this=0x897e770, i=1) at ../../include/QtCore/../../src/corelib/tools/qvector.h:323 #13 0x01da2f35 in QTreeViewPrivate::rowsRemoved (this=0x897e518, parent= 0xbfa0b044, start=1, end=1, after=false) at itemviews/qtreeview.cpp:3649 #14 0x01da5eda in QTreeView::rowsAboutToBeRemoved (this=0x8901788, parent= 0xbfa0b044, start=1, end=1) at itemviews/qtreeview.cpp:2425 #15 0x01d6fcd1 in QAbstractItemView::qt_metacall (this=0x8901788, _c=QMetaObject::InvokeMetaMethod, _id=18, _a=0xbfa0afd4) at .moc/debug-shared/moc_qabstractitemview.cpp:225 #16 0x01dae3b0 in QTreeView::qt_metacall (this=0x8901788, _c=QMetaObject::InvokeMetaMethod, _id=49, _a=0xbfa0afd4) at .moc/debug-shared/moc_qtreeview.cpp:121 #17 0x01de4794 in QTreeWidget::qt_metacall (this=0x8901788, _c=QMetaObject::InvokeMetaMethod, _id=49, _a=0xbfa0afd4) at .moc/debug-shared/moc_qtreewidget.cpp:123 #18 0x053d76fa in KPIM::TreeWidget::qt_metacall (this=0x8901788, _c=QMetaObject::InvokeMetaMethod, _id=49, _a=0xbfa0afd4) at /home/kde-devel/kde/build/kdepim/libkdepim/moc_treewidget.cpp:63 #19 0x00dc088c in KMMimePartTree::qt_metacall (this=0x8901788, _c=QMetaObject::InvokeMetaMethod, _id=49, _a=0xbfa0afd4) at /home/kde-devel/kde/build/kdepim/kmail/kmmimeparttree.moc:78 #20 0x0026ae61 in QMetaObject::activate (sender=0x880c428, from_signal_index=10, to_signal_index=10, argv=0xbfa0afd4) at kernel/qobject.cpp:3007 #21 0x0026b2e3 in QMetaObject::activate (sender=0x880c428, m=0x305758, local_signal_index=6, argv=0xbfa0afd4) at kernel/qobject.cpp:3080 #22 0x002aa50c in QAbstractItemModel::rowsAboutToBeRemoved (this=0x880c428, _t1= 0xbfa0b044, _t2=1, _t3=1) at .moc/debug-shared/moc_qabstractitemmodel.cpp:164 #23 0x0024c4a4 in QAbstractItemModel::beginRemoveRows (this=0x880c428, parent= 0xbfa0b044, first=1, last=1) at kernel/qabstractitemmodel.cpp:2121 #24 0x01ddf499 in QTreeModel::beginRemoveItems (this=0x880c428, parent=0x8efc9f0, row=1, count=1) at itemviews/qtreewidget.cpp:815 #25 0x01de1e5f in QTreeWidgetItem::takeChild (this=0x8efc9f0, index=1) at itemviews/qtreewidget.cpp:1923 #26 0x00dbee29 in KMMimePartTreeItem (this=0x8e86d78, parent=0x8efc9f0, node=0x8e6d388, description= 0xbfa0b158, mimetype= 0xbfa0b154, encoding= 0xbfa0b150, size=190, revertOrder=false) at /home/kde-devel/kde/src/kdepim/kmail/kmmimeparttree.cpp:411 #27 0x00df7bad in partNode::fillMimePartTree (this=0x8e6d388, parentItem=0x8efc9f0, mimePartTree=0x0, labelDescr= 0xbfa0b2bc, labelCntType= 0xbfa0b2b8, labelEncoding= 0xbfa0b2b4, size=0, revertOrder=false) at /home/kde-devel/kde/src/kdepim/kmail/partNode.cpp:505 #28 0x00df7d0f in partNode::fillMimePartTree (this=0x8e763f8, parentItem=0x0, mimePartTree=0x8901788, labelDescr= 0xbfa0b408, labelCntType= 0xbfa0b450, labelEncoding= 0xbfa0b404, size=2421, revertOrder=false) at /home/kde-devel/kde/src/kdepim/kmail/partNode.cpp:517 #29 0x00c767be in KMReaderWin::parseMsg (this=0x8900290, aMsg=0x8eddd80) at /home/kde-devel/kde/src/kdepim/kmail/kmreaderwin.cpp:1527 #30 0x00c6aa08 in KMReaderWin::displayMessage (this=0x8900290) at /home/kde-devel/kde/src/kdepim/kmail/kmreaderwin.cpp:1483 #31 0x00c6ab68 in KMReaderWin::updateReaderWin (this=0x8900290) at /home/kde-devel/kde/src/kdepim/kmail/kmreaderwin.cpp:1423 #32 0x00c6b2b8 in KMReaderWin::setMsg (this=0x8900290, aMsg=0x8eddd80, force=true) at /home/kde-devel/kde/src/kdepim/kmail/kmreaderwin.cpp:1225 #33 0x00c6311f
[Bug 162867] Kmail crashes changing password in pop account
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=162867 --- Additional Comments From mstarkey wcsgabon org 2008-05-30 10:31 --- Sorry just to clarify: In Configure Kmail - Accounts, I click on Modify, then update the pop3 password. Clicking OK closes that window. It is when I click on OK in the Accounts window that the crash occurs. Thanks ! ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
