[Bug 269831] Re: toshset does not support tlsup module (Intrepid)

2008-11-24 Thread Helminthe
Hello - besides a confirmation that the above kernel (lp269831) works perfectly and I now have a fully functional Toshiba U200 laptop (thank you!) - I also need to use Virtualbox / Vmware on the same machine. The patches are not yet in -proposed, I have booted 2.6.27-8-generic. Can I ask for a

[Bug 269831] Re: toshset does not support tlsup module (Intrepid)

2008-11-24 Thread Helminthe
Thank you - yes they are, and I'll add a wow for the response time on this. Receiving a fully packed solution for a personal problem within the hour at 2 AM was far beyond my expectations :) -- toshset does not support tlsup module (Intrepid) https://bugs.launchpad.net/bugs/269831 You received

[Bug 186347] Re: snd-hda-intel toshiba u200-165

2008-11-15 Thread Helminthe
I can now confirm point 2. above, after installing Windows and the needed drivers. -- snd-hda-intel toshiba u200-165 https://bugs.launchpad.net/bugs/186347 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list

[Bug 186347] Re: snd-hda-intel toshiba u200-165

2008-11-11 Thread Helminthe
I can confirm the issue, on Inteprid (2.6.27-7-generic), exactly the same hardware, with a note: the previous reporter might not have noticed that sound is playing, but at a very very low level. I can hear music with no distortions, but only by plugging in headphones and turning every control

[Bug 186347] Re: snd-hda-intel toshiba u200-165

2008-11-11 Thread Helminthe
Update for 4. above - I have installed alsa 1.0.18 from source, rebooted and made sure the new modules are loaded, no change. -- snd-hda-intel toshiba u200-165 https://bugs.launchpad.net/bugs/186347 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed

[Bug 261761] Re: Capslock light on MacBook Pro not working

2008-10-12 Thread Helminthe
*** This bug is a duplicate of bug 125918 *** https://bugs.launchpad.net/bugs/125918 ** This bug has been marked a duplicate of bug 125918 [Gutsy Tribe 2, Intrepid Alpha 2+] Illuminated keyboard not working on MacBook Pro rev.3 (santa rosa) -- Capslock light on MacBook Pro not working

[Bug 278484] Re: pommed crashed with SIGSEGV in __libc_start_main()

2008-10-06 Thread Helminthe
** Visibility changed to: Public -- pommed crashed with SIGSEGV in __libc_start_main() https://bugs.launchpad.net/bugs/278484 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

[Bug 278484] Re: pommed crashed with SIGSEGV in __libc_start_main()

2008-10-06 Thread Helminthe
The crash happens at almost every system startup. Also, when it is running (/usr/sbin/pommed appears in the process list), I can only control the volume using Mac's hotkeys. Keyboard and display brightness cannot be adjusted, the 'eject' button does not work. Motion sensors are not detected

[Bug 234165] Re: Hardy: sound level low, poor quality on Macbook Pro

