Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 373581 - pulseaudio - Failed to load module module-x11-xsmp
pulseaudio - Failed to load module module-x11-xsmp
Product: Fedora
Classification: Fedora
Component: pulseaudio (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Lennart Poettering
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-11-09 14:50 EST by Sammy
Modified: 2008-04-02 12:16 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-04-02 12:16:11 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Sammy 2007-11-09 14:50:04 EST
Upgrading from f7 to f8 via yum. I installed everything via yum to
resolve dependencies correctly. Initially I had (on x86_64 system):


Then I yum installed "kde-settings-pulseaudio" which brought in:

pulseaudio-libs - 0.9.7-0.17.svn20071017.fc8.x86_64
pulseaudio-utils - 0.9.7-0.17.svn20071017.fc8.x86_64
alsa-plugins-pulseaudio - 1.0.14-5.fc8.x86_64
pulseaudio-module-x11 - 0.9.7-0.17.svn20071017.fc8.x86_64

After this I rebooted the computer. I am using KDE only.
After start arts started crashing. In the /var/log/messages file
I see errors:

Nov  9 13:06:58 compsci pulseaudio[3180]: pid.c: Stale PID file, overwriting.
Nov  9 13:07:00 compsci pulseaudio[3180]: module-x11-xsmp.c: X11 session manager
not running.
Nov  9 13:07:00 compsci pulseaudio[3180]: module.c: Failed to load  module
"module-x11-xsmp" (argument: ""): initialization failed

Is this a problem with KDE using its own session manager instead of X11?
Please reassign to KDE if this is so.
Comment 1 Lennart Poettering 2008-04-02 12:16:11 EDT
The version of PA in rawhide doesn't fail anymore if an X11 xsmp manager is not

Note You need to log in before you can comment on or make changes to this bug.