Public bug reported:
Some time ago I bought a kingston pen drive that I discovered to be a
generic crap, but at least it worked initially. Now appears that with
the latest kernels it stopped working.
Any genuine usb devices that I have works including a genuine kingston
flash drive. The only one
Follows the output of lspci -nn on my Toshiba Satellite U305-S2804:
[EMAIL PROTECTED]:~$ lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation Mobile PM965/GM965/GL960 Memory
Controller Hub [8086:2a00] (rev 03)
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960
For me it didn't worked, but my problem is a little different (the same
problem with the function key that controls the volume), any suggestion?
--
X never sees brightness key release events
https://bugs.launchpad.net/bugs/261721
You received this bug notification because you are a member of
Same problem for me on a Toshiba Satellite U305, after changing the
volume the volume bar graph stays blinking on the screen and the
keyboard and right mouse button stops responding. Going to a virtual
terminal and comming back make it work again.
--
Multimediakeys crashes on pressing
Thanks for the last tip, Im using the desktop ISO booting from a pen
drive, my list is empty but if umount the partitions of my hard disk
(that are mounted by default) and start the installer again the
partitioner goes forward.
Appears just to be a problem with the partitions already being
For me it doesn't happens with the brightness key but when I change the
volume, Im using a Toshiba U305, as already reported switching to a
virtual terminal, pressing alt+prtscr+r and returning to X make the
keyboard and right click work again. Its really anoying.
--
X never sees brightness key
The right-hand Windows key works fine, and you are right, Compose , c
generates ç in my keyboard too. And the last part too, Im used to type these
characters without the compose key. Like that:
' e = é
~ a = ã
' u = ú
' c = ç
So the difference is that until now Im used to type ' c to generate ç
** Summary changed:
- Us_intl keyboard doesnt generate ç for brazilian portuguese locale using
UTF-8
+ Us_intl keyboard doesnt generate ç with 'c sequence for brazilian portuguese
locale using UTF-8
--
Us_intl keyboard doesnt generate ç with 'c sequence for brazilian portuguese
locale using
Public bug reported:
Binary package hint: console-setup
After a lot of problems with accents using UTF-8 on the console in Dapper Drake
(Bug 19487), console-tools fixed almost all of them.
I have a us_intl keyboard and when use it with a pt_BR.UTF-8 locale I can't
type a ç, '+c doesnt generate
Tested in Edgy, almost all characters works now in exception of ç
(only with us_intl keyboards), opened a new bug report for the console-
setup package which is used now in turn of console-data (Bug 66978).
--
Accentuated keys not working on text-mode console, portuguese keyboard
in /etc/default/console-setup
XKBMODEL=pc105
XKBLAYOUT=us
XKBVARIANT=alt-intl (with intl the behavior is the same)
XKBOPTIONS=lv3:ralt_switch,compose:rwin
These options was changed and tested using dkg-reconfigure console-
setup and reloaded with /etc/init.d/console-setup restart
Appears to be
Again.
This bug remains in Dapper Drake and for servers without graphical interface is
impossible to use pt_BR.UTF-8 and be able to type accentuated characters at the
console. Changing the LANG variable to pt_BR using the ISO-8859-1 charset works.
--
Accentuated keys not working on text-mode
12 matches
Mail list logo
