| Summary: | kalarm crashes on startup | ||
|---|---|---|---|
| Product: | [Applications] kalarm | Reporter: | Elmar Stellnberger (AT/K) <estellnb> |
| Component: | general | Assignee: | David Jarvie <djarvie> |
| Status: | CLOSED DOWNSTREAM | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
Using the plasma 5 desktop, I couldn't reproduce the crash. Unfortunately the crash trace has no useful information in it which would help to investigate the problem. You seem to be using the KDE 4 version of ktimezoned.desktop, and of kcminit, rather then the KF5 versions - I wonder why, when you're using the KF5 version of KAlarm. Which desktop are you using? Well I am using Xfce4 which makes in turn use of kalarm in its default configuration. How can I do it right if I need to manually start ktimezoned for kde5 (i.e. the same KDE version as of kalarm)? ktimezoned is implemented as a kded plugin in KDE Frameworks 5. It should presumably be possible to run it using the KF5 version of kcminit, but when I try that, it complains that it can't find ktimezoned.desktop. I don't know why that's missing. I suggest asking on the KDE forums or a KDE mailing list (perhaps kde-devel?). I can't guarantee that running the KF5 version of ktimezoned will fix the issue, but it needs to be checked out first, since the issue doesn't seem to exist when running under the Plasma 5 desktop. Hmm; I have now tried to launch kalarm5 under a readily-booted KDE5 desktop and it still gives me the same error message: 'can not access ktimezoned' while being restricted to use of UTC only. However looking under systemsettings/KDE services it claims the TimeZone service to be up and running. It turns out that kalarm 15.12 requires the KDE Frameworks 5 version of ktimezoned, which is provided by the plasma-workspace package (in Debian/Ubuntu - I'm not sure about Archlinux). If this isn't working on your system, it seems likely that it's some kind of packaging problem, since it works fine on a self-compiled system. I raised a bug report for Debian about requiring timezoned. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822061. Closing this bug as "Downstream" since it's a distro packaging issue. |
Process 13909 (kalarm) of user 1000 dumped core. Stack trace of thread 13910: #0 0x00007f075e854b72 _ZN15QGuiApplication23platformNativeInterfaceEv (libQt5Gui.so.5) #1 0x00007f076597996e _ZN8QX11Info7displayEv (/usr/lib/libQt5X11Extras.so.5.5.1) #2 0x00007f075b0812c7 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5) #3 0x00007f075d83c330 __restore_rt (libc.so.6) #4 0x00007f0746fb6379 n/a (n/a) Reproducible: Always Steps to Reproduce: /bin/kcminit /usr/share/kde4/services/kded/ktimezoned.desktop sleep 2 kalarmautostart kalarm --tray using kalarm 15.12.2-1 (ARCH)