Version: 2.4.11 (using KDE 4.6.5) OS: Linux Sometimes in kalarm, when the alarm activates, it will play the sound from the associated file. Sometimes it won't. I can test a given alarm (using the Try button in the Edit Display Alarm - KAlarm dialog box) several times in a row, and sometimes the music file will play while other times it will be silent. When running KAlarm from the command line, the following error shows up when the alarm does not play: ------------------------- kalarm(25849)/kio (Scheduler) KIO::SchedulerPrivate::doJob: KIO is not thread- safe. QObject::startTimer: QTimer can only be used with threads started with QThread : <repeated six additional times> : kalarm(25849)/kio (KIOJob) KIO::SimpleJob::doKill: KIO::FileJob(0x7f7c1001e980) This is overkill. ------------------------- (The PID is 25849. There is an additional error message that occurs when the pop-up window is closed, but that occurs whether or not the sound plays.). This error occurs with both .mp3 and .ogg files, and with gstreamer, xine, or VLC selected as the Phonon back-end. When the sound file does not play, there is no indication in the pavucontrol Output Devices tab that the signal is making it that far. Reproducible: Sometimes Steps to Reproduce: In KAlarm, select an alarm which plays a sound, and double-click to edit. In the edit dialog box, click the Try button. Actual Results: Alarm box pops up. Sometimes the sound plays, sometimes it doesn't. Expected Results: Alarm box pops up and sound plays. Fedora 15 Dell Optiplex 755 (64 bit) A coworker has almost an identical set-up (KAlarm/KDE/Fedora) and has no problem. This all leads me to believe that there is a race condition occurring.
I can confirm this problem, I found that when I have two audio alarms schedules (in order to replace "snooze" function) the first alarm will play, but when I stop it the second alarm does not work
KAlarm only uses one thread class, and it is a QThread, so it looks like this bug must be in library code - presumably in Phonon somewhere, or in some library called by Phonon. I've also sometimes noticed the error "QObject::startTimer: QTimer can only be used with threads started with QThread" when KAlarm attempts to open the sound file chooser dialog (in kalarm/soundpicker.cpp, function SoundPicker::browseFile()). The relevant code in the function is: QString dir = KGlobal::dirs()->findResourceDir("sound", "KDE-Sys-Warning.ogg"); QString filter = Phonon::BackendCapabilities::availableMimeTypes().join(" "); Then KFileDialog is called. However, when the error message appears, the program hangs. I haven't seen this hang occurring when other file dialogs are invoked, so I suspect that it may be the Phonon call to availableMimeTypes() which hangs. This is still to be confirmed, though. Also, this hang may well only happen the first time this code is executed in a session, even if KAlarm is quit and restarted within the session. As for comment #1, that is a different issue which doesn't belong in this bug report.
Is this still valid with Phonon 4.6.0 or current git and a recent KDE 4.10.x?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!