[Bug 395853] Re: no sound from speakers
** 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 from speakers https://bugs.launchpad.net/bugs/395853 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 395853] [NEW] no sound from speakers
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 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: totem Uname: Linux 2.6.28-13-generic i686 ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- no sound from speakers https://bugs.launchpad.net/bugs/395853 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 25931] Re: Failed to initalize HAL.
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 S24avahi-daemon S24dhcdbd S89anacron S89atd S89cron S90binfmt-support S98usplash S99acpi-support S99laptop-mode S99rc.local S99rmnologin S99stop-readahead -- 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 desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 25931] Re: Failed to initalize HAL.
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 editing CONCURRENCY=none to CONCURRENCY=shell. Then saving. Compared my /etc/rc2.d filenames to those posted above. My rc2.d was S50dbus instead of S12dbus. Changed that by: sudo mv /etc/rc2.d/S50dbus /etc/rc2.d/S12dbus Saw in another thread that hal should be set to 13 so that it starts after dbus is started. My HAL was 12. Fixed that by: sudo mv /etc/rc2.d/S12hal /etc/rc2.d/13hal Another post said to change the Hal cache. Did that by: sudo mv /var/cache/hald/fdi-cache~ /var/cache/hald/fdi-cache Restarted PC and all seems fine. Thanks to the Ubuntu posters for your help. Gutsy still starts up awlfully slow compared to Feisty. Any other ideas are appreciated. -- 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 desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 25931] Re: Failed to initalize HAL.
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. -- 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 desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 25931] Re: Failed to initalize HAL.
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 /var/cache/hald/fdi-cache~ /var/cache/hald/fdi-cache Restarted PC and all seems fine. I still have CONCURRENCY in /etc/init.d/rc set to none from shell. Does anyone think I should change it to shell to get faster boot-up speed, or will that hose up my HAL fixes again? I am not running a dual core machine. Thanks to all the posters for your help and file comparisions. -- 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 desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 25931] Re: Failed to initalize HAL.
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 [EMAIL PROTECTED]:~$ /etc/init.d/dhcdbd start open: Permission denied * Starting DHCP D-Bus daemon dhcdbd open: Permission denied [ OK ] [EMAIL PROTECTED]:~$ /etc/init.d/hal start open: Permission denied * Can't start Hardware abstraction layer - detected chrooted sessio [EMAIL PROTECTED]:~$ -- 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 desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 25931] Re: Failed to initalize HAL.
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 desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 25931] Re: Failed to initalize HAL.
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. 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 desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 25931] Re: Failed to initalize HAL.
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 experience. Dialog is greyed out for about 90 seconds. Then populates. Was able to set-up ethernet and wireless connections, but had to use manual settings. Navigating in this dialog takes plenty of patience. Often over a minute between actions. System > Preferences > Hardware Information Unpopulated dialog opens for about 5 seconds then closes. System > Preferences > Power Management No dialog ever opens. Concurrency setting in /etc/init.d/rc is set to 'none'. -- 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 desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
