It dumps core as in coredumpctl. No crash happened. I've seen the behaviors before it dumps core albeit every processes work flawlessly. It'd be good I can be instructed to hunt this happening.
If it's dumping cores a crash is happening. Why do you think there isn't one?
I have .lz4 core files. There's no crashes just coredumpctl things.
Came here to report the same thing, i encountered this in opensuse tumbleweed, i haven't experienced any "weird" noticeable desktop behavior but since its happening better safe than sorry. I ran "sudo coredumpctl gdb /usr/bin/kactivitymanagerd" got this backtrace: #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #1 0x00007f12504376b1 in __GI_abort () at abort.c:79 #2 0x00007f1250be8b61 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib64/libQt5Core.so.5 #3 0x00007f1250bf78cd in QThread::~QThread() () from /usr/lib64/libQt5Core.so.5 #4 0x00007f123e5e3af9 in ResourceScoreMaintainer::Private::~Private (this=0x5594d44161b0, __in_chrg=<optimized out>) at /usr/src/debug/kactivitymanagerd-5.11.90git.20171205T202630~f28f917/src/service/plugins/sqlite/ResourceScoreMaintainer.cpp:62 #5 0x00007f1250438ce8 in __run_exit_handlers (status=0, listp=0x7f12507b46f8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:83 #6 0x00007f1250438d3a in __GI_exit (status=<optimized out>) at exit.c:105 #7 0x00007f1250420f51 in __libc_start_main (main=0x5594d393fe80 <main(int, char**)>, argc=2, argv=0x7fff09dc7f98, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff09dc7f88) at ../csu/libc-start.c:342 #8 0x00005594d394082a in _start () at ../sysdeps/x86_64/start.S:120
Can you post the console output?
(In reply to Ivan Čukić from comment #4) > Can you post the console output? I am assuming you mean the output of "sudo coredumpctl gdb /usr/bin/kactivitymanagerd" https://pastebin.com/pzyQnMtC
Sorry, I wasn't precise. If QMessageLogger::fatal was called, it should have written the message passed to the fatal function to the stderr. Can you just execute kactivitymanagerd in console and report its output?
Just right now, I encountered this bug. I was watching a movie in full screen and when I switch back to normal screen, every application has void of title bars, unresponsive, and can't be closed. Every animation is gone. I still have access to start menu and log out and back in. No dr. konqi. Coredumpctl show it is /bin/kactivitymanagered.
(In reply to Ivan Čukić from comment #6) > Sorry, I wasn't precise. If QMessageLogger::fatal was called, it should have > written the message passed to the fatal function to the stderr. > > Can you just execute > kactivitymanagerd > in console and report its output? Running it, kactivitymanagerd, shows not error, it says its already running. Stopping it, "kactivitymanagerd stop" and running it again shows: joder@linux-7q70:~> kactivitymanagerd Config timer connecting... Setting the name of 0x561592ae0db0 to "org.kde.ActivityManager.Resources.Scoring" Creating directory: "/home/joder/.local/share/kactivitymanagerd/resources/" KActivities: Database connection: "kactivities_db_resources_140138526054592_readwrite" query_only: QVariant(qlonglong, 0) journal_mode: QVariant(QString, "wal") wal_autocheckpoint: QVariant(qlonglong, 100) synchronous: QVariant(qlonglong, 1) Setting the name of 0x561592b2c7b0 to "org.kde.ActivityManager.ActivityTemplates" Setting the name of 0x561592b2fe40 to "org.kde.ActivityManager.RunApplication" Service started, version: 7.0.0 Cleaning up...
I think i may have found a possible cause for the dumps or it may have been a entirely different thing/bug. Just recently i noticed favorites and recently used files in all the launchers was disappearing after logging out/rebooting. I though it was a regression and did not mind it much since i am using "unstable" kde packages. But someone suggested that this may be cause by a corruption of the database of kactivitymanagerd. So i stopped kactivitymanagerd, deleted ~/.local/share/kactivitymanagerd then added a new favorite, this recreated the deleted folder and got the thing working again.
One of the issues that happen sometimes is that there is a file system error in the database file. Sadly, we never got to the bottom of it. As for the 'full screen movie' thing - that is a kwin issue while switching compositing on and off.
Works for whom? With what version?
@kts Didn't notice that there are two people reporting - Tony and you. If it still makes problems for you: - can you killall kactivitymanagerd - and start it in terminal with kactivitymanagerd start-daemon - and post the output Then: - killall kactivitymanagerd - can you backup .local/share/kactivitymanagerd/ somewhere and delete the original - restart it with kactivitymanagerd start-daemon - and report what is happening
It dumped core again with 5.12.12 or 5.12.13, I'm not sure as to which because it happened after update to 5.12.13. The result is same. No crash or interference just core dump. killall kactivitymanagered and kactivitymanagered --start-daemon worked smoothly because the crash is intermittent and normally it's fine only occasionally it manifests. Below is the coredumpctl backtrace: PID: 578 (kactivitymanage) UID: 1000 (kts) GID: 1000 (kts) Signal: 11 (SEGV) Timestamp: Mon 2018-03-12 19:10:29 +0630 (4 days ago) Command Line: /usr/bin/kactivitymanagerd start-daemon Executable: /usr/bin/kactivitymanagerd Control Group: /user.slice/user-1000.slice/user@1000.service/dbus.service Unit: user@1000.service User Unit: dbus.service Slice: user-1000.slice Owner UID: 1000 (kts) Boot ID: eaeb0848f43043d4a6cf26bb262bddc1 Machine ID: b623200976654e82b4d9ebb79566209a Hostname: hdd1 Storage: /var/lib/systemd/coredump/core.kactivitymanage.1000.eaeb0848f43043d4a6cf26bb262bddc1.578.1520858429000000.lz4 (inaccessible) Message: Process 578 (kactivitymanage) of user 1000 dumped core. Stack trace of thread 826: #0 0x00007f89fdc4eadc sqlite3DbMallocRawNN (libsqlite3.so.0) #1 0x00007f89fdc8ac95 sqlite3VdbeMemGrow (libsqlite3.so.0) #2 0x00007f89fdc7cfe7 n/a (libsqlite3.so.0) #3 0x00007f89fdc7d8a0 sqlite3VdbeExec (libsqlite3.so.0) #4 0x00007f89fdc84550 sqlite3_step (libsqlite3.so.0) #5 0x00007f89fdee2abe n/a (libqsqlite.so) #6 0x00007f89fdee4333 n/a (libqsqlite.so) #7 0x00007f8a140f7938 _ZN9QSqlQuery4execEv (libQt5Sql.so.5) #8 0x00007f8a14373e26 n/a (kactivitymanagerd_plugin_sqlite.so) #9 0x00007f8a14377c0f n/a (kactivitymanagerd_plugin_sqlite.so) #10 0x00007f8a21bb0b4d n/a (libQt5Core.so.5) #11 0x00007f8a2083c08c start_thread (libpthread.so.0) #12 0x00007f8a214b8e7f __clone (libc.so.6) Stack trace of thread 586: #0 0x00007f8a214ae97b __poll (libc.so.6) #1 0x00007f8a1e2bfff3 n/a (libglib-2.0.so.0) #2 0x00007f8a1e2c010e g_main_context_iteration (libglib-2.0.so.0) #3 0x00007f8a21dfa2f1 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #4 0x00007f8a21d9c3db _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #5 0x00007f8a21bab7ae _ZN7QThread4execEv (libQt5Core.so.5) #6 0x0000560eeb4a15db n/a (kactivitymanagerd) #7 0x00007f8a21bb0b4d n/a (libQt5Core.so.5) #8 0x00007f8a2083c08c start_thread (libpthread.so.0) #9 0x00007f8a214b8e7f __clone (libc.so.6) Stack trace of thread 581: #0 0x00007f8a214ae97b __poll (libc.so.6) #1 0x00007f8a1e2bfff3 n/a (libglib-2.0.so.0) #2 0x00007f8a1e2c010e g_main_context_iteration (libglib-2.0.so.0) #3 0x00007f8a21dfa2f1 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #4 0x00007f8a21d9c3db _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #5 0x00007f8a21bab7ae _ZN7QThread4execEv (libQt5Core.so.5) #6 0x00007f8a2271e416 n/a (libQt5DBus.so.5) #7 0x00007f8a21bb0b4d n/a (libQt5Core.so.5) #8 0x00007f8a2083c08c start_thread (libpthread.so.0) #9 0x00007f8a214b8e7f __clone (libc.so.6) Stack trace of thread 580: #0 0x00007f8a214ae97b __poll (libc.so.6) #1 0x00007f8a20c62180 n/a (libxcb.so.1) #2 0x00007f8a20c63e4b xcb_wait_for_event (libxcb.so.1) #3 0x00007f8a1a1b182a n/a (libQt5XcbQpa.so.5) #4 0x00007f8a21bb0b4d n/a (libQt5Core.so.5) #5 0x00007f8a2083c08c start_thread (libpthread.so.0) #6 0x00007f8a214b8e7f __clone (libc.so.6) Stack trace of thread 583: #0 0x00007f8a214ae97b __poll (libc.so.6) #1 0x00007f8a1e2bfff3 n/a (libglib-2.0.so.0) #2 0x00007f8a1e2c010e g_main_context_iteration (libglib-2.0.so.0) #3 0x00007f8a21dfa2f1 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #4 0x00007f8a21d9c3db _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #5 0x00007f8a21bab7ae _ZN7QThread4execEv (libQt5Core.so.5) #6 0x0000560eeb4a15ab n/a (kactivitymanagerd) #7 0x00007f8a21bb0b4d n/a (libQt5Core.so.5) #8 0x00007f8a2083c08c start_thread (libpthread.so.0) #9 0x00007f8a214b8e7f __clone (libc.so.6) Stack trace of thread 587: #0 0x00007f8a214ae97b __poll (libc.so.6) #1 0x00007f8a1e2bfff3 n/a (libglib-2.0.so.0) #2 0x00007f8a1e2c010e g_main_context_iteration (libglib-2.0.so.0) #3 0x00007f8a21dfa2f1 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #4 0x00007f8a21d9c3db _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #5 0x00007f8a21bab7ae _ZN7QThread4execEv (libQt5Core.so.5) #6 0x0000560eeb4a160b n/a (kactivitymanagerd) #7 0x00007f8a21bb0b4d n/a (libQt5Core.so.5) #8 0x00007f8a2083c08c start_thread (libpthread.so.0) #9 0x00007f8a214b8e7f __clone (libc.so.6) Stack trace of thread 2894: #0 0x00007f8a21486b10 __nanosleep (libc.so.6) #1 0x00007f8a21df9c5f n/a (libQt5Core.so.5) #2 0x0000560eeb4abe1c n/a (kactivitymanagerd) #3 0x00007f8a21bb0b4d n/a (libQt5Core.so.5) #4 0x00007f8a2083c08c start_thread (libpthread.so.0) #5 0x00007f8a214b8e7f __clone (libc.so.6) Stack trace of thread 578: #0 0x00007f8a21476da7 __tzstring_len (libc.so.6) #1 0x00007f8a21478b7f __tzfile_compute (libc.so.6) #2 0x00007f8a21477a70 __tz_convert (libc.so.6) #3 0x00007f8a214761cf ranged_convert (libc.so.6) #4 0x00007f8a21476406 __mktime_internal (libc.so.6) #5 0x00007f8a21bec3b7 n/a (libQt5Core.so.5) #6 0x00007f8a21bef9e9 _ZNK9QDateTime17toMSecsSinceEpochEv (libQt5Core.so.5) #7 0x00007f8a21bf0167 _ZNK9QDateTime8toTime_tEv (libQt5Core.so.5) #8 0x00007f8a1436c6b7 n/a (kactivitymanagerd_plugin_sqlite.so) #9 0x00007f8a1436d4da n/a (kactivitymanagerd_plugin_sqlite.so) #10 0x00007f8a14380a2a n/a (kactivitymanagerd_plugin_sqlite.so) #11 0x00007f8a21dcf112 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5) #12 0x00007f8a232a6fec _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5) #13 0x00007f8a232ae9c6 _ZN12QApplication6notifyEP7QObjectP6QEvent (libQt5Widgets.so.5) #14 0x00007f8a21d9dda0 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5) #15 0x00007f8a21da0a06 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5) #16 0x00007f8a21dfad04 n/a (libQt5Core.so.5) #17 0x00007f8a1e2bfe38 g_main_context_dispatch (libglib-2.0.so.0) #18 0x00007f8a1e2c0081 n/a (libglib-2.0.so.0) #19 0x00007f8a1e2c010e g_main_context_iteration (libglib-2.0.so.0) #20 0x00007f8a21dfa2f1 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #21 0x00007f8a1a239482 n/a (libQt5XcbQpa.so.5) #22 0x00007f8a21d9c3db _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #23 0x00007f8a21da57d8 _ZN16QCoreApplication4execEv (libQt5Core.so.5) #24 0x0000560eeb49f0b7 n/a (kactivitymanagerd) #25 0x00007f8a213e3f4a __libc_start_main (libc.so.6) #26 0x0000560eeb49f31a _start (kactivitymanagerd) As a mention, quite recently every fundamental component of KDE is running flawlessly especially kwin. So far, I only have core dump of kactivitymanagered. If it be fixed, KDE said to be without core dump.
This is now a different issue than the original - the crash is in the sqlite library (sqlite3DbMallocRawNN). I'll try to find the reason for it, but don't get your hopes up because I can not reproduce the issue. One similar crash report was in Chromium and one in Qt. One claims that it has been fixed in latest sqlite https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=288 and one claims that it is not the sqlite problem, but the problem of qsql's driver and threading.
p.s. Which version of Qt are you using?
(In reply to Ivan Čukić from comment #15) > p.s. Which version of Qt are you using? For what is worth i for one, haven't seen this for a while now. When i came here to report it i used to have a good number of kactivitymanagerd core dumps when i ran coredumpctl. Still running tumbleweed with unstable KDE repositories.
That is good to hear. What I'm afraid of is that Qt 5.10 might have introduced a change which might lead to more crashed in sqlite - we'll see. KRunner has a similar report https://bugs.kde.org/show_bug.cgi?id=389782 which was I think wrongly set to 'duplicate'.
Please retry this with a Qt6 based version, thanks!
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.