From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
...that you can get rid of the "[mailing list name]"
added to the subject of some mailing lists by using the rewrite
header filter action? Just use
rewrite header "Subject"
replace "\s*\[mailing list name\]\s*"
with ""
This tip is egoistic - it might be good for the single user using KMail, but can upset all the other mailinglist users because it clutters up the subject :-(
Example:
Original Subject: Re: [ML] Hi!
After rewriting: Re: Hi!
So far, so good.
If you send a reply, it's still "Re: Hi!". Unfortunately, the list manager will prefix it with [ML] again, which results in this subject:
[ML] Re: Hi!
(this is how all other list members will see it)
Now if someone without the subject filter replies (which is the majority of the list members), you will see a subject like:
Re: [ML] Re: Hi!
Please note the duplicate "Re:" that is now in the subject.
After some more replies, the subject can even look more funny. Just imagine someone replaces "[a long list prefix]" with "[long-ML]" or something like that instead of removing it completely - it's only a question of time until you end up with something like
Re: [a long list prefix] Re: [long-ML] Re: [long-ML] Re: Hi!
I see two options for the tip:
- add a notice that the subject should *never* be changed
if one wants to reply to the mailinglist (because the
subject will be cluttered up with crap)
- drop this tip completely
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
Thomas
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
There is also no notifier in the kontact taskbar, to display information about the current status from kontact (online/offline) would be also a nice feature...
My third wish, that is probably more difficult to realise, where to add a feature, enabling kontact to get the state from knetwork manager....
Sometimes small feature, can really improve the way you're working, and save you a lot time.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
Sometimes during the first try the status message is that X messages were
downloaded in 0 (!) KB. The second try gives the correct number of messages
with the correct size, the third try gives the error.
With another POP3 account I get:
"Could not login to XXX. The password may be wrong.
The server said: "[IN-USE] Unable to lock maildrop: Mailbox is locked by POP
server"
kio_pop3: pop3_open()
kdeinit: Got EXEC_NEW 'kio_pop3' from launcher.
kio_pop3: POP3Protocol::POP3Protocol()
kdeinit: Got EXEC_NEW 'kio_pop3' from launcher.
kdeinit: Got EXEC_NEW 'kio_pop3' from launcher.
kdeinit: Got EXEC_NEW 'kio_pop3' from launcher.
kio_pop3: POP3Protocol::POP3Protocol()
kio_pop3: POP3Protocol::POP3Protocol()
kio_pop3: pop3_open()
kio_pop3: pop3_open()
kio_pop3: POP3Protocol::POP3Protocol()
kio_pop3: pop3_open()
kio_pop3: pop3_open()
kio_pop3: greeting: mail.XXX.ro Cyrus POP3 v2.2.12 server ready
kio_pop3: Trying USER/PASS
kio_pop3: greeting: mail.XXX.ro Cyrus POP3 v2.2.12 server ready
kio_pop3: Trying USER/PASS
kio_pop3: greeting: mail.XXX.ro Cyrus POP3 v2.2.12 server ready
kio_pop3: Trying USER/PASS
kio_pop3: greeting: mail.XXX.ro Cyrus POP3 v2.2.12 server ready
kio_pop3: Trying USER/PASS
kio_pop3: USER/PASS login succeeded
kio_pop3: pop3_open()
kio_pop3: Reusing old connection
kio_pop3: greeting: mail.XXX.ro Cyrus POP3 v2.2.12 server ready
kio_pop3: Trying USER/PASS
kio_pop3: Finishing up list
kio_pop3: Couldn't login. Bad password Sorry.
kio_pop3: Couldn't login. Bad password Sorry.
kio_pop3: Couldn't login. Bad password Sorry.
kio_pop3: pop3_open failed
kio_pop3: pop3_open failed
kio_pop3: Couldn't login. Bad password Sorry.
kio_pop3: pop3_open failed
kio_pop3: pop3_open failed
I have to say that the password is OK in this case.
Both accounts worked fine until I recompiled all my KDE, including KMail from
the above revision.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
*** This bug has been marked as a duplicate of 128357 ***
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
From: Ingo Klöcker
Message-id: <200711062238.29142 erwin ingo-kloecker de>
Subject: Re: [Kde-pim] compacting mbox shows empty folder
On Tuesday 06 November 2007, Rex Dieter wrote:
> See also,
> http://bugs.kde.org/146967
>
> Does the provided patch look good?
Not really. It might fix the symptoms but it does not seem to fix the
real problem. Anyway, the patch shouldn't hurt and thus it should
probably be applied.
Regards,
Ingo
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
Maybe Sebastian Kügler knows more? He recently fixed a very similar thing in KPageDialog, which is a parent class of KSettings::Dialog.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
Messages should be kept in original form as they were received from pop3 server. If KMail have to add something do it in other file.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
*** This bug has been marked as a duplicate of 136145 ***
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
*** This bug has been marked as a duplicate of 143627 ***
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
Did you use a new clean user?
Thanks.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
The remedy is to answer kwallet so it is now open; restart kmail to refresh connection to kwallet; retype the kmail passwords; tick box to save kmail passwords; now ok... But it was a big effort to get there...
[1] I have seen a post (#139844) about starting a separate kwallet thread so kmail does not look like it has hung. Is this the reason kmail continues alone?
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
Rather than having:
- beep
- detailed new mail notification
- other actions
--- play a sound
There should be:
- sound to play
--- soundfile xy
--- beep
--- none
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
Click on New, select criteria. Select 'Move to Folder' as action. Click on folder button (button has folder icon and no label). "Select Folder - KMail" dialog box opens, containing single entry "Local Folders".
Double-click on "Local Folders" or single click on [-] (normally used to expand/collapse tree) will cause crash.
Note this also crashes when using "Message->Create Filter->Filter on From" from main menu, and the same button is used to select the folder to move messages into (same "Select Folder - KMail" dialog box opens etc.
Note that the tree is not populated with the Local Folders in the "Select Folder -KMail" dialog box.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
Changing it manually to "Müller" will also misspell it in receiver's mailbox to "=?iso-8859-1?q?M=FCller?=".
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
KMail settings will open OK.
Here is the backtrace:
Aplicación: Kontact (kontact), señal SIGABRT
[Thread debugging using libthread_db enabled]
[New Thread 0xb4e5f700 (LWP 16455)]
[KCrash handler]
#6 0xb7f9e424 in __kernel_vsyscall ()
#7 0xb549e740 in raise () from /lib/libc.so.6
#8 0xb54a0078 in abort () from /lib/libc.so.6
#9 0xb549768e in __assert_fail () from /lib/libc.so.6
#10 0xb18e2393 in KMKernel::self ()
at /home/dario/myData/ArchPKG/kdemod4/work/kdepim/src/kdepim-4.0.99/kmail/kmkernel.cpp:2096
#11 0xb1a61b39 in CustomTemplates (this=0x9e409d8, parent=0x0, name=0x0)
at /home/dario/myData/ArchPKG/kdemod4/work/kdepim/src/kdepim-4.0.99/kmail/customtemplates.cpp:88
#12 0xb1760dfa in ComposerPageCustomTemplatesTab (this=0x9e1fd08, parent=0x0)
at /home/dario/myData/ArchPKG/kdemod4/work/kdepim/src/kdepim-4.0.99/kmail/configuredialog.cpp:3346
#13 0xb176696c in ComposerPage (this=0x9cf0688, instance= 0x0, parent=0x0)
at /home/dario/myData/ArchPKG/kdemod4/work/kdepim/src/kdepim-4.0.99/kmail/configuredialog.cpp:2794
#14 0xb1c003e1 in create_kmail_config_composer (parent=0x9b28d90)
at /home/dario/myData/ArchPKG/kdemod4/work/kdepim/src/kdepim-4.0.99/kmail/kcm_kmail.cpp:60
#15 0xb5711a4d in KCModuleLoader::loadModule (mod= 0x9d3f508,
report=KCModuleLoader::Inline, parent=0x9b28d90, args= 0x9d3f4f0)
at /home/dario/myData/ArchPKG/kdemod4/work/kdelibs/src/kdelibs-4.0.99/kutils/kcmoduleloader.cpp:112
#16 0xb571632f in KCModuleProxyPrivate::loadModule (this=0x9d3f4f0)
at /home/dario/myData/ArchPKG/kdemod4/work/kdelibs/src/kdelibs-4.0.99/kutils/kcmoduleproxy.cpp:107
#17 0xb5716d74 in KCModuleProxy::realModule (this=0x9b28d90)
at /home/dario/myData/ArchPKG/kdemod4/work/kdelibs/src/kdelibs-4.0.99/kutils/kcmoduleproxy.cpp:83
#18 0xb5716da0 in KCModuleProxy::minimumSizeHint (this=0x9b28d90)
at /home/dario/myData/ArchPKG/kdemod4/work/kdelibs/src/kdelibs-4.0.99/kutils/kcmoduleproxy.cpp:346
#19 0xb71bd30d in KPageViewPrivate::_k_modelChanged (this=0x9cc8a08)
at /home/dario/myData/ArchPKG/kdemod4/work/kdelibs/src/kdelibs-4.0.99/kdeui/paged/kpageview.cpp:204
#20 0xb71bd4d5 in KPageView::qt_metacall (this=0x9cc8650,
_c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfab9018)
at /home/dario/myData/ArchPKG/kdemod4/work/kdelibs/src/build/kdeui/kpageview.moc:92
#21 0xb71c0b99 in KPageWidget::qt_metacall (this=0x9cc8650,
_c=QMetaObject::InvokeMetaMethod, _id=29, _a=0xbfab9018)
at /home/dario/myData/ArchPKG/kdemod4/work/kdelibs/src/build/kdeui/kpagewidget.moc:69
#22 0xb6b5d636 in QMetaObject::activate (sender=0x9ccf198,
from_signal_index=, to_signal_index=6, argv=0x0)
at kernel/qobject.cpp:3010
#23 0xb6b5f73a in QMetaObject::activate (sender=0x9ccf198, m=0xb6c32178,
local_signal_index=2, argv=0x0) at kernel/qobject.cpp:3080
#24 0xb6b98bc6 in QAbstractItemModel::layoutChanged (this=0x9ccf198)
at .moc/debug-shared/moc_qabstractitemmodel.cpp:137
#25 0xb71c21f0 in KPageWidgetModel::addSubPage (this=0x9ccf198,
parent=0x9d5b960, item=0x9d4b1e8)
at /home/dario/myData/ArchPKG/kdemod4/work/kdelibs/src/kdelibs-4.0.99/kdeui/paged/kpagewidgetmodel.cpp:452
#26 0xb71c0d4c in KPageWidget::addSubPage (this=0x9cc8650, parent=0x9d5b960,
item=0x9d4b1e8)
at /home/dario/myData/ArchPKG/kdemod4/work/kdelibs/src/kdelibs-4.0.99/kdeui/paged/kpagewidget.cpp:107
#27 0xb71baf39 in KPageDialog::addSubPage (this=0x9b6ed28, parent=0x9d5b960,
item=0x9d4b1e8)
at /home/dario/myData/ArchPKG/kdemod4/work/kdelibs/src/kdelibs-4.0.99/kdeui/paged/kpagedialog.cpp:100
#28 0xb5714346 in KCMultiDialog::addModule (this=0x9b6ed28,
moduleInfo= 0x9d81e28, parentItem=0x9d5b960, args= 0x9b69c6c)
at /home/dario/myData/ArchPKG/kdemod4/work/kdelibs/src/kdelibs-4.0.99/kutils/kcmultidialog.cpp:305
#29 0xb5726c86 in KSettings::DialogPrivate::createDialogFromServices (
this=0x9b69be8)
at /home/dario/myData/ArchPKG/kdemod4/work/kdelibs/src/kdelibs-4.0.99/kutils/ksettings/dialog.cpp:318
#30 0xb5728041 in KSettings::Dialog::showEvent (this=0x9b6ed28)
at /home/dario/myData/ArchPKG/kdemod4/work/kdelibs/src/kdelibs-4.0.99/kutils/ksettings/dialog.cpp:120
#31 0xb590b4c2 in QWidget::event (this=0x9b6ed28, event=0xbfab98e0)
at kernel/qwidget.cpp:7122
#32 0xb58b1fa8 in QApplicationPrivate::notify_helper (this=0x9924c18,
receiver=0x9b6ed28, e=0xbfab98e0) at kernel/qapplication.cpp:3772
#33 0xb58b8d31 in QApplication::notify (this=0xbfabab5c, receiver=0x9b6ed28,
e=0xbfab98e0) at kernel/qapplication.cpp:3739
#34 0xb718f5b0 in KApplication::notify (this=0xbfabab5c, receiver=0x9b6ed28,
event=0xbfab98e0)
at /home/dario/myData/ArchPKG/kdemod4/work/kdelibs/src/kdelibs-4.0.99/kdeui/kernel/kapplication.cpp:311
#35 0xb6b46ec1 in QCoreApplication::notifyInternal (this=0xbfabab5c,
receiver=0x9b6ed28, event=0xbfab98e0) at kernel/qcoreapplication.cpp:587
#36 0xb590e0b6 in QWidgetPrivate::show_helper (this=0x9b69ce8)
at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#37 0xb590e640 in QWidget::setVisible (this=0x9b6ed28, visible=true)
at kernel/qwidget.cpp:6378
#38 0xb5d380a3 in QDialog::setVisible (this=0x9b6ed28, visible=true)
at dialogs/qdialog.cpp:655
#39 0xb7f6045f in Kontact::MainWindow::slotPreferences ()
from /opt/kdemod/lib/libkontactprivate.so.4
#40 0xb7f65648 in Kontact::MainWindow::qt_metacall ()
from /opt/kdemod/lib/libkontactprivate.so.4
#41 0xb6b5d636 in QMetaObject::activate (sender=0x9ae68b8,
from_signal_index=, to_signal_index=6, argv=0x0)
at kernel/qobject.cpp:3010
#42 0xb6b5daee in QMetaObject::activate (sender=0x9ae68b8, m=0xb60905d8,
from_local_signal_index=1, to_local_signal_index=2, argv=0xbfab9b00)
at kernel/qobject.cpp:3100
#43 0xb58ac0a8 in QAction::triggered (this=0x9ae68b8, _t1=false)
at .moc/debug-shared/moc_qaction.cpp:216
#44 0xb58ac90c in QAction::activate (this=0x9ae68b8, event=QAction::Trigger)
at kernel/qaction.cpp:1119
#45 0xb5ca54ee in QMenuPrivate::activateAction (this=0x9b20de8,
action=0x9ae68b8, action_e=QAction::Trigger, self=true)
at widgets/qmenu.cpp:1005
#46 0xb5ca5f15 in QMenu::mouseReleaseEvent (this=0x9ac2900, e=0xbfaba2ac)
at widgets/qmenu.cpp:2160
#47 0xb723d801 in KMenu::mouseReleaseEvent (this=0x9ac2900, e=0xbfaba2ac)
at /home/dario/myData/ArchPKG/kdemod4/work/kdelibs/src/kdelibs-4.0.99/kdeui/widgets/kmenu.cpp:452
#48 0xb590b68a in QWidget::event (this=0x9ac2900, event=0xbfaba2ac)
at kernel/qwidget.cpp:6927
#49 0xb5ca82ca in QMenu::event (this=0x9ac2900, e=0xbfaba2ac)
at widgets/qmenu.cpp:2256
#50 0xb58b1fa8 in QApplicationPrivate::notify_helper (this=0x9924c18,
receiver=0x9ac2900, e=0xbfaba2ac) at kernel/qapplication.cpp:3772
#51 0xb58b965b in QApplication::notify (this=0xbfabab5c, receiver=0x9ac2900,
e=0xbfaba2ac) at kernel/qapplication.cpp:3501
#52 0xb718f5b0 in KApplication::notify (this=0xbfabab5c, receiver=0x9ac2900,
event=0xbfaba2ac)
at /home/dario/myData/ArchPKG/kdemod4/work/kdelibs/src/kdelibs-4.0.99/kdeui/kernel/kapplication.cpp:311
#53 0xb6b46ec1 in QCoreApplication::notifyInternal (this=0xbfabab5c,
receiver=0x9ac2900, event=0xbfaba2ac) at kernel/qcoreapplication.cpp:587
#54 0xb58baae0 in QApplicationPrivate::sendMouseEvent (receiver=0x9ac2900,
event=0xbfaba2ac, alienWidget=0x0, nativeWidget=0x9ac2900,
buttonDown=0xb60a7540, lastMouseReceiver= 0xb60a7544)
at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#55 0xb5925cf2 in QETWidget::translateMouseEvent (this=0x9ac2900,
event=0xbfaba77c) at kernel/qapplication_x11.cpp:4067
#56 0xb5924fe9 in QApplication::x11ProcessEvent (this=0xbfabab5c,
event=0xbfaba77c) at kernel/qapplication_x11.cpp:3133
#57 0xb594c770 in x11EventSourceDispatch (s=0x9927980, callback=0,
user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:148
#58 0xb52e80e8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#59 0xb52eb783 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0
#60 0xb52eb941 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#61 0xb6b729b1 in QEventDispatcherGlib::processEvents (this=0x9923c60, flags=
{i = -1079269080}) at kernel/qeventdispatcher_glib.cpp:325
#62 0xb594bf0d in QGuiEventDispatcherGlib::processEvents (this=0x9923c60,
flags={i = -1079269032}) at kernel/qguieventdispatcher_glib.cpp:204
#63 0xb6b45a4c in QEventLoop::processEvents (this=0xbfaba9d0, flags=
{i = -1079268968}) at kernel/qeventloop.cpp:149
#64 0xb6b45c05 in QEventLoop::exec (this=0xbfaba9d0, flags={i = -1079268904})
at kernel/qeventloop.cpp:200
#65 0xb6b480c6 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845
#66 0xb58b1d53 in QApplication::exec () at kernel/qapplication.cpp:3304
#67 0x0804bf87 in main ()
#0 0xb7f9e424 in __kernel_vsyscall ()
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
kmail(12802) KMail::ActionScheduler::moveMessageFinished: Moving the message
from the temporary filter folder to the target folder failed. Message will stay
unfiltered.
kmail(12802) KMail::ActionScheduler::moveMessageFinished: This might be
becauseyou're using GMail, see bug 166150.
QPainter::end: Painter ended with 2 saved states
kmail(12802) KMFolderMgr::removeFolderAux: Can not find parent folder
ASSERT: "!transferInProgress( serNum )" in file
/home/mandrake/rpm/BUILD/kdepim-4.1.1/kmail/messageproperty.cpp, line 180
*** KMail got signal 6 (Crashing)
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = kmail path = pid = 12802
sock_file=/home/anaselli/.kde4/socket-localhost/kdeinit4__0
--
Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
It WIPED OUT ALL my mails!
When do you want to fix this?
--=20
Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=3Demail
------- You are receiving this mail because: -------
You are the assignee for the bug.=
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
Application: Kontact (kontact), signal SIGSEGV
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7feb2f4d36f0 (LWP 10911)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#5 0x00007feb15316637 in ?? ()
from /usr/lib/kde4/akregator_mk4storage_plugin.so
#6 0x00007feb15309cbc in ?? ()
from /usr/lib/kde4/akregator_mk4storage_plugin.so
#7 0x00007feb15318c25 in ?? ()
from /usr/lib/kde4/akregator_mk4storage_plugin.so
#8 0x00007feb1531a049 in ?? ()
from /usr/lib/kde4/akregator_mk4storage_plugin.so
#9 0x00007feb15311c09 in ?? ()
from /usr/lib/kde4/akregator_mk4storage_plugin.so
#10 0x00007feb15319445 in ?? ()
from /usr/lib/kde4/akregator_mk4storage_plugin.so
#11 0x00007feb1531adcd in ?? ()
from /usr/lib/kde4/akregator_mk4storage_plugin.so
#12 0x00007feb15c5af76 in Akregator::Article::setKeep ()
from /usr/lib/kde4/akregatorpart.so
#13 0x00007feb15c6b06f in Akregator::Feed::appendArticles ()
from /usr/lib/kde4/akregatorpart.so
#14 0x00007feb15c6b832 in Akregator::Feed::fetchCompleted ()
from /usr/lib/kde4/akregatorpart.so
#15 0x00007feb15c6bd18 in Akregator::Feed::qt_metacall ()
from /usr/lib/kde4/akregatorpart.so
#16 0x00007feb2de34134 in QMetaObject::activate ()
from /usr/lib/libQtCore.so.4
#17 0x00007feb155c0972 in Syndication::Loader::loadingComplete ()
from /usr/lib/libsyndication.so.4
#18 0x00007feb155c1dab in Syndication::Loader::slotRetrieverDone ()
from /usr/lib/libsyndication.so.4
#19 0x00007feb155c2227 in Syndication::Loader::qt_metacall ()
from /usr/lib/libsyndication.so.4
#20 0x00007feb2de34134 in QMetaObject::activate ()
from /usr/lib/libQtCore.so.4
#21 0x00007feb155c4b03 in Syndication::DataRetriever::dataRetrieved ()
from /usr/lib/libsyndication.so.4
#22 0x00007feb155c55cd in Syndication::FileRetriever::slotResult ()
from /usr/lib/libsyndication.so.4
#23 0x00007feb155c58d7 in Syndication::FileRetriever::qt_metacall ()
from /usr/lib/libsyndication.so.4
#24 0x00007feb2de34134 in QMetaObject::activate ()
from /usr/lib/libQtCore.so.4
#25 0x00007feb2e1fdb72 in KJob::result () from /usr/lib/libkdecore.so.5
#26 0x00007feb2e1fdf37 in KJob::emitResult () from /usr/lib/libkdecore.so.5
#27 0x00007feb2bb3f0f0 in KIO::SimpleJob::slotFinished ()
from /usr/lib/libkio.so.5
#28 0x00007feb2bb42543 in KIO::TransferJob::slotFinished ()
from /usr/lib/libkio.so.5
#29 0x00007feb2bb432a5 in KIO::TransferJob::qt_metacall ()
from /usr/lib/libkio.so.5
#30 0x00007feb2de34134 in QMetaObject::activate ()
from /usr/lib/libQtCore.so.4
#31 0x00007feb2bbfa0a1 in KIO::SlaveInterface::dispatch ()
from /usr/lib/libkio.so.5
#32 0x00007feb2bbf6f02 in KIO::SlaveInterface::dispatch ()
from /usr/lib/libkio.so.5
#33 0x00007feb2bbe7f53 in KIO::Slave::gotInput () from /usr/lib/libkio.so.5
#34 0x00007feb2bbea678 in KIO::Slave::qt_metacall () from /usr/lib/libkio.so.5
#35 0x00007feb2de34134 in QMetaObject::activate ()
from /usr/lib/libQtCore.so.4
#36 0x00007feb2bb0c830 in ?? () from /usr/lib/libkio.so.5
#37 0x00007feb2bb0c96a in KIO::Connection::qt_metacall ()
from /usr/lib/libkio.so.5
#38 0x00007feb2de2eda5 in QObject::event () from /usr/lib/libQtCore.so.4
#39 0x00007feb2d341c3d in QApplicationPrivate::notify_helper ()
from /usr/lib/libQtGui.so.4
#40 0x00007feb2d3499ea in QApplication::notify () from /usr/lib/libQtGui.so.4
#41 0x00007feb2e77bb8b in KApplication::notify () from /usr/lib/libkdeui.so.5
#42 0x00007feb2de1fd61 in QCoreApplication::notifyInternal ()
from /usr/lib/libQtCore.so.4
#43 0x00007feb2de209fa in QCoreApplicationPrivate::sendPostedEvents ()
from /usr/lib/libQtCore.so.4
#44 0x00007feb2de484d3 in ?? () from /usr/lib/libQtCore.so.4
#45 0x00007feb27550d3b in g_main_context_dispatch ()
from /usr/lib/libglib-2.0.so.0
#46 0x00007feb2755450d in ?? () from /usr/lib/libglib-2.0.so.0
#47 0x00007feb275546cb in g_main_context_iteration ()
from /usr/lib/libglib-2.0.so.0
#48 0x00007feb2de4815f in QEventDispatcherGlib::processEvents ()
from /usr/lib/libQtCore.so.4
#49 0x00007feb2d3d3a9f in ?? () from /usr/lib/libQtGui.so.4
#50 0x00007feb2de1e682 in QEventLoop::processEvents ()
from /usr/lib/libQtCore.so.4
#51 0x00007feb2de1e80d in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#52 0x00007feb2de20cbd in QCoreApplication::exec ()
from /usr/lib/libQtCore.so.4
#53 0x00000000004048e5 in _start ()
#0 0x00007feb2cba05f0 in nanosleep () from /lib/libc.so.6
--
Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
that it includes people not registered to the computer system, but still to
your address book (and thus to your own virtual computer system).
--
Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
QObject: Do not delete object, 'unnamed', during its event handler!
kdeinit4: preparing to launch /usr/lib/kde4/libexec/drkonqi
ASSERT: "d->appConnection.inited()" in file ../../kio/kio/slavebase.cpp, line
265
kioslave: ####### CRASH ###### protocol = imap pid = 8713 signal = 6
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
*** KMail got signal 6 (Crashing)
(8705)/: Communication problem with "kontact" , it
probably crashed.
Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did not
receive a reply (timeout by message bus)" "
KCrash: Application 'kontact' crashing...
sock_file=/home/drazzib/.kde4/socket-gauloise/kdeinit4__0
--
Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
letters, an exclamation point. You may need to press RightShift-RightContro=
l to
set directionality of the compose window to RTL.
--=20
Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=3Demail
------- You are receiving this mail because: -------
You are the assignee for the bug.=
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
this is a user setting issue?
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
right click the attachment and chose save.
Then go to some fish:// path and click Save As..
You get a error message stating: Could not write the file /path-without-fish://
Twist: The filename has been touched remotely, thus giving a file with the
attachments name with the size 0
Confirmed with current trunk, with original ~/.fishsrv.pl removed.
Something different happens if the attachment icon is dragged to a Dolphin or
Konqueror view showing the fish: path, instead of going through the save
dialogue. Nothing is created there, not even an empty file, but an error box
is displayed with the message:
The file or folder /tmp/kde-jjm4/kmailr11025.3/ATTACHMENT_NAME
does not exist.
The same also happens in both these cases for saving to a smb: or ftp:
location.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
working on this feature until KMail has a proper full-fledged HTML composer
(based on WebKit/KHTML contentEditable), like Mailody has.
The current composer arch. is so extremely limited that it is never going to be
able to properly preserve most formatting anyway.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
0x00000035718a7f81 in nanosleep () from /lib64/libc.so.6
[Current thread is 1 (Thread 0x7fd63c7fc800 (LWP 7455))]
Thread 2 (Thread 0x7fd62c944950 (LWP 7469)):
#0 0x00000035718deaa2 in select () from /lib64/libc.so.6
#1 0x0000003d5e522626 in ?? () from /usr/lib64/libQtCore.so.4
#2 0x0000003d5e459852 in ?? () from /usr/lib64/libQtCore.so.4
#3 0x00000035724073da in start_thread () from /lib64/libpthread.so.0
#4 0x00000035718e62bd in clone () from /lib64/libc.so.6
Thread 1 (Thread 0x7fd63c7fc800 (LWP 7455)):
[KCrash Handler]
#5 0x0000003d6baa35ef in ?? () from /usr/lib64/libkmailprivate.so.4
#6 0x0000003d6b983cfe in KMMainWidget::updateMessageActions () from
/usr/lib64/libkmailprivate.so.4
#7 0x0000003d6b99abd5 in KMMainWidget::qt_metacall () from
/usr/lib64/libkmailprivate.so.4
#8 0x0000003d5e556764 in QMetaObject::activate () from
/usr/lib64/libQtCore.so.4
#9 0x0000003d5e551073 in QObject::event () from /usr/lib64/libQtCore.so.4
#10 0x0000003d5f1828dd in QApplicationPrivate::notify_helper () from
/usr/lib64/libQtGui.so.4
#11 0x0000003d5f18a68a in QApplication::notify () from /usr/lib64/libQtGui.so.4
#12 0x0000003d60404deb in KApplication::notify () from /usr/lib64/libkdeui.so.5
#13 0x0000003d5e542391 in QCoreApplication::notifyInternal () from
/usr/lib64/libQtCore.so.4
#14 0x0000003d5e56e0d6 in ?? () from /usr/lib64/libQtCore.so.4
#15 0x0000003d5e56a83d in ?? () from /usr/lib64/libQtCore.so.4
#16 0x0000003d5a43779b in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#17 0x0000003d5a43af6d in ?? () from /lib64/libglib-2.0.so.0
#18 0x0000003d5a43b12b in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#19 0x0000003d5e56a79f in QEventDispatcherGlib::processEvents () from
/usr/lib64/libQtCore.so.4
#20 0x0000003d5f21328f in ?? () from /usr/lib64/libQtGui.so.4
#21 0x0000003d5e540cb2 in QEventLoop::processEvents () from
/usr/lib64/libQtCore.so.4
#22 0x0000003d5e540e3d in QEventLoop::exec () from /usr/lib64/libQtCore.so.4
#23 0x0000003d5e5432ed in QCoreApplication::exec () from
/usr/lib64/libQtCore.so.4
#24 0x0000000000402b5b in _start ()
______________________________________________________
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
klauncher(3160) KConfigGroup::readXdgListEntry: List entry MimeType in
"/a1/home/danaw/.local/share/applications/mozilla-firefox.desktop" is not
compliant with XDG standard (missing trailing semicolon).
kdeinit4: preparing to launch /usr/bin/firefox
QObject: Do not delete object, 'unnamed', during its event handler!
kdeinit4: preparing to launch
kwin: X Error (error: [DAMAGE+0], request: XDamageDestroy[DAMAGE+2],
resource: 0x1e0eda5)
kdeinit4: preparing to launch
kded(3162): The kwalletd service has been disabled
kded(3162): The kwalletd service has been disabled
kded(3162): The kwalletd service has been disabled
kded(3162): The kwalletd service has been disabled
kded(3162): The kwalletd service has been disabled
kded(3162): The kwalletd service has been disabled
kded(3162): The kwalletd service has been disabled
kded(3162): The kwalletd service has been disabled
kded(3162): The kwalletd service has been disabled
kded(3162): The kwalletd service has been disabled
kded(3162): The kwalletd service has been disabled
kded(3162): The kwalletd service has been disabled
kded(3162): The kwalletd service has been disabled
kded(3162): The kwalletd service has been disabled
kded(3162): The kwalletd service has been disabled
kded(3162): The kwalletd service has been disabled
kded(3162): The kwalletd service has been disabled
kded(3162): The kwalletd service has been disabled
kded(3162): The kwalletd service has been disabled
kded(3162): The kwalletd service has been disabled
kded(3162): The kwalletd service has been disabled
klauncher(3160) KConfigGroup::readXdgListEntry: List entry MimeType in
"/a1/home/danaw/.local/share/applications/mozilla-firefox.desktop" is not
compliant with XDG standard (missing trailing semicolon).
kdeinit4: preparing to launch /usr/bin/firefox
QObject: Do not delete object, 'unnamed', during its event handler!
kwin: X Error (error: [DAMAGE+0], request: XDamageDestroy[DAMAGE+2],
resource: 0x1e0ee6f)
kmail(7455) KMReaderWin::message: Attempt to reference invalid serial number
90932
kmail(7455) KMail::MessageListView::StorageModel::releaseMessage: Trying to
release a message at row 241 that no longer exists in the folder
kmail(7455) KMReaderWin::message: Attempt to reference invalid serial number
90933
kmail(7455) KMReaderWin::message: Attempt to reference invalid serial number
90927
kmail(7455) KMReaderWin::message: Attempt to reference invalid serial number
90930
kmail(7455) KMReaderWin::message: Attempt to reference invalid serial number
90930
kwin: X Error (error: [DAMAGE+0], request: XDamageDestroy[DAMAGE+2],
resource: 0x1e0ef3c)
kmail(7455) KMail::MessageListView::StorageModel::releaseMessage: Trying to
release a message at row 239 that no longer exists in the folder
kmail(7455) KMReaderWin::message: Attempt to reference invalid serial number
90927
do_ypcall: clnt_call: RPC: Unable to receive; errno = Connection refused
kmail(7455) KMReaderWin::message: Attempt to reference invalid serial number
90925
kwin: X Error (error: [DAMAGE+0], request: XDamageDestroy[DAMAGE+2],
resource: 0x1e0ef3f)
kmail(7455) KMail::MessageListView::StorageModel::releaseMessage: Trying to
release a message at row 237 that no longer exists in the folder
*** KMail got signal 11 (Crashing)
QObject: Do not delete object, 'unnamed', during its event handler!
KCrash: Application 'kmail' crashing...
kdeinit4: preparing to launch /usr/libexec/kde4/drkonqi
kwin: X Error (error: [DAMAGE+0], request: XDamageDestroy[DAMAGE+2],
resource: 0x1e0f04b)
kdeinit4: preparing to launch
kded(3162): The kwalletd service has been disabled
kded(3162) KWallet::Wallet::openWallet: Pass a valid window to
KWallet::Wallet::openWallet().
kded(3162): The kwalletd service has been disabled
kded(3162): The kwalletd service has been disabled
kded(3162): The kwalletd service has been disabled
kded(3162): The kwalletd service has been disabled
kded(3162): The kwalletd service has been disabled
kded(3162): The kwalletd service has been disabled
plasma(3201)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(-22,
27)
plasma(3201)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 0)
plasma(3201)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(-22,
27)
plasma(3201)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 0)
QCoreApplication::postEvent: Unexpected null receiver
kdeinit4: preparing to launch
kded(3162): The kwalletd service has been disabled
kded(3162) KWallet::Wallet::openWallet: Pass a valid window to
KWallet::Wallet::openWallet().
kded(3162): The kwalletd service has been disabled
kded(3162): The kwalletd service has been disabled
kded(3162): The kwalletd service has been disabled
kded(3162): The kwalletd service has been disabled
kded(3162): The kwalletd service has been disabled
kded(3162): The kwalletd service has been disabled
QCoreApplication::postEvent: Unexpected null receiver
klauncher(3160) KConfigGroup::readXdgListEntry: List entry MimeType in
"/a1/home/danaw/.local/share/applications/mozilla-firefox.desktop" is not
compliant with XDG standard (missing trailing semicolon).
kdeinit4: preparing to launch /usr/bin/firefox
QGraphicsGridLayout::itemAt: invalid row, column 0, 0
QObject: Do not delete object, 'unnamed', during its event handler!
LoadPlugin: failed to initialize shared library
/usr/java/jdk1.6.0_03/jre/plugin/i386/ns7/libjavaplugin_oji.so
[/usr/java/jdk1.6.0_03/jre/plugin/i386/ns7/libjavaplugin_oji.so: wrong ELF
class: ELFCLASS32]
QGraphicsGridLayout::itemAt: invalid row, column 0, 0
kwin: X Error (error: [DAMAGE+0], request: XDamageDestroy[DAMAGE+2],
resource: 0x1e0f085)
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
that the processevent was managing a timeout event.
It seems that in the same moment I dropped the messages
(concluding the message movement action) a timeout expired
and the routine that manage the timeout hitted
a variable with a wrong value, triggering the qt_assert at #11.
In my opinion that variable was modified by the routine
that move the messages, but the processevent stopped
that routine before its end;
then processevent started the timeout management,
which found the wrong value in the variable and then asserted.
my 2 cents
Tom
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
it will store the passwords in kwallet unless you do not want to use it
(denying its access to kwallet).
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
that text into another new memo, and it reverts to black. Can the formatting
color be kept on paste, please?
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
if he declines he can then manually construct a second (or third...) email
message for each recipient.
Thanks Shlomi, have a happy Independence Day!
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
through all emails (~25.000 and ~4,5 GB). Started from konsole, kmail outputs
lines like:
kmail(6098)/kmail (storage internals) KMFolderMaildir::getDwString:
KDE_fopen(abs_file=
"/usr/oms/Mail/.MailingLists.directory/Andere/cur/1239002674.5913.zKNVK:2,S" ,
"r+") == stream == 0x9ae7668
kmail(6098)/kmail (storage internals) KMFolderMaildir::getDwString:
fclose(mIndexStream = 0x9ae7668 )
kmail(6098)/kmail (storage internals) KMFolderMaildir::getDwString:
KDE_fopen(abs_file=
"/usr/oms/Mail/.MailingLists.directory/Andere/cur/1239009776.5913.15eQ9:2,S" ,
"r+") == stream == 0x9a2c7a0
kmail(6098)/kmail (storage internals) KMFolderMaildir::getDwString:
fclose(mIndexStream = 0x9a2c7a0 )
I already stopped kmail, removed all index files, started again. Kmail than
rebuilds the index files - that's what i expect. after a few minutes pausing,
kmail seems to start again... pausing... starting...etc.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
German, which comes from this .desktop file: plasma-applet-incomingmsg.desktop
That file says that the author is Christian Weilbach
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
Mem). More than Konqueror or Plasma-desktop (about 28000K and 25000K). It seems
a bit too much.
Each time I add a new note, the memory usage grown about 1M.
P.S: I've 25 notes stored on knotes, each note contains very few lines of text.
P.P.S: I'm using Qt 4.5.1 and KDE from trunk r967367
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
do with a message being deleted while it's being downloaded. This isn't a
problem per-se, but if the download is triggered by a request to display it in
the preview pane, I think, then when the preview pane tries to display it, the
message no longer exists.
Is this a possibility?
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
Backtrace:
0: /etc/X11/X(xorg_backtrace+0x37) [0x8136207]
1: /etc/X11/X(xf86SigHandler+0x56) [0x80d1fd6]
2: [0xffffe400]
3: /etc/X11/X(FindGlyphRef+0x13) [0x8172863]
4: /etc/X11/X(FindGlyphByHash+0x3b) [0x8172f8b]
5: /etc/X11/X [0x817fc92]
6: /etc/X11/X [0x8178c03]
7: /etc/X11/X(Dispatch+0x34f) [0x808971f]
8: /etc/X11/X(main+0x39d) [0x806d2fd]
9: /lib/i686/libc.so.6(__libc_start_main+0xe5) [0xb7ad06a5]
10: /etc/X11/X [0x806c7d1]
Fatal server error:
Caught signal 11. Server aborting
Please consult the The X.Org Foundation support
at http://qa.mandriva.com
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional
information.
(II) UnloadModule: "synaptics"
(II) HID 1241:1111: Close
(II) UnloadModule: "evdev"
(II) AT Translated Set 2 keyboard: Close
(II) UnloadModule: "evdev"
(II) Sleep Button (CM): Close
(II) UnloadModule: "evdev"
(II) Video Bus: Close
(II) UnloadModule: "evdev"
(II) Power Button (CM): Close
(II) UnloadModule: "evdev"
(II) Power Button (FF): Close
(II) UnloadModule: "evdev"
(II) UnloadModule: "synaptics"
(II) AIGLX: Suspending AIGLX clients for VT switch
disable LVDS
(II) RADEON(0): RADEONRestoreMemMapRegisters() :
(II) RADEON(0): MC_FB_LOCATION : 0x1fff0000 0xd3ffd000
(II) RADEON(0): MC_AGP_LOCATION : 0x27ff2000
finished PLL2
finished PLL1
Entering Restore TV
Restore TV PLL
Restore TVHV
Restore TV Restarts
Restore Timing Tables
Restore TV standard
Leaving Restore TV
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
(corrupted) while loading the a contact.
It seems you are using Gentoo.
- When this crash appeared ? After some update ?
- Does KAddressBook crashes too ?
Thanks
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
side of Kaddressbook main window.
But if a label address is entered for the Work address for example then it is
displayed instead of the standard address.
Why is the standard address not displayed as well in Kaddressbook?
Note: both work addresses are displayed when selecting 'detailled Style' in the
printing assistant which makes more sense in my opinion.
Trunk, Svn Rev 1016607
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
Attachment, inline and so on.
Its working however in the right-click-on-message-context-menu.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
uses the full width of the window and the Type column is stretched to use the
most space.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
message). This means KMail is compatible only with selected KDE color schemes
-- scheme change (in KDE) can lead to getting dark blue text on dark brown
background. Hardly readable.
My suggestion: instead of using hardcoded values for defaults for colors not
covered by KDE global scheme, "link" internally colors
KDE color -> KMail color
Since color scheme is well polished, this means with each change whole KMail
would change dynamically and correctly. For example such links could be
created:
KDE active -> KMail new
KDE link (not visited) -> KMail unread
This guarantees 100% working colors in KMail.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
I created my 'Helene Duchateau' contact with a display name and exported it as
a Vcard file on my hard drive. When I reimported it somehow the display name
got lost and this is why the sorting is disrupted.
Maybe the 'full name' display radio button should be checked by default to
avoid that.
Trunk, Svn Rev 1030016
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
smtp server, I do not know). In that case, the mail window where I have created
the new email if grayed, apparently waiting for the email to be send. And it
lasts...
In the main window of KMail (which I use inside Kontact), i can temporarily
cancel the sending of the email (in the job queue). I can even "send the unsend
emails" (or something like that), and usually the sending of the email works,
that time.
But the original email window is still here, greyed. The only thing I can do is
to close it, using the close button of the KWin decoration. Then a popup, that
asks if I want to cancel, save the unsend mail in drafts, or forget the unsend
mail. As the mail is already send (remember: I manage to re-send it using
File->Send unsend emails in KMail, I chose to forget it, and the window closes,
but Kontact closes also and crash.
-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6 0x035c9e51 in KMFolderCachedImap::findNewMessages (this=0xa4ee938) at
/usr/src/debug/kdepim-4.3.1/kmail/kmfoldercachedimap.cpp:1399
#7 0x035daca9 in KMFolderCachedImap::uploadNewMessages (this=0xa4ee938) at
/usr/src/debug/kdepim-4.3.1/kmail/kmfoldercachedimap.cpp:1409
#8 0x035da1a2 in KMFolderCachedImap::serverSyncInternal (this=0xa4ee938) at
/usr/src/debug/kdepim-4.3.1/kmail/kmfoldercachedimap.cpp:971
#9 0x035e3100 in KMFolderCachedImap::createNewFolders (this=0xa4ee938) at
/usr/src/debug/kdepim-4.3.1/kmail/kmfoldercachedimap.cpp:1605
#10 0x035d9633 in KMFolderCachedImap::serverSyncInternal (this=0xa4ee938) at
/usr/src/debug/kdepim-4.3.1/kmail/kmfoldercachedimap.cpp:965
#11 0x035e6834 in KMFolderCachedImap::qt_metacall (this=0xa4ee938,
_c=QMetaObject::InvokeMetaMethod, _id=48, _a=0xbfaef468)
at
/usr/src/debug/kdepim-4.3.1/i586-redhat-linux-gnu/kmail/kmfoldercachedimap.moc:209
#12 0x05fc1843 in QMetaObject::activate (sender=0xd49a130,
from_signal_index=10, to_signal_index=10, argv=0xbfaef468) at
kernel/qobject.cpp:3112
#13 0x05fc24a2 in QMetaObject::activate (sender=0xd49a130, m=0x3ae54d0,
local_signal_index=6, argv=0xbfaef468) at kernel/qobject.cpp:3186
#14 0x0370e313 in KMail::FolderJob::result (this=0xd49a130, _t1=0xd49a130) at
/usr/src/debug/kdepim-4.3.1/i586-redhat-linux-gnu/kmail/folderjob.moc:140
#15 0x0370ec47 in KMail::FolderJob::~FolderJob (this=0xd49a130,
__in_chrg=) at
/usr/src/debug/kdepim-4.3.1/kmail/folderjob.cpp:95
#16 0x0370fc20 in KMail::CachedImapJob::~CachedImapJob (this=0xd49a130,
__in_chrg=) at
/usr/src/debug/kdepim-4.3.1/kmail/cachedimapjob.cpp:122
#17 0x0371727e in KMail::CachedImapJob::slotCheckUidValidityResult
(this=0xd49a130, job=0xd777868) at
/usr/src/debug/kdepim-4.3.1/kmail/cachedimapjob.cpp:728
#18 0x03714577 in KMail::CachedImapJob::qt_metacall (this=0xd49a130,
_c=QMetaObject::InvokeMetaMethod, _id=24, _a=0xbfaef6c8)
at
/usr/src/debug/kdepim-4.3.1/i586-redhat-linux-gnu/kmail/cachedimapjob.moc:113
#19 0x05fc1843 in QMetaObject::activate (sender=0xd777868, from_signal_index=7,
to_signal_index=7, argv=0xbfaef6c8) at kernel/qobject.cpp:3112
#20 0x05fc24a2 in QMetaObject::activate (sender=0xd777868, m=0x73b1ee8,
local_signal_index=3, argv=0xbfaef6c8) at kernel/qobject.cpp:3186
#21 0x07219573 in KJob::result (this=0xd777868, _t1=0xd777868) at
/usr/src/debug/kdelibs-4.3.1/i586-redhat-linux-gnu/kdecore/kjob.moc:188
#22 0x07219a19 in KJob::emitResult (this=0xd777868) at
/usr/src/debug/kdelibs-4.3.1/kdecore/jobs/kjob.cpp:304
#23 0x07a2b240 in KIO::SimpleJob::slotFinished (this=0xd777868) at
/usr/src/debug/kdelibs-4.3.1/kio/kio/job.cpp:477
#24 0x07a2b76a in KIO::TransferJob::slotFinished (this=0xd777868) at
/usr/src/debug/kdelibs-4.3.1/kio/kio/job.cpp:948
#25 0x07a29483 in KIO::TransferJob::qt_metacall (this=0xd777868,
_c=QMetaObject::InvokeMetaMethod, _id=47, _a=0xbfaef92c) at
/usr/src/debug/kdelibs-4.3.1/i586-redhat-linux-gnu/kio/jobclasses.moc:343
#26 0x05fc1843 in QMetaObject::activate (sender=0xbb69d50, from_signal_index=8,
to_signal_index=8, argv=0x0) at kernel/qobject.cpp:3112
#27 0x05fc24a2 in QMetaObject::activate (sender=0xbb69d50, m=0x7c0eb04,
local_signal_index=4, argv=0x0) at kernel/qobject.cpp:3186
#28 0x07af6bd7 in KIO::SlaveInterface::finished (this=0xbb69d50) at
/usr/src/debug/kdelibs-4.3.1/i586-redhat-linux-gnu/kio/slaveinterface.moc:165
#29 0x07afaacd in KIO::SlaveInterface::dispatch (this=0xbb69d50, _cmd=104,
rawdata=@0xbfaefac8) at
/usr/src/debug/kdelibs-4.3.1/kio/kio/slaveinterface.cpp:175
#30 0x07af70a3 in KIO::SlaveInterface::dispatch (this=0xbb69d50) at
/usr/src/debug/kdelibs-4.3.1/kio/kio/slaveinterface.cpp:91
#31 0x07ae917a in KIO::Slave::gotInput (this=0xbb69d50) at
/usr/src/debug/kdelibs-4.3.1/kio/kio/slave.cpp:322
#32 0x07aeb573 in KIO::Slave::qt_metacall (this=0xbb69d50,
_c=QMetaObject::InvokeMetaMethod, _id=30, _a=0xbfaefc0c) at
/usr/src/debug/kdelibs-4.3.1/i586-redhat-linux-gnu/kio/slave.moc:76
#33 0x05fc1843 in QMetaObject::activate (sender=0xc818ab0, from_signal_index=4,
to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3112
#34 0x05fc24a2 in QMetaObject::activate (sender=0xc818ab0, m=0x7c0b440,
local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3186
#35 0x079f1ab7 in KIO::Connection::readyRead (this=0xc818ab0) at
/usr/src/debug/kdelibs-4.3.1/i586-redhat-linux-gnu/kio/connection.moc:86
#36 0x079f388e in KIO::ConnectionPrivate::dequeue (this=0xbc20358) at
/usr/src/debug/kdelibs-4.3.1/kio/kio/connection.cpp:82
#37 0x079f39b6 in KIO::Connection::qt_metacall (this=0xc818ab0,
_c=QMetaObject::InvokeMetaMethod, _id=5, _a=0xbe67980) at
/usr/src/debug/kdelibs-4.3.1/i586-redhat-linux-gnu/kio/connection.moc:73
#38 0x05fba46b in QMetaCallEvent::placeMetaCall (this=0xc2b2528,
object=0xc818ab0) at kernel/qobject.cpp:477
#39 0x05fbbbb6 in QObject::event (this=0xc818ab0, e=0xc2b2528) at
kernel/qobject.cpp:1110
#40 0x064a4974 in QApplicationPrivate::notify_helper (this=0x9cb43a8,
receiver=0xc818ab0, e=0xc2b2528) at kernel/qapplication.cpp:4056
#41 0x064ac0e9 in QApplication::notify (this=0xbfaf1934, receiver=0xc818ab0,
e=0xc2b2528) at kernel/qapplication.cpp:3603
#42 0x0758d60a in KApplication::notify (this=0xbfaf1934, receiver=0xc818ab0,
event=0xc2b2528) at
/usr/src/debug/kdelibs-4.3.1/kdeui/kernel/kapplication.cpp:302
#43 0x05fabafb in QCoreApplication::notifyInternal (this=0xbfaf1934,
receiver=0xc818ab0, event=0xc2b2528) at kernel/qcoreapplication.cpp:610
#44 0x05fac722 in QCoreApplication::sendEvent (event=,
receiver=) at kernel/qcoreapplication.h:213
#45 QCoreApplicationPrivate::sendPostedEvents (event=,
receiver=) at kernel/qcoreapplication.cpp:1247
#46 0x05fac8dd in QCoreApplication::sendPostedEvents (receiver=0x0,
event_type=0) at kernel/qcoreapplication.cpp:1140
#47 0x05fd69af in QCoreApplication::sendPostedEvents () at
kernel/qcoreapplication.h:218
#48 postEventSourceDispatch () at kernel/qeventdispatcher_glib.cpp:210
#49 0x02dea308 in g_main_dispatch (context=) at
gmain.c:1824
#50 IA__g_main_context_dispatch (context=) at gmain.c:2377
#51 0x02ded9e0 in g_main_context_iterate (context=0x9ca0e90, block=, dispatch=1, self=0x9cb76b0) at gmain.c:2455
#52 0x02dedb13 in IA__g_main_context_iteration (context=0x9ca0e90, may_block=1)
at gmain.c:2518
#53 0x05fd65dc in QEventDispatcherGlib::processEvents (this=0x9c7fa28, flags={i
= 36}) at kernel/qeventdispatcher_glib.cpp:327
#54 0x06543cb5 in QGuiEventDispatcherGlib::processEvents (this=0x9c7fa28,
flags={i = 36}) at kernel/qguieventdispatcher_glib.cpp:202
#55 0x05faa0c9 in QEventLoop::processEvents (this=0xbfaf04d0, flags={i = 36})
at kernel/qeventloop.cpp:149
#56 0x05faa51a in QEventLoop::exec (this=0xbfaf04d0, flags={i = 0}) at
kernel/qeventloop.cpp:201
#57 0x076257e0 in KWallet::Wallet::openWallet (name=@0xbfaf0564, w=79254584,
ot=KWallet::Wallet::Synchronous) at
/usr/src/debug/kdelibs-4.3.1/kdeui/util/kwallet.cpp:252
#58 0x08276650 in MailTransport::TransportManager::wallet (this=0xa0444a8) at
/usr/src/debug/kdepimlibs-4.3.1/mailtransport/transportmanager.cpp:420
#59 0x0826b0f5 in MailTransport::Transport::readPassword (this=0xa0e4f88) at
/usr/src/debug/kdepimlibs-4.3.1/mailtransport/transport.cpp:245
#60 0x0827565f in MailTransport::TransportManager::loadPasswords
(this=0xa0444a8) at
/usr/src/debug/kdepimlibs-4.3.1/mailtransport/transportmanager.cpp:445
#61 0x0826a7cc in MailTransport::Transport::password (this=0xe074640) at
/usr/src/debug/kdepimlibs-4.3.1/mailtransport/transport.cpp:76
#62 0x0827d607 in MailTransport::SmtpJob::startSmtpJob (this=0xe06cd88) at
/usr/src/debug/kdepimlibs-4.3.1/mailtransport/smtpjob.cpp:159
#63 0x0827e78d in MailTransport::SmtpJob::doStart (this=0xe06cd88) at
/usr/src/debug/kdepimlibs-4.3.1/mailtransport/smtpjob.cpp:114
#64 0x08274348 in MailTransport::TransportJob::start (this=0xe06cd88) at
/usr/src/debug/kdepimlibs-4.3.1/mailtransport/transportjob.cpp:129
#65 0x03535dec in KMSender::doSendMsg (this=0xa26e540) at
/usr/src/debug/kdepim-4.3.1/kmail/kmsender.cpp:592
#66 0x0353743e in KMSender::doSendQueued (this=0xa26e540,
customTransport=@0xbfaf0c50) at
/usr/src/debug/kdepim-4.3.1/kmail/kmsender.cpp:244
#67 0x035338f8 in KMail::MessageSender::sendQueued (transport=, this=) at
/usr/src/debug/kdepim-4.3.1/kmail/messagesender.h:77
#68 KMSender::doSend (transport=, this=) at /usr/src/debug/kdepim-4.3.1/kmail/kmsender.cpp:194
#69 0x034afe03 in KMail::MessageSender::send (method=,
msg=, this=) at
/usr/src/debug/kdepim-4.3.1/kmail/messagesender.h:65
#70 KMComposeWin::slotContinueDoSend (method=, msg=, this=) at
/usr/src/debug/kdepim-4.3.1/kmail/kmcomposewin.cpp:3700
#71 0x034c0500 in KMComposeWin::qt_metacall (this=0xd59f260,
_c=QMetaObject::InvokeMetaMethod, _id=84, _a=0xbfaf0e78) at
/usr/src/debug/kdepim-4.3.1/i586-redhat-linux-gnu/kmail/kmcomposewin.moc:313
#72 0x05fc1843 in QMetaObject::activate (sender=0xd59f260,
from_signal_index=50, to_signal_index=50, argv=0xbfaf0e78) at
kernel/qobject.cpp:3112
#73 0x05fc24a2 in QMetaObject::activate (sender=0xd59f260, m=0x3add12c,
local_signal_index=0, argv=0xbfaf0e78) at kernel/qobject.cpp:3186
#74 0x034933d9 in KMComposeWin::applyChangesDone (this=0xd59f260, _t1=true) at
/usr/src/debug/kdepim-4.3.1/i586-redhat-linux-gnu/kmail/kmcomposewin.moc:331
#75 0x03494961 in KMComposeWin::slotComposerDone (this=0xd59f260, rc=) at /usr/src/debug/kdepim-4.3.1/kmail/kmcomposewin.cpp:2021
#76 0x034c04e3 in KMComposeWin::qt_metacall (this=0xd59f260,
_c=QMetaObject::InvokeMetaMethod, _id=83, _a=0xbfaf0ff8) at
/usr/src/debug/kdepim-4.3.1/i586-redhat-linux-gnu/kmail/kmcomposewin.moc:312
#77 0x05fc1843 in QMetaObject::activate (sender=0xc32cef0, from_signal_index=4,
to_signal_index=4, argv=0xbfaf0ff8) at kernel/qobject.cpp:3112
#78 0x05fc24a2 in QMetaObject::activate (sender=0xc32cef0, m=0x3ae73c4,
local_signal_index=0, argv=0xbfaf0ff8) at kernel/qobject.cpp:3186
#79 0x03761f49 in MessageComposer::done (this=0xc32cef0, _t1=true) at
/usr/src/debug/kdepim-4.3.1/i586-redhat-linux-gnu/kmail/messagecomposer.moc:82
#80 0x03762227 in MessageComposer::emitDone (this=0xc32cef0, ok=48) at
/usr/src/debug/kdepim-4.3.1/kmail/messagecomposer.cpp:417
#81 0x03762398 in MessageComposer::doNextJob (this=0xc32cef0) at
/usr/src/debug/kdepim-4.3.1/kmail/messagecomposer.cpp:393
#82 0x03762518 in MessageComposer::qt_metacall (this=0xc32cef0,
_c=QMetaObject::InvokeMetaMethod, _id=5, _a=0xbfaf113c)
at
/usr/src/debug/kdepim-4.3.1/i586-redhat-linux-gnu/kmail/messagecomposer.moc:70
#83 0x05fc1843 in QMetaObject::activate (sender=0xd5d6c10, from_signal_index=4,
to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3112
#84 0x05fc24a2 in QMetaObject::activate (sender=0xd5d6c10, m=0x609c3c8,
local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3186
#85 0x05fc6957 in QSingleShotTimer::timeout (this=0xd5d6c10) at
.moc/release-shared/qtimer.moc:76
#86 0x05fc6a6c in QSingleShotTimer::timerEvent (this=0xd5d6c10) at
kernel/qtimer.cpp:298
#87 0x05fbb95f in QObject::event (this=0xd5d6c10, e=0xbfaf15d0) at
kernel/qobject.cpp:1074
#88 0x064a4974 in QApplicationPrivate::notify_helper (this=0x9cb43a8,
receiver=0xd5d6c10, e=0xbfaf15d0) at kernel/qapplication.cpp:4056
#89 0x064ac0e9 in QApplication::notify (this=0xbfaf1934, receiver=0xd5d6c10,
e=0xbfaf15d0) at kernel/qapplication.cpp:3603
#90 0x0758d60a in KApplication::notify (this=0xbfaf1934, receiver=0xd5d6c10,
event=0xbfaf15d0) at
/usr/src/debug/kdelibs-4.3.1/kdeui/kernel/kapplication.cpp:302
#91 0x05fabafb in QCoreApplication::notifyInternal (this=0xbfaf1934,
receiver=0xd5d6c10, event=0xbfaf15d0) at kernel/qcoreapplication.cpp:610
#92 0x05fd8d6e in QCoreApplication::sendEvent (event=,
receiver=) at kernel/qcoreapplication.h:213
#93 QTimerInfoList::activateTimers (event=,
receiver=) at kernel/qeventdispatcher_unix.cpp:572
#94 0x05fd6690 in timerSourceDispatch (source=0x9ca1878) at
kernel/qeventdispatcher_glib.cpp:165
#95 0x02dea308 in g_main_dispatch (context=) at
gmain.c:1824
#96 IA__g_main_context_dispatch (context=) at gmain.c:2377
#97 0x02ded9e0 in g_main_context_iterate (context=0x9ca0e90, block=, dispatch=1, self=0x9cb76b0) at gmain.c:2455
#98 0x02dedb13 in IA__g_main_context_iteration (context=0x9ca0e90, may_block=1)
at gmain.c:2518
#99 0x05fd65dc in QEventDispatcherGlib::processEvents (this=0x9c7fa28, flags={i
= 36}) at kernel/qeventdispatcher_glib.cpp:327
#100 0x06543cb5 in QGuiEventDispatcherGlib::processEvents (this=0x9c7fa28,
flags={i = 36}) at kernel/qguieventdispatcher_glib.cpp:202
#101 0x05faa0c9 in QEventLoop::processEvents (this=0xbfaf1894, flags={i = 36})
at kernel/qeventloop.cpp:149
#102 0x05faa51a in QEventLoop::exec (this=0xbfaf1894, flags={i = 0}) at
kernel/qeventloop.cpp:201
#103 0x05fac99f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#104 0x064a47f7 in QApplication::exec () at kernel/qapplication.cpp:3525
#105 0x0804b2e6 in main (argc=1, argv=0xbfaf1b54) at
/usr/src/debug/kdepim-4.3.1/kontact/src/main.cpp:218
Reported using DrKonqi
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
Chicago = 160, New_York = 334
from bug #115763
Oslo = 818, Arctic/Longyearbyen = 483
So my big insight :)
If it is an error it is not an offset error and my next question is what is
TIMEZONES?
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
" I find the e-mail, and then I click on it. The message suddenly turns blank
(unknown sender, no subject, unknown date, no body). Furthermore, if I try to
view the source of the message, I get a widow displaying absolutely nothing."
Exactly same bug seen today, 3.5 years later with Kamil 4.3.2.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
-
What I was doing when the application crashed:
I just have had a new rule in order to filter my email. For this rule, on the
email matching this rule, there is a crash when I apply filters manually.
Kmail don't crash on other rules.
-
I know a little more about the context. When I have added my new filter, i have
created one with the right-click on the message. But after that, I have copied
the sender and add it to an another already existant rule.
An incomplete rule was then staying at the begining of the list of rules.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
"selecting a big folder (13000 mails) crashed kmail"
Backtrace:
-
-- Backtrace:
Application: Kontact (kontact), signal: Aborted
[KCrash Handler]
#5 0x00007f7ead939205 in raise () from /lib/libc.so.6
#6 0x00007f7ead93a723 in abort () from /lib/libc.so.6
#7 0x00007f7eae671295 in qt_message_output (msgType=QtFatalMsg, buf=) at global/qglobal.cpp:2042
#8 0x00007f7eae6713b0 in qFatal (msg=) at
global/qglobal.cpp:2241
#9 0x00007f7e9cf72d23 in
KMail::MessageListView::Core::Model::applyFilterToSubtree (this=0x1503b60,
item=0x2ff41b0, parentIndex=@0x7fff95188890)
at
/var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2/kmail/messagelistview/core/model.cpp:348
#10 0x00007f7e9cf7902e in KMail::MessageListView::Core::Model::setFilter
(this=0x1503b60, filter=)
at
/var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2/kmail/messagelistview/core/model.cpp:340
#11 0x00007f7e9cfa108c in
KMail::MessageListView::Core::Widget::searchTimerFired (this=0x14b87c0)
at
/var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2/kmail/messagelistview/core/widgetbase.cpp:1130
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
anything that would help me in getting this issue solved. Is there some other
log file I could look into?
If not, where inside the code is the part that decides whether I can select a
certificate or not? Then I could add some debug output to track this issue
down.
I've asked this question in #kontact before, and still idle there, if you want
any more input from my side.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
What I was doing when the application crashed:
Trying to open Kontact, has one IMAP account, it crashes immediately. It was
working correctly until I upgraded to the RC.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
It seems I could solve this issue here.
Kadressbook has had an Akonadi-Resource wich points to my Adressbookfile. As I
changed this at KDE-Resources in Systemsettings to "file-Resource" pointing to
the same file.
This had to effects:
- Kontact doesn't need 20minutes to start anymore,
- Kontact closes and starts without segfault
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
'Name Surname' part whereas it should only have displayed the 'email address'
part.
Trunk, Svn Rev 1043144
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
an invalid signature, even if the sender using KMail did not change anything in
his GnuPG configuration, because:
1) There are clients which complain when the declared hash algorithm does not
match the hash algorithm that has been used. If I remember correctly I
encountered this problem with Sylpheed (and this is how I got aware of this bug
in the first place).
2) If a mail is both, encrypted and signed, GnuPG by default should use the
hash algorithm that is preferred according to the recipient's key preferences.
So if the recipient prefers SHA256 according to his key SHA256 should be used.
However, KMail will still declare it as SHA1.
With people moving away from SHA1, I think the priority of this bug should be
increased.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
What I was doing when the application crashed:
As I was loosing records in schedule & addressbook ( file sync ) I hit the save
button on addressbook to save it.
And launch save schedules on the akonadi in korganizer.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
'Name Surname' part whereas it should only have displayed the 'email address'
part.
Is it possible to do anything about this eventhough it comes from a user
mistake?
I guess it could happen to other users.
Trunk, Svn Rev 1044595
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
This happened immediately after I filtered three messages out of the queue
after creating the filter to use for the purpose. Two messages were left in the
stack, both of which will be deleted ASAP.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
I tried to modify a contact wich is saved in an Akonadi resource (syncronised
with google). And after few minutes, I can't save any modification on a
contact. And finally, Kontact crashed during closing.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
the
text properly in some contexts. Can somebody who has worked on composer co=
de
provide some insight?
--=20
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=3Demail
------- You are receiving this mail because: -------
You are the assignee for the bug.=
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
After starting kmail i have heavy harddisk activity, i think kmail try to
reindexing all emails. In my lokal Mail-Folders i have over 11GB mails, so
kmail needs >30min for indexing. If I had not the time to wait, i try to close
kmail and than it crashed sometimes doing this.
---
Backtrace:
---
Application: Kontact (kontact), signal: Segmentation fault
The current source language is "auto; currently c".
[KCrash Handler]
#5 QBasicAtomicInt::operator!= (this=0x3e1ab40, job=0x3e38610) at
/usr/include/qt4/QtCore/qbasicatomic.h:69
#6 QMap::detach (this=0x3e1ab40,
job=0x3e38610) at /usr/include/qt4/QtCore/qmap.h:172
#7 QMap::find (this=0x3e1ab40,
job=0x3e38610) at /usr/include/qt4/QtCore/qmap.h:565
#8 KMail::ImapAccountBase::findJob (this=0x3e1ab40, job=0x3e38610) at
../../kmail/imapaccountbase.h:180
#9 KMail::ListJob::slotListResult (this=0x3e1ab40, job=0x3e38610) at
../../kmail/listjob.cpp:166
#10 0x00007f9ab9689c53 in KMail::ListJob::qt_metacall (this=0x3e1ab40,
_c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff3e9f36d0)
at ./listjob.moc:77
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
After starting kmail i have heavy harddisk activity, i think kmail try to
reindexing all emails. In my lokal Mail-Folders i have over 11GB mails, so
kmail needs >30min for indexing. If I had not the time to wait, i try to close
kmail and than it crashed sometimes doing this.
---
Backtrace:
---
Application: Kontact (kontact), signal: Segmentation fault
The current source language is "auto; currently c".
[KCrash Handler]
#5 QBasicAtomicInt::operator!= (this=0x3e1ab40, job=0x3e38610) at
/usr/include/qt4/QtCore/qbasicatomic.h:69
#6 QMap::detach (this=0x3e1ab40,
job=0x3e38610) at /usr/include/qt4/QtCore/qmap.h:172
#7 QMap::find (this=0x3e1ab40,
job=0x3e38610) at /usr/include/qt4/QtCore/qmap.h:565
#8 KMail::ImapAccountBase::findJob (this=0x3e1ab40, job=0x3e38610) at
../../kmail/imapaccountbase.h:180
#9 KMail::ListJob::slotListResult (this=0x3e1ab40, job=0x3e38610) at
../../kmail/listjob.cpp:166
#10 0x00007f9ab9689c53 in KMail::ListJob::qt_metacall (this=0x3e1ab40,
_c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff3e9f36d0)
at ./listjob.moc:77
--- Comment #12 from Dario Andres 2009-11-16 01:32:24 ---
*** Bug 214329 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.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
i was just looking at some mail thats on the gmail server and when i clicked to
retrieve the mail kmail suddenly crashed with a segment fault ,, this has
happened before with other actions like attaching photos to emails etc etc and
always is a segment fault ,this time i got the proper debugging packages to a
proper report
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
i was just looking at some mail thats on the gmail server and when i clicked to
retrieve the mail kmail suddenly crashed with a segment fault ,, this has
happened before with other actions like attaching photos to emails etc etc and
always is a segment fault ,this time i got the proper debugging packages to a
proper report
--- Comment #33 from Dario Andres 2009-11-16 01:35:30 ---
*** Bug 214333 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.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
KMail crashed when I choose to open a pdf file attachet to an email. I choose
to open the file with okular.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
----
Thread 1 (Thread 0xb77d5700 (LWP 3244)):
[KCrash Handler]
#6 QBasicAtomicInt::ref (this=0xa061450, job=0xa062260, uds=...) at
/usr/include/qt4/QtCore/qatomic_i386.h:120
#7 QString (this=0xa061450, job=0xa062260, uds=...) at
/usr/include/qt4/QtCore/qstring.h:712
#8 jobData (this=0xa061450, job=0xa062260, uds=...) at
../../kmail/imapaccountbase.h:146
#9 QMap::node_create (this=0xa061450,
job=0xa062260, uds=...) at /usr/include/qt4/QtCore/qmap.h:421
#10 QMap::detach_helper
(this=0xa061450, job=0xa062260, uds=...) at /usr/include/qt4/QtCore/qmap.h:708
#11 QMap::detach (this=0xa061450,
job=0xa062260, uds=...) at /usr/include/qt4/QtCore/qmap.h:172
#12 QMap::find (this=0xa061450,
job=0xa062260, uds=...) at /usr/include/qt4/QtCore/qmap.h:565
#13 KMail::ImapAccountBase::findJob (this=0xa061450, job=0xa062260, uds=...) at
../../kmail/imapaccountbase.h:180
#14 KMail::ListJob::slotListEntries (this=0xa061450, job=0xa062260, uds=...) at
../../kmail/listjob.cpp:189
#15 0xb436ff86 in KMail::ListJob::qt_metacall (this=0xa061450,
_c=QMetaObject::InvokeMetaMethod, _id=14, _a=0xbfe17494) at ./listjob.moc:78
#16 0x0717d263 in QMetaObject::activate (sender=0xa062260,
from_signal_index=40, to_signal_index=40, argv=0xbfe17494) at
kernel/qobject.cpp:3113
#17 0x0717dec2 in QMetaObject::activate (sender=0xa062260, m=0x3e9d3a0,
local_signal_index=0, argv=0xbfe17494) at kernel/qobject.cpp:3187
#18 0x03ce53a9 in KIO::ListJob::entries (this=0xa062260, _t1=0xa062260,
_t2=...) at ./jobclasses.moc:781
#19 0x03cf40ab in KIO::ListJobPrivate::slotListEntries (this=0xa061eb8,
list=...) at ../../kio/kio/job.cpp:2333
#20 0x03cf4458 in KIO::ListJob::qt_metacall (this=0xa062260,
_c=QMetaObject::InvokeMetaMethod, _id=46, _a=0xbfe17698) at
./jobclasses.moc:767
...
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
I just set up several filtering rules in Kmail on an IMAP account, then i
started applying them all on 3000 messages, it crashed after treating 1000 of
them.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
from being inline, just not there. Send as attachment does work.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
I accidentally closed Kontact on the window button (not File=>Quit) and wanted
to reopen it by clicking on the korgac reminder systray icon. I thought that it
was supposed to work that way.
BTW: Kontact doesn't quit all the time when using File=>Quit so you have to
kill a stale process to be able to open it again.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
I accidentally closed Kontact on the window button (not File=>Quit) and wanted
to reopen it by clicking on the korgac reminder systray icon. I thought that it
was supposed to work that way.
BTW: Kontact doesn't quit all the time when using File=>Quit so you have to
kill a stale process to be able to open it again.
--- Comment #42 from Dario Andres 2009-11-21 14:43:00 ---
*** Bug 215512 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.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
While reading the emails, and tried to open an attachment (the type does not
really matter), KMail crashes.
Sometimes I've noticed, that it happens more often if the mail is not fully
downloaded.
IMAP + TLS (SSL) on GMAIL
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
While reading the emails, and tried to open an attachment (the type does not
really matter), KMail crashes.
Sometimes I've noticed, that it happens more often if the mail is not fully
downloaded.
IMAP + TLS (SSL) on GMAIL
--- Comment #63 from Dario Andres 2009-11-25 14:12:46 ---
*** Bug 216000 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.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
Move subfolder and kmail crashes while in progress.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
Move subfolder and kmail crashes while in progress.
--- Comment #14 from Dario Andres 2009-11-25 14:20:25 ---
*** Bug 215928 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.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
when saving contact in Kontact failed to save to a file on my desktop.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
when saving contact in Kontact failed to save to a file on my desktop.
--- Comment #19 from Dario Andres 2009-11-25 14:47:11 ---
*** Bug 215874 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 on the CC list for the bug.
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
I was creating a new MetaContact in Kopete....
Right click on exsisting Kopete Entry, edit, Select Kontact, nothing sows up.
Click create contact and bang....
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
-----
1: Content-type: text/html;
2: charset=ISO-8859-1
3: Status: R
4: X-Status: N
5: X-KMail-EncryptionState:
6: X-KMail-SignatureState:
7: X-KMail-MDN-Sent:
8:
9: Content-Transfer-Encoding: 7bit
10:
11: Subject: My Comic Page 11/29/2009
-----
at line 8 above there is an empty line. This is the mailformats way of saying
headers section ended, body begins. Hence everything below is by definition the
body of the email. So the rendering in KMail is correct.
However if it is KMail that inserts the blank line (#8) then there is an issue
in KMail, but not the one you reported here. To find out which we would need to
see the mail source before it is processed by KMail. If the blank line is
present then it's not a bug in KMail but if the blank line is missing then it's
a bug in KMail.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
I was trying to load a message from my GMail account's All Mail folder via
IMAP. I had previously selected a message in the same thread to view in the
preview pane, and that never loaded, then I set KMail to show the preview pane
next to the message list, then tried to select the message after which KMail
segfaulted.
---
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
kmail crashes when closing application using the X icon
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
I applied 3 EMail Account and enabled catch mails after start.
But some some information of my accounts seems to be wrong (wrong passwords).
Now when I start KMail it crashes.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
kontact left running over night. On trying to send an email (by hitting the
send button in the composer window), the window is fadded and the email to be
sent is added to the outbox, but does not get sent. I hit the x button to
close the email and was presented with a 'save draft' 'discard' 'cancel' dialog
window. I selected cancel and then kontact crashed. Upon restarting kontact,
I was given the 'kontact already running' warning window to which I responded
'start anyway'. The email was still in the out box and sent with out error in
the restarted kontact.
This has happened before (once ever other week), but I can not reliabley
reproduce it. I have a hunch that it is related to kwallet interactions. In
all the cases that it has crashed I have first started kopete and opened
kwallet. The wallet is still open when I attempted to send the email.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
Kmail crashed when i tried to change the status of a read mail to new
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
when selecting and marking some imap folders read kmail crashed. It was only
after marking a few folders read that the crash appeared.
Part of the backtrace:
---
-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6 0xb6fa88e9 in KIO::Slave::slaveProtocol() () from /usr/lib/libkio.so.5
#7 0xb6fa3449 in ?? () from /usr/lib/libkio.so.5
#8 0xb6fa3806 in KIO::Scheduler::assignJobToSlave(KIO::Slave*,
KIO::SimpleJob*) () from /usr/lib/libkio.so.5
#9 0xb10413c7 in KMail::SearchJob::searchSingleMessage (this=0x98115c0) at
/usr/src/debug/kdepim-4.3.3/kmail/searchjob.cpp:394
#10 0xb0fa1214 in KMail::FolderJob::start (this=0x0) at
/usr/src/debug/kdepim-4.3.3/kmail/folderjob.cpp:106
#11 0xb0e416e6 in KMFolderImap::search (this=0x86dd180, pattern=0x84188a0,
serNum=644019) at /usr/src/debug/kdepim-4.3.3/kmail/kmfolderimap.cpp:2435
#12 0xb0f9dcc7 in KMFolderSearch::propagateHeaderChanged (this=0x86b3070,
aFolder=0x86d3ce8, idx=1049) at
/usr/src/debug/kdepim-4.3.3/kmail/kmfoldersearch.cpp:1167
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
My internet connection lag (disconnect for a minute) and kontact show error
window. After showing this error window it crashes. ( I don't remember what
wxactly is in error window, but it is something about timeout exceed).
Thread 1 (Thread 0x7f5c5d38d750 (LWP 32749)):
[KCrash Handler]
#5 0x00007f5c5cb10b61 in KPIM::ProgressItem::setComplete() () from
/usr/lib64/libkdepim.so.4
#6 0x00007f5c464b7495 in KMail::ImapAccountBase::removeJob (this=0xb3fda0,
it=...) at /usr/src/debug/kdepim-4.3.3/kmail/imapaccountbase.cpp:1370
#7 0x00007f5c464db69a in KMFolderImap::slotListFolderResult (this=0xbc8570,
job=0xdf4230) at /usr/src/debug/kdepim-4.3.3/kmail/kmfolderimap.cpp:1314
#8 0x00007f5c464e74b5 in KMFolderImap::qt_metacall (this=0xbc8570,
_c=InvokeMetaMethod, _id=, _a=0x7fff0f5d6e10) at
/usr/src/debug/kdepim-4.3.3/build/kmail/kmfolderimap.moc:182
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
I add a new contact in my kontact.
It works with akanodi and synchronize with google.
When I want to closed the software, it crash...
At this time, my connection lag.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
I add a new contact in my kontact.
It works with akanodi and synchronize with google.
When I want to closed the software, it crash...
At this time, my connection lag.
--- Comment #22 from Dario Andres 2009-12-11 13:03:16 ---
*** Bug 218233 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 on the CC list for the bug.
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
Kontact crashes when going to next folder in Kmail
It happened only once (I have used this version every day for one month), all I
was doing was reading emails.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
After searching through the advanced search dialog, I sorted the results by
date and double-clicked on one of the matches to open it. Kontact crashed.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
Kontact crashes when deleting a lot of files one-by-one in the inbox of
googlemail. The same happens if I start kmail alone...
Most time deleting works perfect but after about 45 or 50 mails the program
crashes.
---
Updated complete backtrace:
---
[KCrash Handler]
#6 KMMsgBase::storage (this=0xa0e48c8) at ../../kmail/kmmsgbase.cpp:140
#7 0xb461b8e2 in KMail::ImapJob::slotGetMessageResult (this=0x9aacd20,
job=0x9defa60) at ../../kmail/imapjob.cpp:373
#8 0xb462060f in KMail::ImapJob::qt_metacall (this=0x9aacd20,
_c=QMetaObject::InvokeMetaMethod, _id=12, _a=0xbff87d98) at ./imapjob.moc:82
#9 0x05eb4263 in QMetaObject::activate (sender=0x9defa60, from_signal_index=7,
to_signal_index=7, argv=0xbff87d98) at kernel/qobject.cpp:3113
#10 0x05eb4ec2 in QMetaObject::activate (sender=0x9defa60, m=0x468d68,
local_signal_index=3, argv=0xbff87d98) at kernel/qobject.cpp:3187
#11 0x00302fe3 in KJob::result (this=0x9defa60, _t1=0x9defa60) at
./kjob.moc:188
#12 0x00303469 in KJob::emitResult (this=0x9defa60) at
../../kdecore/jobs/kjob.cpp:304
#13 0x015cd660 in KIO::SimpleJob::slotFinished (this=0x9defa60) at
../../kio/kio/job.cpp:477
#14 0x015cdb7a in KIO::TransferJob::slotFinished (this=0x9defa60) at
../../kio/kio/job.cpp:948
#15 0x015cb8a3 in KIO::TransferJob::qt_metacall (this=0x9defa60,
_c=QMetaObject::InvokeMetaMethod, _id=47, _a=0xbff87ffc) at
./jobclasses.moc:343
...
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
-- Information about the crash:
After I disabled everything related to korganizer in kontact and started
korganizer from the system tray icon, kontact immediately crashed. Korganizer
didn't start.
After a restart of kontact, everything works as expected.
Updated backtrace:
---
[KCrash Handler]
#6 0x00fdaae0 in KontactInterface::Plugin::part (this=0x9b83be8) at
../../kontactinterface/plugin.cpp:190
#7 0x02257e0a in KOrganizerUniqueAppHandler::newInstance (this=0xa5678c8) at
../../../../kontact/plugins/korganizer/korg_uniqueapp.cpp:33
#8 0x00fdc769 in KontactInterface::UniqueAppHandler::newInstance
(this=0xa5678c8, asn_id=..., args=...) at
../../kontactinterface/uniqueapphandler.cpp:129
#9 0x00fdc7f4 in KontactInterface::UniqueAppHandler::qt_metacall
(this=0xa5678c8, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfd99d6c) at
./uniqueapphandler.moc:79
...
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
-- Information about the crash:
After I disabled everything related to korganizer in kontact and started
korganizer from the system tray icon, kontact immediately crashed. Korganizer
didn't start.
After a restart of kontact, everything works as expected.
Updated backtrace:
---
[KCrash Handler]
#6 0x00fdaae0 in KontactInterface::Plugin::part (this=0x9b83be8) at
../../kontactinterface/plugin.cpp:190
#7 0x02257e0a in KOrganizerUniqueAppHandler::newInstance (this=0xa5678c8) at
../../../../kontact/plugins/korganizer/korg_uniqueapp.cpp:33
#8 0x00fdc769 in KontactInterface::UniqueAppHandler::newInstance
(this=0xa5678c8, asn_id=..., args=...) at
../../kontactinterface/uniqueapphandler.cpp:129
#9 0x00fdc7f4 in KontactInterface::UniqueAppHandler::qt_metacall
(this=0xa5678c8, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfd99d6c) at
./uniqueapphandler.moc:79
...
--- Comment #50 from Dario Andres 2009-12-15 13:28:16 ---
*** Bug 218747 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.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
After closing Kontact I receive several messages indicating that the one or
more resource files used by Akonadi are being used by another application and
cannot be closed out.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
Kmail crashed after closing the preference dialog and selected a mail in the
inbox folder for display. The preference dialog was used to change the layout
and hide the favorite folders list.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
Kmail crashed after closing the preference dialog and selected a mail in the
inbox folder for display. The preference dialog was used to change the layout
and hide the favorite folders list.
--- Comment #39 from Dario Andres 2009-12-15 14:13:54 ---
*** Bug 218645 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.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
Dec 16 18:32:03 histor2 imapd: Connection, ip=[::ffff:192.168.0.10]
Dec 16 18:32:10 histor2 imapd: LOGIN, user=jmho, ip=[::ffff:192.168.0.10],
port=[57451], protocol=IMAP
Dec 16 18:33:01 histor2 sa-exim[5819]: Removed 0 of 0 greylist tuplets in 0
seconds
Dec 16 18:33:01 histor2 sa-exim[5819]: Removed 0 of 0 greylist directories in 0
seconds
Dec 16 19:33:01 histor2 sa-exim[6098]: Removed 0 of 0 greylist tuplets in 0
seconds
Dec 16 19:33:01 histor2 sa-exim[6098]: Removed 0 of 0 greylist directories in 0
seconds
Dec 16 20:33:01 histor2 sa-exim[7070]: Removed 0 of 0 greylist tuplets in 0
seconds
Dec 16 20:33:01 histor2 sa-exim[7070]: Removed 0 of 0 greylist directories in 0
seconds
Dec 16 21:04:25 histor2 imapd: Unexpected SSL connection shutdown.
Dec 16 21:04:25 histor2 imapd: DISCONNECTED, user=jmho,
ip=[::ffff:192.168.0.10], headers=39342529, body=110248, rcvd=573563,
sent=58279899, time=91
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
I was selecting emails for deletion from an IMAP folder and it
has crashed. The folder was using SSL and not TLS.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
I was selecting emails for deletion from an IMAP folder and it
has crashed. The folder was using SSL and not TLS.
--- Comment #114 from Dario Andres 2009-12-17 00:43:14 ---
*** Bug 218953 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.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
I was in the inbox, teaching kmail what is ham or spam on my new account.
I clicked on the first message, clicked the "ham" button in the toolbar, kmail
moves to the next message, I click on "ham", etc.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
I can reproduce this crash 100% when accessing folders with 64000+ messages.
(courier-imap server running on Debian Lenny)
With smaller folders (25000 or less messages) no crash.
Updated (4.4trunk) backtrace:
---
#5 KPIM::ProgressItem::setComplete (this=0x6c64657463657078) at
/home/jmho/kde-devel/kdesvn/kdepim/libkdepim/progressmanager.cpp:52
#6 0x00007f2ba9879f65 in KMail::ImapAccountBase::removeJob (this=0x1e2f9f0,
it=...) at /home/jmho/kde-devel/kdesvn/kdepim/kmail/imapaccountbase.cpp:1375
#7 0x00007f2ba98a4036 in KMFolderImap::slotListFolderResult (this=0x28970a0,
job=) at
/home/jmho/kde-devel/kdesvn/kdepim/kmail/kmfolderimap.cpp:1305
#8 0x00007f2ba98aae25 in KMFolderImap::qt_metacall (this=0x28970a0,
_c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fffe44dbfd0)
at /home/jmho/kde-devel/kdesvn/build/kdepim/kmail/kmfolderimap.moc:188
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
mail-related operation, so I don't know if the appearance configuration could
be related.
Thanks
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
le
in size.
--=20
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=3Demail
------- You are receiving this mail because: -------
You are the assignee for the bug.=
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
"Use the innermost non-empty identity completly instead of merging the group,
account and global identity in case of empty fields."
So this is the intended behaviour
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
kaddressbook on its own the resources are shown at the bottom-left and there is
no "recently used" resource. If I click on the "+" to add one there no such
resource either.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
kontact -> settings -> popup notes -> network
[v] accept incoming notes
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
send a note to your host -> Error: "Connection refused"
== Notes ==
If you quit from kontact and use "Configure knotes" from systray knotes icon,
you can correct the problem and receive notes. So i guess it is a bug in
kontact.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
I had just sent a message and saved it from the Sent folder in Kmail to the
file browser in Ubuntu Linux. I then clicked on the same message in the Sent
folder a second time. KDE Kontact then crashed.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
In Kontact, i want to delete 3 attached files of one message (minder memory).
The first one it is Ok, but the second one give an error
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
When adding a new event, upon choosing a WebDav calendar to which the event is
to be added, korganizer crashes. This happens about 50% of the time.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
Kontact crashed in the background when I was doing other tasks.
KOrganizer was the active component, and it was set on month view. I use
Akonadi to connect to a Google Calendar as my primary calendar, and my address
book birthdays and a read-only ical from an internet source (meetup.com) as my
only other calendars.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
Kmail crash randomly when filtering mail on one of my imap accounts. This
happens most the time on first start/check, but even when I manually apply all
filter to the rest of the mails in the inbox. A few crashes later I could
filter all mails and then kmail seems to stable for the rest of the day.
Updated backtrace:
---
Thread 1 (Thread 0x7fe12e56f840 (LWP 16135)):
[KCrash Handler]
#5 KMail::ActionScheduler::actionMessage (this=0x2298330, res=) at /usr/src/debug/kdepim-4.3.4/kmail/actionscheduler.cpp:675
#6 0x00007fe12029b4a9 in KMail::ActionScheduler::filterMessage
(this=0x2298330) at /usr/src/debug/kdepim-4.3.4/kmail/actionscheduler.cpp:648
#7 0x00007fe12029b864 in KMail::ActionScheduler::qt_metacall (this=0x2298330,
_c=InvokeMetaMethod, _id=17, _a=0x7fffcbf4f740)
at
/usr/src/debug/kdepim-4.3.4/x86_64-redhat-linux-gnu/kmail/actionscheduler.moc:124
#8 0x000000370835408c in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib64/libQtCore.so.4
...
Bug 219926 also contains some config files and a testcase email.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
Kmail crash randomly when filtering mail on one of my imap accounts. This
happens most the time on first start/check, but even when I manually apply all
filter to the rest of the mails in the inbox. A few crashes later I could
filter all mails and then kmail seems to stable for the rest of the day.
Updated backtrace:
---
Thread 1 (Thread 0x7fe12e56f840 (LWP 16135)):
[KCrash Handler]
#5 KMail::ActionScheduler::actionMessage (this=0x2298330, res=) at /usr/src/debug/kdepim-4.3.4/kmail/actionscheduler.cpp:675
#6 0x00007fe12029b4a9 in KMail::ActionScheduler::filterMessage
(this=0x2298330) at /usr/src/debug/kdepim-4.3.4/kmail/actionscheduler.cpp:648
#7 0x00007fe12029b864 in KMail::ActionScheduler::qt_metacall (this=0x2298330,
_c=InvokeMetaMethod, _id=17, _a=0x7fffcbf4f740)
at
/usr/src/debug/kdepim-4.3.4/x86_64-redhat-linux-gnu/kmail/actionscheduler.moc:124
#8 0x000000370835408c in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib64/libQtCore.so.4
...
Bug 219926 also contains some config files and a testcase email.
--- Comment #22 from Dario Andres 2009-12-24 14:20:48 ---
*** Bug 219926 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.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
I was in the todo view, and wanted to look for a specific group. I have clicked
on the search textbox, typed "Uv" - and kontact has crashed.
I am not sure if this pattern matches anything at all, probably the todo I was
looking for was deleted - it was not visible, so even if it exists, the filters
have hidden it.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
Kontact (Kmail) crashes (segmentation fault) when the wireless network
connection drops and Kontact doesn't know the connection is being
re-negotiated.
--- Comment #52 from Dario Andres 2009-12-24 20:14:33 ---
*** Bug 219979 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.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
Kontact (Kmail) crashes (segmentation fault) when the wireless network
connection drops and Kontact doesn't know the connection is being
re-negotiated.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
Kmail crash when I open email in a research.
Notice that the email that is to be open is located in a virtual folder came
from a Thunderbird import.
This bug is reproducable.
-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6 QString (this=0xf9609d8, s=..., number=false) at
../../include/QtCore/../../src/corelib/tools/qstring.h:711
#7 QTextStreamPrivate::putString (this=0xf9609d8, s=..., number=false) at
io/qtextstream.cpp:933
#8 0xb65b518b in QTextStream::operator<< (this=0xc9238c0, string=...) at
io/qtextstream.cpp:2511
#9 0xb0b7f198 in QDebug::operator<< (this=0xaee4318, it=0x0) at
/usr/include/qt4/QtCore/qdebug.h:108
#10 KMail::MessageListView::Core::View::setCurrentMessageItem (this=0xaee4318,
it=0x0) at ../../kmail/messagelistview/core/view.cpp:768
#11 0xb0b28b24 in KMail::MessageListView::Widget::activateMessageItemByMsgBase
(this=0xaf37c00, msg=0xedae460) at ../../kmail/messagelistview/widget.cpp:276
#12 0xb0b1effb in KMail::MessageListView::Pane::activateMessage
(this=0xa732ad8, msg=0xedae460) at ../../kmail/messagelistview/pane.cpp:604
#13 0xb09c115a in KMMainWidget::slotSelectMessage (this=0xa5107b0,
msg=0xedae460) at ../../kmail/kmmainwidget.cpp:3150
#14 0xb0920a33 in KMail::SearchWindow::slotShowMsg (this=0xb9bec78,
item=0xe7fb5e8) at ../../kmail/searchwindow.cpp:726
#15 0xb0920f6e in KMail::SearchWindow::qt_metacall (this=0xb9bec78,
_c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbff2eee4) at
./searchwindow.moc:128
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
I was doing maintenance on names and addresses. trying to standardize.
verifying that all names are "last name" "coma" "first name". process seems to
wrok for upto 5 contacts (sometimes less) than slows down to 30 seconds to 3
minutes or crashes. shutting down kontact after 5 changes and then restarting
keepps process fast. There has to be a better way.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
I am able to reproduce it (at least one of 3 attempts is successful - makes
KMail crashed). How to reproduce it: launch KMail, click on New..., write an
e-mail address into a recipient field, close only the main KMail window (keep
the message open), launch KMail and quickly click on an inbox folder (I have to
open the inbox folder of my first account.). When it opens, KMail crashes.
-- Backtrace:
[KCrash Handler]
#5 0x00007fdda99906d6 in KMail::ISubject::notify (this=0x1569d10) at
../../kmail/isubject.cpp:30
#6 0x00007fdda967beec in KMMessage::updateBodyPart (this=0x1569c40,
partSpecifier=) at ../../kmail/kmmessage.cpp:3235
#7 0x00007fdda9964bca in KMail::ImapJob::slotGetMessageResult (this=0x2118610,
job=) at ../../kmail/imapjob.cpp:435
#8 0x00007fdda996904b in KMail::ImapJob::qt_metacall (this=0x2118610,
_c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff114cc5a0)
at ./imapjob.moc:82
...
--- Comment #42 from Dario Andres 2009-12-31 15:10:32 ---
*** Bug 220802 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.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
I am able to reproduce it (at least one of 3 attempts is successful - makes
KMail crashed). How to reproduce it: launch KMail, click on New..., write an
e-mail address into a recipient field, close only the main KMail window (keep
the message open), launch KMail and quickly click on an inbox folder (I have to
open the inbox folder of my first account.). When it opens, KMail crashes.
-- Backtrace:
[KCrash Handler]
#5 0x00007fdda99906d6 in KMail::ISubject::notify (this=0x1569d10) at
../../kmail/isubject.cpp:30
#6 0x00007fdda967beec in KMMessage::updateBodyPart (this=0x1569c40,
partSpecifier=) at ../../kmail/kmmessage.cpp:3235
#7 0x00007fdda9964bca in KMail::ImapJob::slotGetMessageResult (this=0x2118610,
job=) at ../../kmail/imapjob.cpp:435
#8 0x00007fdda996904b in KMail::ImapJob::qt_metacall (this=0x2118610,
_c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff114cc5a0)
at ./imapjob.moc:82
...
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
The text of that line is shown in the detail view when selecting that contact,
but when I like to edit it, the ROLE is nowhere shown so I can't modify it.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
Version of the application: 4.3.2
[KCrash Handler]
#6 0xb06f1c70 in KMKernel::config () at
/usr/src/debug/kdepim-4.3.2/kmail/kmkernel.cpp:2154
#7 0xb06f2c29 in KMKernel::slotRunBackgroundTasks (this=0x82e1998) at
/usr/src/debug/kdepim-4.3.2/kmail/kmkernel.cpp:2207
#8 0xb07043e8 in KMKernel::qt_metacall (this=0x82e1998,
_c=QMetaObject::InvokeMetaMethod, _id=40, _a=0xbfc8fd68) at
/usr/src/debug/kdepim-4.3.2/build/kmail/kmkernel.moc:226
...
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
Kontact crashed sometimes reload of old session
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
What I was doing when the application crashed:
After resuming from suspend to ram I clicked to exit kmail and it crashed on
exit. This has happened a few times and also when resuming from suspend to
disk.
-- Updated Backtrace:
...
Thread 1 (Thread 0xb347d700 (LWP 1935)):
[KCrash Handler]
#6 KMFilterMgr::deref (this=0x0, force=false) at
/usr/src/debug/kdepim-4.3.4/kmail/kmfiltermgr.cpp:365
#7 0xb6c60262 in KMail::AccountManager::processNextCheck (this=0x80a5718,
_newMail=248) at /usr/src/debug/kdepim-4.3.4/kmail/accountmanager.cpp:175
#8 0xb6c61926 in KMail::AccountManager::qt_metacall (this=0x80a5718,
_c=InvokeMetaMethod, _id=12, _a=0xbf9956d4) at
/usr/src/debug/kdepim-4.3.4/build/kmail/accountmanager.moc:96
#9 0xb6884864 in QMetaObject::activate(QObject*, int, int, void**) () from
/usr/lib/libQtCore.so.4
#10 0xb6885585 in QMetaObject::activate(QObject*, QMetaObject const*, int,
void**) () from /usr/lib/libQtCore.so.4
#11 0xb6bcad75 in KMAccount::finishedCheck (this=0x81e6700, _t1=false,
_t2=CheckOK) at /usr/src/debug/kdepim-4.3.4/build/kmail/kmaccount.moc:162
#12 0xb6bcb78a in KMAccount::checkDone (this=0x81e6700, newmail=false,
status=CheckOK) at /usr/src/debug/kdepim-4.3.4/kmail/kmaccount.cpp:507
#13 0xb6cdfb07 in KMAcctImap::killAllJobs (this=0x81e6700,
disconnectSlave=true) at /usr/src/debug/kdepim-4.3.4/kmail/kmacctimap.cpp:204
#14 0xb6cdfc41 in KMAcctImap::~KMAcctImap (this=0x81e6700, __in_chrg=) at /usr/src/debug/kdepim-4.3.4/kmail/kmacctimap.cpp:86
#15 0xb6c5f2d6 in qDeleteAll::const_iterator> (end=, begin=) at
/usr/include/QtCore/qalgorithms.h:350
#16 qDeleteAll (end=, begin=) at /usr/include/QtCore/qalgorithms.h:358
#17 KMail::AccountManager::~AccountManager (end=,
begin=) at
/usr/src/debug/kdepim-4.3.4/kmail/accountmanager.cpp:39
#18 0xb6d4e7af in KMKernel::cleanup (this=0xbf995920) at
/usr/src/debug/kdepim-4.3.4/kmail/kmkernel.cpp:1731
#19 0x0804a73c in main (argc=3, argv=0xbf995b74) at
/usr/src/debug/kdepim-4.3.4/kmail/main.cpp:148
---
Several of the other duplicate reports are related to exiting KMail too
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
-- Information about the crash:
I use KMail as a stand-alone application.
What I did was:
I removed a mail from an IMAP mailbox (gmail).
The mail was already gone from the message list view and the next mail was
selected (an approval mail from KDE's mailing list daemon). The new mail was
then marked as "read" and its content about to be shown in the message view.
Before the mail content was shown, KMail crashed.
-- Backtrace:
#6 QAbstractItemView::d_func (this=3D0x7) at itemviews/qabstractitemview.h=
:353
#7 QAbstractItemView::model (this=3D0x7) at itemviews/qabstractitemview.cp=
p:669
#8 0xb585cf5c in QTreeWidgetItem::executePendingSort (this=3D0x9f34718) at
itemviews/qtreewidget.cpp:2189
#9 0xb6c8eda5 in QTreeWidgetItem::indexOfChild (this=3D0x9f39520,
parent=3D0x9f34718, node=3D0x9ff7ad0, description=3D..., mimetype=3D..., en=
coding=3D...,
size=3D0, revertOrder=3Dfalse)
at /usr/include/qt4/QtGui/qtreewidget.h:251
#10 KMMimePartTreeItem (this=3D0x9f39520, parent=3D0x9f34718, node=3D0x9ff7=
ad0,
description=3D..., mimetype=3D..., encoding=3D..., size=3D0, revertOrder=3D=
false)
at /home/fs/kdesvn/kdepim/kmail/kmmimeparttree.cpp:385
#11 0xb6cd8e8a in partNode::fillMimePartTree (this=3D0x9ff7ad0,
parentItem=3D0x9f34718, mimePartTree=3D0x0, labelDescr=3D..., labelCntType=
=3D...,
labelEncoding=3D..., size=3D0, revertOrder=3D)
at /home/fs/kdesvn/kdepim/kmail/partNode.cpp:549
#12 0xb6cc5efd in KMail::ObjectTreeParser::insertAndParseNewChildNode
(this=3D0xbf8a9670, startNode=3D..., content=3D0xb5f87ea0 "", cntDesc=3D0xb=
6fc0aa2
"encapsulated message", append=3D,=20
addToTextualContent=3Dfalse) at
/home/fs/kdesvn/kdepim/kmail/objecttreeparser.cpp:232
#13 0xb6cca1d9 in KMail::ObjectTreeParser::processMessageRfc822Subtype
(this=3D0xbf8a9670, node=3D0xa130768) at
/home/fs/kdesvn/kdepim/kmail/objecttreeparser.cpp:1582
#14 0xb6cd348b in process (this=3D0xa0479b0, otp=3D0xbf8a9670, node=3D0xa13=
0768,
result=3D...) at /home/fs/kdesvn/kdepim/kmail/bodypartformatter.cpp:116
#15 0xb6cc553b in KMail::ObjectTreeParser::parseObjectTree (this=3D0xbf8a96=
70,
node=3D0xa130768) at /home/fs/kdesvn/kdepim/kmail/objecttreeparser.cpp:318
#16 0xb6cc58a7 in KMail::ObjectTreeParser::stdChildHandling (this=3D0xbf8a9=
88c,
child=3D0x9fb1248) at /home/fs/kdesvn/kdepim/kmail/objecttreeparser.cpp:1278
#17 0xb6cc5ca1 in KMail::ObjectTreeParser::processMultiPartMixedSubtype
(this=3D0xbf8a988c, node=3D0x9f396b0) at
/home/fs/kdesvn/kdepim/kmail/objecttreeparser.cpp:1291
#18 0xb6cd344b in process (this=3D0x9dcbcc0, otp=3D0xbf8a988c, node=3D0x9f3=
96b0,
result=3D...) at /home/fs/kdesvn/kdepim/kmail/bodypartformatter.cpp:118
#19 0xb6cc553b in KMail::ObjectTreeParser::parseObjectTree (this=3D0xbf8a98=
8c,
node=3D0x9f396b0) at /home/fs/kdesvn/kdepim/kmail/objecttreeparser.cpp:318
#20 0xb6b25d71 in KMReaderWin::parseMsg (this=3D0x923eff0, aMsg=3D0xa1e02e8=
) at
/home/fs/kdesvn/kdepim/kmail/kmreaderwin.cpp:1610
#21 0xb6b19a43 in KMReaderWin::displayMessage (this=3D0x923eff0) at
/home/fs/kdesvn/kdepim/kmail/kmreaderwin.cpp:1534
#22 0xb6b19c2d in KMReaderWin::updateReaderWin (this=3D0x923eff0) at
/home/fs/kdesvn/kdepim/kmail/kmreaderwin.cpp:1477
#23 0xb6b1a530 in KMReaderWin::update (this=3D0x923eff0, observable=3D0xa1e=
0358) at
/home/fs/kdesvn/kdepim/kmail/kmreaderwin.cpp:903
#24 0xb6d737c2 in KMail::ISubject::notify (this=3D0xa1e0358) at
/home/fs/kdesvn/kdepim/kmail/isubject.cpp:33
#25 0xb6a231a2 in KMMessage::updateBodyPart (this=3D0xa1e02e8, partSpecifie=
r=3D...,
data=3D...) at /home/fs/kdesvn/kdepim/kmail/kmmessage.cpp:3185
#26 0xb6d483a0 in KMail::ImapJob::slotGetMessageResult (this=3D0x926e2f0,
job=3D0xa023e98) at /home/fs/kdesvn/kdepim/kmail/imapjob.cpp:435
#27 0xb6d4a2ef in KMail::ImapJob::qt_metacall (this=3D0x926e2f0,
_c=3DQMetaObject::InvokeMetaMethod, _id=3D12, _a=3D0xbf8a9e68) at
/home/fs/kdesvn/build/kdepim/kmail/imapjob.moc:88
...
--=20
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=3Demail
------- You are receiving this mail because: -------
You are the assignee for the bug.=
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
don't use it. Maybe let's close it is as worksforme if it didn't happen for
you, and I will reopen it again, if the issue occurs again?
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
KMail crashes when deleting more than 16000+ messages
[KCrash Handler]
#6 0xb44e46bc in KMMoveCommand (this=0xf4851b0, destFolder=0x0, msgList=...)
at ../../kmail/kmcommands.cpp:2010
#7 0xb451fc3b in KMMainWidget::moveMessageSet (this=0x932aef8, set=0x110184e0,
destination=0x0, confirmOnDeletion=true) at ../../kmail/kmmainwidget.cpp:1730
#8 0xb4520379 in KMMainWidget::slotDeleteMsg (this=0x932aef8,
confirmDelete=true) at ../../kmail/kmmainwidget.cpp:1804
#9 0xb4533345 in KMMainWidget::qt_metacall (this=0x932aef8,
_c=QMetaObject::InvokeMetaMethod, _id=68, _a=0xbf878288) at
./kmmainwidget.moc:415
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
---
I don't know whether this is reproducible. I did this:
1. Add a new IMAP account (this account has dozens of folders and tens or
maybe a hundred thousand messages)
2. While kmail was reading message information, I opened the settings dialog
3. Changed folder list to "short", press "apply"
4. Changed folder list back to "long", press "apply"
5. Crash
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
button. The RSS feed url was autofilled from the clipboard. After continuing,
Kontact crashed. The url in question was:
http://www.worldcommunitygrid.org/about_us/displayNews.do?rss=1&filterCategory=1_0
-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[Current thread is 1 (Thread 0xb7820700 (LWP 4787))]
Thread 14 (Thread 0xae4e2b70 (LWP 4808)):
#0 0x00927422 in __kernel_vsyscall ()
#1 0x0324f142 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib/tls/i686/cmov/libpthread.so.0
#2 0x00da67e4 in pthread_cond_timedwait () from /lib/tls/i686/cmov/libc.so.6
#3 0x027c09ff in ?? () from /usr/lib/libxine.so.1
#4 0x0324a80e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#5 0x00d997ee in clone () from /lib/tls/i686/cmov/libc.so.6
Thread 13 (Thread 0xadce1b70 (LWP 4809)):
#0 0x009fde7a in __i686.get_pc_thunk.bx () from /usr/lib/libQtCore.so.4
#1 0x00b2c31d in socketNotifierSourceCheck (source=0x8e87360) at
kernel/qeventdispatcher_glib.cpp:79
#2 0x019f3cd1 in g_main_context_check () from /lib/libglib-2.0.so.0
#3 0x019f447c in ?? () from /lib/libglib-2.0.so.0
#4 0x019f4863 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#5 0x00b2c067 in QEventDispatcherGlib::processEvents (this=0xa340360,
flags=...) at kernel/qeventdispatcher_glib.cpp:329
#6 0x00affc79 in QEventLoop::processEvents (this=0xadce12b4, flags=) at
kernel/qeventloop.cpp:149
#7 0x00b000ca in QEventLoop::exec (this=0xadce12b4, flags=...) at
kernel/qeventloop.cpp:201
#8 0x00a0db73 in QThread::exec (this=0xa3402f8) at thread/qthread.cpp:487
#9 0x0263920a in ?? () from /usr/lib/qt4/plugins/phonon_backend/phonon_xine.so
#10 0x00a10e32 in QThreadPrivate::start (arg=0xa3402f8) at
thread/qthread_unix.cpp:188
#11 0x0324a80e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#12 0x00d997ee in clone () from /lib/tls/i686/cmov/libc.so.6
Thread 12 (Thread 0xa94dfb70 (LWP 4815)):
#0 0x00927422 in __kernel_vsyscall ()
#1 0x00d8bba6 in poll () from /lib/tls/i686/cmov/libc.so.6
#2 0x03964c3b in ?? () from /usr/lib/xine/plugins/1.26/xineplug_ao_out_alsa.so
#3 0x0324a80e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#4 0x00d997ee in clone () from /lib/tls/i686/cmov/libc.so.6
Thread 11 (Thread 0xa8cdeb70 (LWP 4816)):
#0 0x00927422 in __kernel_vsyscall ()
#1 0x0324ee15 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/tls/i686/cmov/libpthread.so.0
#2 0x00da678d in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3 0x027d15ee in ?? () from /usr/lib/libxine.so.1
#4 0x0324a80e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#5 0x00d997ee in clone () from /lib/tls/i686/cmov/libc.so.6
Thread 10 (Thread 0xa84ddb70 (LWP 4817)):
#0 0x00927422 in __kernel_vsyscall ()
#1 0x00d92981 in select () from /lib/tls/i686/cmov/libc.so.6
#2 0x027e9be0 in xine_usec_sleep () from /usr/lib/libxine.so.1
#3 0x027ce011 in ?? () from /usr/lib/libxine.so.1
#4 0x0324a80e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#5 0x00d997ee in clone () from /lib/tls/i686/cmov/libc.so.6
Thread 9 (Thread 0xacb16b70 (LWP 4830)):
#0 0x00927422 in __kernel_vsyscall ()
#1 0x0324f142 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib/tls/i686/cmov/libpthread.so.0
#2 0x00da67e4 in pthread_cond_timedwait () from /lib/tls/i686/cmov/libc.so.6
#3 0x027c09ff in ?? () from /usr/lib/libxine.so.1
#4 0x0324a80e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#5 0x00d997ee in clone () from /lib/tls/i686/cmov/libc.so.6
Thread 8 (Thread 0xac148b70 (LWP 4836)):
#0 0x00927422 in __kernel_vsyscall ()
#1 0x00d8bba6 in poll () from /lib/tls/i686/cmov/libc.so.6
#2 0x03964c3b in ?? () from /usr/lib/xine/plugins/1.26/xineplug_ao_out_alsa.so
#3 0x0324a80e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#4 0x00d997ee in clone () from /lib/tls/i686/cmov/libc.so.6
Thread 7 (Thread 0xab947b70 (LWP 4837)):
#0 0x00927422 in __kernel_vsyscall ()
#1 0x0324ee15 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/tls/i686/cmov/libpthread.so.0
#2 0x00da678d in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3 0x027d15ee in ?? () from /usr/lib/libxine.so.1
#4 0x0324a80e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#5 0x00d997ee in clone () from /lib/tls/i686/cmov/libc.so.6
Thread 6 (Thread 0xaacb3b70 (LWP 4838)):
#0 0x00927422 in __kernel_vsyscall ()
#1 0x00d92981 in select () from /lib/tls/i686/cmov/libc.so.6
#2 0x027e9be0 in xine_usec_sleep () from /usr/lib/libxine.so.1
#3 0x027ce011 in ?? () from /usr/lib/libxine.so.1
#4 0x0324a80e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#5 0x00d997ee in clone () from /lib/tls/i686/cmov/libc.so.6
Thread 5 (Thread 0xaa0a7b70 (LWP 4851)):
#0 0x00927422 in __kernel_vsyscall ()
#1 0x0324f142 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib/tls/i686/cmov/libpthread.so.0
#2 0x00da67e4 in pthread_cond_timedwait () from /lib/tls/i686/cmov/libc.so.6
#3 0x027c09ff in ?? () from /usr/lib/libxine.so.1
#4 0x0324a80e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#5 0x00d997ee in clone () from /lib/tls/i686/cmov/libc.so.6
Thread 4 (Thread 0xa7cdcb70 (LWP 4857)):
#0 0x00927422 in __kernel_vsyscall ()
#1 0x00d8bba6 in poll () from /lib/tls/i686/cmov/libc.so.6
#2 0x03964c3b in ?? () from /usr/lib/xine/plugins/1.26/xineplug_ao_out_alsa.so
#3 0x0324a80e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#4 0x00d997ee in clone () from /lib/tls/i686/cmov/libc.so.6
Thread 3 (Thread 0xa74dbb70 (LWP 4858)):
#0 0x00927422 in __kernel_vsyscall ()
#1 0x0324ee15 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/tls/i686/cmov/libpthread.so.0
#2 0x00da678d in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3 0x027d15ee in ?? () from /usr/lib/libxine.so.1
#4 0x0324a80e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#5 0x00d997ee in clone () from /lib/tls/i686/cmov/libc.so.6
Thread 2 (Thread 0xa2cd9b70 (LWP 4859)):
#0 0x00927422 in __kernel_vsyscall ()
#1 0x00d92981 in select () from /lib/tls/i686/cmov/libc.so.6
#2 0x027e9be0 in xine_usec_sleep () from /usr/lib/libxine.so.1
#3 0x027ce011 in ?? () from /usr/lib/libxine.so.1
#4 0x0324a80e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#5 0x00d997ee in clone () from /lib/tls/i686/cmov/libc.so.6
Thread 1 (Thread 0xb7820700 (LWP 4787)):
[KCrash Handler]
#6 QListData::size (this=0x0, node=0xb551c18, after=0x0) at
/usr/include/qt4/QtCore/qlist.h:87
#7 QList::indexOf (this=0x0, node=0xb551c18, after=0x0)
at /usr/include/qt4/QtCore/qlist.h:633
#8 Akregator::Folder::insertChild (this=0x0, node=0xb551c18, after=0x0) at
../../../akregator/src/folder.cpp:179
#9 0x03bd0a3b in Akregator::CreateFeedCommand::Private::doCreate
(this=0xb4b3a20) at ../../../akregator/src/createfeedcommand.cpp:123
#10 0x03bd0cb4 in Akregator::CreateFeedCommand::qt_metacall (this=0xb4b59f0,
_c=QMetaObject::InvokeMetaMethod, _id=7, _a=0xbf93bb5c) at
./createfeedcommand.moc:66
#11 0x00b17263 in QMetaObject::activate (sender=0xb4b4918, from_signal_index=4,
to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113
#12 0x00b17ec2 in QMetaObject::activate (sender=0xb4b4918, m=0xbf1908,
local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187
#13 0x00b1c387 in QSingleShotTimer::timeout (this=0xb4b4918) at
.moc/release-shared/qtimer.moc:76
#14 0x00b1c49c in QSingleShotTimer::timerEvent (this=0xb4b4918) at
kernel/qtimer.cpp:298
#15 0x00b113bf in QObject::event (this=0xb4b4918, e=0xbf93bff0) at
kernel/qobject.cpp:1075
#16 0x0102cf54 in QApplicationPrivate::notify_helper (this=0x8ea5038,
receiver=0xb4b4918, e=0xbf93bff0) at kernel/qapplication.cpp:4056
#17 0x0103467c in QApplication::notify (this=0xbf93c354, receiver=0xb4b4918,
e=0xbf93bff0) at kernel/qapplication.cpp:3603
#18 0x002e2bfa in KApplication::notify (this=0xbf93c354, receiver=0xb4b4918,
event=0xbf93bff0) at ../../kdeui/kernel/kapplication.cpp:302
#19 0x00b016cb in QCoreApplication::notifyInternal (this=0xbf93c354,
receiver=0xb4b4918, event=0xbf93bff0) at kernel/qcoreapplication.cpp:610
#20 0x00b2e7ce in QCoreApplication::sendEvent (this=0x8e93714) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#21 QTimerInfoList::activateTimers (this=0x8e93714) at
kernel/qeventdispatcher_unix.cpp:572
#22 0x00b2c0e0 in timerSourceDispatch (source=0x8e936e0) at
kernel/qeventdispatcher_glib.cpp:165
#23 0x019f0e88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#24 0x019f4730 in ?? () from /lib/libglib-2.0.so.0
#25 0x019f4863 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#26 0x00b2c02c in QEventDispatcherGlib::processEvents (this=0x8e6c9f8,
flags=...) at kernel/qeventdispatcher_glib.cpp:327
#27 0x010cdbe5 in QGuiEventDispatcherGlib::processEvents (this=0x8e6c9f8,
flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#28 0x00affc79 in QEventLoop::processEvents (this=0xbf93c2b4, flags=) at
kernel/qeventloop.cpp:149
#29 0x00b000ca in QEventLoop::exec (this=0xbf93c2b4, flags=...) at
kernel/qeventloop.cpp:201
#30 0x00b0253f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#31 0x0102cdd7 in QApplication::exec () at kernel/qapplication.cpp:3525
#32 0x0804b4e6 in main (argc=1, argv=0xbf93c574) at
../../../kontact/src/main.cpp:218
Reported using DrKonqi
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
-- Information about the crash:
Kmail often crashes slightly after startup when I select an imap folder.
Restarting the application sometimes helps but often leads to a crash again.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
-- Information about the crash:
When click on a mail in the mail-list, which is HTML-formatted, Kontact cra=
shes
every time. Kontact crashes not at every HTML-Mail, only a special one.
The crash can be reproduced every time.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
-- Information about the crash:
I have open kmail, go to IMAP folder Drafts, select for view first unread
message from drafts (Created from another computer) and kmail crashes
momentally.
I try this operation four times and see the crash every time.
--=20
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=3Demail
------- You are receiving this mail because: -------
You are the assignee for the bug.=
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
-- What I was doing when the application crashed:
Kontact crashes upon trying to view my feeds. I cannot run Akregator as a
stand alone application.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
From bogus@does.not.exist.com Wed Apr 17 12:44:40 2019
From: bogus@does.not.exist.com ()
Date: Wed, 17 Apr 2019 11:44:40 -0000
Subject: No subject
Message-ID:
but dbus-daemon will be using 99% CPU. Only solution is to kill kmail. Not
clear what causes the freeze.
This is what gdb said kmail was doing last time this happened:
(gdb) bt
#0 0x0000003e6e6d4db3 in *__GI___poll (fds=,
nfds=, timeout=9998)
at ../sysdeps/unix/sysv/linux/poll.c:87
#1 0x0000003e7023aecc in g_main_context_poll (n_fds=,
fds=, priority=,
timeout=, context=)
at gmain.c:2768
#2 g_main_context_iterate (n_fds=,
fds=, priority=,
timeout=, context=)
at gmain.c:2450
#3 0x0000003e7023b20a in IA__g_main_context_iteration (context=0x1ddf120,
may_block=1) at gmain.c:2518
#4 0x000000315f78f243 in QEventDispatcherGlib::processEvents (this=0x1d9bf00,
flags=) at kernel/qeventdispatcher_glib.cpp:412
#5 0x00000031602592ae in QGuiEventDispatcherGlib::processEvents (this=
0x3567190, flags=)
at kernel/qguieventdispatcher_glib.cpp:204
#6 0x000000315f764852 in QEventLoop::processEvents (
this=, flags={i = 37}) at kernel/qeventloop.cpp:149
#7 0x000000315f764c2c in QEventLoop::exec (this=0x7fff98e34f00, flags={i = 1})
at kernel/qeventloop.cpp:201
#8 0x0000003162af9d56 in KJob::exec (this=0x6311a80)
at /usr/src/debug/kdelibs-4.3.90/kdecore/jobs/kjob.cpp:204
#9 0x00007f6f5094e23f in Kleo::KeyResolver::lookupContactPreferences (
this=0x64b6400, address=@0x7fff98e352a0)
at /usr/src/debug/kdepim-4.3.90/kmail/keyresolver.cpp:1741
#10 0x00007f6f5094fe1e in Kleo::KeyResolver::getEncryptionItems (
this=, addresses=)
at /usr/src/debug/kdepim-4.3.90/kmail/keyresolver.cpp:935
#11 0x00007f6f50950307 in Kleo::KeyResolver::setPrimaryRecipients (
this=0x64b6400, addresses=@0x270e)
at /usr/src/debug/kdepim-4.3.90/kmail/keyresolver.cpp:923
#12 0x00007f6f5093fd3b in MessageComposer::adjustCryptFlags (this=0x4854730)
at /usr/src/debug/kdepim-4.3.90/kmail/messagecomposer.cpp:736
#13 0x00007f6f509348b8 in MessageComposer::slotDoNextJob (this=0x4854730)
at /usr/src/debug/kdepim-4.3.90/kmail/messagecomposer.cpp:435
#14 0x00007f6f50934991 in MessageComposer::qt_metacall (this=0x4854730,
_c=QMetaObject::InvokeMetaMethod, _id=,
_a=0x7fff98e35920)
at
/usr/src/debug/kdepim-4.3.90/x86_64-redhat-linux-gnu/kmail/messagecomposer.moc:76
#15 0x000000315f778dcf in QMetaObject::activate (sender=0x6cb1990,
m=, local_signal_index=,
argv=0xffffffffffffffff) at kernel/qobject.cpp:3275
#16 0x000000315f78048f in QSingleShotTimer::timerEvent (this=0x6cb1990)
at kernel/qtimer.cpp:308
#17 0x000000315f775a2e in QObject::event (this=0x6cb1990, e=0x7fff98e36080)
at kernel/qobject.cpp:1212
#18 0x00000031601ab9cc in QApplicationPrivate::notify_helper (this=0x1dd5c90,
receiver=0x6cb1990, e=0x7fff98e36080) at kernel/qapplication.cpp:4298
#19 0x00000031601b1efb in QApplication::notify (this=0x7fff98e37910,
receiver=0x6cb1990, e=0x7fff98e36080) at kernel/qapplication.cpp:4181
---Type to continue, or q to quit---
#20 0x000000316141d9d6 in KApplication::notify (this=0x7fff98e37910,
receiver=0x6cb1990, event=0x7fff98e36080)
at /usr/src/debug/kdelibs-4.3.90/kdeui/kernel/kapplication.cpp:302
#21 0x000000315f765f1c in QCoreApplication::notifyInternal (this=
0x7fff98e37910, receiver=0x6cb1990, event=0x7fff98e36080)
at kernel/qcoreapplication.cpp:704
#22 0x000000315f792952 in QCoreApplication::sendEvent (
event=, receiver=)
at kernel/qcoreapplication.h:215
#23 QTimerInfoList::activateTimers (event=,
receiver=) at kernel/qeventdispatcher_unix.cpp:603
#24 0x000000315f78f578 in timerSourceDispatch (source=)
at kernel/qeventdispatcher_glib.cpp:184
#25 idleTimerSourceDispatch (source=)
at kernel/qeventdispatcher_glib.cpp:231
#26 0x0000003e7023790e in g_main_dispatch (context=)
at gmain.c:1824
#27 IA__g_main_context_dispatch (context=) at gmain.c:2377
#28 0x0000003e7023b0e8 in g_main_context_iterate (context=0x1ddf120,
block=, dispatch=,
self=) at gmain.c:2455
#29 0x0000003e7023b20a in IA__g_main_context_iteration (context=0x1ddf120,
may_block=1) at gmain.c:2518
#30 0x000000315f78f243 in QEventDispatcherGlib::processEvents (this=0x1d9bf00,
flags=