[kactivitymanagerd] [Bug 388287] coredumpctl confirms /bin/kactivitymanagerd dumps core, everything worked fine

https://bugs.kde.org/show_bug.cgi?id=388287 Eric Edlund changed: What|Removed |Added CC||ericedlund2...@gmail.com

[kactivitymanagerd] [Bug 388287] coredumpctl confirms /bin/kactivitymanagerd dumps core, everything worked fine

https://bugs.kde.org/show_bug.cgi?id=388287 --- Comment #17 from Ivan Čukić --- 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

[kactivitymanagerd] [Bug 388287] coredumpctl confirms /bin/kactivitymanagerd dumps core, everything worked fine

https://bugs.kde.org/show_bug.cgi?id=388287 --- Comment #16 from Tony --- (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

[kactivitymanagerd] [Bug 388287] coredumpctl confirms /bin/kactivitymanagerd dumps core, everything worked fine

https://bugs.kde.org/show_bug.cgi?id=388287 --- Comment #15 from Ivan Čukić --- p.s. Which version of Qt are you using? -- You are receiving this mail because: You are watching all bug changes.

[kactivitymanagerd] [Bug 388287] coredumpctl confirms /bin/kactivitymanagerd dumps core, everything worked fine

https://bugs.kde.org/show_bug.cgi?id=388287 Ivan Čukić changed: What|Removed |Added Status|RESOLVED|REOPENED

[kactivitymanagerd] [Bug 388287] coredumpctl confirms /bin/kactivitymanagerd dumps core, everything worked fine

https://bugs.kde.org/show_bug.cgi?id=388287 --- Comment #13 from kts --- 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

[kactivitymanagerd] [Bug 388287] coredumpctl confirms /bin/kactivitymanagerd dumps core, everything worked fine

https://bugs.kde.org/show_bug.cgi?id=388287 Ivan Čukić changed: What|Removed |Added Resolution|WORKSFORME |WAITINGFORINFO -- You are

[kactivitymanagerd] [Bug 388287] coredumpctl confirms /bin/kactivitymanagerd dumps core, everything worked fine

https://bugs.kde.org/show_bug.cgi?id=388287 --- Comment #12 from Ivan Čukić --- @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

[kactivitymanagerd] [Bug 388287] coredumpctl confirms /bin/kactivitymanagerd dumps core, everything worked fine

https://bugs.kde.org/show_bug.cgi?id=388287 --- Comment #11 from kts --- Works for whom? With what version? -- You are receiving this mail because: You are watching all bug changes.

[kactivitymanagerd] [Bug 388287] coredumpctl confirms /bin/kactivitymanagerd dumps core, everything worked fine

https://bugs.kde.org/show_bug.cgi?id=388287 Ivan Čukić changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[kactivitymanagerd] [Bug 388287] coredumpctl confirms /bin/kactivitymanagerd dumps core, everything worked fine

https://bugs.kde.org/show_bug.cgi?id=388287 --- Comment #9 from Tony --- 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

[kactivitymanagerd] [Bug 388287] coredumpctl confirms /bin/kactivitymanagerd dumps core, everything worked fine

https://bugs.kde.org/show_bug.cgi?id=388287 --- Comment #8 from Tony --- (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

[kactivitymanagerd] [Bug 388287] coredumpctl confirms /bin/kactivitymanagerd dumps core, everything worked fine

https://bugs.kde.org/show_bug.cgi?id=388287 --- Comment #7 from kts --- 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

[kactivitymanagerd] [Bug 388287] coredumpctl confirms /bin/kactivitymanagerd dumps core, everything worked fine

https://bugs.kde.org/show_bug.cgi?id=388287 --- Comment #6 from Ivan Čukić --- 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

[kactivitymanagerd] [Bug 388287] coredumpctl confirms /bin/kactivitymanagerd dumps core, everything worked fine

https://bugs.kde.org/show_bug.cgi?id=388287 --- Comment #5 from Tony --- (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 -- You

[kactivitymanagerd] [Bug 388287] coredumpctl confirms /bin/kactivitymanagerd dumps core, everything worked fine

https://bugs.kde.org/show_bug.cgi?id=388287 --- Comment #4 from Ivan Čukić --- Can you post the console output? -- You are receiving this mail because: You are watching all bug changes.

[kactivitymanagerd] [Bug 388287] coredumpctl confirms /bin/kactivitymanagerd dumps core, everything worked fine

https://bugs.kde.org/show_bug.cgi?id=388287 Tony changed: What|Removed |Added CC||jodr...@live.com --- Comment #3 from

[kactivitymanagerd] [Bug 388287] coredumpctl confirms /bin/kactivitymanagerd dumps core, everything worked fine

https://bugs.kde.org/show_bug.cgi?id=388287 --- Comment #2 from kts --- I have .lz4 core files. There's no crashes just coredumpctl things. -- You are receiving this mail because: You are watching all bug changes.

[kactivitymanagerd] [Bug 388287] coredumpctl confirms /bin/kactivitymanagerd dumps core, everything worked fine

https://bugs.kde.org/show_bug.cgi?id=388287 David Edmundson changed: What|Removed |Added CC|