[Bug 225325] Crash when trying to open a PDF attachment
https://bugs.kde.org/show_bug.cgi?id=225325 Oliver Putz regna...@web.de changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||regna...@web.de Resolution||DUPLICATE --- Comment #2 from Oliver Putz Regnaron web de 2010-02-02 23:48:39 --- Marking as duplicate as asked for by reporter *** This bug has been marked as a duplicate of bug 136145 *** -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 136145] Crash when saving some (but not all) IMAP attachments at once
https://bugs.kde.org/show_bug.cgi?id=136145 Oliver Putz regna...@web.de changed: What|Removed |Added CC||o.kannibal...@gmail.com --- Comment #78 from Oliver Putz Regnaron web de 2010-02-02 23:48:39 --- *** Bug 225325 has been marked as a duplicate of this bug. *** -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 156319] Seemingly random KMail crash
https://bugs.kde.org/show_bug.cgi?id=156319 --- Comment #6 from Oliver Putz Regnaron web de 2009-08-03 09:53:07 --- Ups, sorry for the late reply. Apparently I completely missed the first message from Michael... At any rate: The problem with confirming that the fix fixed the problem is that I was never able to reliably reproduce this crash at will to begin with. So I'd suggest we close this as (supposedly) fixed, and if I encounter a crash with a similar backtrace to the original one in the future (so far kmail seems to have stabilized quite a bit), I just reopen this bugreport... -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 169236] Crash after creating new dIMAP account
https://bugs.kde.org/show_bug.cgi?id=169236 Oliver Putz regna...@web.de changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME | --- Comment #2 from Oliver Putz Regnaron web de 2009-06-02 22:30:14 --- I think I saw this one surface once again... Still haven't found a reliable way to reproduce it though... What I did: 1) Set up the personal account and mailserver (IMAP) 2) Checked mail via CTRL+L 3) Entered password 4) Kontact (kmail) from KDE-4.2.3 crashed with the backtrace below [Thread debugging using libthread_db enabled] [New Thread 0x7fec52255750 (LWP 10087)] [New Thread 0x426e5950 (LWP 10114)] [KCrash handler] #5 0x01498640 in ?? () #6 0x7fec3dbccf2a in KMail::ImapAccountBase::makeConnection ( this=0x14d6a80) at /var/tmp/portage/kde-base/kmail-4.2.3-r1/work/kmail-4.2.3/kmail/imapaccountbase.cpp:336 #7 0x7fec3db08569 in AccountsPageReceivingTab::save ( this=value optimized out) at /var/tmp/portage/kde-base/kmail-4.2.3-r1/work/kmail-4.2.3/kmail/configuredialog.cpp:1196 #8 0x7fec3db16eb7 in ConfigModuleWithTabs::save (this=0x14a1910) at /var/tmp/portage/kde-base/kmail-4.2.3-r1/work/kmail-4.2.3/kmail/configuredialog_p.cpp:323 #9 0x7fec49739ef0 in KCModuleProxy::save (this=value optimized out) at /var/tmp/portage/kde-base/kdelibs-4.2.3/work/kdelibs-4.2.3/kutils/kcmoduleproxy.cpp:276 #10 0x7fec4973702c in KCMultiDialogPrivate::apply ( this=value optimized out) at /var/tmp/portage/kde-base/kdelibs-4.2.3/work/kdelibs-4.2.3/kutils/kcmultidialog.cpp:192 #11 0x7fec49738629 in KCMultiDialog::qt_metacall (this=0x146e1c0, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff5a2a4140) at /var/tmp/portage/kde-base/kdelibs-4.2.3/work/kdelibs-4.2.3_build/kutils/kcmultidialog.moc:86 #12 0x7fec3db0e77a in ConfigureDialog::qt_metacall (this=0x14d6a80, _c=1512717520, _id=0, _a=0x7fff5a2a3ba0) at /var/tmp/portage/kde-base/kmail-4.2.3-r1/work/kmail-4.2.3_build/kmail/configuredialog.moc:67 #13 0x7fec4caa0900 in QMetaObject::activate (sender=0x146e1c0, from_signal_index=value optimized out, to_signal_index=42, argv=0x7fff5a2a3ba0) at kernel/qobject.cpp:3025 #14 0x7fec4e6fc601 in KDialog::slotButtonClicked (this=0x146e1c0, button=8) at /var/tmp/portage/kde-base/kdelibs-4.2.3/work/kdelibs-4.2.3/kdeui/dialogs/kdialog.cpp:847 #15 0x7fec4e6fde50 in KDialog::qt_metacall (this=0x146e1c0, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff5a2a4370) at /var/tmp/portage/kde-base/kdelibs-4.2.3/work/kdelibs-4.2.3_build/kdeui/kdialog.moc:181 #16 0x7fec4e7778b2 in KPageDialog::qt_metacall (this=0x14d6a80, _c=1512717520, _id=0, _a=0x7fff5a2a3ba0) at /var/tmp/portage/kde-base/kdelibs-4.2.3/work/kdelibs-4.2.3_build/kdeui/kpagedialog.moc:63 #17 0x7fec497385c6 in KCMultiDialog::qt_metacall (this=0x14d6a80, _c=1512717520, _id=0, _a=0x7fff5a2a3ba0) at /var/tmp/portage/kde-base/kdelibs-4.2.3/work/kdelibs-4.2.3_build/kutils/kcmultidialog.moc:77 #18 0x7fec3db0e77a in ConfigureDialog::qt_metacall (this=0x14d6a80, _c=1512717520, _id=0, _a=0x7fff5a2a3ba0) at /var/tmp/portage/kde-base/kmail-4.2.3-r1/work/kmail-4.2.3_build/kmail/configuredialog.moc:67 #19 0x7fec4caa0900 in QMetaObject::activate (sender=0x1471308, from_signal_index=value optimized out, to_signal_index=4, argv=0x7fff5a2a3ba0) at kernel/qobject.cpp:3025 #20 0x7fec4caa415e in QSignalMapper::mapped (this=0x14d6a80, _t1=8) at .moc/debug-shared/moc_qsignalmapper.cpp:93 #21 0x7fec4caa4200 in QSignalMapper::map (this=0x1471308, sender=0x147f9b0) at kernel/qsignalmapper.cpp:277 #22 0x7fec4caa55c0 in QSignalMapper::qt_metacall (this=0x1471308, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff5a2a44f0) at .moc/debug-shared/moc_qsignalmapper.cpp:80 #23 0x7fec4caa0900 in QMetaObject::activate (sender=0x147f9b0, from_signal_index=value optimized out, to_signal_index=30, argv=0x7fff5a2a3ba0) at kernel/qobject.cpp:3025 #24 0x7fec4da809e7 in QAbstractButton::clicked (this=0x14d6a80, _t1=false) at .moc/debug-shared/moc_qabstractbutton.cpp:185 #25 0x7fec4d8245eb in QAbstractButtonPrivate::emitClicked (this=0x147ddd0) at widgets/qabstractbutton.cpp:544 #26 0x7fec4d825f82 in QAbstractButtonPrivate::click (this=0x147ddd0) at widgets/qabstractbutton.cpp:537 #27 0x7fec4d8261b5 in QAbstractButton::mouseReleaseEvent (this=0x147f9b0, e=0x7fff5a2a4e10) at widgets/qabstractbutton.cpp:1116 #28 0x7fec4d582674 in QWidget::event (this=0x147f9b0, event=0x7fff5a2a4e10) at kernel/qwidget.cpp:7169 #29 0x7fec4d52fa2d in QApplicationPrivate::notify_helper (this=0x62ea80, receiver=0x147f9b0
[Bug 171157] when answering mails adressed to my second email address, kget puts my first email adress in the CC field
https://bugs.kde.org/show_bug.cgi?id=171157 Oliver Putz regna...@web.de changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |INVALID --- Comment #3 from Oliver Putz Regnaron web de 2009-04-15 22:00:29 --- Hi! I was just going to write that I can still reproduce the problem. However, as embarrassing as it is, I just found out that what I described as a bug was a feature! (I just now realized that the described behavior only happens when I reply to a mail by hitting a... Just that a isn't the shortcut for a simple reply, but for a reply all... [which have the same behavior if you get mails addressed to the email address you configured in KMail]) Biig sorry for the noise this report created... -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 176529] kmail crashes when clicking on a mail account
http://bugs.kde.org/show_bug.cgi?id=176529 Oliver Putz Regnaron web de changed: What|Removed |Added AssignedTo|[EMAIL PROTECTED] |kdepim-bugs@kde.org --- Comment #5 from Oliver Putz Regnaron web de 2008-12-01 20:40:47 --- I cannot reproduce, but the backtrace should be good enough now and its also reproducibly by the reporter, so reassigning -- Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 146994] Crash after quiting Kopete (changed presence info)
http://bugs.kde.org/show_bug.cgi?id=146994 Oliver Putz Regnaron web de changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Comment #5 from Oliver Putz Regnaron web de 2008-11-29 18:16:53 --- @Fremir Hernandez Diaz: Your backtrace is unrelated to the problem discussed here. What you experienced most likely was bug #172011 -- Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 175826] The application KMix (kmix) crashed and caused the signal 6 (SIGABRT).
http://bugs.kde.org/show_bug.cgi?id=175826 Oliver Putz Regnaron web de changed: What|Removed |Added CC||[EMAIL PROTECTED] Status|UNCONFIRMED |RESOLVED Component|general |general Product|kontact |kmix Resolution||DUPLICATE --- Comment #1 from Oliver Putz Regnaron web de 2008-11-23 19:28:32 --- Looks like yet another report where something in solid goes wrong and kmix crashes as a result of that. So I guess its eiter a duplicate of bug #170873 or bug #173564. @Frank: If you can reproduce the crash, please have a look at http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a more detailed backtrace. *** This bug has been marked as a duplicate of bug 173564 *** -- Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 175850] Crashes when downloading Email from my IMAP Account and No window borders. All other Apps have borders
http://bugs.kde.org/show_bug.cgi?id=175850 Oliver Putz Regnaron web de changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Comment #1 from Oliver Putz Regnaron web de 2008-11-23 20:03:58 --- Hi and thanks for your bugreport. It sounds as if you can reproduce the crash. So could you please have a look at http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports, install the debugging symbols and post a more detailed backtrace? For the record: At least the description matches bug #175825. -- Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 175095] stochastic crash with signal 11 (SIGSEGV)
http://bugs.kde.org/show_bug.cgi?id=175095 Oliver Putz Regnaron web de changed: What|Removed |Added CC||[EMAIL PROTECTED] Status|UNCONFIRMED |RESOLVED Resolution||DUPLICATE --- Comment #3 from Oliver Putz Regnaron web de 2008-11-19 09:27:49 --- Hi! Jep, the new backtrace is better, thanks. Actually it seems like you ran into the same problem described in bug #164265 which should be fixed in KDE-4.1.3 *** This bug has been marked as a duplicate of bug 164265 *** -- Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 175144] crash instantly at startup
http://bugs.kde.org/show_bug.cgi?id=175144 Oliver Putz Regnaron web de changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Comment #4 from Oliver Putz Regnaron web de 2008-11-19 09:36:07 --- Hi and thanks for your bugreport. The two crashes not posted by the initial reporter are duplicates of bug #164265 which will be fixed in KDE-4.1.3. So lets just work on the initial crash. If you can reliably reproduce that one, could you please have a look at http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports, try to install the debugging packages for your distribution and post a more detailed backtrace for that crash? -- Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 175462] Kontact (kontact), signaal SIGSEGV
http://bugs.kde.org/show_bug.cgi?id=175462 Oliver Putz Regnaron web de changed: What|Removed |Added CC||[EMAIL PROTECTED] Severity|normal |crash --- Comment #1 from Oliver Putz Regnaron web de 2008-11-19 08:27:47 --- Hi, thanks for your bugreport. Can you tell us what you did right before the crash? Can you perhaps even reproduce it? -- Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 95064] Duplicates messages in imap folder after filtering
http://bugs.kde.org/show_bug.cgi?id=95064 Oliver Putz Regnaron web de changed: What|Removed |Added CC||[EMAIL PROTECTED] -- Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 169172] Renaming DIMAP folders crashes KMail
http://bugs.kde.org/show_bug.cgi?id=169172 --- Comment #4 from Oliver Putz Regnaron web de 2008-11-02 09:23:06 --- *** Bug 169934 has been marked as a duplicate of this bug. *** -- Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 169934] KMail crashes when some folders of its are deleted
http://bugs.kde.org/show_bug.cgi?id=169934 Oliver Putz Regnaron web de changed: What|Removed |Added CC||[EMAIL PROTECTED] Status|UNCONFIRMED |RESOLVED Resolution||DUPLICATE --- Comment #2 from Oliver Putz Regnaron web de 2008-11-02 09:23:06 --- Seems to be the same problem as in bug #169172 *** This bug has been marked as a duplicate of bug 169172 *** -- Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 174036] kontact crashes on pc startup
http://bugs.kde.org/show_bug.cgi?id=174036 Oliver Putz Regnaron web de changed: What|Removed |Added CC||[EMAIL PROTECTED] Status|UNCONFIRMED |RESOLVED Resolution||DUPLICATE --- Comment #1 from Oliver Putz Regnaron web de 2008-11-02 11:15:34 --- *** This bug has been marked as a duplicate of bug 173474 *** -- Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 173410] Crash on startup with SIGSEGV
http://bugs.kde.org/show_bug.cgi?id=173410 Oliver Putz Regnaron web de changed: What|Removed |Added CC||[EMAIL PROTECTED] Status|UNCONFIRMED |RESOLVED Resolution||DUPLICATE --- Comment #1 from Oliver Putz Regnaron web de 2008-10-30 22:10:01 --- Same backtrace as in bug #173474 *** This bug has been marked as a duplicate of bug 173474 *** -- Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 173438] Mails are not shown after deselecting grouped email list
http://bugs.kde.org/show_bug.cgi?id=173438 Oliver Putz Regnaron web de changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Comment #4 from Oliver Putz Regnaron web de 2008-10-27 23:04:56 --- Hi, an easier and reproducible way (at least for me) to reproduce this is to just thread messages in a folder and then use Folder-Remove duplicate messages on that folder. Until I uncheck and recheck the Folder-Thread Messages, I cannot see any but the root mails of the threaded messages. -- Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 121089] Random crashing when working on IMAP.
http://bugs.kde.org/show_bug.cgi?id=121089 Oliver Putz Regnaron web de changed: What|Removed |Added CC||[EMAIL PROTECTED] -- Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 172944] KMail crashed when typing messag
http://bugs.kde.org/show_bug.cgi?id=172944 Oliver Putz Regnaron web de changed: What|Removed |Added CC||[EMAIL PROTECTED] Severity|normal |crash --- Comment #1 from Oliver Putz Regnaron web de 2008-10-21 20:46:36 --- Let me guess: you had on-the-fly spellchecking enabled while you were typing the message? (sounds to me like a duplicate of the spellchecker bugs) -- Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 172291] kontact crashs - with debug info
http://bugs.kde.org/show_bug.cgi?id=172291 Oliver Putz Regnaron web de changed: What|Removed |Added CC||[EMAIL PROTECTED] Severity|normal |crash --- Comment #1 from Oliver Putz Regnaron web de 2008-10-21 20:57:05 --- Let me guess: You dragged a folder right before it kontact crashed? If so: This bug looks like a duplicate of bug #166003 -- Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 172166] Kmail Crash When sending
http://bugs.kde.org/show_bug.cgi?id=172166 Oliver Putz Regnaron web de changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Comment #4 from Oliver Putz Regnaron web de 2008-10-21 21:00:56 --- Warren, your second backtrace seems to be unrelated to your first backtrace. It rather looks like the backtrace in bug #166003 -- Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 163071] Crash when deleting messages from inbox
http://bugs.kde.org/show_bug.cgi?id=163071
Oliver Putz Regnaron web de changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
--- Comment #5 from Oliver Putz Regnaron web de 2008-10-21 21:32:10 ---
Confirming as I just got the same backtrace as in (my) bugreport #168848 which
was marked as a duplicate of this one (KDE version ~4.1.68)
What I did:
I deleted a (unread) message from my IMAP inbox. While it was being deleted I
went over several other unread mails in the same folder (thereby marking them
read) and before the deletion of the first message finished, I hit the delete
button on yet another unread message in the same inbox.
The backtrace was:
#6 0x464d4b28 in ?? ()
#7 0xb1c5dc72 in KMAcctImap::ignoreJobsForMessage (this=0x83eb220,
msg=0x87203b0) at
/var/tmp/portage/kde-base/kmail-/work/kmail/kmail/kmacctimap.cpp:217
#8 0xb1c7051b in KMFolderImap::ignoreJobsForMessage (this=0x845af18,
msg=0x87203b0) at
/var/tmp/portage/kde-base/kmail-/work/kmail/kmail/kmfolderimap.cpp:1543
#9 0xb1d3277a in KMMoveCommand::execute (this=0x8bc3560) at
/var/tmp/portage/kde-base/kmail-/work/kmail/kmail/kmcommands.cpp:2089
#10 0xb1d40bc5 in KMCommand::slotPostTransfer (this=0x8bc3560,
result=KMCommand::OK) at
/var/tmp/portage/kde-base/kmail-/work/kmail/kmail/kmcommands.cpp:273
#11 0xb1d40dde in KMCommand::qt_metacall (this=0x8bc3560,
_c=QMetaObject::InvokeMetaMethod, _id=5, _a=0xbf9c08bc) at
/var/tmp/portage/kde-base/kmail-/work/kmail_build/kmail/kmcommands.moc:86
#12 0xb1d41326 in KMMoveCommand::qt_metacall (this=0x8bc3560,
_c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbf9c08bc)
at
/var/tmp/portage/kde-base/kmail-/work/kmail_build/kmail/kmcommands.moc:1662
#13 0xb1d413da in KMDeleteMsgCommand::qt_metacall (this=0x8bc3560,
_c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbf9c08bc)
at
/var/tmp/portage/kde-base/kmail-/work/kmail_build/kmail/kmcommands.moc:1712
#14 0xb7ed64e1 in QMetaObject::activate (sender=0x8bc3560,
from_signal_index=value optimized out, to_signal_index=4, argv=0xbf9c08bc) at
kernel/qobject.cpp:3028
#15 0xb7ed83d8 in QMetaObject::activate (sender=0x8bc3560, m=0xb1fbca14,
local_signal_index=0, argv=0xbf9c08bc) at kernel/qobject.cpp:3098
#16 0xb1d28e8d in KMCommand::messagesTransfered (this=0x8bc3560,
_t1=KMCommand::OK) at
/var/tmp/portage/kde-base/kmail-/work/kmail_build/kmail/kmcommands.moc:100
#17 0xb1d40ae7 in KMCommand::transferSelectedMsgs (this=0x8bc3560) at
/var/tmp/portage/kde-base/kmail-/work/kmail/kmail/kmcommands.cpp:367
#18 0xb1d41e08 in KMCommand::slotStart (this=0x8bc3560) at
/var/tmp/portage/kde-base/kmail-/work/kmail/kmail/kmcommands.cpp:265
#19 0xb1d40dc4 in KMCommand::qt_metacall (this=0x8bc3560,
_c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbf9c0ad8) at
/var/tmp/portage/kde-base/kmail-/work/kmail_build/kmail/kmcommands.moc:85
#20 0xb1d41326 in KMMoveCommand::qt_metacall (this=0x8bc3560,
_c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbf9c0ad8)
at
/var/tmp/portage/kde-base/kmail-/work/kmail_build/kmail/kmcommands.moc:1662
#21 0xb1d413da in KMDeleteMsgCommand::qt_metacall (this=0x8bc3560,
_c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbf9c0ad8)
at
/var/tmp/portage/kde-base/kmail-/work/kmail_build/kmail/kmcommands.moc:1712
#22 0xb7ed64e1 in QMetaObject::activate (sender=0x8b2a5f0,
from_signal_index=value optimized out, to_signal_index=4, argv=0x0) at
kernel/qobject.cpp:3028
#23 0xb7ed83d8 in QMetaObject::activate (sender=0x8b2a5f0, m=0xb7fa39e4,
local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3098
#24 0xb7edc005 in QSingleShotTimer::timeout (this=0x8b2a5f0) at
.moc/debug-shared/qtimer.moc:74
#25 0xb7edc106 in QSingleShotTimer::timerEvent (this=0x8b2a5f0) at
kernel/qtimer.cpp:300
#26 0xb7ecf969 in QObject::event (this=0x8b2a5f0, e=0xbf9c0f8c) at
kernel/qobject.cpp:1117
#27 0xb5a22fab in QApplicationPrivate::notify_helper (this=0x8066200,
receiver=0x8b2a5f0, e=0xbf9c0f8c) at kernel/qapplication.cpp:3809
#28 0xb5a29ae5 in QApplication::notify (this=0xbf9c1348, receiver=0x8b2a5f0,
e=0xbf9c0f8c) at kernel/qapplication.cpp:3399
#29 0xb7a0f2b1 in KApplication::notify (this=0xbf9c1348, receiver=0x8b2a5f0,
event=0xbf9c0f8c) at
/var/tmp/portage/kde-base/kdelibs-/work/kdelibs-/kdeui/kernel/kapplication.cpp:307
#30 0xb7ebfb21 in QCoreApplication::notifyInternal (this=0xbf9c1348,
receiver=0x8b2a5f0, event=0xbf9c0f8c) at kernel/qcoreapplication.cpp:593
#31 0xb7eec36e in QTimerInfoList::activateTimers (this=0x8067a34) at
kernel/qcoreapplication.h:215
#32 0xb7eec532 in QEventDispatcherUNIX::processEvents (this=0x80670f0, flags={i
= -1080290772}) at kernel/qeventdispatcher_unix.cpp:899
#33 0xb5ab864f in QEventDispatcherX11::processEvents (this=0x80670f0, flags={i
= -1080290712}) at kernel/qeventdispatcher_x11.cpp:154
#34
[Bug 171445] khtml to read help file not found, kontact crashed while mailing
http://bugs.kde.org/show_bug.cgi?id=171445 Oliver Putz Regnaron web de changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Comment #5 from Oliver Putz Regnaron web de 2008-10-19 20:30:51 --- Backtrace looks similar to the one in bug #171491. The same problem / bug? -- Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 162347] Crash in updateMessageActions() after trying to send message
http://bugs.kde.org/show_bug.cgi?id=162347 Oliver Putz Regnaron web de changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Comment #1 from Oliver Putz Regnaron web de 2008-10-19 20:31:38 --- Backtrace looks similar to the one in bug #171491. The same problem / bug? -- Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 171741] New: Kontact crashed when minizing detailed progress window after sending mail failed
http://bugs.kde.org/show_bug.cgi?id=171741 Summary: Kontact crashed when minizing detailed progress window after sending mail failed Product: kmail Version: 1.10.90 Platform: unspecified OS/Version: Linux Status: NEW Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: [EMAIL PROTECTED] Version: 1.10.90 (using 4.1.67 (KDE 4.1.67 (KDE 4.2 = 20080918)), Gentoo) Compiler: i686-pc-linux-gnu-gcc OS:Linux (i686) release 2.6.25-gentoo-r7 What I did: 1) I was trying to answer to some email. Even though the email was in the outbox, sending stalled for some reason 2) I expanded the detailed progress window thing in the lower right corner 3) I canceled the sending (discarded the message) 4) I hit the red minus sign in the detailed progress window thing in the lower right corner in order to minimize it again 5) Kontact (roughly two weeks old SVN checkout) crashed with the following backtrace: Application: Kontact (kontact), signal SIGABRT [Current thread is 0 (LWP 480)] Thread 2 (Thread 0xb10d0b90 (LWP 6823)): #0 0xe424 in __kernel_vsyscall () #1 0xb58d1021 in select () from /lib/libc.so.6 #2 0xb6a61227 in QProcessManager::run (this=0x8061718) at io/qprocess_unix.cpp:307 #3 0xb6991a24 in QThreadPrivate::start (arg=0x8061718) at thread/qthread_unix.cpp:191 #4 0xb6913160 in start_thread (arg=0xb10d0b90) at pthread_create.c:297 #5 0xb58d7c0e in clone () from /lib/libc.so.6 Thread 1 (Thread 0xb4da4720 (LWP 480)): [KCrash Handler] #6 0xe424 in __kernel_vsyscall () #7 0xb5836690 in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #8 0xb5837ed8 in *__GI_abort () at abort.c:88 #9 0xb5a33780 in __gnu_cxx::__verbose_terminate_handler () at /var/tmp/portage/sys-devel/gcc-4.3.1-r1/work/gcc-4.3.1/libstdc++-v3/libsupc++/vterminate.cc:98 #10 0xb5a31955 in __cxxabiv1::__terminate (handler=0xb5a33630 __gnu_cxx::__verbose_terminate_handler()) at /var/tmp/portage/sys-devel/gcc-4.3.1-r1/work/gcc-4.3.1/libstdc++-v3/libsupc++/eh_terminate.cc:43 #11 0xb5a3198c in std::terminate () at /var/tmp/portage/sys-devel/gcc-4.3.1-r1/work/gcc-4.3.1/libstdc++-v3/libsupc++/eh_terminate.cc:53 #12 0xb5a324d3 in __cxa_pure_virtual () at /var/tmp/portage/sys-devel/gcc-4.3.1-r1/work/gcc-4.3.1/libstdc++-v3/libsupc++/pure.cc:55 #13 0xb1c0f1c1 in KMFolderMaildir::compact (this=0x8489848, startIndex=0, nbMessages=-1, [EMAIL PROTECTED], [EMAIL PROTECTED]) at /var/tmp/portage/kde-base/kmail-/work/kmail/kmail/kmfoldermaildir.cpp:266 #14 0xb1d5a619 in KMail::MaildirCompactionJob::slotDoWork (this=0x8d75d40) at /var/tmp/portage/kde-base/kmail-/work/kmail/kmail/compactionjob.cpp:262 #15 0xb1d5a9c2 in KMail::MaildirCompactionJob::executeNow (this=0x8d75d40, silent=true) at /var/tmp/portage/kde-base/kmail-/work/kmail/kmail/compactionjob.cpp:251 #16 0xb1c0f062 in KMFolderMaildir::compact (this=0x8489848, silent=false) at /var/tmp/portage/kde-base/kmail-/work/kmail/kmail/kmfoldermaildir.cpp:303 #17 0xb1b3ec88 in KMFolder::compact (this=0x848a908, options=KMFolder::CompactSilentlyNow) at /var/tmp/portage/kde-base/kmail-/work/kmail/kmail/kmfolder.cpp:837 #18 0xb1b83755 in KMSender::cleanup (this=0x83e4cb8) at /var/tmp/portage/kde-base/kmail-/work/kmail/kmail/kmsender.cpp:632 #19 0xb1b86c2d in KMSender::slotResult (this=0x83e4cb8, job=0x8d82e90) at /var/tmp/portage/kde-base/kmail-/work/kmail/kmail/kmsender.cpp:736 #20 0xb1b86d49 in KMSender::qt_metacall (this=0x83e4cb8, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfd0ac8c) at /var/tmp/portage/kde-base/kmail-/work/kmail_build/kmail/kmsender.moc:72 #21 0xb6a994e1 in QMetaObject::activate (sender=0x8d82e90, from_signal_index=value optimized out, to_signal_index=7, argv=0xbfd0ac8c) at kernel/qobject.cpp:3028 #22 0xb6a9b3d8 in QMetaObject::activate (sender=0x8d82e90, m=0xb6e3fee8, local_signal_index=3, argv=0xbfd0ac8c) at kernel/qobject.cpp:3098 #23 0xb6d397d5 in KJob::result (this=0x8d82e90, _t1=0x8d82e90) at /var/tmp/portage/kde-base/kdelibs-/work/kdelibs_build/kdecore/kjob.moc:186 #24 0xb6d39c4c in KJob::emitResult (this=0x8d82e90) at /var/tmp/portage/kde-base/kdelibs-/work/kdelibs-/kdecore/jobs/kjob.cpp:290 #25 0xb6d39cab in KJob::kill (this=0x8d82e90, verbosity=KJob::EmitResult) at /var/tmp/portage/kde-base/kdelibs-/work/kdelibs-/kdecore/jobs/kjob.cpp:112 #26 0xb1b835ca in KMSender::slotAbortSend (this=0x83e4cb8) at /var/tmp/portage/kde-base/kmail-/work/kmail/kmail/kmsender.cpp:653 #27 0xb1b86d82 in KMSender::qt_metacall (this=0x83e4cb8, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfd0adfc) at /var/tmp/portage/kde-base/kmail-/work/kmail_build/kmail/kmsender.moc:74 #28 0xb6a994e1 in QMetaObject::activate (sender=0x8a75f00, from_signal_index=value optimized out, to_signal_index=7, argv=0xbfd0adfc) at
[Bug 171178] Kmail crashing, when I type konett
http://bugs.kde.org/show_bug.cgi?id=171178 Oliver Putz Regnaron web de changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Comment #1 from Oliver Putz Regnaron web de 2008-09-17 12:39:12 --- Hello, Thanks for your report. Regrettably I cannot reproduce the crash. Can have a look at http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports, try to install the debugging packages for your distribution and post a backtrace for the crash? (there seem to be several spell-checker related bug floating around...) -- Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 171157] when answering mails adressed to my second email address, kget puts my first email adress in the CC field
http://bugs.kde.org/show_bug.cgi?id=171157 --- Comment #1 from Oliver Putz Regnaron web de 2008-09-16 14:14:33 --- To further clarify: The private server only holds one unified mailbox that stores all mails from the different accounts. (which is why I have mails addressed to different mailboxes in the same IMAP inbox) -- Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 171159] Kmail crashes after adding new cached IMAP account
http://bugs.kde.org/show_bug.cgi?id=171159 Oliver Putz Regnaron web de changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Comment #1 from Oliver Putz Regnaron web de 2008-09-16 15:47:14 --- Hello, Thanks for your report. Unfortunately your backtrace is not really usable as is. Can you have a look at http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and try to install the debugging packages for your distribution and post a more verbose backtrace? -- Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 171102] kmail crashes when writing and email
http://bugs.kde.org/show_bug.cgi?id=171102 Oliver Putz Regnaron web de changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Comment #1 from Oliver Putz Regnaron web de 2008-09-15 12:34:12 --- Hello, Thanks for your report. Unfortunately without any backtrace the developers cannot fix this problem. So, can you have a look at http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports, install the debugging packages for your distribution, make kmail crash and then post the backtrace here? -- Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 170997] New: kmail crashed in KMReaderWin::copyText when trying to answer mail
http://bugs.kde.org/show_bug.cgi?id=170997 Summary: kmail crashed in KMReaderWin::copyText when trying to answer mail Product: kmail Version: 1.9.9 Platform: unspecified OS/Version: Linux Status: NEW Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: [EMAIL PROTECTED] Version: 1.9.9 (using 3.5.9, Gentoo) Compiler: Target: x86_64-pc-linux-gnu OS:Linux (x86_64) release 2.6.25-gentoo-r7 In case anyone is still working on the kmail-3.5 codebase: Today as I asnwered a mail on an IMAP server (by hitting a), kmail crashed with the backtrace below. After the crash, the mail appeared (in kmail) to be empty [nothing left except the headers]. However, on the IMAP server, the mail is still completely intact. The backtrace for this crash was: Using host libthread_db library /lib/libthread_db.so.1. [Thread debugging using libthread_db enabled] [New Thread 0x7f57ef764700 (LWP 19468)] [New Thread 0x42af3950 (LWP 19472)] [New Thread 0x422f2950 (LWP 19471)] [New Thread 0x41af1950 (LWP 19470)] [New Thread 0x412f0950 (LWP 19469)] [KCrash handler] #5 0x7f57e29ccf65 in KMReaderWin::copyText (this=value optimized out) at kmreaderwin.cpp:2376 #6 0x7f57e2b822c9 in KMail::MessageActions::replyCommandKMReplyToAllCommand (this=0xd98f80) at messageactions.h:67 #7 0x7f57e2b80883 in KMail::MessageActions::qt_invoke (this=0xd98f80, _id=6, _o=0x777a2b00) at messageactions.moc:108 #8 0x7f57e9193888 in QObject::activate_signal (this=0xd9c660, clist=0xd9cb30, o=0x777a2b00) at kernel/qobject.cpp:2356 #9 0x7f57e91948a2 in QObject::activate_signal (this=0xd9c660, signal=2) at kernel/qobject.cpp:2325 #10 0x7f57eb8bcb15 in KAction::qt_invoke (this=0xd9c660, _id=15, _o=0x777a2c70) at kaction.moc:218 #11 0x7f57e9193888 in QObject::activate_signal (this=0xeabda0, clist=0xed3ff0, o=0x777a2c70) at kernel/qobject.cpp:2356 #12 0x7f57e91948a2 in QObject::activate_signal (this=0xeabda0, signal=2) at kernel/qobject.cpp:2325 #13 0x7f57ea929630 in KAccelPrivate::emitActivatedSignal (this=0xeabda0, pAction=0xeefe20) at kaccel.cpp:400 #14 0x7f57ea929c80 in KAccelPrivate::eventFilter (this=0xeabda0, pEvent=0x777a3420) at kaccel.cpp:370 #15 0x7f57e91911c0 in QObject::activate_filters (this=0x6e6510, e=0x777a3420) at kernel/qobject.cpp:903 #16 0x7f57e9191260 in QObject::event (this=0x6e6510, e=0x777a3420) at kernel/qobject.cpp:735 #17 0x7f57e91d6eb3 in QWidget::event (this=0x6e6510, e=0x777a3420) at kernel/qwidget.cpp:4659 #18 0x7f57e92d197e in QMainWindow::event (this=0x6e6510, e=0x777a3420) at widgets/qmainwindow.cpp:1687 #19 0x7f57e911897f in QApplication::internalNotify (this=0x777a3c10, receiver=0x6e6510, e=0x777a3420) at kernel/qapplication.cpp:2635 #20 0x7f57e911acb9 in QApplication::notify (this=0x777a3c10, receiver=0x1259c60, e=0x777a3420) at kernel/qapplication.cpp:2392 #21 0x7f57ea8c276c in KApplication::notify (this=0x777a3c10, receiver=0x1259c60, event=0x777a3420) at kapplication.cpp:550 #22 0x7f57ea92a818 in KAccelEventHandler::x11Event ( this=value optimized out, pEvent=value optimized out) at kaccel.cpp:144 #23 0x7f57ea8bae24 in KApplication::x11EventFilter (this=0x777a3c10, _event=0x777a38b0) at kapplication.cpp:1729 #24 0x7f57e908249f in qt_x11EventFilter (ev=0x777a38b0) at kernel/qapplication_x11.cpp:387 #25 0x7f57e9096858 in QApplication::x11ProcessEvent (this=0x777a3c10, event=0x777a38b0) at kernel/qapplication_x11.cpp:3315 #26 0x7f57e90b05a4 in QEventLoop::processEvents (this=0x6a8bd0, flags=4) at kernel/qeventloop_x11.cpp:192 #27 0x7f57e91385e5 in QEventLoop::enterLoop (this=0x6a8bd0) at kernel/qeventloop.cpp:198 #28 0x7f57e91383eb in QEventLoop::exec (this=0x6a8bd0) at kernel/qeventloop.cpp:145 #29 0x7f57e911a7c4 in QApplication::exec (this=0x777a3c10) at kernel/qapplication.cpp:2758 #30 0x0041ea63 in main (argc=value optimized out, argv=0x777a3f28) at main.cpp:163 #31 0x7f57e53a1486 in __libc_start_main (main=0x41e8ba main, argc=1, ubp_av=0x777a3f28, init=0x430b20 __libc_csu_init, fini=value optimized out, rtld_fini=value optimized out, stack_end=0x777a3f18) at libc-start.c:226 #32 0x0041e5c9 in _start () Current language: auto; currently c -- Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 170728] New: kontact freezes when trying to modify sending smtp account (trying to use not-installed kwallet)
http://bugs.kde.org/show_bug.cgi?id=170728 Summary: kontact freezes when trying to modify sending smtp account (trying to use not-installed kwallet) Product: kmail Version: 1.10.1 Platform: unspecified OS/Version: Linux Status: NEW Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: [EMAIL PROTECTED] Version: 1.10.1 (using 4.1.1 (KDE 4.1.1), Gentoo) Compiler: i686-pc-linux-gnu-gcc OS:Linux (i686) release 2.6.25-gentoo-r7 Steps to reproduce 1) Open kontact 2) Go to Settings-Configure Kmail-Accounts-Sending 3) Select an account and hit modify Note: This only happens with an old (KDE-4.0 times) SMTP Account. If I create a new Account, I can normally modify all the data. Starting Kontact from konsole and executing the above steps prints infinitely many The kwalletd service has been disabled messages. Even though kwallet is not installed, I think this dialog should not freeze if kwallet is not available. As the account is quite old, is it possible that kmail once stored some pasword in the wallet and now wants to retrieve it but cannot accept that it is no longer there? -- Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 131434] SIGSEV when searching for duplicate messages
http://bugs.kde.org/show_bug.cgi?id=131434 Oliver Putz Regnaron web de changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Comment #2 from Oliver Putz Regnaron web de 2008-09-03 16:46:34 --- I think I just ran into this bug. When I fetched some mails, my personal IMAP server had some hickups so that it fetched several mails multiple times. When I browsed a folder in KMail, I saw all the duplicates and used Folder-Remove Duplicate Messages to remove the dulplicates on the IMAP server. This seemed to remove some duplicates, but not all. So I (shortly after) used that function again. Right after this, Kontact from KDE-3.5.9 crashed (maybe it tried to delete some already deleted message?) with the following backtrace: Using host libthread_db library /lib/libthread_db.so.1. [Thread debugging using libthread_db enabled] [New Thread 0x7f02a5ebd700 (LWP 18193)] [New Thread 0x426e9950 (LWP 18201)] [New Thread 0x41ee8950 (LWP 18200)] [New Thread 0x416e7950 (LWP 18199)] [New Thread 0x40ee6950 (LWP 18198)] [KCrash handler] #5 KMFolderImap::deleteMessage (this=0xbf5ce0, msg=0x0) at kmfolderimap.cpp:1821 #6 0x7f02991a0630 in KMFolderImap::removeMsg (this=0xbf5ce0, idx=820, quiet=value optimized out) at kmfolderimap.cpp:285 #7 0x7f029922868f in KMMainWidget::removeDuplicates (this=0xcd7c30) at kmmainwidget.cpp:3606 #8 0x7f0299238db6 in KMMainWidget::qt_invoke (this=0xcd7c30, _id=175, _o=0x7fffadefaa70) at kmmainwidget.moc:619 #9 0x7f029f8eb888 in QObject::activate_signal (this=0xd83650, clist=0xd83a90, o=0x7fffadefaa70) at kernel/qobject.cpp:2356 #10 0x7f029f8ec8a2 in QObject::activate_signal (this=0xd83650, signal=2) at kernel/qobject.cpp:2325 #11 0x7f02a2014877 in KAction::slotPopupActivated (this=0xd83650) at kaction.cpp:1137 #12 0x7f02a2014b28 in KAction::qt_invoke (this=0xd83650, _id=16, _o=0x7fffadefac00) at kaction.moc:219 #13 0x7f029f8eb888 in QObject::activate_signal (this=0xef0b30, clist=0xef0c10, o=0x7fffadefac00) at kernel/qobject.cpp:2356 #14 0x7f029fd1f5a0 in QSignal::signal (this=0xef0b30, [EMAIL PROTECTED]) at .moc/debug-shared-mt/moc_qsignal.cpp:100 #15 0x7f029f91097c in QSignal::activate (this=0xef0b30) at kernel/qsignal.cpp:212 #16 0x7f029fa44b0a in QPopupMenu::mouseReleaseEvent (this=0xeea4b0, e=0x7fffadefb390) at widgets/qpopupmenu.cpp:1691 #17 0x7f029f92efc5 in QWidget::event (this=0xeea4b0, e=0x7fffadefb390) at kernel/qwidget.cpp:4677 #18 0x7f029f87097f in QApplication::internalNotify (this=0x7fffadefbd80, receiver=0xeea4b0, e=0x7fffadefb390) at kernel/qapplication.cpp:2635 #19 0x7f029f872e9c in QApplication::notify (this=0x7fffadefbd80, receiver=0xeea4b0, e=0x7fffadefb390) at kernel/qapplication.cpp:2421 #20 0x7f02a101a76c in KApplication::notify (this=0x7fffadefbd80, receiver=0xeea4b0, event=0x7fffadefb390) at kapplication.cpp:550 #21 0x7f029f7f242e in QApplication::sendSpontaneousEvent ( receiver=0xeea4b0, event=0x7fffadefb390) at kernel/qapplication.h:499 #22 0x7f029f7f0d0a in QETWidget::translateMouseEvent (this=0xeea4b0, event=0x7fffadefba20) at kernel/qapplication_x11.cpp:4240 #23 0x7f029f7eeec2 in QApplication::x11ProcessEvent (this=0x7fffadefbd80, event=0x7fffadefba20) at kernel/qapplication_x11.cpp:3449 #24 0x7f029f8085a4 in QEventLoop::processEvents (this=0x6a8bc0, flags=4) at kernel/qeventloop_x11.cpp:192 #25 0x7f029f8905e5 in QEventLoop::enterLoop (this=0x6a8bc0) at kernel/qeventloop.cpp:198 #26 0x7f029f8903eb in QEventLoop::exec (this=0x6a8bc0) at kernel/qeventloop.cpp:145 #27 0x7f029f8727c4 in QApplication::exec (this=0x7fffadefbd80) at kernel/qapplication.cpp:2758 #28 0x0041ea63 in main (argc=value optimized out, argv=0x7fffadefc098) at main.cpp:163 #29 0x7f029baf9486 in __libc_start_main (main=0x41e8ba main, argc=1, ubp_av=0x7fffadefc098, init=0x430b20 __libc_csu_init, fini=value optimized out, rtld_fini=value optimized out, stack_end=0x7fffadefc088) at libc-start.c:226 #30 0x0041e5c9 in _start () Current language: auto; currently c -- Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 169236] New: Kontact crashed after creating new dIMAP account
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=169236 Summary: Kontact crashed after creating new dIMAP account Product: kmail Version: 1.10.0 Platform: unspecified OS/Version: Linux Status: NEW Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: Regnaron web de Version: 1.10.0 (using 4.1.00 (KDE 4.1.0), Gentoo) Compiler: i686-pc-linux-gnu-gcc OS:Linux (i686) release 2.6.25-gentoo-r7 I just tried to create a new dIMAP account in Kontact and after setting it up, it crashed with the backtrace below. I *think* right after I created the account I was asked for a password which I only entered after having closed the window for the account setup. Anyway, the backtrace was: Application: Kontact (kontact), signal SIGSEGV [Thread debugging using libthread_db enabled] [New Thread 0xb4d5e720 (LWP 21462)] [KCrash handler] #6 0x000b in ?? () #7 0xb1f847c9 in KMail::ImapAccountBase::makeConnection (this=0x87d20a0) at /var/tmp/portage/kde-base/kmail-4.1.0/work/kmail-4.1.0/kmail/imapaccountbase.cpp:336 #8 0xb1e35efe in AccountUpdater::update (this=0x8a69ee8) at /var/tmp/portage/kde-base/kmail-4.1.0/work/kmail-4.1.0/kmail/configuredialog.cpp:5416 #9 0xb1e61ba2 in AccountsPageReceivingTab::save (this=0x88ff8a0) at /var/tmp/portage/kde-base/kmail-4.1.0/work/kmail-4.1.0/kmail/configuredialog.cpp:1212 #10 0xb1e7a1ab in ConfigModuleWithTabs::save (this=0x88ca428) at /var/tmp/portage/kde-base/kmail-4.1.0/work/kmail-4.1.0/kmail/configuredialog_p.cpp:422 #11 0xb565be29 in KCModuleProxy::save (this=0x88fcd38) at /var/tmp/portage/kde-base/kdelibs-4.1.0/work/kdelibs-4.1.0/kutils/kcmoduleproxy.cpp:276 #12 0xb56579a1 in KCMultiDialogPrivate::apply (this=0x8896128) at /var/tmp/portage/kde-base/kdelibs-4.1.0/work/kdelibs-4.1.0/kutils/kcmultidialog.cpp:192 #13 0xb5657c54 in KCMultiDialog::slotApplyClicked (this=0x8889868) at /var/tmp/portage/kde-base/kdelibs-4.1.0/work/kdelibs-4.1.0/kutils/kcmultidialog.cpp:219 #14 0xb5659552 in KCMultiDialog::qt_metacall (this=0x8889868, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbfb47bd8) at /var/tmp/portage/kde-base/kdelibs-4.1.0/work/kdelibs_build/kutils/kcmultidialog.moc:86 #15 0xb1e69bf0 in ConfigureDialog::qt_metacall (this=0x8889868, _c=QMetaObject::InvokeMetaMethod, _id=77, _a=0xbfb47bd8) at /var/tmp/portage/kde-base/kmail-4.1.0/work/kmail_build/kmail/configuredialog.moc:67 #16 0xb6ae3530 in QMetaObject::activate (sender=0x8889868, from_signal_index=value optimized out, to_signal_index=42, argv=value optimized out) at kernel/qobject.cpp:3001 #17 0xb6ae3c92 in QMetaObject::activate (sender=0x8889868, m=0xb727c824, local_signal_index=7, argv=0x0) at kernel/qobject.cpp:3071 #18 0xb70a0431 in KDialog::applyClicked (this=0x8889868) at /var/tmp/portage/kde-base/kdelibs-4.1.0/work/kdelibs_build/kdeui/kdialog.moc:235 #19 0xb70a1862 in KDialog::slotButtonClicked (this=0x8889868, button=8) at /var/tmp/portage/kde-base/kdelibs-4.1.0/work/kdelibs-4.1.0/kdeui/dialogs/kdialog.cpp:848 #20 0xb70a388c in KDialog::qt_metacall (this=0x8889868, _c=QMetaObject::InvokeMetaMethod, _id=68, _a=0xbfb47dec) at /var/tmp/portage/kde-base/kdelibs-4.1.0/work/kdelibs_build/kdeui/kdialog.moc:181 #21 0xb7158de0 in KPageDialog::qt_metacall (this=0x8889868, _c=QMetaObject::InvokeMetaMethod, _id=68, _a=0xbfb47dec) at /var/tmp/portage/kde-base/kdelibs-4.1.0/work/kdelibs_build/kdeui/kpagedialog.moc:63 #22 0xb56594da in KCMultiDialog::qt_metacall (this=0x8889868, _c=QMetaObject::InvokeMetaMethod, _id=68, _a=0xbfb47dec) at /var/tmp/portage/kde-base/kdelibs-4.1.0/work/kdelibs_build/kutils/kcmultidialog.moc:77 #23 0xb1e69bf0 in ConfigureDialog::qt_metacall (this=0x8889868, _c=QMetaObject::InvokeMetaMethod, _id=68, _a=0xbfb47dec) at /var/tmp/portage/kde-base/kmail-4.1.0/work/kmail_build/kmail/configuredialog.moc:67 #24 0xb6ae3530 in QMetaObject::activate (sender=0x8896178, from_signal_index=value optimized out, to_signal_index=4, argv=value optimized out) at kernel/qobject.cpp:3001 #25 0xb6ae3c92 in QMetaObject::activate (sender=0x8896178, m=0xb6bb88d0, local_signal_index=0, argv=0xbfb47dec) at kernel/qobject.cpp:3071 #26 0xb6ae94e7 in QSignalMapper::mapped (this=0x8896178, _t1=8) at .moc/debug-shared/moc_qsignalmapper.cpp:93 #27 0xb6ae9a97 in QSignalMapper::map (this=0x8896178, sender=0x88ab8b0) at kernel/qsignalmapper.cpp:277 #28 0xb6ae9cc0 in QSignalMapper::map (this=0x8896178) at kernel/qsignalmapper.cpp:268 #29 0xb6ae9f31 in QSignalMapper::qt_metacall (this=0x8896178, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbfb47f5c) at
[Bug 169023] Kmail loses mail when it freezes after I'd moved some to an other folder (DIMAP). DATA LOSS.
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=169023 Regnaron web de changed: What|Removed |Added CC||Regnaron web de --- Additional Comments From Regnaron web de 2008-08-13 21:40 --- As you say that this crash happens regularly, could you have a look at http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and install the debug packages for your distribution so that? This way you can paste a good backtrace the next time it crashes for you. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 168881] kmail crash imap image attachment
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=168881 Regnaron web de changed: What|Removed |Added CC||Regnaron web de --- Additional Comments From Regnaron web de 2008-08-11 11:40 --- Hi, regrettably your backtrace isn't too verbose. Can you reproduce the crash? If so, how? Could you have a look at http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and give a more verbose backtrace? ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 168909] New: Kontact crashed when fetching new mail at startup
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=168909 Summary: Kontact crashed when fetching new mail at startup Product: kmail Version: 1.10.0 Platform: unspecified OS/Version: Linux Status: NEW Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: Regnaron web de Version: 1.10.0 (using 4.1.00 (KDE 4.1.0), Gentoo) Compiler: i686-pc-linux-gnu-gcc OS:Linux (i686) release 2.6.25-gentoo-r7 I started kontact, entered the password for my IMAP account, and as soon as kontact was fired up, I hit CTRL+L to fetch all mails. Kontact responed by crashing with the backtrace below. This normally works and I regrettably am not able to reproduce this crash (maybe some race condition somewhere?) Anyway, the backtrace is: Application: Kontact (kontact), signal SIGABRT [Thread debugging using libthread_db enabled] [New Thread 0xb4d7e720 (LWP 8490)] [KCrash handler] #6 0xe424 in __kernel_vsyscall () #7 0xb540f690 in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #8 0xb5410ed8 in *__GI_abort () at abort.c:88 #9 0xb69f0097 in qt_message_output (msgType=QtFatalMsg, buf=0xbfa6499c ASSERT: \!mSlave\ in file /var/tmp/portage/kde-base/kmail-4.1.0/work/kmail-4.1.0/kmail/imapaccountbase.cpp, line 304) at global/qglobal.cpp:2058 #10 0xb69f014f in qFatal (msg=0xb6b43ab4 ASSERT: \%s\ in file %s, line %d) at global/qglobal.cpp:2260 #11 0xb69f05cb in qt_assert (assertion=0xb21eb014 !mSlave, file=0xb21ea608 /var/tmp/portage/kde-base/kmail-4.1.0/work/kmail-4.1.0/kmail/imapaccountbase.cpp, line=304) at global/qglobal.cpp:1828 #12 0xb1fa04be in KMail::ImapAccountBase::makeConnection (this=0x84d8b88) at /var/tmp/portage/kde-base/kmail-4.1.0/work/kmail-4.1.0/kmail/imapaccountbase.cpp:304 #13 0xb1fa7571 in KMAcctImap::makeConnection (this=0x0) at /var/tmp/portage/kde-base/kmail-4.1.0/work/kmail-4.1.0/kmail/kmacctimap.cpp:561 #14 0xb1fa8545 in KMAcctImap::processNewMail (this=0x84d8b88, interactive=true) at /var/tmp/portage/kde-base/kmail-4.1.0/work/kmail-4.1.0/kmail/kmacctimap.cpp:278 #15 0xb1f4b6b9 in KMail::AccountManager::processNextCheck (this=0x83cdb10, _newMail=false) at /var/tmp/portage/kde-base/kmail-4.1.0/work/kmail-4.1.0/kmail/accountmanager.cpp:216 #16 0xb1f4b864 in KMail::AccountManager::singleCheckMail (this=0x83cdb10, account=0x84d8b88, interactive=true) at /var/tmp/portage/kde-base/kmail-4.1.0/work/kmail-4.1.0/kmail/accountmanager.cpp:143 #17 0xb1f9b8c8 in KMail::ImapAccountBase::slotCheckQueuedFolders ( this=0x84d8b88) at /var/tmp/portage/kde-base/kmail-4.1.0/work/kmail-4.1.0/kmail/imapaccountbase.cpp:1134 #18 0xb1fa1a74 in KMail::ImapAccountBase::qt_metacall (this=0x84d8b88, _c=QMetaObject::InvokeMetaMethod, _id=10, _a=0xbfa66e68) at /var/tmp/portage/kde-base/kmail-4.1.0/work/kmail_build/kmail/imapaccountbase.moc:127 #19 0xb1fa841a in KMAcctImap::qt_metacall (this=0x84d8b88, _c=QMetaObject::InvokeMetaMethod, _id=20, _a=0xbfa66e68) at /var/tmp/portage/kde-base/kmail-4.1.0/work/kmail_build/kmail/kmacctimap.moc:76 #20 0xb6b03530 in QMetaObject::activate (sender=0x84d8b88, from_signal_index=value optimized out, to_signal_index=4, argv=value optimized out) at kernel/qobject.cpp:3001 #21 0xb6b03c92 in QMetaObject::activate (sender=0x84d8b88, m=0xb22f7c14, local_signal_index=0, argv=0xbfa66e68) at kernel/qobject.cpp:3071 #22 0xb1ec6dc5 in KMAccount::finishedCheck (this=0x84d8b88, _t1=false, _t2=KMAccount::CheckOK) at /var/tmp/portage/kde-base/kmail-4.1.0/work/kmail_build/kmail/kmaccount.moc:158 #23 0xb1ec6e60 in KMAccount::checkDone (this=0x84d8b88, newmail=false, status=KMAccount::CheckOK) at /var/tmp/portage/kde-base/kmail-4.1.0/work/kmail-4.1.0/kmail/kmaccount.cpp:497 #24 0xb1fa9593 in KMAcctImap::killAllJobs (this=0x84d8b88, disconnectSlave=true) at /var/tmp/portage/kde-base/kmail-4.1.0/work/kmail-4.1.0/kmail/kmacctimap.cpp:198 #25 0xb1f9ce07 in KMail::ImapAccountBase::handleError (this=0x84d8b88, errorCode=146, errorMsg= 0xbfa67410, job=0x0, context= 0xbfa670b8, abortSync=true) at /var/tmp/portage/kde-base/kmail-4.1.0/work/kmail-4.1.0/kmail/imapaccountbase.cpp:1009 #26 0xb1fa967c in KMAcctImap::handleError (this=0x84d8b88, errorCode=6, errorMsg= 0xbfa67410, job=0x0, context= 0xbfa670b8, abortSync=value optimized out) at /var/tmp/portage/kde-base/kmail-4.1.0/work/kmail-4.1.0/kmail/kmacctimap.cpp:131 #27 0xb1fa1844 in KMail::ImapAccountBase::slotSchedulerSlaveError ( this=0x84d8b88, aSlave=0x85c9690, errorCode=146, errorMsg= 0xbfa67410) at
[Bug 168911] Kmail chrashes when trying to forward a message
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=168911 Regnaron web de changed: What|Removed |Added CC||Regnaron web de --- Additional Comments From Regnaron web de 2008-08-11 15:58 --- Hello, Thanks for your report. Unfortunately your backtrace is not really usable as is. Can you have a look at http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and try to install the debugging packages for your distribution? Can you reproduce the crash? If so, how exactly (forwarding works for me here)? ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 168848] New: Crash on deleting unread message
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=168848 Summary: Crash on deleting unread message Product: kmail Version: 1.10.0 Platform: unspecified OS/Version: Linux Status: NEW Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: Regnaron web de Version: 1.10.0 (using 4.1.00 (KDE 4.1.0), Gentoo) Compiler: i686-pc-linux-gnu-gcc OS:Linux (i686) release 2.6.25-gentoo-r7 I was deleting some unread messages on an IMAP server by hitting the del key. At the second hit, kontact crashed with the backtrace below. Regrettably I don't seem to be able to reproduce this crash. Application: Kontact (kontact), signal SIGSEGV [Thread debugging using libthread_db enabled] [New Thread 0xb4db4720 (LWP 12183)] [KCrash handler] #6 0xb1f38047 in QList (this=0xbfe99ae8, l= 0x40) at /usr/include/qt4/QtCore/qlist.h:113 #7 0xb210d88e in KMail::FolderJob::msgList (this=0x38) at /var/tmp/portage/kde-base/kmail-4.1.0/work/kmail-4.1.0/kmail/folderjob.cpp:120 #8 0xb1ffa1f9 in KMAcctImap::ignoreJobsForMessage (this=0x84772f8, msg=0x89c6b68) at /var/tmp/portage/kde-base/kmail-4.1.0/work/kmail-4.1.0/kmail/kmacctimap.cpp:215 #9 0xb200cc1b in KMFolderImap::ignoreJobsForMessage (this=0x846bcb0, msg=0x89c6b68) at /var/tmp/portage/kde-base/kmail-4.1.0/work/kmail-4.1.0/kmail/kmfolderimap.cpp:1552 #10 0xb20c9ff2 in KMMoveCommand::execute (this=0x89d0240) at /var/tmp/portage/kde-base/kmail-4.1.0/work/kmail-4.1.0/kmail/kmcommands.cpp:2092 #11 0xb20d8673 in KMCommand::slotPostTransfer (this=0x89d0240, result=KMCommand::OK) at /var/tmp/portage/kde-base/kmail-4.1.0/work/kmail-4.1.0/kmail/kmcommands.cpp:273 #12 0xb20d8886 in KMCommand::qt_metacall (this=0x89d0240, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0xbfe99d9c) at /var/tmp/portage/kde-base/kmail-4.1.0/work/kmail_build/kmail/kmcommands.moc:86 #13 0xb20d8dce in KMMoveCommand::qt_metacall (this=0x89d0240, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbfe99d9c) at /var/tmp/portage/kde-base/kmail-4.1.0/work/kmail_build/kmail/kmcommands.moc:1662 #14 0xb20d8e82 in KMDeleteMsgCommand::qt_metacall (this=0x89d0240, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbfe99d9c) at /var/tmp/portage/kde-base/kmail-4.1.0/work/kmail_build/kmail/kmcommands.moc:1712 #15 0xb6b39530 in QMetaObject::activate (sender=0x89d0240, from_signal_index=value optimized out, to_signal_index=4, argv=value optimized out) at kernel/qobject.cpp:3001 #16 0xb6b39c92 in QMetaObject::activate (sender=0x89d0240, m=0xb234f954, local_signal_index=0, argv=0xbfe99d9c) at kernel/qobject.cpp:3071 #17 0xb20c0b7d in KMCommand::messagesTransfered (this=0x89d0240, _t1=KMCommand::OK) at /var/tmp/portage/kde-base/kmail-4.1.0/work/kmail_build/kmail/kmcommands.moc:100 #18 0xb20d8596 in KMCommand::transferSelectedMsgs (this=0x89d0240) at /var/tmp/portage/kde-base/kmail-4.1.0/work/kmail-4.1.0/kmail/kmcommands.cpp:367 #19 0xb20d98c6 in KMCommand::slotStart (this=0x89d0240) at /var/tmp/portage/kde-base/kmail-4.1.0/work/kmail-4.1.0/kmail/kmcommands.cpp:265 #20 0xb20d886c in KMCommand::qt_metacall (this=0x89d0240, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbfe99fe8) at /var/tmp/portage/kde-base/kmail-4.1.0/work/kmail_build/kmail/kmcommands.moc:85 #21 0xb20d8dce in KMMoveCommand::qt_metacall (this=0x89d0240, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbfe99fe8) at /var/tmp/portage/kde-base/kmail-4.1.0/work/kmail_build/kmail/kmcommands.moc:1662 #22 0xb20d8e82 in KMDeleteMsgCommand::qt_metacall (this=0x89d0240, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbfe99fe8) at /var/tmp/portage/kde-base/kmail-4.1.0/work/kmail_build/kmail/kmcommands.moc:1712 #23 0xb6b39530 in QMetaObject::activate (sender=0x871cd38, from_signal_index=value optimized out, to_signal_index=4, argv=value optimized out) at kernel/qobject.cpp:3001 #24 0xb6b39c92 in QMetaObject::activate (sender=0x871cd38, m=0xb6c0e944, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3071 #25 0xb6b41c2d in QSingleShotTimer::timeout (this=0x871cd38) at .moc/debug-shared/qtimer.moc:74 #26 0xb6b41d26 in QSingleShotTimer::timerEvent (this=0x871cd38) at kernel/qtimer.cpp:300 #27 0xb6b35296 in QObject::event (this=0x871cd38, e=0xbfe9a4e8) at kernel/qobject.cpp:1096 #28 0xb585c8a4 in QApplicationPrivate::notify_helper (this=0x805f160, receiver=0x871cd38, e=0xbfe9a4e8) at kernel/qapplication.cpp:3772 #29 0xb5860a75 in QApplication::notify (this=0xbfe9a778, receiver=0x871cd38, e=0xbfe9a4e8) at kernel/qapplication.cpp:3366 #30 0xb71826c3 in KApplication::notify (this=0xbfe9a778, receiver=0x871cd38, event=0xbfe9a4e8)
[Bug 143816] When editing preferences Kontact crashes and caused the signal 11 (SIGSEV)
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=143816 Regnaron web de changed: What|Removed |Added CC||Regnaron web de Status|UNCONFIRMED |RESOLVED Resolution||DUPLICATE --- Additional Comments From Regnaron web de 2008-08-07 20:29 --- Looks like the same as bug #167386. As that one has far more input than this one, closing this one as a duplicate of bug #167386 *** This bug has been marked as a duplicate of 167386 *** ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 168519] Konrtact crashes if I try to send a bug report after opening any message
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=168519 Regnaron web de changed: What|Removed |Added CC||Regnaron web de Status|UNCONFIRMED |NEW everconfirmed|0 |1 --- Additional Comments From Regnaron web de 2008-08-07 21:09 --- Confirmed on KDE-4.1 with the following backtrace: Application: Kontact (kontact), signal SIGABRT [Thread debugging using libthread_db enabled] [New Thread 0xb4d37720 (LWP 4328)] [New Thread 0xb0eb8b90 (LWP 4339)] [KCrash handler] #6 0xe424 in __kernel_vsyscall () #7 0xb53d9b91 in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #8 0xb53db378 in *__GI_abort () at abort.c:88 #9 0xb69ef097 in qt_message_output (msgType=QtFatalMsg, buf=0xbf92b64c Fatal error: you need to have a KComponentData object before\nyou do anything that requires it! Examples of this are config\nobjects, standard directories or translations.) at global/qglobal.cpp:2058 #10 0xb69ef14f in qFatal ( msg=0xb6e37bdc Fatal error: you need to have a KComponentData object before\nyou do anything that requires it! Examples of this are config\nobjects, standard directories or translations.) at global/qglobal.cpp:2260 #11 0xb6d6d952 in KGlobal::activeComponent () at /var/tmp/portage/kde-base/kdelibs-4.1.0/work/kdelibs-4.1.0/kdecore/kernel/kglobal.cpp:175 #12 0xb7066e68 in KBugReport (this=0x88946f0, _parent=0x81469b8, modal=false, aboutData=0x0) at /var/tmp/portage/kde-base/kdelibs-4.1.0/work/kdelibs-4.1.0/kdeui/dialogs/kbugreport.cpp:101 #13 0xb7196a39 in KHelpMenu::reportBug (this=0x81d7558) at /var/tmp/portage/kde-base/kdelibs-4.1.0/work/kdelibs-4.1.0/kdeui/widgets/khelpmenu.cpp:304 #14 0xb71970aa in KHelpMenu::qt_metacall (this=0x81d7558, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0xbf92dbfc) at /var/tmp/portage/kde-base/kdelibs-4.1.0/work/kdelibs_build/kdeui/khelpmenu.moc:85 #15 0xb6b02530 in QMetaObject::activate (sender=0x81ffd70, from_signal_index=value optimized out, to_signal_index=6, argv=value optimized out) at kernel/qobject.cpp:3001 #16 0xb6b02a4a in QMetaObject::activate (sender=0x81ffd70, m=0xb5ff59f8, from_local_signal_index=1, to_local_signal_index=2, argv=0xbf92dbfc) at kernel/qobject.cpp:3091 #17 0xb581ec3f in QAction::triggered (this=0x81ffd70, _t1=false) at .moc/debug-shared/moc_qaction.cpp:216 #18 0xb581f4d4 in QAction::activate (this=0x81ffd70, event=QAction::Trigger) at kernel/qaction.cpp:1119 #19 0xb5c1d4d8 in QMenuPrivate::activateAction (this=0x82500a8, action=0x81ffd70, action_e=QAction::Trigger, self=true) at widgets/qmenu.cpp:1005 #20 0xb5c1f920 in QMenu::mouseReleaseEvent (this=0x82070b8, e=0xbf92e470) at widgets/qmenu.cpp:2160 #21 0xb71abf56 in KMenu::mouseReleaseEvent (this=0x82070b8, e=0xbf92e470) at /var/tmp/portage/kde-base/kdelibs-4.1.0/work/kdelibs-4.1.0/kdeui/widgets/kmenu.cpp:452 #22 0xb587edc2 in QWidget::event (this=0x82070b8, event=0xbf92e470) at kernel/qwidget.cpp:6927 #23 0xb5c1ae38 in QMenu::event (this=0x82070b8, e=0xbf92e470) at widgets/qmenu.cpp:2256 #24 0xb58258a4 in QApplicationPrivate::notify_helper (this=0x805f158, receiver=0x82070b8, e=0xbf92e470) at kernel/qapplication.cpp:3772 #25 0xb5829b60 in QApplication::notify (this=0xbf92ea38, receiver=0x82070b8, e=0xbf92e470) at kernel/qapplication.cpp:3501 #26 0xb70f76c3 in KApplication::notify (this=0xbf92ea38, receiver=0x82070b8, event=0xbf92e470) at /var/tmp/portage/kde-base/kdelibs-4.1.0/work/kdelibs-4.1.0/kdeui/kernel/kapplication.cpp:311 #27 0xb6aecd59 in QCoreApplication::notifyInternal (this=0xbf92ea38, receiver=0x82070b8, event=0xbf92e470) at kernel/qcoreapplication.cpp:587 #28 0xb582b67f in QApplicationPrivate::sendMouseEvent (receiver=0x82070b8, event=0xbf92e470, alienWidget=0x0, nativeWidget=0x82070b8, buttonDown=0xb600cc40, lastMouseReceiver= 0xb600cc44) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218 #29 0xb5890a78 in QETWidget::translateMouseEvent (this=0x82070b8, event=0xbf92e868) at kernel/qapplication_x11.cpp:4067 #30 0xb588f48d in QApplication::x11ProcessEvent (this=0xbf92ea38, event=0xbf92e868) at kernel/qapplication_x11.cpp:3133 #31 0xb58b5ed8 in QEventDispatcherX11::processEvents (this=0x805dc10, flags= 0xbf92e958) at kernel/qeventdispatcher_x11.cpp:134 #32 0xb6aec0d3 in QEventLoop::processEvents (this=0xbf92e9d0, flags= 0xbf92e998) at kernel/qeventloop.cpp:149 #33 0xb6aec246 in QEventLoop::exec (this=0xbf92e9d0, flags= 0xbf92e9d8) at kernel/qeventloop.cpp:200 #34 0xb6aee401 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845 #35
[Bug 127139] KMail crashes when I open this mail
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=127139 Regnaron web de changed: What|Removed |Added CC||Regnaron web de Status|UNCONFIRMED |RESOLVED Resolution||REMIND --- Additional Comments From Regnaron web de 2008-07-28 00:35 --- No crash here either on KDE-3.5.9. Please reopen if someone can reproduce the crash. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 127139] KMail crashes when I open this mail
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=127139 Regnaron web de changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|REMIND | --- Additional Comments From Regnaron web de 2008-07-28 00:36 --- Wanted to close as worksforme... ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 127139] KMail crashes when I open this mail
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=127139 Regnaron web de changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||WORKSFORME --- Additional Comments From Regnaron web de 2008-07-28 00:37 --- Wanted to close as worksforme... ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 161833] Repeated knotify signal 11 sigsev on start.
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=161833 Regnaron web de changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||DUPLICATE --- Additional Comments From Regnaron web de 2008-06-27 07:00 --- *** This bug has been marked as a duplicate of 164859 *** ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 162610] New: Kontact crash after changing layout and panes
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=162610 Summary: Kontact crash after changing layout and panes Product: kmail Version: unspecified Platform: unspecified OS/Version: Linux Status: NEW Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: Regnaron web de Version: 1.9.51 (using 4.00.80 (KDE 4.0.80 = (KDE 4.1 Beta1), compiled sources) Compiler: gcc OS:Linux (i686) release 2.6.24-gentoo-r8 Today, after I did the following steps in Kmail (with an IMAP account), it crashed with the backtrace below. Regrettably I was not able to reproduce this crash so far. I use kdepimlibs r812282 and kdepim r812462 1) Switch standard layout to horizontal 3 pane layout [Configure KMail - Appearance - Layout - Show message preview pane next to message list] 2) Move the borders of the message preview pane 3) Switch from long folder list to short folder list [Configure KMail - Appearance - Layout - Short folder list] 4) read some mail 5) Switch back to standard layout but still keep short folder list 6) move borders of message preview pane 7) Switch back to long folder list Application: Kontact (kontact), signal SIGSEGV Using host libthread_db library /lib/libthread_db.so.1. [Thread debugging using libthread_db enabled] [New Thread 0xb4aba6f0 (LWP 31761)] [New Thread 0xb0865b90 (LWP 31836)] [KCrash handler] #6 0xb18012f5 in KMail::ISubject::notify (this=0x8bbeea4) at /home/kde-devel/kde/src/KDE/kdepim/kmail/isubject.cpp:30 #7 0xb14b4a90 in KMMessage::updateBodyPart (this=0x8bbee88, partSpecifier= 0xbfe37bb0, data= 0x8de7800) at /home/kde-devel/kde/src/KDE/kdepim/kmail/kmmessage.cpp:4178 #8 0xb17dd697 in KMail::ImapJob::slotGetMessageResult (this=0x8ad2ac8, job=0x8d09120) at /home/kde-devel/kde/src/KDE/kdepim/kmail/imapjob.cpp:416 #9 0xb17de374 in KMail::ImapJob::qt_metacall (this=0x8ad2ac8, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfe37ccc) at /home/kde-devel/kde/build/KDE/kdepim/kmail/imapjob.moc:81 #10 0xb7e82530 in QMetaObject::activate () from /usr/lib/qt4/libQtCore.so.4 #11 0xb7e82c92 in QMetaObject::activate () from /usr/lib/qt4/libQtCore.so.4 #12 0xb7bf8d68 in KJob::result (this=0x8d09120, _t1=0x8d09120) at /home/kde-devel/kde/build/KDE/kdelibs/kdecore/kjob.moc:186 #13 0xb7bf92e8 in KJob::emitResult (this=0x8d09120) at /home/kde-devel/kde/src/KDE/kdelibs/kdecore/jobs/kjob.cpp:290 #14 0xb764a91c in KIO::SimpleJob::slotFinished (this=0x8d09120) at /home/kde-devel/kde/src/KDE/kdelibs/kio/kio/job.cpp:491 #15 0xb764aceb in KIO::TransferJob::slotFinished (this=0x8d09120) at /home/kde-devel/kde/src/KDE/kdelibs/kio/kio/job.cpp:961 #16 0xb7651ca3 in KIO::TransferJob::qt_metacall (this=0x8d09120, _c=QMetaObject::InvokeMetaMethod, _id=7, _a=0xbfe37ef8) at /home/kde-devel/kde/build/KDE/kdelibs/kio/jobclasses.moc:336 #17 0xb7e82530 in QMetaObject::activate () from /usr/lib/qt4/libQtCore.so.4 #18 0xb7e82c92 in QMetaObject::activate () from /usr/lib/qt4/libQtCore.so.4 #19 0xb76f8c79 in KIO::SlaveInterface::finished (this=0x876a7b0) at /home/kde-devel/kde/build/KDE/kdelibs/kio/slaveinterface.moc:161 #20 0xb76fa9f4 in KIO::SlaveInterface::dispatch (this=0x876a7b0, _cmd=104, rawdata= 0xbfe380a4) at /home/kde-devel/kde/src/KDE/kdelibs/kio/kio/slaveinterface.cpp:175 #21 0xb76fb581 in KIO::SlaveInterface::dispatch (this=0x876a7b0) at /home/kde-devel/kde/src/KDE/kdelibs/kio/kio/slaveinterface.cpp:90 #22 0xb76ed4ce in KIO::Slave::gotInput (this=0x876a7b0) at /home/kde-devel/kde/src/KDE/kdelibs/kio/kio/slave.cpp:319 #23 0xb76ee93c in KIO::Slave::qt_metacall (this=0x876a7b0, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfe38198) at /home/kde-devel/kde/build/KDE/kdelibs/kio/slave.moc:75 #24 0xb7e82530 in QMetaObject::activate () from /usr/lib/qt4/libQtCore.so.4 #25 0xb7e82c92 in QMetaObject::activate () from /usr/lib/qt4/libQtCore.so.4 #26 0xb7618c33 in KIO::Connection::readyRead (this=0x8677ed8) at /home/kde-devel/kde/build/KDE/kdelibs/kio/connection.moc:84 #27 0xb7619c21 in KIO::ConnectionPrivate::dequeue (this=0x8760488) at /home/kde-devel/kde/src/KDE/kdelibs/kio/kio/connection.cpp:82 #28 0xb761ab43 in KIO::Connection::qt_metacall (this=0x8677ed8, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x8c341d8) at /home/kde-devel/kde/build/KDE/kdelibs/kio/connection.moc:72 #29 0xb7e7c249 in QMetaCallEvent::placeMetaCall () from /usr/lib/qt4/libQtCore.so.4 #30 0xb7e7e309 in QObject::event () from /usr/lib/qt4/libQtCore.so.4 #31 0xb6be98a4 in QApplicationPrivate::notify_helper () from /usr/lib/qt4/libQtGui.so.4 #32 0xb6beda75 in QApplication::notify () from /usr/lib/qt4/libQtGui.so.4 #33 0xb7998be6 in KApplication::notify
[Bug 162611] New: Kontact crash when switching between long and short folder list view in kmail
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=162611 Summary: Kontact crash when switching between long and short folder list view in kmail Product: kmail Version: unspecified Platform: unspecified OS/Version: Linux Status: NEW Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: Regnaron web de Version: 1.9.51 (using 4.00.80 (KDE 4.0.80 = (KDE 4.1 Beta1), compiled sources) Compiler: gcc OS:Linux (i686) release 2.6.24-gentoo-r8 Steps to reproduce: 1) Open Kmail (needs to be done via kontact. I cannot reproduce this with the kmail standalone app) 2) Switch from long folder list to short folder list [Configure KMail - Appearance - Layout - Short folder list] (works vice versa too) 3) Close kontact and see it crash with the following backtrace (kdepimlibs r812282 and kdepim r812462) Remark: The backtrace I get looks very similar to the backtraces of bug #160920 and bug #102470. However, as I end up with this backtrace via a completely differnt set of actions, I post this in a new bugreport. Application: Kontact (kontact), signal SIGSEGV Using host libthread_db library /lib/libthread_db.so.1. [Thread debugging using libthread_db enabled] [New Thread 0xb4ae36f0 (LWP 32087)] [KCrash handler] #6 0xb6c6caa3 in ?? () from /usr/lib/qt4/libQtGui.so.4 #7 0xb6c5a3e1 in QWidget::removeAction () from /usr/lib/qt4/libQtGui.so.4 #8 0xb7ad5d1f in KXMLGUI::ActionList::unplug (this=0x873ba14, container=0x8723290) at /home/kde-devel/kde/src/KDE/kdelibs/kdeui/xmlgui/kxmlguifactory_p.cpp:52 #9 0xb7ad5ee5 in KXMLGUI::ContainerNode::unplugClient (this=0x873b9a8, client=0x873ba10) at /home/kde-devel/kde/src/KDE/kdelibs/kdeui/xmlgui/kxmlguifactory_p.cpp:438 #10 0xb7ad611f in KXMLGUI::ContainerNode::unplugActions (this=0x873b9a8, state= 0x8227640) at /home/kde-devel/kde/src/KDE/kdelibs/kdeui/xmlgui/kxmlguifactory_p.cpp:417 #11 0xb7ad61c7 in KXMLGUI::ContainerNode::destruct (this=0x873b9a8, element= 0xbfce1e4c, state= 0x8227640) at /home/kde-devel/kde/src/KDE/kdelibs/kdeui/xmlgui/kxmlguifactory_p.cpp:326 #12 0xb7ad63cf in KXMLGUI::ContainerNode::destructChildren (this=0x822bcc8, element= 0xbfce1ecc, state= 0x8227640) at /home/kde-devel/kde/src/KDE/kdelibs/kdeui/xmlgui/kxmlguifactory_p.cpp:369 #13 0xb7ad61b5 in KXMLGUI::ContainerNode::destruct (this=0x822bcc8, element= 0xbfce1ecc, state= 0x8227640) at /home/kde-devel/kde/src/KDE/kdelibs/kdeui/xmlgui/kxmlguifactory_p.cpp:324 #14 0xb7ad63cf in KXMLGUI::ContainerNode::destructChildren (this=0x8227870, element= 0xbfce1f88, state= 0x8227640) at /home/kde-devel/kde/src/KDE/kdelibs/kdeui/xmlgui/kxmlguifactory_p.cpp:369 #15 0xb7ad61b5 in KXMLGUI::ContainerNode::destruct (this=0x8227870, element= 0xbfce1f88, state= 0x8227640) at /home/kde-devel/kde/src/KDE/kdelibs/kdeui/xmlgui/kxmlguifactory_p.cpp:324 #16 0xb7ad079b in KXMLGUIFactory::removeClient (this=0x8228480, client=0x82d6204) at /home/kde-devel/kde/src/KDE/kdelibs/kdeui/xmlgui/kxmlguifactory.cpp:337 #17 0xb759ce5d in KParts::MainWindow::createGUI (this=0x80a60d8, part=0x0) at /home/kde-devel/kde/src/KDE/kdelibs/kparts/mainwindow.cpp:106 #18 0xb60274e7 in ~MainWindow (this=0x80a60d8) at /home/kde-devel/kde/src/KDE/kdepim/kontact/src/mainwindow.cpp:236 #19 0xb7ea52b2 in qDeleteInEventHandler () from /usr/lib/qt4/libQtCore.so.4 #20 0xb7ea72ca in QObject::event () from /usr/lib/qt4/libQtCore.so.4 #21 0xb6c6b434 in QWidget::event () from /usr/lib/qt4/libQtGui.so.4 #22 0xb6fde05e in QMainWindow::event () from /usr/lib/qt4/libQtGui.so.4 #23 0xb7a8697f in KMainWindow::event (this=0x80a60d8, ev=0x84fb3b8) at /home/kde-devel/kde/src/KDE/kdelibs/kdeui/widgets/kmainwindow.cpp:1002 #24 0xb7ac6abf in KXmlGuiWindow::event (this=0x80a60d8, ev=0x84fb3b8) at /home/kde-devel/kde/src/KDE/kdelibs/kdeui/xmlgui/kxmlguiwindow.cpp:122 #25 0xb6c128a4 in QApplicationPrivate::notify_helper () from /usr/lib/qt4/libQtGui.so.4 #26 0xb6c169b2 in QApplication::notify () from /usr/lib/qt4/libQtGui.so.4 #27 0xb79c1be6 in KApplication::notify (this=0xbfce27dc, receiver=0x80a60d8, event=0x84fb3b8) at /home/kde-devel/kde/src/KDE/kdelibs/kdeui/kernel/kapplication.cpp:311 #28 0xb7e95d59 in QCoreApplication::notifyInternal () from /usr/lib/qt4/libQtCore.so.4 #29 0xb7e97006 in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib/qt4/libQtCore.so.4 #30 0xb7e9735d in QCoreApplication::sendPostedEvents () from /usr/lib/qt4/libQtCore.so.4 #31 0xb7e97431 in QCoreApplication::exec () from /usr/lib/qt4/libQtCore.so.4 #32 0xb6c1223f in QApplication::exec () from /usr/lib/qt4/libQtGui.so.4 #33 0x0804b2d9 in main
[Bug 160002] KMail crashes on exit
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=160002 Regnaron web de changed: What|Removed |Added CC||Regnaron web de Status|UNCONFIRMED |NEW everconfirmed|0 |1 --- Additional Comments From Regnaron web de 2008-04-08 03:09 --- I think I just stumbled over this crash (at least this assertion). Kontact (kdepimlibs r794328, kdepim r783669) just crashed with the backtrace below when I tried to close it. Backtrace: Application: Kontact (kontact), signal SIGABRT Using host libthread_db library /lib/libthread_db.so.1. [Thread debugging using libthread_db enabled] [New Thread 0xb4e7b6d0 (LWP 10115)] [KCrash handler] #14 0xe410 in __kernel_vsyscall () #15 0xb53991f1 in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #16 0xb539a9b8 in *__GI_abort () at abort.c:88 #17 0xb53927d5 in *__GI___assert_fail (assertion=0xb3270f3b mySelf, file=0xb327088c /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmkernel.cpp, line=2052, function=0xb3271b80 static KMKernel* KMKernel::self()) at assert.c:78 #18 0xb30614f7 in KMKernel::self () at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmkernel.cpp:2052 #19 0xb2f13159 in KMFolderComboBox::createFolderList (this=0x84c9638, names=0xbfcabbf0, folders=0xbfcabbec) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmfoldercombobox.cpp:65 #20 0xb2f13437 in KMFolderComboBox::getFolder (this=0x84c9638) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmfoldercombobox.cpp:142 #21 0xb2f583d5 in KMComposeWin::writeConfig (this=0x83fe1a0) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmcomposewin.cpp:652 #22 0xb2f593d1 in ~KMComposeWin (this=0x83fe1a0) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmcomposewin.cpp:383 #23 0x0804bb26 in qDeleteAllQListKMainWindow*::const_iterator ( begin= 0xbfcabd28, end= 0xbfcabd24) at /usr/include/qt4/QtCore/qalgorithms.h:352 #24 0x0804bb92 in qDeleteAllQListKMainWindow* (c= 0xbfcabe64) at /usr/include/qt4/QtCore/qalgorithms.h:360 #25 0x0804b4df in main (argc=1, argv=0xbfcabf14) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kontact/src/main.cpp:166 #26 0xb5385fdc in __libc_start_main (main=0x804ac20 main, argc=1, ubp_av=0xbfcabf14, init=0x804c200 __libc_csu_init, fini=0x804c1f0 __libc_csu_fini, rtld_fini=0xb7efa100 _dl_fini, stack_end=0xbfcabf0c) at libc-start.c:229 #27 0x0804a851 in _start () #0 0xe410 in __kernel_vsyscall () ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 156292] Crash after starting the second time
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=156292 Regnaron web de changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||WORKSFORME --- Additional Comments From Regnaron web de 2008-03-19 01:30 --- I did not experience this crash over the last couple of weeks, so I assume it got fixed. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 156528] Crash when applying all filters to an IMAP folder
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=156528 Regnaron web de changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||WORKSFORME --- Additional Comments From Regnaron web de 2008-03-19 01:37 --- I cannot reproduce this crash in a current SVN build any longer, so I assume it was fixed ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 156990] Assertion failure in ImapAccountBase::makeConnection
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=156990 --- Additional Comments From Regnaron web de 2008-03-19 01:54 --- This bug is still valid in a current SVN build ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 156991] assertion !transferInProgress( serNum ) failed
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=156991 --- Additional Comments From Regnaron web de 2008-03-19 01:56 --- Still valid in a current SVN version ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 157562] New: Crash in Contact-Custom pages
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=157562 Summary: Crash in Contact-Custom pages Product: kontact Version: unspecified Platform: unspecified OS/Version: Linux Status: NEW Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: Regnaron web de Version: unknown (using 4.00.61 (KDE 4.0.61 = 20080207), Gentoo) Compiler: i686-pc-linux-gnu-gcc OS:Linux (i686) release 2.6.23-gentoo-r6 Steps to reproduce: 1) Start kontact 2) Click on Settings-Configure Kontact 3) Click on Contact-Custom pages 4) See kontact crash with the following backtrace: Application: Kontact (kontact), signal SIGABRT Using host libthread_db library /lib/libthread_db.so.1. [Thread debugging using libthread_db enabled] [New Thread 0xb531a6d0 (LWP 20083)] [KCrash handler] #6 0xe410 in __kernel_vsyscall () #7 0xb56b91f1 in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #8 0xb56ba9b8 in *__GI_abort () at abort.c:88 #9 0xb7d92265 in qt_message_output (msgType=QtFatalMsg, buf=0xbfff3e5c ASSERT: \!isEmpty()\ in file /usr/include/qt4/QtCore/qlist.h, line 242) at global/qglobal.cpp:2160 #10 0xb7d9232a in qFatal (msg=0xb7e9987c ASSERT: \%s\ in file %s, line %d) at global/qglobal.cpp:2392 #11 0xb7d92555 in qt_assert (assertion=0xb16c28fc !isEmpty(), file=0xb16c29b0 /usr/include/qt4/QtCore/qlist.h, line=242) at global/qglobal.cpp:1917 #12 0xb16c232a in QListQString::first (this=0xbfff5efc) at /usr/include/qt4/QtCore/qlist.h:242 #13 0xb16c1119 in KCMKabCustomFields::kabLocalDir (this=0x80a90b8) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kaddressbook/kcmconfigs/kcmkabcustomfields.cpp:75 #14 0xb16c121f in KCMKabCustomFields::localUiDir (this=0x80a90b8) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kaddressbook/kcmconfigs/kcmkabcustomfields.cpp:47 #15 0xb61a2843 in KPIM::KCMDesignerFields::delayedInit (this=0x80a90b8) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/libkdepim/kcmdesignerfields.cpp:174 #16 0xb61a29be in KPIM::KCMDesignerFields::qt_metacall (this=0x80a90b8, _c=QMetaObject::InvokeMetaMethod, _id=40, _a=0xbfff6454) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim_build/libkdepim/kcmdesignerfields.moc:80 #17 0xb7e781f4 in QMetaObject::activate (sender=0x88399d0, from_signal_index=4, to_signal_index=4, argv=value optimized out) at kernel/qobject.cpp:3081 #18 0xb7e78d94 in QMetaObject::activate (sender=0x88399d0, m=0xb7f16c64, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3140 #19 0xb7e813c3 in QSingleShotTimer::timeout (this=0x88399d0) at .moc/debug-shared/qtimer.moc:73 #20 0xb7e8140c in QSingleShotTimer::timerEvent (this=0x88399d0) at kernel/qtimer.cpp:296 #21 0xb7e76269 in QObject::event (this=0x88399d0, e=0x4e73) at kernel/qobject.cpp:1086 #22 0xb6d2fe8a in QApplicationPrivate::notify_helper (this=0x80647b0, receiver=0x88399d0, e=0xbfff6988) at kernel/qapplication.cpp:3556 #23 0xb6d3177a in QApplication::notify (this=0xbfff6c10, receiver=0x88399d0, e=0xbfff6988) at kernel/qapplication.cpp:3115 #24 0xb79e4763 in KApplication::notify (this=0xbfff6c10, receiver=0x88399d0, event=0xbfff6988) at /var/tmp/portage/kde-base/kdelibs-.4/work/kdelibs-.4/kdeui/kernel/kapplication.cpp:311 #25 0xb7e64d7b in QCoreApplication::notifyInternal (this=0xbfff6c10, receiver=0x88399d0, event=0xbfff6988) at kernel/qcoreapplication.cpp:530 #26 0xb7e8defb in QTimerInfoList::activateTimers (this=0x8064f2c) at kernel/qcoreapplication.h:200 #27 0xb7e8dfd1 in QEventDispatcherUNIX::activateTimers (this=0x805f170) at kernel/qeventdispatcher_unix.cpp:828 #28 0xb7e8e9ab in QEventDispatcherUNIX::processEvents (this=0x805f170, flags= 0xbfff6b08) at kernel/qeventdispatcher_unix.cpp:890 #29 0xb6db9cce in QEventDispatcherX11::processEvents (this=0x805f170, flags= 0xbfff6b34) at kernel/qeventdispatcher_x11.cpp:145 #30 0xb7e64191 in QEventLoop::processEvents (this=0xbfff6ba0, flags= 0xbfff6b68) at kernel/qeventloop.cpp:140 #31 0xb7e6429a in QEventLoop::exec (this=0xbfff6ba0, flags= 0xbfff6ba8) at kernel/qeventloop.cpp:186 #32 0xb7e66626 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:759 #33 0xb6d2f487 in QApplication::exec () at kernel/qapplication.cpp:3053 #34 0x0804b3f5 in main (argc=1, argv=0xbfff6da4) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kontact/src/main.cpp:162 #35 0xb56a5fdc in __libc_start_main (main=0x804ab60 main, argc=1, ubp_av=0xbfff6da4, init=0x804c180 __libc_csu_init, fini=0x804c170 __libc_csu_fini, rtld_fini=0xb7f28100 _dl_fini, stack_end=0xbfff6d9c) at libc-start.c:229 #36
[Bug 156990] New: simultaneously saving mail and logging in to IMAP account crashes kmail
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=156990 Summary: simultaneously saving mail and logging in to IMAP account crashes kmail Product: kmail Version: 1.9.50 Platform: unspecified OS/Version: Linux Status: NEW Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: Regnaron web de Version: 1.9.50 (using 4.00.60 (KDE 4.0.60 = 20080129), Gentoo) Compiler: i686-pc-linux-gnu-gcc OS:Linux (i686) release 2.6.23-gentoo-r3 Steps to reproduce: 1) Open kmail 2) Right click on a mail and select save as (leave window as is) 3) Check your mails (IMAP account) [you need to be asked for your username and password in order to make this work] 4) Click ok on the popup that asks for your username and password 5) See kmail crash Note: When you cancel the login procedure (click cancel twice), kmail does not crash. Backtrace: Application: KMail (kmail), signal SIGABRT Using host libthread_db library /lib/libthread_db.so.1. [Thread debugging using libthread_db enabled] [New Thread 0xb4a616d0 (LWP 14669)] [KCrash handler] #6 0xe410 in __kernel_vsyscall () #7 0xb50211f1 in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #8 0xb50229b8 in *__GI_abort () at abort.c:88 #9 0xb7d66265 in qt_message_output (msgType=QtFatalMsg, buf=0xbfad7e2c ASSERT: \!mSlave\ in file /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/imapaccountbase.cpp, line 299) at global/qglobal.cpp:2160 #10 0xb7d6632a in qFatal (msg=0xb7e6d87c ASSERT: \%s\ in file %s, line %d) at global/qglobal.cpp:2392 #11 0xb7d66555 in qt_assert (assertion=0xb78fb072 !mSlave, file=0xb78fa5c8 /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/imapaccountbase.cpp, line=299) at global/qglobal.cpp:1917 #12 0xb76e59c8 in KMail::ImapAccountBase::makeConnection (this=0x8208ff0) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/imapaccountbase.cpp:299 #13 0xb76ec508 in KMAcctImap::makeConnection (this=0x6) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmacctimap.cpp:546 #14 0xb76ed47a in KMAcctImap::processNewMail (this=0x8208ff0, interactive=true) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmacctimap.cpp:264 #15 0xb7694340 in KMail::AccountManager::processNextCheck (this=0x81fab78, _newMail=false) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/accountmanager.cpp:192 #16 0xb7694466 in KMail::AccountManager::singleCheckMail (this=0x81fab78, account=0x8208ff0, interactive=true) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/accountmanager.cpp:119 #17 0xb76947da in KMail::AccountManager::checkMail (this=0x81fab78, _interactive=true) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/accountmanager.cpp:310 #18 0xb77d706e in KMMainWidget::slotCheckMail (this=0x821e0d8) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmmainwidget.cpp:1035 #19 0xb77dbcd8 in KMMainWidget::qt_metacall (this=0x821e0d8, _c=QMetaObject::InvokeMetaMethod, _id=31, _a=0xbfada74c) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim_build/kmail/kmmainwidget.moc:335 #20 0xb7e4c1f4 in QMetaObject::activate (sender=0x82d6e20, from_signal_index=9, to_signal_index=10, argv=value optimized out) at kernel/qobject.cpp:3081 #21 0xb7e4c5e2 in QMetaObject::activate (sender=0x82d6e20, m=0xb5e114c0, from_local_signal_index=5, to_local_signal_index=6, argv=0xbfada74c) at kernel/qobject.cpp:3160 #22 0xb56bb95d in QAction::activated (this=0x82d6e20, _t1=-234) at .moc/debug-shared/moc_qaction.cpp:228 #23 0xb56bc4d6 in QAction::activate (this=0x82d6e20, event=QAction::Trigger) at kernel/qaction.cpp:1117 #24 0xb5aea000 in QToolButton::nextCheckState (this=0x8332100) at ../../include/QtGui/../../src/gui/kernel/qaction.h:188 #25 0xb5a0b74d in QAbstractButtonPrivate::click (this=0x8332198) at widgets/qabstractbutton.cpp:513 #26 0xb5a0b9ee in QAbstractButton::mouseReleaseEvent (this=0x8332100, e=0xbfadae84) at widgets/qabstractbutton.cpp:1101 #27 0xb5aea0fc in QToolButton::mouseReleaseEvent (this=0x8332100, e=0xbfadae84) at widgets/qtoolbutton.cpp:656 #28 0xb57159a5 in QWidget::event (this=0x8332100, event=0xbfadae84) at kernel/qwidget.cpp:6138 #29 0xb5a0a4e3 in QAbstractButton::event (this=0x8332100, e=0x394d) at widgets/qabstractbutton.cpp:1063 #30 0xb5ae9934 in QToolButton::event (this=0x8332100, e=0xbfadae84) at widgets/qtoolbutton.cpp:1073 #31 0xb56c2e8a in QApplicationPrivate::notify_helper (this=0x8065610, receiver=0x8332100, e=0xbfadae84) at
[Bug 156991] New: assertion !transferInProgress( serNum ) failed
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=156991 Summary: assertion !transferInProgress( serNum ) failed Product: kmail Version: 1.9.50 Platform: unspecified OS/Version: Linux Status: NEW Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: Regnaron web de Version: 1.9.50 (using 4.00.60 (KDE 4.0.60 = 20080129), Gentoo) Compiler: i686-pc-linux-gnu-gcc OS:Linux (i686) release 2.6.23-gentoo-r3 Steps to reproduce: 1) save mail 2) right click on mail - open with - other - type kmail 3) Save mail in Draft folder (is on IMAP account) 4) You are asked for username / password of the IMAP account 5) Hit Cancel on that popup twice 6) See kmail crash with the following backtrace: Application: KMail (kmail), signal SIGABRT Using host libthread_db library /lib/libthread_db.so.1. [Thread debugging using libthread_db enabled] [New Thread 0xb4ad36d0 (LWP 21649)] [KCrash handler] #6 0xe410 in __kernel_vsyscall () #7 0xb50931f1 in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #8 0xb50949b8 in *__GI_abort () at abort.c:88 #9 0xb7dd8265 in qt_message_output (msgType=QtFatalMsg, buf=0xbf9e6e8c ASSERT: \!transferInProgress( serNum )\ in file /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/messageproperty.cpp, line 164) at global/qglobal.cpp:2160 #10 0xb7dd832a in qFatal (msg=0xb7edf87c ASSERT: \%s\ in file %s, line %d) at global/qglobal.cpp:2392 #11 0xb7dd8555 in qt_assert ( assertion=0xb7963c41 !transferInProgress( serNum ), file=0xb7963bec /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/messageproperty.cpp, line=164) at global/qglobal.cpp:1917 #12 0xb76fdea1 in KMail::MessageProperty::forget (msgBase=0x841ac80) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/messageproperty.cpp:164 #13 0xb77483bd in ~KMMsgBase (this=0x841ac80) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmmsgbase.cpp:88 #14 0xb760e215 in ~KMMessage (this=0x841ac80) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmmessage.cpp:216 #15 0xb7748d13 in KMMsgList::clear (this=0x820863c, doDelete=true, syncDict=false) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmmsglist.cpp:41 #16 0xb77978ea in KMFolderMaildir::close (this=0x82085e8, aForced=true) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmfoldermaildir.cpp:258 #17 0xb76d5666 in KMFolder::close (this=0x81fb028, owner=0xb7976a19 kmkernel, force=true) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmfolder.cpp:502 #18 0xb77a835b in KMKernel::cleanup (this=0xbf9e9030) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmkernel.cpp:1617 #19 0x0804a8e8 in main (argc=) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/main.cpp:133 #20 0xb507ffdc in __libc_start_main (main=0x804a720 main, argc=4, ubp_av=0xbf9e91c4, init=0x804af60 __libc_csu_init, fini=0x804af50 __libc_csu_fini, rtld_fini=0xb7f6e100 _dl_fini, stack_end=0xbf9e91bc) at libc-start.c:229 #21 0x0804a021 in _start () #0 0xe410 in __kernel_vsyscall () ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 156990] simultaneously saving mail and logging in to IMAP account crashes kmail
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=156990 --- Additional Comments From Regnaron web de 2008-01-30 23:59 --- Another way of triggering this crash is: 1) Save some mail on your HDD 2) Open that mail with kmail by right-clicking - open with - other - kmail 3) Save mail into Drafts folder (on IMAP account) 4) You get asked for your username / password for that account 5) Press ok without entering your password 6) See kmail crash with the following backtrace: Application: KMail (kmail), signal SIGABRT Using host libthread_db library /lib/libthread_db.so.1. [Thread debugging using libthread_db enabled] [New Thread 0xb4b366d0 (LWP 21846)] [KCrash handler] #6 0xe410 in __kernel_vsyscall () #7 0xb50f61f1 in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #8 0xb50f79b8 in *__GI_abort () at abort.c:88 #9 0xb7e3b265 in qt_message_output (msgType=QtFatalMsg, buf=0xbfd9f8cc ASSERT: \!mSlave\ in file /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/imapaccountbase.cpp, line 299) at global/qglobal.cpp:2160 #10 0xb7e3b32a in qFatal (msg=0xb7f4287c ASSERT: \%s\ in file %s, line %d) at global/qglobal.cpp:2392 #11 0xb7e3b555 in qt_assert (assertion=0xb79d0072 !mSlave, file=0xb79cf5c8 /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/imapaccountbase.cpp, line=299) at global/qglobal.cpp:1917 #12 0xb77ba9c8 in KMail::ImapAccountBase::makeConnection (this=0x81fc9d0) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/imapaccountbase.cpp:299 #13 0xb77c1508 in KMAcctImap::makeConnection (this=0x6) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmacctimap.cpp:546 #14 0xb77d6265 in KMFolderImap::checkValidity (this=0x8211608) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmfolderimap.cpp:1068 #15 0xb77d6a42 in KMFolderImap::getFolder (this=0x8211608, force=false) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmfolderimap.cpp:1259 #16 0xb770f3c4 in KMComposeWin::saveDraftOrTemplate (this=0x820b6c8, folderName= 0xbfda1da0, msg=value optimized out) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmcomposewin.cpp:3674 #17 0xb77173c4 in KMComposeWin::slotContinueDoSend (this=0x820b6c8, sentOk=false) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmcomposewin.cpp:3701 #18 0xb77287e4 in KMComposeWin::qt_metacall (this=0x820b6c8, _c=QMetaObject::InvokeMetaMethod, _id=148, _a=0xbfda22fc) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim_build/kmail/kmcomposewin.moc:355 #19 0xb7f211f4 in QMetaObject::activate (sender=0x820b6c8, from_signal_index=47, to_signal_index=47, argv=value optimized out) at kernel/qobject.cpp:3081 #20 0xb7f21d94 in QMetaObject::activate (sender=0x820b6c8, m=0xb7a1944c, local_signal_index=0, argv=0xbfda22fc) at kernel/qobject.cpp:3140 #21 0xb7725d67 in KMComposeWin::applyChangesDone (this=0x820b6c8, _t1=true) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim_build/kmail/kmcomposewin.moc:371 #22 0xb7725dc8 in KMComposeWin::slotComposerDone (this=0x820b6c8, rc=true) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmcomposewin.cpp:2087 #23 0xb77287ca in KMComposeWin::qt_metacall (this=0x820b6c8, _c=QMetaObject::InvokeMetaMethod, _id=147, _a=0xbfda283c) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim_build/kmail/kmcomposewin.moc:354 #24 0xb7f211f4 in QMetaObject::activate (sender=0x836c3d8, from_signal_index=4, to_signal_index=4, argv=value optimized out) at kernel/qobject.cpp:3081 #25 0xb7f21d94 in QMetaObject::activate (sender=0x836c3d8, m=0xb7a24224, local_signal_index=0, argv=0xbfda283c) at kernel/qobject.cpp:3140 #26 0xb78f4a47 in MessageComposer::done (this=0x836c3d8, _t1=true) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim_build/kmail/messagecomposer.moc:79 #27 0xb78ff247 in MessageComposer::emitDone (this=0x836c3d8, ok=true) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/messagecomposer.cpp:410 #28 0xb78ff2af in MessageComposer::doNextJob (this=0x836c3d8) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/messagecomposer.cpp:386 #29 0xb78ff438 in MessageComposer::slotDoNextJob (this=0x836c3d8) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/messagecomposer.cpp:433 #30 0xb78ff4c9 in MessageComposer::qt_metacall (this=0x836c3d8, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfda2d74) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim_build/kmail/messagecomposer.moc:68 #31 0xb7f211f4 in QMetaObject::activate (sender=0x8370e78, from_signal_index=4, to_signal_index=4, argv=value optimized out) at kernel/qobject.cpp:3081 #32
[Bug 156997] New: crash when trying to save mail to IMAP folder with no access
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=156997 Summary: crash when trying to save mail to IMAP folder with no access Product: kmail Version: 1.9.50 Platform: unspecified OS/Version: Linux Status: NEW Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: Regnaron web de Version: 1.9.50 (using 4.00.60 (KDE 4.0.60 = 20080129), Gentoo) Compiler: i686-pc-linux-gnu-gcc OS:Linux (i686) release 2.6.23-gentoo-r3 Steps to reproduce: 1) Set your account preferences so that you drafts folder is on an IMAP account 2) Create a new mail 3) Save that mail to Drafts folder 4) You are asked for your username / password for the IMAP folder 5) Just click ok without providing password 6) See kmail crash with the following backtrace: Application: KMail (kmail), signal SIGABRT Using host libthread_db library /lib/libthread_db.so.1. [Thread debugging using libthread_db enabled] [New Thread 0xb4b366d0 (LWP 21846)] [KCrash handler] #6 0xe410 in __kernel_vsyscall () #7 0xb50f61f1 in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #8 0xb50f79b8 in *__GI_abort () at abort.c:88 #9 0xb7e3b265 in qt_message_output (msgType=QtFatalMsg, buf=0xbfd9f8cc ASSERT: \!mSlave\ in file /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/imapaccountbase.cpp, line 299) at global/qglobal.cpp:2160 #10 0xb7e3b32a in qFatal (msg=0xb7f4287c ASSERT: \%s\ in file %s, line %d) at global/qglobal.cpp:2392 #11 0xb7e3b555 in qt_assert (assertion=0xb79d0072 !mSlave, file=0xb79cf5c8 /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/imapaccountbase.cpp, line=299) at global/qglobal.cpp:1917 #12 0xb77ba9c8 in KMail::ImapAccountBase::makeConnection (this=0x81fc9d0) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/imapaccountbase.cpp:299 #13 0xb77c1508 in KMAcctImap::makeConnection (this=0x6) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmacctimap.cpp:546 #14 0xb77d6265 in KMFolderImap::checkValidity (this=0x8211608) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmfolderimap.cpp:1068 #15 0xb77d6a42 in KMFolderImap::getFolder (this=0x8211608, force=false) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmfolderimap.cpp:1259 #16 0xb770f3c4 in KMComposeWin::saveDraftOrTemplate (this=0x820b6c8, folderName= 0xbfda1da0, msg=value optimized out) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmcomposewin.cpp:3674 #17 0xb77173c4 in KMComposeWin::slotContinueDoSend (this=0x820b6c8, sentOk=false) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmcomposewin.cpp:3701 #18 0xb77287e4 in KMComposeWin::qt_metacall (this=0x820b6c8, _c=QMetaObject::InvokeMetaMethod, _id=148, _a=0xbfda22fc) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim_build/kmail/kmcomposewin.moc:355 #19 0xb7f211f4 in QMetaObject::activate (sender=0x820b6c8, from_signal_index=47, to_signal_index=47, argv=value optimized out) at kernel/qobject.cpp:3081 #20 0xb7f21d94 in QMetaObject::activate (sender=0x820b6c8, m=0xb7a1944c, local_signal_index=0, argv=0xbfda22fc) at kernel/qobject.cpp:3140 #21 0xb7725d67 in KMComposeWin::applyChangesDone (this=0x820b6c8, _t1=true) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim_build/kmail/kmcomposewin.moc:371 #22 0xb7725dc8 in KMComposeWin::slotComposerDone (this=0x820b6c8, rc=true) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmcomposewin.cpp:2087 #23 0xb77287ca in KMComposeWin::qt_metacall (this=0x820b6c8, _c=QMetaObject::InvokeMetaMethod, _id=147, _a=0xbfda283c) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim_build/kmail/kmcomposewin.moc:354 #24 0xb7f211f4 in QMetaObject::activate (sender=0x836c3d8, from_signal_index=4, to_signal_index=4, argv=value optimized out) at kernel/qobject.cpp:3081 #25 0xb7f21d94 in QMetaObject::activate (sender=0x836c3d8, m=0xb7a24224, local_signal_index=0, argv=0xbfda283c) at kernel/qobject.cpp:3140 #26 0xb78f4a47 in MessageComposer::done (this=0x836c3d8, _t1=true) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim_build/kmail/messagecomposer.moc:79 #27 0xb78ff247 in MessageComposer::emitDone (this=0x836c3d8, ok=true) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/messagecomposer.cpp:410 #28 0xb78ff2af in MessageComposer::doNextJob (this=0x836c3d8) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/messagecomposer.cpp:386 #29 0xb78ff438 in
[Bug 156990] simultaneously saving mail and logging in to IMAP account crashes kmail
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=156990 --- Additional Comments From Regnaron web de 2008-01-31 00:13 --- Oops, forget about my last comment. I just recognized that the second crash does have a quite different backtrace after line 14, so I just opened an own bug for that crash. (bug #156997) ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 156834] KMail crashes when opening encrypted message (KMReaderWin::decryptMessage)
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=156834 --- Additional Comments From Regnaron web de 2008-01-28 13:52 --- Created an attachment (id=2) -- (http://bugs.kde.org/attachment.cgi?id=2action=view) Sample mail for crashing KMail with bug 156834 (see comment #1) Import this mail into your KMail outbox as described in comment #1 in order to reproduce this bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 156834] New: KMail crashes when opening encrypted message (KMReaderWin::decryptMessage)
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=156834 Summary: KMail crashes when opening encrypted message (KMReaderWin::decryptMessage) Product: kmail Version: 1.9.50 Platform: unspecified OS/Version: Linux Status: NEW Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: Regnaron web de Version: 1.9.50 (using 4.00.80 (KDE 4.0.80 = 20080104), Gentoo) Compiler: i686-pc-linux-gnu-gcc OS:Linux (i686) release 2.6.23-gentoo-r3 Steps to reproduce: 1) Create a new message. 2) Encrypt that message. (OpenPGP) 3) Store the message in the queue for later sending (message is going to be encrypted now) 4) Double click on the message in your outbox 5) See KMail crash There also is another problem with this bug: KMail does not just crash, the encrypted Mail is gone after the next reboot. So at least I also experience a data loss here. I am running kdepimlibs r765208 and kdepim r765208. Note: If I store the mail on my hard disk, I can easily open it directly with KMail. (- open with...) The backtrace for this crash is: Application: Kontact (kontact), signal SIGSEGV [?1034hUsing host libthread_db library /lib/libthread_db.so.1. [Thread debugging using libthread_db enabled] [New Thread 0xb534c6d0 (LWP 13057)] [KCrash handler] #5 0xb347fd58 in KMReaderWin::decryptMessage (this=0x0) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmreaderwin.cpp:2574 #6 0xb359eb2e in KMail::ObjectTreeParser::okDecryptMIME (this=0xbfe2b510, data= 0x86030d8, decryptedData= 0xbfe2b2f8, signatureFound= 0xbfe2b31b, sigMeta= 0xbfe2b2ac, showWarning=true, passphraseError= 0xbfe2b31a, actuallyEncrypted= 0xbfe2b319, aErrorText= 0xbfe2b270) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/objecttreeparser.cpp:662 #7 0xb35a63ed in KMail::ObjectTreeParser::processMultiPartEncryptedSubtype ( this=0xbfe2b510, node=0x8602fa8, result= 0xbfe2b3d8) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/objecttreeparser.cpp:1238 #8 0xb35a927b in (anonymous namespace)::MultiPartEncryptedBodyPartFormatter::process (this=0x83b01d8, otp=0xbfe2b510, node=0x8602fa8, result= 0xbfe2b3d8) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/bodypartformatter.cpp:121 #9 0xb359ff7e in KMail::ObjectTreeParser::parseObjectTree (this=0xbfe2b510, node=0x8602fa8) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/objecttreeparser.cpp:284 #10 0xb345dd10 in KMComposeWin::setMsg (this=0x8300068, newMsg=0x843f250, mayAutoSign=false, allowDecryption=true, isModified=false) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmcomposewin.cpp:1711 #11 0xb35c40f4 in KMEditMsgCommand::execute (this=0x8506f28) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmcommands.cpp:688 #12 0xb35c544d in KMCommand::slotPostTransfer (this=0x8506f28, result=KMCommand::OK) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmcommands.cpp:270 #13 0xb35c58c6 in KMCommand::qt_metacall (this=0x8506f28, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbfe2bbfc) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim_build/kmail/kmcommands.moc:85 #14 0xb35c6572 in KMEditMsgCommand::qt_metacall (this=0x8506f28, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbfe2bbfc) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim_build/kmail/kmcommands.moc:532 #15 0xb7e981f4 in QMetaObject::activate (sender=0x8506f28, from_signal_index=4, to_signal_index=4, argv=value optimized out) at kernel/qobject.cpp:3081 #16 0xb7e98d94 in QMetaObject::activate (sender=0x8506f28, m=0xb375c334, local_signal_index=0, argv=0xbfe2bbfc) at kernel/qobject.cpp:3140 #17 0xb35b1a41 in KMCommand::messagesTransfered (this=0x8506f28, _t1=KMCommand::OK) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim_build/kmail/kmcommands.moc:99 #18 0xb35c536b in KMCommand::transferSelectedMsgs (this=0x8506f28) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmcommands.cpp:364 #19 0xb35c5736 in KMCommand::slotStart (this=0x8506f28) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmcommands.cpp:262 #20 0xb35c58ac in KMCommand::qt_metacall (this=0x8506f28, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbfe2c1f4) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim_build/kmail/kmcommands.moc:84 #21 0xb35c6572 in KMEditMsgCommand::qt_metacall (this=0x8506f28, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbfe2c1f4) at
[Bug 156292] Crash after starting the second time
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=156292 --- Additional Comments From Regnaron web de 2008-01-25 01:20 --- Kontact just crashed right after I logged into my KDE Session. (I left kontact running when I rebooted the computer, so I guess the crash occurred while trying to restore the old kontact session) The upper part of the backtrace is identical to the backtrace in this bug, so I'll attach the backtrace (that differs in the lower part) here. Application: Kontact (kontact), signal SIGABRT Using host libthread_db library /lib/libthread_db.so.1. [Thread debugging using libthread_db enabled] [New Thread 0xb53a26d0 (LWP 5681)] [KCrash handler] #6 0xe410 in __kernel_vsyscall () #7 0xb57371f1 in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #8 0xb57389b8 in *__GI_abort () at abort.c:88 #9 0xb7e04265 in qt_message_output (msgType=QtFatalMsg, buf=0xbfbaefcc ASSERT: \!privateObject-q\ in file /var/tmp/portage/kde-base/kdelibs-.4/work/kdelibs-.4/kio/kio/kdbusservicestarter.cpp, line 54) at global/qglobal.cpp:2160 #10 0xb7e0432a in qFatal (msg=0xb7f0b87c ASSERT: \%s\ in file %s, line %d) at global/qglobal.cpp:2392 #11 0xb7e04555 in qt_assert (assertion=0xb788d9d6 !privateObject-q, file=0xb788d84c /var/tmp/portage/kde-base/kdelibs-.4/work/kdelibs-.4/kio/kio/kdbusservicestarter.cpp, line=54) at global/qglobal.cpp:1917 #12 0xb7759cad in KDBusServiceStarter (this=0x81098f0) at /var/tmp/portage/kde-base/kdelibs-.4/work/kdelibs-.4/kio/kio/kdbusservicestarter.cpp:54 #13 0xb62ab652 in ServiceStarter (this=0x81098f0, pluginList=0x805fa60) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kontact/src/mainwindow.cpp:104 #14 0xb62a69e4 in MainWindow (this=0x805fa10) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kontact/src/mainwindow.cpp:150 #15 0x0804b56e in KontactApp::newInstance (this=0xbfbb2b60) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kontact/src/main.cpp:98 #16 0xb7a62c10 in KUniqueApplicationAdaptor::newInstance (this=0x80eb520, asn_id= 0x82f80c0, args= 0x82f7a20) at /var/tmp/portage/kde-base/kdelibs-.4/work/kdelibs-.4/kdeui/kernel/kuniqueapplication_p.h:71 #17 0xb7a6122b in KUniqueApplicationAdaptor::qt_metacall (this=0x80eb520, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfbb1208) at /var/tmp/portage/kde-base/kdelibs-.4/work/kdelibs_build/kdeui/kuniqueapplication_p.moc:73 #18 0xb752cb58 in QDBusConnectionPrivate::deliverCall (this=0x805b690, object=0x80eb520, msg= 0x805ef74, metaTypes= 0xbfbb1334, slotIdx=4) at qdbusintegrator.cpp:837 #19 0xb752d756 in QDBusConnectionPrivate::activateCall (this=0x805b690, object=0x80eb520, flags=337, msg= 0x805ef74) at qdbusintegrator.cpp:742 #20 0xb752e146 in QDBusConnectionPrivate::activateObject (this=0x805b690, node= 0x805ef60, msg= 0x805ef74, pathStartPos=16) at qdbusintegrator.cpp:1269 #21 0xb752e28a in QDBusActivateObjectEvent::placeMetaCall (this=0x805ef30) at qdbusintegrator.cpp:1382 #22 0xb7ee8017 in QObject::event (this=0xbfbb2b60, e=0x1631) at kernel/qobject.cpp:1122 #23 0xb7ed714b in QCoreApplication::event (this=0xbfbb2b60, e=0x805ef30) at kernel/qcoreapplication.cpp:1295 #24 0xb6daf9f7 in QApplication::event (this=0xbfbb2b60, e=0x805ef30) at kernel/qapplication.cpp:2093 #25 0xb6da9e8a in QApplicationPrivate::notify_helper (this=0x80605c0, receiver=0xbfbb2b60, e=0x805ef30) at kernel/qapplication.cpp:3556 #26 0xb6dab77a in QApplication::notify (this=0xbfbb2b60, receiver=0xbfbb2b60, e=0x805ef30) at kernel/qapplication.cpp:3115 #27 0xb7a5c083 in KApplication::notify (this=0xbfbb2b60, receiver=0xbfbb2b60, event=0x805ef30) at /var/tmp/portage/kde-base/kdelibs-.4/work/kdelibs-.4/kdeui/kernel/kapplication.cpp:314 #28 0xb7ed6d7b in QCoreApplication::notifyInternal (this=0xbfbb2b60, receiver=0xbfbb2b60, event=0x805ef30) at kernel/qcoreapplication.cpp:530 #29 0xb7ed821a in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x8050f60) at kernel/qcoreapplication.h:200 #30 0xb7ed856d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1001 #31 0xb6e33aee in QEventDispatcherX11::processEvents (this=0x805ffd8, flags= 0xbfbb1ae4) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:205 #32 0xb7ed6191 in QEventLoop::processEvents (this=0xbfbb1b5c, flags= 0xbfbb1b18) at kernel/qeventloop.cpp:140 #33 0xb7ed629a in QEventLoop::exec (this=0xbfbb1b5c, flags= 0xbfbb1b68) at kernel/qeventloop.cpp:186 #34 0xb7214c87 in QDialog::exec (this=0xbfbb1c18) at dialogs/qdialog.cpp:433 #35 0xb3736001 in KMail::ImapAccountBase::makeConnection (this=0x82f8eb8) at
[Bug 156528] New: KMail crashes when applying all filters (CTRL+J) to an IMAP account
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=156528 Summary: KMail crashes when applying all filters (CTRL+J) to an IMAP account Product: kmail Version: 1.9.50 Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: Regnaron web de Version: 1.9.50 (using 4.00.80 (KDE 4.0.80 = 20080104), Gentoo) Compiler: i686-pc-linux-gnu-gcc OS:Linux (i686) release 2.6.23-gentoo-r3 Whenever I try to apply all filters (CTRL+J) on a folder within my IMAP account, KMail crashes. This bug seems to be related to the bugs bug #156319 (almost same backtrace) and bug #156291 (same backtrace, but bug #156291 already was fixed long ago...). Note that - KMail does *not* crash if I apply filters on a local Mailbox (even if the filter moves the mail to an IMAP account) - Kmail does *not* crash if I apply only a single filter on an IMAP Mailbox. The backtrace and valgrind output during the crash are: Backtrace: Application: Kontact (kontact), signal SIGSEGV Using host libthread_db library /lib/libthread_db.so.1. [Thread debugging using libthread_db enabled] [New Thread 0xb53826d0 (LWP 7255)] [KCrash handler] #6 0xb368c709 in KMail::ActionScheduler::debug () at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/actionscheduler.cpp:797 #7 0xb368e2c8 in KMail::ActionScheduler::processMessage (this=0x84ed120) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/actionscheduler.cpp:491 #8 0xb368ebe1 in KMail::ActionScheduler::qt_metacall (this=0x84ed120, _c=QMetaObject::InvokeMetaMethod, _id=18, _a=0xbfffc224) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim_build/kmail/actionscheduler.moc:118 #9 0xb7eca1f4 in QMetaObject::activate (sender=0x8587288, from_signal_index=4, to_signal_index=4, argv=value optimized out) at kernel/qobject.cpp:3081 #10 0xb7ecad94 in QMetaObject::activate (sender=0x8587288, m=0xb7f699e4, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3140 #11 0xb7eeb083 in QTimer::timeout (this=0x8587288) at .moc/debug-shared/moc_qtimer.cpp:125 #12 0xb7ed3a2e in QTimer::timerEvent (this=0x8587288, e=0xbfffc758) at kernel/qtimer.cpp:259 #13 0xb7ec8269 in QObject::event (this=0x8587288, e=0x84e6868) at kernel/qobject.cpp:1086 #14 0xb6d89e8a in QApplicationPrivate::notify_helper (this=0x80648e8, receiver=0x8587288, e=0xbfffc758) at kernel/qapplication.cpp:3556 #15 0xb6d8b77a in QApplication::notify (this=0xbfffc9e0, receiver=0x8587288, e=0xbfffc758) at kernel/qapplication.cpp:3115 #16 0xb7a3c083 in KApplication::notify (this=0xbfffc9e0, receiver=0x8587288, event=0xbfffc758) at /var/tmp/portage/kde-base/kdelibs-.4/work/kdelibs-.4/kdeui/kernel/kapplication.cpp:314 #17 0xb7eb6d7b in QCoreApplication::notifyInternal (this=0xbfffc9e0, receiver=0x8587288, event=0xbfffc758) at kernel/qcoreapplication.cpp:530 #18 0xb7edfefb in QTimerInfoList::activateTimers (this=0x8065024) at kernel/qcoreapplication.h:200 #19 0xb7edffd1 in QEventDispatcherUNIX::activateTimers (this=0x805f108) at kernel/qeventdispatcher_unix.cpp:828 #20 0xb7ee09ab in QEventDispatcherUNIX::processEvents (this=0x805f108, flags= 0xbfffc8d8) at kernel/qeventdispatcher_unix.cpp:890 #21 0xb6e13cce in QEventDispatcherX11::processEvents (this=0x805f108, flags= 0xbfffc904) at kernel/qeventdispatcher_x11.cpp:145 #22 0xb7eb6191 in QEventLoop::processEvents (this=0xbfffc970, flags= 0xbfffc938) at kernel/qeventloop.cpp:140 #23 0xb7eb629a in QEventLoop::exec (this=0xbfffc970, flags= 0xbfffc978) at kernel/qeventloop.cpp:186 #24 0xb7eb8626 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:759 #25 0xb6d89487 in QApplication::exec () at kernel/qapplication.cpp:3053 #26 0x0804b3f5 in main (argc=1, argv=0xbfffcb74) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kontact/src/main.cpp:162 #27 0xb5703fdc in __libc_start_main (main=0x804ab60 main, argc=1, ubp_av=0xbfffcb74, init=0x804c180 __libc_csu_init, fini=0x804c170 __libc_csu_fini, rtld_fini=0xb7f7a100 _dl_fini, stack_end=0xbfffcb6c) at libc-start.c:229 #28 0x0804a791 in _start () #0 0xe410 in __kernel_vsyscall () Valgrind: ==9632== Memcheck, a memory error detector. ==9632== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al. ==9632== Using LibVEX rev 1732, a library for dynamic binary translation. ==9632== Copyright (C) 2004-2007, and GNU GPL'd, by OpenWorks LLP. ==9632== Using valgrind-3.2.3, a dynamic binary instrumentation framework. ==9632== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward et al. ==9632== For more details, rerun
[Bug 156319] New: Seemingly random KMail crash
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=156319 Summary: Seemingly random KMail crash Product: kmail Version: 1.9.50 Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: Regnaron web de Version: 1.9.50 (using 4.00.80 (KDE 4.0.80 = 20080104), Gentoo) Compiler: i686-pc-linux-gnu-gcc OS:Linux (i686) release 2.6.22-gentoo-r9 Today when I was moving mail around in Kontact in order to try to reproduce bug #156291 KMail all of a sudden (seemingly randomly) crashed with the following backtrace: Using host libthread_db library /lib/libthread_db.so.1. [Thread debugging using libthread_db enabled] [New Thread 0xb53fe6d0 (LWP 26320)] [KCrash handler] #6 KMail::ActionScheduler::processMessage (this=0x84e3630) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/actionscheduler.cpp:533 #7 0xb3569181 in KMail::ActionScheduler::qt_metacall (this=0x84e3630, _c=QMetaObject::InvokeMetaMethod, _id=18, _a=0xbf9e8434) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim_build/kmail/actionscheduler.moc:118 #8 0xb7f441f4 in QMetaObject::activate (sender=0x84deeb8, from_signal_index=4, to_signal_index=4, argv=value optimized out) at kernel/qobject.cpp:3081 #9 0xb7f44d94 in QMetaObject::activate (sender=0x84deeb8, m=0xb7fe39e4, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3140 #10 0xb7f65083 in QTimer::timeout (this=0x84deeb8) at .moc/debug-shared/moc_qtimer.cpp:125 #11 0xb7f4da2e in QTimer::timerEvent (this=0x84deeb8, e=0xbf9e8968) at kernel/qtimer.cpp:259 #12 0xb7f42269 in QObject::event (this=0x84deeb8, e=0x8065138) at kernel/qobject.cpp:1086 #13 0xb6e04e8a in QApplicationPrivate::notify_helper (this=0x8060068, receiver=0x84deeb8, e=0xbf9e8968) at kernel/qapplication.cpp:3556 #14 0xb6e0677a in QApplication::notify (this=0xbf9e8bf0, receiver=0x84deeb8, e=0xbf9e8968) at kernel/qapplication.cpp:3115 #15 0xb7ab6fb3 in KApplication::notify (this=0xbf9e8bf0, receiver=0x84deeb8, event=0xbf9e8968) at /var/tmp/portage/kde-base/kdelibs-.4/work/kdelibs-.4/kdeui/kernel/kapplication.cpp:314 #16 0xb7f30d7b in QCoreApplication::notifyInternal (this=0xbf9e8bf0, receiver=0x84deeb8, event=0xbf9e8968) at kernel/qcoreapplication.cpp:530 #17 0xb7f59efb in QTimerInfoList::activateTimers (this=0x80607e4) at kernel/qcoreapplication.h:200 #18 0xb7f59fd1 in QEventDispatcherUNIX::activateTimers (this=0x805f170) at kernel/qeventdispatcher_unix.cpp:828 #19 0xb7f5a9ab in QEventDispatcherUNIX::processEvents (this=0x805f170, flags= 0xbf9e8ae8) at kernel/qeventdispatcher_unix.cpp:890 #20 0xb6e8ecce in QEventDispatcherX11::processEvents (this=0x805f170, flags= 0xbf9e8b14) at kernel/qeventdispatcher_x11.cpp:145 #21 0xb7f30191 in QEventLoop::processEvents (this=0xbf9e8b80, flags= 0xbf9e8b48) at kernel/qeventloop.cpp:140 #22 0xb7f3029a in QEventLoop::exec (this=0xbf9e8b80, flags= 0xbf9e8b88) at kernel/qeventloop.cpp:186 #23 0xb7f32626 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:759 #24 0xb6e04487 in QApplication::exec () at kernel/qapplication.cpp:3053 #25 0x0804b3f5 in main (argc=1, argv=0xbf9e8d84) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kontact/src/main.cpp:162 #26 0xb577ffdc in __libc_start_main (main=0x804ab60 main, argc=1, ubp_av=0xbf9e8d84, init=0x804c180 __libc_csu_init, fini=0x804c170 __libc_csu_fini, rtld_fini=0xb7ff4100 _dl_fini, stack_end=0xbf9e8d7c) at libc-start.c:229 #27 0x0804a791 in _start () #0 0xe410 in __kernel_vsyscall () ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 156319] Seemingly random KMail crash
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=156319 Regnaron web de changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||WORKSFORME --- Additional Comments From Regnaron web de 2008-01-21 18:28 --- Is it possible that this bug is related to bug #156289? The backtraces do not look too different, and after an update that fixed bug #156289 I can neither reproduce bug #156289 nor this bug? (I'll mark this bug as resolved for that reason) ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 156319] Seemingly random KMail crash
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=156319 Regnaron web de changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|WORKSFORME | --- Additional Comments From Regnaron web de 2008-01-21 18:31 --- Sorry, posted the comment above on the wrong bug :/ ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 156290] New: KMail crashed on click on IMAP inbox
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=156290 Summary: KMail crashed on click on IMAP inbox Product: kmail Version: 1.9.50 Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: Regnaron web de Version: 1.9.50 (using 4.00.80 (KDE 4.0.80 = 20080104), Gentoo) Compiler: i686-pc-linux-gnu-gcc OS:Linux (i686) release 2.6.22-gentoo-r9 Today I used Kontact in IMAP mode. When I clicked on a folder and then clicked on the inbox, Kontact crashed. Regrettably I cannot reproduce this crash. Backtrace: Using host libthread_db library /lib/libthread_db.so.1. [Thread debugging using libthread_db enabled] [New Thread 0xb534c6d0 (LWP 6578)] [KCrash handler] #6 0xe410 in __kernel_vsyscall () #7 0xb56f41f1 in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #8 0xb56f59b8 in *__GI_abort () at abort.c:88 #9 0xb7dab265 in qt_message_output (msgType=QtFatalMsg, buf=0xbfda421c ASSERT: \!isEmpty()\ in file /usr/include/qt4/QtCore/qlist.h, line 242) at global/qglobal.cpp:2160 #10 0xb7dab32a in qFatal (msg=0xb7eb287c ASSERT: \%s\ in file %s, line %d) at global/qglobal.cpp:2392 #11 0xb7dab555 in qt_assert (assertion=0xb36fd8b6 !isEmpty(), file=0xb36fd088 /usr/include/qt4/QtCore/qlist.h, line=242) at global/qglobal.cpp:1917 #12 0xb34b2aea in QListint::first (this=0xbfda62a4) at /usr/include/qt4/QtCore/qlist.h:242 #13 0xb352b4db in KMFolderImap::addMsg (this=0x8578110, aMsg=0x881cf08, aIndex_ret=0xbfda62ec) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmfolderimap.cpp:413 #14 0xb34add7b in FolderStorage::addMessages (this=0x8578110, msgList= 0xbfda6378, index_ret= 0xbfda6338) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/folderstorage.cpp:1162 #15 0xb34afa25 in FolderStorage::moveMsg (this=0x8578110, msglist= 0xbfda6378, aIndex_ret=0xbfda6428) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/folderstorage.cpp:626 #16 0xb3493000 in KMFolder::moveMsg (this=0x855b338, q= 0xbfda644c, index_return=0xbfda6428) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmfolder.cpp:437 #17 0xb35d380b in KMMoveCommand::execute (this=0x881fa38) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmcommands.cpp:2133 #18 0xb35def7d in KMCommand::slotPostTransfer (this=0x881fa38, result=KMCommand::OK) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmcommands.cpp:270 #19 0xb35df3f6 in KMCommand::qt_metacall (this=0x881fa38, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbfda69ec) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim_build/kmail/kmcommands.moc:85 #20 0xb35df89a in KMMoveCommand::qt_metacall (this=0x881fa38, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbfda69ec) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim_build/kmail/kmcommands.moc:1661 #21 0xb7e911f4 in QMetaObject::activate (sender=0x881fa38, from_signal_index=4, to_signal_index=4, argv=value optimized out) at kernel/qobject.cpp:3081 #22 0xb7e91d94 in QMetaObject::activate (sender=0x881fa38, m=0xb3775214, local_signal_index=0, argv=0xbfda69ec) at kernel/qobject.cpp:3140 #23 0xb35cb581 in KMCommand::messagesTransfered (this=0x881fa38, _t1=KMCommand::OK) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim_build/kmail/kmcommands.moc:99 #24 0xb35dee9b in KMCommand::transferSelectedMsgs (this=0x881fa38) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmcommands.cpp:364 #25 0xb35df266 in KMCommand::slotStart (this=0x881fa38) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmcommands.cpp:262 #26 0xb35df3dc in KMCommand::qt_metacall (this=0x881fa38, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbfda6ff4) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim_build/kmail/kmcommands.moc:84 #27 0xb35df89a in KMMoveCommand::qt_metacall (this=0x881fa38, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbfda6ff4) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim_build/kmail/kmcommands.moc:1661 #28 0xb7e911f4 in QMetaObject::activate (sender=0x869b9f0, from_signal_index=4, to_signal_index=4, argv=value optimized out) at kernel/qobject.cpp:3081 #29 0xb7e91d94 in QMetaObject::activate (sender=0x869b9f0, m=0xb7f2fc64, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3140 #30 0xb7e9a3c3 in QSingleShotTimer::timeout (this=0x869b9f0) at .moc/debug-shared/qtimer.moc:73 #31 0xb7e9a40c in QSingleShotTimer::timerEvent (this=0x869b9f0) at kernel/qtimer.cpp:296 #32
[Bug 156289] New: Kontact crashes when applying filters on IMAP folder
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=156289 Summary: Kontact crashes when applying filters on IMAP folder Product: kmail Version: 1.9.50 Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: Regnaron web de Version: 1.9.50 (using 4.00.80 (KDE 4.0.80 = 20080104), Gentoo) Compiler: i686-pc-linux-gnu-gcc OS:Linux (i686) release 2.6.22-gentoo-r9 Kontact repeatedly crashes when I try to apply a filter to an IMAP folder. The filter moves messages to another folder on the IMAP server if the Subject containes [Bug . There are 4 messages (all unread) in the inbox that should be moved by the filter. (The other two messages in the inbox are already read and should not be affected by filter) I added the filter to the toolbar and the filter menu. Invoking the filter itself produces the first crash. (signal6) If I apply all (this is the only one) filters (Ctrl+J) to the folder, Kontact crashes with the second backtrace (signal11) Backtrace for only applying single filter: Using host libthread_db library /lib/libthread_db.so.1. [Thread debugging using libthread_db enabled] [New Thread 0xb53176d0 (LWP 6703)] [KCrash handler] #6 0xe410 in __kernel_vsyscall () #7 0xb56bf1f1 in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #8 0xb56c09b8 in *__GI_abort () at abort.c:88 #9 0xb7d76265 in qt_message_output (msgType=QtFatalMsg, buf=0xbff99c6c ASSERT: \!isEmpty()\ in file /usr/include/qt4/QtCore/qlist.h, line 242) at global/qglobal.cpp:2160 #10 0xb7d7632a in qFatal (msg=0xb7e7d87c ASSERT: \%s\ in file %s, line %d) at global/qglobal.cpp:2392 #11 0xb7d76555 in qt_assert (assertion=0xb36c88b6 !isEmpty(), file=0xb36c8088 /usr/include/qt4/QtCore/qlist.h, line=242) at global/qglobal.cpp:1917 #12 0xb347daea in QListint::first (this=0xbff9bcf4) at /usr/include/qt4/QtCore/qlist.h:242 #13 0xb34f64db in KMFolderImap::addMsg (this=0x82f0540, aMsg=0x84cca18, aIndex_ret=0x0) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmfolderimap.cpp:413 #14 0xb347d0f2 in FolderStorage::addMsgKeepUID (this=0x82f0540, msg=0x84cca18, index_return=0x0) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/folderstorage.h:199 #15 0xb345c1c5 in KMFolder::addMsgKeepUID (this=0x82efcb8, msg=0x84cca18, index_return=0x0) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmfolder.cpp:402 #16 0xb349f44f in KMFilterMgr::endFiltering (this=0x82daea8, msgBase=0x84cca18) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmfiltermgr.cpp:133 #17 0xb349f70f in KMFilterMgr::process (this=0x82daea8, serNum=33, filter=0x8644578) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmfiltermgr.cpp:201 #18 0xb35a2e80 in KMFilterActionCommand::execute (this=0x8540770) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmcommands.cpp:1725 #19 0xb35a9f7d in KMCommand::slotPostTransfer (this=0x8540770, result=KMCommand::OK) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmcommands.cpp:270 #20 0xb35aa3f6 in KMCommand::qt_metacall (this=0x8540770, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbff9c3ec) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim_build/kmail/kmcommands.moc:85 #21 0xb35aaa92 in KMFilterActionCommand::qt_metacall (this=0x8540770, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbff9c3ec) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim_build/kmail/kmcommands.moc:1409 #22 0xb7e5c1f4 in QMetaObject::activate (sender=0x8540770, from_signal_index=4, to_signal_index=4, argv=value optimized out) at kernel/qobject.cpp:3081 #23 0xb7e5cd94 in QMetaObject::activate (sender=0x8540770, m=0xb3740214, local_signal_index=0, argv=0xbff9c3ec) at kernel/qobject.cpp:3140 #24 0xb3596581 in KMCommand::messagesTransfered (this=0x8540770, _t1=KMCommand::OK) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim_build/kmail/kmcommands.moc:99 #25 0xb35a9e9b in KMCommand::transferSelectedMsgs (this=0x8540770) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmcommands.cpp:364 #26 0xb35aa266 in KMCommand::slotStart (this=0x8540770) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmcommands.cpp:262 #27 0xb35aa3dc in KMCommand::qt_metacall (this=0x8540770, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbff9c9e4) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim_build/kmail/kmcommands.moc:84 #28 0xb35aaa92 in KMFilterActionCommand::qt_metacall (this=0x8540770,
[Bug 156292] New: Kontact crashed right after starting (after krunner crash)
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=156292 Summary: Kontact crashed right after starting (after krunner crash) Product: kontact Version: unspecified Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: Regnaron web de Version:(using Devel) Installed from:Compiled sources Compiler: gcc version 4.1.2 20070214 OS:Linux I just tried to run kontact via krunner. (Alt+F2). The first time, krunner crashed without starting Kontact. [no usable backtrace for the krunner crash] As I tried to start Kontact a second time (immediately after the first try) via krunner, krunner survived, but Kontact crashed immediately with the following backtrace: Using host libthread_db library /lib/libthread_db.so.1. [Thread debugging using libthread_db enabled] [New Thread 0xb53216d0 (LWP 7027)] [KCrash handler] #6 0xe410 in __kernel_vsyscall () #7 0xb56c91f1 in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #8 0xb56ca9b8 in *__GI_abort () at abort.c:88 #9 0xb7d80265 in qt_message_output (msgType=QtFatalMsg, buf=0xbfc7501c ASSERT: \!privateObject-q\ in file /var/tmp/portage/kde-base/kdelibs-.4/work/kdelibs-.4/kio/kio/kdbusservicestarter.cpp, line 54) at global/qglobal.cpp:2160 #10 0xb7d8032a in qFatal (msg=0xb7e8787c ASSERT: \%s\ in file %s, line %d) at global/qglobal.cpp:2392 #11 0xb7d80555 in qt_assert (assertion=0xb780acd6 !privateObject-q, file=0xb780ab4c /var/tmp/portage/kde-base/kdelibs-.4/work/kdelibs-.4/kio/kio/kdbusservicestarter.cpp, line=54) at global/qglobal.cpp:1917 #12 0xb76d6cad in KDBusServiceStarter (this=0x8123e08) at /var/tmp/portage/kde-base/kdelibs-.4/work/kdelibs-.4/kio/kio/kdbusservicestarter.cpp:54 #13 0xb6229642 in ServiceStarter (this=0x8123e08, pluginList=0x8372830) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kontact/src/mainwindow.cpp:104 #14 0xb62249d4 in MainWindow (this=0x83727e0) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kontact/src/mainwindow.cpp:150 #15 0x0804b55e in KontactApp::newInstance (this=0xbfc79680) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kontact/src/main.cpp:98 #16 0xb79dfb40 in KUniqueApplicationAdaptor::newInstance (this=0x80e4d60, asn_id= 0x813b230, args= 0x8121f08) at /var/tmp/portage/kde-base/kdelibs-.4/work/kdelibs-.4/kdeui/kernel/kuniqueapplication_p.h:71 #17 0xb79de15b in KUniqueApplicationAdaptor::qt_metacall (this=0x80e4d60, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfc77258) at /var/tmp/portage/kde-base/kdelibs-.4/work/kdelibs_build/kdeui/kuniqueapplication_p.moc:73 #18 0xb74a9b58 in QDBusConnectionPrivate::deliverCall (this=0x805b418, object=0x80e4d60, msg= 0x83f5a64, metaTypes= 0x80a163c, slotIdx=4) at qdbusintegrator.cpp:837 #19 0xb74aa804 in QDBusConnectionPrivate::activateCall (this=0x805b418, object=0x80e4d60, flags=337, msg= 0x83f5a64) at qdbusintegrator.cpp:749 #20 0xb74ab146 in QDBusConnectionPrivate::activateObject (this=0x805b418, node= 0x83f5a50, msg= 0x83f5a64, pathStartPos=16) at qdbusintegrator.cpp:1269 #21 0xb74ab28a in QDBusActivateObjectEvent::placeMetaCall (this=0x83f5a20) at qdbusintegrator.cpp:1382 #22 0xb7e64017 in QObject::event (this=0xbfc79680, e=0x1b73) at kernel/qobject.cpp:1122 #23 0xb7e5314b in QCoreApplication::event (this=0xbfc79680, e=0x83f5a20) at kernel/qcoreapplication.cpp:1295 #24 0xb6d2c9f7 in QApplication::event (this=0xbfc79680, e=0x83f5a20) at kernel/qapplication.cpp:2093 #25 0xb6d26e8a in QApplicationPrivate::notify_helper (this=0x8060068, receiver=0xbfc79680, e=0x83f5a20) at kernel/qapplication.cpp:3556 #26 0xb6d2877a in QApplication::notify (this=0xbfc79680, receiver=0xbfc79680, e=0x83f5a20) at kernel/qapplication.cpp:3115 #27 0xb79d8fb3 in KApplication::notify (this=0xbfc79680, receiver=0xbfc79680, event=0x83f5a20) at /var/tmp/portage/kde-base/kdelibs-.4/work/kdelibs-.4/kdeui/kernel/kapplication.cpp:314 #28 0xb7e52d7b in QCoreApplication::notifyInternal (this=0xbfc79680, receiver=0xbfc79680, event=0x83f5a20) at kernel/qcoreapplication.cpp:530 #29 0xb7e5421a in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x8050f60) at kernel/qcoreapplication.h:200 #30 0xb7e5456d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1001 #31 0xb6db0aee in QEventDispatcherX11::processEvents (this=0x805f170, flags= 0xbfc77b34) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:205
[Bug 156291] New: Moving a message (DragDrop) from an IMAP folder to a local folder crashes KMail
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=156291 Summary: Moving a message (DragDrop) from an IMAP folder to a local folder crashes KMail Product: kmail Version: 1.9.50 Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: Regnaron web de Version: 1.9.50 (using 4.00.80 (KDE 4.0.80 = 20080104), Gentoo) Compiler: i686-pc-linux-gnu-gcc OS:Linux (i686) release 2.6.22-gentoo-r9 When I try to move a mail from an IMAP account to a local folder (drag and drop) KMail crashes with the following backtrace: Using host libthread_db library /lib/libthread_db.so.1. [Thread debugging using libthread_db enabled] [New Thread 0xb534f6d0 (LWP 7003)] [KCrash handler] #6 0xe410 in __kernel_vsyscall () #7 0xb56f71f1 in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #8 0xb56f89b8 in *__GI_abort () at abort.c:88 #9 0xb7dae265 in qt_message_output (msgType=QtFatalMsg, buf=0xbf94e5cc ASSERT: \!isEmpty()\ in file /usr/include/qt4/QtCore/qlist.h, line 242) at global/qglobal.cpp:2160 #10 0xb7dae32a in qFatal (msg=0xb7eb587c ASSERT: \%s\ in file %s, line %d) at global/qglobal.cpp:2392 #11 0xb7dae555 in qt_assert (assertion=0xb37008b6 !isEmpty(), file=0xb3700088 /usr/include/qt4/QtCore/qlist.h, line=242) at global/qglobal.cpp:1917 #12 0xb34b5aea in QListint::first (this=0xbf950654) at /usr/include/qt4/QtCore/qlist.h:242 #13 0xb352e4db in KMFolderImap::addMsg (this=0x82fa658, aMsg=0x8626350, aIndex_ret=0xbf95069c) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmfolderimap.cpp:413 #14 0xb34b0d7b in FolderStorage::addMessages (this=0x82fa658, msgList= 0xbf950728, index_ret= 0xbf9506e8) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/folderstorage.cpp:1162 #15 0xb34b2a25 in FolderStorage::moveMsg (this=0x82fa658, msglist= 0xbf950728, aIndex_ret=0xbf9507d8) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/folderstorage.cpp:626 #16 0xb3496000 in KMFolder::moveMsg (this=0x82fa5b8, q= 0xbf9507fc, index_return=0xbf9507d8) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmfolder.cpp:437 #17 0xb35d680b in KMMoveCommand::execute (this=0x84e29a8) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmcommands.cpp:2133 #18 0xb35e1f7d in KMCommand::slotPostTransfer (this=0x84e29a8, result=KMCommand::OK) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmcommands.cpp:270 #19 0xb35e23f6 in KMCommand::qt_metacall (this=0x84e29a8, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbf950d9c) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim_build/kmail/kmcommands.moc:85 #20 0xb35e289a in KMMoveCommand::qt_metacall (this=0x84e29a8, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbf950d9c) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim_build/kmail/kmcommands.moc:1661 #21 0xb7e941f4 in QMetaObject::activate (sender=0x84e29a8, from_signal_index=4, to_signal_index=4, argv=value optimized out) at kernel/qobject.cpp:3081 #22 0xb7e94d94 in QMetaObject::activate (sender=0x84e29a8, m=0xb3778214, local_signal_index=0, argv=0xbf950d9c) at kernel/qobject.cpp:3140 #23 0xb35ce581 in KMCommand::messagesTransfered (this=0x84e29a8, _t1=KMCommand::OK) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim_build/kmail/kmcommands.moc:99 #24 0xb35e1e9b in KMCommand::transferSelectedMsgs (this=0x84e29a8) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmcommands.cpp:364 #25 0xb35e2266 in KMCommand::slotStart (this=0x84e29a8) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmcommands.cpp:262 #26 0xb35e23dc in KMCommand::qt_metacall (this=0x84e29a8, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbf9513a4) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim_build/kmail/kmcommands.moc:84 #27 0xb35e289a in KMMoveCommand::qt_metacall (this=0x84e29a8, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbf9513a4) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim_build/kmail/kmcommands.moc:1661 #28 0xb7e941f4 in QMetaObject::activate (sender=0x850e650, from_signal_index=4, to_signal_index=4, argv=value optimized out) at kernel/qobject.cpp:3081 #29 0xb7e94d94 in QMetaObject::activate (sender=0x850e650, m=0xb7f32c64, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3140 #30 0xb7e9d3c3 in QSingleShotTimer::timeout (this=0x850e650) at .moc/debug-shared/qtimer.moc:73 #31 0xb7e9d40c in QSingleShotTimer::timerEvent (this=0x850e650) at
[Bug 156293] New: KMail crashed after clicking on a message
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=156293 Summary: KMail crashed after clicking on a message Product: kmail Version: 1.9.50 Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: Regnaron web de Version: 1.9.50 (using 4.00.80 (KDE 4.0.80 = 20080104), Gentoo) Compiler: i686-pc-linux-gnu-gcc OS:Linux (i686) release 2.6.22-gentoo-r9 I just tried to move a message via drag and drop from an IMAP folder to a local folder. After having successfully copied(!) the first (already read) message, KMail crashed as soon as I clicked on the second (unread) message (in order to drag and drop it) Remark: This crash just also occurred after clicking on a (read) mail directly after starting Kontact. The backtrace for this (regrettably not reproducible) crash was: Using host libthread_db library /lib/libthread_db.so.1. [Thread debugging using libthread_db enabled] [New Thread 0xb537b6d0 (LWP 7073)] [KCrash handler] #6 0xe410 in __kernel_vsyscall () #7 0xb57231f1 in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #8 0xb57249b8 in *__GI_abort () at abort.c:88 #9 0xb7dda265 in qt_message_output (msgType=QtFatalMsg, buf=0xbfaedfdc ASSERT: \!transferInProgress( serNum )\ in file /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/messageproperty.cpp, line 164) at global/qglobal.cpp:2160 #10 0xb7dda32a in qFatal (msg=0xb7ee187c ASSERT: \%s\ in file %s, line %d) at global/qglobal.cpp:2392 #11 0xb7dda555 in qt_assert ( assertion=0xb374b3a1 !transferInProgress( serNum ), file=0xb374b34c /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/messageproperty.cpp, line=164) at global/qglobal.cpp:1917 #12 0xb34e8891 in KMail::MessageProperty::forget (msgBase=0x855a248) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/messageproperty.cpp:164 #13 0xb3532d0d in ~KMMsgBase (this=0x855a248) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmmsgbase.cpp:87 #14 0xb33f9a25 in ~KMMessage (this=0x855a248) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmmessage.cpp:216 #15 0xb36d93c6 in KMTextSource::text (this=0x84efc98, serialNumber=43) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/textsource.cpp:61 #16 0xb61a56b8 in KPIM::MailList::populateMimeData (this=0xbfaf02d0, md=0x85bcee0, src=0x84efc98) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/libkdepim/maillistdrag.cpp:188 #17 0xb3479a00 in KMHeaders::contentsMouseMoveEvent (this=0x82f34a8, e=0xbfaf0338) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmheaders.cpp:2427 #18 0xb6540e1e in Q3ScrollView::viewportMouseMoveEvent (this=0x82f34a8, e=0xbfaf0a24) at widgets/q3scrollview.cpp:1814 #19 0xb654225a in Q3ScrollView::eventFilter (this=0x82f34a8, obj=0x82e9b00, e=0xbfaf0a24) at widgets/q3scrollview.cpp:1512 #20 0xb64df416 in Q3ListView::eventFilter (this=0x82f34a8, o=0x82e9b00, e=0xbfaf0a24) at itemviews/q3listview.cpp:3790 #21 0xb3485486 in KMHeaders::eventFilter (this=0x82f34a8, o=0x82e9b00, e=0xbfaf0a24) at /var/tmp/portage/kde-base/kdepim-.4/work/kdepim-.4/kmail/kmheaders.cpp:288 #22 0xb6d80d9b in QApplicationPrivate::notify_helper (this=0x8060068, receiver=0x82e9b00, e=0xbfaf0a24) at kernel/qapplication.cpp:3548 #23 0xb6d82a2c in QApplication::notify (this=0xbfaf0fb0, receiver=0x82e9b00, e=0xbfaf0a24) at kernel/qapplication.cpp:3255 #24 0xb7a32fb3 in KApplication::notify (this=0xbfaf0fb0, receiver=0x82e9b00, event=0xbfaf0a24) at /var/tmp/portage/kde-base/kdelibs-.4/work/kdelibs-.4/kdeui/kernel/kapplication.cpp:314 #25 0xb7eacd7b in QCoreApplication::notifyInternal (this=0xbfaf0fb0, receiver=0x82e9b00, event=0xbfaf0a24) at kernel/qcoreapplication.cpp:530 #26 0xb6de6628 in QETWidget::translateMouseEvent (this=0x82e9b00, event=0xbfaf0de8) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:203 #27 0xb6de4e8e in QApplication::x11ProcessEvent (this=0xbfaf0fb0, event=0xbfaf0de8) at kernel/qapplication_x11.cpp:2913 #28 0xb6e0ac45 in QEventDispatcherX11::processEvents (this=0x805f170, flags= 0xbfaf0ed4) at kernel/qeventdispatcher_x11.cpp:125 #29 0xb7eac191 in QEventLoop::processEvents (this=0xbfaf0f40, flags= 0xbfaf0f08) at kernel/qeventloop.cpp:140 #30 0xb7eac29a in QEventLoop::exec (this=0xbfaf0f40, flags= 0xbfaf0f48) at kernel/qeventloop.cpp:186 #31 0xb7eae626 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:759 #32 0xb6d80487 in QApplication::exec () at
[Bug 155911] KMail crashes on klick on Local Inbox
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=155911 --- Additional Comments From Regnaron web de 2008-01-18 16:44 --- Hi, if it helps, I just found out that this crash only occurs when I start kmail from within kontact. (Start Kontact and then go to kmail) If I start kmail directely, it does not crash. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
