After the device is started, the following error occurs: pulseaudio configured for per-user sessions saned disabled; edit/etc/default/saned (not resolved)

Method:

Method 1:

When Ubuntu netbook 10.10 is started, the system prompts "Disable: saned/etc/default/saned". After restarting, select rescue mode. after entering the system, run the sudo passwd root command to change the password. The root user cannot use it by default. After switching to the root user, directly edit the file/etc/default/saned and change the content to the following:
Root @ Ubuntu :~ # Cat/etc/default/saned
# Defaults for the saned initscript, from sane-utils // indicates that the file is from the sane-utils package.
# Set to yes to start saned
Run = Yes // No
# Set to the user saned shoshould run
Run_as_user = saned

Method 2:

After the restart, the startup interface is passed, and it stops at this point as soon as it is about to reach ltpd.
Fsck from util-Linux-ng 2.17.2
/Dev/sda1: clean, 135331/29761536 files, 2585722/119024384 Blocks
* Starting apparmor profiles
Skipping profile in/etc/apparmor. d/Disable: USR. bin. Firefox [OK]
* Setting sensors limits [OK]
Speech-DISPATCHER disabled; edit/etc/default/speech-dispatcher
* (Red) pulseaudio configured for per-user sessions
Saned disabled: edit/etc/default/saned
* Enabling additional executable binary formats binfmt-support [OK]
* Checking battery state...
After searching, modify the saned and speech-dispacher files and change "no" to "yes ".
But the problem persists after the restart, and I have read it, and the Yes values in the two files are changed to No.
So again, the saned file is "yes", but the interface is stuck in start saned.
What is the cause of this problem? What does saned do? What does speech-dispatcher do?

Method 3:

0 down vote

I'm also getting this after upgrade from 11.04 to 11.10-in order to get it to boot I had to force USE OF THE 2.6.x kernel instead of the V3 kernel that 11.10 seems to want use by default. I did this by editing/boot/GRUB/grub. CFG-not a great solution but it's a stopgap until I figure out why it's not booting with the V3 kernel and fix it.

For some reason I cannot use by USB keyboard with grub2 to select previous kernel from the boot menu, hence editing the grub. cfg.

Edit:Exact steps I took to solve this problem:

(1) Press CTRL + ALT + F2 as boot starts to get a login prompt. log in.

(2) navigate to/etc/default/

(3) edit the grub settings: sudo VI grub

(4) set grub_default = 2> 2

(5) set grub_timeout = 10

(6) save the file and run: Update-grub

(7) reboot.

Note, The grub_default value is the 3rd submenu item in the 3rd submenu (counts from 0), which for me is the boot option for the latest 2.6 kernel. if you have a new install yours might not have the 2.6 kernel available, or it may be in a different place, but I hope this helps someone.

Method 4:

Answer edited out from the question:

I found a partial fix and just in case anyone else is having the same problem which is extremely annoying.

It turned out to be an issue with lightdm. anyway to fix this, I removed lightdm and went back to using TPD which is gnome Display Manager. it's extremely ugly but at least it lets you boot.

In order to do that you shoshould follow these steps:

1. When in the black uugly screen hold downCTRL+ALT+F1. If nothing happens holdF2Instead.

2. Enter your credentials

3. Sudo VI/etc/X11/default-display-Manager

4. Change it/Usr/sbin/TPD

   (If you're not familiarVI: Edit, Then save by entering:ThenWQ!)

5. Sudo reboot

My answer to the question:

When the loading stops with the 'Ugly black screen', enter one of the TTYs (for exampleCTRL+ALT+F1) And login into your system.

Then enterSudo service lightdm restart

If it says unrecognized service, try the commandSudo apt-Get install lightdm

This shoshould ensure that lightdm is properly installed.

In short, all the methods that can be tried have been tried. I still cannot enter the system and gave up completely. I really felt that nothing was done, but this problem occurred, it seems that it will be very troublesome to use a virtual machine to play Linux in the future. Otherwise, it will be difficult to reinstall it if such a problem cannot be solved.