[akregator] [Bug 260986] Akregator crashes on KDE shutdown
https://bugs.kde.org/show_bug.cgi?id=260986 Chris Samuel changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #14 from Chris Samuel --- Hi Justin, I believe this was solved a few years ago as per this comment: https://bugs.kde.org/show_bug.cgi?id=260986#c12 I'll try and close this now. All the best, Chris -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 329496] Kontact crashed on exit
https://bugs.kde.org/show_bug.cgi?id=329496 --- Comment #11 from Chris Samuel --- FWIW Kontact still always crashes for me, but this is in kaggregator. I'd pretty much given up on getting things fixed so I'd not bothered to report it. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 419782] Unable to connect to IMAP server
https://bugs.kde.org/show_bug.cgi?id=419782 --- Comment #7 from Chris Samuel --- The solution (for me) under Kubuntu 20.04 was to modify /etc/ssl/openssl.cnf after the line: oid_section = new_oids by adding: openssl_conf = default_conf [default_conf] ssl_conf = ssl_sect [ssl_sect] system_default = system_default_sect [system_default_sect] MinProtocol = TLSv1.2 CipherString = DEFAULT@SECLEVEL=1 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 400221] can't talk to dovecot imap server
https://bugs.kde.org/show_bug.cgi?id=400221 --- Comment #9 from Chris Samuel --- The solution (for me) under Kubuntu 20.04 was to modify /etc/ssl/openssl.cnf after the line: oid_section = new_oids by adding: openssl_conf = default_conf [default_conf] ssl_conf = ssl_sect [ssl_sect] system_default = system_default_sect [system_default_sect] MinProtocol = TLSv1.2 CipherString = DEFAULT@SECLEVEL=1 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 400221] can't talk to dovecot imap server
https://bugs.kde.org/show_bug.cgi?id=400221 --- Comment #8 from Chris Samuel --- Apologies, I had two bugs open in adjacent tabs and updated this instead of https://bugs.kde.org/show_bug.cgi?id=419782 (I strongly suspect it's a duplicate of this). -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 419782] Unable to connect to IMAP server
https://bugs.kde.org/show_bug.cgi?id=419782 --- Comment #6 from Chris Samuel --- I suspect this is a duplicate of https://bugs.kde.org/show_bug.cgi?id=400221 which I just mistakenly updated instead of this. It's an SSL issue (the IMAP server is not configured to use long enough DH keys). -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 400221] can't talk to dovecot imap server
https://bugs.kde.org/show_bug.cgi?id=400221 Chris Samuel changed: What|Removed |Added CC||k...@csamuel.org --- Comment #7 from Chris Samuel --- Hi there, I have a strong suspicion that this is SSL related, I've found that this does not work: openssl s_client -connect example.com:993 [...] 139765775537472:error:141A318A:SSL routines:tls_process_ske_dhe:dh key too small:../ssl/statem/statem_clnt.c:2149: [...] but this does (found here: https://imlc.me/dh-key-too-small ): openssl s_client -connect example.com:993 --cipher 'DEFAULT:!DH' Now the received wisdom is that this is because of OpenSSL configuration and you can fix it by adding this to /etc/ssl/openssl.cnf: [system_default_sect] MinProtocol = TLSv1.2 CipherString = DEFAULT@SECLEVEL=2 However, that does not seem to work, either for the OpenSSL command line or for Akonadi. All the best, Chris -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 419782] Unable to connect to IMAP server
https://bugs.kde.org/show_bug.cgi?id=419782 Chris Samuel changed: What|Removed |Added CC||k...@csamuel.org --- Comment #3 from Chris Samuel --- Hi there, I've just run into this issue in the Kubuntu 20.04 beta release with Kontact Version 5.13.3 (19.12.3) and was wondering if you could point me at the fix so I can see if the maintainers are able to backport it into their release please? Thanks! Chris -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 353826] Kontact crashes every time I exit
https://bugs.kde.org/show_bug.cgi?id=353826 Chris Samuel changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #10 from Chris Samuel --- All still good - I'm closing this as fixed, thanks you! -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 260986] Akregator crashes on KDE shutdown
https://bugs.kde.org/show_bug.cgi?id=260986 --- Comment #12 from Chris Samuel --- Hi all, Good news for me at least, with the latest Kubuntu PPA packages everything seems to be good - I am no longer seeing these crashes! Thank you so much! All the best, Chris -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 353826] Kontact crashes every time I exit
https://bugs.kde.org/show_bug.cgi?id=353826 --- Comment #9 from Chris Samuel --- (In reply to Erik Quaeghebeur from comment #8) > Good travels! Thank you! > Can you report back once you're settled and have the time to test a more > recent version than you last reported about? OK, I've just tonight upgraded to 18.10 and installed their Kubuntu PPA backports and upgraded to their most recent Plasma and KDE packages. So far so good! Needs more testing than just starting and exiting 3 times, but no crashes so far. Kontact version 5.8.3, KDE Frameworks 5.52.0 All the best, Chris -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 260986] Akregator crashes on KDE shutdown
https://bugs.kde.org/show_bug.cgi?id=260986 --- Comment #9 from Chris Samuel --- (In reply to CnZhx from comment #8) > Does this still happen with the latest version of Kontact/Akregator as well > as KDE Plasma and Frameworks? My computers have only just arrived by ship from Australia and I won't have a good Internet connection until Sunday evening I'm afraid, so I'm not in a position to upgrade Kubuntu yet. > Have you tried to issue following commands in > Konsole or any terminal and seen what would happen? > ``` > akonadictl fsck && akonadictl restart > ``` Yes, numerous times, and that didn't help I'm afraid. All the best, Chris -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 353826] Kontact crashes every time I exit
https://bugs.kde.org/show_bug.cgi?id=353826 --- Comment #7 from Chris Samuel --- (In reply to Erik Quaeghebeur from comment #5) > Is this still happening? I'm currently in the middle of moving hemispheres so my PC is in a container on a ship somewhere, but it was still happening just before it was packed away. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 260986] Akregator crashes on KDE shutdown
https://bugs.kde.org/show_bug.cgi?id=260986 --- Comment #7 from Chris Samuel --- This is kontact/akgregator 17.04.3 -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 260986] Akregator crashes on KDE shutdown
https://bugs.kde.org/show_bug.cgi?id=260986 Chris Samuel changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|REOPENED --- Comment #6 from Chris Samuel --- Reopening as I'm still seeing this crash and the other bug claims the issue is fixed, so this can't be a duplicate. 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 0x7f0a9c530140 (LWP 14876))] Thread 1 (Thread 0x7f0a9c530140 (LWP 14876)): [KCrash Handler] #6 0x7f09521204d8 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/akregator_mk4storage_plugin.so #7 0x7f0952120b9b in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/akregator_mk4storage_plugin.so #8 0x7f0952120bd1 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/akregator_mk4storage_plugin.so #9 0x7f0952127ae9 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/akregator_mk4storage_plugin.so #10 0x7f095212a8d3 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/akregator_mk4storage_plugin.so #11 0x7f095212b247 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/akregator_mk4storage_plugin.so #12 0x7f095212bb08 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/akregator_mk4storage_plugin.so #13 0x7f095212bbd9 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/akregator_mk4storage_plugin.so #14 0x7f0952141f9f in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/akregator_mk4storage_plugin.so #15 0x7f095214203c in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/akregator_mk4storage_plugin.so #16 0x7f0952142129 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/akregator_mk4storage_plugin.so #17 0x7f095424756f in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/akregatorpart.so #18 0x7f0954247b28 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/akregatorpart.so #19 0x7f0954247cf9 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/akregatorpart.so #20 0x7f0a9bd4e9ce in KontactInterface::Plugin::~Plugin() () from /usr/lib/x86_64-linux-gnu/libKF5KontactInterface.so.5 #21 0x7f09f67aeb36 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/kontact_akregatorplugin.so #22 0x7f09f67aeb59 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/kontact_akregatorplugin.so #23 0x7f0a9bf791b6 in Kontact::MainWindow::~MainWindow() () from /usr/lib/x86_64-linux-gnu/libkontactprivate.so.5 #24 0x7f0a9bf793e9 in Kontact::MainWindow::~MainWindow() () from /usr/lib/x86_64-linux-gnu/libkontactprivate.so.5 #25 0x7f0a99a1f470 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7f0a9a7ab4d3 in QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #27 0x7f0a9a898bab in QMainWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #28 0x7f0a9b8adad7 in KMainWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #29 0x7f0a9b8f2995 in KXmlGuiWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #30 0x7f0a9a76a46c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #31 0x7f0a9a771d34 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #32 0x7f0a999efde8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #33 0x7f0a999f255d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #34 0x7f0a99a48e53 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #35 0x7f0a92c4bfb7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #36 0x7f0a92c4c1f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #37 0x7f0a92c4c27c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #38 0x7f0a99a4847f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #39 0x7f0a999ede3a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #40 0x7f0a999f6da4 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #41 0x55bbe16883f5 in ?? () #42 0x7f0a98e0a1c1 in __libc_start_main (main=0x55bbe1687630, argc=1, argv=0x7ffc233ce968, init=, fini=, rtld_fini=, stack_end=0x7ffc233ce958) at ../csu/libc-start.c:308 #43 0x55bbe1688a0a in _start () -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 353826] Kontact crashes every time I exit
https://bugs.kde.org/show_bug.cgi?id=353826 --- Comment #4 from Chris Samuel --- Crash still happening with Kontact 5.2.3. I've even blown away my Akonadi DB in the last month to try and fix it to no avail. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 259289] Akonadi Crashes
https://bugs.kde.org/show_bug.cgi?id=259289 --- Comment #4 from Chris Samuel --- I've not seen this for a while now, I think. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 309474] akonadictl fsck : item has no RID
https://bugs.kde.org/show_bug.cgi?id=309474 Chris Samuel changed: What|Removed |Added CC||k...@csamuel.org -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 352036] Regression: kMail 5.0.0 cannot open links contained in mails
https://bugs.kde.org/show_bug.cgi?id=352036 --- Comment #15 from Chris Samuel --- (In reply to Gunter Ohrner from comment #14) > Seems to work for me now at least with the following software stack: It's sort of better, but I wouldn't consider it fixed - what is opened is actually (for example using the link for this bug in the email that was triggered by your comment): /home/chris/.cache/kioexec/krun/3830_0_show_bug.cgi rather than the proper URL, consequently the page is not rendered correctly. > I will reopen the bug if it re-appears - if any of you still see this with > the latest Frameworks and PIM releases, please notify me. I'm on the latest version from Kubuntu (via their backports PPA which was updated only a few days ago) which is: KMail 5.0.2 KDE Frameworks 5.18.0 Qt 5.5.1 (built against 5.5.1) The xcb windowing system They don't appear to have KMail 5.0.3 yet, when was that released? thanks! Chris -- 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 353826] Kontact crashes every time I exit
https://bugs.kde.org/show_bug.cgi?id=353826 --- Comment #1 from Chris Samuel --- Still happening every time with Kontact 5.0.2 & KDE Frameworks 5.15.0. -- 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 352036] Regression: kMail 5.0.0 cannot open links contained in mails
https://bugs.kde.org/show_bug.cgi?id=352036 Chris Samuel changed: What|Removed |Added CC||k...@csamuel.org --- Comment #12 from Chris Samuel --- I'm also getting this bug all the time. 'kcmshell5 componentchooser' says "in an application based on the contents of the URL" 'kcmshell5 filetypes' says it's (allegedly) using Konqueror. In my .xsession-errors I also see: KRun(0xedace10) ERROR (stat): 111 "The file or folder http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802048 does not exist." -- 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 353826] New: Kontact crashes every time I exit
https://bugs.kde.org/show_bug.cgi?id=353826 Bug ID: 353826 Summary: Kontact crashes every time I exit Product: kontact Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: k...@csamuel.org Application: kontact (5.0.1) Qt Version: 5.4.2 Operating System: Linux 4.2.0-15-generic x86_64 Distribution: Ubuntu Wily Werewolf (development branch) -- Information about the crash: - What I was doing when the application crashed: After upgrading to the development version of Kubuntu 15.10 every time I exit Kontact (in the email view, not tried any other) it crashes with the attached backtrace. 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 0x7fe03bb84880 (LWP 17692))] Thread 10 (Thread 0x7fe0335ef700 (LWP 17694)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fe05617a48b in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #2 0x7fe05617a4c9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7fe0518f96aa in start_thread (arg=0x7fe0335ef700) at pthread_create.c:333 #4 0x7fe05706ceed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 9 (Thread 0x7fdff085a700 (LWP 17695)): #0 0x7fe0570618dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fe050c7c1ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe050c7c2fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe057ba229b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fe057b4875a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fe0579663d4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fe05796b2be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fe0518f96aa in start_thread (arg=0x7fdff085a700) at pthread_create.c:333 #8 0x7fe05706ceed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 8 (Thread 0x7fdfeae09700 (LWP 17696)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fe055e885b4 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #2 0x7fe0561aa341 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7fe0518f96aa in start_thread (arg=0x7fdfeae09700) at pthread_create.c:333 #4 0x7fe05706ceed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7fdfea5e9700 (LWP 17697)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fe055e895e3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #2 0x7fe0561aa341 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7fe0518f96aa in start_thread (arg=0x7fdfea5e9700) at pthread_create.c:333 #4 0x7fe05706ceed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7fdfe9de8700 (LWP 17698)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fe055e895e3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #2 0x7fe0561aa341 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7fe0518f96aa in start_thread (arg=0x7fdfe9de8700) at pthread_create.c:333 #4 0x7fe05706ceed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7fdfe95e7700 (LWP 17699)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fe055e895e3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #2 0x7fe0561aa341 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7fe0518f96aa in start_thread (arg=0x7fdfe95e7700) at pthread_create.c:333 #4 0x7fe05706ceed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7fdfe8de6700 (LWP 17700)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fe055e895e3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #2 0x7fe0561aa341 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7fe0518f96aa in start_thread (arg=0x7fdfe8de6700) at pthread_create.c:333 #4 0x7fe05706ceed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7fdfe3fff700 (LWP 17701)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fe055e895e3 in
[Akonadi] [Bug 282160] akoandi does not delete mails from .local/share/akonadi/file_db_data
https://bugs.kde.org/show_bug.cgi?id=282160 Chris Samuel changed: What|Removed |Added CC||k...@csamuel.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 329611] Kmail does not appear to properly decode UTF-7 quoted-printable emails
https://bugs.kde.org/show_bug.cgi?id=329611 --- Comment #7 from Chris Samuel --- UTF-7 handling is still broken in 4.13. -- 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 329647] New: Kmail crashed whilst away, left examining a folder for mailing list info
https://bugs.kde.org/show_bug.cgi?id=329647 Bug ID: 329647 Summary: Kmail crashed whilst away, left examining a folder for mailing list info Classification: Unclassified Product: kontact Version: 4.12 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: k...@csamuel.org Application: kontact (4.12) KDE Platform Version: 4.12.0 Qt Version: 4.8.4 Operating System: Linux 3.11.0-14-generic x86_64 Distribution: Ubuntu 13.10 -- Information about the crash: - What I was doing when the application crashed: I had told Kmail to autodetect the linux-btrfs mailing list information and it had seemed to be taking a while to process the folder (which has a lot of email in it), so I went away for an hour or so to do some shopping. On my return it had crashed. -- 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 0x7f452e0257c0 (LWP 24332))] Thread 6 (Thread 0x7f450f9e5700 (LWP 24333)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f4528e161cd in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f4528e16209 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f452553bf6e in start_thread (arg=0x7f450f9e5700) at pthread_create.c:311 #4 0x7f452b5b19cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 5 (Thread 0x7f44cf0e2700 (LWP 24334)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f4528b56bbd in JSC::BlockAllocator::blockFreeingThreadMain() () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f4528e45a76 in WTF::wtfThreadEntryPoint(void*) () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f452553bf6e in start_thread (arg=0x7f44cf0e2700) at pthread_create.c:311 #4 0x7f452b5b19cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 4 (Thread 0x7f44ba76e700 (LWP 24348)): #0 0x7f452b5a9de3 in select () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f452bd2833b in qt_safe_select (nfds=22, fdread=0x7f44bac8, fdwrite=0x7f44bd60, fdexcept=0x7f44bff8, orig_timeout=0x7f44ba76dce0) at kernel/qcore_unix.cpp:93 #2 0x7f452bd2d904 in QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7f44b910, flags=..., timeout=0x7f44ba76dce0) at kernel/qeventdispatcher_unix.cpp:223 #3 0x7f452bd2dd02 in QEventDispatcherUNIX::processEvents (this=0x7f44b8f0, flags=...) at kernel/qeventdispatcher_unix.cpp:937 #4 0x7f452bcfc5ef in QEventLoop::processEvents (this=this@entry=0x7f44ba76ddb0, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f452bcfc8e5 in QEventLoop::exec (this=this@entry=0x7f44ba76ddb0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f452bbfb88f in QThread::exec (this=) at thread/qthread.cpp:542 #7 0x7f452bbfdf2f in QThreadPrivate::start (arg=0x1df19b0) at thread/qthread_unix.cpp:338 #8 0x7f452553bf6e in start_thread (arg=0x7f44ba76e700) at pthread_create.c:311 #9 0x7f452b5b19cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 3 (Thread 0x7f44ab018700 (LWP 24357)): #0 0x7f452b5a9de3 in select () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f452bd2837b in qt_safe_select (nfds=36, fdread=0x7f44aac8, fdwrite=0x7f44ad60, fdexcept=0x7f44aff8, orig_timeout=0x0) at kernel/qcore_unix.cpp:83 #2 0x7f452bd2d904 in QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7f44a910, flags=..., timeout=0x0) at kernel/qeventdispatcher_unix.cpp:223 #3 0x7f452bd2dd02 in QEventDispatcherUNIX::processEvents (this=0x7f44a8f0, flags=...) at kernel/qeventdispatcher_unix.cpp:937 #4 0x7f452bcfc5ef in QEventLoop::processEvents (this=this@entry=0x7f44ab017d70, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f452bcfc8e5 in QEventLoop::exec (this=this@entry=0x7f44ab017d70, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f452bbfb88f in QThread::exec (this=this@entry=0x3563300) at thread/qthread.cpp:542 #7 0x7f452bcddd13 in QInotifyFileSystemWatcherEngine::run (this=0x3563300) at io/qfilesystemwatcher_inotify.cpp:265 #8 0x7f452bbfdf2f in QThreadPrivate::start (arg=0x3563300) at thread/qthread_unix.cpp:338 #9 0x7f452553bf6e in start_thread (arg=0x7f44ab018700) at pthread_create.c:311 #10 0x7f452b5b19cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 2 (Thread 0x7f44baf6f700 (LWP 6612)): #0 0x7f452b5a9de3 in select () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f452bd2837
[kmail2] [Bug 329611] Kmail does not appear to properly decode UTF-7 quoted-printable emails
https://bugs.kde.org/show_bug.cgi?id=329611 --- Comment #2 from Chris Samuel --- Created attachment 84461 --> https://bugs.kde.org/attachment.cgi?id=84461&action=edit Sample UTF-7 encoded email As requested, an email from the btrfs mailing list encoded in UTF-7 which when viewed in Kmail looks odd. -- 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 329611] New: Kmail does not appear to properly decode UTF-7 quoted-printable emails
https://bugs.kde.org/show_bug.cgi?id=329611 Bug ID: 329611 Summary: Kmail does not appear to properly decode UTF-7 quoted-printable emails Classification: Unclassified Product: kmail2 Version: 4.12 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: k...@csamuel.org I have a contact who uses UTF-7 encoding in Evolution to stop Exchange from base64'ing his emails as vger.linux.org apparently breaks the base64 encoded emails by adding lines in plain text. Thunderbird displays his messages correctly but Kmail shows his > quote character as the encoded form of +AD4- instead (and the same for any other quoted-printable parts). His messages are labelled as: Content-Type: text/plain; charset="utf-7" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 and are otherwise unremarkable. Reproducible: Always Steps to Reproduce: 1. Get an email from someone in utf-7 (directly, or via a mailing list). Actual Results: Looks odd, doesn't display correctly. Expected Results: It should be decoded from UTF-7 quoted-printable. -- 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 329496] New: Kontact crashed on exit
https://bugs.kde.org/show_bug.cgi?id=329496 Bug ID: 329496 Summary: Kontact crashed on exit Classification: Unclassified Product: kontact Version: 4.12 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: k...@csamuel.org Application: kontact (4.12) KDE Platform Version: 4.12.0 Qt Version: 4.8.4 Operating System: Linux 3.11.0-14-generic x86_64 Distribution: Ubuntu 13.10 -- Information about the crash: - What I was doing when the application crashed: I was quiting Kontact and it crashed. It doesn't happen all the time, but this was after searching a folder list. -- 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 0x7f7dc42da7c0 (LWP 7443))] Thread 6 (Thread 0x7f7da5678700 (LWP 7444)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f7dbf0cb1cd in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f7dbf0cb209 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f7dbb7f0f6e in start_thread (arg=0x7f7da5678700) at pthread_create.c:311 #4 0x7f7dc18669cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 5 (Thread 0x7f7d64d75700 (LWP 7445)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f7dbee0bbbd in JSC::BlockAllocator::blockFreeingThreadMain() () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f7dbf0faa76 in WTF::wtfThreadEntryPoint(void*) () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f7dbb7f0f6e in start_thread (arg=0x7f7d64d75700) at pthread_create.c:311 #4 0x7f7dc18669cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 4 (Thread 0x7f7d47fff700 (LWP 7461)): #0 0x7f7dc185ede3 in select () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f7dc1fdd33b in qt_safe_select (nfds=23, fdread=0x7f7d4ac8, fdwrite=0x7f7d4d60, fdexcept=0x7f7d4ff8, orig_timeout=0x7f7d47ffece0) at kernel/qcore_unix.cpp:93 #2 0x7f7dc1fe2904 in QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7f7d4910, flags=..., timeout=0x7f7d47ffece0) at kernel/qeventdispatcher_unix.cpp:223 #3 0x7f7dc1fe2d02 in QEventDispatcherUNIX::processEvents (this=0x7f7d48f0, flags=...) at kernel/qeventdispatcher_unix.cpp:937 #4 0x7f7dc1fb15ef in QEventLoop::processEvents (this=this@entry=0x7f7d47ffedb0, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f7dc1fb18e5 in QEventLoop::exec (this=this@entry=0x7f7d47ffedb0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f7dc1eb088f in QThread::exec (this=) at thread/qthread.cpp:542 #7 0x7f7dc1eb2f2f in QThreadPrivate::start (arg=0x1f011a0) at thread/qthread_unix.cpp:338 #8 0x7f7dbb7f0f6e in start_thread (arg=0x7f7d47fff700) at pthread_create.c:311 #9 0x7f7dc18669cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 3 (Thread 0x7f7d37990700 (LWP 7498)): #0 0x7f7dc185ede3 in select () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f7dc1fdd37b in qt_safe_select (nfds=41, fdread=0x7f7d3ac8, fdwrite=0x7f7d3d60, fdexcept=0x7f7d3ff8, orig_timeout=0x0) at kernel/qcore_unix.cpp:83 #2 0x7f7dc1fe2904 in QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7f7d3910, flags=..., timeout=0x0) at kernel/qeventdispatcher_unix.cpp:223 #3 0x7f7dc1fe2d02 in QEventDispatcherUNIX::processEvents (this=0x7f7d38f0, flags=...) at kernel/qeventdispatcher_unix.cpp:937 #4 0x7f7dc1fb15ef in QEventLoop::processEvents (this=this@entry=0x7f7d3798fd70, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f7dc1fb18e5 in QEventLoop::exec (this=this@entry=0x7f7d3798fd70, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f7dc1eb088f in QThread::exec (this=this@entry=0x90d3c10) at thread/qthread.cpp:542 #7 0x7f7dc1f92d13 in QInotifyFileSystemWatcherEngine::run (this=0x90d3c10) at io/qfilesystemwatcher_inotify.cpp:265 #8 0x7f7dc1eb2f2f in QThreadPrivate::start (arg=0x90d3c10) at thread/qthread_unix.cpp:338 #9 0x7f7dbb7f0f6e in start_thread (arg=0x7f7d37990700) at pthread_create.c:311 #10 0x7f7dc18669cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 2 (Thread 0x7f7d55eb3700 (LWP 14900)): #0 0x7f7dc185ede3 in select () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f7dc1fdd37b in qt_safe_select (nfds=21, fdread=0x7f7d48000aa8, fdwrite=0x7f7d48000d40, fdexcept=0x7f7d48000fd8, orig_timeout=0x0) at kernel/qcore_unix.cpp:83 #2 0x7f7dc1fe2904 in QEventDispatcherUNIXPrivate::doSele
[Akonadi] [Bug 318224] Tries to insert existing entries into database
https://bugs.kde.org/show_bug.cgi?id=318224 Chris Samuel changed: What|Removed |Added CC||k...@csamuel.org --- Comment #5 from Chris Samuel --- I am getting: ARY' QMYSQL3: Unable to execute statement" Error during executing query "INSERT INTO CollectionPimItemRelation (Collection_id, PimItem_id) VALUES (:0, :1)" : "Duplicate entry '1116-323043' for key 'PRIMARY' QMYSQL3: Unable to execute statement" Error during executing query "INSERT INTO CollectionPimItemRelation (Collection_id, PimItem_id) VALUES (:0, :1)" : "Duplicate entry '1116-323207' for key 'PRIMARY' QMYSQL3: Unable to execute statement" Error during executing query "INSERT INTO CollectionPimItemRelation (Collection_id, PimItem_id) VALUES (:0, :1)" : "Duplicate entry '1116-323405' for key 'PRIMARY' QMYSQL3: Unable to execute statement" Error during executing query "INSERT INTO CollectionPimItemRelation (Collection_id, PimItem_id) VALUES (:0, :1)" : "Duplicate entry '1116-323483' for key 'PRIMARY' QMYSQL3: Unable to execute statement" Error during executing query "INSERT INTO CollectionPimItemRelation (Collection_id, PimItem_id) VALUES (:0, :1)" : "Duplicate entry '1116-323484' for key 'PRIMARY' QMYSQL3: Unable to execute statement" Error during executing query "INSERT INTO CollectionPimItemRelation (Collection_id, PimItem_id) VALUES (:0, :1)" : "Duplicate entry '1116-323485' for key 'PRIMARY' QMYSQL3: Unable to execute statement" Error during executing query "INSERT INTO CollectionPimItemRelation (Collection_id, PimItem_id) VALUES (:0, :1)" : "Duplicate entry '1116-323486' for key 'PRIMARY' QMYSQL3: Unable to execute statement" Error during executing query "INSERT INTO CollectionPimItemRelation (Collection_id, PimItem_id) VALUES (:0, :1)" : "Duplicate entry '1116-324801' for key 'PRIMARY' QMYSQL3: Unable to execute statement" Error during executing query "INSERT INTO CollectionPimItemRelation (Collection_id, PimItem_id) VALUES (:0, :1)" : "Duplicate entry '1116-324939' for key 'PRIMARY' QMYSQL3: Unable to execute statement" Error during executing query "INSERT INTO CollectionPimItemRelation (Collection_id, PimItem_id) VALUES (:0, :1)" : "Duplicate entry '1116-325025' for key 'PRIMARY' QMYSQL3: Unable to execute statement" If in Akonadi Console DB Console I execute: SELECT collectionTable.name, resourceTable.name FROM collectionTable INNER JOIN resourceTable ON collectionTable.resourceId = resourceTable.id WHERE collectionTable.id = 1116; I see: 1 Last Search akonadi_search_resource This is with KDE 4.12 from the Kubuntu KDE backports PPA. Akonadi Console Version 0.99 Using KDE Development Platform 4.12.0 -- 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
[akregator] [Bug 306922] Kontact (akregator) crashes on quit every time.
https://bugs.kde.org/show_bug.cgi?id=306922 --- Comment #5 from Chris Samuel --- Created attachment 81382 --> https://bugs.kde.org/attachment.cgi?id=81382&action=edit New crash information added by DrKonqi kontact (4.11 rc1) on KDE Platform 4.10.95 using Qt 4.8.4 - What I was doing when the application crashed: Exiting Kontact from KDE 4.11 RC1 (4.10.95). -- Backtrace (Reduced): #6 GetAt (nIndex=458752, this=0x9f0dcb0) at ../../../../akregator/plugins/mk4storage/metakit/src/univ.inl:54 #7 c4_Column::CopyData (this=this@entry=0x9f0dcb0, to_=1879048279, from_=0, count_=count_@entry=-1879048279) at ../../../../akregator/plugins/mk4storage/metakit/src/column.cpp:282 #8 0x7f4b74cfef59 in c4_Column::FinishSlack (this=this@entry=0x9f0dcb0) at ../../../../akregator/plugins/mk4storage/metakit/src/column.cpp:680 #9 0x7f4b74cff2f1 in c4_Column::~c4_Column (this=0x9f0dcb0, __in_chrg=) at ../../../../akregator/plugins/mk4storage/metakit/src/column.cpp:84 #10 0x7f4b74d0592f in c4_FormatB::~c4_FormatB (this=0x9f0dc00, __in_chrg=) at ../../../../akregator/plugins/mk4storage/metakit/src/format.cpp:297 -- 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
[akregator] [Bug 306922] Kontact (akregator) crashes on quit every time.
https://bugs.kde.org/show_bug.cgi?id=306922 --- Comment #4 from Chris Samuel --- Created attachment 80230 --> https://bugs.kde.org/attachment.cgi?id=80230&action=edit New crash information added by DrKonqi kontact (4.10.3) on KDE Platform 4.10.3 using Qt 4.8.4 - What I was doing when the application crashed: Exiting Kontact (as usual). This crash is with KDE 4.10.3. -- Backtrace (Reduced): #6 GetAt (nIndex=458752, this=0x140a820) at ../../../../akregator/plugins/mk4storage/metakit/src/univ.inl:54 #7 c4_Column::CopyData (this=this@entry=0x140a820, to_=1879048279, from_=0, count_=count_@entry=-1879048279) at ../../../../akregator/plugins/mk4storage/metakit/src/column.cpp:282 #8 0x7fb3ce05bf59 in c4_Column::FinishSlack (this=this@entry=0x140a820) at ../../../../akregator/plugins/mk4storage/metakit/src/column.cpp:680 #9 0x7fb3ce05c2f1 in c4_Column::~c4_Column (this=0x140a820, __in_chrg=) at ../../../../akregator/plugins/mk4storage/metakit/src/column.cpp:84 #10 0x7fb3ce06292f in c4_FormatB::~c4_FormatB (this=0x140a770, __in_chrg=) at ../../../../akregator/plugins/mk4storage/metakit/src/format.cpp:297 -- 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
[akregator] [Bug 306922] Kontact (akregator) crashes on quit every time.
https://bugs.kde.org/show_bug.cgi?id=306922 Chris Samuel changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=315601 -- 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 306922] Kontact (akregator) crashes on quit every time.
https://bugs.kde.org/show_bug.cgi?id=306922 --- Comment #3 from Chris Samuel --- Created attachment 79511 --> https://bugs.kde.org/attachment.cgi?id=79511&action=edit New crash information added by DrKonqi kontact (4.10.2) on KDE Platform 4.10.2 using Qt 4.8.4 - What I was doing when the application crashed: Exiting Kontact. Always crashes. Adding a new backtrace. -- Backtrace (Reduced): #6 GetAt (nIndex=458752, this=0x106e510) at ../../../../akregator/plugins/mk4storage/metakit/src/univ.inl:54 #7 c4_Column::CopyData (this=this@entry=0x106e510, to_=1879048279, from_=0, count_=count_@entry=-1879048279) at ../../../../akregator/plugins/mk4storage/metakit/src/column.cpp:282 #8 0x7fc8785abf59 in c4_Column::FinishSlack (this=this@entry=0x106e510) at ../../../../akregator/plugins/mk4storage/metakit/src/column.cpp:680 #9 0x7fc8785ac2f1 in c4_Column::~c4_Column (this=0x106e510, __in_chrg=) at ../../../../akregator/plugins/mk4storage/metakit/src/column.cpp:84 #10 0x7fc8785b292f in c4_FormatB::~c4_FormatB (this=0x106e460, __in_chrg=) at ../../../../akregator/plugins/mk4storage/metakit/src/format.cpp:297 -- 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 306922] Kontact (akregator) crashes on quit every time.
https://bugs.kde.org/show_bug.cgi?id=306922 Chris Samuel changed: What|Removed |Added CC||k...@csamuel.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
[kontact] [Bug 315601] Kmail crashed when exited.
https://bugs.kde.org/show_bug.cgi?id=315601 --- Comment #2 from Chris Samuel --- Created attachment 79510 --> https://bugs.kde.org/attachment.cgi?id=79510&action=edit New crash information added by DrKonqi kontact (4.10.2) on KDE Platform 4.10.2 using Qt 4.8.4 - What I was doing when the application crashed: Exiting Kontact. Yet another backtrace from my always-crashing-on-exit experience of Kontact. :-( -- Backtrace (Reduced): #6 isEmpty (this=this@entry=0x90) at ../../include/QtCore/../../src/corelib/tools/qhash.h:297 #7 QHash::remove (this=this@entry=0x90, akey=...) at ../../include/QtCore/../../src/corelib/tools/qhash.h:786 #8 0x7f2a5e383884 in QAbstractItemModelPrivate::removePersistentIndexData (this=0x0, data=data@entry=0x2673280) at kernel/qabstractitemmodel.cpp:542 #9 0x7f2a5e383af9 in QPersistentModelIndexData::destroy (data=0x2673280) at kernel/qabstractitemmodel.cpp:83 #10 0x7f2a5e383c1f in QPersistentModelIndex::~QPersistentModelIndex (this=0xf1f2540, __in_chrg=) at kernel/qabstractitemmodel.cpp:155 -- 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 315601] Kmail crashed when exited.
https://bugs.kde.org/show_bug.cgi?id=315601 Chris Samuel changed: What|Removed |Added CC||k...@csamuel.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 306922] New: Kontact (akregator) crashes on quit every time.
https://bugs.kde.org/show_bug.cgi?id=306922 Bug ID: 306922 Severity: crash Version: 4.9.1 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kontact (akregator) crashes on quit every time. Classification: Unclassified OS: Linux Reporter: k...@csamuel.org Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.9.1) KDE Platform Version: 4.9.1 Qt Version: 4.8.2 Operating System: Linux 3.2.0-30-generic x86_64 Distribution: Ubuntu 12.04.1 LTS -- Information about the crash: Every time I quit Kontact the Akregator part seems to SEGV. I suspect this is related to bug 260986 but given this has been going on since 4.7 and the backtrace isn't completely identical I thought I should file a new bug just in case. - What I was doing when the application crashed: Quitting Kontact. 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 0x7f98da88f7c0 (LWP 30374))] Thread 6 (Thread 0x7f98be40c700 (LWP 30375)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f98d7098dec in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f98d7098f19 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f98d254be9a in start_thread (arg=0x7f98be40c700) at pthread_create.c:308 #4 0x7f98d7dca4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 5 (Thread 0x7f98bdb0b700 (LWP 30376)): #0 0x7f98d7dc3823 in select () at ../sysdeps/unix/syscall-template.S:82 #1 0x7f98d853c7ef in qt_safe_select (nfds=13, fdread=0x7f98b8000ac8, fdwrite=0x7f98b8000d60, fdexcept=0x7f98b8000ff8, orig_timeout=0x7f98bdb0acf0) at kernel/qcore_unix.cpp:93 #2 0x7f98d8541c92 in QEventDispatcherUNIXPrivate::doSelect (this=0x7f98b8000910, flags=..., timeout=0x7f98bdb0acf0) at kernel/qeventdispatcher_unix.cpp:223 #3 0x7f98d8542183 in QEventDispatcherUNIX::processEvents (this=0x7f98b80008f0, flags=...) at kernel/qeventdispatcher_unix.cpp:926 #4 0x7f98d850ee42 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f98d850f097 in QEventLoop::exec (this=0x7f98bdb0adc0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f98d840e057 in QThread::exec (this=) at thread/qthread.cpp:501 #7 0x7f98d841107b in QThreadPrivate::start (arg=0x25cb710) at thread/qthread_unix.cpp:307 #8 0x7f98d254be9a in start_thread (arg=0x7f98bdb0b700) at pthread_create.c:308 #9 0x7f98d7dca4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #10 0x in ?? () Thread 4 (Thread 0x7f9870e16700 (LWP 30380)): #0 0x7f98d7dc3823 in select () at ../sysdeps/unix/syscall-template.S:82 #1 0x7f98d853c846 in qt_safe_select (nfds=21, fdread=0x7f986c000ac8, fdwrite=0x7f986c000d60, fdexcept=0x7f986c000ff8, orig_timeout=) at kernel/qcore_unix.cpp:83 #2 0x7f98d8541c92 in QEventDispatcherUNIXPrivate::doSelect (this=0x7f986c000910, flags=..., timeout=0x0) at kernel/qeventdispatcher_unix.cpp:223 #3 0x7f98d8542183 in QEventDispatcherUNIX::processEvents (this=0x7f986c0008f0, flags=...) at kernel/qeventdispatcher_unix.cpp:926 #4 0x7f98d850ee42 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f98d850f097 in QEventLoop::exec (this=0x7f9870e15d90, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f98d840e057 in QThread::exec (this=) at thread/qthread.cpp:501 #7 0x7f98d84eeb4f in QInotifyFileSystemWatcherEngine::run (this=0x2d4c650) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x7f98d841107b in QThreadPrivate::start (arg=0x2d4c650) at thread/qthread_unix.cpp:307 #9 0x7f98d254be9a in start_thread (arg=0x7f9870e16700) at pthread_create.c:308 #10 0x7f98d7dca4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 3 (Thread 0x7f9860c06700 (LWP 30596)): #0 0x7f98d7dc3823 in select () at ../sysdeps/unix/syscall-template.S:82 #1 0x7f98d853c846 in qt_safe_select (nfds=29, fdread=0x7f985c000a78, fdwrite=0x7f985c000d10, fdexcept=0x7f985c000fa8, orig_timeout=) at kernel/qcore_unix.cpp:83 #2 0x7f98d8541c92 in QEventDispatcherUNIXPrivate::doSelect (this=0x7f985c0008c0, flags=..., timeout=0x0) at kernel/qeventdispatcher_unix.cpp:223 #3 0x7f98d8542183 in QEventDispatcherUNIX::processEvents (this=0x7f985c005b30, flags=...) at kernel/qeventdispatcher_unix.cpp:926 #4 0x7f98d850ee42 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f98d850f097 in QEventLoop::exec (this=0x7f9860c05d90, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f98d840e057 in QThread::exec (th
[Bug 260986] Akregator crashes on KDE shutdown
https://bugs.kde.org/show_bug.cgi?id=260986 --- Comment #3 from Chris Samuel --- I am still getting this crash in KDE 4.9.1. -- 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 276635] In certain KMail2 setups filters dont get applied
https://bugs.kde.org/show_bug.cgi?id=276635 Chris Samuel changed: What|Removed |Added CC||k...@csamuel.org --- Comment #10 from Chris Samuel --- Version: 4.9.1 Packaged: Kubuntu PPA for 12.04 Package version: 4:4.9.1-0ubuntu1~ubuntu12.04.1~ppa2 I've just taken the plunge and upgraded from 11.04 through 11.10 to 12.04 and then to 4.9.1 in the PPA (last logged in 11.04, then logged in to 4.9.1 in 12.04, no intermediate logins). I didn't use the migration tool but instead added my mixed Maildir/mbox folders which seems fine. However, it appears that kmail2 filters (imported from the kmail1 kmailrc) do not seem to get applied to my IMAP folder (with disconnected mode enabled), looking at the filter log. I do see log messages (and the filters get correctly applied) if I select all messages and apply the filters by hand to them. But when an email appears that should be filtered it just sits in the IMAP inbox and does not get moved, and no log messages appear in the filter log. Please let me know if you need any extra information! -- 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 283563] KMail2 migration failed
https://bugs.kde.org/show_bug.cgi?id=283563 --- Comment #22 from Chris Samuel --- Appears not to be fixed in KDE 4.8, at least according to the latest update on the Kubuntu LaunchPad bug entry for this problem: https://bugs.launchpad.net/bugs/857828 # Just incredible that is isn't fixed with a new LTS release. # # My company just decided to stop using KDE due to bosses finding it # unacceptable that people loses emails and configurations due to just # a update. Back to windows. -- 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 283563] KMail2 migration failed
https://bugs.kde.org/show_bug.cgi?id=283563 Chris Samuel changed: What|Removed |Added CC||k...@csamuel.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 128357] Crash after hovering the mouse over an URL [KMMessage::bodyPart, AttachmentURLHandler::statusBarMessage, KMail::URLHandlerManager::statusBarMessage, KMReaderWin::slotUrlOn]
https://bugs.kde.org/show_bug.cgi?id=128357 --- Comment #54 from Chris Samuel 2011-02-14 12:17:07 --- 5.5 years old, 38 duplicates and still marked as "NEW" and with a priority of "NORMAL" ? Would everyone affected by this please vote for this bug if you feel it's worth noticing by the Kmail developers please ? -- 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 266177] New: Kontact (kmail) crashed when replying to email in IMAP folder
https://bugs.kde.org/show_bug.cgi?id=266177 Summary: Kontact (kmail) crashed when replying to email in IMAP folder Product: kontact Version: unspecified Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: k...@csamuel.org Application: kontact (4.4.9) KDE Platform Version: 4.6.00 (4.6.0) Qt Version: 4.7.0 Operating System: Linux 2.6.37-020637-generic x86_64 Distribution: Ubuntu 10.10 -- Information about the crash: - What I was doing when the application crashed: Replying to an email in an IMAP folder, when I hit send I got the segmentation fault. I'm also getting crashes on exit, but I don't have a backtrace to hand to compare with this (will try and reproduce). I've selected an existing bug as a potential duplicate, the stack trace looks very similar but I'm not completely convinced it's the same issue. The crash can be reproduced some of the time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0x7fad81656780 (LWP 4974))] Thread 2 (Thread 0x7fad5ae3c700 (LWP 4977)): #0 0x7fad7e5d42c3 in select () at ../sysdeps/unix/syscall-template.S:82 #1 0x7fad7ed1076e in qt_safe_select (nfds=29, fdread=0xaa62a0, fdwrite=0xaa6538, fdexcept=0xaa67d0, orig_timeout=0x0) at kernel/qcore_unix.cpp:82 #2 0x7fad7ed15beb in QEventDispatcherUNIXPrivate::doSelect (this=0xaa60e0, flags=, timeout=) at kernel/qeventdispatcher_unix.cpp:219 #3 0x7fad7ed1681b in QEventDispatcherUNIX::processEvents (this=0x2a2c780, flags=) at kernel/qeventdispatcher_unix.cpp:919 #4 0x7fad7ece5a02 in QEventLoop::processEvents (this=, flags=) at kernel/qeventloop.cpp:149 #5 0x7fad7ece5dec in QEventLoop::exec (this=0x7fad5ae3bd90, flags=) at kernel/qeventloop.cpp:201 #6 0x7fad7ebf02fd in QThread::exec (this=) at thread/qthread.cpp:490 #7 0x7fad7ecc55f8 in QInotifyFileSystemWatcherEngine::run (this=0x2341ff0) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x7fad7ebf327e in QThreadPrivate::start (arg=0x2341ff0) at thread/qthread_unix.cpp:266 #9 0x7fad7810d971 in start_thread (arg=) at pthread_create.c:304 #10 0x7fad7e5db92d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 1 (Thread 0x7fad81656780 (LWP 4974)): [KCrash Handler] #6 0x7fad62d69181 in c_str (aDwBodyPart=0x32a3570, aPart=0x78c5488, withBody=true) at ../../mimelib/mimelib/string.h:618 #7 partId (aDwBodyPart=0x32a3570, aPart=0x78c5488, withBody=true) at ../../mimelib/mimelib/msgcmp.h:259 #8 KMMessage::bodyPart (aDwBodyPart=0x32a3570, aPart=0x78c5488, withBody=true) at ../../kmail/kmmessage.cpp:2677 #9 0x7fad63090701 in msgPart (this=, url=..., w=) at ../../kmail/partNode.h:103 #10 (anonymous namespace)::AttachmentURLHandler::statusBarMessage (this=, url=..., w=) at ../../kmail/urlhandlermanager.cpp:688 #11 0x7fad6308f1d4 in KMail::URLHandlerManager::statusBarMessage (this=0x152a7c0, url=..., w=0x1443240) at ../../kmail/urlhandlermanager.cpp:355 #12 0x7fad62e57a54 in KMReaderWin::slotUrlOn (this=0x1443240, aUrl=) at ../../kmail/kmreaderwin.cpp:1966 #13 0x7fad62e59a7e in KMReaderWin::qt_metacall (this=0x1443240, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fffc4c18760) at ./kmreaderwin.moc:189 #14 0x7fad7ecfeb27 in QMetaObject::activate (sender=0x1452bf0, m=, local_signal_index=, argv=0x1010e90) at kernel/qobject.cpp:3280 #15 0x7fad7daf8da2 in KHTMLPart::onURL (this=0x7fad7e873e40, _t1=) at ./khtml_part.moc:408 #16 0x7fad7db1c0c3 in KHTMLPart::overURL (this=0x1452bf0, url=..., target=...) at ../../khtml/khtml_part.cpp:3508 #17 0x7fad7db1e193 in KHTMLPart::handleMouseMoveEventOver (this=0x1452bf0, event=) at ../../khtml/khtml_part.cpp:6478 #18 0x7fad7db1e56b in KHTMLPart::khtmlMouseMoveEvent (this=0x1452bf0, event=0x7fffc4c19b70) at ../../khtml/khtml_part.cpp:6526 #19 0x7fad7ecf8c3c in QObject::event (this=0x1452bf0, e=) at kernel/qobject.cpp:1250 #20 0x7fad7f6c8fdc in QApplicationPrivate::notify_helper (this=0x9901e0, receiver=0x1452bf0, e=0x7fffc4c19b70) at kernel/qapplication.cpp:4396 #21 0x7fad7f6ceaed in QApplication::notify (this=0x7fffc4c1b590, receiver=0x1452bf0, e=0x7fffc4c19b70) at kernel/qapplication.cpp:4277 #22 0x7fad80458a36 in KApplication::notify (this=0x7fffc4c1b590, receiver=0x1452bf0, event=0x7fffc4c19b70) at ../../kdeui/kernel/kapplication.cpp:311 #23 0x7fad7ece6cdc in QCoreApplication::notifyInternal (this=0x7fffc4c1b590, receiver=0x1452bf0, event=0x7fffc4c19b70) at kernel/qcoreapplication.cpp:732 #24 0x7fad7daf1ca2 in sendEvent (this=0x1454520, _mouse=) at /usr/include/qt4/QtCore/qcoreapplication.h:215 #25 KHTMLView::mouseMoveEvent (this=0x1454520, _mouse=) at ../../khtml/khtmlview.cpp:1539 #26 0x7fad7f71ecab in QWid
[Bug 263735] New: Kontact crashes on exit
https://bugs.kde.org/show_bug.cgi?id=263735 Summary: Kontact crashes on exit Product: kontact Version: unspecified Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: k...@csamuel.org Application: kontact (4.4.9) KDE Platform Version: 4.5.95 (4.6 RC2) Qt Version: 4.7.0 Operating System: Linux 2.6.37-020637-generic x86_64 Distribution: Ubuntu 10.10 -- Information about the crash: - What I was doing when the application crashed: Recently Kontact has started to segfault on exit, this happens every time I quit it. I've got Kontact setup to start with Akregator by default, so it may well be related to the the report that DrKonqui has suggested. This is on Ubuntu 10.10 with 4.6.0 RC2 from the Kubuntu KDE PPA. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0x7f6a9f610780 (LWP 7244))] Thread 4 (Thread 0x7f6a78851700 (LWP 7247)): #0 0x7f6a9c58f2c3 in select () at ../sysdeps/unix/syscall-template.S:82 #1 0x7f6a9cccb76e in qt_safe_select (nfds=24, fdread=0x1480170, fdwrite=0x1480408, fdexcept=0x14806a0, orig_timeout=0x0) at kernel/qcore_unix.cpp:82 #2 0x7f6a9ccd0beb in QEventDispatcherUNIXPrivate::doSelect (this=0x147ffb0, flags=, timeout=) at kernel/qeventdispatcher_unix.cpp:219 #3 0x7f6a9ccd181b in QEventDispatcherUNIX::processEvents (this=0x260c700, flags=) at kernel/qeventdispatcher_unix.cpp:919 #4 0x7f6a9cca0a02 in QEventLoop::processEvents (this=, flags=) at kernel/qeventloop.cpp:149 #5 0x7f6a9cca0dec in QEventLoop::exec (this=0x7f6a78850d90, flags=) at kernel/qeventloop.cpp:201 #6 0x7f6a9cbab2fd in QThread::exec (this=) at thread/qthread.cpp:490 #7 0x7f6a9cc805f8 in QInotifyFileSystemWatcherEngine::run (this=0x2348720) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x7f6a9cbae27e in QThreadPrivate::start (arg=0x2348720) at thread/qthread_unix.cpp:266 #9 0x7f6a960b8971 in start_thread (arg=) at pthread_create.c:304 #10 0x7f6a9c59692d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 3 (Thread 0x7f6a77d4f700 (LWP 27097)): #0 0x7f6a9c58f2c3 in select () at ../sysdeps/unix/syscall-template.S:82 #1 0x7f6a9cccb76e in qt_safe_select (nfds=109, fdread=0x7a57010, fdwrite=0x7a572a8, fdexcept=0x7a57540, orig_timeout=0x0) at kernel/qcore_unix.cpp:82 #2 0x7f6a9ccd0beb in QEventDispatcherUNIXPrivate::doSelect (this=0x7a56e50, flags=, timeout=) at kernel/qeventdispatcher_unix.cpp:219 #3 0x7f6a9ccd181b in QEventDispatcherUNIX::processEvents (this=0x619f9c0, flags=) at kernel/qeventdispatcher_unix.cpp:919 #4 0x7f6a9cca0a02 in QEventLoop::processEvents (this=, flags=) at kernel/qeventloop.cpp:149 #5 0x7f6a9cca0dec in QEventLoop::exec (this=0x7f6a77d4ed90, flags=) at kernel/qeventloop.cpp:201 #6 0x7f6a9cbab2fd in QThread::exec (this=) at thread/qthread.cpp:490 #7 0x7f6a9cc805f8 in QInotifyFileSystemWatcherEngine::run (this=0x7527370) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x7f6a9cbae27e in QThreadPrivate::start (arg=0x7527370) at thread/qthread_unix.cpp:266 #9 0x7f6a960b8971 in start_thread (arg=) at pthread_create.c:304 #10 0x7f6a9c59692d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 2 (Thread 0x7f6a7751d700 (LWP 27098)): #0 0x7f6a9c58f2c3 in select () at ../sysdeps/unix/syscall-template.S:82 #1 0x7f6a9cccb76e in qt_safe_select (nfds=117, fdread=0x6e2f7b0, fdwrite=0x6e2fa48, fdexcept=0x6e2fce0, orig_timeout=0x0) at kernel/qcore_unix.cpp:82 #2 0x7f6a9ccd0beb in QEventDispatcherUNIXPrivate::doSelect (this=0x6e2f5f0, flags=, timeout=) at kernel/qeventdispatcher_unix.cpp:219 #3 0x7f6a9ccd181b in QEventDispatcherUNIX::processEvents (this=0x6e2ea40, flags=) at kernel/qeventdispatcher_unix.cpp:919 #4 0x7f6a9cca0a02 in QEventLoop::processEvents (this=, flags=) at kernel/qeventloop.cpp:149 #5 0x7f6a9cca0dec in QEventLoop::exec (this=0x7f6a7751cdb0, flags=) at kernel/qeventloop.cpp:201 #6 0x7f6a9cbab2fd in QThread::exec (this=) at thread/qthread.cpp:490 #7 0x7f6a91629b6c in Herqq::Upnp::HControlPointThread::run() () from /usr/lib/libHUpnp.so.0 #8 0x7f6a9cbae27e in QThreadPrivate::start (arg=0x4954900) at thread/qthread_unix.cpp:266 #9 0x7f6a960b8971 in start_thread (arg=) at pthread_create.c:304 #10 0x7f6a9c59692d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 1 (Thread 0x7f6a9f610780 (LWP 7244)): [KCrash Handler] #6 c4_Column::CopyData (this=0x2658110, to_=1879048279, from_=0, count_=-1879048279) at ../../../../akregator/plugins/mk4storage/metakit/src/column.cpp:283 #7 0x7f6a7a8ca487 in c4_Column::Fin
[Bug 261593] Frequent plasma-desktop crashes [KCalCore::IncidenceBase::isReadOnly, CalendarSupport::Calendar::Private::dataChanged]
https://bugs.kde.org/show_bug.cgi?id=261593 --- Comment #6 from Chris Samuel 2011-01-08 07:22:47 --- Created an attachment (id=55725) --> (http://bugs.kde.org/attachment.cgi?id=55725) New crash information added by DrKonqi plasma-desktop (0.4) on KDE Platform 4.5.95 (4.6 RC2) using Qt 4.7.0 - What I was doing when the application crashed: Came home a few hours after logging into 4.6.0 RC2 to find this crash again. Originally reported as bug #261759 which was marked as a duplicate of this. -- Backtrace (Reduced): #6 KCalCore::IncidenceBase::isReadOnly (this=0x0) at ../../kcalcore/incidencebase.cpp:286 #7 0x7f3738d05f23 in CalendarSupport::Calendar::Private::updateItem (this=0x1422a70, item=, mode=) at ../../../../../plasma/generic/dataengines/calendar/akonadi/calendar.cpp:222 #8 0x7f3738d08e9b in CalendarSupport::Calendar::Private::dataChanged (this=, topLeft=, bottomRight=) at ../../../../../plasma/generic/dataengines/calendar/akonadi/calendar.cpp:157 #9 0x7f3738ce9f0c in CalendarSupport::Calendar::Private::qt_metacall (this=0x1422a70, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fffaa2318b0) at moc_calendar_p.cpp:155 [...] #11 0x7f375a51e2c7 in QAbstractItemModel::dataChanged (this=0x0, _t1=, _t2=) at .moc/release-shared/moc_qabstractitemmodel.cpp:148 -- 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 259289] Akonadi Crashes
https://bugs.kde.org/show_bug.cgi?id=259289 --- Comment #2 from Chris Samuel 2010-12-11 08:43:14 --- These DrKonqui messages constantly appear as Akonadi tries to restart the failed service indefinitely. Only way to stop them is to disable Akonadi. -- 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 259289] Akonadi Crashes
https://bugs.kde.org/show_bug.cgi?id=259289 --- Comment #1 from Chris Samuel 2010-12-11 08:35:12 --- Created an attachment (id=54414) --> (http://bugs.kde.org/attachment.cgi?id=54414) New crash information added by DrKonqi akonadi_kcal_resource (0.1) on KDE Platform 4.5.85 (4.6 Beta2) using Qt 4.7.0 - What I was doing when the application crashed: Logged in for the first time after upgrading from KDE 4.5.4 to 4.6.0 beta 2 via the Kubuntu beta PPA. - Unusual behavior I noticed: I got two of these backtraces from Akonadi, the other one is almost identical *except* frame #16 is: #16 main (argc=, argv=) at ../../../resources/vcard/vcardresource.cpp:189 -- Backtrace (Reduced): #12 0x7f5429a4df3d in QEventLoop::exec (this=, flags=) at kernel/qeventloop.cpp:214 #13 0x7f5429a51ebb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009 #14 0x7f542a0d0ac2 in Akonadi::ResourceBase::init (r=0x1457600) at ../../akonadi/resourcebase.cpp:283 #15 0x004093d8 in init (argc=, argv=) at /usr/include/akonadi/resourcebase.h:188 #16 main (argc=, argv=) at ../../../resources/kcal/kcalresource.cpp:690 -- 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 259289] Akonadi Crashes
https://bugs.kde.org/show_bug.cgi?id=259289 Chris Samuel changed: What|Removed |Added CC||k...@csamuel.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 227770] New: kmail crash dragging multiple emails from inbox to a folder
https://bugs.kde.org/show_bug.cgi?id=227770 Summary: kmail crash dragging multiple emails from inbox to a folder Product: kontact Version: unspecified Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: k...@csamuel.org Application: kontact (4.4) KDE Platform Version: 4.4.00 (KDE 4.4.0) Qt Version: 4.6.1 Operating System: Linux 2.6.33-020633rc8-generic x86_64 Distribution: Ubuntu 9.10 -- Information about the crash: I had selected all of a filtered list of emails, marked them as new and then was dragging them to a folder, on releasing the mouse button kmail/kontact crashed. I suspect this is a duplicate of 223245. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #5 0x7f936f4438a4 in MessageList::Core::Item::parent() const () from /usr/lib/libmessagelist.so.4 #6 0x7f936f456da8 in MessageList::Core::Model::index(MessageList::Core::Item*, int) const () from /usr/lib/libmessagelist.so.4 #7 0x7f936f456f0a in MessageList::Core::Model::parent(QModelIndex const&) const () from /usr/lib/libmessagelist.so.4 #8 0x7f93872872ad in QModelIndex::parent (this=0x3b8cd10, index=) at ../../include/QtCore/../../src/corelib/kernel/qabstractitemmodel.h:389 #9 QTreeView::indexRowSizeHint (this=0x3b8cd10, index=) at itemviews/qtreeview.cpp:2823 #10 0x7f9387287a2e in QTreeViewPrivate::itemHeight (this=0x3a6b0b0, item=38) at itemviews/qtreeview.cpp:3242 #11 0x7f9387287c6f in QTreeViewPrivate::updateScrollBars (this=0x3a6b0b0) at itemviews/qtreeview.cpp:3487 #12 0x7f93872880a4 in QTreeView::updateGeometries (this=0x3b8cd10) at itemviews/qtreeview.cpp:2751 #13 0x7f936f45f226 in ?? () from /usr/lib/libmessagelist.so.4 #14 0x7f936f45fa13 in ?? () from /usr/lib/libmessagelist.so.4 #15 0x7f936f46187e in MessageList::Core::Model::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libmessagelist.so.4 #16 0x7f938797ed3f in QMetaObject::activate (sender=0x3b682c8, m=, local_signal_index=, argv=0x0) at kernel/qobject.cpp:3275 #17 0x7f938797b993 in QObject::event (this=0x3b682c8, e=0x7fff7a7af5d0) at kernel/qobject.cpp:1212 #18 0x7f9386d26fac in QApplicationPrivate::notify_helper (this=0xf325a0, receiver=0x3b682c8, e=0x7fff7a7af5d0) at kernel/qapplication.cpp:4298 #19 0x7f9386d2d59b in QApplication::notify (this=0x7fff7a7af9c0, receiver=0x3b682c8, e=0x7fff7a7af5d0) at kernel/qapplication.cpp:4181 #20 0x7f938835ad16 in KApplication::notify (this=0x7fff7a7af9c0, receiver=0x3b682c8, event=0x7fff7a7af5d0) at ../../kdeui/kernel/kapplication.cpp:302 #21 0x7f938796bf3c in QCoreApplication::notifyInternal (this=0x7fff7a7af9c0, receiver=0x3b682c8, event=0x7fff7a7af5d0) at kernel/qcoreapplication.cpp:704 #22 0x7f9387998b92 in QCoreApplication::sendEvent (this=0xf260e0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #23 QTimerInfoList::activateTimers (this=0xf260e0) at kernel/qeventdispatcher_unix.cpp:603 #24 0x7f9387998d0c in QEventDispatcherUNIX::processEvents (this=0xef8df0, flags=) at kernel/qeventdispatcher_unix.cpp:924 #25 0x7f9386dd75c7 in QEventDispatcherX11::processEvents (this=, flags=) at kernel/qeventdispatcher_x11.cpp:152 #26 0x7f938796a862 in QEventLoop::processEvents (this=, flags=) at kernel/qeventloop.cpp:149 #27 0x7f938796ac3c in QEventLoop::exec (this=0x7fff7a7af900, flags=) at kernel/qeventloop.cpp:201 #28 0x7f938796e97b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981 #29 0x00403ece in _start () This bug may be a duplicate of or related to bug 223245. Possible duplicates by query: bug 223260, bug 223245, bug 219964. 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
