[Akonadi] [Bug 440781] New: Kmail fails to append item/ akonadi db states wrong date format
https://bugs.kde.org/show_bug.cgi?id=440781
Bug ID: 440781
Summary: Kmail fails to append item/ akonadi db states wrong
date format
Product: Akonadi
Version: 5.17.90
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Severity: grave
Priority: NOR
Component: IMAP resource
Assignee: kdepim-b...@kde.org
Reporter: s.pa...@spiekerbros.com
Target Milestone: ---
SUMMARY
Since last update Kmail/ Akonadi fails to get new email from IMAP server. Kmail
reports "failed to append item" when synchronising mailbox. The Akonadi error
log states:
2021-08-09T14:00:17 [CRITICAL] org.kde.pim.akonadiserver: DATABASE ERROR:
2021-08-09T14:00:17 [CRITICAL] org.kde.pim.akonadiserver: Error code: "1292"
2021-08-09T14:00:17 [CRITICAL] org.kde.pim.akonadiserver: DB error:
"Incorrect datetime value: '2021-08-09T12:00:17Z' for column
`akonadi`.`pimitemtable`.`datetime` at row 1"
2021-08-09T14:00:17 [CRITICAL] org.kde.pim.akonadiserver: Error text:
"Incorrect datetime value: '2021-08-09T12:00:17Z' for column
`akonadi`.`pimitemtable`.`datetime` at row 1 QMYSQL: Unable to execute query"
2021-08-09T14:00:17 [CRITICAL] org.kde.pim.akonadiserver: Values: QMap((":0",
QVariant(int, 0))(":1", QVariant(QString, "6773"))(":2", QVariant(QString,
""))(":3", QVariant(QString, ""))(":4", QVariant(qlonglong, 21))(":5",
QVariant(qlonglong, 3))(":6", QVariant(QDateTime, QDateTime(2021-08-09
12:00:17.471 UTC Qt::UTC)))(":7", QVariant(QDateTime, QDateTime(2021-08-09
12:00:17.471 UTC Qt::UTC)))(":8", QVariant(bool, false))(":9",
QVariant(qlonglong, 2491777)))
2021-08-09T14:00:17 [CRITICAL] org.kde.pim.akonadiserver: Query: "INSERT INTO
PimItemTable (rev, remoteId, remoteRevision, gid, collectionId, mimeTypeId,
datetime, atime, dirty, size) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9)"
2021-08-09T14:00:17 [WARN ] org.kde.pim.akonadiserver: Error during insertion
into table "PimItemTable" "Incorrect datetime value: '2021-08-09T12:00:17Z' for
column `akonadi`.`pimitemtable`.`datetime` at row 1 QMYSQL: Unable to execute
query"
2021-08-09T14:00:17 [WARN ] org.kde.pim.akonadiserver: Error while handling
command CreateItem on connection akonadi_imap_resource_0 (0x559fee8e4a30)
2021-08-09T14:00:26 [INFO ] org.kde.pim.akonadiserver: Subscriber
"MessageViewerMonitor - 94908118964128" disconnected
2021-08-09T14:00:26 [INFO ] org.kde.pim.akonadiserver: Subscriber
"MessageListTagMonitor - 94908119944352" disconnected
2021-08-09T14:00:26 [INFO ] org.kde.pim.akonadiserver: Subscriber "KMail Kernel
ETM - 94908118071664" disconnected
2021-08-09T14:00:26 [INFO ] org.kde.pim.akonadiserver: Subscriber
"SpecialCollectionsMonitor - 94908118206576" disconnected
2021-08-09T14:00:26 [INFO ] org.kde.pim.akonadiserver: Subscriber
"FilterManagerTagMonitor - 94908124039120" disconnected
2021-08-09T14:00:26 [INFO ] org.kde.pim.akonadiserver: Subscriber
"TagActionManagerMonitor - 94908124186832" disconnected
This even happens with a completely new user set up. The directory structure as
present on the IMAP server is correctly created in KMAIL upon setup, but
retrieving messages fails with the above error.
STEPS TO REPRODUCE
1. Try to get new mail from imap server
OBSERVED RESULT
KMAIL states "failed to append item" and does not show emails coming in upon
sync; as a result all email folders are empty and stay empty when setting up as
a new user.
EXPECTED RESULT
Emails actually show up in Kmail
I´ĺl happily create any logfile or anything else you need to squash this ugly
bug
OS: OpenSuse Tumbleweed
KDE:5.22.4
KDE Framework: 5.84.0
--
You are receiving this mail because:
You are watching all bug changes.
[Akonadi] [Bug 420495] New: Akonadi Crashes upon removal of duplicates in folder
https://bugs.kde.org/show_bug.cgi?id=420495 Bug ID: 420495 Summary: Akonadi Crashes upon removal of duplicates in folder Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: s.pa...@spiekerbros.com Target Milestone: --- Application: akonadiserver (5.13.3 (19.12.3)) Qt Version: 5.14.1 Frameworks Version: 5.69.0 Operating System: Linux 5.6.4-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: As, once again, many duplicates are showing up in some folders I wanted to use the "remove duplicates in folder" functionality. This makes akonadi crash every time. The crash can be reproduced every time. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1292ce6800 (LWP 18221))] Thread 6 (Thread 0x7f12897fa700 (LWP 18231)): #0 0x7f1293a5e629 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f1293a13324 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f1293a1345f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f1295488c0b in QEventDispatcherGlib::processEvents (this=0x7f126c000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f1295430b9b in QEventLoop::exec (this=this@entry=0x7f12897f9da0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #5 0x7f129525b5ce in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #6 0x7f129525c698 in QThreadPrivate::start (arg=0x55c9d81878c0) at thread/qthread_unix.cpp:342 #7 0x7f1294722efa in start_thread () from /lib64/libpthread.so.0 #8 0x7f1295c243bf in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f1289ffb700 (LWP 18230)): #0 0x7f1294729795 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f12952621db in QWaitConditionPrivate::wait (deadline=..., this=0x55c9d8159a30) at thread/qwaitcondition_unix.cpp:146 #2 QWaitCondition::wait (this=, mutex=0x55c9d8187170, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7f1295262299 in QWaitCondition::wait (this=this@entry=0x55c9d8187168, mutex=mutex@entry=0x55c9d8187170, time=time@entry=18446744073709551615) at ../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68 #4 0x55c9d804560c in Akonadi::Server::SearchTaskManager::searchLoop (this=0x55c9d8187140) at /usr/src/debug/akonadi-server-19.12.3-1.1.x86_64/src/server/search/searchtaskmanager.cpp:221 #5 0x7f129545ea19 in QObject::event (this=0x55c9d8187140, e=0x55c9d8187680) at kernel/qobject.cpp:1339 #6 0x7f1295431fdf in doNotify (event=0x55c9d8187680, receiver=0x55c9d8187140) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:153 #7 QCoreApplication::notify (event=0x55c9d8187680, receiver=0x55c9d8187140, this=) at kernel/qcoreapplication.cpp:1168 #8 QCoreApplication::notifyInternal2 (receiver=0x55c9d8187140, event=0x55c9d8187680) at kernel/qcoreapplication.cpp:1092 #9 0x7f1295434794 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x55c9d81872f0) at kernel/qcoreapplication.cpp:1832 #10 0x7f1295489573 in postEventSourceDispatch (s=0x7f1268004fe0) at kernel/qeventdispatcher_glib.cpp:277 #11 0x7f1293a13048 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #12 0x7f1293a133d0 in ?? () from /usr/lib64/libglib-2.0.so.0 #13 0x7f1293a1345f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #14 0x7f1295488bee in QEventDispatcherGlib::processEvents (this=0x7f1268000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #15 0x7f1295430b9b in QEventLoop::exec (this=this@entry=0x7f1289ffada0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #16 0x7f129525b5ce in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #17 0x7f129525c698 in QThreadPrivate::start (arg=0x55c9d8187240) at thread/qthread_unix.cpp:342 #18 0x7f1294722efa in start_thread () from /lib64/libpthread.so.0 #19 0x7f1295c243bf in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f128a7fc700 (LWP 18229)): [KCrash Handler] #6 0x7f12952dca4e in std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x0) at /usr/include/c++/9/bits/atomic_base.h:413 #7 QAtomicOps::loadRelaxed (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239 #8 QBasicAtomicInteger::loadRelaxed (this=0x0) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:107 #9 QtPrivate::RefCount::deref
[plasmashell] [Bug 419103] New: Clicking on Spotify icon in task bar causes crash
https://bugs.kde.org/show_bug.cgi?id=419103 Bug ID: 419103 Summary: Clicking on Spotify icon in task bar causes crash Product: plasmashell Version: 5.18.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: s.pa...@spiekerbros.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.18.3) Qt Version: 5.14.1 Frameworks Version: 5.67.0 Operating System: Linux 5.5.9-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Wanting to restart a song, clicked on the player icon (spotify) in taskbar; plasma crashed. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4139f48800 (LWP 6063))] Thread 13 (Thread 0x7f40e5f7e700 (LWP 12977)): #0 0x7f413e684acf in poll () at /lib64/libc.so.6 #1 0x7f411c0c34f2 in () at /usr/lib64/libpulse.so.0 #2 0x7f411c0b4e39 in pa_mainloop_poll () at /usr/lib64/libpulse.so.0 #3 0x7f411c0b54bf in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0 #4 0x7f411c0b5570 in pa_mainloop_run () at /usr/lib64/libpulse.so.0 #5 0x7f411c0c3439 in () at /usr/lib64/libpulse.so.0 #6 0x7f40ffdfad78 in () at /usr/lib64/pulseaudio/libpulsecommon-13.0.so #7 0x7f413b6b2efa in start_thread () at /lib64/libpthread.so.0 #8 0x7f413e68f3bf in clone () at /lib64/libc.so.6 Thread 12 (Thread 0x7f411e67a700 (LWP 6616)): #0 0x7f413e684acf in poll () at /lib64/libc.so.6 #1 0x7f413a9ce2fe in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f413a9ce41f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f413c2a0c6b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f410400f8d0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f413c248bfb in QEventLoop::exec(QFlags) (this=this@entry=0x7f411e679d60, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #5 0x7f413c07362e in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #6 0x7f40f978ee48 in KCupsConnection::run() () at /usr/lib64/libkcupslib.so #7 0x7f413c0746f8 in QThreadPrivate::start(void*) (arg=0x5589674bc490) at thread/qthread_unix.cpp:342 #8 0x7f413b6b2efa in start_thread () at /lib64/libpthread.so.0 #9 0x7f413e68f3bf in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7f411ee7b700 (LWP 6319)): #0 0x7f413e684acf in poll () at /lib64/libc.so.6 #1 0x7f413a9ce2fe in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f413a9ce41f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f413c2a0c6b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f41000549b0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f413c248bfb in QEventLoop::exec(QFlags) (this=this@entry=0x7f411ee7ad60, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #5 0x7f413c07362e in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #6 0x7f413dcc10e6 in () at /usr/lib64/libQt5Quick.so.5 #7 0x7f413c0746f8 in QThreadPrivate::start(void*) (arg=0x558966ba25c0) at thread/qthread_unix.cpp:342 #8 0x7f413b6b2efa in start_thread () at /lib64/libpthread.so.0 #9 0x7f413e68f3bf in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7f411700 (LWP 6251)): #0 0x7f413a9cd704 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #1 0x7f413a9ce22b in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f413a9ce41f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f413c2a0c6b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f410c000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f413c248bfb in QEventLoop::exec(QFlags) (this=this@entry=0x7f411fffeda0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #5 0x7f413c07362e in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #6 0x7f413c0746f8 in QThreadPrivate::start(void*) (arg=0x558964e91230) at thread/qthread_unix.cpp:342 #7 0x7f413b6b2efa in start_thread () at /lib64/libpthread.so.0 #8 0x7f413e68f3bf in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7f4124f11700 (LWP 6250)): #0 0x7f413e6804fc in read () at /lib64/libc.so.6 #1 0x7f413aa151df in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f413a9cde57 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f413a9ce2a2 in () at /usr/lib64/libglib-2.0.so.0 #4
[kio-extras] [Bug 417336] Trying to use sftp causes crash in kdeinit5
https://bugs.kde.org/show_bug.cgi?id=417336 Frits Spieker changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Frits Spieker --- Just got quite the system update (1400 files or so) and I am happy to announce that this solved the problem. sftp is working again. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 417336] New: Trying to use sftp causes crash in kdeinit5
https://bugs.kde.org/show_bug.cgi?id=417336 Bug ID: 417336 Summary: Trying to use sftp causes crash in kdeinit5 Product: kio-extras Version: 19.12 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: SFTP Assignee: plasma-b...@kde.org Reporter: s.pa...@spiekerbros.com Target Milestone: --- SUMMARY Trying to use sftp (Dolphin, Konqueror, or any other kde-based program) to access remote locations causes a crash in kdeinit5. Those remote locations that also support fish are still accessible; it is only sftp which causes the crash STEPS TO REPRODUCE 1. try to access a remote location using sftp OBSERVED RESULT kdeinit5 crashes and dolphin (or other program) shows "unknown error". Keeping the Dolphin window open will result in repeated crashes. EXPECTED RESULT dolphin shows the contents of the remote folder SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSuse Tumbleweed KDE Plasma Version: 5.17.5-2.2 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION Application: kdeinit5 (kdeinit5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f600da06580 (LWP 30188))] Thread 2 (Thread 0x7f600ab1f700 (LWP 30190)): #0 0x7f6010219abf in poll () from /lib64/libc.so.6 #1 0x7f600de8f2ee in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f600de8f40f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f600f5dac6b in QEventDispatcherGlib::processEvents (this=0x7f6004000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f600f582bfb in QEventLoop::exec (this=this@entry=0x7f600ab1ed70, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #5 0x7f600f3ad62e in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #6 0x7f600ba4d507 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7f600f3ae6f8 in QThreadPrivate::start (arg=0x7f600bacfda0) at thread/qthread_unix.cpp:342 #8 0x7f600e989f2a in start_thread () from /lib64/libpthread.so.0 #9 0x7f601022438f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f600da06580 (LWP 30188)): [KCrash Handler] #6 0x7f600b7b5044 in EVP_CIPHER_CTX_ctrl (ctx=0x0, type=type@entry=19, arg=arg@entry=1, ptr=ptr@entry=0x7ffced1913c7) at crypto/evp/evp_enc.c:648 #7 0x7f600acd13ae in evp_cipher_aead_encrypt (cipher=0x7f60040061e0, in=0x5562fe0afc70, out=0x5562fe0a4e10, len=36, tag=0x5562fe073320 "", seq=) at /usr/src/debug/libssh-0.9.3-1.1.x86_64/src/libcrypto.c:754 #8 0x7f600ace0382 in ssh_packet_encrypt (len=, data=0x5562fe0afc70, session=0x5562fe072b30) at /usr/src/debug/libssh-0.9.3-1.1.x86_64/src/packet_crypt.c:176 #9 packet_send2 (session=session@entry=0x5562fe072b30) at /usr/src/debug/libssh-0.9.3-1.1.x86_64/src/packet.c:1684 #10 0x7f600ace0a38 in ssh_packet_send (session=0x5562fe072b30) at /usr/src/debug/libssh-0.9.3-1.1.x86_64/src/packet.c:1810 #11 0x7f600acf357f in ssh_disconnect (session=0x5562fe072b30) at /usr/src/debug/libssh-0.9.3-1.1.x86_64/src/client.c:692 #12 0x7f600bdf142a in sftpProtocol::closeConnection (this=0x7ffced191bd0) at /usr/src/debug/kio-extras5-19.12.1-1.1.x86_64/sftp/kio_sftp.cpp:1282 #13 0x7f600bdf80f0 in sftpProtocol::sftpOpenConnection (this=this@entry=0x7ffced191bd0, info=...) at /usr/src/debug/kio-extras5-19.12.1-1.1.x86_64/sftp/kio_sftp.cpp:635 #14 0x7f600bdf84f0 in sftpProtocol::openConnection (this=0x7ffced191bd0) at /usr/src/debug/kio-extras5-19.12.1-1.1.x86_64/sftp/kio_sftp.cpp:686 #15 0x7f600bdf1782 in sftpProtocol::sftpLogin (this=this@entry=0x7ffced191bd0) at /usr/src/debug/kio-extras5-19.12.1-1.1.x86_64/sftp/kio_sftp.cpp:2604 #16 0x7f600bdf3513 in sftpProtocol::listDir (this=0x7ffced191bd0, url=...) at /usr/src/debug/kio-extras5-19.12.1-1.1.x86_64/sftp/kio_sftp.cpp:2150 #17 0x7f600becf3a6 in KIO::SlaveBase::dispatch (this=0x7ffced191bd0, command=71, data=...) at /usr/src/debug/kio-5.66.0-1.1.x86_64/src/core/slavebase.cpp:1247 #18 0x7f600bed in KIO::SlaveBase::dispatchLoop (this=this@entry=0x7ffced191bd0) at /usr/src/debug/kio-5.66.0-1.1.x86_64/src/core/slavebase.cpp:338 #19 0x7f600bdfe45b in kdemain (argc=, argv=) at /usr/src/debug/kio-extras5-19.12.1-1.1.x86_64/sftp/kio_sftp.cpp:77 #20 0x5562fd04847c in launch (argc=4, _name=0x5562fe064318 "/usr/lib64/qt5/plugins/kf5/kio/sftp.so", args=, cwd=, envc=0, envs=, reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x5562fd04a175 "0") at /usr/src/debug/kinit-5.66.0-1.1.x86_64/src/kdeinit/kinit.cpp:704 #21 0x5562fd049288 in handle_launcher_request (sock=, who=) at /usr/src/debug/kinit-5.66.0-1.1.x86_64/src/kdeinit/kinit.cpp:1142 #22 0x5562fd049c64 in handle_requests (waitForPid=0) at
[systemsettings] [Bug 414221] New: System settings crashes when backing out of an option (going back to main menu)
https://bugs.kde.org/show_bug.cgi?id=414221 Bug ID: 414221 Summary: System settings crashes when backing out of an option (going back to main menu) Product: systemsettings Version: 5.17.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: s.pa...@spiekerbros.com Target Milestone: --- Application: systemsettings5 (5.17.2) Qt Version: 5.13.1 Frameworks Version: 5.64.0 Operating System: Linux 5.3.9-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Looking for a setting (themes/ application appearance) settings crashes every time when backing out of a setting (going back to the main menu) The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f087b2d9800 (LWP 12606))] Thread 5 (Thread 0x7f086bef4700 (LWP 12614)): #0 0x7f087be025f4 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f087bdb67fd in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x7f087bdb71ab in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f087bdb739f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f087dfa899b in QEventDispatcherGlib::processEvents (this=0x7f086036b100, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f087df510db in QEventLoop::exec (this=this@entry=0x7f086bef3d80, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #6 0x7f087dd89021 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #7 0x7f087d24a3f5 in ?? () from /usr/lib64/libQt5Qml.so.5 #8 0x7f087dd8a1a2 in QThreadPrivate::start (arg=0x5566556c0440) at thread/qthread_unix.cpp:360 #9 0x7f087c6f1f2a in start_thread () from /lib64/libpthread.so.0 #10 0x7f087f66e4af in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f0872189700 (LWP 12609)): #0 0x7f087c6f86a5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f087264e24b in ?? () from /usr/lib64/dri/i965_dri.so #2 0x7f087264e147 in ?? () from /usr/lib64/dri/i965_dri.so #3 0x7f087c6f1f2a in start_thread () from /lib64/libpthread.so.0 #4 0x7f087f66e4af in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f0873fff700 (LWP 12608)): #0 0x7f087be025d9 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f087bdb7264 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f087bdb739f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f087dfa899b in QEventDispatcherGlib::processEvents (this=0x7f086c000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f087df510db in QEventLoop::exec (this=this@entry=0x7f0873ffed70, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7f087dd89021 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7f087ce894f6 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7f087dd8a1a2 in QThreadPrivate::start (arg=0x7f087cf0bd80) at thread/qthread_unix.cpp:360 #8 0x7f087c6f1f2a in start_thread () from /lib64/libpthread.so.0 #9 0x7f087f66e4af in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f0879541700 (LWP 12607)): #0 0x7f087f663bdf in poll () from /lib64/libc.so.6 #1 0x7f087c6c1742 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f087c6c23fa in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f087974bf90 in QXcbEventQueue::run (this=0x556654efebc0) at qxcbeventqueue.cpp:228 #4 0x7f087dd8a1a2 in QThreadPrivate::start (arg=0x556654efebc0) at thread/qthread_unix.cpp:360 #5 0x7f087c6f1f2a in start_thread () from /lib64/libpthread.so.0 #6 0x7f087f66e4af in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f087b2d9800 (LWP 12606)): [KCrash Handler] #6 0x7f087e7f7fc8 in vtable for QStandardItemModel () from /usr/lib64/libQt5Gui.so.5 #7 0x7f087df83611 in QObject::property (this=0x5566555bf650, name=0x7f086abd6264 "gridUnit") at kernel/qobject.cpp:3974 #8 0x7f086abb71e0 in ?? () from /usr/lib64/qt5/qml/org/kde/kirigami.2/libkirigamiplugin.so #9 0x7f087d23289f in QQmlObjectCreator::createInstance(int, QObject*, bool) () from /usr/lib64/libQt5Qml.so.5 #10 0x7f087d230eaa in QQmlObjectCreator::setPropertyBinding(QQmlPropertyData const*, QV4::CompiledData::Binding const*) () from /usr/lib64/libQt5Qml.so.5 #11 0x7f087d2315fa in QQmlObjectCreator::setupBindings(bool) () from /usr/lib64/libQt5Qml.so.5 #12 0x7f087d23225b in
[korganizer] [Bug 406411] Korganizer daemon closes when plasma starts
https://bugs.kde.org/show_bug.cgi?id=406411 Frits Spieker changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #14 from Frits Spieker --- Hi. I just got an update to the 19. series of KDE on Tumbleweed and now Kontact and Akonadi have been updated as well (5.11), I can happily report that the bug indeed seems to have been fixed. No more crash of the reminder deamon. Suggest to close. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 283682] KMail duplicates filtered messages
https://bugs.kde.org/show_bug.cgi?id=283682 --- Comment #212 from Frits Spieker --- (In reply to Eric Depagne from comment #203) > (In reply to Tristan Miller from comment #202) > > Is this problem still reproducible in the latest version of KMail? There > > haven't been any comments on this bug in over a year; I'm wondering if > > that's because the problem has been fixed or because it has driven most of > > the user base away. I'd love to return to using KMail but can't as long as > > this message duplication problem persists. (I was getting dozens of > > duplicated messages every day, which was too much to put up with.) > > It has been fixed I believe, since it disappeared from my kmail in 2015. Most definitely not fixed. Still run into it multiple times per day with some messages showing up 5 or more times. Sometimes I just delete the entire folder and filter and just set everything up again. Sometimes seems to do the trick. I have been unable to find any logic behind why some messages get duplicated where others don't (in the same folder). -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 406411] Korganizer daemon closes when plasma starts
https://bugs.kde.org/show_bug.cgi?id=406411 --- Comment #4 from Frits Spieker --- That was fast ;-) -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 406411] Korganizer daemon closes when plasma starts
https://bugs.kde.org/show_bug.cgi?id=406411 --- Comment #2 from Frits Spieker --- Created attachment 119340 --> https://bugs.kde.org/attachment.cgi?id=119340=edit Korganizer Reminder Daemon crashes at plasma login. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 406411] Korganizer daemon closes when plasma starts
https://bugs.kde.org/show_bug.cgi?id=406411 Frits Spieker changed: What|Removed |Added CC||s.pa...@spiekerbros.com --- Comment #1 from Frits Spieker --- I just updated my Tumbleweed as well and get exactly the same crash. I'll upload a crash-log. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 405434] KMail crashes when trying to switch on add-blocker
https://bugs.kde.org/show_bug.cgi?id=405434 --- Comment #3 from Frits Spieker --- Hi, Still crashes reliably. Even a fresh install of Tumbleweed did not help. It's a bug I totally can work around and live with, so please feel free to put it on hold. Cheers, Frits -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 405434] KMail crashes when trying to switch on add-blocker
https://bugs.kde.org/show_bug.cgi?id=405434 --- Comment #2 from Frits Spieker --- Created attachment 119300 --> https://bugs.kde.org/attachment.cgi?id=119300=edit log for Kontact crash whilst enabling add blocker -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 405434] New: KMail crashes when trying to switch on add-blocker
https://bugs.kde.org/show_bug.cgi?id=405434 Bug ID: 405434 Summary: KMail crashes when trying to switch on add-blocker Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: s.pa...@spiekerbros.com Target Milestone: --- Application: kontact (5.10.2) Qt Version: 5.12.0 Frameworks Version: 5.55.0 Operating System: Linux 4.20.13-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Switched on add-blocker, selected a "addblocking list" from the drop-down list and clicked OK. Crashed immediately. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb22e243f40 (LWP 8736))] Thread 27 (Thread 0x7fb1250f3700 (LWP 9233)): #0 0x7fb23c60f428 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb2361b7c57 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7fb2361b85aa in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7fb2361b8692 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7fb236176131 in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7fb236178c67 in () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7fb236179254 in () at /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7fb2361ba7b1 in () at /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7fb23c608fab in start_thread () at /lib64/libpthread.so.0 #9 0x7fb23d5df6af in clone () at /lib64/libc.so.6 Thread 26 (Thread 0x7fb1e57fa700 (LWP 9227)): #0 0x7fb23c60f428 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb23d91e595 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #2 0x7fb23d91e6c5 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #3 0x7fb23d91c7c2 in () at /usr/lib64/libQt5Core.so.5 #4 0x7fb23d9186e2 in () at /usr/lib64/libQt5Core.so.5 #5 0x7fb23c608fab in start_thread () at /lib64/libpthread.so.0 #6 0x7fb23d5df6af in clone () at /lib64/libc.so.6 Thread 25 (Thread 0x7fb20b7fe700 (LWP 9220)): #0 0x7fb23d5da2f9 in syscall () at /lib64/libc.so.6 #1 0x7fb23d91aa04 in QSemaphore::acquire(int) () at /usr/lib64/libQt5Core.so.5 #2 0x7fb23c75abd4 in () at /usr/lib64/libQt5Network.so.5 #3 0x7fb23d9186e2 in () at /usr/lib64/libQt5Core.so.5 #4 0x7fb23c608fab in start_thread () at /lib64/libpthread.so.0 #5 0x7fb23d5df6af in clone () at /lib64/libc.so.6 Thread 24 (Thread 0x7fb126237700 (LWP 9219)): #0 0x7fb23d5d4ae9 in poll () at /lib64/libc.so.6 #1 0x7fb23bc1f156 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fb23bc1f27c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fb23db22c5b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fb23dacd4fb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fb23d917396 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fb23d9186e2 in () at /usr/lib64/libQt5Core.so.5 #7 0x7fb23c608fab in start_thread () at /lib64/libpthread.so.0 #8 0x7fb23d5df6af in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7fb20a7fc700 (LWP 9024)): #0 0x7fb21830e48f in pa_srbchannel_read () at /usr/lib64/pulseaudio/libpulsecommon-12.2.so #1 0x7fb21830a9f8 in () at /usr/lib64/pulseaudio/libpulsecommon-12.2.so #2 0x7fb21830d74b in () at /usr/lib64/pulseaudio/libpulsecommon-12.2.so #3 0x7fb21830dae9 in () at /usr/lib64/pulseaudio/libpulsecommon-12.2.so #4 0x7fb21830e33a in () at /usr/lib64/pulseaudio/libpulsecommon-12.2.so #5 0x7fb218372ca8 in pa_mainloop_dispatch () at /usr/lib64/libpulse.so.0 #6 0x7fb218372f7c in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0 #7 0x7fb218373020 in pa_mainloop_run () at /usr/lib64/libpulse.so.0 #8 0x7fb218381039 in () at /usr/lib64/libpulse.so.0 #9 0x7fb21831de28 in () at /usr/lib64/pulseaudio/libpulsecommon-12.2.so #10 0x7fb23c608fab in start_thread () at /lib64/libpthread.so.0 #11 0x7fb23d5df6af in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7fb127fff700 (LWP 8789)): #0 0x7fb23d5d4ae9 in poll () at /lib64/libc.so.6 #1 0x7fb23bc1f156 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fb23bc1f27c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fb23db22c5b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fb23dacd4fb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fb23d917396 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fb23d9186e2 in ()
[kontact] [Bug 400901] New: KMail crashes when closing a message window after search
https://bugs.kde.org/show_bug.cgi?id=400901 Bug ID: 400901 Summary: KMail crashes when closing a message window after search Product: kontact Version: 5.9.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: s.pa...@spiekerbros.com Target Milestone: --- Application: kontact (5.9.2) Qt Version: 5.11.2 Frameworks Version: 5.51.0 Operating System: Linux 4.18.15-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Searched for a specific message using Tools > Find Message. Open message (double click on search result), close message (clicking on the "X"), Kmail crashes every time. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f65bb454ec0 (LWP 3656))] Thread 32 (Thread 0x7f646685d700 (LWP 7285)): #0 0x7f65cde608c8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f65c6f25d37 in base::ConditionVariable::TimedWait () at ./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:120 #2 0x7f65c6f27a0a in base::WaitableEvent::TimedWaitUntil () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:221 #3 0x7f65c6f27af2 in base::WaitableEvent::TimedWait () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:161 #4 0x7f65c6f2c8b1 in base::internal::SchedulerWorker::Delegate::WaitForWork () at ./../../3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:171 #5 0x7f65c6f2dd91 in base::internal::SchedulerWorker::Thread::ThreadMain () at ./../../3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:68 #6 0x7f65c6f381c1 in ThreadFunc () at ./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:75 #7 0x7f65cde5a554 in start_thread () from /lib64/libpthread.so.0 #8 0x7f65cefc4ccf in clone () from /lib64/libc.so.6 Thread 31 (Thread 0x7f65957fa700 (LWP 7268)): #0 0x7f65cde608c8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f65c6f25d37 in base::ConditionVariable::TimedWait () at ./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:120 #2 0x7f65c6f27a0a in base::WaitableEvent::TimedWaitUntil () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:221 #3 0x7f65c6f27af2 in base::WaitableEvent::TimedWait () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:161 #4 0x7f65c6f2c8b1 in base::internal::SchedulerWorker::Delegate::WaitForWork () at ./../../3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:171 #5 0x7f65c6f2dd91 in base::internal::SchedulerWorker::Thread::ThreadMain () at ./../../3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:68 #6 0x7f65c6f381c1 in ThreadFunc () at ./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:75 #7 0x7f65cde5a554 in start_thread () from /lib64/libpthread.so.0 #8 0x7f65cefc4ccf in clone () from /lib64/libc.so.6 Thread 30 (Thread 0x7f6476a45700 (LWP 7246)): #0 0x7f65cefba2c9 in poll () from /lib64/libc.so.6 #1 0x7f65cc9fef46 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f65cc9ff06c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f65cf6dfadb in QEventDispatcherGlib::processEvents (this=0x7f657c008d40, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f65cf68cadb in QEventLoop::exec (this=this@entry=0x7f6476a44be0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7f65cf4dbde6 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7f65cf4e59b7 in QThreadPrivate::start (arg=0x5650a2ffb6d0) at thread/qthread_unix.cpp:367 #7 0x7f65cde5a554 in start_thread () from /lib64/libpthread.so.0 #8 0x7f65cefc4ccf in clone () from /lib64/libc.so.6 Thread 29 (Thread 0x7f648938b700 (LWP 3778)): #0 0x7f65cca45426 in g_private_get () from /usr/lib64/libglib-2.0.so.0 #1 0x7f65cca27950 in g_thread_self () from /usr/lib64/libglib-2.0.so.0 #2 0x7f65cc9fdf9e in g_main_context_acquire () from /usr/lib64/libglib-2.0.so.0 #3 0x7f65cc9fee05 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f65cc9ff06c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f65cf6dfadb in QEventDispatcherGlib::processEvents (this=0x7f647c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7f65cf68cadb in QEventLoop::exec (this=this@entry=0x7f648938abe0, flags=..., flags@entry=...) at
[Akonadi] [Bug 398282] Akonadi crashes frequently since upgrade to 5.9.0
https://bugs.kde.org/show_bug.cgi?id=398282 --- Comment #3 from Frits Spieker --- Hi. Updated PC today and so far (knock on wood) it seems indeed to be fixed. So far can consider as resolved indeed. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 398282] New: Akonadi crashes frequently since upgrade to 5.9.0
https://bugs.kde.org/show_bug.cgi?id=398282 Bug ID: 398282 Summary: Akonadi crashes frequently since upgrade to 5.9.0 Product: Akonadi Version: 5.9.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: libakonadi Assignee: kdepim-b...@kde.org Reporter: s.pa...@spiekerbros.com Target Milestone: --- Created attachment 114789 --> https://bugs.kde.org/attachment.cgi?id=114789=edit backtrace for akonadi crash whilst trying to filter messages Application: akonadiserver (5.9.0) Qt Version: 5.11.1 Frameworks Version: 5.49.0 Operating System: Linux 4.18.5-1-default x86_64 Distribution: "openSUSE Tumbleweed" The backtrace is too long to be reported via the automatic reporting wizzard nor can it be pasted into the comment window. (too many characters) -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 393572] New: KTorrent crashes upon closing
https://bugs.kde.org/show_bug.cgi?id=393572 Bug ID: 393572 Summary: KTorrent crashes upon closing Product: ktorrent Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: s.pa...@spiekerbros.com Target Milestone: --- Application: ktorrent (5.1.0) Qt Version: 5.10.0 Frameworks Version: 5.45.0 Operating System: Linux 4.16.3-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Selecting "Quit" in the file menu whilst in the "Plugins" screen crashes the application. Closing it using the "X" on top of the window, just closes the program without crashing. Tried multiple times; crashes each time via the "quit" option in the file menu. -- Backtrace: Application: KTorrent (ktorrent), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f860ad16800 (LWP 13840))] Thread 5 (Thread 0x7f85c533d700 (LWP 14170)): #0 0x7f8604e5a179 in poll () at /lib64/libc.so.6 #1 0x7f85fc609831 in () at /usr/lib64/libpulse.so.0 #2 0x7f85fc5fb1f0 in pa_mainloop_poll () at /usr/lib64/libpulse.so.0 #3 0x7f85fc5fb880 in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0 #4 0x7f85fc5fb910 in pa_mainloop_run () at /usr/lib64/libpulse.so.0 #5 0x7f85fc609779 in () at /usr/lib64/libpulse.so.0 #6 0x7f85fa09d498 in () at /usr/lib64/pulseaudio/libpulsecommon-11.1.so #7 0x7f8600b2159b in start_thread () at /lib64/libpthread.so.0 #8 0x7f8604e64a1f in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f85d9608700 (LWP 13871)): #0 0x7f8604e5a179 in poll () at /lib64/libc.so.6 #1 0x7f85cb553600 in __res_context_send () at /lib64/libresolv.so.2 #2 0x7f85cb551183 in __res_context_query () at /lib64/libresolv.so.2 #3 0x7f85cb7651a6 in _nss_dns_gethostbyaddr2_r () at /lib64/libnss_dns.so.2 #4 0x7f85cb7653e3 in _nss_dns_gethostbyaddr_r () at /lib64/libnss_dns.so.2 #5 0x7f8604e76811 in gethostbyaddr_r@@GLIBC_2.2.5 () at /lib64/libc.so.6 #6 0x7f8604e7ed30 in gni_host_inet_name.isra () at /lib64/libc.so.6 #7 0x7f8604e7f483 in getnameinfo () at /lib64/libc.so.6 #8 0x7f860a56d636 in () at /usr/lib64/libKF5Torrent.so.6 #9 0x7f860a56d6eb in () at /usr/lib64/libKF5Torrent.so.6 #10 0x7f860a56da53 in () at /usr/lib64/libKF5Torrent.so.6 #11 0x7f8605b16ba0 in QThreadPrivate::start(void*) (arg=0x564eef480990) at thread/qthread_unix.cpp:376 #12 0x7f8600b2159b in start_thread () at /lib64/libpthread.so.0 #13 0x7f8604e64a1f in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f85f0c2a700 (LWP 13844)): #0 0x7f85fe1fbe44 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f85fe1b5978 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f85fe1b635b in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f85fe1b653c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f8605d43a2b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f85e8000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f8605cea95a in QEventLoop::exec(QFlags) (this=this@entry=0x7f85f0c29dc0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f8605b11baa in QThread::exec() (this=) at thread/qthread.cpp:522 #7 0x7f8605b16ba0 in QThreadPrivate::start(void*) (arg=0x564eeeac5680) at thread/qthread_unix.cpp:376 #8 0x7f8600b2159b in start_thread () at /lib64/libpthread.so.0 #9 0x7f8604e64a1f in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f85f22d3700 (LWP 13842)): #0 0x7f8604e5a179 in poll () at /lib64/libc.so.6 #1 0x7f85fe1b6429 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f85fe1b653c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f8605d43a2b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f85e4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f8605cea95a in QEventLoop::exec(QFlags) (this=this@entry=0x7f85f22d2d90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f8605b11baa in QThread::exec() (this=) at thread/qthread.cpp:522 #6 0x7f860715da35 in () at /usr/lib64/libQt5DBus.so.5 #7 0x7f8605b16ba0 in QThreadPrivate::start(void*) (arg=0x7f86073cdd60) at thread/qthread_unix.cpp:376 #8 0x7f8600b2159b in start_thread () at /lib64/libpthread.so.0 #9 0x7f8604e64a1f in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f860ad16800 (LWP 13840)): [KCrash Handler] #6 0x7f8605d2b8ed in std::__atomic_base::load(std::memory_order) const (__m=std::memory_order_relaxed, this=0x31) at /usr/include/c++/7/bits/atomic_base.h:396 #7 0x7f8605d2b8ed in QAtomicOps::load(std::atomic
[Akonadi] [Bug 336581] accidental database loss causes Akonadi / KMail to silently break correct folder assignments
https://bugs.kde.org/show_bug.cgi?id=336581 Frits Spieker <s.pa...@spiekerbros.com> changed: What|Removed |Added CC||s.pa...@spiekerbros.com --- Comment #12 from Frits Spieker <s.pa...@spiekerbros.com> --- As to broken architecture... The dreaded KMail hanging with the message "Retrieving message/ folder content screen" showing indefinitely is back. On top of that KMail now always crashes when writing a new email using autofill for the receiver (start typing the email address and when trying to select one of the suggestions made, KMail will crash). I will search if a bug report has been filed for that one and if not I will file it myself. KMail/ Akonadi had been "OK-ish" for a couple of months (to the extent I even removed my backup solution of Thunderbird), but it is back to being near useless again. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 379585] Kontakt crashed upon restarting to get rid of "Retrieving Folder Content" screen
https://bugs.kde.org/show_bug.cgi?id=379585 --- Comment #3 from Frits Spieker <s.pa...@spiekerbros.com> --- Hi, I tried every trick in the book to re-create the bug, but no show. Might be also because since reporting it there were some updates to (among others) akonadi which made things a bit more stable. Consider it closed/ resolved for now. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 379585] Kontakt crashed upon restarting to get rid of "Retrieving Folder Content" screen
https://bugs.kde.org/show_bug.cgi?id=379585 --- Comment #2 from Frits Spieker <s.pa...@spiekerbros.com> --- Will do. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 379585] New: Kontakt crashed upon restarting to get rid of "Retrieving Folder Content" screen
https://bugs.kde.org/show_bug.cgi?id=379585 Bug ID: 379585 Summary: Kontakt crashed upon restarting to get rid of "Retrieving Folder Content" screen Product: kontact Version: 5.4.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: s.pa...@spiekerbros.com Target Milestone: --- Application: kontact (5.4.3) Qt Version: 5.7.1 Frameworks Version: 5.33.0 Operating System: Linux 4.10.12-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: As I was hit again with the "Retrieving Folder Content" on one of the folders which contains duplicates due to the filtering bug, I ran: - akonadictl fsck - akonadictl vacuum - akonadictl restart Closed Kontakt, restarted it which made kontakt crash. The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f43f5b73940 (LWP 18809))] Thread 35 (Thread 0x7f43c11d2700 (LWP 27791)): #0 0x7f43ee43ddb3 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f43e537e052 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f43e538ceb0 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f43e538d3e3 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f43e538699c in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f43ee437537 in start_thread () at /lib64/libpthread.so.0 #6 0x7f43f25a204f in clone () at /lib64/libc.so.6 Thread 34 (Thread 0x7f42b700 (LWP 27789)): #0 0x7f43f25944bd in read () at /lib64/libc.so.6 #1 0x7f43ec22df00 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f43ec1e9562 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f43ec1e9a34 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f43ec1e9bac in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f43f30d31bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f43f307cb1a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f43f2eaa813 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f43f2eaf4c8 in () at /usr/lib64/libQt5Core.so.5 #9 0x7f43ee437537 in start_thread () at /lib64/libpthread.so.0 #10 0x7f43f25a204f in clone () at /lib64/libc.so.6 Thread 33 (Thread 0x7f429047b700 (LWP 22551)): #0 0x7f43ee43d9a6 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f42c9167eb3 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f42c949e2c1 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f43ee437537 in start_thread () at /lib64/libpthread.so.0 #4 0x7f43f25a204f in clone () at /lib64/libc.so.6 Thread 32 (Thread 0x7f4290c7c700 (LWP 22550)): #0 0x7f43ee43d9a6 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f42c9167eb3 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f42c949e2c1 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f43ee437537 in start_thread () at /lib64/libpthread.so.0 #4 0x7f43f25a204f in clone () at /lib64/libc.so.6 Thread 31 (Thread 0x7f429147d700 (LWP 22549)): #0 0x7f43ee43d9a6 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f42c9167eb3 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f42c949e2c1 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f43ee437537 in start_thread () at /lib64/libpthread.so.0 #4 0x7f43f25a204f in clone () at /lib64/libc.so.6 Thread 30 (Thread 0x7f4291c7e700 (LWP 22548)): #0 0x7f43ee43d9a6 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f42c9167eb3 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f42c949e2c1 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f43ee437537 in start_thread () at /lib64/libpthread.so.0 #4 0x7f43f25a204f in clone () at /lib64/libc.so.6 Thread 29 (Thread 0x7f428d79d700 (LWP 22547)): #0 0x7f43ee43d9a6 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f42c9167eb3 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f42c949e2c1 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f43ee437537 in start_thread () at /lib64/libpthread.so.0 #4 0x7f43f25a204f in clone () at /lib64/libc.so.6 Thread 28 (Thread 0x7f4273fff700 (LWP 22546)): #0 0x7f43ee43d9a6 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f42c9167eb3 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f42c949e2c1 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f43ee437537 in start_thread () at /lib64/libpthread.so.0 #4 0x7f43f25a204f in clone () at /lib64/libc.so.6 Thread 27 (Thread 0x7f428c93b700 (LWP 22545)): #0 0x7f43ee43d9a6 in pthread_cond_wait@@GLIBC_2.3.2 ()
[Akonadi] [Bug 283682] KMail duplicates filtered messages
https://bugs.kde.org/show_bug.cgi?id=283682 --- Comment #192 from Frits Spieker <s.pa...@spiekerbros.com> --- Excellent! Good to know there is some progress. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 283682] KMail duplicates filtered messages
https://bugs.kde.org/show_bug.cgi?id=283682 --- Comment #190 from Frits Spieker <s.pa...@spiekerbros.com> --- But is one of the developers actually looking at this? The duplication of the messages, combined with the akonadi hanging itself out to dry when deleting messages (resulting in the famous "retrieving folder content" screen) makes KMail basically unusable. I'm really baffled how such a crucial piece of software (unless developers use other program to read email) can be so broken for so long. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 283682] KMail duplicates filtered messages
https://bugs.kde.org/show_bug.cgi?id=283682 Frits Spieker <s.pa...@spiekerbros.com> changed: What|Removed |Added CC||s.pa...@spiekerbros.com --- Comment #181 from Frits Spieker <s.pa...@spiekerbros.com> --- (In reply to Andreas Mahel from comment #179) > I'm experiencing email duplication after filter activity as well (openSUSE > Tumbleweed, most recent versions). > > The filters move mainly mailing list traffic from a POP3 account into local > sub folders. > > Duplication happens both for automatic filtering as well as executing the > filters manually. > > In most cases, the duplicated entry shows a different size than the original > one (but not always). > > On top, selecting any of the two entries will result in Kmail endlessly > waiting for Akonadi. > > A akonadictl fsck and vacuum does not remove the duplicates; also a "Remove > duplicate emails" from the "Folder" menu does'nt, and ends with an error > message. > > In the meantime I have deleted the Akonadi database several times, as well > as re-created the filters manually, to no avail. > > As a workaround for myself I've written a short SQL script to show / delete > the offending rows from the database (from within akonadiconsole) - this is > tedious, but at least allows me to read all mails. > > (How) can I gather more information about what exactly is going on? Both > Kmail and Akonadi are kind of cryptic in their output - is there a way to > increase verbosity? Exactly as you describe. Sometimes I can get things going again for a short time by doing a restart of akonadi, but lately more often than not this causes akonadi to crash. Weird thing though; in some sub-folders the "delete duplicates" functionality works fine, in other sub-folders (underneath the same account) it will indeed hang everything solid with an error message at the end, just like you describe. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 376808] Akonadi stuck on retrieving folder content, ItemFetchJob Stuck, Failed: Multiple Merge Candidates
https://bugs.kde.org/show_bug.cgi?id=376808 Frits Spieker <s.pa...@spiekerbros.com> changed: What|Removed |Added CC||s.pa...@spiekerbros.com --- Comment #6 from Frits Spieker <s.pa...@spiekerbros.com> --- Same problem here. Updated on OpenSUSE Tumbleweed. The Kmail/ Akonadi combo is very much a "hit and miss" at the moment. Sometimes I can read quite some emails in a row, sometimes I get the "Retrieving Folder Content" message for hours on end. In the past restarting akonadi seemed to help, but no longer. Akonadi is at 5.4.3. I'll be happy to provide any logs, info whatever that could help in fixing this. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 376923] New: Akonadi crashes on restart when KMail hangs on "Retrieving folder content" (POP accounts). Akonadi also creates many dupplicates.
https://bugs.kde.org/show_bug.cgi?id=376923 Bug ID: 376923 Summary: Akonadi crashes on restart when KMail hangs on "Retrieving folder content" (POP accounts). Akonadi also creates many dupplicates. Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: s.pa...@spiekerbros.com Target Milestone: --- Application: akonadiserver (5.4.2) Qt Version: 5.7.1 Frameworks Version: 5.30.0 Operating System: Linux 4.9.11-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: When KMail hangs on "Retrieving Folder content" it sometimes helps to restart akonadi. However, since last update this does not help anymore; akonadi just crashes on the restart. Also, many duplicates and duplicates of duplicates are being created upon filtering. - Unusual behavior I noticed: The crash can be reproduced sometimes. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f63648868c0 (LWP 6998))] Thread 35 (Thread 0x7f62b4ff9700 (LWP 7192)): #0 0x7f635f24af64 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f635f20588a in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f635f2059ac in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f636312418b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7f63630cdaea in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f6362efb813 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7f6362f004c8 in ?? () from /usr/lib64/libQt5Core.so.5 #7 0x7f6361422454 in start_thread () from /lib64/libpthread.so.0 #8 0x7f63625f637f in clone () from /lib64/libc.so.6 Thread 34 (Thread 0x7f62b57fa700 (LWP 7189)): #0 0x7f63625ed66d in poll () from /lib64/libc.so.6 #1 0x7f635f205896 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f635f2059ac in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f636312418b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7f63630cdaea in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f6362efb813 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7f6362f004c8 in ?? () from /usr/lib64/libQt5Core.so.5 #7 0x7f6361422454 in start_thread () from /lib64/libpthread.so.0 #8 0x7f63625f637f in clone () from /lib64/libc.so.6 Thread 33 (Thread 0x7f62b5ffb700 (LWP 7184)): #0 0x7f63625ed66d in poll () from /lib64/libc.so.6 #1 0x7f635f205896 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f635f2059ac in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f636312418b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7f63630cdaea in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f6362efb813 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7f6362f004c8 in ?? () from /usr/lib64/libQt5Core.so.5 #7 0x7f6361422454 in start_thread () from /lib64/libpthread.so.0 #8 0x7f63625f637f in clone () from /lib64/libc.so.6 Thread 32 (Thread 0x7f62b67fc700 (LWP 7180)): #0 0x7f635f24af64 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f635f204d70 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x7f635f2057bb in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f635f2059ac in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f636312418b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f63630cdaea in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7f6362efb813 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #7 0x7f6362f004c8 in ?? () from /usr/lib64/libQt5Core.so.5 #8 0x7f6361422454 in start_thread () from /lib64/libpthread.so.0 #9 0x7f63625f637f in clone () from /lib64/libc.so.6 Thread 31 (Thread 0x7f62b77fe700 (LWP 7176)): [KCrash Handler] #6 0x7f63625415af in raise () from /lib64/libc.so.6 #7 0x7f63625429aa in abort () from /lib64/libc.so.6 #8 0x7f6362b5b69d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib64/libstdc++.so.6 #9 0x7f6362b59676 in ?? () from /usr/lib64/libstdc++.so.6 #10 0x7f6362b596c1 in std::terminate() () from /usr/lib64/libstdc++.so.6 #11 0x7f6362b598d8 in __cxa_throw () from /usr/lib64/libstdc++.so.6 #12 0x7f6363fdfc02 in Akonadi::Protocol::DataStream::operator<< (this=, val=) at
[Akonadi] [Bug 340046] after long inactivity (sleep) mailfilter agent remains at 0% indefinitely (and kmail at "Retrieving folder contents")
https://bugs.kde.org/show_bug.cgi?id=340046 Frits Spieker <s.pa...@spiekerbros.com> changed: What|Removed |Added CC||s.pa...@spiekerbros.com --- Comment #6 from Frits Spieker <s.pa...@spiekerbros.com> --- This ugly bug also rears its head in Opensuse Tumbleweed. akonadi is at version 16.12.1-1.1. As is kmail for that matter. Sometimes restarting akonadi does seem to help but never long. I can normally read some email, but then (without any pattern that I can find) the "retrieving etc" will occupy the message pane. As far as I can tell it most of the times starts when trying to read email from a POP3 account, but when it does it will also block IMAP folders. Any suggestions on producing usable input for debugging very welcome. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 267864] migration of akonadi_mixedmaildir_resource fails
https://bugs.kde.org/show_bug.cgi?id=267864 --- Comment #4 from Frits Spieker <s.pa...@spiekerbros.com> --- AFAIK it works fine now. I have quite some local mail folders and they all show up just fine. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 246195] Cannot create Google Contacts akonadi resource [strlen, strdup,extract_and_check_multi, ..., gcal_get_contacts]
https://bugs.kde.org/show_bug.cgi?id=246195 --- Comment #51 from Frits Spieker <s.pa...@spiekerbros.com> --- No longer present. Works fine now. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 310897] Reading mbox files is extremely slow and often fails to show message body
https://bugs.kde.org/show_bug.cgi?id=310897 --- Comment #4 from Frits Spieker <s.pa...@spiekerbros.com> --- As far as I know the bug is no longer there. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 369118] New: Multiple selection of "find in message" causes crash
https://bugs.kde.org/show_bug.cgi?id=369118 Bug ID: 369118 Summary: Multiple selection of "find in message" causes crash Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: s.pa...@spiekerbros.com Application: kontact (5.3.0 (QtWebEngine)) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.7.3-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I was searching for a specific message so selected "find in message". The "search box" appeared at the bottom of the screen (so far so good). When I clicked "search in message" again, the application crashed. Tried again, but have not yet been able to reproduce. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fbec73f25c0 (LWP 3112))] Thread 41 (Thread 0x7fbd177fe700 (LWP 3258)): #0 0x7fbebfc4b10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fbda9ffb353 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fbdaa331971 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7fbebfc45454 in start_thread () at /lib64/libpthread.so.0 #4 0x7fbec3da03ff in clone () at /lib64/libc.so.6 Thread 40 (Thread 0x7fbd17fff700 (LWP 3257)): #0 0x7fbebfc4b10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fbda9ffb353 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fbdaa331971 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7fbebfc45454 in start_thread () at /lib64/libpthread.so.0 #4 0x7fbec3da03ff in clone () at /lib64/libc.so.6 Thread 39 (Thread 0x7fbd1cdf4700 (LWP 3256)): #0 0x7fbebfc4b10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fbda9ffb353 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fbdaa331971 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7fbebfc45454 in start_thread () at /lib64/libpthread.so.0 #4 0x7fbec3da03ff in clone () at /lib64/libc.so.6 Thread 38 (Thread 0x7fbd1d5f5700 (LWP 3255)): #0 0x7fbebfc4b10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fbda9ffb353 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fbdaa331971 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7fbebfc45454 in start_thread () at /lib64/libpthread.so.0 #4 0x7fbec3da03ff in clone () at /lib64/libc.so.6 Thread 37 (Thread 0x7fbd1ddf6700 (LWP 3254)): #0 0x7fbebfc4b10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fbda9ffb353 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fbdaa331971 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7fbebfc45454 in start_thread () at /lib64/libpthread.so.0 #4 0x7fbec3da03ff in clone () at /lib64/libc.so.6 Thread 36 (Thread 0x7fbd1e5f7700 (LWP 3253)): #0 0x7fbebfc4b10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fbda9ffb353 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fbdaa331971 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7fbebfc45454 in start_thread () at /lib64/libpthread.so.0 #4 0x7fbec3da03ff in clone () at /lib64/libc.so.6 Thread 35 (Thread 0x7fbd1edf8700 (LWP 3252)): #0 0x7fbebfc4b10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fbda9ffa201 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fbdaa331971 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7fbebfc45454 in start_thread () at /lib64/libpthread.so.0 #4 0x7fbec3da03ff in clone () at /lib64/libc.so.6 Thread 34 (Thread 0x7fbd77fff700 (LWP 3251)): #0 0x7fbebfc4b10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fbdaa300c4b in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fbdaa300c89 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7fbebfc45454 in start_thread () at /lib64/libpthread.so.0 #4 0x7fbec3da03ff in clone () at /lib64/libc.so.6 Thread 33 (Thread 0x7fbd6e6ee700 (LWP 3214)): #0 0x7fbec3dacc1f in __libc_enable_asynccancel () at /lib64/libc.so.6 #1 0x7fbec3d976e2 in poll () at /lib64/libc.so.6 #2 0x7fbebeff5016 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fbebeff512c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7fbec48d6aab in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fbd640008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #5 0x7fbec487e6fa in QEventLoop::exec(QFlags) (this=this@entry=0x7fbd6e6edc80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7fbec46a43c3 in QThread::exec() (this=) at thread/qthread.cpp:500 #7 0x7fbec46a92e8 in QThreadPrivate::start(void*) (arg=0x15e3da0) at
[Akonadi] [Bug 367846] KMail2 and akonadiconsole continuously lose connection to akonadi server - happens every 30 secs to 2 minutes.
https://bugs.kde.org/show_bug.cgi?id=367846 --- Comment #5 from Frits Spieker <s.pa...@spiekerbros.com> --- Not to be blunt, but deleting all imap accounts, dropping and recreating the akonadi database and recreating of all imap accounts is not what I would call resolved. It is a messy workaround and a very messy one at that. What about users that also still have pop3 email boxes? What about the less technical inclined? It's a messy workaround which hides a messy bug which is in need of a proper fix. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 367846] KMail2 and akonadiconsole continuously lose connection to akonadi server - happens every 30 secs to 2 minutes.
https://bugs.kde.org/show_bug.cgi?id=367846 Frits Spieker <s.pa...@spiekerbros.com> changed: What|Removed |Added CC||s.pa...@spiekerbros.com --- Comment #1 from Frits Spieker <s.pa...@spiekerbros.com> --- I am "glad" I am not the only one. Have exactly the same error. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 364278] kdenlive crashes whilst starting
https://bugs.kde.org/show_bug.cgi?id=364278 --- Comment #14 from Frits Spieker <s.pa...@spiekerbros.com> --- Hi. I can confirm that all is well again. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 364278] kdenlive crashes whilst starting
https://bugs.kde.org/show_bug.cgi?id=364278 --- Comment #9 from Frits Spieker <s.pa...@spiekerbros.com> --- Hi, Farid might be on to something. I do not have a dedicated graphics card in my PC. I just use the embedded graphics from the Intel processor (i915) Does this help? OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Desktop OpenGL version string: 3.3 (Core Profile) Mesa 11.2.2 OpenGL shading language version string: 3.30 Driver: Intel GPU class: IvyBridge OpenGL version: 3.3 GLSL version: 3.30 Mesa version: 11.2.2 X server version: 1.18.3 Linux kernel version: 4.6.2 Requires strict binding:yes GLSL shaders: yes Texture NPOT support: yes -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 364278] kdenlive crashes whilst starting
https://bugs.kde.org/show_bug.cgi?id=364278 --- Comment #5 from Frits Spieker <s.pa...@spiekerbros.com> --- 6.2.0-70.4 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 364278] kdenlive crashes whilst starting
https://bugs.kde.org/show_bug.cgi?id=364278 --- Comment #3 from Frits Spieker <s.pa...@spiekerbros.com> --- OK. This is weird. I went into the software manager (Yast) to see if there were other version lying around. I downgraded to version 16.04.1-1.1 (from 16.04.2-1.2) and it auto-installed dvbgrab (I think) and now it works. I also tested what happens when I go back again to 16.04.2-1.2 and the result is that it crashes immediately on start-up. Are there any other log-files I can send to help? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 364278] kdenlive crashes whilst starting
https://bugs.kde.org/show_bug.cgi?id=364278 --- Comment #2 from Frits Spieker <s.pa...@spiekerbros.com> --- Not that I know. It is a clean install and the application crashes the very moment I try to start it. (So I do not even get a chance to click anywhere in the screen). -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 364278] kdenlive crashes whilst starting
https://bugs.kde.org/show_bug.cgi?id=364278 Frits Spieker <s.pa...@spiekerbros.com> changed: What|Removed |Added Component|general |User Interface Version|unspecified |16.04.0 Product|kde |kdenlive Platform|unspecified |openSUSE RPMs -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 364278] New: kdenlive crashes whilst starting
https://bugs.kde.org/show_bug.cgi?id=364278 Bug ID: 364278 Summary: kdenlive crashes whilst starting Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: s.pa...@spiekerbros.com Application: kdenlive (16.04.2) Qt Version: 5.6.0 Frameworks Version: 5.22.0 Operating System: Linux 4.6.1-1-default x86_64 Distribution: "openSUSE Tumbleweed (20160422) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: clean desktop, simply try to start kdenlive. Crashes every time. Clean installation of Opensuse Tumbleweed (re-installed yesterday) to see if that woulf fix things. The crash can be reproduced every time. -- Backtrace: Application: Kdenlive (kdenlive), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6fcf48e8c0 (LWP 29920))] Thread 6 (Thread 0x7f6fb8e7d700 (LWP 29921)): #0 0x7f6fc76bc9cd in poll () from /lib64/libc.so.6 #1 0x7f6fc1b353f2 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f6fc1b37147 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f6fbb3dd969 in QXcbEventReader::run (this=0x2b10540) at qxcbconnection.cpp:1325 #4 0x7f6fc80b6b29 in QThreadPrivate::start (arg=0x2b10540) at thread/qthread_unix.cpp:340 #5 0x7f6fc5dc5454 in start_thread () from /lib64/libpthread.so.0 #6 0x7f6fc76c53fd in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f6fb32a7700 (LWP 29922)): #0 0x7f6fc4174754 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f6fc41304ce in g_main_context_acquire () from /usr/lib64/libglib-2.0.so.0 #2 0x7f6fc41312c5 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f6fc41314fc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f6fc82ccc5b in QEventDispatcherGlib::processEvents (this=0x7f6fac0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #5 0x7f6fc827879a in QEventLoop::exec (this=this@entry=0x7f6fb32a6ce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f6fc80b1f2c in QThread::exec (this=) at thread/qthread.cpp:503 #7 0x7f6fc9c8b7b5 in ?? () from /usr/lib64/libQt5DBus.so.5 #8 0x7f6fc80b6b29 in QThreadPrivate::start (arg=0x7f6fc9efad00) at thread/qthread_unix.cpp:340 #9 0x7f6fc5dc5454 in start_thread () from /lib64/libpthread.so.0 #10 0x7f6fc76c53fd in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f6f93f5d700 (LWP 29923)): #0 0x7ffce5d72a50 in clock_gettime () #1 0x7f6fc76d2086 in clock_gettime () from /lib64/libc.so.6 #2 0x7f6fc815ddf6 in qt_clock_gettime (ts=0x7f6f93f5ca90, clock=) at tools/qelapsedtimer_unix.cpp:105 #3 do_gettime (frac=, sec=) at tools/qelapsedtimer_unix.cpp:156 #4 qt_gettime () at tools/qelapsedtimer_unix.cpp:165 #5 0x7f6fc82ca919 in QTimerInfoList::updateCurrentTime (this=this@entry=0x7f6f8c002cd0) at kernel/qtimerinfo_unix.cpp:84 #6 0x7f6fc82cae45 in QTimerInfoList::timerWait (this=0x7f6f8c002cd0, tm=...) at kernel/qtimerinfo_unix.cpp:381 #7 0x7f6fc82cc1be in timerSourcePrepareHelper (timeout=0x7f6f93f5cb44, src=) at kernel/qeventdispatcher_glib.cpp:126 #8 timerSourcePrepare (source=, timeout=0x7f6f93f5cb44) at kernel/qeventdispatcher_glib.cpp:159 #9 0x7f6fc4130a1d in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #10 0x7f6fc4131323 in ?? () from /usr/lib64/libglib-2.0.so.0 #11 0x7f6fc41314fc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #12 0x7f6fc82ccc5b in QEventDispatcherGlib::processEvents (this=0x7f6f8c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #13 0x7f6fc827879a in QEventLoop::exec (this=this@entry=0x7f6f93f5ccf0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #14 0x7f6fc80b1f2c in QThread::exec (this=this@entry=0x51ec490) at thread/qthread.cpp:503 #15 0x7f6fc945ef35 in QQmlThreadPrivate::run (this=0x51ec490) at /usr/src/debug/qtdeclarative-opensource-src-5.6.0/src/qml/qml/ftw/qqmlthread.cpp:141 #16 0x7f6fc80b6b29 in QThreadPrivate::start (arg=0x51ec490) at thread/qthread_unix.cpp:340 #17 0x7f6fc5dc5454 in start_thread () from /lib64/libpthread.so.0 #18 0x7f6fc76c53fd in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f6f9207a700 (LWP 29925)): #0 0x7f6fc76bc9cd in poll () from /lib64/libc.so.6 #1 0x7f6fc41313f4 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f6fc41314fc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f6fc82ccc5b in QEventDispatcherGlib::processEvents (this=0x7f6f880008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #4 0x7f6fc827879a in QEventLoop::exec (this=this@entry=0x7f6f92079cf0, flags=..., flags@entry=...) at
[kdeconnect] [Bug 355015] SFTP: Can't browse files on phone using kdeconnect-kde5
https://bugs.kde.org/show_bug.cgi?id=355015 --- Comment #12 from Frits Spieker <s.pa...@spiekerbros.com> --- There is hope! Well spotted Johannes. -- You are receiving this mail because: You are watching all bug changes.
