| Summary: | Couldn't start kalarm. Returns a popped up error message: KDEInit couldn't start /usr/bin/kalarm | ||
|---|---|---|---|
| Product: | [Applications] kalarm | Reporter: | fehlermeldungen |
| Component: | Akonadi | Assignee: | David Jarvie <djarvie> |
| Status: | CLOSED DOWNSTREAM | ||
| Severity: | crash | ||
| Priority: | NOR | ||
| Version: | 2.11 | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | debugging infos from the onboard program cookbug in sabayon linux | ||
The error message about KDEInit not finding /usr/bin/kalarm is not a KAlarm issue - it must be the way the system is set up. This should be reported to Sabayon Linux instead. The fact that you couldn't click on the desktop menu bar while KAlarm was running also looks like a system configuration issue. It seems extremely unlikely that KAlarm could itself have been responsible for preventing the desktop's menu bar from being accessed - there is no mechanism that I know of for it to do such a thing. Again, this should be reported to Sabayon Linux. As you noticed, closing the KAlarm window by clicking the close button does not usually quit the program - it normally minimises it to the system tray. On my system, "kalarm -h" doesn't display any error message, so I can't investigate this issue. Since this is the only bug which is potentially an actual issue with KAlarm, I'm closing this bug report as being for the distro to investigate and fix. The issue with "kalarm -h" should now be fixed in KDE Applications 16.12.2 or 16.12.3 (not sure which release it will get into). The problem was due to differences in how unique applications are handled under KDE Frameworks 5 as compared to KDE 4. Fixed in commit c5897d0eabf515a82a62429a726819cb60e255ae (16.12 branch). |
Created attachment 103648 [details] debugging infos from the onboard program cookbug in sabayon linux Dear team, after my last update in my Sabayon Linux (based on Gentoo) I couldn't start kalarm by clicking on the starter button. It returns me an error message that KDEInit couldn't find /usr/bin/kalarm. It was always reproduceable by clicking on the starter button. By clicking on the main menu kalarm died with no response. Now I found another reproducable thing. When typing kalarm -h in the terminal with the normal user access, it lists the help menu and returns this as an error: "Message recipient disconnected from message bus without replying" If I would only type in the command kalarm, nothing happens. With this I did solve this issue partially by repeating the above step. Another issue seems to be, that if kalarm is now running, I couldn't click on the desktop menu bar. It just works again, when completely finishing the kalarm program, then the error message will be returned again (KDEInit couldn't find /usr/bin/kalarm) although it's there. And after clicking on "OK" I can use my desktop again. But I have to exit it completely and not only press the little "x" (close-button) on the program window itself. After some trial-and-error tests I found this partially solution. BTW, my precise kalarm version is 2.11.11-5 I don't know if it's an akonadi issue though it sometimes returns me also an error message that akonadi control couldn't be loaded. Regards @all