Public bug reported:
Binary package hint: pulseaudio
No input at all from the front microphone on my system.
tried alsamixer upped the levels on capture the input microphone, no
such Luck.
Expected:
able to record sound
Result:
No sound heard or able to be recorded
ProblemType: Bug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/798574
Title:
[TECRA A9, Realtek ALC262, Black Mic, Front] Input Microphone not
working
To manage notifications about this bug go to:
Chuck,
Apologies for not getting back sooner. This machine is with an old
employer. Enough said.
This bug should probably get closed, as I have no access to the machine
in question.
Nick
--
Apache trying to start before network interfaces are up
https://bugs.launchpad.net/bugs/353594
You
Chuck,
Apologies for not getting back sooner. This machine is with an old
employer. Enough said.
This bug should probably get closed, as I have no access to the machine
in question.
Nick
--
Apache trying to start before network interfaces are up
https://bugs.launchpad.net/bugs/353594
You
OK, this works fine with the ppa bluez packages. Connection comes up I
am writing this comment with the connection.
Thanks!
--
Error Msg: Device added successfuly, but failed to connect
https://bugs.launchpad.net/bugs/403779
You received this bug notification because you are a member of Ubuntu
n...@toshi:~$ apt-cache policy bluez
bluez:
Installed: 4.32-0ubuntu4.1
Candidate: 4.32-0ubuntu4.1
Version table:
*** 4.32-0ubuntu4.1 0
500 http://au.archive.ubuntu.com jaunty-updates/main Packages
100 /var/lib/dpkg/status
4.32-0ubuntu4 0
500
The dhclient does not want to work either, exactly the same problem
(although I havent checked all the logs etc, but its the same error
message)
Am I correct in assuming that blueman-manager is sending off a dbus msg
to blueman-applet, and it is the result of this failing that is causing
the
All the settings are set to system settings. I assume that this is
what you mean by system mode.
Apologies, I thought I had already responded to this comment.
--
Apache trying to start before network interfaces are up
https://bugs.launchpad.net/bugs/353594
You received this bug notification
Public bug reported:
Binary package hint: apache2
Apache fails to start when I boot my system (Intrepid Desktop). The init
scripts report this error:
apache2: Could not reliably determine the server's fully qualified domain name,
using 127.0.1.1 for ServerName
(99)Cannot assign requested
Public bug reported:
Binary package hint: apache2
Apache fails to start when I boot my system (Intrepid Desktop). The init
scripts report this error:
apache2: Could not reliably determine the server's fully qualified domain name,
using 127.0.1.1 for ServerName
(99)Cannot assign requested
Adding the line:
sleep 10
to the /etc/init.d/apache2 script before starting the daemon, fixes the
problem (workaround).
--
Apache trying to start before network interfaces are up
https://bugs.launchpad.net/bugs/353594
You received this bug notification because you are a member of Ubuntu
Bugs,
11 matches
Mail list logo
