[Bug 906825] Re: [11.10 - 12.04] lxpanel crashing randomly. High CPU-Load nothing is clickable correctly. Redraw fails

2012-01-03 Thread Daniel Monedero
In my case, lxpanel also takes all the cpu when I disconnect my USB webcam :-? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/906825 Title: [11.10 - 12.04] lxpanel crashing randomly. High CPU-Load no

[Bug 779680] Re: Firewire broken

2011-08-01 Thread Daniel Monedero
Thank you, but it didn't work, the command "LD_PRELOAD=/usr/lib/libv4l/v4l1compat.so dvgrab" returns: Found AV/C device with GUID 0x008088030730d524 Waiting for DV... And nothing happens, when killing the process it outputs: 0.00 MiB 0 frames Capture Stopped Error: no DV dmesg upon executing the

[Bug 779680] Re: Firewire broken

2011-05-10 Thread Daniel Monedero
I still haven't found a working solution, but there seems to be an alternative. sudo aptitude install v4l2loopback-source module-assistant sudo module-assistant auto-install v4l2loopback-source sudo modprobe -r ohci1394 sudo modprobe firewire-ohci sudo modprobe v4l2loopback sudo gst-launch videote

[Bug 779680] Re: Firewire broken

2011-05-08 Thread Daniel Monedero
Regarding kino and dvgrab, it seems like they are looking for the device at the wrong place. So "sudo ln /dev/fw0 /dev/raw1394" solves the problem for them. But dv4l still isn't working because the vloopback module cannot be compiled: sudo apt-get install vloopback-source cd /usr/src/ sudo bunzip

[Bug 779680] Re: Firewire broken

2011-05-08 Thread Daniel Monedero
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/779680 Title: Firewire broken -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 779680] [NEW] Firewire broken

2011-05-08 Thread Daniel Monedero
Public bug reported: Binary package hint: dvgrab Looks like the old firewire stack wasn't included in Natty. As a result, dvgrab, kino, and dv4l don't work anymore because the module raw1394 is no longer included: $sudo modprobe raw1394 FATAL: Module raw1394 not found. ProblemType: Bug DistroRe

[Bug 458577] Re: no wireless with ipw2200 on karmic

2011-03-12 Thread Daniel Monedero
You're right, Charles. The problem was caused by WICD, using NetworkManager instead solved the problem :) Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/458577 Title: no wireless with ipw22

[Bug 458577] Re: no wireless with ipw2200 on karmic

2011-03-12 Thread Daniel Monedero
Tried several but none worked, I'm already thinking about giving a try to ndiswrapper. Using an Intel ipw2200 on a Fujitsu-siemens amilo m1425. By the way, I'm using xubuntu and getting this on dmesg: [162405.881841] ADDRCONF(NETDEV_UP): eth0: link is not ready [162405.907194] ADDRCONF(NETDEV_UP

[Bug 366217] Re: Intel PRO/Wireless 2200BG Fails to connect to any network

2011-03-12 Thread Daniel Monedero
Still happening on Maverick... -- You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. https://bugs.launchpad.net/bugs/366217 Title: Intel PRO/Wireless 2200BG Fails to connect to any network -- ubuntu-bugs mailing list ubuntu-bugs@lists.ub

[Bug 458577] Re: no wireless with ipw2200 on karmic

2011-03-12 Thread Daniel Monedero
I also have an Intel 2200 and I confirm this bug also happens on Maverick. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/458577 Title: no wireless with ipw2200 on karmic -- ubuntu-bugs mailing lis

[Bug 85946] Re: Error in powernowd startup script, "Directory nonexistent"

2007-10-23 Thread Daniel Monedero
Same problem in Butsy stable -- Error in powernowd startup script, "Directory nonexistent" https://bugs.launchpad.net/bugs/85946 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.