Public bug reported:
Press Ctrl+Shift+U (start entering a Unicode character by its hex code),
followed by seven alphanumeric characters.
The keyboard stops working. It's no longer possible to enter any keys
into any application, making the system completely unusable. (Tested
with gnome-terminal,
Yup, it's NP300E5Z -- is it really relevant? Sounds like a software only
problem to me :)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1263249
Title:
Keyboard stops working after Ctrl+Shift+U
More precisely, as found on another sticker: NP300E5Z-S07HU (it has a
Hungarian layout)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1263249
Title:
Keyboard stops working after Ctrl+Shift+U fo
Hi Christopher,
This is most definitely *not* a hardware issue, but something with X or
Gtk or Unity or Compiz, or something along these lines.
The bug is triggered by a certain key sequence of entering too many
digits to Unicode characters. In the resulted state, certain keys
(whichever are con
My old laptop (a Samsung NP300E5Z, originally with Precise and upgraded
all the way up to Yakkety) died a few days ago. I cannot tell for 100%
but I'm like 99% sure that this bug still existed there in Yakkety,
otherwise I pretty sure would have noticed being releived by the pain
being gone while u
Is the behavior the same in other apps, e.g. gedit, libreoffice writer,
firefox, etc...?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1720213
Title:
Word moving with left-arrow-ctrl broken
This is a bug in GTK+, just recently fixed in git. For details, see
https://bugzilla.gnome.org/show_bug.cgi?id=789356
https://bugzilla.gnome.org/show_bug.cgi?id=789357
** Bug watch added: GNOME Bug Tracker #789356
https://bugzilla.gnome.org/show_bug.cgi?id=789356
** Bug watch added: GNOME Bug
vte 0.36 (gnome 3.12) changes the function keys to be compatible with
Xterm.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xterm in Ubuntu.
https://bugs.launchpad.net/bugs/96676
Title:
function keys don't work in gnome-terminal
To manage no
I attach a patch to xorg-server which seems to fix it for me. Side
effects are yet to be discovered :)
Rebuild xorg-server with the following series of commands (might not be
the best way, but that's what I found, I'm not yet familiar with these):
sudo apt-get install build-essential fakeroot dpk
A few people confirmed that their system always sends keycode 87 for
keypad 1/End, independently of NumLock's state. They don't face this
bug.
I've connected an external keyboard to my laptop and that one also
always sends 87, as opposed to the built-in one.
Really looks like we're facing some br
I have XKBOPTIONS="" in that file.
Note that I'm using Gnome (Unity) which infamously handles the layout
switch itself nowadays rather than letting X do so (see e.g.
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1244090). I guess
the contents of /etc/default/keyboard are completely overrid
Created attachment 98637
Works for me, probably not the proper solution though
Here's a workaround patch that I've been using successfully for a while.
Upon loading a new keymap, Xkb does something with the locks. I'm not
sure what it is and why it would do so. I just commented out that part
and
The bug is still present in Trusty.
I've installed a Fedora 20, and it's working correctly there. Note that
Ctrl+Shift+U works in xterm under Ubuntu, but does nothing in xterm
under Fedora. This means that probably something is done substantially
differenty in the two distros. I have a feeling
Gtk+ apps: Reproducible with GTK_IM_MODULE=ibus and with
GTK_IM_MODULE=xim. Not reproducible if GTK_IM_MODULE is unset before
launching a Gtk+ app [I guess Ctrl+Shift+U is handled by Gtk+ in this
case, rather than the X Input Method].
xterm: Reproducible with the default XMODIFIERS=@im=ibus, no
I've located the bug. Upstream report:
https://code.google.com/p/ibus/issues/detail?id=1715
** Package changed: xorg (Ubuntu) => ibus (Ubuntu)
** Bug watch added: IBus bugs #1715
http://code.google.com/p/ibus/issues/detail?id=1715
--
You received this bug notification because you are a memb
15 matches
Mail list logo
