[kmail2] [Bug 393421] No ability to hide the HTML Message Status Bar
https://bugs.kde.org/show_bug.cgi?id=393421 Niels changed: What|Removed |Added CC||ni...@peen.ch --- Comment #66 from Niels --- Surprised to find that we cannot disable the bar (anymore), but are still allowed to obfuscate it by changing its colors. This makes little sense, unless the goal is to have kmail's appearance be less attractive and inconsistent. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 425976] mysql.err.old contains lots of errors: "Incorrect definition of table mysql.column_stats: expected column 'min_value' at position 3 to have type varbinary(255), found type varcha
https://bugs.kde.org/show_bug.cgi?id=425976 Niels changed: What|Removed |Added CC||niels.m...@noyo.dk --- Comment #3 from Niels --- I have the same problem, but I'm reluctant to experiment with mysql as suggested. Could akonadi do this kind of maintenance itself? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 380179] Regression kMail 5.5.1: Moving messages (DnD) does not work reliably any more
https://bugs.kde.org/show_bug.cgi?id=380179 Niels Ole Salscheider <niels_...@salscheider-online.de> changed: What|Removed |Added CC||niels_ole@salscheider-onlin ||e.de -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 380182] deleting a message thread doesn't remove it from the message list
https://bugs.kde.org/show_bug.cgi?id=380182 Niels Ole Salscheider <niels_...@salscheider-online.de> changed: What|Removed |Added CC||niels_ole@salscheider-onlin ||e.de -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 362305] New: Crash when setting up kmail for the first time
https://bugs.kde.org/show_bug.cgi?id=362305 Bug ID: 362305 Summary: Crash when setting up kmail for the first time Product: Akonadi Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: elga...@agol.dk CC: kdepim-bugs@kde.org, vkra...@kde.org Application: akonadi_imap_resource () 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: Setting up up kmail for the first time with imap account. It fails because kmail does not know the certificate. then Kmail crashes - Custom settings of the application: none. -- Backtrace: Application: akonadi_imap_resource (akonadi_imap_resource), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa4bdffe940 (LWP 4505))] Thread 5 (Thread 0x7fa4ba8a5700 (LWP 4507)): #0 0x7fa4c8edea64 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fa4c8e9931e in g_main_context_acquire () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa4c8e9a1d5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa4c8e9a42c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fa4cdd3ca9b in QEventDispatcherGlib::processEvents (this=0x7fa4ac0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7fa4cdce3dea in QEventLoop::exec (this=this@entry=0x7fa4ba8a4c80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7fa4cdb008a4 in QThread::exec (this=) at thread/qthread.cpp:503 #7 0x7fa4cdb0584e in QThreadPrivate::start (arg=0xf2c280) at thread/qthread_unix.cpp:331 #8 0x7fa4ca1dd6fa in start_thread (arg=0x7fa4ba8a5700) at pthread_create.c:333 #9 0x7fa4cd205b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7fa4ba0a4700 (LWP 4509)): #0 0x7fa4c8e99ed8 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fa4c8e9a380 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa4c8e9a42c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa4cdd3ca9b in QEventDispatcherGlib::processEvents (this=0x7fa4b8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7fa4cdce3dea in QEventLoop::exec (this=this@entry=0x7fa4ba0a3c80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7fa4cdb008a4 in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7fa4cdb0584e in QThreadPrivate::start (arg=0xf43d40) at thread/qthread_unix.cpp:331 #7 0x7fa4ca1dd6fa in start_thread (arg=0x7fa4ba0a4700) at pthread_create.c:333 #8 0x7fa4cd205b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7fa4b8e93700 (LWP 4513)): #0 0x7fa4c8edea49 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fa4c8e993f4 in g_main_context_release () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa4c8e9a2d6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa4c8e9a42c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fa4cdd3ca9b in QEventDispatcherGlib::processEvents (this=0x7fa4a40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7fa4cdce3dea in QEventLoop::exec (this=this@entry=0x7fa4b8e92c80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7fa4cdb008a4 in QThread::exec (this=) at thread/qthread.cpp:503 #7 0x7fa4cdb0584e in QThreadPrivate::start (arg=0xf3c710) at thread/qthread_unix.cpp:331 #8 0x7fa4ca1dd6fa in start_thread (arg=0x7fa4b8e93700) at pthread_create.c:333 #9 0x7fa4cd205b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fa4abba4700 (LWP 4588)): #0 0x7fa4c8e99b91 in g_main_context_query () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fa4c8e9a297 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa4c8e9a42c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa4cdd3ca9b in QEventDispatcherGlib::processEvents (this=0x7fa4a016aba0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7fa4cdce3dea in QEventLoop::exec (this=this@entry=0x7fa4abba3c80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7fa4cdb008a4 in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7fa4cdb0584e in QThreadPrivate::start (arg=0x14718b0) at thread/qthread_unix.cpp:331 #7 0x7fa4ca1dd6fa in start_thread (arg=0x7fa4abba4700) at pthread_create.c:333 #8 0x7fa4cd205b5d in clone () at
[kmail2] [Bug 360649] New: Quick win: provide a toolbar button to toggle "message preview pane"
https://bugs.kde.org/show_bug.cgi?id=360649 Bug ID: 360649 Summary: Quick win: provide a toolbar button to toggle "message preview pane" Product: kmail2 Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: UI Assignee: kdepim-bugs@kde.org Reporter: ni...@nielsvm.org Hello great kdepim folks! In my usage patterns of kmail/kontact, I often find myself using it on a small screen and using it on multihead setups. When I'm using kmail on a small screen, I'd like to have the message preview pane below the message list, when on a bigger screen rather on the right. If you could add a toolbar button and/or shortcut combo, that would make my life easier! Thanks in advance, Niels Reproducible: Always -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 337396] Caldav (owncloud) hangs on sync caused by db issues
https://bugs.kde.org/show_bug.cgi?id=337396 Niels Dettenbach n...@syndicat.com changed: What|Removed |Added CC||n...@syndicat.com --- Comment #2 from Niels Dettenbach n...@syndicat.com --- It seems i can confirm the bug, because i get a similiar error with akonadi 1.13.0 (in kontact 4.14.3 / Gentoo). Beside this, akonadi is hardly consuming system ressources from time to time (for ~30 seconds in steps of 10-20 minutes - leads to nearly full hang of KDE only, while text konsoles are not affected from time to time and some times the full system) on a relatively powerful machine (Mac Book Pro 6,1 with fast SSD, 8 GB, i7 Dual/Quad CPU): DB error: Cannot add or update a child row: a foreign key constraint fails (`akonadi`.`collectionpimitemrelation`, CONSTRAINT `collectionpimitemrelation_ibfk_2` FOREIGN KEY (`PimItem_id`) REFERENCES `pimitemtable` (`id`) ON DELETE CASCADE ON UPDATE CASCADE) Error text: Cannot add or update a child row: a foreign key constraint fails (`akonadi`.`collectionpimitemrelation`, CONSTRAINT `collectionpimitemrelation_ibfk_2` FOREIGN KEY (`PimItem_id`) REFERENCES `pimitemtable` (`id`) ON DELETE CASCADE ON UPDATE CASCADE) QMYSQL3: Unable to execute statement Query: INSERT INTO CollectionPimItemRelation (Collection_id, PimItem_id) VALUES (:0, :1) Error during adding a record to table CollectionPimItemRelation Cannot add or update a child row: a foreign key constraint fails (`akonadi`.`collectionpimitemrelation`, CONSTRAINT `collectionpimitemrelation_ibfk_2` FOREIGN KEY (`PimItem_id`) REFERENCES `pimitemtable` (`id`) ON DELETE CASCADE ON UPDATE CASCADE) QMYSQL3: Unable to execute statement DATABASE ERROR: Error code: 1452 DB error: Cannot add or update a child row: a foreign key constraint fails (`akonadi`.`collectionpimitemrelation`, CONSTRAINT `collectionpimitemrelation_ibfk_2` FOREIGN KEY (`PimItem_id`) REFERENCES `pimitemtable` (`id`) ON DELETE CASCADE ON UPDATE CASCADE) Error text: Cannot add or update a child row: a foreign key constraint fails (`akonadi`.`collectionpimitemrelation`, CONSTRAINT `collectionpimitemrelation_ibfk_2` FOREIGN KEY (`PimItem_id`) REFERENCES `pimitemtable` (`id`) ON DELETE CASCADE ON UPDATE CASCADE) QMYSQL3: Unable to execute statement Query: INSERT INTO CollectionPimItemRelation (Collection_id, PimItem_id) VALUES (:0, :1) Error during adding a record to table CollectionPimItemRelation Cannot add or update a child row: a foreign key constraint fails (`akonadi`.`collectionpimitemrelation`, CONSTRAINT `collectionpimitemrelation_ibfk_2` FOREIGN KEY (`PimItem_id`) REFERENCES `pimitemtable` (`id`) ON DELETE CASCADE ON UPDATE CASCADE) QMYSQL3: Unable to execute statement DATABASE ERROR: Error code: 1452 DB error: Cannot add or update a child row: a foreign key constraint fails (`akonadi`.`collectionpimitemrelation`, CONSTRAINT `collectionpimitemrelation_ibfk_2` FOREIGN KEY (`PimItem_id`) REFERENCES `pimitemtable` (`id`) ON DELETE CASCADE ON UPDATE CASCADE) Error text: Cannot add or update a child row: a foreign key constraint fails (`akonadi`.`collectionpimitemrelation`, CONSTRAINT `collectionpimitemrelation_ibfk_2` FOREIGN KEY (`PimItem_id`) REFERENCES `pimitemtable` (`id`) ON DELETE CASCADE ON UPDATE CASCADE) QMYSQL3: Unable to execute statement Query: INSERT INTO CollectionPimItemRelation (Collection_id, PimItem_id) VALUES (:0, :1) Error during adding a record to table CollectionPimItemRelation Cannot add or update a child row: a foreign key constraint fails (`akonadi`.`collectionpimitemrelation`, CONSTRAINT `collectionpimitemrelation_ibfk_2` FOREIGN KEY (`PimItem_id`) REFERENCES `pimitemtable` (`id`) ON DELETE CASCADE ON UPDATE CASCADE) QMYSQL3: Unable to execute statement DATABASE ERROR: Error code: 1452 DB error: Cannot add or update a child row: a foreign key constraint fails (`akonadi`.`collectionpimitemrelation`, CONSTRAINT `collectionpimitemrelation_ibfk_2` FOREIGN KEY (`PimItem_id`) REFERENCES `pimitemtable` (`id`) ON DELETE CASCADE ON UPDATE CASCADE) Error text: Cannot add or update a child row: a foreign key constraint fails (`akonadi`.`collectionpimitemrelation`, CONSTRAINT `collectionpimitemrelation_ibfk_2` FOREIGN KEY (`PimItem_id`) REFERENCES `pimitemtable` (`id`) ON DELETE CASCADE ON UPDATE CASCADE) QMYSQL3: Unable to execute statement Query: INSERT INTO CollectionPimItemRelation (Collection_id, PimItem_id) VALUES (:0, :1) Error during adding a record to table CollectionPimItemRelation Cannot add or update a child row: a foreign key constraint fails (`akonadi`.`collectionpimitemrelation`, CONSTRAINT `collectionpimitemrelation_ibfk_2` FOREIGN KEY (`PimItem_id`) REFERENCES `pimitemtable` (`id`) ON DELETE CASCADE ON UPDATE CASCADE) QMYSQL3: Unable to execute statement DATABASE ERROR: Error code: 1452 DB error: Cannot add or update a child row: a foreign key constraint fails
[Bug 289342] Akonadi server should shut down automatically if idle
https://bugs.kde.org/show_bug.cgi?id=289342 Niels van Mourik ni...@shodan.nl changed: What|Removed |Added CC||ni...@shodan.nl --- Comment #3 from Niels van Mourik ni...@shodan.nl --- Please be a bit more polite here, we are all trying to improve KDE and Akonadi to gain more market share. I'm actually agreeing with Jonathan that this makes sense as we'd only like these services to be available when we - the user - demand them to. Let's not forget the user perspective in here, that doesn't know what Akonadi is and - as being a humble user - shouldn't know about it. Akonadi is a background service that facilitates the user indirectly and therefore should be gaining less to no direct attention - even not in unexpected system resources. Adding a auto shutdown feature would be very appreciated - and I think I speak on behalf of many KDE users - and even does it when it's optional. Niels (In reply to comment #1) so, following your logic, you should also: - stop cups when you don't need it, - stop the firewall when you don't need it, - stop udev when you don't need it and so on for every service ? -- 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 269589] which version to keep-dialogue blocks Kontact-GUI
https://bugs.kde.org/show_bug.cgi?id=269589 Niels van Mourik ni...@shodan.nl changed: What|Removed |Added CC||ni...@shodan.nl --- Comment #1 from Niels van Mourik ni...@shodan.nl --- Totally agreeing here that this dialogue creates a daily amount of irritation and the - data integrity focused - attempt at preserving data is very humble but different compared to other e-mail and PIM solutions. I would therefore opt that Akonadi gets automatic conflict resolution picking whatever option it seems best, even duplicating records with BACKUP in a title is usually less obtrusive then a blocking dialog in front of the user. My attempt here is to raise awareness on the fact that Akonadi is a - very beautiful - piece of tech but that it facilitates the user indirectly and not directly - e.g. Kmail has a direct relationship with the user. The less visible Akonadi and it's logo's are to the end user, the better as it gives them the it all just works impression. -- 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 301206] New: Wish: Improve KDE, be less obtrusive!
https://bugs.kde.org/show_bug.cgi?id=301206 Bug ID: 301206 Severity: wishlist Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Wish: Improve KDE, be less obtrusive! Classification: Unclassified OS: Linux Reporter: ni...@shodan.nl Hardware: Other Status: UNCONFIRMED Component: general Product: Akonadi Hi there, As a wintered programmer the first thing - besides stating that I don't have enough time myself - I would like to state is how much of a beautiful piece of tech Akonadi actually is. It's architecture makes total sense, the system works and came a very long way but is getting rock solid. The point I would like to make to everybody is that Akonadi is a background service that never facilitates users directly, it facilitates developers of front-end implementations like Kmail and Korganizer. Although I'm not telling any new here, where I do want to emphasize on is Akonadi's role in the user interface of the average KDE user (John Ko :p). The fact the project has a logo and is named generically PIM services in some dialogues is good and there's nothing wrong with that. However, there are several examples in it's design where we wouldn't want the user to be bothered with things - most users - won't understand initially, let me give some examples: - Not automatically going back to online mode after connection failure (kmail). - Failed connection notifications, technical error messages that disturb users. - Conflict notification that disturb users instead of forced automatic conflict resolution. - Presence of the systray applet named AkonadiTray, why no generic naming? - Any direct mentioning of Akonadi where users expect something they understand. - Akonadi not automatically shutting down when it's not needed anymore, saving resources. Well I gave some examples and I do know and realize that many tickets created probably try to mention them or users giving their irritation on it. My point here is a little bit different though. Once we are at the point that the average user never sees Akonadi or knows about its existence anymore we have accomplished something very useful, a KDE experience that just works (TM) with rock solid PIM service integration everywhere. I genuinely think that getting more user expected behavior in the interface bits will improve the product and thus the long-term satisfaction for the limited resources behind Akonadi! When I ever find the time I will try to work on bits like the ones mentioned! Thanks a lot for listening to my plea! Niels -- 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 295474] kmail 4.8.1 crashes all the time
https://bugs.kde.org/show_bug.cgi?id=295474 --- Comment #14 from Niels Ole Salscheider niels_...@salscheider-online.de --- Many of the warnings about uninitialized values are from libcrypto that uses uninitialized values as an entropy source. Unfortunately, you are missing some debug symbols... I cannot get kmail to crash with valgrind. -- 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 295474] kmail 4.8.1 crashes all the time
https://bugs.kde.org/show_bug.cgi?id=295474 Niels Ole Salscheider niels_...@salscheider-online.de changed: What|Removed |Added CC||niels_ole@salscheider-onlin ||e.de --- Comment #2 from Niels Ole Salscheider niels_...@salscheider-online.de --- I think this is the same issue I have. My backtrace is: Application: KMail (kmail), signal: Aborted Using host libthread_db library /lib64/libthread_db.so.1. [Current thread is 1 (Thread 0x7ff8566db780 (LWP 3800))] Thread 5 (Thread 0x7ff83747d700 (LWP 3811)): #0 0x7ff8517bffec in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7ff847e8c5b4 in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/qt4/libQtWebKit.so.4 #2 0x7ff847e8c6e9 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/qt4/libQtWebKit.so.4 #3 0x7ff8517bbf7c in start_thread () from /lib64/libpthread.so.0 #4 0x7ff8539dfded in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7ff836b7c700 (LWP 3812)): #0 0x7ff8539d7173 in poll () from /lib64/libc.so.6 #1 0x7ff84c01f5b8 in g_main_context_iterate.isra.21 () from /usr/lib64/libglib-2.0.so.0 #2 0x7ff84c01fa3b in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7ff854363936 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #4 0x7ff854333452 in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #5 0x7ff8543336d7 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #6 0x7ff854232b3f in QThread::exec() () from /usr/lib64/qt4/libQtCore.so.4 #7 0x7ff854235b7b in QThreadPrivate::start(void*) () from /usr/lib64/qt4/libQtCore.so.4 #8 0x7ff8517bbf7c in start_thread () from /lib64/libpthread.so.0 #9 0x7ff8539dfded in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7ff7e700 (LWP 4025)): #0 0x7ff8517c036b in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7ff85423602a in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/qt4/libQtCore.so.4 #2 0x7ff854229166 in QThreadPoolThread::run() () from /usr/lib64/qt4/libQtCore.so.4 #3 0x7ff854235b7b in QThreadPrivate::start(void*) () from /usr/lib64/qt4/libQtCore.so.4 #4 0x7ff8517bbf7c in start_thread () from /lib64/libpthread.so.0 #5 0x7ff8539dfded in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7ff7edbce700 (LWP 4027)): #0 0x7ff8539ed26e in __lll_lock_wait_private () from /lib64/libc.so.6 #1 0x7ff85398243f in _L_lock_6476 () from /lib64/libc.so.6 #2 0x7ff8539809c1 in free () from /lib64/libc.so.6 #3 0x7ff85427fd6c in QString::free(QString::Data*) () from /usr/lib64/qt4/libQtCore.so.4 #4 0x7ff8543581c1 in clear(QVariant::Private*) () from /usr/lib64/qt4/libQtCore.so.4 #5 0x7ff8519ebd7c in QListQVariant::~QList() () from /usr/lib64/qt4/libQtDBus.so.4 #6 0x7ff851a0041f in QDBusMessage::~QDBusMessage() () from /usr/lib64/qt4/libQtDBus.so.4 #7 0x7ff851a2fa05 in QDBusPendingCallPrivate::~QDBusPendingCallPrivate() () from /usr/lib64/qt4/libQtDBus.so.4 #8 0x7ff851a2fb83 in QDBusPendingCall::~QDBusPendingCall() () from /usr/lib64/qt4/libQtDBus.so.4 #9 0x7ff84c65d77b in Nepomuk::ResourceWatcher::addResource(Nepomuk::Resource const) () from /usr/lib64/libnepomuk.so.4 #10 0x7ff84c63f07b in Nepomuk::ResourceData::load() () from /usr/lib64/libnepomuk.so.4 #11 0x7ff84c63fa5c in Nepomuk::ResourceData::property(QUrl const) () from /usr/lib64/libnepomuk.so.4 #12 0x7ff84c655d4a in Nepomuk::Resource::property(QUrl const) const () from /usr/lib64/libnepomuk.so.4 #13 0x7ff84fa3921a in MessageCore::NepomukResourceRetrieverRunnable::run() () from /usr/lib64/libmessagecore.so.4 #14 0x7ff8542290b0 in QThreadPoolThread::run() () from /usr/lib64/qt4/libQtCore.so.4 #15 0x7ff854235b7b in QThreadPrivate::start(void*) () from /usr/lib64/qt4/libQtCore.so.4 #16 0x7ff8517bbf7c in start_thread () from /lib64/libpthread.so.0 #17 0x7ff8539dfded in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7ff8566db780 (LWP 3800)): [KCrash Handler] #6 0x7ff85393cd75 in raise () from /lib64/libc.so.6 #7 0x7ff85393e245 in abort () from /lib64/libc.so.6 #8 0x7ff853976a5e in __libc_message () from /lib64/libc.so.6 #9 0x7ff85397cadd in malloc_printerr () from /lib64/libc.so.6 #10 0x7ff8539809cc in free () from /lib64/libc.so.6 #11 0x7ff85427fd6c in QString::free(QString::Data*) () from /usr/lib64/qt4/libQtCore.so.4 #12 0x7ff8519ec4ca in QDBusError::QDBusError(QDBusMessage const) () from /usr/lib64/qt4/libQtDBus.so.4 #13 0x7ff8519f036b in QDBusConnectionPrivate::processFinishedCall
[Bug 166121] New: Kmail crashes on renaming a folder on a imap account
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=166121 Summary: Kmail crashes on renaming a folder on a imap account Product: kmail Version: unspecified Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: niels shodan nl Version:(using Devel) Installed from:Compiled sources Compiler: gcc (GCC) 4.1.2 (Gentoo 4.1.2 p1.1) OS:Linux Simply to reproduce: 1. rightclick on a folder in a IMAP account (only tested with IMAP) 2. Open properties dialog 3. Change the name of the folder -submit- Kmail crashes, see bt below. The imap folder get's renamed funny enough, so after the crash restarting Kmail is enough. -- Application: KMail (kmail), signal SIGABRT (no debugging symbols found) Using host libthread_db library /lib/libthread_db.so.1. (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb49196d0 (LWP 7170)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging
