[kontact] [Bug 315666] New: Kontact crashed while running in the background
https://bugs.kde.org/show_bug.cgi?id=315666 Bug ID: 315666 Summary: Kontact crashed while running in the background Classification: Unclassified Product: kontact Version: 4.9.4 Platform: Ubuntu Packages OS: Linux Status: CONFIRMED Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: rob...@narnia.homeunix.com Application: kontact (4.9.4) KDE Platform Version: 4.9.4 Qt Version: 4.8.3 Operating System: Linux 3.5.0-25-generic x86_64 Distribution: Ubuntu 12.10 -- Information about the crash: I wasn't interacting with it at the time, so this is an odd bug. Perhaps there was some fetch running that crashed? Or some interaction with kalarm? -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. __lll_lock_wait_private () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:93 [Current thread is 1 (Thread 0x7f0bbc3d37c0 (LWP 7379))] Thread 4 (Thread 0x7f0bb4913700 (LWP 7382)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f0bcd94ab2d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f0bcd94ac39 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f0bc8e94e9a in start_thread (arg=0x7f0bb4913700) at pthread_create.c:308 #4 0x7f0bce675ccd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 3 (Thread 0x7f0bb4012700 (LWP 7383)): [KCrash Handler] #6 _int_free (av=0x7f0bce93a740 main_arena, p=0x1864740, have_lock=0) at malloc.c:4016 #7 0x7f0bced093b8 in QString::free (d=0x1864750) at tools/qstring.cpp:1235 #8 0x7f0bcb7e4949 in ~QString (this=0x8c56a40, __in_chrg=optimized out) at ../../include/QtCore/../../src/corelib/tools/qstring.h:880 #9 QDBusMessagePrivate::~QDBusMessagePrivate (this=0x8c56a20, __in_chrg=optimized out) at qdbusmessage.cpp:72 #10 0x7f0bcb7e4a5f in QDBusMessage::~QDBusMessage (this=0x7f0bce93a740 main_arena, __in_chrg=optimized out) at qdbusmessage.cpp:537 #11 0x7f0bcb7e077d in ~QDBusCallDeliveryEvent (this=0x878ea50, __in_chrg=optimized out) at qdbusintegrator_p.h:93 #12 QDBusCallDeliveryEvent::~QDBusCallDeliveryEvent (this=0x878ea50, __in_chrg=optimized out) at qdbusintegrator_p.h:93 #13 0x7f0bcedc03fa in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x18187f0) at kernel/qcoreapplication.cpp:1555 #14 0x7f0bcedeaa63 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236 #15 postEventSourceDispatch (s=0x7f0bac0012d0) at kernel/qeventdispatcher_glib.cpp:279 #16 0x7f0bc89c5ab5 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x7f0bc89c5de8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7f0bc89c5ea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x7f0bcedeac16 in QEventDispatcherGlib::processEvents (this=0x7f0bac0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #20 0x7f0bcedbb2bf in QEventLoop::processEvents (this=this@entry=0x7f0bb4011dc0, flags=...) at kernel/qeventloop.cpp:149 #21 0x7f0bcedbb548 in QEventLoop::exec (this=0x7f0bb4011dc0, flags=...) at kernel/qeventloop.cpp:204 #22 0x7f0bcecbcb10 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #23 0x7f0bcecbfaec in QThreadPrivate::start (arg=0x1818680) at thread/qthread_unix.cpp:338 #24 0x7f0bc8e94e9a in start_thread (arg=0x7f0bb4012700) at pthread_create.c:308 #25 0x7f0bce675ccd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #26 0x in ?? () Thread 2 (Thread 0x7f0b65f75700 (LWP 7415)): #0 0x7f0bc8a02ba5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f0bc8a02e49 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0bc89c5769 in g_main_context_query () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0bc89c5cf9 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f0bc89c5ea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f0bcedeac16 in QEventDispatcherGlib::processEvents (this=0x7f0b580008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0x7f0bcedbb2bf in QEventLoop::processEvents (this=this@entry=0x7f0b65f74d90, flags=...) at kernel/qeventloop.cpp:149 #7 0x7f0bcedbb548 in QEventLoop::exec (this=0x7f0b65f74d90, flags=...) at kernel/qeventloop.cpp:204 #8 0x7f0bcecbcb10 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #9 0x7f0bced9b9af in QInotifyFileSystemWatcherEngine::run (this=0x1e9c870) at io/qfilesystemwatcher_inotify.cpp:248 #10 0x7f0bcecbfaec in QThreadPrivate::start (arg=0x1e9c870) at thread/qthread_unix.cpp:338 #11
[kontact] [Bug 314682] New: Kontact crashed unexpectedly with a dbus-error.
https://bugs.kde.org/show_bug.cgi?id=314682 Bug ID: 314682 Summary: Kontact crashed unexpectedly with a dbus-error. Classification: Unclassified Product: kontact Version: 4.9.4 Platform: Ubuntu Packages OS: Linux Status: CONFIRMED Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: rob...@narnia.homeunix.com Application: kontact (4.9.4) KDE Platform Version: 4.9.4 Qt Version: 4.8.3 Operating System: Linux 3.5.0-23-generic x86_64 Distribution: Ubuntu 12.10 -- Information about the crash: I wasn't actually using Kontact when it crashed. Perhaps it was fetching mail? -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0x7f15905667c0 (LWP 13367))] Thread 5 (Thread 0x7f1588aa6700 (LWP 13368)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f15a1addb2d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f15a1addc39 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f159d027e9a in start_thread (arg=0x7f1588aa6700) at pthread_create.c:308 #4 0x7f15a2808ccd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 4 (Thread 0x7f15881a5700 (LWP 13369)): [KCrash Handler] #6 0x7f15a274b425 in __GI_raise (sig=optimized out) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #7 0x7f15a274eb8b in __GI_abort () at abort.c:91 #8 0x7f15a278939e in __libc_message (do_abort=2, fmt=0x7f15a2893028 *** glibc detected *** %s: %s: 0x%s ***\n) at ../sysdeps/unix/sysv/linux/libc_fatal.c:201 #9 0x7f15a2793b96 in malloc_printerr (action=3, str=0x7f15a288f94b invalid fastbin entry (free), ptr=optimized out) at malloc.c:5018 #10 0x7f15a2e9c3b8 in QString::free (d=0xfb19f0) at tools/qstring.cpp:1235 #11 0x7f159f977949 in ~QString (this=0x6e599e0, __in_chrg=optimized out) at ../../include/QtCore/../../src/corelib/tools/qstring.h:880 #12 QDBusMessagePrivate::~QDBusMessagePrivate (this=0x6e599c0, __in_chrg=optimized out) at qdbusmessage.cpp:72 #13 0x7f159f977a5f in QDBusMessage::~QDBusMessage (this=0x3437, __in_chrg=optimized out) at qdbusmessage.cpp:537 #14 0x7f159f97377d in ~QDBusCallDeliveryEvent (this=0xb6ae3f0, __in_chrg=optimized out) at qdbusintegrator_p.h:93 #15 QDBusCallDeliveryEvent::~QDBusCallDeliveryEvent (this=0xb6ae3f0, __in_chrg=optimized out) at qdbusintegrator_p.h:93 #16 0x7f15a2f533fa in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0xfb1430) at kernel/qcoreapplication.cpp:1555 #17 0x7f15a2f7da63 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236 #18 postEventSourceDispatch (s=0x7f15800012d0) at kernel/qeventdispatcher_glib.cpp:279 #19 0x7f159cb58ab5 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x7f159cb58de8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x7f159cb58ea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x7f15a2f7dc16 in QEventDispatcherGlib::processEvents (this=0x7f1588c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #23 0x7f15a2f4e2bf in QEventLoop::processEvents (this=this@entry=0x7f15881a4dc0, flags=...) at kernel/qeventloop.cpp:149 #24 0x7f15a2f4e548 in QEventLoop::exec (this=0x7f15881a4dc0, flags=...) at kernel/qeventloop.cpp:204 #25 0x7f15a2e4fb10 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #26 0x7f15a2e52aec in QThreadPrivate::start (arg=0xfb12a0) at thread/qthread_unix.cpp:338 #27 0x7f159d027e9a in start_thread (arg=0x7f15881a5700) at pthread_create.c:308 #28 0x7f15a2808ccd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #29 0x in ?? () Thread 3 (Thread 0x7f153aa30700 (LWP 13374)): #0 0x7f159d029f69 in __pthread_mutex_lock (mutex=0x7f1534000a60) at pthread_mutex_lock.c:92 #1 0x7f159cb95e21 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f159cb58d3d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f159cb58ea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f15a2f7dc16 in QEventDispatcherGlib::processEvents (this=0x7f15340008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #5 0x7f15a2f4e2bf in QEventLoop::processEvents (this=this@entry=0x7f153aa2fd90, flags=...) at kernel/qeventloop.cpp:149 #6 0x7f15a2f4e548 in QEventLoop::exec (this=0x7f153aa2fd90, flags=...) at kernel/qeventloop.cpp:204 #7 0x7f15a2e4fb10 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #8 0x7f15a2f2e9af in QInotifyFileSystemWatcherEngine::run (this=0x16467b0) at
[Bug 307185] New: Kontact crashes on login
https://bugs.kde.org/show_bug.cgi?id=307185 Bug ID: 307185 Severity: crash Version: 4.9.1 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kontact crashes on login Classification: Unclassified OS: Linux Reporter: rob...@narnia.homeunix.com Hardware: Ubuntu Packages Status: NEW Component: general Product: kontact Application: kontact (4.9.1) KDE Platform Version: 4.9.1 Qt Version: 4.8.3 Operating System: Linux 3.5.0-10-generic x86_64 Distribution: Ubuntu quantal (development branch) -- Information about the crash: When I log in to KDE4, this crash report always pops up. I can't open Kontact until I close the crash report, so it really is running, but it crashes before I can interact with it. Once I close the bug report and reopen Kontact, everything seems fine. Possibly there is a race condition with something in Plasma? A possible related symptom is that the first time I pull up Akregator, it asks me if I want to restore a previous session. Even if I close out normally, so that the message goes away, it comes back whenever I log out and back in. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0x7f500d9637c0 (LWP 3107))] Thread 5 (Thread 0x7f50064d8700 (LWP 3192)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f501eedab2d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f501eedac39 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f501a425e9a in start_thread (arg=0x7f50064d8700) at pthread_create.c:308 #4 0x7f501fc0339d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 4 (Thread 0x7f5005bd7700 (LWP 3209)): #0 0x7f501fbf79e3 in __GI___poll (fds=optimized out, nfds=optimized out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f5019f56e84 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5019f56fa4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5020377c16 in QEventDispatcherGlib::processEvents (this=0x7f5008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f50203482bf in QEventLoop::processEvents (this=this@entry=0x7f5005bd6dc0, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f5020348548 in QEventLoop::exec (this=0x7f5005bd6dc0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f5020249b10 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #7 0x7f502024caec in QThreadPrivate::start (arg=0x122a460) at thread/qthread_unix.cpp:338 #8 0x7f501a425e9a in start_thread (arg=0x7f5005bd7700) at pthread_create.c:308 #9 0x7f501fc0339d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #10 0x in ?? () Thread 3 (Thread 0x7f4fb7ef7700 (LWP 3413)): #0 0x7f501fbf79e3 in __GI___poll (fds=optimized out, nfds=optimized out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f5019f56e84 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5019f56fa4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5020377c16 in QEventDispatcherGlib::processEvents (this=0x7f4fb8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f50203482bf in QEventLoop::processEvents (this=this@entry=0x7f4fb7ef6d90, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f5020348548 in QEventLoop::exec (this=0x7f4fb7ef6d90, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f5020249b10 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #7 0x7f50203289af in QInotifyFileSystemWatcherEngine::run (this=0x188e2b0) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x7f502024caec in QThreadPrivate::start (arg=0x188e2b0) at thread/qthread_unix.cpp:338 #9 0x7f501a425e9a in start_thread (arg=0x7f4fb7ef7700) at pthread_create.c:308 #10 0x7f501fc0339d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 2 (Thread 0x7f4faa7d2700 (LWP 3445)): #0 0x7f501fbf79e3 in __GI___poll (fds=optimized out, nfds=optimized out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f5019f56e84 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5019f56fa4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5020377c16 in QEventDispatcherGlib::processEvents (this=0x7f4fa8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f50203482bf in QEventLoop::processEvents (this=this@entry=0x7f4faa7d1dc0, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f5020348548 in QEventLoop::exec (this=0x7f4faa7d1dc0, flags=...)
[Bug 293013] dataloss: missing message bodies ON THE IMAP SERVER
https://bugs.kde.org/show_bug.cgi?id=293013 Robert Marmorstein rob...@narnia.homeunix.com changed: What|Removed |Added CC||rob...@narnia.homeunix.com --- Comment #9 from Robert Marmorstein rob...@narnia.homeunix.com --- I too am having this issue when mail filters are enabled. I am using Kontact 4.8.3 with Kdelibs 4.8.4 on Kubuntu. Manually moving messages to local folders seems to work fine, but the problem seems to occur when I enable spam filters(bogofilter) using the spam wizard. It goes away when I delete the filters. One thing I noticed -- when the problem occurs, I get a bunch of messages in my Inbox that have no subject, unknown date, and empty header fields. Let me know if I can help debug this further -- this is a serious issue for me and one I'd love to help solve. I'm not afraid to plunge into the code or use Akonadi Console. I can arrange to be available on IRC (#kontact) as atomopawn at a convenient time if that would help. -- 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 258338] accountwizard crashed in KPIMIdentities::Identity::setProperty
https://bugs.kde.org/show_bug.cgi?id=258338 Robert Marmorstein rob...@narnia.homeunix.com changed: What|Removed |Added CC||rob...@narnia.homeunix.com --- Comment #2 from Robert Marmorstein rob...@narnia.homeunix.com --- Looks to me like the probelm is with whatever is calling setProperty not the setProperty call itself (notice that the this pointer is NULL, which should never happen if called from code that correctly creates an Identity object). Unfortunately, the backtrace doesn't go back quite far enough to tell us why this happened in the first place. Aaron -- can you still trigger this bug? -- 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 280313] New: kontact crashes with editor should not be dirty assert when clicking Apply in a new KOrganizer event
https://bugs.kde.org/show_bug.cgi?id=280313 Summary: kontact crashes with editor should not be dirty assert when clicking Apply in a new KOrganizer event Product: kontact Version: GIT (master) Platform: Compiled Sources OS/Version: Linux Status: NEW Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: rob...@narnia.homeunix.com Version: GIT (master) (using Devel) OS:Linux kontact crashes with the following output: kontact(22884) IncidenceEditorNG::CombinedIncidenceEditor::load: Faulty editor was IncidenceCategories kontact(22884) IncidenceEditorNG::CombinedIncidenceEditor::load: Incidence true kontact(22884) IncidenceEditorNG::IncidenceCategories::printDebugInfo: mSelectedCategories = (Miscellaneous, Research:Conference, Research:Conference) kontact(22884) IncidenceEditorNG::IncidenceCategories::printDebugInfo: mLoadedIncidence-categories() = (Miscellaneous, Research:Conference) ASSERT failure in load: editor shouldn't be dirty, file /var/abs/local/eth-os/sources/KDE/kdepim/incidenceeditor-ng/combinedincidenceeditor.cpp, line 108 *** KMail got signal 6 (Exiting) I believe this is a recent regression. KOrganizer was working okay just a few days ago (Some time around Aug 15, 2011?) Reproducible: Always Steps to Reproduce: If I create a new KOrganizer task, add information, check two Categories, and click Apply, kontact crashes with the output shown above. Actual Results: An assertion fails and kontact goes bye-bye. (No task is created in the calendar, either). Expected Results: Kontact correctly creates a new task and continues running. I have debugging symbols enabled, so if I can be of help tracking this down, I can easily obtain a complete backtrace. I usually hang out in #kontact, so just ping me (atomopawn) or post comments here. -- 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 280313] kontact crashes with editor should not be dirty assert when clicking Apply in a new KOrganizer event
https://bugs.kde.org/show_bug.cgi?id=280313 --- Comment #1 from Robert Marmorstein robert narnia homeunix com 2011-08-18 06:53:28 --- Actually, I was mistaken. The tasks DO get created. But kontact does crash immediately afterward. -- 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 251531] Akonadi Crashes Periodically
https://bugs.kde.org/show_bug.cgi?id=251531 Robert Marmorstein rob...@narnia.homeunix.com changed: What|Removed |Added Component|IMAP resource |libakonadi --- Comment #6 from Robert Marmorstein robert narnia homeunix com 2011-01-22 11:01:10 --- Just realized that I never refiled this bug as Kevin had asked. It's possible that this has been fixed already. Should I go back to kdepim from 4.4 and try it? It would be nice to close this out as either fixed or wontfix or whatever. The problem does disappear if you use trunk kdepimlibs with trunk kdepim. -- 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. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 251531] Akonadi Crashes Periodically
https://bugs.kde.org/show_bug.cgi?id=251531 --- Comment #2 from Robert Marmorstein robert narnia homeunix com 2010-09-18 14:56:39 --- Okay. I inserted a qFatal assertion into the throwPayloadException function so it would generate a better backtrace. Here's what I found: Application: Akonadi Resource (akonadi_imap_resource), signal: Aborted [Current thread is 1 (Thread 0x7f58fbf51760 (LWP 24128))] Thread 3 (Thread 0x7f58e7df0710 (LWP 24178)): #0 0x7f58f75d4f43 in poll () from /lib/libc.so.6 #1 0x7f58f65ee064 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f58f65ee59d in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f58fb408832 in QEventDispatcherGlib::processEvents (this=0x16844a0, flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:415 #4 0x7f58fb3e7b6b in QEventLoop::processEvents (this=value optimized out, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f58fb3e7d48 in QEventLoop::exec (this=0x7f58e7defde0, flags=...) at kernel/qeventloop.cpp:201 #6 0x7f58fb34a003 in QThread::exec (this=value optimized out) at thread/qthread.cpp:490 #7 0x7f58fa03f154 in KIMAP::SessionThread::run (this=0x16d9b30) at /var/abs/local/eth-os/sources/KDE/kdepimlibs/kimap/sessionthread.cpp:166 #8 0x7f58fb34bfba in QThreadPrivate::start (arg=0x16d9b30) at thread/qthread_unix.cpp:285 #9 0x7f58fb0c8cb0 in start_thread () from /lib/libpthread.so.0 #10 0x7f58f75dd7ad in clone () from /lib/libc.so.6 #11 0x in ?? () Thread 2 (Thread 0x7f58e6be8710 (LWP 24186)): #0 0x7f58f65ec792 in g_main_context_release () from /usr/lib/libglib-2.0.so.0 #1 0x7f58f65ee098 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f58f65ee59d in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f58fb408832 in QEventDispatcherGlib::processEvents (this=0x183e780, flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:415 #4 0x7f58fb3e7b6b in QEventLoop::processEvents (this=value optimized out, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f58fb3e7d48 in QEventLoop::exec (this=0x7f58e6be7de0, flags=...) at kernel/qeventloop.cpp:201 #6 0x7f58fb34a003 in QThread::exec (this=value optimized out) at thread/qthread.cpp:490 #7 0x7f58fa03f154 in KIMAP::SessionThread::run (this=0x1831a20) at /var/abs/local/eth-os/sources/KDE/kdepimlibs/kimap/sessionthread.cpp:166 #8 0x7f58fb34bfba in QThreadPrivate::start (arg=0x1831a20) at thread/qthread_unix.cpp:285 #9 0x7f58fb0c8cb0 in start_thread () from /lib/libpthread.so.0 #10 0x7f58f75dd7ad in clone () from /lib/libc.so.6 #11 0x in ?? () Thread 1 (Thread 0x7f58fbf51760 (LWP 24128)): [KCrash Handler] #6 0x7f58f7541565 in raise () from /lib/libc.so.6 #7 0x7f58f75429e6 in abort () from /lib/libc.so.6 #8 0x7f58fb345cdf in qt_message_output (msgType=value optimized out, buf=value optimized out) at global/qglobal.cpp:2259 #9 0x7f58fb345dbf in qt_message(QtMsgType, const char *, typedef __va_list_tag __va_list_tag *) (msgType=QtFatalMsg, msg=0x7f58fbae7b73 Payload Exception!, ap=0x7fffd6d69990) at global/qglobal.cpp:2305 #10 0x7f58fb345ede in qFatal (msg=value optimized out) at global/qglobal.cpp:2488 #11 0x7f58fba5ecd8 in Akonadi::Item::throwPayloadException (this=0x177dde0, spid=0, mtid=12) at /var/abs/local/eth-os/sources/KDE/kdepimlibs/akonadi/item.cpp:390 #12 0x7f58fba6f50d in Akonadi::Item::payloadImplQByteArray (this=0x177dde0) at /var/abs/local/eth-os/sources/KDE/kdepimlibs/akonadi/item.h:517 #13 0x7f58fba6f5b8 in Akonadi::Item::payloadQByteArray (this=0x177dde0) at /var/abs/local/eth-os/sources/KDE/kdepimlibs/akonadi/item.h:489 #14 0x7f58fba6e1ed in Akonadi::DefaultItemSerializerPlugin::serialize (this=value optimized out, item=..., label=value optimized out, data=...) at /var/abs/local/eth-os/sources/KDE/kdepimlibs/akonadi/itemserializer.cpp:56 #15 0x7f58fba6e4e9 in Akonadi::ItemSerializer::serialize (item=..., label=..., data=..., versi...@0x7fffd6d6a13c) at /var/abs/local/eth-os/sources/KDE/kdepimlibs/akonadi/itemserializer.cpp:126 #16 0x7f58fba6e583 in Akonadi::ItemSerializer::serialize (item=..., label=..., data=value optimized out, versi...@0x7fffd6d6a13c) at /var/abs/local/eth-os/sources/KDE/kdepimlibs/akonadi/itemserializer.cpp:116 #17 0x7f58fba633ee in Akonadi::ItemCreateJob::doStart (this=value optimized out) at /var/abs/local/eth-os/sources/KDE/kdepimlibs/akonadi/itemcreatejob.cpp:85 #18 0x7f58fba75980 in Akonadi::JobPrivate::startQueued (this=0x177dda0) at /var/abs/local/eth-os/sources/KDE/kdepimlibs/akonadi/job.cpp:152 #19 0x7f58fba75e68 in Akonadi::Job::qt_metacall (this=0x18164b0, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0x17b4a10) at /var/abs/local/eth-os/sources/KDE/kdepimlibs/build/akonadi/job.moc:89 #20 0x7f58fbab9666 in Akonadi::TransactionSequence::qt_metacall (this=0x18164b0, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x17b4a10
[Bug 251531] Akonadi Crashes Periodically
https://bugs.kde.org/show_bug.cgi?id=251531 Robert Marmorstein rob...@narnia.homeunix.com changed: What|Removed |Added Component|IMAP resource |libakonadi --- Comment #3 from Robert Marmorstein robert narnia homeunix com 2010-09-18 15:10:42 --- [09:00] atomopawn_home I'm experiencing bug #251531 and would like some help figuring out how to fix it (or at least provide useful information that might help you guys fix it...). [09:03] krake atomopawn: kdepimlibs from trunk, kdepim-runtime from earlier trunk or branch [09:03] krake see my mail on serializer compatibility on kde-...@kde.org [09:05] krake you can reassign the bug to component libakonadi, not sure though which mail address Marc is using for bugzilla And yes, I am using old kdepim with trunk kdepimlibs -- 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. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 251531] Akonadi Crashes Periodically
https://bugs.kde.org/show_bug.cgi?id=251531 --- Comment #1 from Robert Marmorstein robert narnia homeunix com 2010-09-18 06:51:14 --- Running the akonadi server by hand gives this (potentially useful) output in the terminal: Qt has caught an exception thrown from an event handler. Throwing exceptions from an event handler is not supported in Qt. You must reimplement QApplication::notify() and catch all exceptions there. terminate called after throwing an instance of 'Akonadi::PayloadException' what(): Akonadi::PayloadException: Wrong payload type (requested: sp(0)QByteArray; present: sp(1)KMime::Message* Lost connection to resource org.freedesktop.Akonadi.Resource.akonadi_imap_resource_18 , discarding cached interface KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = akonadi_imap_resource path = /usr/bin pid = 7444 KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit sock_file=/home/robert/.kde/socket-hyaline/kdeinit4__0 -- 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. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 251531] New: Akonadi Crashes Periodically
https://bugs.kde.org/show_bug.cgi?id=251531 Summary: Akonadi Crashes Periodically Product: Akonadi Version: unspecified Platform: Compiled Sources OS/Version: Linux Status: NEW Severity: crash Priority: NOR Component: IMAP resource AssignedTo: er...@kde.org ReportedBy: rob...@narnia.homeunix.com CC: vkra...@kde.org, kdepim-bugs@kde.org Application: akonadi_imap_resource (0.1) KDE Platform Version: 4.5.68 (4.6 = 20100912) (Compiled from sources) Qt Version: 4.7.0 Operating System: Linux 2.6.35-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: This doesn't seem to affect mail retrieval in anyway, but it crashes every few minutes and can be really, really annoying. My guess is that it is happening at the end of a sync. Mail is retrieved -- and then in the cleanup process, the resource crashes. If you'd like, I can valgrind it or try to obtain an akonadiconsole debug log The crash can be reproduced every time. -- Backtrace: Application: Akonadi Resource (akonadi_imap_resource), signal: Aborted [Current thread is 1 (Thread 0x7fa26b02d760 (LWP 17951))] Thread 3 (Thread 0x7fa256ee0710 (LWP 17953)): #0 0xff60017b in ?? () #1 0x7fa256edfa30 in ?? () #2 0x7fffbb7ff6e2 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 2 (Thread 0x7fa252428710 (LWP 17955)): #0 0xff60017b in ?? () #1 0x7fa252427a30 in ?? () #2 0x7fffbb7ff6e2 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 1 (Thread 0x7fa26b02d760 (LWP 17951)): [KCrash Handler] #6 0x7fa26662b565 in raise () from /lib/libc.so.6 #7 0x7fa26662c9e6 in abort () from /lib/libc.so.6 #8 0x7fa266eabded in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/libstdc++.so.6 #9 0x7fa266eaa006 in ?? () from /usr/lib/libstdc++.so.6 #10 0x7fa266eaa033 in std::terminate() () from /usr/lib/libstdc++.so.6 #11 0x7fa266eaa186 in __cxa_rethrow () from /usr/lib/libstdc++.so.6 #12 0x7fa26a4c9d3d in QEventLoop::exec (this=0x7fffbb6e4390, flags=...) at kernel/qeventloop.cpp:214 #13 0x7fa26a4cd16c in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009 #14 0x7fa26ab69e9d in Akonadi::ResourceBase::init (r=0x1bfcb80) at /var/abs/local/eth-os/sources/KDE/kdepimlibs/akonadi/resourcebase.cpp:247 #15 0x004265d1 in int Akonadi::ResourceBase::initImapResource(int, char**) () #16 0x7fa266617c4d in __libc_start_main () from /lib/libc.so.6 #17 0x00411af9 in _start () This bug may be a duplicate of or related to bug 251337. Possible duplicates by query: bug 251337, bug 250953, bug 250863, bug 250705, bug 250525. Reported using DrKonqi -- 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. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 246560] New: imap resource crashes repeatedly on sync
https://bugs.kde.org/show_bug.cgi?id=246560 Summary: imap resource crashes repeatedly on sync Product: kontact Version: SVN trunk (KDE 4) Platform: Compiled Sources OS/Version: Linux Status: NEW Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: rmm...@sdf.lonestar.org Created an attachment (id=49760) -- (http://bugs.kde.org/attachment.cgi?id=49760) Backtrace Version: SVN trunk (KDE 4) (using Devel) OS:Linux Every time I launch kontact (or any other Akonadi-enabled application) the imap_resource crashes repeatedly until Akonadi finally disables it. The debug window in akonadiconsole gives: AgentBase(akonadi_imap_resource_8): No message retrieved, server reply was empty. Which may or may not be directly related to the message. From looking at the backtrace (which I will attach), it seems that what is happening is that the slotDeliveryDone slot is activated while the current task is a SyncCollection task which triggers an assert since the resource expects only itemFetch tasks to be active then. The IMAP server is a Kolab server which has both mail folders and calendars/contacts folders. Synchronization never successfully completes and I am unable to subscribe to folders. Reproducible: Always Steps to Reproduce: Create an imap resource. Try to synchronize it. Actual Results: An assert is hit. Expected Results: Synchronization should complete successfully. -- 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 246560] imap resource crashes repeatedly on sync
https://bugs.kde.org/show_bug.cgi?id=246560 --- Comment #1 from Robert Marmorstein rmmarm sdf lonestar org 2010-08-02 23:59:26 --- One thing to note is that I pulled up the crashed process in gdb and did: (gdb) p scheduler-currentTask().type $4 = Akonadi::ResourceScheduler::SyncCollection So, the current Task is a SyncCollection task. There are some similar bugs, but none of them involve a SyncCollection task. I tested this several times and this is always exactly what happens. I've also deleted and recreated the resource several times with no change in behavior -- it still crashes. -- 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 246560] imap resource crashes repeatedly on sync
https://bugs.kde.org/show_bug.cgi?id=246560 --- Comment #2 from Robert Marmorstein rmmarm sdf lonestar org 2010-08-03 00:02:48 --- Oops. I forgot that I'm not running latest trunk of kdepim. This is with kdepimlibs-4.4 and kdepim-4.4. Everything else on my system (kdelibs, kdebase, kdesupport, etc.) is running from latest trunk. -- 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 236739] KMail Crashes When Opening Config Window
https://bugs.kde.org/show_bug.cgi?id=236739 --- Comment #3 from Robert Marmorstein rmmarm sdf lonestar org 2010-07-11 10:05:17 --- Created an attachment (id=48767) -- (http://bugs.kde.org/attachment.cgi?id=48767) Candidate fix Does this fix the problem? It fixed a similar bug I am having. -- 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 225393] /usr/lib64/gpgmepp/GpgmeppConfig.cmake has incorrect include
https://bugs.kde.org/show_bug.cgi?id=225393 Robert Marmorstein rmm...@sdf.lonestar.org changed: What|Removed |Added CC||rmm...@sdf.lonestar.org --- Comment #1 from Robert Marmorstein rmmarm sdf lonestar org 2010-02-03 16:30:28 --- This breaks compilation of the soon-to-be-released basKet and may affect other third party apps. -- 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 193399] width of items in kmail favorites list is not adjustable
https://bugs.kde.org/show_bug.cgi?id=193399 Robert Marmorstein rmm...@sdf.lonestar.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||FIXED --- Comment #1 from Robert Marmorstein rmmarm sdf lonestar org 2009-07-21 17:24:44 --- This seems to be fixed in trunk now. Thanks! -- 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 193399] New: width of items in kmail favorites list is not adjustable
https://bugs.kde.org/show_bug.cgi?id=193399 Summary: width of items in kmail favorites list is not adjustable Product: kmail Version: unspecified Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: rmm...@sdf.lonestar.org Version:(using Devel) Compiler: gcc-4.4 OS:Linux Installed from:Compiled sources I use kmail from within kontact and have several folders marked as favorites. Unfortunately, kmail automatically pads a lot of extra space onto the end of the names of these folders in the favorites list, which prevents me from resizing the Favorite Folders column in the header. This, in turn, makes it is impossible to eliminate the horizontal scroll bar below the favorites list. It's not a big deal, but I could save a little screen real estate if the behavior can be changed. -- 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
