The good news is that this does enable the thing to work after resume from suspend.
The bad news is that this kernel panics upon mkfs.ext4. I just tested it again, installing as you suggested rather than using the 17.04 install I had tried before. The 16.04 and 16.10 kernels didn't crash. Both are 4.8 kernels; the new one is 4.10. It's somewhat of a soft crash. The cursor disappears and the keyboard does nothing, but the X window system is still alive and if I tail -f syslog before running mkfs.ext4, I can see the call trace appear (but I can't capture it, and it doesn't get written to disk). A few more messages may appear later. After a few minutes, it goes black but does not reboot. The fan turns on immediately after the crash, at high revs. Should I file a separate bug about the panic? I'm not sure it's technically a panic, as it doesn't say that word, as some other OSes have in the past. But, it's some kind of exceptional kernel event that brings the system down. I'm very happy to run tests to work either problem. --jh-- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1694866 Title: (Alps?) DualPoint Stick disabled but visible after suspend Dell Latitude 7480 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1694866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
