Description of problem: kalarm crashes when starting up. Version-Release number of selected component (if applicable): kdepim-4.2.4-1.fc10.i386 How reproducible: always Steps to Reproduce: 1. set an alarm which plays a sound 2. log out 3. log in after alarm time has expired Actual results: $ kalarm <unknown program name>(9208)/ main: Unknown resource type: "alarms" $ QObject: Cannot create children for a parent that is in a different thread. (Parent is Phonon::Xine::MediaObject(0xb532c9c0), parent's thread is AudioThread(0x9dffbd0), current thread is QThread(0x9adc260) KCrash: Application 'kalarm' crashing... sock_file=/home/rstory/.kde/socket-vspx.vb.futz.org/kdeinit4__0 E: core-util.c: Assertion 'pa_close(fds[0]) == 0' failed at pulsecore/core-util.c:2107, function pa_close_pipe(). Aborting. Unable to start Dr. Konqi Expected results: kalarm starts and alarms display Additional info: I am running kalarm under a gnome session... it used to work...
It also crashes on login here (only using alarms that run scripts), but it auto-restarts itself and running from the command line doesn't crash.
mine does crash when started from the command line... it seems to be related to playing sounds.. luckily all the sounds for my alarms are in a directory in my home dir, and if I rename that directory it starts, I get some warnings about missing sounds, and it continues to run...
Thank you for taking the time to report this issue. This is an issue that needs to be addressed by the upstream developers. Please report this at http://bugs.kde.org and then add the upstream report information to this report. We will monitor the upstream report for a resolution to this issue, and will review any bug fixes that become available for consideration in future updates. Setting status to NEEDINFO, and awaiting upstream bug report URL for tracking. Thanks in advance. -- Steven M. Parrish - KDE Triage Master - PackageKit Triager Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
i piggybacked on this one: https://bugs.kde.org/show_bug.cgi?id=199654
and they told me to submit a new one.. in the process of which I found an existing report, which is resolved. Upstream is https://bugs.kde.org/show_bug.cgi?id=194745, and comment 18 is included here: "Fixed, by preventing more than one audio thread being created at any one time. This has the benefit (apart from fixing the crash) that KAlarm won't play two different audio files at the same time! Fixed for KDE 4.3.0, and in KDE 4.2 branch (SVN commits 981995, 981995)." I can confirm this.. i created a new alarm with a sound, quit until it had expired, and it worked fine. i created a second alarm with a sound, quit until time for both had expired, and when i ran kalarm again, kablooey...
Excellent, we'll pick up this fix in 4.3.0
Consistently setting the status of everything blocked by KDE 4.3.0 to ON_QA. I'll mass-change them to CLOSED ERRATA once the update hits stable.
This issue should be resolved in Fedora 10 and 11 with the KDE 4.3.0 update, which just got pushed to stable. If the issue persists after upgrading to KDE 4.3.0, please report that fact in this bug report.