Thanks for the feedback. I supposed lshal works, but I'm not so sure now (here it failed to start hal when requested). Could affected people try to run 'lshal' or/and 'sudo lshal' in a terminal (with all workarounds disabled)? If this does not work (i.e. it displays a "could not contact hald" error), then the bug is in hal…
Thanks for the feedback. I supposed lshal works, but I'm not so sure now (here it failed to start hal when requested). Could affected people try to run 'lshal' or/and 'sudo lshal' in a terminal (with all workarounds disabled)? If this does not work (i.e. it displays a "could not contact hald" error), then the bug is in hal…