I tried echo-cancellation with pulseaudio using an ubuntu 13.10 live-
session (booting a live-session from usb-stick).
Loading module-echo-cancel without specifying canceller works like
expected (propably using speex canceller-implementation; I also verified
this by using gstreamer-properties,
** Tags added: module-echo-cancel webrtc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1261666
Title:
[pulseaudio] module.c: Failed to load module module-echo-cancel
(argument:
-guard/run.d/ just before doing the real shutdown, it seems the
perfect way for me on our server-system.
I know it's just another workaround, but it's the least intrusive way and works
very well because shutting down KVMs is done before all the other
upstart/sysv-scripting stuff.
Greets
tomcrus
-guard/run.d/ just before doing the real shutdown, it seems the
perfect way for me on our server-system.
I know it's just another workaround, but it's the least intrusive way and works
very well because shutting down KVMs is done before all the other
upstart/sysv-scripting stuff.
Greets
tomcrus
As I'm currently setting up an intranet mail-server for my company
(based on lucid / ebox) in some kvm-guests and there for have exactly
the same problem. Reading all previous posts - and because I need kvm-
guest shutdown as well - I will use something like this:
Add following lines in
As I'm currently setting up an intranet mail-server for my company
(based on lucid / ebox) in some kvm-guests and there for have exactly
the same problem. Reading all previous posts - and because I need kvm-
guest shutdown as well - I will use something like this:
Add following lines in
Same to me. I use kubuntu 9.10 AMD64 on a Dell Studio. It was an
upgrade-installation from 9.04.
I've got two users: user1 has the problem as described above, user2 not (both
existed also before upgrade from 9.04)
As I played around a bit, I recognized that even some other
system-notifications
** Description changed:
Binary package hint: mountall
Release: 9.10
Package-Version: 1.0, 1.0.1
Multiple entries in fstab with the same mount-point get not mounted as
expected. (see mount-point '/home' in attached fstab for example)
Probably it doesn't make very much sense to
Public bug reported:
Binary package hint: mountall
Release: 9.10
Package-Version: 1.0, 1.0.1
Multiple entries in fstab with the same mount-point get not mounted as
expected. (see mount-point '/home' in attached fstab for example)
Probably it doesn't make very much sense to mount different
** Attachment added: example fstab
http://launchpadlibrarian.net/37410812/fstab
--
multiple entries in fstab with same mount-point
https://bugs.launchpad.net/bugs/503003
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
As I looked at the sources of mountall I found the function parse_fstab, which
already has a spacial-case-handling of lines for swap-partitions (which would
get a mount-point of 'none' and so there also could be only one swap-entry).
I think probably this was the fix for bug #435027, but I
Note: the attached patch is just a suggestion and isn't even tested. As
mountall seems to do more then just walk through fstab and mount each
line, just applying the patch probably won't work. So maybe someone more
familar with it should take a deeper look at it
--
multiple entries in fstab with
I have a Dell Studio 15 installed with Kubuntu 64bit. In 9.04 touchfreeze never
crashed, after upgrading to 9.10 it crashes everytime I start it. When starting
it in a console I see that's a segmentation fault.
As I was using it basically to turn the touchpad off I now type synclient
13 matches
Mail list logo
