[Bug 295809] Re: Patch for fixing LCD brightness on sony vaio VGN-FE31H

2008-11-23 Thread José M . Vaz
** Summary changed: - Fn Keys events don't change LCD brightness + Patch for fixing LCD brightness on sony vaio VGN-FE31H -- Patch for fixing LCD brightness on sony vaio VGN-FE31H https://bugs.launchpad.net/bugs/295809 You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 295809] Re: Fn Keys events don't change LCD brightness

2008-11-14 Thread José M . Vaz
The attached patch adds the correct acpi events to /etc/acpi/event/... in order to make my Fn-Brightness keys work ** Attachment added: patch adds acpi brightness events matching my sony vaio laptop http://launchpadlibrarian.net/19658456/laptop-keys-sony-vaio.patch -- Fn Keys events

[Bug 295809] [NEW] Fn Keys events don't change LCD brightness

2008-11-08 Thread José M . Vaz
Public bug reported: Binary package hint: acpi-support Problem: Can't change LCD brightness via Fn Keys Fn key presses are detected: Although the gnome pop-up for brightness adjustment pops-up and increases/decreases matching the pressing of the increase/decrease brightness keys, no change in

Re: [Bug 78257] Re: Intel HDA No sound after Standby

2008-09-06 Thread José M . Vaz
Hello, I've upgraded my installation to the latest Ubuntu alpha 5. The bug is fixed for me. The resume processes now finishes, and the sound output works just fine! Finally, I'll be able to use suspend/resume in my portable computer! Thanks! The contents of the /proc/version_signature file are:

Re: [Bug 78257] Re: Intel HDA No sound after Standby

2008-08-28 Thread José M . Vaz
Hello, I tried the 2.6.27 kernels available at: http://kernel.ubuntu.com/pub/next/2.6.27-rc3/hardy/ ... But after numerous reboots, the resume never completes, and the machine hangs. Are there any other 2.6.27 kernel packages available for testing ? Where ? Else, I'll try to test Alpha5, when

[Bug 183365] Re: Must be root to change screen brightness [regression from gutsy]

2008-02-18 Thread José M . Vaz
The two last hardy betas no longer have this problem. This bug report can be closed. I'll reopen it, if i have the same problem again. ** Changed in: smartdimmer (Ubuntu) Status: New = Fix Released -- Must be root to change screen brightness [regression from gutsy]

[Bug 183365] Re: Must be root to change screen brightness [regression from gutsy]

2008-01-19 Thread José M . Vaz
with non root permissions: [EMAIL PROTECTED]:~$ smartdimmer -s10 init_nvclock() failed! with root permissions: [EMAIL PROTECTED]:~# smartdimmer -s10 [EMAIL PROTECTED]:~# (and the screen brightness is changed) -- Must be root to change screen brightness [regression from gutsy]

[Bug 183365] Re: Must be root to change screen brightness [regression from gutsy]

2008-01-19 Thread José M . Vaz
The attachment is the output of stracing as a standard user, running the following command: strace smartdimmer -s10 ** Attachment added: strace without root permissions http://launchpadlibrarian.net/11442845/smartdimmer.user -- Must be root to change screen brightness [regression from

[Bug 183365] Re: Must be root to change screen brightness [regression from gutsy]

