[Touch-packages] [Bug 1552844] Re: Ghost touch events on MX4
Great, if there's anything I can do to help, I'd be happy to. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1552844 Title: Ghost touch events on MX4 Status in Canonical System Image: Confirmed Status in unity8 package in Ubuntu: Incomplete Bug description: When I attempt to use the phone I haven't used for a bit, I am sometimes unable to unlock it because it seems to be processing touch events (a very long series of them) even though I am not touching the screen at the moment. It usually ends up in it being locked due to too many wrong unlock attempts, and I end up force-rebooting it. Since it's locked, I can't even get to adb shell. It still registers actual touch events, just interleaved with these ghost touches, and one time I managed to unlock it, but couldn't do any more debugging because I wasn't near the computer at the time. It also made it worse because now it was doing random touches in my applications, initiating calls and such. I can reproduce this most easily if I carry the phone in my trouser pocket for a while, though I don't always get it. I suspect hardware still detects the phone rubbing against my inner trousers as touch events, and I suspect the lock button is pressed accidentally. This has been happening for a long while with my MX4 Ubuntu edition, and I am on the latest OTA update. Let me know where should I look for log files to find what has been going wrong here? Note that this happens in the lock screen, but continues on even if I manage to unlock the screen while these spurious touches continue to happen, so it might be even lower level than unity8. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552844/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1552844] Re: Ghost touch events on MX4
I do have bluetooth enabled, but I've never attached a keyboard or any other input device to it. I've only used that to connect to the bluetooth system in the car (I believe the car acts as a bluetooth headset, though it supports rSAP as well, but I'd be surprised if Ubuntu Touch does: I think only my Nokia N9 and other Nokia phones of old supported rSAP). ** Changed in: canonical-devices-system-image Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1552844 Title: Ghost touch events on MX4 Status in Canonical System Image: New Status in unity8 package in Ubuntu: Incomplete Bug description: When I attempt to use the phone I haven't used for a bit, I am sometimes unable to unlock it because it seems to be processing touch events (a very long series of them) even though I am not touching the screen at the moment. It usually ends up in it being locked due to too many wrong unlock attempts, and I end up force-rebooting it. Since it's locked, I can't even get to adb shell. It still registers actual touch events, just interleaved with these ghost touches, and one time I managed to unlock it, but couldn't do any more debugging because I wasn't near the computer at the time. It also made it worse because now it was doing random touches in my applications, initiating calls and such. I can reproduce this most easily if I carry the phone in my trouser pocket for a while, though I don't always get it. I suspect hardware still detects the phone rubbing against my inner trousers as touch events, and I suspect the lock button is pressed accidentally. This has been happening for a long while with my MX4 Ubuntu edition, and I am on the latest OTA update. Let me know where should I look for log files to find what has been going wrong here? Note that this happens in the lock screen, but continues on even if I manage to unlock the screen while these spurious touches continue to happen, so it might be even lower level than unity8. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552844/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1552844] Re: Ghost touch events on MX4
Right, thanks. If there's anything I can do to collect more information when it does happen (though sometimes that's very hard), do let me know. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1552844 Title: Ghost touch events on MX4 Status in Canonical System Image: New Status in unity8 package in Ubuntu: Incomplete Bug description: When I attempt to use the phone I haven't used for a bit, I am sometimes unable to unlock it because it seems to be processing touch events (a very long series of them) even though I am not touching the screen at the moment. It usually ends up in it being locked due to too many wrong unlock attempts, and I end up force-rebooting it. Since it's locked, I can't even get to adb shell. It still registers actual touch events, just interleaved with these ghost touches, and one time I managed to unlock it, but couldn't do any more debugging because I wasn't near the computer at the time. It also made it worse because now it was doing random touches in my applications, initiating calls and such. I can reproduce this most easily if I carry the phone in my trouser pocket for a while, though I don't always get it. I suspect hardware still detects the phone rubbing against my inner trousers as touch events, and I suspect the lock button is pressed accidentally. This has been happening for a long while with my MX4 Ubuntu edition, and I am on the latest OTA update. Let me know where should I look for log files to find what has been going wrong here? Note that this happens in the lock screen, but continues on even if I manage to unlock the screen while these spurious touches continue to happen, so it might be even lower level than unity8. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552844/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1552844] [NEW] Ghost touch events on MX4
Public bug reported: When I attempt to use the phone I haven't used for a bit, I am sometimes unable to unlock it because it seems to be processing touch events (a very long series of them) even though I am not touching the screen at the moment. It usually ends up in it being locked due to too many wrong unlock attempts, and I end up force-rebooting it. Since it's locked, I can't even get to adb shell. It still registers actual touch events, just interleaved with these ghost touches, and one time I managed to unlock it, but couldn't do any more debugging because I wasn't near the computer at the time. It also made it worse because now it was doing random touches in my applications, initiating calls and such. I can reproduce this most easily if I carry the phone in my trouser pocket for a while, though I don't always get it. I suspect hardware still detects the phone rubbing against my inner trousers as touch events, and I suspect the lock button is pressed accidentally. This has been happening for a long while with my MX4 Ubuntu edition, and I am on the latest OTA update. Let me know where should I look for log files to find what has been going wrong here? Note that this happens in the lock screen, but continues on even if I manage to unlock the screen while these spurious touches continue to happen, so it might be even lower level than unity8. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Description changed: - When I take the phone I haven't used for a while, I am sometimes unable - to unlock it because it seems to be processing touch events (a very long - series of them) even though I am not touching the screen at the moment. - It usually ends up in it being locked due to too many wrong unlock - attempts, and I end up force-rebooting it. + When I attempt to use the phone I haven't used for a bit, I am sometimes + unable to unlock it because it seems to be processing touch events (a + very long series of them) even though I am not touching the screen at + the moment. It usually ends up in it being locked due to too many wrong + unlock attempts, and I end up force-rebooting it. Since it's locked, I can't even get to adb shell. It still registers actual touch events, just interleaved with these ghost touches, and one time I managed to unlock it, but couldn't do any more debugging because I wasn't near the computer at the time. It also made it worse because now it was doing random touches in my applications, initiating calls and such. I can reproduce this most easily if I carry the phone in my trouser pocket for a while, though I don't always get it. I suspect hardware still detects the phone rubbing against my inner trousers as touch events, and I suspect the lock button is pressed accidentally. This has been happening for a long while with my MX4 Ubuntu edition, and I am on the latest OTA update. Let me know where should I look for log files to find what has been going wrong here? Note that this happens in the lock screen, but continues on even if I manage to unlock the screen while these spurious touches continue to happen, so it might be even lower level than unity8. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1552844 Title: Ghost touch events on MX4 Status in unity8 package in Ubuntu: New Bug description: When I attempt to use the phone I haven't used for a bit, I am sometimes unable to unlock it because it seems to be processing touch events (a very long series of them) even though I am not touching the screen at the moment. It usually ends up in it being locked due to too many wrong unlock attempts, and I end up force-rebooting it. Since it's locked, I can't even get to adb shell. It still registers actual touch events, just interleaved with these ghost touches, and one time I managed to unlock it, but couldn't do any more debugging because I wasn't near the computer at the time. It also made it worse because now it was doing random touches in my applications, initiating calls and such. I can reproduce this most easily if I carry the phone in my trouser pocket for a while, though I don't always get it. I suspect hardware still detects the phone rubbing against my inner trousers as touch events, and I suspect the lock button is pressed accidentally. This has been happening for a long while with my MX4 Ubuntu edition, and I am on the latest OTA update. Let me know where should I look for log files to find what has been going wrong here? Note that this happens in the lock screen, but continues on even if I manage to unlock the screen while these spurious touches continue to happen, so it might be even lower level than unity8. To manage notifications about this bug go to:
[Touch-packages] [Bug 1467595] Re: cursor sometimes disappears on XPS 13 9343 and external monitor
I've also seen on my Fujitsu U904 (3200x1800) connected over DP to the external 4k screen. I've worked around it by using Ctrl to highlight the cursor position until the cursor returns (sometimes it takes more than a couple of hours, and the only sure way to get it back is to log out and log back in — switching to terminal console or suspending and resuming does not help). Will attach more info once I hit it again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1467595 Title: cursor sometimes disappears on XPS 13 9343 and external monitor Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: I have a new Dell XPS 13 9343 with the HiDPI touch screen and am using an external display port monitor. Occasionally, the mouse cursor disappears (sometimes after screen lock, other times just normal usage). I saw something on stack exchange that said this might help: gsettings set org.gnome.settings-daemon.plugins.cursor active false I've done this and it sometimes helps and sometimes doesn't. I've also just seen the cursor come back on its own after a few minutes without doing anything. Trying to interact with the touch screen, then the mouse has no effect. Unplugging and replugging the mouse has no effect. Using the touchpad has no effect. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150420-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Jun 22 11:19:40 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.19.0-18-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 3.19.0-20-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 3.19.0-21-generic, x86_64: installed GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0665] InstallationDate: Installed on 2015-06-13 (8 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: Dell Inc. XPS 13 9343 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic root=UUID=7bc4dcd2-0bd8-4e42-b8b7-9f1ed6b8a3e9 ro libata.force=noncq quiet splash vt.handoff=7 SourcePackage: unity UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0310JH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd03/25/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Mon Jun 22 10:53:54 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5153 vendor SHP xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1467595/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1326954] Re: ModemManager does not seem to recognize Sierra Wireless EM7305 (Fujitsu Lifebook S904)
FWIW, additional details are given in a threads http://permalink.gmane.org/gmane.linux.network/319839 http://lists.freedesktop.org/archives/modemmanager-devel/2014-June/001213.html (I am experiencing exactly the same problems). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1326954 Title: ModemManager does not seem to recognize Sierra Wireless EM7305 (Fujitsu Lifebook S904) Status in ModemManager (with NetworkManager support): New Status in “libmbim” package in Ubuntu: Confirmed Status in “modemmanager” package in Ubuntu: Invalid Bug description: Ubuntu 14.04, x86_64, ModemManager-1.0.0-2ubuntu1 Card: Sierra Wireless EM7305 (PCI Express M.2 form factor) Expected: Sierra plugin is used Happens: Generic plugin is used instead After cold start the card seems to work almost fine, but does not come back after suspend or hibernate. At least after hibernate MM may go into a tight loop consuming 100% CPU. MM debug log output (full log attached): debug [1401992536.121631] [mm-plugin-manager.c:576] build_plugins_list(): (Plugin Manager) [wwan0] Found '1' plugins to try... debug [1401992536.125236] [mm-plugin-manager.c:580] build_plugins_list(): (Plugin Manager) [wwan0] Will try with plugin 'Generic' debug [1401992536.128923] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested debug [1401992536.132687] [mm-plugin-manager.c:505] plugin_supports_port_ready(): (Plugin Manager) [wwan0] deferring support check until result suggested debug [1401992536.142664] [mm-port-probe.c:536] wdm_probe_mbim(): (usbmisc/cdc-wdm0) probing MBIM... debug [1401992538.202591] [mm-plugin-manager.c:646] min_probing_timeout_cb(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] Minimum probing time consumed [/dev/cdc-wdm0] Queried max control message size: 4096[/dev/cdc-wdm0] Sent message... RAW: length = 16 data = 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00 [/dev/cdc-wdm0] Sent message (translated)... Header: length = 16 type= open (0x0001) transaction = 1 Contents: max_control_transfer = 4096 [/dev/cdc-wdm0] Received message... RAW: length = 16 data = 01:00:00:80:10:00:00:00:01:00:00:00:00:00:00:00 debug [1401992539.481429] [mm-port-probe.c:300] mm_port_probe_set_result_mbim(): (usbmisc/cdc-wdm0) port is MBIM-capable [/dev/cdc-wdm0] Sent message... RAW: length = 12 data = 02:00:00:00:0C:00:00:00:02:00:00:00 [/dev/cdc-wdm0] Sent message (translated)... Header: length = 12 type= close (0x0002) transaction = 2 [/dev/cdc-wdm0] Received message... RAW: length = 16 data = 02:00:00:80:10:00:00:00:02:00:00:00:00:00:00:00 debug [1401992539.545529] [mm-plugin-manager.c:417] plugin_supports_port_ready(): (Plugin Manager) (Generic) [cdc-wdm0] found best plugin for port debug [1401992539.549361] [mm-plugin-manager.c:334] suggest_port_probe_result(): (Plugin Manager) (Generic) [wwan0] deferred task completed, got suggested plugin debug [1401992539.553247] [mm-plugin-manager.c:274] port_probe_context_finished(): (Plugin Manager) 'cdc-wdm0' port probe finished, still 1 running probes in this device (wwan0) debug [1401992539.556995] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested debug [1401992539.560690] [mm-plugin-manager.c:485] plugin_supports_port_ready(): (Plugin Manager) (Generic) [wwan0] task completed, got suggested plugin debug [1401992539.564175] [mm-plugin-manager.c:285] port_probe_context_finished(): (Plugin Manager) 'wwan0' port probe finished, last one in device debug [1401992539.567868] [mm-plugin-manager.c:107] find_device_support_context_complete_and_free(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] device support check finished in '3.677528' seconds info [1401992539.571611] [mm-device.c:486] mm_device_create_modem(): Creating modem with plugin 'Generic' and '2' ports debug [1401992539.575477] [generic/mm-plugin-generic.c:73] create_modem(): MBIM-powered generic modem found... mmcli output: /org/freedesktop/ModemManager1/Modem/0 (device id 'b3a77501ed8da196baa804a4142ff280766f6f98') - Hardware | manufacturer: 'Generic' | model: 'MBIM [1199:9063]' | revision: 'SWI9X15C_01.12' | supported: 'gsm-umts, lte' |current: 'gsm-umts, lte' | equipment id: '356906050069168' - System | device: '/sys/devices/pci:00/:00:14.0/usb1/1-6' |drivers: 'cdc_mbim' | plugin: 'Generic' | primary port:
