[Akonadi] [Bug 374676] The Akonadi personal information management service is not operational
https://bugs.kde.org/show_bug.cgi?id=374676 --- Comment #5 from sq...@web.de --- (In reply to squan from comment #2) > (In reply to Rewarp from comment #1) > Same for me running openSUSE Tumbleweed with (...) NOT the same according to https://forums.opensuse.org/showthread.php/521873-Akonadi-Won-t-Start comment #7. Regarding the crash on arch it says "That's a well-known and long-standing issue in Arch. Their VLC is still using Qt4, and KF5 applications crash when they try to play a notification sound with the phonon-backend-vlc". Regarding the openSUSE crash on mysql start the forum thread also says that this is about to be fixed in Tumbleweed by cleaning up stale socket files, dunno if this only affects Tumbleweed though. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 373034] auto correction
https://bugs.kde.org/show_bug.cgi?id=373034 rjwgn...@yahoo.com changed: What|Removed |Added CC||rjwgn...@yahoo.com --- Comment #1 from rjwgn...@yahoo.com --- This occurs for me too: - Under Settings->Configure KMail->Identities - edit an identitiy - go to "Advanced" tab - The "Autocorrection lanuage" field shows "Abkhazian". - Change to "English" - Click "OK" Returning back to the same setting, the field has reverted to "Abkhazian". KMail 5.43.3 from Fedora 25 packages. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 375448] bad date for items
https://bugs.kde.org/show_bug.cgi?id=375448 --- Comment #1 from Philippe ROUBACH --- also for google blog sometime there is no date -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 375461] akonadi_davgroupware_resource signal: Segmentation fault 16.12.0 during start up
https://bugs.kde.org/show_bug.cgi?id=375461 Bruno Friedmann changed: What|Removed |Added Version|unspecified |5.4.0 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 375461] New: akonadi_davgroupware_resource signal: Segmentation fault 16.12.0 during start up
https://bugs.kde.org/show_bug.cgi?id=375461 Bug ID: 375461 Summary: akonadi_davgroupware_resource signal: Segmentation fault 16.12.0 during start up Product: Akonadi Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: DAV Resource Assignee: kdepim-bugs@kde.org Reporter: br...@ioda-net.ch Target Milestone: --- on openSUSE Tumbleweed 20170121 at startup akonadi_groupware agent crash Application: akonadi_davgroupware_resource (akonadi_davgroupware_resource), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcb6ea54940 (LWP 3153))] Thread 5 (Thread 0x7fcb42ffd700 (LWP 3299)): #0 0x7fcb68ffc66d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fcb615d6886 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fcb615d699c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fcb69b3318b in QEventDispatcherGlib::processEvents (this=0x7fcb380008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fcb69adcaea in QEventLoop::exec (this=this@entry=0x7fcb42ffcc80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7fcb6990a813 in QThread::exec (this=) at thread/qthread.cpp:507 #6 0x7fcb6990f4c8 in QThreadPrivate::start (arg=0xb59e30) at thread/qthread_unix.cpp:368 #7 0x7fcb63323454 in start_thread (arg=0x7fcb42ffd700) at pthread_create.c:333 #8 0x7fcb6900537f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 4 (Thread 0x7fcb437fe700 (LWP 3239)): #0 __libc_enable_asynccancel () at ../sysdeps/unix/sysv/linux/x86_64/cancellation.S:67 #1 0x7fcb68ffc662 in poll () at ../sysdeps/unix/syscall-template.S:84 #2 0x7fcb615d6886 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7fcb615d699c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7fcb69b3318b in QEventDispatcherGlib::processEvents (this=0x7fcb340008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7fcb69adcaea in QEventLoop::exec (this=this@entry=0x7fcb437fdc80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7fcb6990a813 in QThread::exec (this=) at thread/qthread.cpp:507 #7 0x7fcb6990f4c8 in QThreadPrivate::start (arg=0xb48d80) at thread/qthread_unix.cpp:368 #8 0x7fcb63323454 in start_thread (arg=0x7fcb437fe700) at pthread_create.c:333 #9 0x7fcb6900537f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 3 (Thread 0x7fcb43fff700 (LWP 3235)): #0 0x7fcb68ffc66d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fcb615d6886 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fcb615d699c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fcb69b3318b in QEventDispatcherGlib::processEvents (this=0x7fcb3c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fcb69adcaea in QEventLoop::exec (this=this@entry=0x7fcb43ffec50, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7fcb6990a813 in QThread::exec (this=) at thread/qthread.cpp:507 #6 0x7fcb69f45385 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7fcb6990f4c8 in QThreadPrivate::start (arg=0x7fcb6a1b6d20) at thread/qthread_unix.cpp:368 #8 0x7fcb63323454 in start_thread (arg=0x7fcb43fff700) at pthread_create.c:333 #9 0x7fcb6900537f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 2 (Thread 0x7fcb4c3cb700 (LWP 3187)): #0 0x7fcb68ffc66d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fcb637493e0 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7fcb6374b179 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7fcb4e2be889 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7fcb6990f4c8 in QThreadPrivate::start (arg=0x742e90) at thread/qthread_unix.cpp:368 #5 0x7fcb63323454 in start_thread (arg=0x7fcb4c3cb700) at pthread_create.c:333 #6 0x7fcb6900537f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 1 (Thread 0x7fcb6ea54940 (LWP 3153)): [KCrash Handler] #6 std::__atomic_base::load (__m=std::memory_order_relaxed, this=) at /usr/include/c++/6/bits/atomic_base.h:396 #7 QAtomicOps::load (_q_value=) at /usr/include/qt5/QtCore/qatomic_cxx11.h:227 #8 QBasicAtomicInteger::load (this=) at /usr/include/qt5/QtCore/qbasicatomic.h:99 #9 QtPrivate::RefCount::isShared (this=) at /usr/include/qt5/QtCore/qrefcount.h:101 #10 QMap::detach (this=0x10) at /usr/include/qt5/QtCore/qmap.h:366 #11 QMap::operator[] (akey=..., this=0x10) at /usr/include/qt5/QtCore/qmap.h:664 #12 EtagCache::setEtag (this=this@entry=0x0, remoteId=..., etag=...) at /usr/src/debug/kdepim-runtime-16.12.0/resources/dav/common/etagcache.cpp:38 #13 0x0046427f in DavGroupwareResource::onItemFetched (this=0xb4da10, job=, upd
[kmail2] [Bug 375444] Expire... in kmail2 version 5.4.0 is honored but not saved
https://bugs.kde.org/show_bug.cgi?id=375444 Laurent Montel changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||mon...@kde.org Resolution|--- |FIXED --- Comment #1 from Laurent Montel --- I fixed a bug when we click on ok in 5.4.2 So for me it's fixed. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 375450] New: akonadiserver crashes on system shudown
https://bugs.kde.org/show_bug.cgi?id=375450 Bug ID: 375450 Summary: akonadiserver crashes on system shudown Product: Akonadi Version: 5.4.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: robby.engelm...@igfs-ev.de Target Milestone: --- akonadiserver crashes on almost every system shutdown using openSUSE Tumbleweed: gdb) bt #0 0x7f8bac7115af in raise () from /lib64/libc.so.6 #1 0x7f8bae3f6b84 in KCrash::defaultCrashHandler(int) () from /usr/lib64/libKF5Crash.so.5 #2 #3 QScopedPointer >::data (this=0x8) at ../../src/corelib/tools/qscopedpointer.h:141 #4 qGetPtrHelper > (p=...) at ../../src/corelib/global/qglobal.h:980 #5 QIODevice::d_func (this=0x0) at ../../src/corelib/io/qiodevice.h:178 #6 QIODevice::write (this=0x0, data=0x7f8b52ffc3ec "\227", maxSize=1) at io/qiodevice.cpp:1596 #7 0x7f8bae1afbc0 in ?? () from /usr/lib64/libKF5AkonadiPrivate.so.5 #8 0x7f8bae1b332f in ?? () from /usr/lib64/libKF5AkonadiPrivate.so.5 #9 0x7f8bae19a9b4 in Akonadi::Protocol::serialize(QIODevice*, Akonadi::Protocol::Command const&) () from /usr/lib64/libKF5AkonadiPrivate.so.5 #10 0x0042c9b3 in Akonadi::Server::Connection::sendResponse (this=0x211c1e0, tag=10, response=...) at /usr/src/debug/akonadi-16.12.1/src/server/connection.cpp:404 #11 0x00430e42 in Akonadi::Server::Handler::sendResponse (response=..., this=0x7f8b48052fb0) at /usr/src/debug/akonadi-16.12.1/src/server/handler.cpp:268 #12 Akonadi::Server::Handler::sendResponse (this=0x7f8b48052fb0, response=...) at /usr/src/debug/akonadi-16.12.1/src/server/handler.h:152 #13 Akonadi::Server::Handler::failureResponse (this=this@entry=0x7f8b48052fb0, failureMessage=...) at /usr/src/debug/akonadi-16.12.1/src/server/handler.cpp:261 #14 0x00430fff in Akonadi::Server::Handler::failureResponse (this=0x7f8b48052fb0, failureMessage=) at /usr/src/debug/akonadi-16.12.1/src/server/handler.cpp:252 #15 0x0042eb8d in Akonadi::Server::Connection::slotNewData (this=0x211c1e0) at /usr/src/debug/akonadi-16.12.1/src/server/connection.cpp:252 #16 0x7f8bad2cba7e in QtPrivate::QSlotObjectBase::call (a=0x7f8b52ffc8d0, r=0x211c1e0, this=) at ../../src/corelib/kernel/qobject_impl.h:101 #17 QMetaObject::activate (sender=0x7f8b48002cd0, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3723 #18 0x7f8bad2cb709 in QMetaObject::activate (sender=0x7f8b48002dc8, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3740 #19 0x7f8baded6265 in ?? () from /usr/lib64/libQt5Network.so.5 ---Type to continue, or q to quit--- #20 0x7f8baded631c in ?? () from /usr/lib64/libQt5Network.so.5 #21 0x7f8badee1121 in ?? () from /usr/lib64/libQt5Network.so.5 #22 0x7f8bad29faeb in doNotify (event=0x7f8b52ffcae0, receiver=0x7f8b48003060) at kernel/qcoreapplication.cpp:1063 #23 QCoreApplication::notify (event=, receiver=, this=) at kernel/qcoreapplication.cpp:1049 #24 QCoreApplication::notifyInternal2 (receiver=0x7f8b48003060, event=event@entry=0x7f8b52ffcae0) at kernel/qcoreapplication.cpp:988 #25 0x7f8bad2f461d in QCoreApplication::sendEvent (event=0x7f8b52ffcae0, receiver=) at ../../src/corelib/kernel/qcoreapplication.h:231 #26 socketNotifierSourceDispatch (source=0x7f8b48002a00) at kernel/qeventdispatcher_glib.cpp:106 #27 0x7f8ba9445687 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #28 0x7f8ba94458f0 in ?? () from /usr/lib64/libglib-2.0.so.0 #29 0x7f8ba944599c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #30 0x7f8bad2f416f in QEventDispatcherGlib::processEvents (this=0x7f8b480008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #31 0x7f8bad29daea in QEventLoop::exec (this=this@entry=0x7f8b52ffcd00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #32 0x7f8bad0cb813 in QThread::exec (this=) at thread/qthread.cpp:507 #33 0x7f8bad0d04c8 in QThreadPrivate::start (arg=0x21138c0) at thread/qthread_unix.cpp:368 #34 0x7f8bab35d454 in start_thread () from /lib64/libpthread.so.0 #35 0x7f8bac7c637f in clone () from /lib64/libc.so.6 -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 375448] New: bad date for items
https://bugs.kde.org/show_bug.cgi?id=375448 Bug ID: 375448 Summary: bad date for items Product: akregator Version: 5.3.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: philippe.roub...@free.fr Target Milestone: --- Created attachment 103601 --> https://bugs.kde.org/attachment.cgi?id=103601&action=edit bad date opensuse 42.2 x86_64 for some site the date for the news are very strange for example for google blog we get a date as 7/2/2106 07:28 a new technology by kde to travel through time? see the attachment moreover i deleted many times this news and they come back again and again. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 375445] KMail2 hangs with 100% CPU usage when trying to preview or read large emails from IMAP server
https://bugs.kde.org/show_bug.cgi?id=375445 Rodney Baker changed: What|Removed |Added CC||rodney.ba...@iinet.net.au -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 375445] New: KMail2 hangs with 100% CPU usage when trying to preview or read large emails from IMAP server
https://bugs.kde.org/show_bug.cgi?id=375445 Bug ID: 375445 Summary: KMail2 hangs with 100% CPU usage when trying to preview or read large emails from IMAP server Product: kmail2 Version: 5.4.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: rodney.ba...@iinet.net.au Target Milestone: --- KMail2 hangs when trying to read large text-based emails (~22MB Log files) from a Dovecot IMAP server. The emails are never shown in the preview window and KMail2 becomes unresponsive. CPU Usage for the KMail2 process goes to 100% and stays there. Memory usage gradually increases as the email is presumably parsed but the preview is never displayed, even after CPU usage eventually returns to normal and KMail again becomes responsive (takes >5 minutes). At the same time, none of the akonadi processes show unusual CPU or memory usage (if anything, perhaps unusually low, as if it is not actually doing a whole lot). By comparison, Mozilla Thunderbird can read the same emails from the same IMAP server and account without issues. The initial preview is shown immediately as the rest of the message is parsed (which does take some time, but Thunderbird remains responsive). -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 375444] New: Expire... in kmail2 version 5.4.0 is honored but not saved
https://bugs.kde.org/show_bug.cgi?id=375444 Bug ID: 375444 Summary: Expire... in kmail2 version 5.4.0 is honored but not saved Product: kmail2 Version: 5.4.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: folders Assignee: kdepim-bugs@kde.org Reporter: freekdekru...@kde.nl Target Milestone: --- Right click on the trash folder of an IMAP account gives a menu with Expire... After selecting that item the check box for the number of days is not checked. Checking the check boxes for read and unread and exit the popup shows that the number of messages is reduced, but reentering this popup shows that the check boxes are unchecked again. So the Expire... setting is honored but not saved. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 375441] Scrambled / unreadable Text when answer to or forward an HTML-Mail
https://bugs.kde.org/show_bug.cgi?id=375441 Laurent Montel changed: What|Removed |Added Resolution|--- |FIXED CC||mon...@kde.org Status|UNCONFIRMED |RESOLVED --- Comment #2 from Laurent Montel --- It was fixed in 5.4.0 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 375441] Scrambled / unreadable Text when answer to or forward an HTML-Mail
https://bugs.kde.org/show_bug.cgi?id=375441 Thorsten Oppels changed: What|Removed |Added CC||thopp...@web.de --- Comment #1 from Thorsten Oppels --- Created attachment 103597 --> https://bugs.kde.org/attachment.cgi?id=103597&action=edit Screenshots -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 375441] New: Scrambled / unreadable Text when answer to or forward an HTML-Mail
https://bugs.kde.org/show_bug.cgi?id=375441 Bug ID: 375441 Summary: Scrambled / unreadable Text when answer to or forward an HTML-Mail Product: kmail2 Version: 5.3.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: thopp...@web.de Target Milestone: --- When answer to an HTML mail which has an attachment (seen at png and pdf attachments) the editor windows shows the part of the mail as some kind of coded content. If I mark some parts of the Mail text and choose 'answer' after that, the editor window shows readable text. -- You are receiving this mail because: You are the assignee for the bug.
