Bug 133948 - knotify: not playing wav files - frequent crashes
Summary: knotify: not playing wav files - frequent crashes
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: KDE (show other bugs)
Version: Final
Hardware: 32bit SuSE Linux 10.0
: P5 - None : Normal
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-16 02:06 UTC by Spiros Georgaras
Modified: 2005-11-30 13:42 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Spiros Georgaras 2005-11-16 02:06:36 UTC 
knotify does not play any wav file. Checked with Kcontrol's System Notifications and Kmail (new messages event notification). arts system works fine though. 
 
 .xsession-errors says: 
 akode: Guessed format: wav 
 KNotify::playTimeout 
 
 When knotify crashes (randomly), .xsession-errors says: 
 (This time: trying to play an ogg file) 
 
 akode: Guessed format: xiph 
 akode: Could not open auto-sink 
 KCrash: Application 'knotify' crashing... 
 akode: Could not open auto-sink 
 KCrash: Application 'knotify' crashing... 
 X Error: BadWindow (invalid Window parameter) 3 
   Major opcode:  20 
   Minor opcode:  0 
   Resource id:  0x2a00007 
 X Error: BadWindow (invalid Window parameter) 3 
   Major opcode:  20 
   Minor opcode:  0 
   Resource id:  0x2a00007 
 X Error: BadWindow (invalid Window parameter) 3 
   Major opcode:  20 
   Minor opcode:  0 
   Resource id:  0x2a00007 
 X Error: BadWindow (invalid Window parameter) 3 
   Major opcode:  19 
   Minor opcode:  0 
   Resource id:  0x2a00007 
 
Using KDE 3.5-rc1
This was originally reported at kde.bugs.org (http://bugs.kde.org/show_bug.cgi?id=116446), but it is said to be a SUSE breakage
Comment 1 Stephan Kulow 2005-11-30 13:42:34 UTC 
it was just a libakode bug