[Bug 388081] Re: audio skips, pulseaudio -vvv shows underrun in module-alsa-sink.c

2010-05-01 Thread Robert Moerland
For me (original reporter), it seems like this is not an issue anymore after an upgrade to the lucid distribution. I've been playing audio for a couple of hours now and haven't heard a single hiccup. I had the exact same issues as poster #6, but for me they've disappeared. -- audio skips, pulseau

[Bug 514675] Re: After resume, wireless connection is not restored with kernel 2.6.31-17-generic

2010-04-27 Thread Robert Moerland
It was an issue on my Karmic laptop, until I updated it to an alpha version of Lucid back in february. The issue seems to be resolved in that version. For me personally it's not an issue anymore. -- After resume, wireless connection is not restored with kernel 2.6.31-17-generic https://bugs.launc

[Bug 510246] apport-collect data

2010-05-05 Thread Robert Moerland
Architecture: i386 Dependencies: DistroRelease: Ubuntu 9.04 NonfreeKernelModules: nvidia Package: linux None [modified: /var/lib/dpkg/info/linux.list] PackageArchitecture: i386 ProcEnviron: SHELL=/bin/bash LANG=en_US.utf8 Uname: Linux 2.6.28-18-generic i686 UserGroups: adm admin cdrom dialout l

[Bug 510246] Re: Suspend only works once, dmesg shows errors about sata disk

2010-05-05 Thread Robert Moerland
I have the exact same issue with ubuntu jaunty, with (slightly?) different hardware: a Promise PDC20375 (SATA150 TX2plus) controller. I've attached the dmesg output after the first and second (attempt at a ) suspend. The second time, the graphics are turned off and a single blinking cursor is visib

[Bug 510246] Re: Suspend only works once, dmesg shows errors about sata disk

2010-05-05 Thread Robert Moerland
** Attachment added: "dmesg_after_2nd_suspend.txt" http://launchpadlibrarian.net/47862638/dmesg_after_2nd_suspend.txt -- Suspend only works once, dmesg shows errors about sata disk https://bugs.launchpad.net/bugs/510246 You received this bug notification because you are a member of Ubuntu Bug

[Bug 510246] Re: Suspend only works once, dmesg shows errors about sata disk

2010-05-05 Thread Robert Moerland
** Attachment added: "lspci.txt" http://launchpadlibrarian.net/47862644/lspci.txt -- Suspend only works once, dmesg shows errors about sata disk https://bugs.launchpad.net/bugs/510246 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -

[Bug 518623] Re: [KM400] Black screen after boot, no text console possible

2010-04-13 Thread Robert Moerland
Confirming workaround by Marien Zwart. After blacklisting both viafb and vga16fb, I can boot kernel 2.6.32.20 and can use my laptop normally. Don't know if there are any (major) drawbacks involved with blacklisting these modules. -- [KM400] Black screen after boot, no text console possible https:

[Bug 549383] Re: WUSB54G not working out of the box

2010-04-16 Thread Robert Moerland
For me, the solution was to install the linux-firmware-nonfree package. After that, the hardware was found and activated. -- WUSB54G not working out of the box https://bugs.launchpad.net/bugs/549383 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 518623] Re: [KM400] Black screen after boot, no text console possible

2010-03-30 Thread Robert Moerland
Adding: Section "Module" Disable "dri" EndSection to my xorg.conf file didn't make a difference, neither did adding 'Disable "glx"'. I also tried removing the xorg.conf file altogether, but also that didn't have any visible effect. @Bartosz: your involvement in this bug, does that mean you

[Bug 258764] Re: Via KM400 : no matching mode for vesa

2010-05-13 Thread Robert Moerland
The original reported won't be able to help anymore: "This bugs has been annoying for so long I had time to change my 4 years old PC and get another card. Won't be able to help anymore." I still can reproduce this bug on my 10.04 install. Same error message: (EE) VESA(0): No matching modes (EE)

[Bug 258764] Re: Via KM400 : no matching mode for vesa

2010-05-28 Thread Robert Moerland
In response to the tag needs-retested-on-lucid-by-june: it's nearly june and I've retested this issue on 10.04. Should the bug still be listed as incomplete? -- Via KM400 : no matching mode for vesa https://bugs.launchpad.net/bugs/258764 You received this bug notification because you are a member

[Bug 518623] Re: VIA KM400: Black screen after boot, no text console possible

2010-03-25 Thread Robert Moerland
I (the original reporter) can confirm the observed behavior by Jon Welsh (#26). I'm typing this response on a version 2.6.32-16 kernel-based lucid, booted from a USB stick. The same kernel version, when booted from hard disk after an upgrade from karmic (see original description) doesn't work at al

[Bug 518623] Re: VIA KM400: Black screen after boot, no text console possible

2010-03-25 Thread Robert Moerland
Small addition, the virtual terminals cannot be used by me from within the live cd environment, the screen that is shown is corrupt. Furthermore, I actually used the Xubuntu live cd instead of the Ubuntu live cd. -- VIA KM400: Black screen after boot, no text console possible https://bugs.launchp

[Bug 540533] Re: totem subtitle plugin cannot contact opensubtitles.org

2010-03-20 Thread Robert Moerland
You're welcome. I accidentally got the patch reversed and have corrected this in the upstream bug report. For completeness, I'm attaching the correct patch here as well. ** Attachment added: "Correct patch to address the issue described" http://launchpadlibrarian.net/41378597/opensubtitles.py.p