From noreply at ubuntu.com Tue Aug 2 09:25:53 2016 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Tue, 02 Aug 2016 09:25:53 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Hotkeys/Troubleshooting=22_by_pe?= =?utf-8?q?nalvch?= Message-ID: <20160802092553.13822.49161@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Hotkeys/Troubleshooting" page has been changed by penalvch: http://wiki.ubuntu.com/Hotkeys/Troubleshooting?action=diff&rev1=43&rev2=44 Comment: 1) Reworded uncompress/untar statement as some don't read it. 2) LiveCD > Live environment 3) Syntax fixes. - This page details the process of debugging the behavior of hotkeys/media keys in Ubuntu. See [[Hotkeys/Architecture]] for an overview of the architecture used for handling hotkey events. + This page details the process of debugging the behavior of hotkeys/media keys in Ubuntu. See [[Hotkeys/Architecture]] for an overview of the architecture used for handling hotkey events. - === Involved Components === + = Involved Components = - Hotkey and ACPI events cross a lot of different layers, and determining the component that is handling them can take quite a bit of digging. Below is a non-comprehensive list of components which have been known to handle hotkey events: + Hotkey and ACPI events cross a lot of different layers, and determining the component that is handling them can take quite a bit of digging. Below is a non-comprehensive list of components which have been known to handle hotkey events: Packages involved in acting on hotkey events: * gnome-settings-daemon (handles media, brightness, and power keys and visual feedback, display toggling) @@ -18, +18 @@ * xkeyboard-config * acpi-support (deprecated, being phased out) - Note that the 'acpi' source package is *not* involved in any of this, although many acpi/hotkey issues get (incorrectly) filed against it. 'acpi' is just a command line tool for listing info about acpi devices. + Note that the 'acpi' source package is *not* involved in any of this, although many acpi/hotkey issues get (incorrectly) filed against it. 'acpi' is just a command line tool for listing info about acpi devices. - === Step-by-step Troubleshooting === + = Step-by-step Troubleshooting = 1. First, upgrade your BIOS to the newest version available. If still reproducible, continue troubleshooting. 1. If `gnome-settings-daemon` is running, stop it first with `killall gnome-settings-daemon`; these daemons grab some X events exclusively and prevent them from being seen with `xev`. @@ -29, +29 @@ }}} 1. if there's a keypress event: a. if the keycode is right, it's a desktop issue; see the list of packages that act on hotkey events for further diagnosis (`gnome-settings-daemon`, `gnome-power-manager`, ...) - * in some cases the keybindings may be wrong, perhaps due to a legacy (i.e., pre-evdev) keymap. You can check your keymap using `gconf-editor` and looking under `/apps/gnome_settings_daemon/keybindings`. Bindings without sensible key names are probably bugs. + * in some cases the keybindings may be wrong, perhaps due to a legacy (i.e., pre-evdev) keymap. You can check your keymap using `gconf-editor` and looking under `/apps/gnome_settings_daemon/keybindings`. Bindings without sensible key names are probably bugs. * for audio volume control hotkeys, gnome-sound-properties may be misconfigured. You can either examine with gconf-editor '/desktop/gnome/sound' or do 'gconftool --recursive-list /desktop/gnome/sound' to get the current settings; the particular configuration items are 'default_mixer_tracks' and 'default_mixer_device'. a. if there are too many keypress events then you need to determine where they are being duplicated. 1. if the key code is wrong, or there is no keypress event, or the key only works once and then the desktop gets "stuck", install the "evtest" package, run `sudo evtest`, select your keyboard device, press the broken keys, and note down their scan code (MSC_SCAN), current keycode (KEY_*), and intended meaning. a. If that was successful, file a bug against udev ("ubuntu-bug udev") and add the scan code → meaning map. - a. If evtest shows a correct key symbol, look up the symbolic name in /usr/include/linux/input.h. If it is mapped to a code over 255 (over 0x0ff), then it is outside X's range see [[https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/313514|bug 313514]]. In this case, if it is important to have the key mapped, the key should be remapped to an appropriate value < 256. + a. If evtest shows a correct key symbol, look up the symbolic name in /usr/include/linux/input.h. If it is mapped to a code over 255 (over 0x0ff), then it is outside X's range see [[https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/313514|bug 313514]]. In this case, if it is important to have the key mapped, the key should be remapped to an appropriate value < 256. 1. If the events are reported by more than one input device then report a kernel bug (Ubuntu `linux` package) because it should only send the event on one device. - 1. if not found with `keymap`, use `acpi_listen` to determine whether the key is coming through as an ACPI event instead of a keypress + 1. if not found with `keymap`, use `acpi_listen` to determine whether the key is coming through as an ACPI event instead of a keypress. a. if there is an ACPI event but no keypress, this is a bug in the kernel (ubuntu-bug linux) for not translating the ACPI event to an input event. - a. if there is neither an ACPI event nor an input event, this is probably also a kernel bug, though probably harder to diagnose (WMI, perhaps?) + a. if there is neither an ACPI event nor an input event, this is probably also a kernel bug, though probably harder to diagnose (WMI, perhaps?). - === Useful Information to Collect in Reports === + = Useful Information to Collect in Reports = - /!\ Open a terminal, run each command below, and include the output files in your report. Please do not compress the files, but attach each individually to the report: + /!\ Open a terminal, run each command below, and attache the output of each file separately, uncompressed, and untarred to your report: * `udevadm info --export-db > udev-db.txt` * `dmesg > dmesg.log` * `sudo lsinput > lsinput.log` @@ -50, +50 @@ * `xkbcomp -xkb :0 - > xkbcomp.txt` * `setxkbmap -print > xkbmap.txt` - === Troubleshooting Tricks and Tips === + = Troubleshooting Tricks and Tips = - * Testing: Before making changes, make a list of all your keys and hit each of them in turn, and record how they work. Repeat this after every change, so you'll know if a change fixed one thing but broke something else. + * Testing: Before making changes, make a list of all your keys and hit each of them in turn, and record how they work. Repeat this after every change, so you'll know if a change fixed one thing but broke something else. - * Run gnome-power-manager in verbose mode (`gnome-power-manager --no-daemon --verbose`) to get detailed debug info + * Run gnome-power-manager in verbose mode (`gnome-power-manager --no-daemon --verbose`) to get detailed debug information. - * In some cases, hotkeys are communicated correctly to X but applications are listening for them as dbus events generated by hal. Use `lshal -m` to monitor which hotkey events are being produced by hal. + * In some cases, hotkeys are communicated correctly to X but applications are listening for them as dbus events generated by hal. Use `lshal -m` to monitor which hotkey events are being produced by hal. - * Experiment with the scripts in /etc/acpi/. These come into play only for *some* hardware and are being phased out, so may not be relevant for your case. + * Experiment with the scripts in /etc/acpi/. These come into play only for *some* hardware and are being phased out, so may not be relevant for your case. * To test sleep modes directly, `echo S3 > /proc/acpi/sleep` - * Switch to a virtual terminal and back (e.g. ctrl+alt+F1 ; ctrl+alt+f7) and see if that resets things + * Switch to a virtual terminal and back (e.g. ctrl+alt+F1 ; ctrl+alt+f7) and see if that resets things. * Switch to the Guest Account and see if the issue can be reproduced. - * Boot a LiveCD and try reproducing it there. If you can't, it suggests either a modification to your system or a software update not present on the LiveCD. + * Boot a Live environment and try reproducing it there. If you can't, it suggests either a modification to your system or a software update not present on the Live environment. - * Create a test user account, log out of all sessions and into that one. If you can't reproduce the issue there, then suspect some stored gconf or other settings in your dot files. (This is less likely if you've recently done a fresh install, vs. upgraded from past versions of Ubuntu.) + * Create a test user account, log out of all sessions and into that one. If you can't reproduce the issue there, then suspect some stored gconf or other settings in your dot files (this is less likely if you've recently done a fresh install, vs. upgraded from past versions of Ubuntu). - * If the key used to work properly at one time, and you've narrowed the problem to a specific component, then try testing different past versions of that package to try to bracket where the regression first started. This can help narrow down what patch might have caused the problem. + * If the key used to work properly at one time, and you've narrowed the problem to a specific component, then try testing different past versions of that package to try to bracket where the regression first started. This can help narrow down what patch might have caused the problem. * Check if a proper keyboard shortcut is mapped to the action in gnome-keybinding-properties. A working shortcut looks like ''XF86AudioMute'' or ''Ctrl+Alt+Tab''. An unknown key mapping looks like ''0xed''. From noreply at ubuntu.com Tue Aug 2 10:01:48 2016 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Tue, 02 Aug 2016 10:01:48 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingKernelSuspend=22_by_pen?= =?utf-8?q?alvch?= Message-ID: <20160802100148.19354.40423@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingKernelSuspend" page has been changed by penalvch: http://wiki.ubuntu.com/DebuggingKernelSuspend?action=diff&rev1=50&rev2=51 Comment: Added spaces as some folks just run the command, and thinking they are done don't attach anything to their report. * Clicked a key on the keyboard 1. While booted into the latest [[https://wiki.ubuntu.com/Kernel/MainlineBuilds|non-daily mainline kernel]], execute at a terminal: {{{ cat /proc/acpi/wakeup > wakeup - }}} + }}} Please attach to your report the resume trace mentioned below. <
> 1. While booted into the latest [[https://wiki.ubuntu.com/Kernel/MainlineBuilds|non-daily mainline kernel]], execute at a terminal:{{{ sudo su echo freezer > /sys/power/pm_test exit - }}} Please attach to your report the resume trace mentioned below. + }}} Please attach to your report the resume trace mentioned below. <
> 1. While booted into the latest [[https://wiki.ubuntu.com/Kernel/MainlineBuilds|non-daily mainline kernel]], execute at a terminal:{{{ sudo su echo devices > /sys/power/pm_test exit - }}} Please attach to your report the resume trace mentioned below. + }}} Please attach to your report the resume trace mentioned below. <
> 1. While booted into the latest [[https://wiki.ubuntu.com/Kernel/MainlineBuilds|non-daily mainline kernel]], execute at a terminal:{{{ sudo su echo platform > /sys/power/pm_test exit - }}} Please attach to your report the resume trace mentioned below. + }}} Please attach to your report the resume trace mentioned below. <
> 1. While booted into the latest [[https://wiki.ubuntu.com/Kernel/MainlineBuilds|non-daily mainline kernel]], execute at a terminal:{{{ sudo su echo processors > /sys/power/pm_test exit - }}} Please attach to your report the resume trace mentioned below. + }}} Please attach to your report the resume trace mentioned below. <
> 1. While booted into the latest [[https://wiki.ubuntu.com/Kernel/MainlineBuilds|non-daily mainline kernel]], execute at a terminal:{{{ sudo su echo core > /sys/power/pm_test exit - }}} Please attach to your report the resume trace mentioned below. + }}} Please attach to your report the resume trace mentioned below. <
> 1. While booted into the latest [[https://wiki.ubuntu.com/Kernel/MainlineBuilds|non-daily mainline kernel]], execute at a terminal:{{{ sudo su echo none > /sys/power/pm_test exit - }}} Please attach to your report the resume trace mentioned below. + }}} Please attach to your report the resume trace mentioned below. <
> 1. Please provide the output of the following terminal command: {{{ cat /sys/kernel/debug/suspend_stats }}} - 1. If you have a graphics related issue after resume (corruption, display blank, etc.) please [[https://help.ubuntu.com/community/DebuggingSystemCrash#SSH|SSH]] into your machine and capture both /var/log/Xorg.0.log and /var/log/Xorg.0.log.old. + 1. If you have a graphics related issue after resume (corruption, display blank, etc.) please [[https://help.ubuntu.com/community/DebuggingSystemCrash#SSH|SSH]] into your machine and capture both /var/log/Xorg.0.log and /var/log/Xorg.0.log.old. Please attach each separately. == "resume-trace" debugging procedure for finding buggy drivers == From rsw at americamail.com Tue Aug 23 03:39:18 2016 From: rsw at americamail.com (mark greenberg) Date: Tue, 23 Aug 2016 06:39:18 +0300 Subject: =?utf-8?B?c29tZSBpbmZvcm1hdGlvbg==?= Message-ID: <00009645d5b2$7c6e0ba5$77f1bc19$@americamail.com> Hi friend! There is some information I found recentle, I thought you might like it, please read it here My Best, mark greenberg -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 1725 bytes Desc: not available URL: From steve.lorimer at gmail.com Wed Aug 24 18:59:18 2016 From: steve.lorimer at gmail.com (Steve Lorimer) Date: Wed, 24 Aug 2016 13:59:18 -0500 Subject: Bug in Ubuntu 16.04 stock gcc-5.4.0 standard library Message-ID: Consider the following small test application: #include #include #include int main(){ double d = NAN; std::cout << std::isnan(d) << '\n'; std::cout << isnan(d) << '\n'; return 0;} Compiling on Ubuntu 16.04 with g++-5.4.0 using C++11 standard fails: $ g++ -std=c++11 main.cpp main.cpp: In function ‘int main()’: main.cpp:10:25: error: ‘isnan’ was not declared in this scope std::cout << isnan(d) << '\n'; ^ main.cpp:10:25: note: suggested alternative:In file included from main.cpp:3:0:/usr/include/c++/5/cmath:641:5: note: ‘std::isnan’ isnan(_Tp __x) ^ I've compiled this on Centos gcc-4.9.1 and gcc-5.2.1 and it works on both. I've compiled this on Ubuntu gcc-4.9.3 and that too works. However, compiling on Ununtu gcc-5.4.0 doesn't. I've also tried several online compilers, with mixed results. Wandbox has gcc-6.3.0, gcc-5.2.0, gcc-5.1.0 and they all compiled fine. Godbolt broke for gcc-4.9.2 through gcc-5.3, but then works on 6.1. Given it works for gcc-5.2.0 on Wandbox and breaks for gcc-5-2.0 on Godbolt makes me thing one must be using a patched standard library. Not sure how to report this bug? -------------- next part -------------- An HTML attachment was scrubbed... URL: From es20490446e at gmail.com Wed Aug 24 22:14:36 2016 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Thu, 25 Aug 2016 00:14:36 +0200 Subject: Bug in Ubuntu 16.04 stock gcc-5.4.0 standard library In-Reply-To: References: Message-ID: <3f41659d-9cd2-8e19-4d6f-704ba6db9865@gmail.com> Steve Lorimer: > Not sure how to report this bug? (https://bugs.launchpad.net/ubuntu/+source/gcc-5/+filebug?no-redirect) -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4747 bytes Desc: S/MIME Cryptographic Signature URL: From mm at ekimia.fr Sun Aug 28 14:23:36 2016 From: mm at ekimia.fr (Michel Memeteau - EKIMIA) Date: Sun, 28 Aug 2016 16:23:36 +0200 Subject: Missing feedback on critical bug Message-ID: Hi , I'd like some feeback on this bug : https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1580882 This seems to impact any Brodwell-U after suspend. Any help welcome. <------------------------------------------------------------------------------------------------------------------> Michel Memeteau - Directeur. Notre Boutique Ordinateurs GNU/Linux : http://shop.ekimia.fr 280 avenue de la malvesine 13720 La Bouilladisse - France. Fixe : +33 (0) 972308334 Mobile : +33(0) 624808051 <------------------------------------------------------------------------------------------------------------------> -------------- next part -------------- An HTML attachment was scrubbed... URL: From es20490446e at gmail.com Sun Aug 28 15:03:22 2016 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Sun, 28 Aug 2016 17:03:22 +0200 Subject: Missing feedback on critical bug In-Reply-To: References: Message-ID: <067682ab-e252-615b-7d77-d1e607fba44f@gmail.com> Michel Memeteau: > I'd like some feeback on this bug. I have realised that the upstream bug tracker for (https://launchpad.net/alsa-driver) seems gone! Normally you'll see more feedback by reporting upstream, but (http://www.alsa-project.org) isn't responding. Anybody knows where the project is hosted now? -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4747 bytes Desc: S/MIME Cryptographic Signature URL: From rsw at americamail.com Wed Aug 31 12:45:56 2016 From: rsw at americamail.com (rsw) Date: Wed, 31 Aug 2016 15:45:56 +0300 Subject: it's magic! Message-ID: <0000112553f1$64e458b0$fb0d84a9$@americamail.com> Dear! Have you already seen that? It's pure magic! Just take a look here Best Wishes, rsw -------------- next part -------------- An HTML attachment was scrubbed... URL: