KDE 5.3.0 KDE Frameworks 5.9 Netrunner 16 (Kubuntu 15.04) kteatime version 1.3 When run from terminal kteatime runs fine. If launched from the KDE application launcher the Plasma Desktop hard-freezes, requiring a system re-boot from terminal. When run from terminal, no errors are given.
For me, krunner would freeze from starting kteatime until closing it again, after which it would show the error message "KDEInit could not launch '/usr/bin/kteatime'". (With Plasma 5.3.95 and Applications 15.07.90) You should try deleting the line "X-DBUS-StartupType=Multi" (or putting None instead of Multi) at the end of the file /usr/share/applications/org.kde.kteatime.desktop. If your problem is the same as mine, that should fix it. Also, it seems to me (from looking into it quickly) that kteatime doesn't register with D-Bus directly anyway (only saw something for the status notifier item), so this should actually probably not be there.
Hello, same problem, kteatime freezes when is runnig from krunner. Krunner and plasma freeze too. Starting application from terminal works fine. I have seen this bug in KDE4, now I'm runnig plasma 5.4.0 and bug is stil present. Tested with clean profile too. Bug reproducible: Always Steps to reproduce: 1. Start KDE 2. Run krunner 3. Search and run kteatime
Created attachment 94263 [details] Proposed fix for freeze when started from krunner What I described in my first comment should fix the problem with krunner, but I had hoped to get a reply whether this also fixes the originally reported bug, because I am not really sure if it actually is the same. I could always start kteatime without problems from the Application Launcher (if that is supposed to mean the menu plasmoid of that name) and plasma would also not be affected when starting from krunner. Since that was quite some time ago, I also attach the patch corresponding to my comment, but it would be good if someone with the exact problem described in the bug report would check if that is also fixed.
(In reply to Alexander Kowalski from comment #3) > What I described in my first comment should fix the problem with krunner, > but I had hoped to get a reply whether this also fixes the originally > reported bug, because I am not really sure if it actually is the same. Your proposed fix does solve the problem :) > I could always start kteatime without problems from the Application Launcher > (if that is supposed to mean the menu plasmoid of that name) I did indeed mean the application launcher of the same name. > Since that was quite some time ago, I also attach the patch corresponding to > my comment, but it would be good if someone with the exact problem described > in the bug report would check if that is also fixed. It does indeed appear that the patch fixes the problem, for me at least. Thank you. - James
Alexander, thanks for the patch. If possible, please post it to https://git.reviewboard.kde.org/
I had the same problem with Kompare. The proposed patch fixed it.
Adding Andrius, who did the port to Frameworks 5. It seems indeed that kteatime does not expose a dbus interface anymore.
Ok, I committed the patch in http://commits.kde.org/kteatime/d2922c0b8fcf4f500908d826073907ed26453ec7 Thanks for reporting.
(In reply to Andrius Štikonas from comment #8) > Ok, I committed the patch in > http://commits.kde.org/kteatime/d2922c0b8fcf4f500908d826073907ed26453ec7 > > Thanks for reporting. So the removal of dbus interface in the Frameworks version is a planned choice (not questioning, just for reference; the alternative to this problem would have been reenabling the dbus interface). (PS: I think you know and you just forgot, but if you use BUG: nnnnn in a separate line in the commit message, the bug is closed automatically).
Well, dbus interface can be reenabled. But it's probably harder and less safe to do just before the release of 15.12. I also don't know much of dbus myself :(...