[kontact] [Bug 419882] New: reproducible kontact (or akonadiconsole) crash when viewing one specific mail
https://bugs.kde.org/show_bug.cgi?id=419882 Bug ID: 419882 Summary: reproducible kontact (or akonadiconsole) crash when viewing one specific mail Product: kontact Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: dilfri...@gentoo.org Target Milestone: --- Application: kontact (5.13.3 (19.12.3)) Qt Version: 5.14.1 Frameworks Version: 5.67.0 Operating System: Linux 5.4.30-gentoo-ah1 x86_64 Distribution: "Gentoo Base System release 2.6" -- Information about the crash: - What I was doing when the application crashed: Opened a specific e-mail by clicking on it in the folder contents list. The same crash occurs when I click on the mail in akondadiconsole. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f680832e340 (LWP 30909))] Thread 42 (Thread 0x7f6733fff700 (LWP 31047)): #0 0x7f6818d64f2c in read () at /lib64/libc.so.6 #1 0x7f681756646f in g_wakeup_acknowledge () at /usr/lib64/libglib-2.0.so.0 #2 0x7f681751f83e in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f681751fcb2 in g_main_context_iterate.isra () at /usr/lib64/libglib-2.0.so.0 #4 0x7f681751fe2f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f6819390a6b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f681933b56b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f681919033e in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f681919136b in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #9 0x7f6817e72fa7 in start_thread () at /lib64/libpthread.so.0 #10 0x7f6818d73d3f in clone () at /lib64/libc.so.6 Thread 41 (Thread 0x7f6745dac700 (LWP 31016)): #0 0x7f6817e79635 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f681189a57c in base::ConditionVariable::Wait() () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x in () Thread 40 (Thread 0x7f67471eb700 (LWP 31010)): #0 0x7f6817e79635 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f6805f44823 in util_queue_thread_func () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f6805f7 in impl_thrd_routine () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f6817e72fa7 in start_thread () at /lib64/libpthread.so.0 #4 0x7f6818d73d3f in clone () at /lib64/libc.so.6 Thread 39 (Thread 0x7f6747fff700 (LWP 30995)): #0 0x7f6817e79635 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f6805f44823 in util_queue_thread_func () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f6805f7 in impl_thrd_routine () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f6817e72fa7 in start_thread () at /lib64/libpthread.so.0 #4 0x7f6818d73d3f in clone () at /lib64/libc.so.6 Thread 38 (Thread 0x7f675ccbd700 (LWP 30993)): #0 0x7f6817e79635 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f6805f44823 in util_queue_thread_func () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f6805f7 in impl_thrd_routine () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f6817e72fa7 in start_thread () at /lib64/libpthread.so.0 #4 0x7f6818d73d3f in clone () at /lib64/libc.so.6 Thread 37 (Thread 0x7f675e187700 (LWP 30976)): #0 0x7f681751f27b in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #1 0x7f681751fc36 in g_main_context_iterate.isra () at /usr/lib64/libglib-2.0.so.0 #2 0x7f681751fe2f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f6819390a6b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f681933b56b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f681919033e in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f681919136b in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #7 0x7f6817e72fa7 in start_thread () at /lib64/libpthread.so.0 #8 0x7f6818d73d3f in clone () at /lib64/libc.so.6 Thread 36 (Thread 0x7f675ef44700 (LWP 30966)): #0 0x7f681756a904 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f681751fd03 in g_main_context_iterate.isra () at /usr/lib64/libglib-2.0.so.0 #2 0x7f681751fe2f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f6819390a6b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f681933b56b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f681919033e in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f681919136b in Q
[Akonadi] [Bug 397316] akonadi loses connection with IMAP server after suspend (but not only, DB error too)
https://bugs.kde.org/show_bug.cgi?id=397316 Andreas K. Huettel changed: What|Removed |Added CC||dilfri...@gentoo.org -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 Andreas K. Huettel changed: What|Removed |Added CC|dilfri...@gentoo.org| -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
[kmail2] [Bug 350219] Kmail can't create IMAP top level folders
https://bugs.kde.org/show_bug.cgi?id=350219 Andreas K. Huettel changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #21 from Andreas K. Huettel --- Definitely not fixed in 17.04.2, symptoms remain exactly the same. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 350219] Kmail can't create IMAP top level folders
https://bugs.kde.org/show_bug.cgi?id=350219 Andreas K. Huettel changed: What|Removed |Added CC||dilfri...@gentoo.org Platform|Kubuntu Packages|Gentoo Packages Version|5.1.3 |5.4.1 --- Comment #15 from Andreas K. Huettel --- Same effect on Gentoo, kmail 5.4.1 New top-level IMAP folders cannot be created in kmail / kontact. Creating one in akonadiconsole works fine. Updating the bug data to show it's still current / applicable -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email
https://bugs.kde.org/show_bug.cgi?id=374734 Andreas K. Huettel changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||dilfri...@gentoo.org Ever confirmed|0 |1 --- Comment #13 from Andreas K. Huettel --- Same phenomenon here as described by original submitter, here with Gentoo. * randomly, kmail does not delete an e-mail * when leaving kmail and then stopping akonadi, akonadi crashes. Backtrace: Application: akonadiserver (akonadiserver), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". pthread_cond_timedwait () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 [Current thread is 1 (Thread 0x7f8b76e62780 (LWP 32690))] Thread 19 (Thread 0x7f8b6cfc5700 (LWP 32691)): #0 0x7f8b73242b79 in g_mutex_lock (mutex=mutex@entry=0x7f8b68000990) at /var/tmp/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gthread-posix.c:1336 #1 0x7f8b731fd6c2 in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7f8b680210c0, timeout=-1, context=0x7f8b68000990) at /var/tmp/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:4223 #2 g_main_context_iterate (context=context@entry=0x7f8b68000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:3924 #3 0x7f8b731fd7ec in g_main_context_iteration (context=0x7f8b68000990, may_block=1) at /var/tmp/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:3990 #4 0x7f8b766f369c in QEventDispatcherGlib::processEvents (this=0x7f8b680008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #5 0x7f8b766a6d9a in QEventLoop::exec (this=this@entry=0x7f8b6cfc4e10, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f8b765001f4 in QThread::exec (this=this@entry=0x7f8b769a9b00 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:507 #7 0x7f8b7693b445 in QDBusConnectionManager::run (this=0x7f8b769a9b00 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #8 0x7f8b7650478c in QThreadPrivate::start (arg=0x7f8b769a9b00 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:368 #9 0x7f8b74c72454 in start_thread (arg=0x7f8b6cfc5700) at pthread_create.c:333 #10 0x7f8b75c3a5dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 18 (Thread 0x7f8b6768d700 (LWP 32700)): #0 0x7f8b75c314fd in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f8b731fd6dc in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7f8b60295560, timeout=3330855, context=0x7f8b6990) at /var/tmp/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:4228 #2 g_main_context_iterate (context=context@entry=0x7f8b6990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:3924 #3 0x7f8b731fd7ec in g_main_context_iteration (context=0x7f8b6990, may_block=1) at /var/tmp/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:3990 #4 0x7f8b766f369c in QEventDispatcherGlib::processEvents (this=0x7f8b68c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #5 0x7f8b766a6d9a in QEventLoop::exec (this=this@entry=0x7f8b6768ce40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f8b765001f4 in QThread::exec (this=) at thread/qthread.cpp:507 #7 0x7f8b7650478c in QThreadPrivate::start (arg=0x2010e80) at thread/qthread_unix.cpp:368 #8 0x7f8b74c72454 in start_thread (arg=0x7f8b6768d700) at pthread_create.c:333 #9 0x7f8b75c3a5dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 17 (Thread 0x7f8b66e8c700 (LWP 32713)): #0 0x7f8b75c314fd in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f8b731fd6dc in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7f8b58003020, timeout=3330881, context=0x7f8b58000990) at /var/tmp/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:4228 #2 g_main_context_iterate (context=context@entry=0x7f8b58000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:3924 #3 0x7f8b731fd7ec in g_main_context_iteration (context=0x7f8b58000990, may_block=1) at /var/tmp/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:3990 #4 0x7f8b766f369c in QEventDispatcherGlib::processEvents (this=0x7f8b580008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #5 0x7f8b766a6d9a in QEventLoop::exec (this=this@entry=0x7f8b66e8be40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f8b765001f4 in QThread::exec (this=) at thread/qthread.cp
[kmail2] [Bug 356634] Kmail Randomly Hangs On Email Deletion
https://bugs.kde.org/show_bug.cgi?id=356634 Andreas K. Huettel changed: What|Removed |Added CC||dilfri...@gentoo.org -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 --- Comment #51 from Andreas K. Huettel --- (In reply to Daniel Vrátil from comment #50) > The only fix for the "Multiple merge candidates" error is to run Akonadi > Console, go to "Browser" tab, right-click the broken folder and select > "Clear Akonadi cache". Then restart Akonadi and it will re-fetch content of > the broken folder from the IMAP server. Dan, if I've been working on the folder in the meantime locally, in particular moving e-mails into that folder, are these mails lost then? -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 Andreas K. Huettel changed: What|Removed |Added Platform|Archlinux Packages |unspecified -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 Andreas K. Huettel changed: What|Removed |Added Summary|GMail: "Multiple merge |GMail, Novell Groupwise, |candidates, aborting" |other IMAP: "Multiple merge ||candidates, aborting" CC||dilfri...@gentoo.org --- Comment #18 from Andreas K. Huettel --- Same here observed with Novell Groupwise server. Gentoo, kmail 4.14.3, akonadi 1.13.0 -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 311292] Select failed, server replied: A001162 NO SELECT ( 8908 )
https://bugs.kde.org/show_bug.cgi?id=311292 Andreas K. Huettel changed: What|Removed |Added Resolution|WAITINGFORINFO |INVALID Status|NEEDSINFO |RESOLVED --- Comment #3 from Andreas K. Huettel --- In the meantime I put up some efforts to figure out what happens. Result: This was caused by a bug in Novell Groupwise, which for mysterious reasons starts sending negative (!) UUIDS. Hilarity ensues. Not much we can do here, setting invalid. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kontact] [Bug 324403] Fatal "Could not create collection outbox" following upgrade to 4.11.0, duplicate special folders, locale issue?
https://bugs.kde.org/show_bug.cgi?id=324403 --- Comment #9 from Andreas K. Huettel --- There is an easier workaround. Start akonadiconsole and look at your local folders. If you have "Duplicates" there, e.g. two times an "Outbox" or two times a "Waste bin", for example with a different localization (I've seen both "Papierkorb" and "Mülleimer" being present), delete the *empty* one. Afterwards kmail should start fine. -- 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
[Akonadi] [Bug 323642] segfault of plasma-desktop upon startup / login
https://bugs.kde.org/show_bug.cgi?id=323642 Andreas K. Huettel changed: What|Removed |Added Summary|Error appeared upon startup |segfault of plasma-desktop ||upon startup / login -- 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
[Akonadi] [Bug 323642] Error appeared upon startup
https://bugs.kde.org/show_bug.cgi?id=323642 --- Comment #7 from Andreas K. Huettel --- Created attachment 84086 --> https://bugs.kde.org/attachment.cgi?id=84086&action=edit New crash information added by DrKonqi plasma-desktop (4.11.4) on KDE Platform 4.11.4 using Qt 4.8.5 - What I was doing when the application crashed: Log in. Immediate segfault of plasma-desktop. -- Backtrace (Reduced): #6 QModelIndex (other=..., this=) at /usr/include/qt4/QtCore/qabstractitemmodel.h:65 #7 KDescendantsProxyModel::mapFromSource (this=0x3c40980, sourceIndex=...) at /var/tmp/portage/kde-base/kdelibs-4.11.4/work/kdelibs-4.11.4/kdeui/itemviews/kdescendantsproxymodel.cpp:462 #8 0x7f28ad3aaf0f in KDescendantsProxyModelPrivate::sourceDataChanged (this=, topLeft=..., bottomRight=...) at /var/tmp/portage/kde-base/kdelibs-4.11.4/work/kdelibs-4.11.4/kdeui/itemviews/kdescendantsproxymodel.cpp:963 [...] #10 0x7f28ac691387 in QAbstractItemModel::dataChanged (this=, _t1=..., _t2=...) at .moc/release-shared/moc_qabstractitemmodel.cpp:163 #11 0x7f2800b086f3 in Akonadi::EntityTreeModelPrivate::dataChanged (this=this@entry=0x3c24340, top=..., bottom=...) at /var/tmp/portage/kde-base/kdepimlibs-4.11.4/work/kdepimlibs-4.11.4/akonadi/entitytreemodel_p.cpp:1687 -- 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
[Akonadi] [Bug 323642] Error appeared upon startup
https://bugs.kde.org/show_bug.cgi?id=323642 Andreas K. Huettel changed: What|Removed |Added CC||dilfri...@gentoo.org -- 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
[kmail2] [Bug 312460] Kmail can not show correct number of unread mails
https://bugs.kde.org/show_bug.cgi?id=312460 Andreas K. Huettel changed: What|Removed |Added CC||dilfri...@gentoo.org -- 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
[kmail2] [Bug 286481] Unable to open attachments in encrypted messages
https://bugs.kde.org/show_bug.cgi?id=286481 --- Comment #27 from Andreas K. Huettel --- (In reply to comment #26) > (In reply to comment #25) > > i have noticed that the bug only occurs, when the mail is signed AND > > encrypted. All mails that are only encrypted are working. When i have a > > signed and encrypted mail, the attachement name shown on the top of the mail > > is called encrypted.asc and not . for encrypted mails > > (not signed) this line states the attached file name. so maybe this > > obversations are somewhat connected? > > Actually this is exactly the bug that was solved. It sounds for me, that the > patch was NOT included in the version you have used. Plaese look into your > code, that you compile, to make sure that the pach is added (only three > lines patch). My fault. Till please also upgrade to kdepim-common-libs-4.11.2-r1. I applied the patch in the wrong part of our split kdepim; it got happily applied but never compiled. (side note, if you need help in splitting kdepim into different repositories, have a look at our ebuilds :) -- 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
[kmail2] [Bug 286481] Unable to open attachments in encrypted messages
https://bugs.kde.org/show_bug.cgi?id=286481 --- Comment #21 from Andreas K. Huettel --- Hey Till, yes I did indeed add this commit. Please make sure that you re-started everything relevant... it would be best if you log out and log back in again! -- 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
[Akonadi] [Bug 323762] IMAP error every time after sending mail and saving to sent-mail IMAP folder (kde 4.11.0)
https://bugs.kde.org/show_bug.cgi?id=323762
--- Comment #5 from Andreas K. Huettel ---
(In reply to comment #4)
> I found a slightly suspect IMAP sequence, but I'm not familiar enough with
> the protocol to determine if this is the cause of my problem or not:
> C: A84 APPEND "Sent" (\Seen $SENT) {1214}
> S: A84 BAD Invalid flag specified
this is afaik the reason why your mail does not exist on the server, the APPEND
command fails. No idea why.
> C: A85 SELECT "Sent"
> S: * 391 EXISTS
> S: * 0 RECENT
> S: * OK UID validity status [ UIDVALIDITY 8742276 ]
> S: * OK Predicted next UID [ UIDNEXT 394 ]
> S: * FLAGS ( \Seen \Deleted \Answered \Forwarded \Redirected \Flagged
> \Hidden \Draft $MDNSent )
> S: * OK Permanent flags [ PERMANENTFLAGS ( \Seen \Deleted \Answered
> \Forwarded \Redirected \Flagged \Hidden \Draft $MDNSent ) ]
> S: A85 OK SELECT completed [ READ-WRITE ]
> C: A86 UID STORE +FLAGS (\Seen $SENT)
> S: A86 BAD Invalid sequence specified
this is the same error as I have above, the UID STORE command is missing the
actual uid.
I don't know if these are related. In my case the e-mails do end up in the
sent-mail folder.
--
You are receiving this mail because:
You are on the CC list for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 323762] IMAP error every time after sending mail and saving to sent-mail IMAP folder (kde 4.11.0)
https://bugs.kde.org/show_bug.cgi?id=323762 --- Comment #3 from Andreas K. Huettel --- environment variable, sorry -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 323762] IMAP error every time after sending mail and saving to sent-mail IMAP folder (kde 4.11.0)
https://bugs.kde.org/show_bug.cgi?id=323762 --- Comment #2 from Andreas K. Huettel --- set the environment file KIMAP_LOGFILE to some logfile with path, and re-start akonadi -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kontact] [Bug 324403] Fatal "Could not create collection outbox" following upgrade to 4.11.0, duplicate special folders, locale issue?
https://bugs.kde.org/show_bug.cgi?id=324403
--- Comment #4 from Andreas K. Huettel ---
Additional datapoints:
* I saw the problem on upgrade from 4.11rc2 to 4.11.0 (packager prerelease).
kontact starts up, shows a dialog box "serious problem, program terminated:
"Could not create collection Entwürfe resourceId: 9" and terminates on OK.
Entwürfe is german for Drafts.
* From memory and maybe related, some of the special folders (like "Recycle
Bin") were duplicated with different translations ("Papierkorb" and
"Mülleimer").
--
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
[kontact] [Bug 324403] Fatal "Could not create collection outbox" following upgrade to 4.11.0, duplicate special folders, locale issue?
https://bugs.kde.org/show_bug.cgi?id=324403 Andreas K. Huettel changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||dilfri...@gentoo.org Summary|Fatal "Could not create |Fatal "Could not create |collection outbox" |collection outbox" |following upgrade to 4.11.0 |following upgrade to ||4.11.0, duplicate special ||folders, locale issue? Ever confirmed|0 |1 --- Comment #3 from Andreas K. Huettel --- Also seen by me on Gentoo upon upgrade to 4.11. (The trick to get kmail2 running again is to remove the duplicate special local folders with akonadiconsole. That's just a workaround though.) -- 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
[kmail2] [Bug 286481] Unable to open attachments in encrypted messages
https://bugs.kde.org/show_bug.cgi?id=286481 Andreas K. Huettel changed: What|Removed |Added CC||dilfri...@gentoo.org Version|4.11 beta2 |4.11 -- 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
[Akonadi] [Bug 323762] New: IMAP error every time after sending mail and saving to sent-mail IMAP folder (kde 4.11.0)
https://bugs.kde.org/show_bug.cgi?id=323762 Bug ID: 323762 Summary: IMAP error every time after sending mail and saving to sent-mail IMAP folder (kde 4.11.0) Classification: Unclassified Product: Akonadi Version: 4.11 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: IMAP resource Assignee: er...@kde.org Reporter: dilfri...@gentoo.org CC: kdepim-bugs@kde.org, vkra...@kde.org My sent-mail folder is on an IMAP resource. After sending an e-mail I always obtain a popup NO UID STORE Invalid parameter: +FLAGS ( 61FF ) It seems like some parameter to the UID STORE command is missing (to be precise the UID of the uploaded message). Here is part of an IMAP transscript, starting directly after the message data that has been uploaded: S: A005284 OK APPEND completed [ APPENDUID 1322069043 4410 ] C: A005285 SELECT "Sent Items" S: * 188 EXISTS S: * 1 RECENT S: * OK [ UIDVALIDITY 1322069043 ] S: * OK [ UIDNEXT 4411 ] S: * FLAGS ( \Answered \Flagged \Deleted \Draft \Seen ) S: * OK [ PERMANENTFLAGS ( \Answered \Flagged \Deleted \Draft \Seen \* ) ] S: A005285 OK SELECT completed [ READ-WRITE ] C: A005286 UID STORE +FLAGS (\SEEN $SENT) S: A005286 NO UID STORE Invalid parameter: +FLAGS ( 61FF ) C: A005287 SELECT "INBOX" The IMAP server is Novell Groupwise 2012. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 319842] KMail ignores negative acknowledgements from IMAP server
https://bugs.kde.org/show_bug.cgi?id=319842 Andreas K. Huettel changed: What|Removed |Added CC||dilfri...@gentoo.org -- 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
[Akonadi] [Bug 306390] creating folders on IMAP-Server removes "i" in the name
https://bugs.kde.org/show_bug.cgi?id=306390 Andreas K. Huettel changed: What|Removed |Added CC||dilfri...@gentoo.org -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 289062] kmail2, 4.7.90: cannot delete e-mails in inbox (all back after server sync)
https://bugs.kde.org/show_bug.cgi?id=289062 Andreas K. Huettel changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from Andreas K. Huettel --- Has been working fine for quite some time now (I'm on 4.9.98 now). Most likely fixed. -- 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
[kmail2] [Bug 313889] Forwarding an e-mail "inline" in the text does not actually forward anything
https://bugs.kde.org/show_bug.cgi?id=313889 Andreas K. Huettel changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|FIXED |--- --- Comment #3 from Andreas K. Huettel --- So where should I reset the templates, if not in my personal configuration? (see comment 2) -- 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
[kmail2] [Bug 313889] Forwarding an e-mail "inline" in the text does not actually forward anything
https://bugs.kde.org/show_bug.cgi?id=313889 --- Comment #2 from Andreas K. Huettel --- Hmm, all three identities have no "self-made templates" set (the box to customize them is unchecked). When I check it to customize it, the following is filled in as default for forward: %REM="Standardvorlage für Weiterleitungen"%- -- Weitergeleitete Nachricht -- Betreff: %OFULLSUBJECT Datum: %ODATE, %OTIMELONG Von: %OFROMADDR %OADDRESSEESADDR %TEXT - This fixes forwarding, but I guess "enabling customized templates" is not the real solution. When I press "Copy global default templates", the content of the "forward template" is replaced with a single line %BLANK which seems wrong somehow. ??? -- 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
[kmail2] [Bug 313889] New: Forwarding an e-mail "inline" in the text does not actually forward anything
https://bugs.kde.org/show_bug.cgi?id=313889 Bug ID: 313889 Summary: Forwarding an e-mail "inline" in the text does not actually forward anything Classification: Unclassified Product: kmail2 Version: 4.9.98 RC3 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: dilfri...@gentoo.org When I select "Forward", "im Text" (inline? within the message text?) in the composer, an empty e-mail (except for my signature) is created. No trace of any forwarding. (Selecting some text with the mouse beforehand does not help either.) -- 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 285935] Cannot fetch item in Offline mode? How do I go offline then?
https://bugs.kde.org/show_bug.cgi?id=285935 Andreas K. Huettel changed: What|Removed |Added CC||dilfri...@gentoo.org --- Comment #3 from Andreas K. Huettel --- This still happens with KMail 4.9.4. -- 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 306005] Violation of rfc822: kmail2 end of line handling, CR (0x0D) is dropped from messages and not inserted when sending messages
https://bugs.kde.org/show_bug.cgi?id=306005 --- Comment #2 from Andreas K. Huettel --- Someone with appropriate permissions- please change the summary, this bug DOES invalidate signatures made with GPG, rendering the signing support partly useless. -- 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 311292] New: Select failed, server replied: A001162 NO SELECT ( 8908 )
https://bugs.kde.org/show_bug.cgi?id=311292 Bug ID: 311292 Severity: normal Version: 4.9 Priority: NOR CC: kdepim-bugs@kde.org, vkra...@kde.org Assignee: er...@kde.org Summary: Select failed, server replied: A001162 NO SELECT ( 8908 ) Classification: Unclassified OS: Linux Reporter: dilfri...@gentoo.org Hardware: Other Status: UNCONFIRMED Component: IMAP resource Product: Akonadi Server is Novell Groupwise. After a while, this error Select failed, server replied: A001162 NO SELECT ( 8908 ) pops up, and keeps coming every second or so. Only way to stop it is to restart akonadi. This may obviously be some server-side error, however it's not handled really gracefully in the client... especially if you come back to the office in the morning, the notification system has a few thousand messages for you and still keeps making a noise every second. :) Reproducible: Sometimes Steps to Reproduce: 1. Run Akonadi server with IMAP resource on Novell Groupwise 2. Wait -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 311265] New: Remember if IMAP server does not support a feature, do not warn again
https://bugs.kde.org/show_bug.cgi?id=311265 Bug ID: 311265 Severity: wishlist Version: unspecified Priority: NOR CC: kdepim-bugs@kde.org, vkra...@kde.org Assignee: er...@kde.org Summary: Remember if IMAP server does not support a feature, do not warn again Classification: Unclassified OS: Linux Reporter: dilfri...@gentoo.org Hardware: Other Status: UNCONFIRMED Component: IMAP resource Product: Akonadi I have my e-mail remotely on a GroupWise IMAP server. It seems like that server does not support annotations, and I always obtain some warning message about a failed SET ANNOTATION command after changing folder properties. It would be great if the IMAP resource could somehow remember what the server does not support, and at least not warn again and again... -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 308122] After some weeks downtime, google calendar fetch fails. "The requested minimum modification time lies too far in the past"
https://bugs.kde.org/show_bug.cgi?id=308122 Andreas K. Huettel changed: What|Removed |Added Hardware|Other |Gentoo Packages -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 308122] New: After some weeks downtime, google calendar fetch fails. "The requested minimum modification time lies too far in the past"
https://bugs.kde.org/show_bug.cgi?id=308122 Bug ID: 308122 Severity: normal Version: 4.9 Priority: NOR CC: kdepim-bugs@kde.org Assignee: dvra...@redhat.com Summary: After some weeks downtime, google calendar fetch fails. "The requested minimum modification time lies too far in the past" Classification: Unclassified OS: Linux Reporter: dilfri...@gentoo.org Hardware: Other Status: UNCONFIRMED Component: Google Resource Product: Akonadi Gentoo Linux, KDE 4.9.2 with libkgapi-0.4.2 After ~3 weeks downtime, google calendar fetch fails on every login with an error message: Resource does not exist anymore. Google replied: "The requested minimum modification time lies too far in the past" Please tell me if you need any additional info... -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 306323] [kdepimlibs] missed boost dependency in KdepimLibsConfig.cmake.in
https://bugs.kde.org/show_bug.cgi?id=306323 --- Comment #30 from Andreas K. Huettel --- the three possible solutions are: a) fix boost header location in Gentoo (which is what Christophe wants us to do). Since Gentoo still wants to support multiple concurrent Boost installations, and since FindBoost.cmake actually finds everything correctly, this is not going to happen. b) add a FindBoost call to the CMakeLists.txt file of *every* kde app that uses kdepimlibs (this is how Christophe wants to work around the problem for kde sc apps, see comment 24) c) add the one-line patch to kdepimlibs build system that records and re-exports boost include location for the boost that kdepimlibs was compiled against. On the whole this bug is a neat example how people dont read or dont bother to think through what others write, and resort to nitpicking instead. Since we're unwilling to patch every single application using kdepimlibs, we'll probably end up applying Alex's patch locally. -- 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 306323] [kdepimlibs] missed boost dependency in KdepimLibsConfig.cmake.in
https://bugs.kde.org/show_bug.cgi?id=306323
--- Comment #15 from Andreas K. Huettel ---
> - Adding the boost include dir to kdepimlibs_include_dirs supposes that :
> 1/ Boost was already found,
>From /CMakeLists.txt:
set(Boost_MINIMUM_VERSION "1.34.0")
if (WIN32)
find_package(Boost ${Boost_MINIMUM_VERSION}) # (jstaniek) temp. fix unless we
have graph library, not just headers
else()
find_package(Boost ${Boost_MINIMUM_VERSION} COMPONENTS graph)
endif()
macro_log_feature(Boost_FOUND "Boost C++ Libraries" "Required by core
components" "http://www.boost.org"; TRUE "${Boost_MINIMUM_VERSION}" "Boost must
include the boost-graph library")
[...]
include_directories (${CMAKE_SOURCE_DIR} ${CMAKE_BINARY_DIR} ${KDE4_INCLUDES}
${Boost_INCLUDE_DIR})
OK, it's not marked as REQUIRED. Which means build takes place as well if it is
not found. However:
> 2/ All of kdepimlibs needs boost
>
> These two statements are incorrect. Adding a find_package(boost) is excluded
> because of 2 and the posted patch is wrong because of 1.
The find_package(boost) is already there, see above.
And please have a look at the following output:
huettel@grenadine ~/tmp/kdepimlibs-4.9.1 $ find . -name CMakeLists.txt -exec
grep -i boost {} +
./kblog/CMakeLists.txt:include_directories(${Boost_INCLUDE_DIR})
./kioslave/imap4/CMakeLists.txt:include_directories(${imap4_optional_includes}
${Boost_INCLUDE_DIR})
./syndication/tests/CMakeLists.txt:include_directories( ../
${Boost_INCLUDE_DIR} )
./syndication/CMakeLists.txt:include_directories( ${Boost_INCLUDE_DIR} )
./CMakeLists.txt:set(Boost_MINIMUM_VERSION "1.34.0")
./CMakeLists.txt: find_package(Boost ${Boost_MINIMUM_VERSION}) # (jstaniek)
temp. fix unless we have graph library, not just headers
./CMakeLists.txt: find_package(Boost ${Boost_MINIMUM_VERSION} COMPONENTS
graph)
./CMakeLists.txt:macro_log_feature(Boost_FOUND "Boost C++ Libraries" "Required
by core components" "http://www.boost.org"; TRUE "${Boost_MINIMUM_VERSION}"
"Boost must include the boost-graph library")
./CMakeLists.txt:include_directories (${CMAKE_SOURCE_DIR} ${CMAKE_BINARY_DIR}
${KDE4_INCLUDES} ${Boost_INCLUDE_DIR})
./gpgme++/CMakeLists.txt:include_directories( ${GPGME_INCLUDES}
${Boost_INCLUDE_DIR} )
./gpgme++/CMakeLists.txt:set( GPGMEPP_INCLUDE ${INCLUDE_INSTALL_DIR}
${GPGME_INCLUDES} ${Boost_INCLUDE_DIR} )
./mailtransport/CMakeLists.txt: ${Boost_INCLUDE_DIR}
./akonadi/tests/testrunner/CMakeLists.txt:${Boost_INCLUDE_DIR}
./akonadi/tests/etm_test_app/CMakeLists.txt:${Boost_INCLUDE_DIR}
./akonadi/tests/CMakeLists.txt:${Boost_INCLUDE_DIR}
./akonadi/tests/benchmarker/CMakeLists.txt:${Boost_INCLUDE_DIR}
./akonadi/CMakeLists.txt: ${Boost_INCLUDE_DIR}
./akonadi/kmime/CMakeLists.txt:${Boost_INCLUDE_DIR}
./akonadi/contact/CMakeLists.txt:${Boost_INCLUDE_DIR}
./includes/tests/CMakeLists.txt: ${Boost_INCLUDE_DIR}
./kimap/tests/CMakeLists.txt:include_directories( ${CMAKE_SOURCE_DIR}/kimap
${Boost_INCLUDE_DIR})
./kimap/CMakeLists.txt:include_directories( ${CMAKE_SOURCE_DIR}/kioslave
${SASL2_INCLUDE_DIR} ${Boost_INCLUDE_DIR} )
./kldap/CMakeLists.txt: ${Boost_INCLUDE_DIR}
./qgpgme/tests/CMakeLists.txt:include_directories( ${Boost_INCLUDE_DIR} )
./qgpgme/CMakeLists.txt: include_directories( ${GPGME_INCLUDES}
${CMAKE_SOURCE_DIR}/gpgme++ ${Boost_INCLUDE_DIR} )
This means kblog, kioslave/imap4, syndication, gpgme++, mailtransport, akonadi,
kimap, kldap, and qgpgme already use Boost includes in the CMakeLists.txt,
which makes me strongly doubt if they build without Boost. Is kdepimlibs useful
if you switch off these components? (Not that it is done anywhere in the build
system.)
> And even without 1 & 2, that would mean we'd have to support FindBoost.cmake
You already do.
--
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 306323] [kdepimlibs] missed boost dependency in KdepimLibsConfig.cmake.in
https://bugs.kde.org/show_bug.cgi?id=306323 Andreas K. Huettel changed: What|Removed |Added CC||dilfri...@gentoo.org --- Comment #12 from Andreas K. Huettel --- You have an explicit dependency on Boost, and this means you should also detect and provide the required include directories. Even if an external application does not use *any* boost functions itself it will fail using kdepimlibs. So, the external application does *not* depend on boost, but kdepimlibs does. Resolving as invalid is not productive. -- 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 306005] kmail2 is not compliant with RfC 822 in end of line handling, CR (0x0D) is droped
https://bugs.kde.org/show_bug.cgi?id=306005 Andreas K. Huettel changed: What|Removed |Added CC||dilfri...@gentoo.org -- 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 289277] kmail_clamav.sh causes email duplication
https://bugs.kde.org/show_bug.cgi?id=289277 Andreas K. Huettel changed: What|Removed |Added CC||dilfri...@gentoo.org -- 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 298313] New: kontact crash when re-opening mail "stuck" in outbox
https://bugs.kde.org/show_bug.cgi?id=298313 Bug ID: 298313 Severity: crash Version: 4.8.2 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: kontact crash when re-opening mail "stuck" in outbox Classification: Unclassified OS: Linux Reporter: dilfri...@gentoo.org Hardware: Compiled Sources Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.8.2) KDE Platform Version: 4.8.2 (4.8.2) (Compiled from sources) Qt Version: 4.8.1 Operating System: Linux 3.2.2-hardened-r1 x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: Tried to send an e-mail to many recipients. One of the addresses was incorrect, and the mail server refused it, so it remained in the outbox. Doubleclicked on it to edit, and kontact crashed. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0x360b118c760 (LWP 31583))] Thread 4 (Thread 0x3609690b700 (LWP 31584)): #0 pthread_cond_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x0360ad77d8a4 in scavengerThread (this=0x360ae12aec0) at wtf/FastMalloc.cpp:2495 #2 WTF::TCMalloc_PageHeap::runScavengerThread (context=0x360ae12aec0) at wtf/FastMalloc.cpp:1618 #3 0x0360a8b21c5c in start_thread (arg=0x3609690b700) at pthread_create.c:301 #4 0x0360ae4889cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 3 (Thread 0x3609600a700 (LWP 31585)): #0 0x0360ae47fd13 in *__GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x0360a7947028 in g_main_context_poll (n_fds=1, fds=0x360900021f0, timeout=-1, context=0x3609970, priority=) at gmain.c:3402 #2 g_main_context_iterate (context=0x3609970, block=1, dispatch=1, self=) at gmain.c:3084 #3 0x0360a7947531 in g_main_context_iteration (context=0x3609970, may_block=1) at gmain.c:3152 #4 0x0360af9f9e7f in QEventDispatcherGlib::processEvents (this=0x3c1be0d020, flags=) at kernel/qeventdispatcher_glib.cpp:424 #5 0x0360af9c1cd2 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #6 0x0360af9c20b5 in QEventLoop::exec (this=0x36096009e10, flags=...) at kernel/qeventloop.cpp:204 #7 0x0360af89c5f8 in QThread::exec (this=) at thread/qthread.cpp:501 #8 0x0360af89f503 in QThreadPrivate::start (arg=0x3c1be0cb40) at thread/qthread_unix.cpp:298 #9 0x0360a8b21c5c in start_thread (arg=0x3609600a700) at pthread_create.c:301 #10 0x0360ae4889cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 2 (Thread 0x36082606700 (LWP 4010)): #0 0x0360ae482263 in select () at ../sysdeps/unix/syscall-template.S:82 #1 0x0360af99a10c in QProcessManager::run (this=0x360afd35d40) at io/qprocess_unix.cpp:245 #2 0x0360af89f503 in QThreadPrivate::start (arg=0x360afd35d40) at thread/qthread_unix.cpp:298 #3 0x0360a8b21c5c in start_thread (arg=0x36082606700) at pthread_create.c:301 #4 0x0360ae4889cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 1 (Thread 0x360b118c760 (LWP 31583)): [KCrash Handler] #6 QCoreApplication::postEvent (receiver=0x3c1e43ffb0, event=0x3c1e5b3370, priority=0) at kernel/qcoreapplication.cpp:1273 #7 0x0360af9dbf56 in QObject::event (this=0x3c1e43ffb0, e=) at kernel/qobject.cpp:1195 #8 0x0360aec3ca64 in QApplicationPrivate::notify_helper (this=0x3c1bc3ff70, receiver=0x3c1e43ffb0, e=0x3c1f97fa50) at kernel/qapplication.cpp:4554 #9 0x0360aec41c2b in QApplication::notify (this=, receiver=0x3c1e43ffb0, e=0x3c1f97fa50) at kernel/qapplication.cpp:4415 #10 0x0360b04ecb66 in KApplication::notify (this=0x3cb08df6240, receiver=0x3c1e43ffb0, event=0x3c1f97fa50) at /opt/virtual/tmp-portage/portage/kde-base/kdelibs-4.8.2/work/kdelibs-4.8.2/kdeui/kernel/kapplication.cpp:311 #11 0x0360af9c31eb in QCoreApplication::notifyInternal (this=0x3cb08df6240, receiver=0x3c1e43ffb0, event=0x3c1f97fa50) at kernel/qcoreapplication.cpp:876 #12 0x0360af9c70a7 in sendEvent (event=0x3c1f97fa50, receiver=0x3c1e43ffb0) at kernel/qcoreapplication.h:231 #13 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x3c1bc0bb40) at kernel/qcoreapplication.cpp:1500 #14 0x0360af9f9c87 in sendPostedEvents () at kernel/qcoreapplication.h:236 #15 postEventSourceDispatch (s=) at kernel/qeventdispatcher_glib.cpp:279 #16 0x0360a7946ada in g_main_dispatch (context=0x3c1bc428e0) at gmain.c:2441 #17 g_main_context_dispatch (context=0x3c1bc428e0) at gmain.c:3011 #18 0x0360a7947308 in g_main_context_iterate (context=0x3c1bc428e0, block=1, dispatch=1, self=) at gmain.c:3089 #19 0x0360a7947531 in g_main_context_iteration (context=0x3c1bc428e0, may_block=1) at gmain.c:3152 #20 0x0360af9f9e7f in QEventDispatcherGlib::processEvents (this=0x3c1bc
[Bug 295138] kmail-4.8.0 crashes on Ctrl-P
https://bugs.kde.org/show_bug.cgi?id=295138 --- Comment #3 from Andreas K. Huettel --- Created attachment 70338 --> https://bugs.kde.org/attachment.cgi?id=70338&action=edit New crash information added by DrKonqi kontact (4.8.2) on KDE Platform 4.8.2 (4.8.2) using Qt 4.8.1 - What I was doing when the application crashed: Try to print calendar month from dialog box. -- Backtrace (Reduced): #6 0x02571ee93d0e in QCUPSSupport::printerOption (this=0x74f6d9f570, key=...) at painting/qcups.cpp:251 #7 0x02571f15e363 in QUnixPrintWidgetPrivate::_q_printerChanged (this=0x74f6f816e0, index=) at dialogs/qprintdialog_unix.cpp:830 #8 0x02571f15f04b in QUnixPrintWidgetPrivate::QUnixPrintWidgetPrivate (this=0x74f6f816e0, p=) at dialogs/qprintdialog_unix.cpp:737 #9 0x02571f15f39b in QUnixPrintWidget::QUnixPrintWidget (this=0x74f6e08ee0, printer=0x0, parent=) at dialogs/qprintdialog_unix.cpp:1062 #10 0x02571f15f443 in QPrintDialogPrivate::init (this=) at dialogs/qprintdialog_unix.cpp:386 -- 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 295138] kmail-4.8.0 crashes on Ctrl-P
https://bugs.kde.org/show_bug.cgi?id=295138 Andreas K. Huettel changed: What|Removed |Added CC||dilfri...@gentoo.org -- 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 295138] kmail-4.8.0 crashes on Ctrl-P
https://bugs.kde.org/show_bug.cgi?id=295138 Andreas K. Huettel changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|DUPLICATE |--- --- Comment #2 from Andreas K. Huettel --- > *** This bug has been marked as a duplicate of bug 223809 *** How can this be a duplicate of a bug that was *resolved* two years ago in kdepim *svn*? The crash was on kdepim-4.8.0 and still occurs on kdepim-4.8.2 ! -- 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 295138] New: kmail-4.8.0 crashes on Ctrl-P
https://bugs.kde.org/show_bug.cgi?id=295138 Summary: kmail-4.8.0 crashes on Ctrl-P Product: kontact Version: unspecified Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: dilfri...@gentoo.org Application: kontact (4.8.0) KDE Platform Version: 4.8.00 (4.8.0 (Compiled from sources) Qt Version: 4.8.0 Operating System: Linux 3.2.1-gentoo-r2 x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: Press Ctrl-P to print an e-mail. Note: **no** recent Cups restart as in "duplicates" from DrKonqui -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0x7f385ce37760 (LWP 23402))] Thread 6 (Thread 0x7f3842883700 (LWP 23403)): #0 pthread_cond_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f38594288d4 in scavengerThread (this=0x7f3859dd5f40) at wtf/FastMalloc.cpp:2495 #2 WTF::TCMalloc_PageHeap::runScavengerThread (context=0x7f3859dd5f40) at wtf/FastMalloc.cpp:1618 #3 0x7f38547cfc5c in start_thread (arg=0x7f3842883700) at pthread_create.c:301 #4 0x7f385a1339cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 5 (Thread 0x7f3841f7a700 (LWP 23404)): #0 0x7f38535f4eb1 in g_main_context_iterate (context=0x7f385d9abc50, block=1, dispatch=1, self=) at gmain.c:3069 #1 0x7f38535f5531 in g_main_context_iteration (context=0x7f385d9abc50, may_block=1) at gmain.c:3152 #2 0x7f385b6a367e in QEventDispatcherGlib::processEvents (this=0x7f385d9ab9e0, flags=) at kernel/qeventdispatcher_glib.cpp:426 #3 0x7f385b66b462 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #4 0x7f385b66b845 in QEventLoop::exec (this=0x7f3841f79e10, flags=...) at kernel/qeventloop.cpp:204 #5 0x7f385b5465f8 in QThread::exec (this=) at thread/qthread.cpp:501 #6 0x7f385b549503 in QThreadPrivate::start (arg=0x7f385d9ab450) at thread/qthread_unix.cpp:298 #7 0x7f38547cfc5c in start_thread (arg=0x7f3841f7a700) at pthread_create.c:301 #8 0x7f385a1339cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 4 (Thread 0x7f3831cef700 (LWP 13816)): #0 0x7f385a140770 in pthread_mutex_unlock (mutex=0x7f3861c7b438) at forward.c:184 #1 0x7f38535f501c in g_main_context_poll (n_fds=1, fds=0x7f3861a9b0f0, timeout=-1, context=0x7f3861c7b430, priority=) at gmain.c:3401 #2 g_main_context_iterate (context=0x7f3861c7b430, block=1, dispatch=1, self=) at gmain.c:3084 #3 0x7f38535f5531 in g_main_context_iteration (context=0x7f3861c7b430, may_block=1) at gmain.c:3152 #4 0x7f385b6a367e in QEventDispatcherGlib::processEvents (this=0x7f385db69960, flags=) at kernel/qeventdispatcher_glib.cpp:426 #5 0x7f385b66b462 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #6 0x7f385b66b845 in QEventLoop::exec (this=0x7f3831ceedc0, flags=...) at kernel/qeventloop.cpp:204 #7 0x7f385b5465f8 in QThread::exec (this=) at thread/qthread.cpp:501 #8 0x7f385b6458f0 in QInotifyFileSystemWatcherEngine::run (this=0x7f385da5bcf0) at io/qfilesystemwatcher_inotify.cpp:248 #9 0x7f385b549503 in QThreadPrivate::start (arg=0x7f385da5bcf0) at thread/qthread_unix.cpp:298 #10 0x7f38547cfc5c in start_thread (arg=0x7f3831cef700) at pthread_create.c:301 #11 0x7f385a1339cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 3 (Thread 0x7f3834586700 (LWP 14691)): #0 pthread_cond_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f385b54a65b in wait (time=18446744073709551615, this=0x7f3861b08d00) at thread/qwaitcondition_unix.cpp:86 #2 QWaitCondition::wait (this=, mutex=0x7f3862e6c790, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:158 #3 0x7f385ae6cbc4 in QFileInfoGatherer::run (this=0x7f3862e6c780) at dialogs/qfileinfogatherer.cpp:214 #4 0x7f385b549503 in QThreadPrivate::start (arg=0x7f3862e6c780) at thread/qthread_unix.cpp:298 #5 0x7f38547cfc5c in start_thread (arg=0x7f3834586700) at pthread_create.c:301 #6 0x7f385a1339cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 2 (Thread 0x7f3821230700 (LWP 14692)): #0 0x7f385a140747 in pthread_mutex_lock (mutex=0x7f3862eccd48) at forward.c:182 #1 0x7f38535f4914 in g_main_context_dispatch (context=0x7f3862eccd40) at gmain.c:3007 #2 0x7f38535f5308 in g_main_context_iterate (context=0x7f3862eccd40, block=1, dispatch=1, self=) at gmain.c:3089 #3 0x7f38535f5531 in g_main_context_iteration (context=0x7f3862eccd40, may_block=1) at gmain.c:3152 #4 0x7f385b6a367e in QEventDispatcherGlib::processEvents (this=0x7f385ee158a0, flags=) at kernel/qeventdispatcher_glib.cpp:426 #5 0x7f385b66b462 in
[Bug 294489] New: imap resource crashed after changing(?) account settings
https://bugs.kde.org/show_bug.cgi?id=294489 Summary: imap resource crashed after changing(?) account settings Product: Akonadi Version: 4.8 Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: IMAP resource AssignedTo: er...@kde.org ReportedBy: dilfri...@gentoo.org CC: vkra...@kde.org, kdepim-bugs@kde.org Application: akonadi_imap_resource (4.8) KDE Platform Version: 4.8.00 (4.8.0 (Compiled from sources) Qt Version: 4.8.0 Operating System: Linux 3.2.1-gentoo-r2 x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: Come back from 7days absence to office, unlock screen. A dialog informs me that the IMAP server has refused my password (possible, since we have password expiry and I may have changed it some time ago from another box). Select "Edit account settings" and enter correct password, press OK. IMAP resource crashes. -- Backtrace: Application: Uni Regensburg vom Typ IMAP-E-Mail-Server (akonadi_imap_resource), signal: Segmentation fault [KCrash Handler] #6 0x0050 in ?? () #7 0x7f2cc7bbeb07 in QObject::disconnect (sender=0x7f2cca2ffd40, signal=0x7f2cca5c5a29 "stateChanged(KIMAP::Session::State,KIMAP::Session::State)", receiver=0x7f2cca26bdf0, method=0x7f2cca502b49 "onSessionStateChanged(KIMAP::Session::State,KIMAP::Session::State)") at kernel/qobject.cpp:2891 #8 0x7f2cc88bb55b in SessionPool::killSession (this=0x7f2cca26bdf0, session=0x7f2cca2ffd40, termination=SessionPool::LogoutSession) at /opt/virtual/tmp-portage/portage/kde-base/kdepim-runtime-4.8.0/work/kdepim-runtime-4.8.0/resources/imap/sessionpool.cpp:175 #9 0x7f2cc88bbc79 in SessionPool::cancelSessionCreation (this=0x7f2cca26bdf0, session=0x7f2cca2ffd40, errorCode=2, errorMessage=...) at /opt/virtual/tmp-portage/portage/kde-base/kdepim-runtime-4.8.0/work/kdepim-runtime-4.8.0/resources/imap/sessionpool.cpp:227 #10 0x7f2cc88bc03c in SessionPool::onPasswordRequestDone (this=0x7f2cca26bdf0, resultType=, password=...) at /opt/virtual/tmp-portage/portage/kde-base/kdepim-runtime-4.8.0/work/kdepim-runtime-4.8.0/resources/imap/sessionpool.cpp:289 #11 0x7f2cc88bdf1f in SessionPool::qt_static_metacall (_o=, _c=, _id=, _a=) at /opt/virtual/tmp-portage/portage/kde-base/kdepim-runtime-4.8.0/work/kdepim-runtime-4.8.0_build/resources/imap/sessionpool.moc:94 #12 0x7f2cc7bbc343 in QMetaObject::activate (sender=0x7f2cca28c7e0, m=, local_signal_index=, argv=0x7fffeedcdf90) at kernel/qobject.cpp:3547 #13 0x7f2cc88a74f3 in PasswordRequesterInterface::done (this=, _t1=1, _t2=) at /opt/virtual/tmp-portage/portage/kde-base/kdepim-runtime-4.8.0/work/kdepim-runtime-4.8.0_build/resources/imap/passwordrequesterinterface.moc:118 #14 0x7f2cc88828b6 in SettingsPasswordRequester::askUserInput (this=0x7f2cca28c7e0, serverError=...) at /opt/virtual/tmp-portage/portage/kde-base/kdepim-runtime-4.8.0/work/kdepim-runtime-4.8.0/resources/imap/settingspasswordrequester.cpp:66 #15 0x7f2cc7bbb6e6 in QObject::event (this=0x7f2cca28c7e0, e=) at kernel/qobject.cpp:1195 #16 0x7f2cc6e1c994 in QApplicationPrivate::notify_helper (this=0x7f2cca04df60, receiver=0x7f2cca28c7e0, e=0x7f2ca0001030) at kernel/qapplication.cpp:4550 #17 0x7f2cc6e21b5b in QApplication::notify (this=, receiver=0x7f2cca28c7e0, e=0x7f2ca0001030) at kernel/qapplication.cpp:4411 #18 0x7f2cc4e1ea16 in KApplication::notify (this=0x7fffeedced10, receiver=0x7f2cca28c7e0, event=0x7f2ca0001030) at /opt/virtual/tmp-portage/portage/kde-base/kdelibs-4.8.0-r1/work/kdelibs-4.8.0/kdeui/kernel/kapplication.cpp:311 #19 0x7f2cc7ba297b in QCoreApplication::notifyInternal (this=0x7fffeedced10, receiver=0x7f2cca28c7e0, event=0x7f2ca0001030) at kernel/qcoreapplication.cpp:876 #20 0x7f2cc7ba6837 in sendEvent (event=0x7f2ca0001030, receiver=0x7f2cca28c7e0) at kernel/qcoreapplication.h:231 #21 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x7f2cca025a90) at kernel/qcoreapplication.cpp:1500 #22 0x7f2cc7bd9417 in sendPostedEvents () at kernel/qcoreapplication.h:236 #23 postEventSourceDispatch (s=0x7f2cca050d80) at kernel/qeventdispatcher_glib.cpp:279 #24 0x7f2cc2b8dada in g_main_dispatch (context=0x7f2cca050c90) at gmain.c:2441 #25 g_main_context_dispatch (context=0x7f2cca050c90) at gmain.c:3011 #26 0x7f2cc2b8e308 in g_main_context_iterate (context=0x7f2cca050c90, block=1, dispatch=1, self=) at gmain.c:3089 #27 0x7f2cc2b8e531 in g_main_context_iteration (context=0x7f2cca050c90, may_block=1) at gmain.c:3152 #28 0x7f2cc7bd960f in QEventDispatcherGlib::processEvents (this=0x7f2cca04bff0, flags=) at kernel/qeventdispatcher_glib.cpp:424 #29 0x7f2cc6edb6f6 in QGuiEventDispatcherGlib::processEvents (this=, flags=) at kernel/qguieventdispatcher_glib.cpp:204 #30
[Bug 291050] Cannot drag message into another folder
https://bugs.kde.org/show_bug.cgi?id=291050 --- Comment #2 from Andreas K. Huettel 2012-01-10 20:35:47 --- OK, to describe this a bit more: Start situation is, I have kontact open on the kmail page, with folder tree, message list of one folder and one e-mail displayed. I want to pull one message from the message list into one of the folders displayed on the folder tree. kde-4.7.97, kdepim-4.7.97, qt-4.7.4 (office desktop) 0) Mouse pointer is arrow. 1) Press mouse button down on message entry. 2) Start dragging. The mouse pointer changes to a hand (NOT displaying a "no valid target" or "dragging message" indicator). 3) When I move the mouse pointer rapidly I sometimes see the "no valid target" indicator flickering up. As soon as I stop moving the mouse, I only have a hand again. 4) I move the mouse pointer on top of the target folder. 5) I release the mouse button. For a short moment, a context-menu-like widget flickers up with a message similar to "Getting mime info", don't remember exactly 6) That's it, nothing else happens. Mail stays as it is. Interestingly, on my home desktop running kmail*1*, I very recently also see problems- so the bug may not be in kmail directly, but may e.g. have been introduced somewhere between libkdepim/kdelibs 4.7.85 and 97. Symptoms are slightly different: kde-4.7.97, **kdepim-4.4.11.1**, qt-4.7.4 (office desktop) 0) Mouse pointer is arrow. 1) Press mouse button down on message entry. 2) Start dragging. The mouse pointer changes to "dragging mode, no valid target" 3a) 80% of attempts: When I move the mouse pointer rapidly I sometimes see "valid drag target" flickering up, but the highlighted drag target is not exactly below the mouse pointer! As soon as I stop moving the mouse, I only have a "dragging mode, no valid target" pointer again and cannot drop anywhere. 3b) 20% of attempts: drag and drop works fine -- 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 291050] Cannot drag message into another folder
https://bugs.kde.org/show_bug.cgi?id=291050 --- Comment #1 from Andreas K. Huettel 2012-01-10 16:17:59 --- No change in kde-4.7.97, dragging of messages still broken -- 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 291050] New: Cannot drag message into another folder
https://bugs.kde.org/show_bug.cgi?id=291050 Summary: Cannot drag message into another folder Product: kmail2 Version: 4.8 Platform: Gentoo Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: message list AssignedTo: kdepim-bugs@kde.org ReportedBy: dilfri...@gentoo.org When I try to drag a message from the message list into a folder in the folder tree or the preferred folders list, nothing happens except some short flickering. (No menu popup, no message is copied or moved.) This may be related to bug 290869, since the mouse pointer is also not really behaving consistently (there is no visual feedback of the dragging, and occasionally while moving the mouse the "No drag target" symbol flickers, but on the whole the pointer remains the plain hand). Gentoo kde-4.7.95, with qt-4.7.4; will test .97 shortly. -- 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 289855] New: kontact crash after quitting
https://bugs.kde.org/show_bug.cgi?id=289855 Summary: kontact crash after quitting Product: kontact Version: unspecified Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: dilfri...@gentoo.org Application: kontact (4.8 rc1) KDE Platform Version: 4.7.95 (4.8 RC1 (4.7.95) (Compiled from sources) Qt Version: 4.8.0 Operating System: Linux 3.0.6-gentoo x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: Quitting kontact - Unusual behavior I noticed: kmail part was not displaying my inbox content (folder looked empty, but the e-mails were visible in akonadiconsole browser) -> wanted to restart kontct to see if this fixes the problem -- Backtrace: Application: Kontact (kontact), signal: Aborted [Current thread is 1 (Thread 0x7fbffee0b760 (LWP 1206))] Thread 3 (Thread 0x7fbfe6fba700 (LWP 1207)): #0 pthread_cond_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7fbffb60d0b4 in scavengerThread (this=0x7fbffbffa100) at wtf/FastMalloc.cpp:2495 #2 WTF::TCMalloc_PageHeap::runScavengerThread (context=0x7fbffbffa100) at wtf/FastMalloc.cpp:1618 #3 0x7fbff6c8cd5c in start_thread (arg=0x7fbfe6fba700) at pthread_create.c:301 #4 0x7fbffc34a2dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 2 (Thread 0x7fbfe67b9700 (LWP 1208)): #0 0x7fbffc341513 in *__GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7fbff5cecdf3 in g_main_context_poll (n_fds=1, fds=0x212b0a0, timeout=-1, context=0x212ad20, priority=) at gmain.c:3402 #2 g_main_context_iterate (context=0x212ad20, block=1, dispatch=1, self=) at gmain.c:3084 #3 0x7fbff5ced2c1 in g_main_context_iteration (context=0x212ad20, may_block=1) at gmain.c:3152 #4 0x7fbffd75b316 in QEventDispatcherGlib::processEvents (this=0x212ae10, flags=) at kernel/qeventdispatcher_glib.cpp:426 #5 0x7fbffd72afd2 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #6 0x7fbffd72b28d in QEventLoop::exec (this=0x7fbfe67b8e20, flags=...) at kernel/qeventloop.cpp:204 #7 0x7fbffd627d48 in QThread::exec (this=) at thread/qthread.cpp:501 #8 0x7fbffd62a3cb in QThreadPrivate::start (arg=0x212a4c0) at thread/qthread_unix.cpp:298 #9 0x7fbff6c8cd5c in start_thread (arg=0x7fbfe67b9700) at pthread_create.c:301 #10 0x7fbffc34a2dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 1 (Thread 0x7fbffee0b760 (LWP 1206)): [KCrash Handler] #6 0x7fbffc2a5925 in *__GI_raise (sig=) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #7 0x7fbffc2a6da6 in *__GI_abort () at abort.c:92 #8 0x7fbffc2e0ae3 in __libc_message (do_abort=2, fmt=0x7fbffc3be7a8 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:186 #9 0x7fbffc2e5f76 in malloc_printerr (action=3, str=0x7fbffc3bb9a4 "free(): invalid pointer", ptr=) at malloc.c:6283 #10 0x7fbff90c9960 in qDeleteAll::const_iterator> (begin=..., end=...) at /usr/include/qt4/QtCore/qalgorithms.h:322 #11 0x7fbff90c9082 in qDeleteAll > (c=) at /usr/include/qt4/QtCore/qalgorithms.h:330 #12 Akonadi::EntityTreeModel::~EntityTreeModel (this=0x244aef0, __in_chrg=) at /var/tmp/portage/kde-base/kdepimlibs-4.7.95/work/kdepimlibs-4.7.95/akonadi/entitytreemodel.cpp:79 #13 0x7fbff90c9159 in Akonadi::EntityTreeModel::~EntityTreeModel (this=0x244aef0, __in_chrg=) at /var/tmp/portage/kde-base/kdepimlibs-4.7.95/work/kdepimlibs-4.7.95/akonadi/entitytreemodel.cpp:83 #14 0x7fbffd73f204 in QObjectPrivate::deleteChildren (this=0x23feaa0) at kernel/qobject.cpp:1908 #15 0x7fbffd742af0 in QObject::~QObject (this=0x23e5010, __in_chrg=) at kernel/qobject.cpp:927 #16 0x7fbfa2f6a0ae in KMKernel::~KMKernel (this=0x23e5010, __in_chrg=) at /var/tmp/portage/kde-base/kmail-4.7.95/work/kmail-4.7.95/kmail/kmkernel.cpp:226 #17 0x7fbfa2f6a1d9 in KMKernel::~KMKernel (this=0x23e5010, __in_chrg=) at /var/tmp/portage/kde-base/kmail-4.7.95/work/kmail-4.7.95/kmail/kmkernel.cpp:236 #18 0x7fbfa32ba687 in KMailPart::~KMailPart (this=0x227f9b0, __in_chrg=, __vtt_parm=) at /var/tmp/portage/kde-base/kmail-4.7.95/work/kmail-4.7.95/kmail/kmail_part.cpp:138 #19 0x7fbfa32ba779 in KMailPart::~KMailPart (this=0x227f9b0, __in_chrg=, __vtt_parm=) at /var/tmp/portage/kde-base/kmail-4.7.95/work/kmail-4.7.95/kmail/kmail_part.cpp:140 #20 0x7fbffe600a6e in KontactInterface::Plugin::~Plugin (this=0x2254810, __vtt_parm=, __in_chrg=) at /var/tmp/portage/kde-base/kdepimlibs-4.7.95/work/kdepimlibs-4.7.95/kontactinterface/plugin.cpp:90 #21 0x7fbfa4047bb0 in KMailPlugin::~KMailPlugin (this=0x2254810, __in_chrg=, __vtt_parm=) at /var/tmp/portage/kde-base/kmail-4.7.95/work/kmail-4.7.95/kontact/plu
[Bug 289062] kmail2, 4.7.90: cannot delete e-mails in inbox (all back after server sync)
https://bugs.kde.org/show_bug.cgi?id=289062 --- Comment #2 from Andreas K. Huettel 2011-12-16 12:40:28 --- No, trash was always local. I "solved" the problem... for some reason, kmail had forgotten which folder to use as trash. Re-setting the local trash as trash folder of my dimap account makes the deleting work again. (I found this because none of the "not-really-deleted" messages ended up in the trash folder!) Not sure if or where there is a bug, resolve as you see fit. -- 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 289084] kio_imap APPEND omits message size without flags
https://bugs.kde.org/show_bug.cgi?id=289084 --- Comment #3 from Andreas K. Huettel 2011-12-16 00:02:03 --- I can confirm that my simplified patch resolves the problem described in the Gentoo bug. > https://bugs.gentoo.org/show_bug.cgi?id=382411 -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 279432] Error while uploading message (unexpected end of data) when applying filters
https://bugs.kde.org/show_bug.cgi?id=279432 --- Comment #7 from Andreas K. Huettel 2011-12-16 00:01:18 --- This is a duplicate of bug 289084, and the patch attached there seems to resolve the problem. -- 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 289084] kio_imap APPEND omits message size without flags
https://bugs.kde.org/show_bug.cgi?id=289084 --- Comment #2 from Andreas K. Huettel 2011-12-15 23:49:56 --- Created an attachment (id=66793) --> (http://bugs.kde.org/attachment.cgi?id=66793) more compact version of the patch, makes it easier to see the change -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 289084] kio_imap APPEND omits message size without flags
https://bugs.kde.org/show_bug.cgi?id=289084 Andreas K. Huettel changed: What|Removed |Added CC||dilfri...@gentoo.org --- Comment #1 from Andreas K. Huettel 2011-12-15 23:22:11 --- Please have a look at this, it may be related to https://bugs.kde.org/show_bug.cgi?id=279432 https://bugs.gentoo.org/show_bug.cgi?id=382411 -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 289062] New: kmail2, 4.7.90: cannot delete e-mails in inbox (all back after server sync)
https://bugs.kde.org/show_bug.cgi?id=289062 Summary: kmail2, 4.7.90: cannot delete e-mails in inbox (all back after server sync) Product: kmail2 Version: 4.8 Platform: Gentoo Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: commands and actions AssignedTo: kdepim-bugs@kde.org ReportedBy: dilfri...@gentoo.org Recently (since the upgrade from 4.8 beta1 to beta2?), deleting an e-mail in my (dimap) inbox only removes this e-mail temporarily. After the next sync with the server, all deleted mails are back. Re-starting Akonadi did not help, neither did logging out completely and logging back in. Not sure what other information might be useful, please ping me on irc (dilfridge on #kontact or #kde-devel) if you have specific questions. -- 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 265494] kdepim-runtime 4.4.10 fails to build (final)
https://bugs.kde.org/show_bug.cgi?id=265494 Andreas K. Huettel changed: What|Removed |Added CC||dilfri...@gentoo.org -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 288578] New: Akonaditray segfaults when selecting "Make backup"
https://bugs.kde.org/show_bug.cgi?id=288578 Summary: Akonaditray segfaults when selecting "Make backup" Product: Akonadi Version: unspecified Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: dilfri...@gentoo.org Application: akonaditray (0.1) KDE Platform Version: 4.7.90 (4.8 Beta2 (4.7.90) (Compiled from sources) Qt Version: 4.7.4 Operating System: Linux 2.6.39-gentoo-r3 x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: Select "Make backup" in akonaditray right-click menu -> bang! -- Backtrace: Application: AkonadiTray (akonaditray), signal: Segmentation fault [KCrash Handler] #6 size (this=0x7fffc6352860) at /usr/include/qt4/QtCore/qstringbuilder.h:288 #7 operator QString (this=0x7fffc6352860) at /usr/include/qt4/QtCore/qstringbuilder.h:103 #8 Tray::Global::init (this=0x7fffc6352860) at /opt/virtual/tmp-portage/portage/kde-base/kdepim-runtime-4.7.90/work/kdepim-runtime-4.7.90/tray/global.cpp:64 #9 0x00416b41 in Tray::Global::dbdriver (this=0x7fffc6352860) at /opt/virtual/tmp-portage/portage/kde-base/kdepim-runtime-4.7.90/work/kdepim-runtime-4.7.90/tray/global.cpp:78 #10 0x0040b308 in Backup::possible (this=0x1f219b0) at /opt/virtual/tmp-portage/portage/kde-base/kdepim-runtime-4.7.90/work/kdepim-runtime-4.7.90/tray/backup.cpp:52 #11 0x0040f86a in BackupAssistant::BackupAssistant (this=0x1e8b900, parent=) at /opt/virtual/tmp-portage/portage/kde-base/kdepim-runtime-4.7.90/work/kdepim-runtime-4.7.90/tray/backupassistant.cpp:36 #12 0x00409317 in Dock::slotStartBackup (this=0x1e97380) at /opt/virtual/tmp-portage/portage/kde-base/kdepim-runtime-4.7.90/work/kdepim-runtime-4.7.90/tray/dock.cpp:140 #13 0x0040adf8 in Dock::qt_metacall (this=0x1e97380, _c=QMetaObject::InvokeMetaMethod, _id=12, _a=0x7fffc6352d40) at /opt/virtual/tmp-portage/portage/kde-base/kdepim-runtime-4.7.90/work/kdepim-runtime-4.7.90_build/tray/dock.moc:112 #14 0x7f8e2cb61847 in QMetaObject::activate (sender=0x1e89b30, m=, local_signal_index=, argv=0x7fffc6352d40) at kernel/qobject.cpp:3278 #15 0x7f8e2d043a02 in QAction::triggered (this=, _t1=false) at .moc/release-shared/moc_qaction.cpp:263 #16 0x7f8e2d043bfa in QAction::activate (this=0x1e89b30, event=) at kernel/qaction.cpp:1257 #17 0x7f8e2d045142 in trigger (this=0x1e89b30, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0x1e81200) at kernel/qaction.h:218 #18 QAction::qt_metacall (this=0x1e89b30, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0x1e81200) at .moc/release-shared/moc_qaction.cpp:174 #19 0x7f8e2cb6134a in QObject::event (this=0x1e89b30, e=) at kernel/qobject.cpp:1217 #20 0x7f8e2d043cba in QAction::event (this=, e=) at kernel/qaction.cpp:1187 #21 0x7f8e2d04a064 in QApplicationPrivate::notify_helper (this=0x1cc73a0, receiver=0x1e89b30, e=0x1e4cc30) at kernel/qapplication.cpp:4481 #22 0x7f8e2d04ebda in QApplication::notify (this=, receiver=0x1e89b30, e=0x1e4cc30) at kernel/qapplication.cpp:4360 #23 0x7f8e2e8bb086 in KApplication::notify (this=0x7fffc63538d0, receiver=0x1e89b30, event=0x1e4cc30) at /opt/virtual/tmp-portage/portage/kde-base/kdelibs-4.7.90/work/kdelibs-4.7.90/kdeui/kernel/kapplication.cpp:311 #24 0x7f8e2cb4d07b in QCoreApplication::notifyInternal (this=0x7fffc63538d0, receiver=0x1e89b30, event=0x1e4cc30) at kernel/qcoreapplication.cpp:787 #25 0x7f8e2cb50834 in sendEvent (receiver=0x0, event_type=0, data=0x1c9d8d0) at kernel/qcoreapplication.h:215 #26 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x1c9d8d0) at kernel/qcoreapplication.cpp:1428 #27 0x7f8e2cb77e33 in sendPostedEvents (s=) at kernel/qcoreapplication.h:220 #28 postEventSourceDispatch (s=) at kernel/qeventdispatcher_glib.cpp:277 #29 0x7f8e28859f6e in g_main_dispatch (context=0x1cc98e0) at gmain.c:2441 #30 g_main_context_dispatch (context=0x1cc98e0) at gmain.c:3014 #31 0x7f8e2885a758 in g_main_context_iterate (context=0x1cc98e0, block=1, dispatch=1, self=) at gmain.c:3092 #32 0x7f8e2885a9ed in g_main_context_iteration (context=0x1cc98e0, may_block=1) at gmain.c:3155 #33 0x7f8e2cb77fcf in QEventDispatcherGlib::processEvents (this=0x1cc7220, flags=) at kernel/qeventdispatcher_glib.cpp:422 #34 0x7f8e2d0ef75e in QGuiEventDispatcherGlib::processEvents (this=, flags=) at kernel/qguieventdispatcher_glib.cpp:204 #35 0x7f8e2cb4c422 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #36 0x7f8e2cb4c664 in QEventLoop::exec (this=0x7fffc6353800, flags=...) at kernel/qeventloop.cpp:201 #37 0x7f8e2cb50aeb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064 #38 0x00408dfc in main (argc=3, argv=0x7fffc6353b08) at /opt/virtual/tmp-portage/po
[Bug 287923] KMail crash when dragging mail to a folder
https://bugs.kde.org/show_bug.cgi?id=287923 --- Comment #4 from Andreas K. Huettel 2011-12-08 21:54:32 --- (In reply to comment #3) > from bug 288492 (4.8beta2) > > -- Information about the crash: > - What I was doing when the application crashed: > > 3 messages marked, right-click in message list & select "move to" with another > dimap folder. Crash. This seems reproducible as long as the target folder is not yet in the "recently used folders list". On a related note, I cannot drag any messages from the message list directly into another folder; going via the context menu is the only working option. But this is likely a different 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 288492] New: KMail2 crash when moving messages to other folder
https://bugs.kde.org/show_bug.cgi?id=288492 Summary: KMail2 crash when moving messages to other folder Product: kontact Version: unspecified Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: dilfri...@gentoo.org Application: kontact (4.8 beta2) KDE Platform Version: 4.7.90 (4.8 Beta2 (4.7.90) (Compiled from sources) Qt Version: 4.7.4 Operating System: Linux 2.6.39-gentoo-r3 x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: 3 messages marked, right-click in message list & select "move to" with another dimap folder. Crash. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0x7f7465443760 (LWP 2910))] Thread 4 (Thread 0x7f744e93b700 (LWP 2911)): #0 pthread_cond_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f7461e66144 in scavengerThread (context=0x7f7462687f20) at wtf/FastMalloc.cpp:2378 #2 WTF::TCMalloc_PageHeap::runScavengerThread (context=0x7f7462687f20) at wtf/FastMalloc.cpp:1497 #3 0x7f745d759c5c in start_thread (arg=0x7f744e93b700) at pthread_create.c:301 #4 0x7f74629dbfcd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 3 (Thread 0x7f744e03a700 (LWP 2912)): #0 0x7f745d75c22e in __pthread_mutex_lock (mutex=0x2656b18) at pthread_mutex_lock.c:62 #1 0x7f745c59a468 in g_main_context_prepare (context=0x2656b10, priority=0x7f744e039d0c) at gmain.c:2764 #2 0x7f745c59b349 in g_main_context_iterate (context=0x2656b10, block=1, dispatch=1, self=) at gmain.c:3072 #3 0x7f745c59b9ed in g_main_context_iteration (context=0x2656b10, may_block=1) at gmain.c:3155 #4 0x7f7463da6026 in QEventDispatcherGlib::processEvents (this=0x2656690, flags=) at kernel/qeventdispatcher_glib.cpp:424 #5 0x7f7463d7a422 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #6 0x7f7463d7a664 in QEventLoop::exec (this=0x7f744e039e20, flags=...) at kernel/qeventloop.cpp:201 #7 0x7f7463c90744 in QThread::exec (this=) at thread/qthread.cpp:498 #8 0x7f7463c92f95 in QThreadPrivate::start (arg=0x2656120) at thread/qthread_unix.cpp:331 #9 0x7f745d759c5c in start_thread (arg=0x7f744e03a700) at pthread_create.c:301 #10 0x7f74629dbfcd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 2 (Thread 0x7f7438dc2700 (LWP 18144)): #0 0x7f74629d3353 in __poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f745c59b4bd in g_main_context_poll (context=0x69e7690, block=1, dispatch=1, self=) at gmain.c:3405 #2 g_main_context_iterate (context=0x69e7690, block=1, dispatch=1, self=) at gmain.c:3087 #3 0x7f745c59b9ed in g_main_context_iteration (context=0x69e7690, may_block=1) at gmain.c:3155 #4 0x7f7463da6026 in QEventDispatcherGlib::processEvents (this=0x656b110, flags=) at kernel/qeventdispatcher_glib.cpp:424 #5 0x7f7463d7a422 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #6 0x7f7463d7a664 in QEventLoop::exec (this=0x7f7438dc1de0, flags=...) at kernel/qeventloop.cpp:201 #7 0x7f7463c90744 in QThread::exec (this=) at thread/qthread.cpp:498 #8 0x7f7463d5bfd8 in QInotifyFileSystemWatcherEngine::run (this=0x69e5c20) at io/qfilesystemwatcher_inotify.cpp:248 #9 0x7f7463c92f95 in QThreadPrivate::start (arg=0x69e5c20) at thread/qthread_unix.cpp:331 #10 0x7f745d759c5c in start_thread (arg=0x7f7438dc2700) at pthread_create.c:301 #11 0x7f74629dbfcd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 1 (Thread 0x7f7465443760 (LWP 2910)): [KCrash Handler] #6 isEmpty (this=0x0, id=) at /usr/include/qt4/QtCore/qlist.h:95 #7 isEmpty (this=0x0, id=) at /usr/include/qt4/QtCore/qlist.h:139 #8 Akonadi::RecentCollectionAction::addRecentCollection (this=0x0, id=) at /opt/virtual/tmp-portage/portage/kde-base/kdepimlibs-4.7.90/work/kdepimlibs-4.7.90/akonadi/recentcollectionaction.cpp:97 #9 0x7f745fc2371a in Akonadi::StandardActionManager::Private::addRecentCollection (this=, id=40) at /opt/virtual/tmp-portage/portage/kde-base/kdepimlibs-4.7.90/work/kdepimlibs-4.7.90/akonadi/standardactionmanager.cpp:1105 #10 0x7f745fc2396b in Akonadi::StandardActionManager::Private::pasteTo (this=0x2c106e0, selectionModel=, action=, dropAction=Qt::MoveAction) at /opt/virtual/tmp-portage/portage/kde-base/kdepimlibs-4.7.90/work/kdepimlibs-4.7.90/akonadi/standardactionmanager.cpp:1096 #11 0x7f745fc22938 in slotMoveItemTo (this=0x2c11fa0, _c=QMetaObject::InvokeMetaMethod, _id=35, _a=0x7fffdac1ba70) at /opt/virtual/tmp-portage/portage/kde-base/kdepimlibs-4.7.90/work/kdepimlibs-4.7.90/akonadi/standardactionmanager.cpp:952 #12 Akonadi::StandardActionManager::qt_metaca
[Bug 275534] kmail2: outbox folder does not have its specific options for the first time on rightclick
https://bugs.kde.org/show_bug.cgi?id=275534 Andreas K. Huettel changed: What|Removed |Added CC||dilfri...@gentoo.org --- Comment #1 from Andreas K. Huettel 2011-11-30 19:56:19 --- Confirmed with 4.7.80 -- 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 281797] kmail2/akonadi handels maildir incorrect
https://bugs.kde.org/show_bug.cgi?id=281797 Andreas K. Huettel changed: What|Removed |Added CC||dilfri...@gentoo.org -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 279432] Error while uploading message (unexpected end of data) when applying filters
https://bugs.kde.org/show_bug.cgi?id=279432 Andreas K. Huettel changed: What|Removed |Added CC||dilfri...@gentoo.org --- Comment #4 from Andreas K. Huettel 2011-09-10 10:08:57 --- Confirmed twice on Gentoo https://bugs.gentoo.org/show_bug.cgi?id=382411 -- 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 278717] Can't read my email
https://bugs.kde.org/show_bug.cgi?id=278717 Andreas K. Huettel changed: What|Removed |Added CC||dilfri...@gentoo.org -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 271640] [regression] Commit e95e0f8e filtering of unread articles causes a bug
https://bugs.kde.org/show_bug.cgi?id=271640 Andreas K. Huettel changed: What|Removed |Added CC||dilfri...@gentoo.org --- Comment #4 from Andreas K. Huettel 2011-04-27 14:00:20 --- Same observed in Gentoo akregator-4.4.11.1. Fixed in Gentoo akregator-4.4.11.1-r1 by reverting kde commit a70973b91b6dd2b14462a114ce2c0b520e41b3af. -- 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 266239] Lost access to contacts in address book (all applications)
https://bugs.kde.org/show_bug.cgi?id=266239 Andreas K. Huettel changed: What|Removed |Added CC||dilfri...@gentoo.org --- Comment #4 from Andreas K. Huettel 2011-04-19 21:20:11 --- https://bugs.gentoo.org/show_bug.cgi?id=354491 This is the original Gentoo bug report -- 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 270171] New: [4.6.2 pre-release tarballs] kmail-4.4.10 crash when adding attachment
https://bugs.kde.org/show_bug.cgi?id=270171 Summary: [4.6.2 pre-release tarballs] kmail-4.4.10 crash when adding attachment Product: kmail2 Version: unspecified Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: dilfri...@gentoo.org Application: kmail (1.13.6) KDE Platform Version: 4.6.2 (4.6.2) (Compiled from sources) Qt Version: 4.7.1 Operating System: Linux 2.6.36-gentoo-r5 x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: klick on "attach file" button to attach a file to an email -> immediate crash -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #6 0x7f4d090aa7c6 in KFileDialogPrivate::getSaveFileName (dir=, filter=, parent=, caption=, options=, selectedFilter=0x5) at /opt/virtual/tmp-portage/portage/kde-base/kdelibs-4.6.2/work/kdelibs-4.6.2/kio/kfile/kfiledialog.cpp:749 #7 0x7f4d0f6ac312 in _dl_fixup (l=, reloc_arg=) at ../elf/dl-runtime.c:118 #8 0x7f4d0f6b22a5 in _dl_runtime_resolve () at ../sysdeps/x86_64/dl-trampoline.S:41 #9 0x7f4d0e0f7edc in KMComposeWin::slotAttachFile (this=0x33100a0) at /opt/virtual/tmp-portage/portage/kde-base/kmail-4.4.10/work/kmail-4.4.10/kmail/kmcomposewin.cpp:2289 #10 0x7f4d0e110801 in KMComposeWin::qt_metacall (this=0x33100a0, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff83e22110) at /opt/virtual/tmp-portage/portage/kde-base/kmail-4.4.10/work/kmail-4.4.10_build/kmail/kmcomposewin.moc:245 #11 0x7f4d0cb631df in QMetaObject::activate (sender=0x13e4190, m=, local_signal_index=, argv=0x0) at kernel/qobject.cpp:3272 #12 0x7f4d0d03cc72 in QAction::triggered (this=0x7f4d0c4b0e60, _t1=false) at .moc/release-shared/moc_qaction.cpp:263 #13 0x7f4d0d03e33b in QAction::activate (this=0x13e4190, event=) at kernel/qaction.cpp:1257 #14 0x7f4d0d3fa76a in QAbstractButtonPrivate::click (this=0x2b164a0) at widgets/qabstractbutton.cpp:528 #15 0x7f4d0d3faa1c in QAbstractButton::mouseReleaseEvent (this=0x29c85a0, e=0x7fff83e22bf0) at widgets/qabstractbutton.cpp:1121 #16 0x7f4d0d4c89aa in QToolButton::mouseReleaseEvent (this=0x7f4d0c4b0e60, e=0x0) at widgets/qtoolbutton.cpp:721 #17 0x7f4d0d09a01d in QWidget::event (this=0x29c85a0, event=0x7fff83e22bf0) at kernel/qwidget.cpp:8200 #18 0x7f4d0d04439c in QApplicationPrivate::notify_helper (this=0x14681c0, receiver=0x29c85a0, e=0x7fff83e22bf0) at kernel/qapplication.cpp:4445 #19 0x7f4d0d04a01b in QApplication::notify (this=0x7fff83e23860, receiver=0x29c85a0, e=0x7fff83e22bf0) at kernel/qapplication.cpp:4006 #20 0x7f4d0f268a06 in KApplication::setTopWidget (this=0x7fff83e23860, topWidget=0x7fff83e22bf0) at /opt/virtual/tmp-portage/portage/kde-base/kdelibs-4.6.2/work/kdelibs-4.6.2/kdeui/kernel/kapplication.cpp:1105 #21 0x7fff83e23860 in ?? () #22 0x7fff83e22bf0 in ?? () #23 0x7f4d0cb4b5fb in QCoreApplication::notifyInternal (this=0x29c85a0, receiver=0x132c340, event=0x7fff83e22bf0) at kernel/qcoreapplication.cpp:732 #24 0x7f4d0d048882 in sendEvent (receiver=0x29c85a0, event=0x7fff83e22bf0, alienWidget=0x29c85a0, nativeWidget=0x33100a0, buttonDown=, lastMouseReceiver=, spontaneous=true) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #25 QApplicationPrivate::sendMouseEvent (receiver=0x29c85a0, event=0x7fff83e22bf0, alienWidget=0x29c85a0, nativeWidget=0x33100a0, buttonDown=, lastMouseReceiver=, spontaneous=true) at kernel/qapplication.cpp:3105 #26 0x7f4d0d0ccf94 in QETWidget::translateMouseEvent (this=0x33100a0, event=) at kernel/qapplication_x11.cpp:4438 #27 0x7f4d0d0cbf8a in QApplication::x11ProcessEvent (this=, event=0x7fff83e23370) at kernel/qapplication_x11.cpp:3564 #28 0x7f4d0d0f6052 in x11EventSourceDispatch (s=0x146a750, callback=, user_data=) at kernel/qguieventdispatcher_glib.cpp:146 #29 0x7f4d03baf3d1 in g_main_dispatch (context=0x146a460) at gmain.c:2149 #30 g_main_context_dispatch (context=0x146a460) at gmain.c:2702 #31 0x7f4d03bb3308 in g_main_context_iterate (context=0x146a460, block=, dispatch=, self=) at gmain.c:2780 #32 0x7f4d03bb34bc in g_main_context_iteration (context=0x146a460, may_block=1) at gmain.c:2843 #33 0x7f4d0cb775e3 in QEventDispatcherGlib::processEvents (this=0x138de80, flags=) at kernel/qeventdispatcher_glib.cpp:415 #34 0x7f4d0d0f59ce in QGuiEventDispatcherGlib::processEvents (this=0x7f4d0c4b0e60, flags=) at kernel/qguieventdispatcher_glib.cpp:204 #35 0x7f4d0cb4a352 in QEventLoop::processEvents (this=, flags=) at kernel/qeventloop.cpp:149 #36 0x7f4d0cb4a734 in QEventLoop::exec (this=0x7fff83e23690, flags=) at kernel/qeventloop.cpp:201 #37 0x7f4d0cb4e7ab in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009 #38 0
[Bug 248026] kmail hangs when pressing send
https://bugs.kde.org/show_bug.cgi?id=248026 Andreas K. Huettel changed: What|Removed |Added CC||dilfri...@gentoo.org --- Comment #9 from Andreas K. Huettel 2011-02-16 20:53:05 --- Same seen here with kontact-4.4.10 on kde-4.6.0, Gentoo Linux. -- 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 245076] New: kontact crash while autocompleting cc addess
https://bugs.kde.org/show_bug.cgi?id=245076 Summary: kontact crash while autocompleting cc addess Product: kontact Version: 4.4.5 Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: m...@akhuettel.de Application: kontact (4.4.5) KDE Platform Version: 4.4.92 (KDE 4.4.92 (KDE 4.5 RC2)) (Compiled from sources) Qt Version: 4.6.3 Operating System: Linux 2.6.32-gentoo-r7 x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: typing in an additional e-mail address as cc for an e-mail. the suggestions drop-down window was displayed for a moment, then kontact crashed. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Traceback (most recent call last): File "/usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.2200.5-gdb.py", line 9, in from gobject import register File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in import gdb.backtrace ImportError: No module named backtrace The current source language is "auto; currently asm". [KCrash Handler] #6 0x7f31a503f1f1 in QListData::size (this=0x31f4f80) at /usr/include/qt4/QtCore/qlist.h:90 #7 QList::count (this=0x31f4f80) at /usr/include/qt4/QtCore/qlist.h:261 #8 operator<< (this=0x31f4f80) at /usr/include/qt4/QtCore/qdebug.h:166 #9 KPIM::AddresseeLineEdit::akonadiHandlePending (this=0x31f4f80) at /var/tmp/portage/kde-base/libkdepim-4.4.5/work/libkdepim-4.4.5/libkdepim/addresseelineedit.cpp:1114 #10 0x7f31a503fabd in KPIM::AddresseeLineEdit::slotAkonadiCollectionsReceived (this=, collections=...) at /var/tmp/portage/kde-base/libkdepim-4.4.5/work/libkdepim-4.4.5/libkdepim/addresseelineedit.cpp:1036 #11 0x7f31a5040ce9 in KPIM::AddresseeLineEdit::qt_metacall (this=0x31f4f80, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fffa8fc4b00) at /var/tmp/portage/kde-base/libkdepim-4.4.5/work/libkdepim-4.4.5_build/libkdepim/addresseelineedit.moc:109 #12 0x7f318ac183d8 in KMLineEdit::qt_metacall (this=0x32d4e00, _c=QMetaObject::InvokeMetaMethod, _id=55139560, _a=0x3574dd2) at /var/tmp/portage/kde-base/kmail-4.4.5/work/kmail-4.4.5_build/kmail/kmlineeditspell.moc:74 #13 0x7f318ac86118 in RecipientLineEdit::qt_metacall (this=0x32d4e00, _c=QMetaObject::InvokeMetaMethod, _id=55139560, _a=0x3574dd2) at /var/tmp/portage/kde-base/kmail-4.4.5/work/kmail-4.4.5_build/kmail/recipientseditor.moc:135 #14 0x7f31a2ee2f36 in QMetaObject::activate (sender=0x28f0b80, m=, local_signal_index=, argv=0x3574dd2) at kernel/qobject.cpp:3287 #15 0x7f31a4a2cc72 in Akonadi::CollectionFetchJob::collectionsReceived (this=0x32d4e00, _t1=) at /var/tmp/portage/kde-base/kdepimlibs-4.4.92/work/kdepimlibs-4.4.92_build/akonadi/collectionfetchjob.moc:92 #16 0x7f31a4a2cf9c in Akonadi::CollectionFetchJobPrivate::timeout (this=, _c=, _id=2, _a=0x7fffa8fc4c50) at /var/tmp/portage/kde-base/kdepimlibs-4.4.92/work/kdepimlibs-4.4.92/akonadi/collectionfetchjob.cpp:64 #17 Akonadi::CollectionFetchJob::qt_metacall (this=, _c=, _id=2, _a=0x7fffa8fc4c50) at /var/tmp/portage/kde-base/kdepimlibs-4.4.92/work/kdepimlibs-4.4.92_build/akonadi/collectionfetchjob.moc:80 #18 0x7f31a2ee2f36 in QMetaObject::activate (sender=0x28f0b80, m=, local_signal_index=, argv=0x3574dd2) at kernel/qobject.cpp:3287 #19 0x7f31a3fa2052 in KJob::result (this=0x32d4e00, _t1=0x28f0b80) at /var/tmp/portage/kde-base/kdelibs-4.4.92/work/kdelibs-4.4.92_build/kdecore/kjob.moc:194 #20 0x7f31a3fa22f0 in KJob::emitResult (this=0x28f0b80) at /var/tmp/portage/kde-base/kdelibs-4.4.92/work/kdelibs-4.4.92/kdecore/jobs/kjob.cpp:312 #21 0x7f31a4a99c09 in Akonadi::JobPrivate::delayedEmitResult (this=0x28f0b80, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fffa8fc4d80) at /var/tmp/portage/kde-base/kdepimlibs-4.4.92/work/kdepimlibs-4.4.92/akonadi/job.cpp:143 #22 Akonadi::Job::qt_metacall (this=0x28f0b80, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fffa8fc4d80) at /var/tmp/portage/kde-base/kdepimlibs-4.4.92/work/kdepimlibs-4.4.92_build/akonadi/job.moc:91 #23 0x7f31a4a2cea5 in Akonadi::CollectionFetchJob::qt_metacall (this=0x32d4e00, _c=QMetaObject::InvokeMetaMethod, _id=55139560, _a=0x3574dd2) at /var/tmp/portage/kde-base/kdepimlibs-4.4.92/work/kdepimlibs-4.4.92_build/akonadi/collectionfetchjob.moc:73 #24 0x7f31a2ee2f36 in QMetaObject::activate (sender=0x3c85060, m=, local_signal_index=, argv=0x3574dd2) at kernel/qobject.cpp:3287 #25 0x7f31a2eea38f in QSingleShotTimer::timerEvent (this=0x3c85060) at kernel/qtimer.cpp:308 #26 0x7f31a2edf7c3 in QObject::event (this=0x3c85060, e=0x0) at kernel/qobject.cpp:1204 #27 0x7f31a33a22ec in QApplicationPrivate::notify_helper (this=0x1c550d0, receiver=0x3c85060, e=0x7fffa8fc54e0) at kernel/qapplication.cpp:
[Bug 201770] irregular and sometimes unpredictable behaviour in message list when selecting and deleting messages
https://bugs.kde.org/show_bug.cgi?id=201770 --- Comment #3 from Andreas K. Huettel 2010-04-30 22:45:30 --- See for a similar bug report http://bugs.gentoo.org/show_bug.cgi?id=294618 -- 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 234801] New: Kontact crash when selecting text in e-mail with mouse
https://bugs.kde.org/show_bug.cgi?id=234801 Summary: Kontact crash when selecting text in e-mail with mouse Product: kontact Version: 4.4.2 Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: m...@akhuettel.de Application: kontact (4.4.2) KDE Platform Version: 4.4.2 (KDE 4.4.2) (Compiled from sources) Qt Version: 4.6.2 Operating System: Linux 2.6.31-gentoo-r6 x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: Kontact crashed when selecting text with the mouse in a received e-mail -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Traceback (most recent call last): File "/usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.2200.4-gdb.py", line 9, in from gobject import register File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in import gdb.backtrace ImportError: No module named backtrace The current source language is "auto; currently c". [KCrash Handler] #5 0x in ?? () #6 0x7f5de9701b26 in KOrg::IncidenceMonthItem::realStartDate (this=0x35ac670) at /var/tmp/portage/kde-base/korganizer-4.4.2/work/korganizer-4.4.2/korganizer/views/monthview/monthitem.cpp:343 #7 0x7f5de96fee45 in KOrg::MonthView::reloadIncidences (this=0x31f4700) at /var/tmp/portage/kde-base/korganizer-4.4.2/work/korganizer-4.4.2/korganizer/views/monthview/monthview.cpp:330 #8 0x7f5de963 in KOrg::MonthView::setStartDate (this=0x31f4700, start=) at /var/tmp/portage/kde-base/korganizer-4.4.2/work/korganizer-4.4.2/korganizer/views/monthview/monthview.cpp:296 #9 0x7f5de970004e in KOrg::MonthView::showDates (this=0x31f4700, start=..., end=) at /var/tmp/portage/kde-base/korganizer-4.4.2/work/korganizer-4.4.2/korganizer/views/monthview/monthview.cpp:283 #10 0x7f5de9745116 in KOViewManager::updateView (this=0x2ec3a70, start=..., end=...) at /var/tmp/portage/kde-base/korganizer-4.4.2/work/korganizer-4.4.2/korganizer/koviewmanager.cpp:237 #11 0x7f5de97330ea in CalendarView::updateView (this=0x2f02860, start=..., end=..., updateTodos=) at /var/tmp/portage/kde-base/korganizer-4.4.2/work/korganizer-4.4.2/korganizer/calendarview.cpp:802 #12 0x7f5de9733f10 in CalendarView::updateView (this=0x2f02860) at /var/tmp/portage/kde-base/korganizer-4.4.2/work/korganizer-4.4.2/korganizer/calendarview.cpp:813 #13 0x7f5de9743197 in CalendarView::qt_metacall (this=0x2f02860, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fffd8c1cb70) at /var/tmp/portage/kde-base/korganizer-4.4.2/work/korganizer-4.4.2_build/korganizer/calendarview.moc:589 #14 0x7f5e042c0167 in QMetaObject::activate (sender=0x2eb0450, m=, local_signal_index=, argv=0x11) at kernel/qobject.cpp:3285 #15 0x7f5e07bcbc38 in KCal::Calendar::qt_metacall (this=0x2eb0450, _c=QMetaObject::InvokeMetaMethod, _id=, _a=) at /var/tmp/portage/kde-base/kdepimlibs-4.4.2/work/kdepimlibs-4.4.2_build/kcal/calendar.moc:82 #16 0x7f5e07c2aa95 in KCal::CalendarResources::qt_metacall (this=0x7fffd8c1c3f0, _c=55482752, _id=56280577, _a=0x11) at /var/tmp/portage/kde-base/kdepimlibs-4.4.2/work/kdepimlibs-4.4.2_build/kcal/calendarresources.moc:85 #17 0x7f5e042c0167 in QMetaObject::activate (sender=0x2fd7740, m=, local_signal_index=, argv=0x11) at kernel/qobject.cpp:3285 #18 0x7f5e07c1d16f in KCal::ResourceCalendar::resourceChanged (this=0x7fffd8c1c3f0, _t1=0x2fd7740) at /var/tmp/portage/kde-base/kdepimlibs-4.4.2/work/kdepimlibs-4.4.2_build/kcal/resourcecalendar.moc:123 #19 0x7f5de813b44e in KCal::ResourceRemote::doLoad (this=0x2fd7740, syncCache=) at /var/tmp/portage/kde-base/kdepim-kresources-4.4.2/work/kdepim-kresources-4.4.2/kresources/remote/resourceremote.cpp:193 #20 0x7f5e07c27a8f in KCal::ResourceCached::load (this=0x2fd7740, action=KCal::ResourceCached::SyncCache) at /var/tmp/portage/kde-base/kdepimlibs-4.4.2/work/kdepimlibs-4.4.2/kcal/resourcecached.cpp:409 #21 0x7f5e07c27e94 in KCal::ResourceCached::slotReload (this=0x2fd7740) at /var/tmp/portage/kde-base/kdepimlibs-4.4.2/work/kdepimlibs-4.4.2/kcal/resourcecached.cpp:808 #22 0x7f5e07c27f1e in KCal::ResourceCached::qt_metacall (this=0x2fd7740, _c=QMetaObject::InvokeMetaMethod, _id=58898000, _a=) at /var/tmp/portage/kde-base/kdepimlibs-4.4.2/work/kdepimlibs-4.4.2_build/kcal/resourcecached.moc:77 #23 0x7f5de813b075 in KCal::ResourceRemote::qt_metacall (this=0x7fffd8c1c3f0, _c=55482752, _id=56280577, _a=0x11) at /var/tmp/portage/kde-base/kdepim-kresources-4.4.2/work/kdepim-kresources-4.4.2_build/kresources/remote/resourceremote.moc:71 #24 0x7f5e042c0167 in QMetaObject::activate (sender=0x2fef410, m=, local_signal_index=, argv=0x11) at kernel/qobject.cpp:3285 #25 0x7f5e042bcc03 in QObject::event (this=0x2fef410, e=0x34e9980) at kernel/qobject.cpp:1204
[Bug 223274] New: Kontact crash when losing network connection
https://bugs.kde.org/show_bug.cgi?id=223274 Summary: Kontact crash when losing network connection Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: m...@akhuettel.de Application that crashed: kontact Version of the application: 4.3.4 KDE Version: 4.3.4 (KDE 4.3.4) Qt Version: 4.5.3 Operating System: Linux 2.6.31-gentoo-r6 x86_64 What I was doing when the application crashed: Network cable was accidentally pulled. Popup "Connection to DIMAP server unexpectedly lost". Confirmed with ok -> crash This is a duplicate of Bug 191589 -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault The current source language is "auto; currently c". [Current thread is 1 (Thread 0x7fdf00eed740 (LWP 10794))] Thread 3 (Thread 0x7fdee555c910 (LWP 14718)): #0 0x7fdefa05f896 in *__GI___poll (fds=0x7fdee5559da0, nfds=1, timeout=5000) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7fdef37c57c0 in send_dg (statp=0x7fdee555cdc8, buf=0x7fdee5559e30 "\274\232\001", buflen=35, buf2=0x0, buflen2=0, ans=0x7fdee555a940 "\b\240\201\200", anssiz=1024, ansp=0x7fdee555b1a0, ansp2=0x0, nansp2=0x0, resplen2=0x0) at res_send.c:1046 #2 __libc_res_nsend (statp=0x7fdee555cdc8, buf=0x7fdee5559e30 "\274\232\001", buflen=35, buf2=0x0, buflen2=0, ans=0x7fdee555a940 "\b\240\201\200", anssiz=1024, ansp=0x7fdee555b1a0, ansp2=0x0, nansp2=0x0, resplen2=0x0) at res_send.c:557 #3 0x7fdef37c3a7d in *__GI___libc_res_nquery (statp=0x7fdee555cdc8, name=0x7fdee0075898 "planet.gentoo.org", class=1, type=1, answer=0x7fdee555a940 "\b\240\201\200", anslen=1024, answerp=0x7fdee555b1a0, answerp2=0x0, nanswerp2=0x0, resplen2=0x0) at res_query.c:225 #4 0x7fdef37c40dd in __libc_res_nquerydomain (statp=0x7fdee555cdc8, name=0x7fdee0075898 "planet.gentoo.org", domain=0x10 , class=1, type=1, answer=0x7fdee555a940 "\b\240\201\200", anslen=1024, answerp=0x7fdee555b1a0, answerp2=0x0, nanswerp2=0x0, resplen2=0x0) at res_query.c:576 #5 0x7fdef37c42c3 in *__GI___libc_res_nsearch (statp=0x7fdee555cdc8, name=0x7fdee0075898 "planet.gentoo.org", class=1, type=1, answer=0x7fdee555a940 "\b\240\201\200", anslen=1024, answerp=0x7fdee555b1a0, answerp2=0x0, nanswerp2=0x0, resplen2=0x0) at res_query.c:377 #6 0x7fdee4b2cff4 in *__GI__nss_dns_gethostbyname3_r (name=0x7fdee0075898 "planet.gentoo.org", af=2, result=0x7fdee555b6c0, buffer=0x7fdee555b2d0 "\204\307fW", buflen=512, errnop=0x7fdee555c8a8, h_errnop=0x7fdee555b6f0, ttlp=0x0, canonp=0x0) at nss_dns/dns-host.c:197 #7 0x7fdee4b2d2b4 in _nss_dns_gethostbyname2_r (name=0x7fdee5559da0 "\005", af=1, result=0x1388, buffer=0x , buflen=0, errnop=0x0, h_errnop=0x7fdee555b6f0) at nss_dns/dns-host.c:251 #8 0x7fdefa07f9a9 in __gethostbyname2_r (name=0x7fdee0075898 "planet.gentoo.org", af=2, resbuf=0x7fdee555b6c0, buffer=0x7fdee555b2d0 "\204\307fW", buflen=512, result=0x7fdee555b6e0, h_errnop=0x7fdee555b6f0) at ../nss/getXXbyYY_r.c:253 #9 0x7fdefa052c1a in gaih_inet (name=0x7fdee0075898 "planet.gentoo.org", service=, req=0x7fdee555b840, pai=0x7fdee555b8b0, naddrs=0x7fdee555b8b8) at ../sysdeps/posix/getaddrinfo.c:531 #10 0x7fdefa0552f1 in *__GI_getaddrinfo (name=0x7fdee0075898 "planet.gentoo.org", service=0x0, hints=0x7fdee555b840, pai=0x7fdee555be18) at ../sysdeps/posix/getaddrinfo.c:2158 #11 0x7fdefcff0d98 in QHostInfoAgent::fromName (hostName=...) at kernel/qhostinfo_unix.cpp:205 #12 0x7fdefcfe8f9f in QHostInfo::fromName (name=) at kernel/qhostinfo.cpp:230 #13 0x7fdefd42889b in QtConcurrent::StoredFunctorCall1::runFunctor (this=0x1c9fe10) at /usr/include/qt4/QtCore/qtconcurrentstoredfunctioncall.h:274 #14 0x7fdefd429423 in QtConcurrent::RunFunctionTask::run (this=0x1c9fe10) at /usr/include/qt4/QtCore/qtconcurrentrunbase.h:103 #15 0x7fdefad0588c in QThreadPoolThread::run (this=0x1243b60) at concurrent/qthreadpool.cpp:106 #16 0x7fdefad0d804 in QThreadPrivate::start (arg=0x1243b60) at thread/qthread_unix.cpp:188 #17 0x7fdefaa9d2a7 in start_thread (arg=) at pthread_create.c:297 #18 0x7fdefa0686ad in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #19 0x in ?? () Thread 2 (Thread 0x7fdede522910 (LWP 14719)): #0 0x7fdefa05f896 in *__GI___poll (fds=0x7fdede51fda0, nfds=1, timeout=5000) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7fdef37c57c0 in send_dg (statp=0x7fdede522dc8, buf=0x7fdede51fe30 "\236\036\001", buflen=29, buf2=0x0, buflen2=0, ans=0x7fdede520940 "\247 \201\200", anssiz=1024, ansp=0x7fdede5211a0, ansp2=0x0, nansp2=0x0, resplen2=0x0) at res_send.c:1046 #2 __libc_res_nsend (statp=0x7fdede522dc8, buf=0x7fdede51fe30 "\236\036\001", buflen=29, buf2=0x0, buflen2=0, ans=0x7fdede520940 "\247
[Bug 222251] New: Kontact crashed when clicking on e-mail
https://bugs.kde.org/show_bug.cgi?id=51 Summary: Kontact crashed when clicking on e-mail Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: m...@akhuettel.de Application that crashed: kontact Version of the application: 4.3.4 KDE Version: 4.3.4 (KDE 4.3.4) Qt Version: 4.5.3 Operating System: Linux 2.6.31-gentoo-r6 x86_64 What I was doing when the application crashed: Kontact crashed when clicking on e-mail in dimap folder -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault The current source language is "auto; currently c". [KCrash Handler] #5 0x in ?? () #6 0x7f70ad1dd941 in KMReaderWin::parseMsg (this=0x10d1820, aMsg=0x206acd0) at /var/tmp/portage/kde-base/kmail-4.3.4/work/kmail-4.3.4/kmail/kmreaderwin.cpp:1691 #7 0x7f70ad1cb92a in KMReaderWin::displayMessage (this=0x10d1820) at /var/tmp/portage/kde-base/kmail-4.3.4/work/kmail-4.3.4/kmail/kmreaderwin.cpp:1608 #8 0x7f70ad1cbb15 in KMReaderWin::updateReaderWin (this=0x10d1820) at /var/tmp/portage/kde-base/kmail-4.3.4/work/kmail-4.3.4/kmail/kmreaderwin.cpp:1548 #9 0x7f70ad1d7c8d in KMReaderWin::qt_metacall (this=0x10d1820, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fffa50ba8b0) at /var/tmp/portage/kde-base/kmail-4.3.4/work/kmail-4.3.4_build/kmail/kmreaderwin.moc:168 #10 0x7f70be4a6826 in QMetaObject::activate (sender=0x10d18c8, from_signal_index=, to_signal_index=4, argv=0x1) at kernel/qobject.cpp:3101 #11 0x7f70be4a3153 in QObject::event (this=0x10d18c8, e=0xa9a324) at kernel/qobject.cpp:1066 #12 0x7f70bf2568fd in QApplicationPrivate::notify_helper (this=0xaca100, receiver=0x10d18c8, e=0x7fffa50baf60) at kernel/qapplication.cpp:4065 #13 0x7f70bf25e1ba in QApplication::notify (this=0x7fffa50bb3b0, receiver=0x10d18c8, e=0x7fffa50baf60) at kernel/qapplication.cpp:4030 #14 0x7f70bffeefdb in KApplication::notify (this=0x7fffa50bb3b0, receiver=0x10d18c8, event=0x7fffa50baf60) at /var/tmp/portage/kde-base/kdelibs-4.3.4/work/kdelibs-4.3.4/kdeui/kernel/kapplication.cpp:302 #15 0x7f70be494a5b in QCoreApplication::notifyInternal (this=0x7fffa50bb3b0, receiver=0x10d18c8, event=0x7fffa50baf60) at kernel/qcoreapplication.cpp:606 #16 0x7f70be4bc656 in QCoreApplication::sendEvent (this=0xacd9a0) at kernel/qcoreapplication.h:213 #17 QTimerInfoList::activateTimers (this=0xacd9a0) at kernel/qeventdispatcher_unix.cpp:580 #18 0x7f70be4b94fd in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:165 #19 0x7f70b98624a9 in g_main_dispatch (context=0xacc920) at gmain.c:1824 #20 IA__g_main_context_dispatch (context=0xacc920) at gmain.c:2377 #21 0x7f70b9865ae8 in g_main_context_iterate (context=0xacc920, block=1, dispatch=1, self=) at gmain.c:2455 #22 0x7f70b9865c9c in IA__g_main_context_iteration (context=0xacc920, may_block=1) at gmain.c:2518 #23 0x7f70be4b945f in QEventDispatcherGlib::processEvents (this=0xac0a80, flags=) at kernel/qeventdispatcher_glib.cpp:327 #24 0x7f70bf2db89f in QGuiEventDispatcherGlib::processEvents (this=0x206acd0, flags=) at kernel/qguieventdispatcher_glib.cpp:202 #25 0x7f70be493442 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #26 0x7f70be4935dc in QEventLoop::exec (this=0x7fffa50bb210, flags=...) at kernel/qeventloop.cpp:197 #27 0x7f70be49561c in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #28 0x00404b49 in main (argc=1, argv=0x7fffa50bb988) at /var/tmp/portage/kde-base/kontact-4.3.4/work/kontact-4.3.4/kontact/src/main.cpp:218 This bug may be a duplicate of or related to bug 221549 Reported using DrKonqi -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 221549] Kontact crashed when clicking on an email in dimap folder
https://bugs.kde.org/show_bug.cgi?id=221549 --- Comment #2 from Andreas K. Huettel 2010-01-06 20:59:35 --- Q: Are you using the preview window when you reported your bug? yes Q: Did your kmail crash if you had the preview window enabled. yes Q: Did your kmail continue to work okay if the preview window was off. no way to check, the crash was not reproducible -- 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 221549] New: Kontact crashed when clicking on an email in dimap folder
https://bugs.kde.org/show_bug.cgi?id=221549 Summary: Kontact crashed when clicking on an email in dimap folder Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: m...@akhuettel.de Application that crashed: kontact Version of the application: 4.3.4 KDE Version: 4.3.4 (KDE 4.3.4) Qt Version: 4.5.3 Operating System: Linux 2.6.30-gentoo-r5 x86_64 What I was doing when the application crashed: Kontact crashed when clicking on an email in a disconnected imap folder -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault The current source language is "auto; currently c". [KCrash Handler] #5 0x7f90358019b0 in vtable for DwString () from /usr/lib64/libmimelib.so.4 #6 0x7f903762f941 in KMReaderWin::parseMsg (this=0x2366360, aMsg=0x4243890) at /var/tmp/portage/kde-base/kmail-4.3.4/work/kmail-4.3.4/kmail/kmreaderwin.cpp:1691 #7 0x7f903761d92a in KMReaderWin::displayMessage (this=0x2366360) at /var/tmp/portage/kde-base/kmail-4.3.4/work/kmail-4.3.4/kmail/kmreaderwin.cpp:1608 #8 0x7f903761db15 in KMReaderWin::updateReaderWin (this=0x2366360) at /var/tmp/portage/kde-base/kmail-4.3.4/work/kmail-4.3.4/kmail/kmreaderwin.cpp:1548 #9 0x7f9037629c8d in KMReaderWin::qt_metacall (this=0x2366360, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7a18d3b0) at /var/tmp/portage/kde-base/kmail-4.3.4/work/kmail-4.3.4_build/kmail/kmreaderwin.moc:168 #10 0x7f9048b75826 in QMetaObject::activate (sender=0x2366408, from_signal_index=, to_signal_index=4, argv=0x1) at kernel/qobject.cpp:3101 #11 0x7f9048b72153 in QObject::event (this=0x2366408, e=0x1b7a354) at kernel/qobject.cpp:1066 #12 0x7f90499258fd in QApplicationPrivate::notify_helper (this=0x1ba2220, receiver=0x2366408, e=0x7a18da60) at kernel/qapplication.cpp:4065 #13 0x7f904992d1ba in QApplication::notify (this=0x7a18deb0, receiver=0x2366408, e=0x7a18da60) at kernel/qapplication.cpp:4030 #14 0x7f904a6bdfdb in KApplication::notify (this=0x7a18deb0, receiver=0x2366408, event=0x7a18da60) at /var/tmp/portage/kde-base/kdelibs-4.3.4/work/kdelibs-4.3.4/kdeui/kernel/kapplication.cpp:302 #15 0x7f9048b63a5b in QCoreApplication::notifyInternal (this=0x7a18deb0, receiver=0x2366408, event=0x7a18da60) at kernel/qcoreapplication.cpp:606 #16 0x7f9048b8b656 in QCoreApplication::sendEvent (this=0x1ba5b40) at kernel/qcoreapplication.h:213 #17 QTimerInfoList::activateTimers (this=0x1ba5b40) at kernel/qeventdispatcher_unix.cpp:580 #18 0x7f9048b884fd in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:165 #19 0x7f9043f204a9 in g_main_dispatch (context=0x1ba5920) at gmain.c:1824 #20 IA__g_main_context_dispatch (context=0x1ba5920) at gmain.c:2377 #21 0x7f9043f23ae8 in g_main_context_iterate (context=0x1ba5920, block=1, dispatch=1, self=) at gmain.c:2455 #22 0x7f9043f23c9c in IA__g_main_context_iteration (context=0x1ba5920, may_block=1) at gmain.c:2518 #23 0x7f9048b8845f in QEventDispatcherGlib::processEvents (this=0x1b9e3b0, flags=) at kernel/qeventdispatcher_glib.cpp:327 #24 0x7f90499aa89f in QGuiEventDispatcherGlib::processEvents (this=0x4243890, flags=) at kernel/qguieventdispatcher_glib.cpp:202 #25 0x7f9048b62442 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #26 0x7f9048b625dc in QEventLoop::exec (this=0x7a18dd10, flags=...) at kernel/qeventloop.cpp:197 #27 0x7f9048b6461c in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #28 0x00404b49 in main (argc=1, argv=0x7a18e488) at /var/tmp/portage/kde-base/kontact-4.3.4/work/kontact-4.3.4/kontact/src/main.cpp:218 Reported using DrKonqi -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 220981] New: Crash when adding calendar entry
https://bugs.kde.org/show_bug.cgi?id=220981 Summary: Crash when adding calendar entry Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: m...@akhuettel.de Application that crashed: kontact Version of the application: 4.3.4 KDE Version: 4.3.4 (KDE 4.3.4) Qt Version: 4.5.3 Operating System: Linux 2.6.30-gentoo-r5 x86_64 What I was doing when the application crashed: Kontact crashed when adding a calendar entry. The calendar is in a "remote file", at a sftp:// url. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault The current source language is "auto; currently c". [KCrash Handler] #5 QBasicAtomicInt::ref (this=0x2474b80) at /usr/include/qt4/QtCore/qatomic_x86_64.h:121 #6 QString (this=0x2474b80) at /usr/include/qt4/QtCore/qstring.h:712 #7 KCal::IncidenceBase::uid (this=0x2474b80) at /var/tmp/portage/kde-base/kdepimlibs-4.3.4/work/kdepimlibs-4.3.4/kcal/incidencebase.cpp:185 #8 0x7ff89330856c in KOEventViewer::changeIncidenceDisplay (this=0x2355fc0, incidence=0x24d1890, action=0) at /var/tmp/portage/kde-base/korganizer-4.3.4/work/korganizer-4.3.4/korganizer/koeventviewer.cpp:136 #9 0x7ff893d05967 in CalendarView::incidenceAdded (this=0x24c4870, incidence=0x24d1890) at /var/tmp/portage/kde-base/korganizer-4.3.4/work/korganizer-4.3.4/korganizer/calendarview.cpp:659 #10 0x7ff893d0aa90 in CalendarView::qt_metacall (this=0x24c4870, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff98c5e560) at /var/tmp/portage/kde-base/korganizer-4.3.4/work/korganizer-4.3.4_build/korganizer/calendarview.moc:484 #11 0x7ff8b090d826 in QMetaObject::activate (sender=0x29ae860, from_signal_index=, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3101 #12 0x7ff8937832df in KOrg::IncidenceChangerBase::incidenceAdded (this=0x7fff98c5e250, _t1=0x24d1890) at /var/tmp/portage/kde-base/korganizer-4.3.4/work/korganizer-4.3.4_build/korganizer/interfaces/korganizer/incidencechangerbase.moc:94 #13 0x7ff893d8ce0d in IncidenceChanger::addIncidence (this=0x29ae860, incidence=0x24d1890, parent=0x30cc350) at /var/tmp/portage/kde-base/korganizer-4.3.4/work/korganizer-4.3.4/korganizer/incidencechanger.cpp:334 #14 0x7ff893d174b7 in KOEventEditor::processInput (this=0x30cc350) at /var/tmp/portage/kde-base/korganizer-4.3.4/work/korganizer-4.3.4/korganizer/koeventeditor.cpp:346 #15 0x7ff893d1440f in KOIncidenceEditor::slotButtonClicked (this=0x30cc350, button=) at /var/tmp/portage/kde-base/korganizer-4.3.4/work/korganizer-4.3.4/korganizer/koincidenceeditor.cpp:102 #16 0x7ff8b23cc6a5 in KDialog::qt_metacall (this=0x30cc350, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff98c5eb00) at /var/tmp/portage/kde-base/kdelibs-4.3.4/work/kdelibs-4.3.4_build/kdeui/kdialog.moc:184 #17 0x7ff8b24814d6 in KPageDialog::qt_metacall (this=0x7fff98c5e250, _c=38226816, _id=0, _a=0x0) at /var/tmp/portage/kde-base/kdelibs-4.3.4/work/kdelibs-4.3.4_build/kdeui/kpagedialog.moc:64 #18 0x7ff893d14bb5 in KOIncidenceEditor::qt_metacall (this=0x7fff98c5e250, _c=38226816, _id=0, _a=0x0) at /var/tmp/portage/kde-base/korganizer-4.3.4/work/korganizer-4.3.4_build/korganizer/koincidenceeditor.moc:107 #19 0x7ff893d17996 in KOEventEditor::qt_metacall (this=0x7fff98c5e250, _c=38226816, _id=0, _a=0x0) at /var/tmp/portage/kde-base/korganizer-4.3.4/work/korganizer-4.3.4_build/korganizer/koeventeditor.moc:71 #20 0x7ff8b090d826 in QMetaObject::activate (sender=0x2ba6088, from_signal_index=, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3101 #21 0x7ff8b091190e in QSignalMapper::mapped (this=0x7fff98c5e250, _t1=4) at .moc/release-shared/moc_qsignalmapper.cpp:95 #22 0x7ff8b09119b0 in QSignalMapper::map (this=0x2ba6088, sender=0x25fae50) at kernel/qsignalmapper.cpp:266 #23 0x7ff8b0912b90 in QSignalMapper::qt_metacall (this=0x2ba6088, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff98c5ec90) at .moc/release-shared/moc_qsignalmapper.cpp:81 #24 0x7ff8b090d826 in QMetaObject::activate (sender=0x25fae50, from_signal_index=, to_signal_index=30, argv=0x0) at kernel/qobject.cpp:3101 #25 0x7ff8b1c44007 in QAbstractButton::clicked (this=0x7fff98c5e250, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:200 #26 0x7ff8b19dfc8b in QAbstractButtonPrivate::emitClicked (this=0x2d07b80) at widgets/qabstractbutton.cpp:543 #27 0x7ff8b19e0afb in QAbstractButtonPrivate::click (this=0x2d07b80) at widgets/qabstractbutton.cpp:536 #28 0x7ff8b19e0d35 in QAbstractButton::mouseReleaseEvent (this=0x25fae50, e=0x7fff98c5f5e0) at widgets/qabstractbutton.cpp:1115 #29 0x7ff8b170a4a8 in QWidget::event (this=0x25fae50, event=0x7fff98c5f5e0) at kernel/qwidget.cpp:7554 #30 0x7ff8b16bd8fd in QApplicationPrivate::notify_hel
[Bug 218100] Kontact crashed after losing connection to IMAP server
https://bugs.kde.org/show_bug.cgi?id=218100 Andreas K. Huettel changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||DUPLICATE --- Comment #1 from Andreas K. Huettel 2009-12-10 12:11:53 --- *** This bug has been marked as a duplicate of bug 191589 *** -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 218100] New: Kontact crashed after losing connection to IMAP server
https://bugs.kde.org/show_bug.cgi?id=218100
Summary: Kontact crashed after losing connection to IMAP server
Product: kontact
Version: unspecified
Platform: Unlisted Binaries
OS/Version: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: m...@akhuettel.de
Application that crashed: kontact
Version of the application: 4.3.4
KDE Version: 4.3.4 (KDE 4.3.4)
Qt Version: 4.5.3
Operating System: Linux 2.6.30-gentoo-r5 x86_64
What I was doing when the application crashed:
Kontact crashed after losing connection to IMAP server
Duplicate of bug 191589
Have not seen this for a long time, but it seems it is not fixed in Gentoo
after all.
-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#5 KIO::Slave::deref (this=0x23267e0) at
/var/tmp/portage/kde-base/kdelibs-4.3.4/work/kdelibs-4.3.4/kio/kio/slave.cpp:242
#6 0x7f9e35b47dea in KIO::Slave::gotInput (this=0x23267e0) at
/var/tmp/portage/kde-base/kdelibs-4.3.4/work/kdelibs-4.3.4/kio/kio/slave.cpp:335
#7 0x7f9e35b4a0e8 in KIO::Slave::qt_metacall (this=0x23267e0,
_c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7c7db7a0)
at
/var/tmp/portage/kde-base/kdelibs-4.3.4/work/kdelibs-4.3.4_build/kio/slave.moc:76
#8 0x7f9e33529826 in QMetaObject::activate (sender=0x226c990,
from_signal_index=, to_signal_index=4, argv=0x301a340) at
kernel/qobject.cpp:3101
#9 0x7f9e35a64cdf in KIO::ConnectionPrivate::dequeue (this=0x2333e80) at
/var/tmp/portage/kde-base/kdelibs-4.3.4/work/kdelibs-4.3.4/kio/kio/connection.cpp:82
#10 0x7f9e35a6513a in KIO::Connection::qt_metacall (this=0x226c990,
_c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x2bdd6e0)
at
/var/tmp/portage/kde-base/kdelibs-4.3.4/work/kdelibs-4.3.4_build/kio/connection.moc:73
#11 0x7f9e33526451 in QObject::event (this=0x226c990, e=0x26d5fd0) at
kernel/qobject.cpp:1099
#12 0x7f9e342d98fd in QApplicationPrivate::notify_helper (this=0x1781950,
receiver=0x226c990, e=0x26d5fd0) at kernel/qapplication.cpp:4065
#13 0x7f9e342e11ba in QApplication::notify (this=0x7c7dc300,
receiver=0x226c990, e=0x26d5fd0) at kernel/qapplication.cpp:4030
#14 0x7f9e35071fdb in KApplication::notify (this=0x7c7dc300,
receiver=0x226c990, event=0x26d5fd0)
at
/var/tmp/portage/kde-base/kdelibs-4.3.4/work/kdelibs-4.3.4/kdeui/kernel/kapplication.cpp:302
#15 0x7f9e33517a5b in QCoreApplication::notifyInternal
(this=0x7c7dc300, receiver=0x226c990, event=0x26d5fd0) at
kernel/qcoreapplication.cpp:606
#16 0x7f9e335183b1 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x1751230) at kernel/qcoreapplication.h:213
#17 0x7f9e3353c7c3 in postEventSourceDispatch (s=) at
kernel/qcoreapplication.h:218
#18 0x7f9e2e8e44a9 in IA__g_main_context_dispatch (context=0x1778e90) at
gmain.c:1824
#19 0x7f9e2e8e7ae8 in g_main_context_iterate (context=0x1778e90, block=1,
dispatch=1, self=) at gmain.c:2455
#20 0x7f9e2e8e7c9c in IA__g_main_context_iteration (context=0x1778e90,
may_block=1) at gmain.c:2518
#21 0x7f9e3353c45f in QEventDispatcherGlib::processEvents (this=0x1781100,
flags=) at kernel/qeventdispatcher_glib.cpp:327
#22 0x7f9e3435e89f in QGuiEventDispatcherGlib::processEvents (this=0x60,
flags=) at kernel/qguieventdispatcher_glib.cpp:202
#23 0x7f9e33516442 in QEventLoop::processEvents (this=, flags={i = -58867424}) at kernel/qeventloop.cpp:149
#24 0x7f9e335165dc in QEventLoop::exec (this=0x7c7dc160, flags={i =
-58867344}) at kernel/qeventloop.cpp:197
#25 0x7f9e3351861c in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:888
#26 0x00404b49 in main (argc=1, argv=0x7c7dc8d8) at
/var/tmp/portage/kde-base/kontact-4.3.4/work/kontact-4.3.4/kontact/src/main.cpp:218
Reported using DrKonqi
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 209136] New: entered new appointment (whole day), remote file (sftp) calendar - crash
https://bugs.kde.org/show_bug.cgi?id=209136 Summary: entered new appointment (whole day), remote file (sftp) calendar - crash Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: m...@akhuettel.de Application that crashed: kontact Version of the application: 4.3.1 KDE Version: 4.3.1 (KDE 4.3.1) Qt Version: 4.5.1 Operating System: Linux 2.6.30-gentoo-r4 x86_64 What I was doing when the application crashed: entered new appointment (whole day), remote file (sftp) calendar - crash -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #5 KCal::IncidenceBase::uid (this=0x255f560) at /usr/include/qt4/QtCore/qatomic_x86_64.h:121 #6 0x7fab066cf56c in KOEventViewer::changeIncidenceDisplay (this=0x268aff0, incidence=0x278f8b0, action=0) at /var/tmp/portage/kde-base/korganizer-4.3.1/work/korganizer-4.3.1/korganizer/koeventviewer.cpp:136 #7 0x7fab070ce797 in CalendarView::incidenceAdded (this=0x279ac00, incidence=0x278f8b0) at /var/tmp/portage/kde-base/korganizer-4.3.1/work/korganizer-4.3.1/korganizer/calendarview.cpp:659 #8 0x7fab070d38e0 in CalendarView::qt_metacall (this=0x279ac00, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fffa8b999b0) at /var/tmp/portage/kde-base/korganizer-4.3.1/work/korganizer-4.3.1_build/korganizer/calendarview.moc:484 #9 0x7fab23686e6d in QMetaObject::activate (sender=0x269bf60, from_signal_index=, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3108 #10 0x7fab06b4b33f in KOrg::IncidenceChangerBase::incidenceAdded (this=0x7fffa8b996a0, _t1=0x278f8b0) at /var/tmp/portage/kde-base/korganizer-4.3.1/work/korganizer-4.3.1_build/korganizer/interfaces/korganizer/incidencechangerbase.moc:94 #11 0x7fab07155ead in IncidenceChanger::addIncidence (this=0x269bf60, incidence=0x278f8b0, parent=0x3524240) at /var/tmp/portage/kde-base/korganizer-4.3.1/work/korganizer-4.3.1/korganizer/incidencechanger.cpp:334 #12 0x7fab070e0427 in KOEventEditor::processInput (this=0x3524240) at /var/tmp/portage/kde-base/korganizer-4.3.1/work/korganizer-4.3.1/korganizer/koeventeditor.cpp:346 #13 0x7fab070dd27f in KOIncidenceEditor::slotButtonClicked (this=0x3524240, button=) at /var/tmp/portage/kde-base/korganizer-4.3.1/work/korganizer-4.3.1/korganizer/koincidenceeditor.cpp:102 #14 0x7fab2517695d in KDialog::qt_metacall (this=0x3524240, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fffa8b99f50) at /var/tmp/portage/kde-base/kdelibs-4.3.1-r1/work/kdelibs-4.3.1_build/kdeui/kdialog.moc:184 #15 0x7fab2522c196 in KPageDialog::qt_metacall (this=0x7fffa8b996a0, _c=39187808, _id=0, _a=0x0) at /var/tmp/portage/kde-base/kdelibs-4.3.1-r1/work/kdelibs-4.3.1_build/kdeui/kpagedialog.moc:64 #16 0x7fab070dda35 in KOIncidenceEditor::qt_metacall (this=0x7fffa8b996a0, _c=39187808, _id=0, _a=0x0) at /var/tmp/portage/kde-base/korganizer-4.3.1/work/korganizer-4.3.1_build/korganizer/koincidenceeditor.moc:107 #17 0x7fab070e0906 in KOEventEditor::qt_metacall (this=0x7fffa8b996a0, _c=39187808, _id=0, _a=0x0) at /var/tmp/portage/kde-base/korganizer-4.3.1/work/korganizer-4.3.1_build/korganizer/koeventeditor.moc:71 #18 0x7fab23686e6d in QMetaObject::activate (sender=0x34438c8, from_signal_index=, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3108 #19 0x7fab2368b05e in QSignalMapper::mapped (this=0x7fffa8b996a0, _t1=4) at .moc/release-shared/moc_qsignalmapper.cpp:95 #20 0x7fab2368b100 in QSignalMapper::map (this=0x34438c8, sender=0x35e0300) at kernel/qsignalmapper.cpp:266 #21 0x7fab2368c2f0 in QSignalMapper::qt_metacall (this=0x34438c8, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fffa8b9a0e0) at .moc/release-shared/moc_qsignalmapper.cpp:81 #22 0x7fab23686e6d in QMetaObject::activate (sender=0x35e0300, from_signal_index=, to_signal_index=30, argv=0x0) at kernel/qobject.cpp:3108 #23 0x7fab249ec8a7 in QAbstractButton::clicked (this=0x7fffa8b996a0, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:200 #24 0x7fab2478679b in QAbstractButtonPrivate::emitClicked (this=0x30cf7d0) at widgets/qabstractbutton.cpp:543 #25 0x7fab24786892 in QAbstractButton::click (this=0x35e0300) at widgets/qabstractbutton.cpp:980 #26 0x7fab24887988 in QDialog::keyPressEvent (this=, e=) at dialogs/qdialog.cpp:628 #27 0x7fab24481cc9 in QWidget::event (this=0x3524240, event=0x7fffa8b9a7d0) at kernel/qwidget.cpp:7556 #28 0x7fab2443467d in QApplicationPrivate::notify_helper (this=0x11b11c0, receiver=0x3524240, e=0x7fffa8b9a7d0) at kernel/qapplication.cpp:4057 #29 0x7fab2443e025 in QApplication::notify (this=, receiver=0x3524240, e=0x7fffa8b9a7d0) at kernel/qapplication.cpp:3663 #30 0x7fab252008ab in KApplication::notify (this=0x7f
[Bug 208296] New: Kmail part crashed a while after making a new dimap folder and moving some messages there
https://bugs.kde.org/show_bug.cgi?id=208296
Summary: Kmail part crashed a while after making a new dimap
folder and moving some messages there
Product: kontact
Version: unspecified
Platform: Unlisted Binaries
OS/Version: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: m...@akhuettel.de
Application that crashed: kontact
Version of the application: 4.3.1
KDE Version: 4.3.1 (KDE 4.3.1)
Qt Version: 4.5.1
Operating System: Linux 2.6.30-gentoo-r5 x86_64
What I was doing when the application crashed:
* made a new dimap folder
* moved some messages there from inbox
* dimap was synchronized
* click on message -> crash!
-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#5 0x7f97726f99b0 in vtable for DwString () from
/usr/lib64/libmimelib.so.4
#6 0x7f9774532b21 in KMReaderWin::parseMsg (this=0x22b3f30,
aMsg=0x2d60fa0) at
/var/tmp/portage/kde-base/kmail-4.3.1/work/kmail-4.3.1/kmail/kmreaderwin.cpp:1681
#7 0x7f977452069a in KMReaderWin::displayMessage (this=0x22b3f30) at
/var/tmp/portage/kde-base/kmail-4.3.1/work/kmail-4.3.1/kmail/kmreaderwin.cpp:1605
#8 0x7f9774520885 in KMReaderWin::updateReaderWin (this=0x22b3f30) at
/var/tmp/portage/kde-base/kmail-4.3.1/work/kmail-4.3.1/kmail/kmreaderwin.cpp:1545
#9 0x7f977452c955 in KMReaderWin::qt_metacall (this=0x22b3f30,
_c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fffd5fac060)
at
/var/tmp/portage/kde-base/kmail-4.3.1/work/kmail-4.3.1_build/kmail/kmreaderwin.moc:168
#10 0x7f9785987e4d in QMetaObject::activate (sender=0x22b3fd8,
from_signal_index=, to_signal_index=4, argv=0x1) at
kernel/qobject.cpp:3108
#11 0x7f97859844e3 in QObject::event (this=0x22b3fd8, e=0x1cfb324) at
kernel/qobject.cpp:1073
#12 0x7f978673565d in QApplicationPrivate::notify_helper (this=0x1d2b4b0,
receiver=0x22b3fd8, e=0x7fffd5fac700) at kernel/qapplication.cpp:4057
#13 0x7f978673e04a in QApplication::notify (this=0x7fffd5facb50,
receiver=0x22b3fd8, e=0x7fffd5fac700) at kernel/qapplication.cpp:4022
#14 0x7f97875008ab in KApplication::notify (this=0x7fffd5facb50,
receiver=0x22b3fd8, event=0x7fffd5fac700)
at
/var/tmp/portage/kde-base/kdelibs-4.3.1-r1/work/kdelibs-4.3.1/kdeui/kernel/kapplication.cpp:302
#15 0x7f9785975a1b in QCoreApplication::notifyInternal
(this=0x7fffd5facb50, receiver=0x22b3fd8, event=0x7fffd5fac700) at
kernel/qcoreapplication.cpp:606
#16 0x7f978599e12e in QTimerInfoList::activateTimers (this=0x1d24500) at
kernel/qcoreapplication.h:213
#17 0x7f978599af2d in timerSourceDispatch (source=) at
kernel/qeventdispatcher_glib.cpp:164
#18 0x7f9780d91ce0 in IA__g_main_context_dispatch (context=0x1d2d920) at
gmain.c:1824
#19 0x7f9780d95408 in g_main_context_iterate (context=0x1d2d920, block=1,
dispatch=1, self=) at gmain.c:2455
#20 0x7f9780d955cc in IA__g_main_context_iteration (context=0x1d2d920,
may_block=1) at gmain.c:2518
#21 0x7f978599ae8f in QEventDispatcherGlib::processEvents (this=0x1d22950,
flags=) at kernel/qeventdispatcher_glib.cpp:324
#22 0x7f97867bb81f in QGuiEventDispatcherGlib::processEvents
(this=0x2d60fa0, flags=) at
kernel/qguieventdispatcher_glib.cpp:202
#23 0x7f97859743d2 in QEventLoop::processEvents (this=, flags={i = -704984720}) at kernel/qeventloop.cpp:149
#24 0x7f9785974565 in QEventLoop::exec (this=0x7fffd5fac9b0, flags={i =
-704984640}) at kernel/qeventloop.cpp:196
#25 0x7f97859765fc in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:888
#26 0x00404b59 in main (argc=1, argv=0x7fffd5fad128) at
/var/tmp/portage/kde-base/kontact-4.3.1/work/kontact-4.3.1/kontact/src/main.cpp:218
This bug may be a duplicate of or related to bug 205809
Reported using DrKonqi
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 207732] New: kontact crash when adding new calendar entry (remote file calendar, sftp)
https://bugs.kde.org/show_bug.cgi?id=207732 Summary: kontact crash when adding new calendar entry (remote file calendar, sftp) Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: m...@akhuettel.de Application that crashed: kontact Version of the application: 4.3.1 KDE Version: 4.3.1 (KDE 4.3.1) Qt Version: 4.5.1 Operating System: Linux 2.6.30-gentoo-r4 x86_64 What I was doing when the application crashed: Added a new calendar entry to remote-file (sftp) calendar. Crash on OK. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #5 KCal::IncidenceBase::uid (this=0x2385690) at /usr/include/qt4/QtCore/qatomic_x86_64.h:121 #6 0x7f5adeada56c in KOEventViewer::changeIncidenceDisplay (this=0x311d6c0, incidence=0x5591560, action=0) at /var/tmp/portage/kde-base/korganizer-4.3.1/work/korganizer-4.3.1/korganizer/koeventviewer.cpp:136 #7 0x7f5adf4d9797 in CalendarView::incidenceAdded (this=0x315e5b0, incidence=0x5591560) at /var/tmp/portage/kde-base/korganizer-4.3.1/work/korganizer-4.3.1/korganizer/calendarview.cpp:659 #8 0x7f5adf4de8e0 in CalendarView::qt_metacall (this=0x315e5b0, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x76189f60) at /var/tmp/portage/kde-base/korganizer-4.3.1/work/korganizer-4.3.1_build/korganizer/calendarview.moc:484 #9 0x7f5afb19de6d in QMetaObject::activate (sender=0x312c7b0, from_signal_index=, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3108 #10 0x7f5adef5633f in KOrg::IncidenceChangerBase::incidenceAdded (this=0x76189c50, _t1=0x5591560) at /var/tmp/portage/kde-base/korganizer-4.3.1/work/korganizer-4.3.1_build/korganizer/interfaces/korganizer/incidencechangerbase.moc:94 #11 0x7f5adf560ead in IncidenceChanger::addIncidence (this=0x312c7b0, incidence=0x5591560, parent=0x4b00380) at /var/tmp/portage/kde-base/korganizer-4.3.1/work/korganizer-4.3.1/korganizer/incidencechanger.cpp:334 #12 0x7f5adf4eb427 in KOEventEditor::processInput (this=0x4b00380) at /var/tmp/portage/kde-base/korganizer-4.3.1/work/korganizer-4.3.1/korganizer/koeventeditor.cpp:346 #13 0x7f5adf4e827f in KOIncidenceEditor::slotButtonClicked (this=0x4b00380, button=) at /var/tmp/portage/kde-base/korganizer-4.3.1/work/korganizer-4.3.1/korganizer/koincidenceeditor.cpp:102 #14 0x7f5afcc8b95d in KDialog::qt_metacall (this=0x4b00380, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7618a500) at /var/tmp/portage/kde-base/kdelibs-4.3.1/work/kdelibs-4.3.1_build/kdeui/kdialog.moc:184 #15 0x7f5afcd41196 in KPageDialog::qt_metacall (this=0x76189c50, _c=37246608, _id=0, _a=0x0) at /var/tmp/portage/kde-base/kdelibs-4.3.1/work/kdelibs-4.3.1_build/kdeui/kpagedialog.moc:64 #16 0x7f5adf4e8a35 in KOIncidenceEditor::qt_metacall (this=0x76189c50, _c=37246608, _id=0, _a=0x0) at /var/tmp/portage/kde-base/korganizer-4.3.1/work/korganizer-4.3.1_build/korganizer/koincidenceeditor.moc:107 #17 0x7f5adf4eb906 in KOEventEditor::qt_metacall (this=0x76189c50, _c=37246608, _id=0, _a=0x0) at /var/tmp/portage/kde-base/korganizer-4.3.1/work/korganizer-4.3.1_build/korganizer/koeventeditor.moc:71 #18 0x7f5afb19de6d in QMetaObject::activate (sender=0x56642a8, from_signal_index=, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3108 #19 0x7f5afb1a205e in QSignalMapper::mapped (this=0x76189c50, _t1=4) at .moc/release-shared/moc_qsignalmapper.cpp:95 #20 0x7f5afb1a2100 in QSignalMapper::map (this=0x56642a8, sender=0x526dbf0) at kernel/qsignalmapper.cpp:266 #21 0x7f5afb1a32f0 in QSignalMapper::qt_metacall (this=0x56642a8, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7618a690) at .moc/release-shared/moc_qsignalmapper.cpp:81 #22 0x7f5afb19de6d in QMetaObject::activate (sender=0x526dbf0, from_signal_index=, to_signal_index=30, argv=0x0) at kernel/qobject.cpp:3108 #23 0x7f5afc5018d7 in QAbstractButton::clicked (this=0x76189c50, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:200 #24 0x7f5afc29b7ab in QAbstractButtonPrivate::emitClicked (this=0x558ce00) at widgets/qabstractbutton.cpp:543 #25 0x7f5afc29c662 in QAbstractButtonPrivate::click (this=0x558ce00) at widgets/qabstractbutton.cpp:536 #26 0x7f5afc29c895 in QAbstractButton::mouseReleaseEvent (this=0x526dbf0, e=0x7618afd0) at widgets/qabstractbutton.cpp:1115 #27 0x7f5afbf96de0 in QWidget::event (this=0x526dbf0, event=0x7618afd0) at kernel/qwidget.cpp:7521 #28 0x7f5afbf4967d in QApplicationPrivate::notify_helper (this=0x1d17e60, receiver=0x526dbf0, e=0x7618afd0) at kernel/qapplication.cpp:4057 #29 0x7f5afbf527c9 in QApplication::notify (this=, receiver=0x526dbf0, e=0x7618afd0) at kernel/qapplication.cpp:3759 #30 0x7f
[Bug 205809] New: kmail crash when clicking on message in dimap folder
https://bugs.kde.org/show_bug.cgi?id=205809
Summary: kmail crash when clicking on message in dimap folder
Product: kontact
Version: unspecified
Platform: Unlisted Binaries
OS/Version: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: m...@akhuettel.de
Application that crashed: kontact
Version of the application: 4.3.0
KDE Version: 4.3.00 (KDE 4.3.0)
Qt Version: 4.5.1
Operating System: Linux 2.6.29-gentoo-r5 x86_64
What I was doing when the application crashed:
Kontact crashed with a segfault when I tried to open a message in a DIMAP
folder via mouse click...
-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[Current thread is 0 (LWP 26524)]
Thread 2 (Thread 0x7fe1a9b6d950 (LWP 26153)):
#0 pthread_cond_timedwait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:217
#1 0x7fe1c060a617 in QWaitCondition::wait (this=0x1f0eef8,
mutex=0x1f0eef0, time=3) at thread/qwaitcondition_unix.cpp:85
#2 0x7fe1c06017f9 in QThreadPoolThread::run (this=0x1f0e130) at
concurrent/qthreadpool.cpp:140
#3 0x7fe1c06098b9 in QThreadPrivate::start (arg=0x1f0e130) at
thread/qthread_unix.cpp:189
#4 0x7fe1c0398ff7 in start_thread (arg=) at
pthread_create.c:297
#5 0x7fe1bf96748d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#6 0x in ?? ()
Thread 1 (Thread 0x7fe1c65bd750 (LWP 26524)):
[KCrash Handler]
#5 0x7fe1af475c4e in KMReaderWin::parseMsg (this=0x16fdef0,
aMsg=0x42823b0) at
/var/tmp/portage/kde-base/kmail-4.3.0/work/kmail-4.3.0/kmail/kmreaderwin.cpp:1667
#6 0x7fe1af4626fa in KMReaderWin::displayMessage (this=0x16fdef0) at
/var/tmp/portage/kde-base/kmail-4.3.0/work/kmail-4.3.0/kmail/kmreaderwin.cpp:1589
#7 0x7fe1af4628e5 in KMReaderWin::updateReaderWin (this=0x16fdef0) at
/var/tmp/portage/kde-base/kmail-4.3.0/work/kmail-4.3.0/kmail/kmreaderwin.cpp:1529
#8 0x7fe1af471135 in KMReaderWin::qt_metacall (this=0x16fdef0,
_c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fffce60bd70)
at
/var/tmp/portage/kde-base/kmail-4.3.0/work/kmail-4.3.0_build/kmail/kmreaderwin.moc:165
#9 0x7fe1c06efe4d in QMetaObject::activate (sender=0x16fdf88,
from_signal_index=, to_signal_index=4, argv=0x1) at
kernel/qobject.cpp:3108
#10 0x7fe1c06ec4e3 in QObject::event (this=0x16fdf88, e=0x46) at
kernel/qobject.cpp:1073
#11 0x7fe1c122e65d in QApplicationPrivate::notify_helper (this=0x1116850,
receiver=0x16fdf88, e=0x7fffce60c410) at kernel/qapplication.cpp:4057
#12 0x7fe1c123704a in QApplication::notify (this=0x7fffce60c860,
receiver=0x16fdf88, e=0x7fffce60c410) at kernel/qapplication.cpp:4022
#13 0x7fe1c1ff8fab in KApplication::notify (this=0x7fffce60c860,
receiver=0x16fdf88, event=0x7fffce60c410)
at
/var/tmp/portage/kde-base/kdelibs-4.3.0-r1/work/kdelibs-4.3.0/kdeui/kernel/kapplication.cpp:302
#14 0x7fe1c06dda1b in QCoreApplication::notifyInternal
(this=0x7fffce60c860, receiver=0x16fdf88, event=0x7fffce60c410) at
kernel/qcoreapplication.cpp:606
#15 0x7fe1c070612e in QTimerInfoList::activateTimers (this=0x110d290) at
kernel/qcoreapplication.h:213
#16 0x7fe1c0702f2d in timerSourceDispatch (source=) at
kernel/qeventdispatcher_glib.cpp:164
#17 0x7fe1bbb07bf6 in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#18 0x7fe1bbb0ade5 in ?? () from /usr/lib/libglib-2.0.so.0
#19 0x7fe1bbb0aff7 in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#20 0x7fe1c0702e8f in QEventDispatcherGlib::processEvents (this=0x11163c0,
flags=) at kernel/qeventdispatcher_glib.cpp:324
#21 0x7fe1c12b481f in QGuiEventDispatcherGlib::processEvents
(this=0x42823b0, flags=) at
kernel/qguieventdispatcher_glib.cpp:202
#22 0x7fe1c06dc3d2 in QEventLoop::processEvents (this=, flags={i = -832518528}) at kernel/qeventloop.cpp:149
#23 0x7fe1c06dc565 in QEventLoop::exec (this=0x7fffce60c6c0, flags={i =
-832518448}) at kernel/qeventloop.cpp:196
#24 0x7fe1c06de5fc in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:888
#25 0x00404b59 in main (argc=1, argv=0x7fffce60ce38) at
/var/tmp/portage/kde-base/kontact-4.3.0/work/kontact-4.3.0/kontact/src/main.cpp:218
This bug may be a duplicate of or related to bug 201024
Reported using DrKonqi
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 205022] New: kmail dimap folder rename crash
https://bugs.kde.org/show_bug.cgi?id=205022 Summary: kmail dimap folder rename crash Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: m...@akhuettel.de Application that crashed: kontact Version of the application: 4.3.0 KDE Version: 4.3.00 (KDE 4.3.0) Qt Version: 4.5.1 Operating System: Linux 2.6.30-gentoo-r4 x86_64 What I was doing when the application crashed: I copied some messages from INBOX (on dimap) to a separate folder on dimap. Then I renamed that folder, and pressed "get new messages" to synchronize with the server. Result: Crash. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #5 0x7f444294ba1e in KMail::MessageListView::StorageModel::initializeMessageItem (this=0x3ba8110, mi=0x4fc3ec0, row=, bUseReceiver=false) at /var/tmp/portage/kde-base/kmail-4.3.0/work/kmail-4.3.0/kmail/messagelistview/storagemodel.cpp:299 #6 0x7f44429722a0 in KMail::MessageListView::Core::Model::viewItemJobStepInternalForJobPass1Fill (this=0x27897f0, job=0x4993780, tsta...@0x7fff759cf3c0) at /var/tmp/portage/kde-base/kmail-4.3.0/work/kmail-4.3.0/kmail/messagelistview/core/model.cpp:2735 #7 0x7f4442973bcd in KMail::MessageListView::Core::Model::viewItemJobStepInternalForJob (this=0x27897f0, job=0xf, tsta...@0x7fff759cf3c0) at /var/tmp/portage/kde-base/kmail-4.3.0/work/kmail-4.3.0/kmail/messagelistview/core/model.cpp:3397 #8 0x7f44429743fa in KMail::MessageListView::Core::Model::viewItemJobStepInternal (this=0x27897f0) at /var/tmp/portage/kde-base/kmail-4.3.0/work/kmail-4.3.0/kmail/messagelistview/core/model.cpp:3769 #9 0x7f4442974f5c in KMail::MessageListView::Core::Model::viewItemJobStep (this=0x27897f0) at /var/tmp/portage/kde-base/kmail-4.3.0/work/kmail-4.3.0/kmail/messagelistview/core/model.cpp:3957 #10 0x7f444297631f in KMail::MessageListView::Core::Model::setStorageModel (this=0x27897f0, storageModel=, preSelectionMode=KMail::MessageListView::Core::PreSelectLastSelected) at /var/tmp/portage/kde-base/kmail-4.3.0/work/kmail-4.3.0/kmail/messagelistview/core/model.cpp:791 #11 0x7f4442976d03 in KMail::MessageListView::Core::Model::slotStorageModelLayoutChanged (this=) at /var/tmp/portage/kde-base/kmail-4.3.0/work/kmail-4.3.0/kmail/messagelistview/core/model.cpp:4440 #12 0x7f444253ecd0 in KMail::MessageListView::Core::Model::qt_metacall (this=0x27897f0, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff759cfa70) at /var/tmp/portage/kde-base/kmail-4.3.0/work/kmail-4.3.0_build/kmail/moc_model.cpp:80 #13 0x7f4453b62e6d in QMetaObject::activate (sender=0x3ba8110, from_signal_index=, to_signal_index=17, argv=0x0) at kernel/qobject.cpp:3108 #14 0x7f4453b4af3f in QAbstractItemModel::reset (this=0x3ba8110) at kernel/qabstractitemmodel.cpp:2263 #15 0x7f444253ee98 in KMail::MessageListView::StorageModel::qt_metacall (this=0x3ba8110, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff759cfbd0) at /var/tmp/portage/kde-base/kmail-4.3.0/work/kmail-4.3.0_build/kmail/moc_storagemodel.cpp:92 #16 0x7f4453b62e6d in QMetaObject::activate (sender=0x27450d0, from_signal_index=, to_signal_index=22, argv=0x0) at kernel/qobject.cpp:3108 #17 0x7f444261e96f in KMFolder::setUserWhoField (this=0x27450d0, whofie...@0x7fff759cfee0, writeConfig=false) at /var/tmp/portage/kde-base/kmail-4.3.0/work/kmail-4.3.0/kmail/kmfolder.cpp:745 #18 0x7f444261f6a0 in KMFolder::readConfig (this=0x27450d0, configgro...@0x7fff759d0040) at /var/tmp/portage/kde-base/kmail-4.3.0/work/kmail-4.3.0/kmail/kmfolder.cpp:211 #19 0x7f444264a363 in FolderStorage::readConfig (this=0x27700c0) at /var/tmp/portage/kde-base/kmail-4.3.0/work/kmail-4.3.0/kmail/folderstorage.cpp:963 #20 0x7f444270db8b in KMFolderCachedImap::readConfig (this=0x27700c0) at /var/tmp/portage/kde-base/kmail-4.3.0/work/kmail-4.3.0/kmail/kmfoldercachedimap.cpp:314 #21 0x7f44426465b0 in FolderStorage::countUnread (this=0x27700c0) at /var/tmp/portage/kde-base/kmail-4.3.0/work/kmail-4.3.0/kmail/folderstorage.cpp:866 #22 0x7f4442664b54 in KMSystemTray::updateNewMessages (this=0x2d0cbe0) at /var/tmp/portage/kde-base/kmail-4.3.0/work/kmail-4.3.0/kmail/kmsystemtray.cpp:483 #23 0x7f44426682a8 in KMSystemTray::qt_metacall (this=0x2d0cbe0, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff759d0780) at /var/tmp/portage/kde-base/kmail-4.3.0/work/kmail-4.3.0_build/kmail/kmsystemtray.moc:78 #24 0x7f4453b62e6d in QMetaObject::activate (sender=0x21538a0, from_signal_index=, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3108 #25 0x7f444265edf2 in KMail::AccountManager::checkedMail (this=0x27700c0, _t1=false, _t2=true, _t3=) at /var/tmp/portage/kde-base/kmail-4.3.0/work/kmail-4.3.0_build/kmail/accountmana
[Bug 204654] New: kontact crash imap broken connection
https://bugs.kde.org/show_bug.cgi?id=204654
Summary: kontact crash imap broken connection
Product: kontact
Version: unspecified
Platform: Unlisted Binaries
OS/Version: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: m...@akhuettel.de
Application that crashed: kontact
Version of the application: 4.3.0
KDE Version: 4.3.00 (KDE 4.3.0)
Qt Version: 4.5.1
Operating System: Linux 2.6.29-gentoo-r5 x86_64
-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#5 KIO::Slave::deref (this=0x2796cb0) at
/var/tmp/portage/kde-base/kdelibs-4.3.0/work/kdelibs-4.3.0/kio/kio/slave.cpp:242
#6 0x7f2cbd73a40f in KIO::Slave::gotInput (this=0x2796cb0) at
/var/tmp/portage/kde-base/kdelibs-4.3.0/work/kdelibs-4.3.0/kio/kio/slave.cpp:335
#7 0x7f2cbd73c668 in KIO::Slave::qt_metacall (this=0x2796cb0,
_c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fffc9277440)
at
/var/tmp/portage/kde-base/kdelibs-4.3.0/work/kdelibs-4.3.0_build/kio/slave.moc:76
#8 0x7f2cbb359e4d in QMetaObject::activate (sender=0x27ace10,
from_signal_index=, to_signal_index=4, argv=0x1066a610) at
kernel/qobject.cpp:3108
#9 0x7f2cbd65811f in KIO::ConnectionPrivate::dequeue (this=0x27a7fd0) at
/var/tmp/portage/kde-base/kdelibs-4.3.0/work/kdelibs-4.3.0/kio/kio/connection.cpp:82
#10 0x7f2cbd65857a in KIO::Connection::qt_metacall (this=0x27ace10,
_c=QMetaObject::InvokeMetaMethod, _id=1, _a=0xd879800)
at
/var/tmp/portage/kde-base/kdelibs-4.3.0/work/kdelibs-4.3.0_build/kio/connection.moc:73
#11 0x7f2cbb3567e1 in QObject::event (this=0x27ace10, e=0xd7d6700) at
kernel/qobject.cpp:1106
#12 0x7f2cbbe9865d in QApplicationPrivate::notify_helper (this=0x1973860,
receiver=0x27ace10, e=0xd7d6700) at kernel/qapplication.cpp:4057
#13 0x7f2cbbea104a in QApplication::notify (this=0x7fffc9277f90,
receiver=0x27ace10, e=0xd7d6700) at kernel/qapplication.cpp:4022
#14 0x7f2cbcc62fab in KApplication::notify (this=0x7fffc9277f90,
receiver=0x27ace10, event=0xd7d6700)
at
/var/tmp/portage/kde-base/kdelibs-4.3.0/work/kdelibs-4.3.0/kdeui/kernel/kapplication.cpp:302
#15 0x7f2cbb347a1b in QCoreApplication::notifyInternal
(this=0x7fffc9277f90, receiver=0x27ace10, event=0xd7d6700) at
kernel/qcoreapplication.cpp:606
#16 0x7f2cbb34835e in QCoreApplicationPrivate::sendPostedEvents
(receiver=, event_type=0, data=0x1942230) at
kernel/qcoreapplication.h:213
#17 0x7f2cbb36d1f3 in postEventSourceDispatch (s=) at
kernel/qcoreapplication.h:218
#18 0x7f2cb6771bf6 in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#19 0x7f2cb6774de5 in ?? () from /usr/lib/libglib-2.0.so.0
#20 0x7f2cb6774ff7 in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#21 0x7f2cbb36ce8f in QEventDispatcherGlib::processEvents (this=0x19733d0,
flags=) at kernel/qeventdispatcher_glib.cpp:324
#22 0x7f2cbbf1e81f in QGuiEventDispatcherGlib::processEvents (this=0x20,
flags=) at kernel/qguieventdispatcher_glib.cpp:202
#23 0x7f2cbb3463d2 in QEventLoop::processEvents (this=, flags={i = -920158800}) at kernel/qeventloop.cpp:149
#24 0x7f2cbb346565 in QEventLoop::exec (this=0x7fffc9277df0, flags={i =
-920158720}) at kernel/qeventloop.cpp:196
#25 0x7f2cbb3485fc in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:888
#26 0x00404b59 in main (argc=1, argv=0x7fffc9278568) at
/var/tmp/portage/kde-base/kontact-4.3.0/work/kontact-4.3.0/kontact/src/main.cpp:218
This bug may be a duplicate of or related to bug 201203
Reported using DrKonqi
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 199859] New: Crash when synchronizing dimap (after emptying trash)
https://bugs.kde.org/show_bug.cgi?id=199859 Summary: Crash when synchronizing dimap (after emptying trash) Product: kontact Version: unspecified Platform: Gentoo Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: m...@akhuettel.de Version: 4.2.4 (using KDE 4.2.4) Compiler: gcc (Gentoo 4.3.2-r3 p1.6, pie-10.1.5) 4.3.2 (x86_64) OS:Linux Installed from:Gentoo Packages Anwendung: Kontact (kontact), Signal SIGSEGV 0x7fa2220dee21 in nanosleep () from /lib/libc.so.6 Current language: auto; currently c Thread 1 (Thread 0x7fa228b2e750 (LWP 5908)): [KCrash Handler] #5 0x7fa212c67772 in KMFolderCachedImap::findByUID (this=0x29b75e0, uid=395) at /var/tmp/portage/kde-base/kmail-4.2.4/work/kmail-4.2.4/kmail/kmfoldercachedimap.cpp:684 #6 0x7fa212c7d7b8 in KMFolderCachedImap::slotGetMessagesData (this=0x29b75e0, job=0x3fdc7a0, da...@0x7fff30b731c0) at /var/tmp/portage/kde-base/kmail-4.2.4/work/kmail-4.2.4/kmail/kmfoldercachedimap.cpp:1846 #7 0x7fa212c805cb in KMFolderCachedImap::qt_metacall (this=0x29b75e0, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff30b72df0) at /var/tmp/portage/kde-base/kmail-4.2.4/work/kmail-4.2.4_build/kmail/kmfoldercachedimap.moc:201 #8 0x7fa222e97e6d in QMetaObject::activate (sender=0x3fdc7a0, from_signal_index=, to_signal_index=40, argv=0x3643840) at kernel/qobject.cpp:3108 #9 0x7fa22519ccb4 in KIO::TransferJob::data (this=0x29b75e0, _t1=0x3fdc7a0, _t2=) at /var/tmp/portage/kde-base/kdelibs-4.2.4-r3/work/kdelibs-4.2.4_build/kio/jobclasses.moc:364 #10 0x7fa2251a7bc9 in KIO::TransferJob::qt_metacall (this=0x3fdc7a0, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff30b72f30) at /var/tmp/portage/kde-base/kdelibs-4.2.4-r3/work/kdelibs-4.2.4_build/kio/jobclasses.moc:344 #11 0x7fa222e97e6d in QMetaObject::activate (sender=0x32ce700, from_signal_index=, to_signal_index=4, argv=0x3643840) at kernel/qobject.cpp:3108 #12 0x7fa2252585d2 in KIO::SlaveInterface::data (this=0x29b75e0, _t1=) at /var/tmp/portage/kde-base/kdelibs-4.2.4-r3/work/kdelibs-4.2.4_build/kio/slaveinterface.moc:140 #13 0x7fa22525be18 in KIO::SlaveInterface::dispatch (this=0x32ce700, _cmd=100, rawdata=) at /var/tmp/portage/kde-base/kdelibs-4.2.4-r3/work/kdelibs-4.2.4/kio/kio/slaveinterface.cpp:163 #14 0x7fa225258881 in KIO::SlaveInterface::dispatch (this=0x32ce700) at /var/tmp/portage/kde-base/kdelibs-4.2.4-r3/work/kdelibs-4.2.4/kio/kio/slaveinterface.cpp:91 #15 0x7fa225249ae3 in KIO::Slave::gotInput (this=0x32ce700) at /var/tmp/portage/kde-base/kdelibs-4.2.4-r3/work/kdelibs-4.2.4/kio/kio/slave.cpp:322 #16 0x7fa22524bde8 in KIO::Slave::qt_metacall (this=0x32ce700, _c=QMetaObject::InvokeMetaMethod, _id=4337, _a=0x7fff30b73330) at /var/tmp/portage/kde-base/kdelibs-4.2.4-r3/work/kdelibs-4.2.4_build/kio/slave.moc:76 #17 0x7fa222e97e6d in QMetaObject::activate (sender=0x25206f0, from_signal_index=, to_signal_index=4, argv=0x3643840) at kernel/qobject.cpp:3108 #18 0x7fa2251717ef in KIO::ConnectionPrivate::dequeue (this=0x3309920) at /var/tmp/portage/kde-base/kdelibs-4.2.4-r3/work/kdelibs-4.2.4/kio/kio/connection.cpp:82 #19 0x7fa225171c4a in KIO::Connection::qt_metacall (this=0x25206f0, _c=QMetaObject::InvokeMetaMethod, _id=4337, _a=0x253c9a0) at /var/tmp/portage/kde-base/kdelibs-4.2.4-r3/work/kdelibs-4.2.4_build/kio/connection.moc:73 #20 0x7fa222e94801 in QObject::event (this=0x25206f0, e=0x29adff0) at kernel/qobject.cpp:1106 #21 0x7fa2239c067d in QApplicationPrivate::notify_helper (this=0x2316c90, receiver=0x25206f0, e=0x29adff0) at kernel/qapplication.cpp:4057 #22 0x7fa2239c906a in QApplication::notify (this=0x7fff30b73e80, receiver=0x25206f0, e=0x29adff0) at kernel/qapplication.cpp:4022 #23 0x7fa224cbffdb in KApplication::notify (this=0x7fff30b73e80, receiver=0x25206f0, event=0x29adff0) at /var/tmp/portage/kde-base/kdelibs-4.2.4-r3/work/kdelibs-4.2.4/kdeui/kernel/kapplication.cpp:307 #24 0x7fa222e85a3b in QCoreApplication::notifyInternal (this=0x7fff30b73e80, receiver=0x25206f0, event=0x29adff0) at kernel/qcoreapplication.cpp:606 #25 0x7fa222e8637e in QCoreApplicationPrivate::sendPostedEvents (receiver=, event_type=0, data=0x22e4090) at kernel/qcoreapplication.h:213 #26 0x7fa222eab203 in postEventSourceDispatch (s=) at kernel/qcoreapplication.h:218 #27 0x7fa21e296711 in IA__g_main_context_dispatch (context=0x230d460) at gmain.c:2144 #28 0x7fa21e299e8d in g_main_context_iterate (context=0x230d460, block=1, dispatch=1, self=) at gmain.c:2778 #29 0x7fa21e29a04b in IA__g_main_context_iteration (context=0x230d460, may_block=1) at gmain.c:2841 #30 0x7fa222eaae9f in QEventDispatcherGlib::processEvents (this=0x230b680, flags=) at kernel/qeventdispatcher_glib.cpp:324
