[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 watching all bug changes.
[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 watching all bug changes.
[kdelibs] [Bug 202129] Plasma simply crashed during normal usage (taskmanager/netwm causes a XIOError, crashing when accessing a global var in the dataengine)
https://bugs.kde.org/show_bug.cgi?id=202129 Chris Samuel changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #24 from Chris Samuel --- Hi Justin, This appears to have been fixed at some point in the last *cough* 9 years.. ;-) All the best, Chris -- You are receiving this mail because: You are watching all bug changes.
[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 watching all bug changes.
[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 watching all bug changes.
[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 watching all bug changes.
[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 watching all bug changes.
[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 watching all bug changes.
[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 watching all bug changes.
[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 watching all bug changes.
[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 watching all bug changes.
[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 watching all bug changes.
[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 watching all bug changes.
[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 watching all bug changes.
[konqueror] [Bug 260702] Konqueror 4.6.0 beta 2 (4.5.85) leaks memory at http://www.abc.net.au/news/
https://bugs.kde.org/show_bug.cgi?id=260702 Chris Samuel changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #5 from Chris Samuel --- (In reply to Chris Samuel from comment #4) > Will do, have just opened the site now, will keep an eye on it. I think this is going to be pretty impossible to debug now. Konqueror has removed the --sync option to prevent it going into the background and the ABC News site now says it doesn't support this browser and gives a very basic HTML view instead. Konqueror has also lost the ability to spoof the browser version. As there's no longer a way to debug it, and I no longer use Konqueror for my everyday browsing I'm going to close this as fixed as there's no closer resolution (it's not invalid because it was a problem, but there's no way to tell if it's still doing it). -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 294530] Crash occured on system restauration on start up
https://bugs.kde.org/show_bug.cgi?id=294530 Chris Samuel changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #8 from Chris Samuel --- (In reply to Chris Samuel from comment #6) > I've stopped using Konqueror with multiple tabs, will try and replicate soon. I've only had the opportunity to try this once, but it worked then. Best to close as fixed I think. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 260702] Konqueror 4.6.0 beta 2 (4.5.85) leaks memory at http://www.abc.net.au/news/
https://bugs.kde.org/show_bug.cgi?id=260702 --- Comment #4 from Chris Samuel --- (In reply to Andrew Crouthamel from comment #3) > Dear Bug Submitter, > > This is a reminder that this bug has been stagnant for a long time. Could > you help us out and re-test if the bug is valid in the latest version? This > bug will be moved back to REPORTED Status for manual review later, which may > take a while. If you are able to, please lend us a hand. > > Thank you for helping us make KDE software even better for everyone! Will do, have just opened the site now, will keep an eye on it. All the best, Chris -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 294530] Crash occured on system restauration on start up
https://bugs.kde.org/show_bug.cgi?id=294530 --- Comment #6 from Chris Samuel --- Hi there, I've stopped using Konqueror with multiple tabs, will try and replicate soon. All the best, Chris -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 176393] krunner crashed because of ... ? (Thread.cpp:95)
https://bugs.kde.org/show_bug.cgi?id=176393 --- Comment #6 from Chris Samuel --- Hi Andrew, Given the last comment from 7 years ago was: > Haven't seen anything like this with Kubuntu 11.04 and KDE 4.6.2 lately. I suspect this is long since fixed. I certainly don't recall having seen it recently myself. All the best, Chris -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 383010] Add support for AVX-512 instructions
https://bugs.kde.org/show_bug.cgi?id=383010 --- Comment #28 from Chris Samuel <k...@csamuel.org> --- Hi there, We hit the illegal instruction message on Skylake (6140) CPUs running valgrind on programs linked against OpenMPI 3.0.0; the cause being that with our GCC 5.5 and higher installs memset() causes the VPXORD command to be emitted during various initialisation routines which Valgrind can't handle. It took a bit of digging to track down what was going on, so we're certainly interested in this work! All the best, Chris (HPC sysadmin at Swinburne University of Technology in Melbourne, Australia) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 383010] Add support for AVX-512 instructions
https://bugs.kde.org/show_bug.cgi?id=383010 Chris Samuel <k...@csamuel.org> changed: What|Removed |Added CC||k...@csamuel.org -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 260986] Akregator crashes on KDE shutdown
https://bugs.kde.org/show_bug.cgi?id=260986 --- Comment #7 from Chris Samuel <k...@csamuel.org> --- This is kontact/akgregator 17.04.3 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 260986] Akregator crashes on KDE shutdown
https://bugs.kde.org/show_bug.cgi?id=260986 Chris Samuel <k...@csamuel.org> changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|REOPENED --- Comment #6 from Chris Samuel <k...@csamuel.org> --- 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 watching all bug changes.
[plasmashell] [Bug 361521] Numerous deleted DRM mmaped objects
https://bugs.kde.org/show_bug.cgi?id=361521 --- Comment #14 from Chris Samuel <k...@csamuel.org> --- (In reply to David Edmundson from comment #12) > Large virtual memory isn't a problem. It can just mean we've mapped a file > on disk, even a file that isn't actually that size. We're not using up /any/ > resources by doing it. OK thanks. > If your resident memory size is high, that's a problem (and the 450Mb is > high, that we should identify and fix). Virtual memory being high is pretty > much a non issue until proved otherwise. Here is what ksysguard tells me about the breakdown of actual memory usage. Process 2344 - plasmashell Summary The process plasmashell (with pid 2344) is using approximately 452.1 MB of memory. It is using 447.7 MB privately, and a further 33.5 MB that is, or could be, shared with other programs. Dividing up the shared memory between all the processes sharing that memory we get a reduced shared memory usage of 4.4 MB. Adding that to the private usage, we get the above mentioned total memory footprint of 452.1 MB. Library Usage The memory usage of a process is found by adding up the memory usage of each of its libraries, plus the process's own heap, stack and any other mappings, plus the stack of its 24 threads. Private 435808 KB [heap] 12212 KB/drm mm object (deleted) 1892 KB /home/chris/.cache/plasma_theme_default_v5.25.kcache [etc] So basically it's all heap usage, with the deleted DRM objects contributing just 12MB. All the best, Chris -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361521] Large virtual memory consumption and many DRM mmaped objects
https://bugs.kde.org/show_bug.cgi?id=361521 --- Comment #10 from Chris Samuel <k...@csamuel.org> --- (In reply to Laurent Bonnaud from comment #8) > But perhaps this baloo problem deserves a separate bug report. This report > was about plasmashell. You misunderstand me, what I am saying is that 5GB of the 10GB VM size that plasmashell is using for me is attributed by Ksysguard to plasmashell mapping in the file: /home/chris/.local/share/baloo/index nothing to do with any baloo processes at all, purely plasmashell and its file I/O. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361521] Insane virtual memory consumption and icon-cache mappings
https://bugs.kde.org/show_bug.cgi?id=361521 --- Comment #7 from Chris Samuel <k...@csamuel.org> --- Using KSysGuard you can get a full breakdown of the mappings, it turns out for me I see 5GB is used mapping in my Baloo index file (which is just 420MB in size), another 2GB is anonymous mapping and then you've got 263MB for the heap. Address PermSize ▴ Rss Pss Shared CleanShared DirtyPrivate Clean Private Dirty Referenced Anonymous AnonHugePages ShmemPmdMapped Shared Hugetlb Private Hugetlb SwapSwapPss Locked Filename 7feebe4ee000-7feffe4ee000 r--s5242880 KB 2708 KB 1239 KB 2700 KB 0 KB8 KB0 KB2704 KB 0 KB0 KB0 KB0 KB0 KB0 KB 0 KB0 KB/home/chris/.local/share/baloo/index 7ff0a000-7ff12000 rwxp2097152 KB 2048 KB 2048 KB 0 KB 0 KB0 KB2048 KB 0 KB2048 KB 0 KB0 KB0 KB0 KB0 KB 0 KB0 KB 55ffc0e7c000-55ffd0fd3000 rw-p263516 KB 249024 KB 249024 KB 0 KB0 KB0 KB249024 KB 235092 KB 249024 KB 180224 KB 0 KB0 KB0 KB0 KB0 KB0 KB[heap] $ du -sh /home/chris/.local/share/baloo/index 420M/home/chris/.local/share/baloo/index That's not a sparse file either: $ ls -lsh /home/chris/.local/share/baloo/index 420M -rw-rw-r-- 1 chris chris 420M Aug 17 22:43 /home/chris/.local/share/baloo/index Do you see the same? Here's the summary from KSysGuard for plasmashell in case it is of use: Process 2344 - plasmashell Summary The process plasmashell (with pid 2344) is using approximately 458.4 MB of memory. It is using 447.9 MB privately, and a further 58.3 MB that is, or could be, shared with other programs. Dividing up the shared memory between all the processes sharing that memory we get a reduced shared memory usage of 10.5 MB. Adding that to the private usage, we get the above mentioned total memory footprint of 458.4 MB. Library Usage The memory usage of a process is found by adding up the memory usage of each of its libraries, plus the process's own heap, stack and any other mappings, plus the stack of its 24 threads. Private 435100 KB [heap] 12028 KB/drm mm object (deleted) 732 KB /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5.6.1 680 KB /home/chris/.cache/plasma_theme_default_v5.25.kcache 364 KB /usr/bin/plasmashell [more] Shared 7640 KB /home/chris/.cache/ksycoca5_en-AU_nRYZdPhro8LuwAG9USlBRsk3F3s= 3696 KB /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 3396 KB /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.6.1 3264 KB /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.6.1 2700 KB /home/chris/.local/share/baloo/index [more] Totals Private 458676 KB (= 6272 KB clean + 452404 KB dirty) Shared 59656 KB(= 59052 KB clean + 604 KB dirty) Rss 518332 KB (= Private + Shared) Pss 469394 KB (= Private + Shared/Number of Processes) Swap0 KB All the best, Chris -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372384] Memory leak in plasmashell
https://bugs.kde.org/show_bug.cgi?id=372384 --- Comment #7 from Chris Samuel <k...@csamuel.org> --- (In reply to Lastique from comment #6) > I'm watching memory consumption through the KDE System Monitor, the Memory > column. I think it shows resident memory minus shared memory. I did not > monitor virtual memory, so this bug is not about that. Thanks for that pointer, with that I see "just" 439MB used. All the best, Chris -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361521] Insane virtual memory consumption and icon-cache mappings
https://bugs.kde.org/show_bug.cgi?id=361521 Chris Samuel <k...@csamuel.org> changed: What|Removed |Added CC||k...@csamuel.org --- Comment #6 from Chris Samuel <k...@csamuel.org> --- I'm seeing this same issue on Kubuntu 16.10 with its Plasma 5.7.5, KDE Frameworks 5.26.0, KDE apps 16.04.3, Qt 5.6.1. I've got Intel graphics, but using the modesetting driver. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372384] Memory leak in plasmashell
https://bugs.kde.org/show_bug.cgi?id=372384 Chris Samuel <k...@csamuel.org> changed: What|Removed |Added CC||k...@csamuel.org --- Comment #5 from Chris Samuel <k...@csamuel.org> --- I too see this same leak, after 8 days plasmashell is reported as using 10GB of "VIRT" by top, but only ~513MB of RSS. I have no swap so it's likely this is memory that has been allocated/mmap()d but never touched. I suspect this is related to (if not a dup of) "Bug 361521 - Insane virtual memory consumption and icon-cache mappings". -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 353826] Kontact crashes every time I exit
https://bugs.kde.org/show_bug.cgi?id=353826 --- Comment #4 from Chris Samuel <k...@csamuel.org> --- 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 watching all bug changes.
[Akonadi] [Bug 259289] Akonadi Crashes
https://bugs.kde.org/show_bug.cgi?id=259289 --- Comment #4 from Chris Samuel <k...@csamuel.org> --- I've not seen this for a while now, I think. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 309474] akonadictl fsck : item has no RID
https://bugs.kde.org/show_bug.cgi?id=309474 Chris Samuel <k...@csamuel.org> changed: What|Removed |Added CC||k...@csamuel.org -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 362224] New: Baloo crashes when sending an email in Kmail
https://bugs.kde.org/show_bug.cgi?id=362224
Bug ID: 362224
Summary: Baloo crashes when sending an email in Kmail
Product: Baloo
Version: unspecified
Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: General
Assignee: m...@vhanda.in
Reporter: k...@csamuel.org
CC: pinak.ah...@gmail.com
Application: baloo_file (5.18.0)
Qt Version: 5.5.1
Operating System: Linux 4.4.0-21-generic x86_64
Distribution: Ubuntu 16.04 LTS
-- Information about the crash:
- What I was doing when the application crashed:
When I send an email I get an alert about baloo crashing. This doesn't appear
to be related to bug 36 which is the only suggestion DrKonqi finds for
this.
Looking at the logs in my .xsession-errors file I can see (this crash is the
one corresponding to the backtrace):
New Notification: "E-Mail Successfully Sent" "Your E-Mail has been sent
successfully." -1 & Part of: 0
log_mixedmaildir: Maildir "/home/chris/Mail/sent-mail" "cur" directory newer
than the index: cur modified at QDateTime(2016-04-23 23:16:48.000 AEST
Qt::TimeSpec(LocalTime)) , index modified at QDateTime(2012-09-15 15:56:53.000
AEST Qt::TimeSpec(LocalTime))
log_mixedmaildirresource: ""
log_mixedmaildir: ItemModifyJob for item "1461576224.R226.quad:2,S" in
collection "sent-mail" skipped: nothing of interest changed ( true ) or only
payload changed but should be ignored ( false ). Modified parts:
QSet("ATR:ErrorAttribute")
log_mixedmaildir: ItemModifyJob for item "1461576224.R226.quad:2,S" in
collection "sent-mail" skipped: nothing of interest changed ( true ) or only
payload changed but should be ignored ( false ). Modified parts:
QSet("ATR:ErrorAttribute")
file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:115:23:
QML Text: Binding loop detected for property "height"
org.kde.baloo: "/home/chris/Mail/sent-mail/tmp/1461576224.R226.quad" ->
"/home/chris/Mail/sent-mail/new/1461576224.R226.quad"
File moved to path which now no longer exists -
"/home/chris/Mail/sent-mail/new/1461576224.R226.quad"
org.kde.baloo: "/home/chris/Mail/sent-mail/new/1461576224.R226.quad" ->
"/home/chris/Mail/sent-mail/cur/1461576224.R226.quad:2,S"
mdb.c:2065: Assertion 'rc == 0' failed in mdb_page_dirty()
6002
Received: 1 Removed: 0 In total: 1 Wanted: 6002
Received: 0 Removed: 0 In total: 1 Wanted: 6002
finished
KCrash: Attempting to start /usr/bin/baloo_file from kdeinit
Here is a second example (triggered by sending myself an email for this purpose
- not the one that this backtrace is for):
New Notification: "E-Mail Successfully Sent" "Your E-Mail has been sent
successfully." -1 & Part of: 0
Database "akonadi" opened using driver "QMYSQL"
log_mixedmaildirresource: ""
org.kde.baloo: "/home/chris/Mail/sent-mail/tmp/1461576841.R287.quad" ->
"/home/chris/Mail/sent-mail/new/1461576841.R287.quad"
log_mixedmaildir: ItemModifyJob for item "1461576841.R287.quad:2,S" in
collection "sent-mail" skipped: nothing of interest changed ( true ) or only
payload changed but should be ignored ( false ). Modified parts:
QSet("ATR:ErrorAttribut
e")
log_mixedmaildir: ItemModifyJob for item "1461576841.R287.quad:2,S" in
collection "sent-mail" skipped: nothing of interest changed ( true ) or only
payload changed but should be ignored ( false ). Modified parts:
QSet("ATR:ErrorAttribut
e")
mdb.c:2065: Assertion 'rc == 0' failed in mdb_page_dirty()
file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:115:23:
QML Text: Binding loop detected for property "height"
KCrash: Attempting to start /usr/bin/baloo_file from kdeinit
The crash can be reproduced every time.
-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f9cc2df38c0 (LWP 2053))]
Thread 2 (Thread 0x7f9b77d3d700 (LWP 2626)):
#0 0x7f9cbe112a64 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1 0x7f9cbe0cd930 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x7f9cbe0ce24b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x7f9cbe0ce42c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x7f9cc1b33a9b in QEventDispatcherGlib::processEvents
(this=0x7f9b78c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5 0x7f9cc1adadea in QEventLoop::exec (this=this@entry=0x7f9b77d3cbc0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6 0x00420cd8 in Baloo::FileContentIndexer::run (this=0xbc00c0) at
../../../src/file/filecontentindexer.cpp:71
#7 0x7f9cc18f9343 in QThreadPoolThread::run (this=0xe536d0) at
thread/qthreadpool.cpp:93
#8 0x7f9cc18fc84e in
[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 <k...@csamuel.org> --- (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 watching all bug changes.
