[kontact] [Bug 368434] Kontact crash when filing through eMail
https://bugs.kde.org/show_bug.cgi?id=368434 --- Comment #9 from Boris Bigott --- This problem has long "gone away". It is so long ago that I do not remember what fixed it. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 418674] New: Kontact crashes everytime "Configure Kontact" is pressed
https://bugs.kde.org/show_bug.cgi?id=418674 Bug ID: 418674 Summary: Kontact crashes everytime "Configure Kontact" is pressed Product: kontact Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: boris.zuba...@gmail.com Target Milestone: --- SUMMARY Kontact crashes everytime "Configure Kontact" is pressed STEPS TO REPRODUCE 1. Run Kontact 2. Open Settings menu 3. Press Configure Kontact OBSERVED RESULT Application immediately crashes with "Report Bug/Restart App" popup EXPECTED RESULT Opened configuration window SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 19.10 Eoan (available in About System) KDE Plasma Version: 5.18.2 KDE Frameworks Version: 5.67.0 Qt Version: 5.12.4 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 418673] New: Kmail hides messages on pressing Del in message list
https://bugs.kde.org/show_bug.cgi?id=418673 Bug ID: 418673 Summary: Kmail hides messages on pressing Del in message list Product: kmail2 Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: message list Assignee: kdepim-bugs@kde.org Reporter: boris.zuba...@gmail.com Target Milestone: --- SUMMARY Kmail hides other messages on pressing Del (or Move to Trash) on single message in message list STEPS TO REPRODUCE 1. Select message among others 2. Press Del to put it in Trash 3. All other messages become hidden. Need to change folder and return back to have the the rest of messages visible again. OBSERVED RESULT Messages become invisible after pressing Del on one of them EXPECTED RESULT Deleted message disappears from list, the rest is still visible. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 19.10 Eoan (available in About System) KDE Plasma Version: 5.18.2 KDE Frameworks Version: 5.67.0 Qt Version: 5.12.4 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 360963] Select identity and "From" automatically on reply in dependence of the answered mail.
https://bugs.kde.org/show_bug.cgi?id=360963 Boris <bugs-kde-joog3eizaec9x...@wcht.de> changed: What|Removed |Added CC||bugs-kde-joog3eizaec9xoo3@w ||cht.de -- 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 339393] New: Akonadi fail to fetch IMAP folder content with over 100MiB of messages (akonadi try to fetch too many UIDs at once)
https://bugs.kde.org/show_bug.cgi?id=339393 Bug ID: 339393 Summary: Akonadi fail to fetch IMAP folder content with over 100MiB of messages (akonadi try to fetch too many UIDs at once) Product: Akonadi Version: 1.13.0 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: boris.sh.1983+kde.bugzi...@gmail.com CC: kdepim-bugs@kde.org, vkra...@kde.org Dear Maintainer, I upgraded to kdepim 4.14-1 from 4.13 (debian unstable) and added a new IMAP account, trying to sync INBOX resolted in zero messages in the folder. during the time of the sync a popup with synching folder inbox is presented that go to 100%. INBOX folder size ~4.5GiB , ~10K unread emails When I created a smaller folder on the IMAP server bellow 100MiB (10MiB akonadi was able to sync and fetch the content). I was able to sync smaller folders. IMAP server Exchange 2007 IMAP logs when clicking on update folder (for INBOX): == imap.log.2116.1 == S: * 28592 EXISTS S: * 0 RECENT S: * FLAGS ( \Seen \Answered \Flagged \Deleted \Draft $MDNSent ) S: * OK Permanent flags [ PERMANENTFLAGS ( \Seen \Answered \Flagged \Deleted \Draft $MDNSent ) ] S: * OK Is the first unseen message [ UNSEEN 2385 ] S: * OK UIDVALIDITY value [ UIDVALIDITY 62022 ] S: * OK The next unique identifier value [ UIDNEXT 42677 ] S: A08 OK SELECT completed. [ READ-WRITE ] C: A09 IDLE S: + IDLE accepted, awaiting DONE command. == imap.log.2116.2 == S: * FLAGS ( \Seen \Answered \Flagged \Deleted \Draft $MDNSent ) S: * OK Permanent flags [ PERMANENTFLAGS ( \Seen \Answered \Flagged \Deleted \Draft $MDNSent ) ] S: * OK Is the first unseen message [ UNSEEN 2385 ] S: * OK UIDVALIDITY value [ UIDVALIDITY 62022 ] S: * OK The next unique identifier value [ UIDNEXT 42677 ] S: A12 OK SELECT completed. [ READ-WRITE ] C: A13 UID SEARCH UID 1:42677 S: A13 NO Server Unavailable. 15 S: * BYE Connection closed. 14 X == imap.log.2116.3 == C: A04 SELECT INBOX S: * 28592 EXISTS S: * 0 RECENT S: * FLAGS ( \Seen \Answered \Flagged \Deleted \Draft $MDNSent ) S: * OK Permanent flags [ PERMANENTFLAGS ( \Seen \Answered \Flagged \Deleted \Draft $MDNSent ) ] S: * OK Is the first unseen message [ UNSEEN 2385 ] S: * OK UIDVALIDITY value [ UIDVALIDITY 62022 ] S: * OK The next unique identifier value [ UIDNEXT 42677 ] S: A04 OK SELECT completed. [ READ-WRITE ] C: A05 EXPUNGE S: A05 OK EXPUNGE completed. C: A06 SELECT INBOX S: * 28592 EXISTS S: * 0 RECENT S: * FLAGS ( \Seen \Answered \Flagged \Deleted \Draft $MDNSent ) S: * OK Permanent flags [ PERMANENTFLAGS ( \Seen \Answered \Flagged \Deleted \Draft $MDNSent ) ] S: * OK Is the first unseen message [ UNSEEN 2385 ] S: * OK UIDVALIDITY value [ UIDVALIDITY 62022 ] S: * OK The next unique identifier value [ UIDNEXT 42677 ] S: A06 OK SELECT completed. [ READ-WRITE ] C: A07 UID SEARCH UID 1:42677 S: A07 NO Server Unavailable. 15 C: A08 EXPUNGE S: A08 OK EXPUNGE completed. C: A09 SELECT INBOX S: * 28592 EXISTS S: * 0 RECENT S: * FLAGS ( \Seen \Answered \Flagged \Deleted \Draft $MDNSent ) S: * OK Permanent flags [ PERMANENTFLAGS ( \Seen \Answered \Flagged \Deleted \Draft $MDNSent ) ] S: * OK Is the first unseen message [ UNSEEN 2385 ] S: * OK UIDVALIDITY value [ UIDVALIDITY 62022 ] S: * OK The next unique identifier value [ UIDNEXT 42677 ] S: A09 OK SELECT completed. [ READ-WRITE ] C: A10 UID SEARCH UID 1:42677 S: A10 NO Server Unavailable. 15 IMAP log for being able to fetch emails : S: A04 OK LIST completed. C: A05 LSUB * S: * LSUB ( ) / Arch S: * LSUB ( ) / Archives/2011 S: * LSUB ( ) / INBOX S: * LSUB ( ) / Sent Items S: * LSUB ( ) / TEST S: A05 OK LSUB completed. C: A06 SUBSCRIBE Junk E-Mail S: A06 OK SUBSCRIBE completed. C: A04 SELECT Junk E-Mail S: * 1065 EXISTS S: * 5 RECENT S: * FLAGS ( \Seen \Answered \Flagged \Deleted \Draft $MDNSent ) S: * OK Permanent flags [ PERMANENTFLAGS ( \Seen \Answered \Flagged \Deleted \Draft $MDNSent ) ] S: * OK Is the first unseen message [ UNSEEN 2 ] S: * OK UIDVALIDITY value [ UIDVALIDITY 62042 ] S: * OK The next unique identifier value [ UIDNEXT 2911 ] S: A04 OK SELECT completed. [ READ-WRITE ] C: A05 EXPUNGE S: A05 OK EXPUNGE completed. C: A06 SELECT Junk E-Mail S: * 1065 EXISTS S: * 0 RECENT S: * FLAGS ( \Seen \Answered \Flagged \Deleted \Draft $MDNSent ) S: * OK Permanent flags [ PERMANENTFLAGS ( \Seen \Answered \Flagged \Deleted \Draft $MDNSent ) ] S: * OK Is the first unseen message [ UNSEEN 2 ] S: * OK UIDVALIDITY value [ UIDVALIDITY 62042 ] S: * OK The next unique identifier value [ UIDNEXT 2911 ] S: A06 OK SELECT completed. [ READ-WRITE ] C: A07 UID SEARCH UID 1:2911 S: *
[Bug 309728] New: Akonadi IMAP resource crashes when I shutdown or reboot my system
https://bugs.kde.org/show_bug.cgi?id=309728 Bug ID: 309728 Severity: crash Version: 4.9 Priority: NOR CC: kdepim-bugs@kde.org, vkra...@kde.org Assignee: er...@kde.org Summary: Akonadi IMAP resource crashes when I shutdown or reboot my system Classification: Unclassified OS: Linux Reporter: bkukush...@gmail.com Hardware: Ubuntu Packages Status: UNCONFIRMED Component: IMAP resource Product: Akonadi Application: akonadi_imap_resource (4.9) KDE Platform Version: 4.9.2 Qt Version: 4.8.2 Operating System: Linux 3.2.0-32-generic-pae i686 Distribution: Ubuntu 12.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: The only thing that needs to be done is to shutdown or reboot my system. Almost every time after the desktop is switched off I end up with the error window on the black background telling that there was an IMAP crash. The crash can be reproduced some of the time. -- Backtrace: Application: Google Mail of type Почтовый сервер IMAP (akonadi_imap_resource), signal: Segmentation fault Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0xb49bb9c0 (LWP 2347))] Thread 3 (Thread 0xb1e59b40 (LWP 2551)): #0 0xb550edcd in __GI_clock_gettime (clock_id=1, tp=0xb1e58fc8) at ../sysdeps/unix/clock_gettime.c:116 #1 0xb723d3b5 in do_gettime (frac=0xb1e58fc0, sec=0xb1e58fb8) at tools/qelapsedtimer_unix.cpp:123 #2 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #3 0xb73276f6 in QTimerInfoList::updateCurrentTime (this=0xb1502074) at kernel/qeventdispatcher_unix.cpp:343 #4 0xb7327a4a in QTimerInfoList::timerWait (this=0xb1502074, tm=...) at kernel/qeventdispatcher_unix.cpp:450 #5 0xb73262f3 in timerSourcePrepareHelper (src=optimized out, timeout=0xb1e590cc) at kernel/qeventdispatcher_glib.cpp:136 #6 0xb732638d in timerSourcePrepare (source=0xb1502040, timeout=optimized out) at kernel/qeventdispatcher_glib.cpp:169 #7 0xb5458872 in g_main_context_prepare (context=0xb15004e0, priority=0xb1e59128) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:2836 #8 0xb5458faf in g_main_context_iterate (dispatch=1, block=1, context=0xb15004e0, self=optimized out) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3126 #9 g_main_context_iterate (context=0xb15004e0, block=1, dispatch=1, self=optimized out) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3083 #10 0xb5459201 in g_main_context_iteration (context=0xb15004e0, may_block=1) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3207 #11 0xb7326db7 in QEventDispatcherGlib::processEvents (this=0xb1500468, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #12 0xb72f267d in QEventLoop::processEvents (this=0xb1e59250, flags=...) at kernel/qeventloop.cpp:149 #13 0xb72f2919 in QEventLoop::exec (this=0xb1e59250, flags=...) at kernel/qeventloop.cpp:204 #14 0xb71db9ec in QThread::exec (this=0x9951950) at thread/qthread.cpp:501 #15 0xb651f299 in KIMAP::SessionThread::run (this=0x9951950) at ../../kimap/sessionthread.cpp:181 #16 0xb71dee80 in QThreadPrivate::start (arg=0x9951950) at thread/qthread_unix.cpp:307 #17 0xb557fd4c in start_thread (arg=0xb1e59b40) at pthread_create.c:308 #18 0xb571dd3e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 2 (Thread 0xb14ffb40 (LWP 2846)): #0 0xb7752424 in __kernel_vsyscall () #1 0xb570d3eb in read () at ../sysdeps/unix/syscall-template.S:82 #2 0xb54976ae in read (__nbytes=16, __buf=0xb14ff08c, __fd=optimized out) at /usr/include/i386-linux-gnu/bits/unistd.h:45 #3 g_wakeup_acknowledge (wakeup=0xb0b01300) at /build/buildd/glib2.0-2.32.3/./glib/gwakeup.c:212 #4 0xb5458bd2 in g_main_context_check (context=0xb0b02000, max_priority=2147483647, fds=0xb0b05d60, n_fds=1) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:2980 #5 0xb5459042 in g_main_context_iterate (dispatch=1, block=-1253676464, context=0xb0b02000, self=optimized out) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3143 #6 g_main_context_iterate (context=0xb0b02000, block=-1253676464, dispatch=1, self=optimized out) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3083 #7 0xb5459201 in g_main_context_iteration (context=0xb0b02000, may_block=1) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3207 #8 0xb7326db7 in QEventDispatcherGlib::processEvents (this=0xb0b03218, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #9 0xb72f267d in QEventLoop::processEvents (this=0xb14ff250, flags=...) at kernel/qeventloop.cpp:149 #10 0xb72f2919 in QEventLoop::exec (this=0xb14ff250, flags=...) at kernel/qeventloop.cpp:204 #11 0xb71db9ec in QThread::exec (this=0x9953690) at thread/qthread.cpp:501 #12 0xb651f299 in KIMAP::SessionThread::run (this=0x9953690) at ../../kimap/sessionthread.cpp:181 #13 0xb71dee80 in QThreadPrivate::start (arg=0x9953690) at thread/qthread_unix.cpp:307 #14 0xb557fd4c in start_thread (arg=0xb14ffb40) at
[Bug 302697] New: Gmail error while shutting the computer down
https://bugs.kde.org/show_bug.cgi?id=302697 Bug ID: 302697 Severity: crash Version: 4.8 Priority: NOR CC: kdepim-bugs@kde.org, vkra...@kde.org Assignee: er...@kde.org Summary: Gmail error while shutting the computer down Classification: Unclassified OS: Linux Reporter: bkukush...@gmail.com Hardware: Ubuntu Packages Status: UNCONFIRMED Component: IMAP resource Product: Akonadi Application: akonadi_imap_resource (4.8) KDE Platform Version: 4.8.3 (4.8.3) Qt Version: 4.8.1 Operating System: Linux 3.2.0-25-generic-pae i686 Distribution: Ubuntu 12.04 LTS -- Information about the crash: - What I was doing when the application crashed: I was shuttin the computer down. During work there were several notifications that there was a Gmail error and that the connection is interrupted. -- Backtrace: Application: Google Mail of type Почтовый сервер IMAP (akonadi_imap_resource), signal: Segmentation fault Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0xb4983980 (LWP 2009))] Thread 3 (Thread 0xb1e16b40 (LWP 2167)): #0 0xb76f3424 in __kernel_vsyscall () #1 0xb56cb380 in __GI___poll (fds=0xb150d5d0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #2 0xb5427a7b in g_poll (fds=0xb150d5d0, nfds=1, timeout=-1) at /build/buildd/glib2.0-2.32.3/./glib/gpoll.c:132 #3 0xb541a0ae in g_main_context_poll (n_fds=1, fds=0xb150d5d0, timeout=optimized out, context=0xb15004e0, priority=optimized out) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3440 #4 g_main_context_iterate (dispatch=1, block=-1253934512, context=0xb15004e0, self=optimized out) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3141 #5 g_main_context_iterate (context=0xb15004e0, block=-1253934512, dispatch=1, self=optimized out) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3083 #6 0xb541a201 in g_main_context_iteration (context=0xb15004e0, may_block=1) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3207 #7 0xb72d78e7 in QEventDispatcherGlib::processEvents (this=0xb1500468, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #8 0xb72a350d in QEventLoop::processEvents (this=0xb1e16250, flags=...) at kernel/qeventloop.cpp:149 #9 0xb72a37a9 in QEventLoop::exec (this=0xb1e16250, flags=...) at kernel/qeventloop.cpp:204 #10 0xb718c94c in QThread::exec (this=0x949bb78) at thread/qthread.cpp:501 #11 0xb64d1269 in ?? () from /usr/lib/libkimap.so.4 #12 0xb718fde0 in QThreadPrivate::start (arg=0x949bb78) at thread/qthread_unix.cpp:298 #13 0xb5540d4c in start_thread (arg=0xb1e16b40) at pthread_create.c:308 #14 0xb56d9ace in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 2 (Thread 0xb14ffb40 (LWP 8889)): #0 0xb54cfdcd in __GI_clock_gettime (clock_id=1, tp=0xb14fefc8) at ../sysdeps/unix/clock_gettime.c:116 #1 0xb71ee315 in do_gettime (frac=0xb14fefc0, sec=0xb14fefb8) at tools/qelapsedtimer_unix.cpp:123 #2 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #3 0xb72d8226 in QTimerInfoList::updateCurrentTime (this=0xb0b0624c) at kernel/qeventdispatcher_unix.cpp:343 #4 0xb72d857a in QTimerInfoList::timerWait (this=0xb0b0624c, tm=...) at kernel/qeventdispatcher_unix.cpp:450 #5 0xb72d6e23 in timerSourcePrepareHelper (src=optimized out, timeout=0xb14ff0cc) at kernel/qeventdispatcher_glib.cpp:136 #6 0xb72d6ebd in timerSourcePrepare (source=0xb0b06218, timeout=optimized out) at kernel/qeventdispatcher_glib.cpp:169 #7 0xb5419872 in g_main_context_prepare (context=0xb0b03020, priority=0xb14ff128) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:2836 #8 0xb5419faf in g_main_context_iterate (dispatch=1, block=1, context=0xb0b03020, self=optimized out) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3126 #9 g_main_context_iterate (context=0xb0b03020, block=1, dispatch=1, self=optimized out) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3083 #10 0xb541a201 in g_main_context_iteration (context=0xb0b03020, may_block=1) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3207 #11 0xb72d78e7 in QEventDispatcherGlib::processEvents (this=0xb0b03218, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #12 0xb72a350d in QEventLoop::processEvents (this=0xb14ff250, flags=...) at kernel/qeventloop.cpp:149 #13 0xb72a37a9 in QEventLoop::exec (this=0xb14ff250, flags=...) at kernel/qeventloop.cpp:204 #14 0xb718c94c in QThread::exec (this=0x94be5f8) at thread/qthread.cpp:501 #15 0xb64d1269 in ?? () from /usr/lib/libkimap.so.4 #16 0xb718fde0 in QThreadPrivate::start (arg=0x94be5f8) at thread/qthread_unix.cpp:298 #17 0xb5540d4c in start_thread (arg=0xb14ffb40) at pthread_create.c:308 #18 0xb56d9ace in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 1 (Thread 0xb4983980 (LWP 2009)): [KCrash Handler] #7 0xb74daf6b in ?? () from /usr/lib/libakonadi-kde.so.4 #8 0xb74db03b in Akonadi::Entity::Entity(Akonadi::Entity const) () from /usr/lib/libakonadi-kde.so.4 #9
[Bug 217367] KMail hangs when I'm writing e-mail
https://bugs.kde.org/show_bug.cgi?id=217367 Boris barb...@ens.fr changed: What|Removed |Added CC||barb...@ens.fr --- Comment #13 from Boris barb...@ens.fr --- I also have noticed kmail hangs while composing (kde 4.6.5 on debian testing). I went searching for a solution because I'd just typed a long email. Couldn't verify any zombie state of mysqld (did I run the wrong command?) $ ps -eaf | grep mysql boris 5819 5816 0 Feb14 ?00:12:55 /usr/sbin/mysqld --defaults-file=/home/boris/.local/share/akonadi//mysql.conf --datadir=/home/boris/.local/share/akonadi/db_data/ --socket=/home/boris/.local/share/akonadi/socket-bordel/mysql.socket boris31488 12407 0 22:20 pts/800:00:00 grep mysql but akonadictl stop akonadictl start unhung things. Thank you, Eero Tamminen. -- 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 277654] some messages are blank after running out of disk space
https://bugs.kde.org/show_bug.cgi?id=277654 Boris barb...@ens.fr changed: What|Removed |Added CC||barb...@ens.fr --- Comment #1 from Boris barbour ens fr 2011-08-02 22:17:27 --- I believe I had a similar problem. Messages were being expired to a mailbox on a network drive (sshfs) that was not spectacularly reliable. At least some messages were lost (blank body) that were expired when the drive was unavailable. I've since arranged things differently, but in general I wonder whether safe arrival is checked before deletion? If not, would it be possible to do? Losing email you intend to keep can cause problems. -- 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 266452] New: segfaulting when opening kaddressbook
https://bugs.kde.org/show_bug.cgi?id=266452 Summary: segfaulting when opening kaddressbook Product: Akonadi Version: unspecified Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Mail Dispatcher Agent AssignedTo: kdepim-bugs@kde.org ReportedBy: valu...@valuial.de CC: vkra...@kde.org Application: akonadi_maildispatcher_agent (0.1) KDE Platform Version: 4.5.5 (KDE 4.5.5) (Compiled from sources) Qt Version: 4.7.1 Operating System: Linux 2.6.37-ck-yuzuki i686 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: First time I encountered the problem, I just added a new contact by right clicking an E-Mail address in a forwarded mail. Second time, I opened kaddressbook from kontact directly. both times several akonadi resources crashed at once, I'll add the other backtraces as well. The crash can be reproduced every time. -- Backtrace: Application: Akonadi Agent (akonadi_maildispatcher_agent), signal: Segmentation fault [KCrash Handler] #7 0xb63ed299 in Akonadi::NotificationMessage::operation() const () from /usr/lib/libakonadiprotocolinternals.so.1 #8 0xb769052b in Akonadi::MonitorPrivate::slotNotify(QListAkonadi::NotificationMessage const) () from /usr/lib/libakonadi-kde.so.4 #9 0xb768aa00 in Akonadi::Monitor::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libakonadi-kde.so.4 #10 0xb743061a in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/qt4/libQtCore.so.4 #11 0xb744318d in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/qt4/libQtCore.so.4 #12 0xb76ebad3 in OrgFreedesktopAkonadiNotificationManagerInterface::notify(QListAkonadi::NotificationMessage const) () from /usr/lib/libakonadi-kde.so.4 #13 0xb76ebb3b in OrgFreedesktopAkonadiNotificationManagerInterface::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libakonadi-kde.so.4 #14 0xb726bb89 in QDBusConnectionPrivate::deliverCall(QObject*, int, QDBusMessage const, QListint const, int) () from /usr/lib/qt4/libQtDBus.so.4 #15 0xb7276dc7 in QDBusCallDeliveryEvent::placeMetaCall(QObject*) () from /usr/lib/qt4/libQtDBus.so.4 #16 0xb743d1c2 in QObject::event(QEvent*) () from /usr/lib/qt4/libQtCore.so.4 #17 0xb5a941ec in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/qt4/libQtGui.so.4 #18 0xb5a99b3e in QApplication::notify(QObject*, QEvent*) () from /usr/lib/qt4/libQtGui.so.4 #19 0xb6ce7caa in KApplication::notify (this=0xbff7ce60, receiver=0x8179720, event=0x817c848) at /var/tmp/portage/kde-base/kdelibs-4.5.5/work/kdelibs-4.5.5/kdeui/kernel/kapplication.cpp:310 #20 0xb742a8db in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/qt4/libQtCore.so.4 #21 0xb742db4c in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/qt4/libQtCore.so.4 #22 0xb742dcad in QCoreApplication::sendPostedEvents(QObject*, int) () from /usr/lib/qt4/libQtCore.so.4 #23 0xb7459334 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /usr/lib/qt4/libQtCore.so.4 #24 0xb5881424 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #25 0xb5885138 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0 #26 0xb5885318 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #27 0xb7458e25 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/qt4/libQtCore.so.4 #28 0xb5b53415 in QGuiEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/qt4/libQtGui.so.4 #29 0xb74293a9 in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/qt4/libQtCore.so.4 #30 0xb742982a in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/qt4/libQtCore.so.4 #31 0xb742dd6f in QCoreApplication::exec() () from /usr/lib/qt4/libQtCore.so.4 #32 0xb5a92f07 in QApplication::exec() () from /usr/lib/qt4/libQtGui.so.4 #33 0xb75d2f78 in Akonadi::AgentBase::init(Akonadi::AgentBase*) () from /usr/lib/libakonadi-kde.so.4 #34 0x0804f874 in main () Possible duplicates by query: bug 266000, bug 252024, bug 251396, bug 247642, bug 247531. 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 266452] segfaulting when opening kaddressbook
https://bugs.kde.org/show_bug.cgi?id=266452 --- Comment #1 from Boris Moddemann valuial valuial de 2011-02-16 14:01:31 --- Created an attachment (id=57294) -- (http://bugs.kde.org/attachment.cgi?id=57294) New crash information added by DrKonqi akonadi_nepomuk_contact_feeder (0.1) on KDE Platform 4.5.5 (KDE 4.5.5) using Qt 4.7.1 - What I was doing when the application crashed: Same as above, this is the second backtrace. two more coming up. -- Backtrace (Reduced): #8 0xb6e8c52b in Akonadi::MonitorPrivate::slotNotify(QListAkonadi::NotificationMessage const) () from /usr/lib/libakonadi-kde.so.4 #9 0xb6df306e in Akonadi::ChangeRecorderPrivate::slotNotify(QListAkonadi::NotificationMessage const) () from /usr/lib/libakonadi-kde.so.4 #10 0xb6e86a00 in Akonadi::Monitor::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libakonadi-kde.so.4 #11 0xb6def4ba in Akonadi::ChangeRecorder::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libakonadi-kde.so.4 [...] [...] #14 0xb6ee7ad3 in OrgFreedesktopAkonadiNotificationManagerInterface::notify(QListAkonadi::NotificationMessage const) () from /usr/lib/libakonadi-kde.so.4 -- 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 266452] segfaulting when opening kaddressbook
https://bugs.kde.org/show_bug.cgi?id=266452 Boris Moddemann valu...@valuial.de changed: What|Removed |Added CC||valu...@valuial.de -- 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 266452] segfaulting when opening kaddressbook
https://bugs.kde.org/show_bug.cgi?id=266452 --- Comment #2 from Boris Moddemann valuial valuial de 2011-02-16 14:02:39 --- Created an attachment (id=57296) -- (http://bugs.kde.org/attachment.cgi?id=57296) New crash information added by DrKonqi kontact (4.4.7) on KDE Platform 4.5.5 (KDE 4.5.5) using Qt 4.7.1 - What I was doing when the application crashed: Same as above, this is the 3rd backtrace, one more coming up. -- Backtrace (Reduced): #8 0xb744052b in Akonadi::MonitorPrivate::slotNotify(QListAkonadi::NotificationMessage const) () from /usr/lib/libakonadi-kde.so.4 #9 0xb73a706e in Akonadi::ChangeRecorderPrivate::slotNotify(QListAkonadi::NotificationMessage const) () from /usr/lib/libakonadi-kde.so.4 #10 0xb743aa00 in Akonadi::Monitor::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libakonadi-kde.so.4 #11 0xb73a34ba in Akonadi::ChangeRecorder::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libakonadi-kde.so.4 [...] [...] #14 0xb749bad3 in OrgFreedesktopAkonadiNotificationManagerInterface::notify(QListAkonadi::NotificationMessage const) () from /usr/lib/libakonadi-kde.so.4 -- 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 266452] segfaulting when opening kaddressbook
https://bugs.kde.org/show_bug.cgi?id=266452 --- Comment #3 from Boris Moddemann valuial valuial de 2011-02-16 14:04:34 --- Created an attachment (id=57297) -- (http://bugs.kde.org/attachment.cgi?id=57297) New crash information added by DrKonqi akonadi_kabc_resource (0.1) on KDE Platform 4.5.5 (KDE 4.5.5) using Qt 4.7.1 - What I was doing when the application crashed: Same as above, this is the last of four backtraces. all four segmentation faults occured at once or right after one another, so I cannot say which came first. -- Backtrace (Reduced): #8 0xb762552b in Akonadi::MonitorPrivate::slotNotify(QListAkonadi::NotificationMessage const) () from /usr/lib/libakonadi-kde.so.4 #9 0xb758c06e in Akonadi::ChangeRecorderPrivate::slotNotify(QListAkonadi::NotificationMessage const) () from /usr/lib/libakonadi-kde.so.4 #10 0xb761fa00 in Akonadi::Monitor::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libakonadi-kde.so.4 #11 0xb75884ba in Akonadi::ChangeRecorder::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libakonadi-kde.so.4 [...] [...] #14 0xb7680ad3 in OrgFreedesktopAkonadiNotificationManagerInterface::notify(QListAkonadi::NotificationMessage const) () from /usr/lib/libakonadi-kde.so.4 -- 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 185544] Kontact is sometimes started twice and crashes when closing the 2nd instance
https://bugs.kde.org/show_bug.cgi?id=185544 Boris Moddemann valu...@valuial.de changed: What|Removed |Added CC|valu...@valuial.de | -- 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 227196] kmail fast search works only for the real names of senders/receivers, but not for their email addresses
https://bugs.kde.org/show_bug.cgi?id=227196 Boris barb...@ens.fr changed: What|Removed |Added CC||barb...@ens.fr --- Comment #1 from Boris barbour ens fr 2010-04-28 16:18:25 --- I agree, it would be extremely useful if the email addresses were indexed in the same way as the subject, real name etc. Best wishes, -- 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 234238] New: Kontact crash on system start; multiple instances
https://bugs.kde.org/show_bug.cgi?id=234238 Summary: Kontact crash on system start; multiple instances Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: valu...@valuial.de Application that crashed: kontact Version of the application: 4.3.5 KDE Version: 4.3.5 (KDE 4.3.5) Qt Version: 4.6.2 Operating System: Linux 2.6.31-gentoo-r6-yuzuki i686 What I was doing when the application crashed: Note: A similar crash (probably duplicate) for a previous version was already reported, but the Assistant didn't find any matching reports. On system start/login, KDE seems to restore multiple instances of Kontact (Error Message appears, asking if I want to start Kontact anyway). If I answer not to start this additional instance, no Kontact is started at all. If I select to start anyway, two instances (windows) are started and crash immediatly with attached backtrace on closing any of the two (using the X-Button on the top right). This bug has been occuring for several versions before, although it became much less frequent. I can't narrow it down completely, but it occures to me that a system shutdown that was not able to run to completion (system hang up during shutdown, but already outside of X) increases the probability of said bug. When the two instances error appears, the application crashes _always_, though. Working with one of the windows, not closing the other, has a high risk of crashing the application as well, which will occure within a few minutes of actively using Kmail (not tested with other parts of Kontact). -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #6 0x08407e77 in ?? () #7 0xaef2cb4d in Akregator::Feed::unread() const () from /usr/lib/kde4/akregatorpart.so #8 0xaef36f4f in Akregator::Folder::updateUnreadCount() const () from /usr/lib/kde4/akregatorpart.so #9 0xaef38d32 in Akregator::Folder::removeChild(Akregator::TreeNode*) () from /usr/lib/kde4/akregatorpart.so #10 0xaef35030 in Akregator::TreeNode::emitSignalDestroyed() () from /usr/lib/kde4/akregatorpart.so #11 0xaef2e58a in Akregator::Feed::~Feed() () from /usr/lib/kde4/akregatorpart.so #12 0xaef35956 in Akregator::Folder::FolderPrivate::~FolderPrivate() () from /usr/lib/kde4/akregatorpart.so #13 0xaef35a17 in Akregator::Folder::~Folder() () from /usr/lib/kde4/akregatorpart.so #14 0xaef35956 in Akregator::Folder::FolderPrivate::~FolderPrivate() () from /usr/lib/kde4/akregatorpart.so #15 0xaef35a17 in Akregator::Folder::~Folder() () from /usr/lib/kde4/akregatorpart.so #16 0xaef3acf4 in Akregator::FeedList::setRootNode(Akregator::Folder*) () from /usr/lib/kde4/akregatorpart.so #17 0xaef3d1be in Akregator::FeedList::~FeedList() () from /usr/lib/kde4/akregatorpart.so #18 0xaef818e8 in boost::detail::sp_counted_impl_pAkregator::FeedList::dispose() () from /usr/lib/kde4/akregatorpart.so #19 0xaef25b30 in Akregator::ArticleDeleteJob::~ArticleDeleteJob() () from /usr/lib/kde4/akregatorpart.so #20 0xb4ccef2f in QObjectPrivate::deleteChildren() () from /usr/lib/qt4/libQtCore.so.4 #21 0xb4cd6909 in QObject::~QObject() () from /usr/lib/qt4/libQtCore.so.4 #22 0xaeee1fe7 in Akregator::Command::~Command() () from /usr/lib/libakregatorinterfaces.so.4 #23 0xaef61aa9 in Akregator::ExpireItemsCommand::~ExpireItemsCommand() () from /usr/lib/kde4/akregatorpart.so #24 0xb4ccef2f in QObjectPrivate::deleteChildren() () from /usr/lib/qt4/libQtCore.so.4 #25 0xb5283263 in QWidget::~QWidget() () from /usr/lib/qt4/libQtGui.so.4 #26 0xaef9852c in Akregator::MainWidget::~MainWidget() () from /usr/lib/kde4/akregatorpart.so #27 0xb6333e4e in ~Part (this=0x86bcde0, __vtt_parm=0xaefe9fa8, __in_chrg=value optimized out) at /var/tmp/portage/kde-base/kdelibs-4.3.5/work/kdelibs-4.3.5/kparts/part.cpp:208 #28 0xb633417a in ~ReadOnlyPart (this=0x86bcde0, __vtt_parm=0xaefe9fa4, __in_chrg=value optimized out) at /var/tmp/portage/kde-base/kdelibs-4.3.5/work/kdelibs-4.3.5/kparts/part.cpp:459 #29 0xaef95f82 in Akregator::Part::~Part() () from /usr/lib/kde4/akregatorpart.so #30 0xb71292f9 in Kontact::Plugin::~Plugin() () from /usr/lib/libkontactinterfaces.so.4 #31 0xb0ba5b4c in AkregatorPlugin::~AkregatorPlugin() () from /usr/lib/kde4/kontact_akregatorplugin.so #32 0xb7148f06 in ~MainWindow (this=0x8148210, __in_chrg=value optimized out, __vtt_parm=value optimized out) at /var/tmp/portage/kde-base/kontact-4.3.5/work/kontact-4.3.5/kontact/src/mainwindow.cpp:274 #33 0xb4cceb55 in qDeleteInEventHandler(QObject*) () from /usr/lib/qt4/libQtCore.so.4 #34 0xb4cd0640 in QObject::event(QEvent*) () from /usr/lib/qt4/libQtCore.so.4 #35 0xb527b3f0 in QWidget::event(QEvent*) () from /usr/lib/qt4/libQtGui.so.4 #36 0xb5680667 in QMainWindow::event(QEvent*) () from /usr/lib/qt4/libQtGui.so.4 #37
[Bug 222378] kmail/kontact crash when clicking on a particular new email (edited subject)
https://bugs.kde.org/show_bug.cgi?id=222378 Boris barb...@ens.fr changed: What|Removed |Added Summary|kmail/kontact crash |kmail/kontact crash when |synchronising dimap when|clicking on a particular |many messages expired |new email (edited subject) |(moved) + click to view new | |message | -- 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 222378] New: kmail/kontact crash synchronising dimap when many messages expired (moved) + click to view new message
https://bugs.kde.org/show_bug.cgi?id=222378 Summary: kmail/kontact crash synchronising dimap when many messages expired (moved) + click to view new message Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: barb...@ens.fr 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-2-amd64 x86_64 Distribution: Debian GNU/Linux testing (squeeze) What I was doing when the application crashed: In kmail I had expired many messages, which moved them to another folder. This was being synchronised (dimap). During the process I clicked on a new message to view it, and the crash occurred. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault The current source language is auto; currently c. [KCrash Handler] #5 KMimeType::d_func (this=0x0, url=...) at ../../kdecore/services/kmimetype.h:48 #6 KMimeType::iconName (this=0x0, url=...) at ../../kdecore/services/kmimetype.cpp:681 #7 0x7f5407bc3388 in KMail::ObjectTreeParser::processApplicationMsTnefSubtype (this=0x7fff2109e410, node=value optimized out, result=value optimized out) at ../../kmail/objecttreeparser.cpp:1900 #8 0x7f5407bce6be in KMail::ObjectTreeParser::parseObjectTree (this=0x7fff2109e410, node=0x2b748cb0) at ../../kmail/objecttreeparser.cpp:296 #9 0x7f5407bce8b5 in KMail::ObjectTreeParser::stdChildHandling (this=0x7fff2109e720, child=0x121534700) at ../../kmail/objecttreeparser.cpp:1146 #10 0x7f5407bcec34 in KMail::ObjectTreeParser::processMultiPartMixedSubtype (this=0x7fff2109dfb0, node=value optimized out) at ../../kmail/objecttreeparser.cpp:1159 #11 0x7f5407bce6be in KMail::ObjectTreeParser::parseObjectTree (this=0x7fff2109e720, node=0x313ff70) at ../../kmail/objecttreeparser.cpp:296 #12 0x7f5407a53b69 in KMReaderWin::parseMsg (this=0x2d77d60, aMsg=0x5029550) at ../../kmail/kmreaderwin.cpp:1682 #13 0x7f5407a42ada in KMReaderWin::displayMessage (this=0x2d77d60) at ../../kmail/kmreaderwin.cpp:1608 #14 0x7f5407a42cb4 in KMReaderWin::updateReaderWin (this=0x2d77d60) at ../../kmail/kmreaderwin.cpp:1548 #15 0x7f5407a4fd9d in KMReaderWin::qt_metacall (this=0x2d77d60, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff2109edc0) at ./kmreaderwin.moc:168 #16 0x7f541dd57df2 in QMetaObject::activate (sender=0x2d77e08, from_signal_index=value optimized out, to_signal_index=4, argv=0xff0f9d01) at kernel/qobject.cpp:3112 #17 0x7f541dd52353 in QObject::event (this=0x2d77e08, e=0x0) at kernel/qobject.cpp:1074 #18 0x7f541d1bc01d in QApplicationPrivate::notify_helper (this=0x1e57fc0, receiver=0x2d77e08, e=0x7fff2109f470) at kernel/qapplication.cpp:4065 #19 0x7f541d1c407a in QApplication::notify (this=0x7fff2109f7e0, receiver=0x2d77e08, e=0x7fff2109f470) at kernel/qapplication.cpp:4030 #20 0x7f541e6e8e06 in KApplication::notify (this=0x7fff2109f7e0, receiver=0x2d77e08, event=0x7fff2109f470) at ../../kdeui/kernel/kapplication.cpp:302 #21 0x7f541dd42c9c in QCoreApplication::notifyInternal (this=0x7fff2109f7e0, receiver=0x2d77e08, event=0x7fff2109f470) at kernel/qcoreapplication.cpp:610 #22 0x7f541dd6f2c6 in QCoreApplication::sendEvent (this=0x1e5b8c0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #23 QTimerInfoList::activateTimers (this=0x1e5b8c0) at kernel/qeventdispatcher_unix.cpp:580 #24 0x7f541dd6b658 in timerSourceDispatch (source=value optimized out) at kernel/qeventdispatcher_glib.cpp:184 #25 idleTimerSourceDispatch (source=value optimized out) at kernel/qeventdispatcher_glib.cpp:231 #26 0x7f5416a4d13a in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #27 0x7f5416a50998 in ?? () from /lib/libglib-2.0.so.0 #28 0x7f5416a50b4c in g_main_context_iteration () from /lib/libglib-2.0.so.0 #29 0x7f541dd6b39c in QEventDispatcherGlib::processEvents (this=0x1e2ef70, flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:407 #30 0x7f541d252f1f in QGuiEventDispatcherGlib::processEvents (this=0x7fff2109dfb0, flags=value optimized out) at kernel/qguieventdispatcher_glib.cpp:202 #31 0x7f541dd41562 in QEventLoop::processEvents (this=value optimized out, flags=...) at kernel/qeventloop.cpp:149 #32 0x7f541dd41934 in QEventLoop::exec (this=0x7fff2109f720, flags=...) at kernel/qeventloop.cpp:201 #33 0x7f541dd43ba4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #34 0x00403f17 in main (argc=value optimized out, argv=value optimized out) at ../../../kontact/src/main.cpp:218 Reported using DrKonqi -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are
[Bug 222378] kmail/kontact crash synchronising dimap when many messages expired (moved) + click to view new message
https://bugs.kde.org/show_bug.cgi?id=222378 --- Comment #1 from Boris barbour ens fr 2010-01-12 15:08:36 --- Having restarted kontact, it seems that the crash is simply triggered by trying to read the email in question (nothing to do with the move/synchronisation on-going at the time). I forwarded the offending email from another program and again it crashed kmail whenever I clicked on it in the message list. Unfortunately I no longer have a copy of the email, as I needed to delete it (using another program). I will post another example if the problem recurs. -- 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 222378] kmail/kontact crash synchronising dimap when many messages expired (moved) + click to view new message
https://bugs.kde.org/show_bug.cgi?id=222378 --- Comment #2 from Boris barbour ens fr 2010-01-13 00:29:44 --- Hi again, I can confirm this on another (similar) computer with the same email - I found another copy. I'm not very keen to post the email, as it contains something confidential. I was hoping to create a reduced test case. I extracted the email from the mbox and was hoping to open it using kmail --view file://emailname, but I must have misunderstood something as I get an error message The file or folder smb://emailname/ does not exist. (I can't understand why the smb protocol is used.) If there is any other information that would be helpful, let me know. Regards, Boris -- 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 212036] New: kontact crash every startup: another instance already running
https://bugs.kde.org/show_bug.cgi?id=212036 Summary: kontact crash every startup: another instance already running Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: valu...@valuial.de Application that crashed: kontact Version of the application: 4.3.2 KDE Version: 4.3.2 (KDE 4.3.2) Qt Version: 4.5.3 Operating System: Linux 2.6.30-gentoo-r7-yuzuki i686 What I was doing when the application crashed: Saved session tries to start kontact, which reports another instance already running. If stopped to start the second instance, no kontact starts at all, if started anyway, two kontact windows (instances) show up, but crash whenever anything is done (closed, navigated to some mails, etc.) This is always reproducable with a saved session. This problem was not in KDE 4.3.1, but I had a similar behaviour some version before that at some point. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 0 (LWP 4425)] Thread 2 (Thread 0xaf343b90 (LWP 4556)): #0 0xb7fd7c50 in ?? () from /lib/ld-linux.so.2 #1 0xb7fd8008 in ?? () from /lib/ld-linux.so.2 #2 0xb7fdd766 in ?? () from /lib/ld-linux.so.2 #3 0xb7fe4740 in ?? () from /lib/ld-linux.so.2 #4 0xb5be9d02 in QEventDispatcherGlib::~QEventDispatcherGlib () from /usr/lib/qt4/libQtCore.so.4 #5 0xb5ad83fd in QThreadPrivate::finish () from /usr/lib/qt4/libQtCore.so.4 #6 0xb5ad8539 in QThreadPrivate::start () from /usr/lib/qt4/libQtCore.so.4 #7 0xb5a564cf in start_thread () from /lib/libpthread.so.0 Thread 1 (Thread 0xb49df700 (LWP 4425)): [KCrash Handler] #6 0xb1421566 in KMail::ListJob::slotListEntries () from /usr/lib/libkmailprivate.so.4 #7 0xb142254e in KMail::ListJob::qt_metacall () from /usr/lib/libkmailprivate.so.4 #8 0xb5bd40f4 in QMetaObject::activate () from /usr/lib/qt4/libQtCore.so.4 #9 0xb5bd4692 in QMetaObject::activate () from /usr/lib/qt4/libQtCore.so.4 #10 0xb6cd0169 in KIO::ListJob::entries (this=0x888a690, _t1=0x888a690, _...@0xbfdb4954) at /var/tmp/portage/kde-base/kdelibs-4.3.2-r3/work/kdelibs-4.3.2_build/kio/jobclasses.moc:781 #11 0xb6cdcb58 in KIO::ListJobPrivate::slotListEntries (this=0x888a360, li...@0xbfdb4954) at /var/tmp/portage/kde-base/kdelibs-4.3.2-r3/work/kdelibs-4.3.2/kio/kio/job.cpp:2333 #12 0xb6cdcc60 in KIO::ListJob::qt_metacall (this=0x888a690, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbfdb481c) at /var/tmp/portage/kde-base/kdelibs-4.3.2-r3/work/kdelibs-4.3.2_build/kio/jobclasses.moc:767 #13 0xb5bd40f4 in QMetaObject::activate () from /usr/lib/qt4/libQtCore.so.4 #14 0xb5bd4692 in QMetaObject::activate () from /usr/lib/qt4/libQtCore.so.4 #15 0xb6da0733 in KIO::SlaveInterface::listEntries (this=0x87d16c8, _...@0xbfdb4954) at /var/tmp/portage/kde-base/kdelibs-4.3.2-r3/work/kdelibs-4.3.2_build/kio/slaveinterface.moc:179 #16 0xb6da44d9 in KIO::SlaveInterface::dispatch (this=0x87d16c8, _cmd=106, rawda...@0xbfdb49a4) at /var/tmp/portage/kde-base/kdelibs-4.3.2-r3/work/kdelibs-4.3.2/kio/kio/slaveinterface.cpp:193 #17 0xb6da0cc7 in KIO::SlaveInterface::dispatch (this=0x87d16c8) at /var/tmp/portage/kde-base/kdelibs-4.3.2-r3/work/kdelibs-4.3.2/kio/kio/slaveinterface.cpp:91 #18 0xb6d92cad in KIO::Slave::gotInput (this=0x87d16c8) at /var/tmp/portage/kde-base/kdelibs-4.3.2-r3/work/kdelibs-4.3.2/kio/kio/slave.cpp:322 #19 0xb6d95193 in KIO::Slave::qt_metacall (this=0x87d16c8, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfdb4aa8) at /var/tmp/portage/kde-base/kdelibs-4.3.2-r3/work/kdelibs-4.3.2_build/kio/slave.moc:76 #20 0xb5bd40f4 in QMetaObject::activate () from /usr/lib/qt4/libQtCore.so.4 #21 0xb5bd4692 in QMetaObject::activate () from /usr/lib/qt4/libQtCore.so.4 #22 0xb6c9ee77 in KIO::Connection::readyRead (this=0x81cfff8) at /var/tmp/portage/kde-base/kdelibs-4.3.2-r3/work/kdelibs-4.3.2_build/kio/connection.moc:86 #23 0xb6ca0793 in KIO::ConnectionPrivate::dequeue (this=0x81cfff8) at /var/tmp/portage/kde-base/kdelibs-4.3.2-r3/work/kdelibs-4.3.2/kio/kio/connection.cpp:82 #24 0xb6ca0b76 in KIO::Connection::qt_metacall (this=0x81cfff8, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x864b7a8) at /var/tmp/portage/kde-base/kdelibs-4.3.2-r3/work/kdelibs-4.3.2_build/kio/connection.moc:73 #25 0xb5bcf50b in QMetaCallEvent::placeMetaCall () from /usr/lib/qt4/libQtCore.so.4 #26 0xb5bd12a0 in QObject::event () from /usr/lib/qt4/libQtCore.so.4 #27 0xb6075544 in QApplicationPrivate::notify_helper () from /usr/lib/qt4/libQtGui.so.4 #28 0xb607dd2e in QApplication::notify () from /usr/lib/qt4/libQtGui.so.4 #29 0xb6949e8d in KApplication::notify (this=0xbfdb5228, receiver=0x81cfff8, event=0x880c748) at /var/tmp/portage/kde-base/kdelibs-4.3.2-r3/work/kdelibs-4.3.2/kdeui/kernel/kapplication.cpp:302 #30 0xb5bc200b in
[Bug 106030] Crash when retrieving mail (cachedimap)
else be helpful.useful? Boris ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
