Bug 390123

Summary: PA /var/log/messages: pulseaudio[4424]: protocol-esound.c: kicked client with invalid authorization key.
Product: [openSUSE] openSUSE 11.0 Reporter: Casual J. Programmer <casualprogrammer>
Component: SoundAssignee: Rodrigo Moya <rodrigo>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: tiwai
Version: Factory   
Target Milestone: ---   
Hardware: x86   
OS: openSUSE 11.0   
Whiteboard:
Found By: Beta-Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: /var/log/messages

Description Casual J. Programmer 2008-05-14 08:48:17 UTC 
After clean network install & update from factory /var/log/messages contains multiple entries stating:

/var/log/messages: pulseaudio[4424]: protocol-esound.c: kicked client with invalid authorization key.

Notebook: Fujitsu Siemens Amilo Si 1520
Graphics: Fujitsu Siemens Mobile 945GM/GMS/GME, 943/940GML Express
Monitor:  QUANTADISPLAY LCD Monitor 1280x800@60Hz
Wireless: Intel PRO/Wireless 3945ABG Network Connection
Sound:    82801G (ICH7 Family) High Definition Audio Controller
Desktop:  gnome-desktop-2.22.1-17
YaST GUI: yast2-qt-2.16.45-4
OS:       openSUSE 11.0 (i586) Beta3 VERSION = 11.0
Kernel:   2.6.25.3-2-pae

rpm -qa | grep pulse | sort

gstreamer-0_10-pulse-0.9.7-42.pm.1
libpulse0-0.9.10-14
libpulse-browse0-0.9.10-14
libpulsecore4-0.9.10-14
libpulse-mainloop-glib0-0.9.10-14
pulseaudio-0.9.10-14
pulseaudio-esound-compat-0.9.10-14
pulseaudio-module-bluetooth-0.9.10-14
pulseaudio-module-gconf-0.9.10-14
pulseaudio-module-lirc-0.9.10-14
pulseaudio-module-x11-0.9.10-14
pulseaudio-module-zeroconf-0.9.10-14
pulseaudio-utils-0.9.10-14
Comment 1 Casual J. Programmer 2008-05-14 08:50:10 UTC 
Created attachment 215035 [details]
/var/log/messages
Comment 2 Takashi Iwai 2008-05-14 14:20:35 UTC 
Rodrigo, could you care?
Comment 3 JP Rosevear 2008-05-16 12:38:00 UTC 
*** Bug 391236 has been marked as a duplicate of this bug. ***
Comment 4 JP Rosevear 2008-05-16 12:39:16 UTC 

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