Bug 221322

Summary: Kalarm does not play ogg/mp3/wav sound file
Product: [Applications] kalarm Reporter: Dherik <dherikb>
Component: generalAssignee: David Jarvie <djarvie>
Status: CLOSED DUPLICATE    
Severity: normal CC: slsimic
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In: KDE 4.4.3, KAlarm 2.4.5
Sentry Crash Report:

Description Dherik 2010-01-05 03:38:19 UTC
Version:           2.2.10 (using 4.3.4 (KDE 4.3.4) "release 2", KDE:43 / openSUSE_11.2)
Compiler:          gcc
OS:                Linux (i686) release 2.6.31.5-0.1-desktop

Hi!

When I create a New Alarm, and configure a sound to play, the Kalarm does not play any sound file tested (OGG, WAV and MP3 ). When I try to play, Kalarm appear to play the sound file but the only thing listened is a strange and short sound, a sound like plugging the microphone in PC. Sometimes no sound is heard. The "bip" sound is OK. No error is shown on screen.
Comment 1 David Jarvie 2010-01-05 11:38:35 UTC
Can you confirm that you have tested it with sound files which are more than a few seconds long. I've noticed that very short sound files aren't always played properly.
Comment 2 Dherik 2010-01-11 03:56:22 UTC
Hi David!

I tested with MP3 with more than 3 minutes long and the same problem occur. I tested too with many OGG sounds from folder '/usr/share/sounds' (KDE sounds), like 'KDE-Sys-Log-In.ogg'.
Comment 3 Slobodan Simic 2010-04-02 15:09:57 UTC
I can confirm this bug. Same situations here. Beep works, but custom files will not.
Comment 4 David Jarvie 2010-04-07 23:27:06 UTC
This is likely to be the same as bug 232353, which is fixed for KDE 4.4.3. Once that has been released, and you have updated to KDE 4.4.3 or later, can you please report whether or not the fault still occurs.
Comment 5 David Jarvie 2010-04-08 10:28:22 UTC
I'm marking this as fixed now, since it probably is fixed. If you see the bug again in KDE 4.4.3 or later, please reopen it.

*** This bug has been marked as a duplicate of bug 232353 ***