This happens quite frequently for me on 10.10 32 bit and 64 bit. I can't
figure out why but I can re-produce easily. If anyone has an idea on
what may fix it, i can test it out since i can reproduce.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
Hi Clint,
no problem on making Ubuntu better, I owe it a lot.
I actually make a different init.d script for each memcache daemon.
This is handy in making a production level web app that leverages
memcache as I can have staging environments on 1 server. For example, I
have my production server li
Public bug reported:
Binary package hint: memcached
The memcached init.d script only passes DAEMON and NAME when calling
status_of_proc. It should be passing PID file as well.
status_of_proc -p $PIDFILE $DAEMON $NAME
This allows 2 memcached init.d scripts (and therefore 2 memcached
servers) to
--
status operation on init.d not working correctly
https://bugs.launchpad.net/bugs/681090
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listin
My sound now works. All I did was boot into the 2.6.24-22 kernel,
opened the volume control, clicked on switches tab and checked
'speaker'.
I then restarted into the -23 kernel and sound works.
my suspicion is when I upgraded the -23 kernel, I also upgraded a
package that disabled that check bo
I followed all of the troubleshooting steps (other than downloading and
compiling the alsa source) outlined here:
https://help.ubuntu.com/community/SoundTroubleshooting
Still no success.
One thing I notice is my lspci -v | less is missing a lines that say
'Kernel driver in use: ' and 'Kernel mod
Same here. I'm on T61p. Upgraded to the 2.6.24-23 kernel and sound no
longer works.
uname -a
Linux 2.6.24-23-generic #1 SMP Thu Nov 27 18:44:42 UTC 2008 i686
GNU/Linux
lspci -v | grep Audio
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio
Controller (rev 03)
--
No soun
The work around does not work as expected for me. I follow the steps
above, and indeed it saves the 'system' setting as well as the wireless
key.
However, on reboot, I expect the system setting for wireless to connect
to the wireless router before logging in (so I should be connected by
the time I
