[Bug 395853] [NEW] no sound from speakers

2009-07-05 Thread Kloudy
Public bug reported: Binary package hint: totem release 9.04. No sound from speakers since upgrade from 8.04. No error messages, just no sound ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/bin/totem-gstreamer Package: totem-gstreamer 2.26.1-0ubuntu5

[Bug 395853] Re: no sound from speakers

2009-07-05 Thread Kloudy
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/28715419/Dependencies.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/28715421/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/28715422/ProcStatus.txt -- no sound

[Bug 25931] Re: Failed to initalize HAL.

2007-10-31 Thread Kloudy
Pescio, here is my ls /etc/rc2.d | sort : README S05vbesave S10acpid S10powernowd.early S10sysklogd S10xserver-xorg-input-wacom S11klogd S12dbus S12sl-modem-daemon S13gdm S13hal S19cupsys S20apmd S20apport S20hotkey-setup S20makedev S20nvidia-kernel S20powernowd S20rsync S22consolekit

[Bug 25931] Re: Failed to initalize HAL.

2007-10-30 Thread Kloudy
Got my HAL working even with CONCURRENCY in /etc/init.d/rc set to shell. Here are the steps I took. (All are included above in previous posts and Bug #149881 link https://bugs.launchpad.net/ubuntu/+source/hal/+bug/149881 .) Changed the CONCURRENCY setting by: sudo gedit /etc/init.d/rc and

[Bug 25931] Re: Failed to initalize HAL.

2007-10-29 Thread Kloudy
I set the CONCURRENCY=shell and the HAL problem came back. rc2.d stayed at S12dbus this time, no S50dbus Set CONCURRENCY=none, rebooted and HAL is working again. The boot process is still slower than I remember in Feisty. I'll bet there still is a tweek somewhere to fix the real problem. --

[Bug 25931] Re: Failed to initalize HAL.

2007-10-28 Thread Kloudy
Got my HAL working even through a complete power down and restart! Here are the steps I took. (All are included above in previous posts.) Compared my /etc/rc2.d filenames to those posted above. My rc2.d was S50dbus instead of S12dbus sudo mv /etc/rc2.d/S50dbus /etc/rc2.d/S12dbus sudo mv

[Bug 25931] Re: Failed to initalize HAL.

2007-10-27 Thread Kloudy
I am another Failed to initialize HAL Gutsy user. My computer is a Dell Inspiron 600m laptop. 1G RAM, 80G HD. I had no problems in Fiesty. Did a network upgrade to get Gutsy. WUBI originally used to install Fiesty. Things are pretty sluggish. System Administration Network Settings

[Bug 25931] Re: Failed to initalize HAL.

2007-10-27 Thread Kloudy
oh my... I disabled dbus in 'services' to try what st33med suggested. Now my permissions are removed and I can't try you suggestions. I also cannot get into 'services'. Do you know how I can get 'services' to open again. I'm a newbee as you can figure. -- Failed to initalize HAL.

[Bug 25931] Re: Failed to initalize HAL.

2007-10-27 Thread Kloudy
I reinstalled dbus. I can try your recommendations now. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber. -- desktop-bugs mailing list

[Bug 25931] Re: Failed to initalize HAL.

2007-10-27 Thread Kloudy
I tried you suggestions. Below is what I got. I am the admin of this system, but I don't have the permissions I guess. [EMAIL PROTECTED]:~$ /etc/init.d/dbus start open: Permission denied * Removing stale PID file /var/run/dbus/pid. rm: cannot remove `/var/run/dbus/pid': Permission denied