ubuntu 16.04 (upgraded to 17.10) audio problems - pulseaudio wrong architecture
up vote
0
down vote
favorite
I found my mediaserver with ubuntu 16.04 suddenly having problems with audio.
Running aplay -l I was getting
ALSA lib conf.c:3357:(snd_config_hooks_call) Cannot open shared library libasound_module_conf_pulse.so
ALSA lib control.c:954:(snd_ctl_open_noupdate) Invalid CTL hw:0
I tried to reinstall pulse & alsa, but no luck. Upgrading to 17.10 hasn't been useful on this problem.
But then I found that the pulseaudio & libasound packages installed on my system was for i386 arch, despite of my system running on with 64bit arch.
There hasn't been any way to restore 64bit version through apt, I had to access ubuntu mirrors and download those packages (and the related dependencies) manually: by installing these through dpkg I finally managed to have the audio device correctly working.
My question is: how could it be happened? how could I restore to a normal condition? my first concern is the next update I will need to install for those packages: I guess apt will try to remove amd64 version and to install i386 one at the first update of one of the interested packages.
The only option I have in mind would be to go through a new clean installation...
apt sound pulseaudio 64-bit alsa
add a comment |Â
up vote
0
down vote
favorite
I found my mediaserver with ubuntu 16.04 suddenly having problems with audio.
Running aplay -l I was getting
ALSA lib conf.c:3357:(snd_config_hooks_call) Cannot open shared library libasound_module_conf_pulse.so
ALSA lib control.c:954:(snd_ctl_open_noupdate) Invalid CTL hw:0
I tried to reinstall pulse & alsa, but no luck. Upgrading to 17.10 hasn't been useful on this problem.
But then I found that the pulseaudio & libasound packages installed on my system was for i386 arch, despite of my system running on with 64bit arch.
There hasn't been any way to restore 64bit version through apt, I had to access ubuntu mirrors and download those packages (and the related dependencies) manually: by installing these through dpkg I finally managed to have the audio device correctly working.
My question is: how could it be happened? how could I restore to a normal condition? my first concern is the next update I will need to install for those packages: I guess apt will try to remove amd64 version and to install i386 one at the first update of one of the interested packages.
The only option I have in mind would be to go through a new clean installation...
apt sound pulseaudio 64-bit alsa
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I found my mediaserver with ubuntu 16.04 suddenly having problems with audio.
Running aplay -l I was getting
ALSA lib conf.c:3357:(snd_config_hooks_call) Cannot open shared library libasound_module_conf_pulse.so
ALSA lib control.c:954:(snd_ctl_open_noupdate) Invalid CTL hw:0
I tried to reinstall pulse & alsa, but no luck. Upgrading to 17.10 hasn't been useful on this problem.
But then I found that the pulseaudio & libasound packages installed on my system was for i386 arch, despite of my system running on with 64bit arch.
There hasn't been any way to restore 64bit version through apt, I had to access ubuntu mirrors and download those packages (and the related dependencies) manually: by installing these through dpkg I finally managed to have the audio device correctly working.
My question is: how could it be happened? how could I restore to a normal condition? my first concern is the next update I will need to install for those packages: I guess apt will try to remove amd64 version and to install i386 one at the first update of one of the interested packages.
The only option I have in mind would be to go through a new clean installation...
apt sound pulseaudio 64-bit alsa
I found my mediaserver with ubuntu 16.04 suddenly having problems with audio.
Running aplay -l I was getting
ALSA lib conf.c:3357:(snd_config_hooks_call) Cannot open shared library libasound_module_conf_pulse.so
ALSA lib control.c:954:(snd_ctl_open_noupdate) Invalid CTL hw:0
I tried to reinstall pulse & alsa, but no luck. Upgrading to 17.10 hasn't been useful on this problem.
But then I found that the pulseaudio & libasound packages installed on my system was for i386 arch, despite of my system running on with 64bit arch.
There hasn't been any way to restore 64bit version through apt, I had to access ubuntu mirrors and download those packages (and the related dependencies) manually: by installing these through dpkg I finally managed to have the audio device correctly working.
My question is: how could it be happened? how could I restore to a normal condition? my first concern is the next update I will need to install for those packages: I guess apt will try to remove amd64 version and to install i386 one at the first update of one of the interested packages.
The only option I have in mind would be to go through a new clean installation...
apt sound pulseaudio 64-bit alsa
apt sound pulseaudio 64-bit alsa
asked Feb 16 at 10:44
v.bontempi
1013
1013
add a comment |Â
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1006751%2fubuntu-16-04-upgraded-to-17-10-audio-problems-pulseaudio-wrong-architecture%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password