Mats Ahlgren, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .
If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report: apport-collect -p xorg-server REPLACE-WITH-BUG-NUMBER Please note, given you already have done this in a prior release, performing this on a release prior to Trusty would not be helpful. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Changed in: xorg-server (Ubuntu) Importance: Undecided => Low ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/768567 Title: x11 keyboard: xkb pointer emulation broken and hard freezing, 100% reproducible Status in “xorg-server” package in Ubuntu: Incomplete Bug description: This worked before absolutely just fine in karmic koala, but now it is crashing and bringing down the entire operating system. ctrl-alt-f1 and ctrl-alt-bksp are not working, and a hard reboot is required. ___Steps to reproduce___ Add a custom symbol file and load it via xkbcomp. The file which produces this behavior is attached and in /usr/share/X11/xkb/symbols/reachable ___Instructions for how to use xkb___ Run [xkbcomp -w 4 schema.txt $DISPLAY], where schema.txt contains the output of [setxkbmap -print], but with '+reachable' added to the xkb_symbols clause. ___Symptoms___ Holding down right-alt+i should normally produce the Up Arrow key, but in this version of the operating system, the system will hard-freeze, such that no keyboard or mouse input seems to arrive at the screen at all. This may take a few keystrokes, or holding it down so it autorepeats, to trigger the freeze. Otherwise the arrow key does not seem to work (as it had before). This can also be replicated on any window, but works reliably on chromium while holding down ctrl+(ralt+[) and holding it down. Furthermore, if you hit shift-alt-numlk to enable Mouse Keys, you will be able to emulate the mouse buttons, via ralt+h,n,m. These used to work just fine in karmic, but now whenever they are pressed, on keydown (I think), the pointer jumps a large way across the screen. The amount jumped is roughly described as follows: If the pointer is on the bottom-right portion of the screen, the pointer jumps a few hundred pixels to the left and slightly fewer (but still a few hundred pixels) upwards. If the point is on the bottom-left portion of the screen, the pointer jumps up and to the left a few hundred pixels, but a bit less than before, and now more towards the direction of the top- left corner. If the pointer is in the top-left corner of the screen, the pointer jumps much less than a hundred pixels, in the direction of the top left corner. It's as if every time any mouse button is pressed, the pointer leaps towards the left side of the screen, and moves slightly towards the top-left corner of the screen, each time jumping a smaller and smaller amount, such that it never quite reaches there. If none of these keys are pressed, the system seems otherwise fairly stable (I am writing this bug right now with this custom setting, but if I use any of these particular key combos, my system will hard- freeze and I will lose my bug report...). Additionally I mention the following for completeness: This is probably unrelated to the fact that in karmic, every few hours when using this setup, all keyboard input will become impossible. The mouse button will still work, but every time one wishes to type a letter, one has to press and hold a key; apparently, autorepeat is able to make the keys work, but the first press does not input anything. Thus typing 'ctrl-S' would take about 5 seconds, since you had to hold down ctrl so it would be autorepeating, then hold down S so it would be autorepeating. This is probably a separate issue from the one I am reporting now. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: xserver-common 2:1.7.6-2ubuntu7.5 ProcVersionSignature: Ubuntu 2.6.32-31.61-generic 2.6.32.32+drm33.14 Uname: Linux 2.6.32-31-generic x86_64 NonfreeKernelModules: fglrx Architecture: amd64 Date: Thu Apr 21 15:24:05 2011 EcryptfsInUse: Yes InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) PackageArchitecture: all ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: xorg-server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/768567/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