2008-07-09 Thread Helminthe
I have just noticed (simply didn't need this before) that the microphone is muted. I have played with alsamixer, kmix, artscontrol, krec, audacity - absolutely no sound input. I don't know how to debug this problem, everything in the interface of the applications tried suggests that the input

[Bug 234165] Re: Hardy: sound level low, poor quality on Macbook Pro

2008-06-19 Thread Helminthe
FYI, I have just installed alsa-1.0.17rc2 (modules, firmware, lib, utils) and there is no improvement. -- Hardy: sound level low, poor quality on Macbook Pro https://bugs.launchpad.net/bugs/234165 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 234165] Re: Hardy: sound level low, poor quality on Macbook Pro

2008-06-19 Thread Helminthe
The report above is wrong, it seems, the output of alsa-info.sh shows Driver version: 1.0.16 Library version:1.0.17rc2 Utilities version: 1.0.17rc2 Modules install seemed to go OK though, is there something similar to /etc/default/linux-restricted-modules-common for alsa? ** Attachment

[Bug 234165] Re: Hardy: sound level low, poor quality on Macbook Pro

2008-06-01 Thread Helminthe
Sorry, didn't see that page, output attached. Thank you for your help. ** Attachment added: alsa-info.txt http://launchpadlibrarian.net/14880883/alsa-info.txt -- Hardy: sound level low, poor quality on Macbook Pro https://bugs.launchpad.net/bugs/234165 You received this bug notification

[Bug 234165] [NEW] Hardy: sound level low, poor quality on Macbook Pro

2008-05-22 Thread Helminthe
Public bug reported: One of the reasons for purchasing a Macbook has been its very good speakers, using OS X they sound louder than any other notebook I've owned, good bass, low noise. Using Ubuntu on the same system, I get a somewhat metallic distortion, and the maximum output level is way

[Bug 234165] Re: Hardy: sound level low, poor quality on Macbook Pro

2008-05-22 Thread Helminthe
** Attachment added: alsamixer output http://launchpadlibrarian.net/14664184/alsamixer.png -- Hardy: sound level low, poor quality on Macbook Pro https://bugs.launchpad.net/bugs/234165 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 229388] Re: parted stack smashing

2008-05-18 Thread Helminthe
Can confirm, same error on Hardy, while trying to format an USB flash drive. fdisk works correctly, while parted and gparted insist that the drive has an unrecognised disk label, and crash when trying to add one. ** Changed in: parted (Ubuntu) Status: New = Confirmed -- parted stack

[Bug 229388] Re: parted stack smashing

2008-05-18 Thread Helminthe
The same problem affects syslinux too, sevearl hits in Google suggesting that #1 it's a known issue for developers of both applications #2 it affects large external USB disks e.g, iPods who are formatted with a sector size 512 #3 it's not trivially fixed -- parted stack smashing

[Bug 226945] Re: ImageMagick broken in Hardy

2008-05-07 Thread Helminthe
Sorry, but I don't have quick access to a Gutsy install, and the live cd doesn't include all needed packages to test. FWIW, the EXIF data has been available properly with ImageMagick and the corresponding Perl module for a long time in all environments I tested (XP and OS X) -- ImageMagick

[Bug 226945] [NEW] ImageMagick broken in Hardy

2008-05-05 Thread Helminthe
Public bug reported: Binary package hint: imagemagick use Image::Magick; $image =Image::Magick - new(); $image-Read($name); print $image-Get('Exif:ImageDescription'); Expected result: the EXIF data should be displayed, and it is on several systems I tried, including OS X and XP, all with Perl

[Bug 226945] Re: ImageMagick broken in Hardy

2008-05-05 Thread Helminthe
Hello - nothing is displayed, $image-Get returns an empty string for any EXIF value I tried (copyright, orientation, camera model). No errors reported. -- ImageMagick broken in Hardy https://bugs.launchpad.net/bugs/226945 You received this bug notification because you are a member of Ubuntu

[Bug 98588] Re: MBR deleted after 6.10-7.04 upgrade

2007-12-04 Thread Helminthe
It sure isn't the case anymore, I'm on 7.10 ti which the upgrade went smoothly :) Thank you for the cleanup work though! -- MBR deleted after 6.10-7.04 upgrade https://bugs.launchpad.net/bugs/98588 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug

[Bug 98582] 6.10-7.04 upgrade failed because of firestarter

2007-03-29 Thread Helminthe
Public bug reported: Binary package hint: firestarter /etc/init.d/firestarter start failed because wireless network interface was not up. upgrade was stopped, with the message your system might be in an inconsistent state. ProblemType: Package Date: Thu Mar 29 14:29:47 2007 ErrorMessage:

[Bug 98588] MBR deleted after 6.10-7.04 upgrade

2007-03-29 Thread Helminthe
Public bug reported: I am dual-booting XP and Ubuntu, with ntloader first and grub on Ubuntu's partition. Upgrade process failed at package firestarter (see bug #98582), with the message your system might be in an inconsistent state (don't know if this is related). After reboot, the MBR was