[Ubuntu-x-swat] [Bug 1728145] Re: gnome-terminal does not fill screen when window snapping on Wayland in Ubuntu 17.10
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 Tracker #789357 https://bugzilla.gnome.org/show_bug.cgi?id=789357 -- 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/1728145 Title: gnome-terminal does not fill screen when window snapping on Wayland in Ubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1728145/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1720213] Re: Word moving with left-arrow-ctrl broken in wayland
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 in wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1720213/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1247668] Re: NumLock turned off on layout switch
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 using Yakkety for about 1.5 months (since around its final beta freeze). My new laptop (a Dell Inspiron 5559 210771, with a brand new Yakkety installation, same plain pretty much default Unity7, same two keyboard layouts and same Alt+Shift toggle configured) does not suffer from this bug. I enable NumLock, it looks like it stays enabled all the time. In the mean time, changing the layout still switches off Caps Lock, including its feedback LED. Luckily I don't care about this too much. At this point I have no clue whether: - it was some system-wide leftover from the upgrade processes, - it was some leftover in my home directory (I did not [yet] bring over my settings), - or the behavior is somehow hardware related. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1247668 Title: NumLock turned off on layout switch To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1247668/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1247668] Re: NumLock turned off on layout switch
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 overridden by Gnome. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1247668 Title: NumLock turned off on layout switch To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1247668/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1263249] Re: [Samsung NP300E5Z-S07HU] Keyboard stops working after Ctrl+Shift+U followed by 7 alphanumeric keys
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 that this keycombo is handled by Gtk+ in Fedora, but Ubuntu somehow made it more generic and patched it to X.Org – is this possible? ** Changed in: xorg (Ubuntu) Status: Expired = New ** Tags removed: saucy ** Tags added: trusty -- 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: [Samsung NP300E5Z-S07HU] Keyboard stops working after Ctrl+Shift+U followed by 7 alphanumeric keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1263249/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1263249] Re: [Input methods] Keyboard stops working after Ctrl+Shift+U followed by 7 alphanumeric keys
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, not reproducible after unsetting this variable [in this case Ctrl+Shift+U has no special effect]. Really looks that the bug resides in X Input Methods. ** Summary changed: - [Samsung NP300E5Z-S07HU] Keyboard stops working after Ctrl+Shift+U followed by 7 alphanumeric keys + [Input methods] Keyboard stops working after Ctrl+Shift+U followed by 7 alphanumeric keys -- 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: [Input methods] Keyboard stops working after Ctrl+Shift+U followed by 7 alphanumeric keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1263249/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1263249] Re: [Input methods] Keyboard stops working after Ctrl+Shift+U followed by 7 alphanumeric keys
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 member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1263249 Title: [Input methods] Keyboard stops working after Ctrl+Shift+U followed by 7 alphanumeric keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1263249/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1247668]
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 it works great for me. There might be side effects unbeknownst to me. Apparently various manufacturers create keyboards that change the keycode of the numpad keys to their non-numpad equivalents when NumLock is off. Crazy, I know. This is an issue Xkb developers should be aware of. The current behavior on layout change is still not reasonable at all, it's a bug somewhere in Xkb, triggered by such keyboards. Nevertheless, this bug should be fixed. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1247668 Title: NumLock turned off on layout switch To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1247668/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1247668]
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 broken keyboards. Anyway, X's behavior is still not reasonable. When NumLock is on, changing the layout and then pressing a modifier shouldn't trigger the keyboard's brain-damaged geez, NumLock went off, let me alter the keycodes mode, since NumLock didn't turn off at all. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1247668 Title: NumLock turned off on layout switch To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1247668/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1247668] Re: NumLock turned off on layout switch
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 dpkg-dev mkdir build cd build apt-get source xorg-server sudo apt-get build-dep xorg-server cd xorg-server-1.15.1 cp ~/Downloads/xorg-server-xkb-numlock.patch debian/patches/ # replace Downloads appropriately echo xorg-server-xkb-numlock.patch debian/patches/series dpkg-buildpackage -rfakeroot -b cd .. sudo dpkg -i xserver-common_1.15.1-0ubuntu2_all.deb xserver-xorg-core_1.15.1-0ubuntu2_amd64.deb ** Patch added: Works for me, probably not the proper solution though https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1247668/+attachment/4099529/+files/xorg-server-xkb-numlock.patch ** Package changed: gnome-settings-daemon (Ubuntu) = xorg-server (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1247668 Title: NumLock turned off on layout switch To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1247668/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 96676] Re: function keys don't work in gnome-terminal
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 notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/96676/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1263249] Re: Keyboard stops working after Ctrl+Shift+U followed by 7 alphanumeric keys
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 followed by 7 alphanumeric keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1263249/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1263249] Re: Keyboard stops working after Ctrl+Shift+U followed by 7 alphanumeric keys
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 followed by 7 alphanumeric keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1263249/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1263249] Re: [Samsung NP300E5Z-S07HU] Keyboard stops working after Ctrl+Shift+U followed by 7 alphanumeric keys
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 configured to do something in Unity, e.g. Alt+F2) still work, only the ones that are supposed to deliver letters into applications stop working. There's no way the hardware could know anything about this. Moreover, I've just tried starting xev and pressing letters to this. xev properly reports all the keys I press. It's only the normal applications on my desktop (gnome-terminal, firefox, the window I get for Alt+F2 etc.) that stop accepting these letter in their input fields. Again, it's impossible that the hardware would properly generate letters for xev but not for firefox. -- 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: [Samsung NP300E5Z-S07HU] Keyboard stops working after Ctrl+Shift+U followed by 7 alphanumeric keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1263249/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1263249] [NEW] Keyboard stops working after Ctrl+Shift+U followed by 7 alphanumeric keys
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, firefox, gedit, konsole, xterm.) Unity shortcut keys (Alt+Tab etc.) still work. The keyboard layout switcher (Alt+Shift for me) works and resets the keyboard so it's back to normal, although it shouldn't be required, and many users probably don't have such a key defined, or wouldn't figure out they need to press it after the lockup. Side note: After Ctrl+Shift+U, not only hex digits but any letters are accepted and accumulated as the hexadecimal character code, this doesn't make any sense to me. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,move,resize,place,imgpng,snap,session,mousepoll,scale,resizeinfo,gnomecompat,regex,animation,expo,workarounds,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Dec 21 00:00:22 2013 DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: I don't know GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c606] InstallationDate: Installed on 2012-05-30 (569 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: SAMSUNG ELECTRONICS CO., LTD. 300E4Z/300E5Z/300E7Z MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-14-generic root=UUID=570ce59e-b28f-434e-9aef-b608ff12622d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to saucy on 2013-10-12 (69 days ago) dmi.bios.date: 12/14/2011 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 03QB dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 300E4Z/300E5Z/300E7Z dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr03QB:bd12/14/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pn300E4Z/300E5Z/300E7Z:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn300E4Z/300E5Z/300E7Z:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 300E4Z/300E5Z/300E7Z dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Fri Dec 20 23:57:12 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12874 vendor SEC xserver.version: 2:1.14.3-3ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 freeze saucy ubuntu -- 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 followed by 7 alphanumeric keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1263249/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