2008-01-19 Thread José M . Vaz
The attachment is the output of stracing as a root user, running the following command: strace smartdimmer -s10 (this attachment is zipped since the uncompressed strace dump is large (141Kb) because there are a lot of gettimeofday(...) calls in the dump ** Attachment added: strace with root

[Bug 183365] Must be root to change screen brightness [regression from gutsy]

2008-01-15 Thread José M . Vaz
Public bug reported: Binary package hint: smartdimmer In the current hardy development release (as of15/Jan/2008) smartdimmer requires root permissions to work. In the previous ubuntu release, any user could change screen brightness without having to resort to sudo. The video card id is:

[Bug 119935] Duplicate hotkey

2007-06-11 Thread José M . Vaz
Public bug reported: Binary package hint: software-properties-gtk In the program interface, the tab Third Party Software has the kotkey [Alt-R] as a duplicate hotkey for Remove and Revert buttons ** Affects: software-properties (Ubuntu) Importance: Undecided Status: Unconfirmed

[Bug 119935] Re: Duplicate hotkey

2007-06-11 Thread José M . Vaz
** Attachment added: Picture with highlighted duplicated hotkey http://launchpadlibrarian.net/8055392/alt-r%2C%20duplicate%20hotkey.png -- Duplicate hotkey https://bugs.launchpad.net/bugs/119935 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug

[Bug 84760] Re: Regression: Sound volume hotkeys stopped working

2007-02-13 Thread José M . Vaz
* In File-Change device my current selection is HDA Intel (Alsa mixer) * With [Right Mouse button]-Preferences the channel selected is Master I tried all other devices (oss mixer), and channel combinations, but to no avail. -- Regression: Sound volume hotkeys stopped working

[Bug 84760] Problem solved!!

2007-02-13 Thread José M . Vaz
I was using volume applet in the upper panel. I ran gnome-sound-properties and by playing around and ticking Enable Software sound mixing (ESD), I was able to restore volume keys function. Problem solved! Thank you for pointing me to gnome-sound-properties. The thing is, how come software sound

[Bug 84760] Regression: Sound volume hotkeys stopped working

2007-02-12 Thread José M . Vaz
Public bug reported: Some update about 2 weeks ago broke sound volume hotkeys functionality: When I press any of the volume up/down keys, OSD info appears, but the bar is empty, and does not increase. Sound card sound volume doesn't change either. I can change the volume in sound volume

[Bug 28834] [feisty] Keyboard volume hotkeys stopped working

2007-02-11 Thread José M . Vaz
I have the same problem in feisty, in a sony vaio laptop: VGN-FE31H. The keys used to work OK, but some update about 2 weeks ago broke their functionality. When I press any of the OSD info appears, but the bar is empty, and does not increase. I can change the volume in sound volume applet.

Re: [Bug 78257] Re: No sound after computer exits standby

2007-02-03 Thread José M . Vaz
Daniel T Chen wrote: Is this symptom still reproducible with 2.6.20-6.11? Yes. It is reproducible with 2.6.20-6.11 -- No sound after computer exits standby https://launchpad.net/bugs/78257 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com

[Bug 78257] Re: No sound after computer exits standby

2007-01-07 Thread José M . Vaz
lspci -nv attached ** Attachment added: output of lspci -nv http://librarian.launchpad.net/5622190/lspci.txt -- No sound after computer exits standby https://launchpad.net/bugs/78257 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com

[Bug 78263] [/etc/resolv.conf] Extra slow login / app launch

2007-01-06 Thread José M . Vaz
Public bug reported: Binary package hint: network-manager [Running NM 0.6.4 on feisty] Since NM keeps /etc/resolv.conf between reboots, major slowdown can happen to the whole desktop if the networks changes between reboots. Consider the following scenario, at different locations: 1) At work

[Bug 78257] Re: No sound after computer exits standby

2007-01-06 Thread José M . Vaz
Same behavior with 2.6.20-5 kernel string: (Linux Papaleguas-Duo 2.6.20-5-generic #2 SMP Sat Jan 6 14:50:47 UTC 2007 i686 GNU/Linux) I'm attaching dmesg output of 2.6.20-5. Thank you for your concern ** Attachment added: dmesg output of 2.6.20-5

Re: [Bug 59095] Re: 100% CPU usage after quiting game

2006-12-22 Thread José M . Vaz
Hello! In 0.1.3 it happened with/without opengl, every time i manually closed the game window, in windowed mode (clicking the top-right close widget) After testing the new supertux (i hadn't installed it yet in my new feisty installation), it seems that the bug no longer exists. I tried

[Bug 59095] 100% CPU usage after quiting game

2006-09-05 Thread José M . Vaz
Public bug reported: Choose start a game in main menu. Press enter, move pinguin in map selection screen , press enter again to start game. Exit the game by click the close button in the top right corner. The window closes but the process starts eating all available CPU, until it crashes, or