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
ProcEn
** 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 sou
Brian:
I ran the script and installed python-launchpadlib. I cannot allow the
system to gain information to all my data, including personal data.
Maybe someone else will have this problem and give you full access to
their personal data.
Thanks for trying to help me.
Levi Nigg
<><
Thank you fo
Aldy Ekosiwi wrote:
> Brian,
> Thanx for quick response. Greatly appreciate it.
> Fortunately, I found the fix for my problem.
> Although, my login was a member of the following groups:
> pulse,
> pulse-access
> pulse-rt
> but somehow "Menu-->>System->Administration->Users &
> Groups->Properties
Brian Murray wrote:
> Kloudy, without any information about your system there is little we can
> do about your bug report. You could manually collect the information
> out-lined at
> https://wiki.ubuntu.com/DebuggingSoundProblems#Reporting%20Sound%20Bugs
>
>
The latest fixes
Aldy Ekosiwi wrote:
> Levi,
>
> 1) Go into menu toolbar and select "System->Administration->Users&Groups"
> 2) Highlight on your login name and click "Unlock" then enter your login
> password as requested
> 3) Then click Properties. A new window would be opened with several tabs
> 4) Click on "Us
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 expe
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://bu
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
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://l
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
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/
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.
--
I have this same problem with a 600m in Gutsy. The acpi-support version
there is 0.103.
Is there a fix on the way for that too or do I need to submit a separate
bug report?
--
[REGRESSION] closing laptop lid does not turn off screen
https://bugs.launchpad.net/bugs/22989
You received this bug no
I confirm the same problem with a Dell 600m. The laptop is extremely
hot after medium usage. I am concerned that it is running too hot.
With everything shut down an in the docking station, I opened up the
laptop lid and held in the lid switch. When I boot in Gutsy, the
display stays on. When I
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 edit
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-da
unggnu:
I want to be able to use my laptop standalone and in the docking
station. What does the command you reference do?
Thanks!
--
laptop screen remains on with external monitor and lid closed
https://bugs.launchpad.net/bugs/145501
You received this bug notification because you are a member
Jerry, I have stopped using the docking station so it is no longer an
issue with me.
Thanks for your diligence in following-up on the problem.
Levi
-Original Message-
From: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of Jeremy
Foshee
Sent: Wednesday, May 05, 2010 2:11
18 matches
Mail list logo
