[Bug 1774242] Re: Wacom touchscreens should use libinput, not wacom driver
Just a note (mostly to other distro maintainers that may come across this) that an alternative to completely disabling the Wacom driver's touchscreen handling is to just add `Option "Gesture" "Off"` to the touchscreen section of 70-wacom.conf instead. The driver currently defaults to consuming all multitouch events to power its own (very limited) gesture recognizer, but the above config option will let it pass everything through to the desktop and applications. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774242 Title: Wacom touchscreens should use libinput, not wacom driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1774242/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822633] Re: Pairing failure with BLE 4.0
I've recently found that while pairing with this pen does not work, "merely" connecting to the pen does work. That is: # This command fails $ echo -e "scan on\npair \nscan off" | bluetoothctl # But this command works $ echo -e "scan on\nconnect \nscan off" | bluetoothctl Looking through the hcidump logs, it appears that "connect" has lower (really, "no") security requirements, which could explain why it succeeds where pairing fails (the AuthReq = 00 sent from the device implies it doesn't want/support security). I see that GNOME ships /usr/share/gnome-bluetooth/pin-code-database.xml which defines default PINs. Inside the file, it says "the special NULL pin means that the devices will not be paired, but connected to and marked as trusted. This is for devices such as mice and joypads where there is no encryption." If I add the pen to the database by adding the following lines at the top of the "device" section, GNOME pairing starts working (although it seems to be a little hit-or-miss): With the connection fix in place, a new issue has been identified. Specifically, the kernel input device is removed after processing just a single Bluetooth HID event. Looking at the output of "journalctl -b0", I see the following error message logged, followed by normal device disconnect messages: bluetoothd[6318]: Error Reading PNP_ID value: Request attribute has encountered an unlikely error Looking at the hcidump logs, it seems that when the pen's Bluetooth button is pressed, it briefly wakes up only long enough to send a HID report to the system. After doing so, it disconnects to save power. The logs show that the system begins requesting information from the device when it connects, and that it gets a response to some of those requests, but at some point (e.g. when asking for PNP_ID) the device goes to sleep and a response is never returned. It would seem that there either the system needs to not re-ask the device for information like PNP-ID (which it already received in the initial "connect" process and should have associated with its MAC) or to not be so stringent when these requests fail. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822633 Title: Pairing failure with BLE 4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1822633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822633] Re: Pairing failure with BLE 4.0
I've just built and installed the master branch of gnome-bluetooth (commit b4edf6a8) and didn't see any behavioral change. Since it isn't even possible to pair through bluetoothctl, I wasn't particularly hopeful that an update to gnome-bluetooth would fix things. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822633 Title: Pairing failure with BLE 4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1822633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807235] [NEW] Wacom tablet stops working when fwupd runs
Public bug reported: Certain Wacom tablets appear to be incompatible with fwupd and stop working as soon as the fwupd service starts. Because the fwupd service starts a few seconds after the desktop loads on my test machine, the tablet initially appears to work after a reboot but then "disappears" (no longer listed in xsetwacom) after perhaps 30 seconds. In addition to the tablet disappearing, the following message is logged: `failed to add USB device :: Failed to get feature report: endpoint stalled or request not supported` More details in the upstream bug report: https://github.com/hughsie/fwupd/issues/882. A patch has been accepted and should be present in the next release. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: fwupd 1.1.2-1 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 6 09:09:02 2018 InstallationDate: Installed on 2018-11-28 (7 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: fwupd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: fwupd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807235 Title: Wacom tablet stops working when fwupd runs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1807235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748876] Re: One by Wacom (medium tablet) not reported by libwacom
In addition to the Linux 4.16 requirement pointed out by Michael, Ubuntu will need to update libwacom to at least version 0.28 for the device to appear in the control panel. Until Ubuntu includes updates, you can build libwacom from source[1][2] as well as get the "input-wacom" kernel backports (version 0.39.0 added support for these devices)[3][4]. [1]: https://github.com/linuxwacom/libwacom/releases [2]: https://github.com/linuxwacom/libwacom/wiki [3]: https://github.com/linuxwacom/input-wacom/releases [4]: https://github.com/linuxwacom/input-wacom/wiki/Installing-input-wacom-from-source -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748876 Title: One by Wacom (medium tablet) not reported by libwacom To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwacom/+bug/1748876/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1753525] Re: Wacom tablet not recognized in Settings > Devices
linuxcub, my apologies for not replying sooner -- I don't think I got a notification of your messages for some reason... Its odd that installing/reinstalling portions of Ubuntu seem to fix the issue. It looks like the Bionic beta only relased IOSs for Kubuntu, Budgie, Kylin, MATE, and Xubuntu. I wonder if their GNOME flavor is still in development and was updated to a broken version when you installed. Force-installing the ubuntu-gnome-desktop and gnome-control- center packages may have brought down a fixed version? Without an official GNOME ISO for me to test, it'll be hard for me to replicate your issue to see if its still present. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1753525 Title: Wacom tablet not recognized in Settings > Devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1753525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1753525] Re: Wacom tablet not recognized in Settings > Devices
The "stylus not recognized" part of this issue is almost certainly https://bugzilla.gnome.org/show_bug.cgi?id=793499. No access to the pad device on the other hand is not an issue I'm familiar with. The old unity-control-center bug that OP linked do was due to an issue with GNOME not being compatible with tablets whose pens don't have an eraser. That issue was fixed in GNOME 3.16, however, and shouldn't be present in the current version of the gnome-control-center. I do see a reference to somebody else having similar pad issues upstream at https://bugzilla.gnome.org/show_bug.cgi?id=789287 but it doesn't look like anyone has begun to dig into the bug. My own (Arch Linux) system doesn't exhibit the pad issue with an Intuos Art Medium (CTH-690) and GNOME 3.26, for what its worth. linuxcub: You should have both a "Stylus" and "Tablet" button at the top of the Wacom control panel, next to "Test your Settings". The "Stylus" button shows "Stylus not Recognized", but what message appears when the "Tablet" button is pressed? Or are the buttons missing? That might give a place to start digging... ** Bug watch added: GNOME Bug Tracker #793499 https://bugzilla.gnome.org/show_bug.cgi?id=793499 ** Bug watch added: GNOME Bug Tracker #789287 https://bugzilla.gnome.org/show_bug.cgi?id=789287 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1753525 Title: Wacom tablet not recognized in Settings > Devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1753525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575887] Re: Intuos Art / Intuos Draw 2015 isn't detected by the wacom properties window
linuxcub, the "Stylus not recognized" is actually a different issue than the one described here. The upstream bug filed for that particular issue can be found at https://bugzilla.gnome.org/show_bug.cgi?id=793499 You should file a new issue against Ubuntu 18.04 (specifically the ) which references the GNOME bug I linked to. This will ensure the Ubuntu developers can track the bug and hopefully work with GNOME upstream to get it fixed before the April release. The bug likely affects *all* lower-end tablets (i.e. non-Pro Intuos and Bamboo) based on the diagnosis. It would be appreciated if you could give me a link to the bug you end up filing against 18.04. I'd like to subscribe to it for updates. ** Bug watch added: GNOME Bug Tracker #793499 https://bugzilla.gnome.org/show_bug.cgi?id=793499 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575887 Title: Intuos Art / Intuos Draw 2015 isn't detected by the wacom properties window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1575887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575887] Re: Intuos Art / Intuos Draw 2015 isn't detected by the wacom properties window
Eugenio, the three workarounds I'm aware of are: * Use the GNOME desktop environment instead of Unity. * Use the command-line based `xsetwacom` utility instead of the GUI. * Use a different tablet. I suppose could try getting in touch with the Ubuntu team (e.g. through IRC) to make sure they're both aware that this bug exists and that it has been fixed in upstream GNOME for a while. Recent news is that Ubuntu will be switching to using GNOME instead of Unity in 2018, so even if this bug never gets fixed it should be less visible as fewer people use Unity... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575887 Title: Intuos Art / Intuos Draw 2015 isn't detected by the wacom properties window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1575887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575887] Re: Intuos Art 2015 isn't detected by the wacom propierties window
Bug is in unity-control-center. Upstream gnome-control-center had an issue with not displaying tablets that had no eraser, such as the newest generation of Wacom's Intuos tablets: "Intuos Draw" and "Intuos Art"(models CTL-490, CTH-490, CTL-690, CTH-690). The issue appears to have been fixed for GNOME 3.16 -- the upstream bug report can be found at https://bugzilla.gnome.org/show_bug.cgi?id=746117 See also the bug filed at the linuxwacom project: https://sourceforge.net/p/linuxwacom/bugs/320/ ** Bug watch added: GNOME Bug Tracker #746117 https://bugzilla.gnome.org/show_bug.cgi?id=746117 ** Package changed: xorg (Ubuntu) => unity-control-center (Ubuntu) ** Summary changed: - Intuos Art 2015 isn't detected by the wacom propierties window + Intuos Art / Intuos Draw 2015 isn't detected by the wacom propierties window ** Summary changed: - Intuos Art / Intuos Draw 2015 isn't detected by the wacom propierties window + Intuos Art / Intuos Draw 2015 isn't detected by the wacom properties window -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575887 Title: Intuos Art / Intuos Draw 2015 isn't detected by the wacom properties window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1575887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1548581] Re: using wacom tablet crashes the whole system in 16.04
I'm aware of two Wacom bugs that can cause 4.4 to lockup, both of which have been recently fixed. It would be very good to know if you're experiencing either. Please let us know what Wacom device you are using that causes these lockups. Issue [1] sounds most like the symptoms you describe and affects multiple tablets (Primarily the newest "Intuos" tablets with model numbers CTL-490, CTH-490, CTL-690, and CTH-690). A fix is included in Linux 4.4.2 as well as the linuxwacom project's backported input-wacom 0.30.2 driver. Updating the kernel or installing the input-wacom driver should narrow down if this is the problem. You might try SSHing into your system prior to the lockup, running `sudo journalctl -f`, and then bringing the pen into prox to trigger the lockup -- if you're lucky, after a short time you'll see a kernel LOCKUP message printed out that you can compare to the bug report. Issue [2] I believe is specific to the CTL-471 and CTL-671. The fix has been sent for inclusion in later 4.4 releases but has not yet (as far as I'm aware) yet been accepted. [1]: https://sourceforge.net/p/linuxwacom/bugs/293/ [2]: https://bugzilla.redhat.com/show_bug.cgi?id=1317116 ** Bug watch added: Red Hat Bugzilla #1317116 https://bugzilla.redhat.com/show_bug.cgi?id=1317116 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1548581 Title: using wacom tablet crashes the whole system in 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1548581/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1562387] Re: digimend / wacom drivers do not recognize chinese clone
The xorg.conf.d configuration files are applied one after the other, so your edits to 10-evdev.conf should be unnecessary (since the settings from your 50-huion.conf file will be applied after it). I would suggest filing a bug with linuxwacom (on Sourceforge) indicating that Huion tablets are not covered by the 50-wacom.conf file like other tablets. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1562387 Title: digimend / wacom drivers do not recognize chinese clone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1562387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1310800] Re: 056a:0302 Trusty Tahr, kernel 3.13: automatic load of wacom.ko driver cause a "hard" kernel panic
Trusty and Utopic kernels from -proposed tested and verified to no longer panic. ** Tags removed: verification-needed-trusty verification-needed-utopic ** Tags added: verification-done-trusty verification-done-utopic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1310800 Title: 056a:0302 Trusty Tahr, kernel 3.13: automatic load of wacom.ko driver cause a "hard" kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532052] Re: "no tablet detected" message in system settings for otherwise-working tablet
Also affects Ubuntu 14.04 now that it pairs the 3.19 kernel with the 0.8 libwacom. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532052 Title: "no tablet detected" message in system settings for otherwise-working tablet To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1532052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532052] Re: "no tablet detected" message in system settings for otherwise-working tablet
** Also affects: trusty-backports Importance: Undecided Status: New ** Changed in: libwacom (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532052 Title: "no tablet detected" message in system settings for otherwise-working tablet To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1532052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532052] Re: "no tablet detected" message in system settings for otherwise-working tablet
** Also affects: libwacom (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532052 Title: "no tablet detected" message in system settings for otherwise-working tablet To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1532052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1310800] Re: 056a:0302 Trusty Tahr, kernel 3.13: automatic load of wacom.ko driver cause a "hard" kernel panic
I've taken a long hard look at this bug and believe I've been able to
nail down the cause. The panic is caused by a NULL pointer being passed
to the 'input_report_switch' function. It occurs if the kernel has
probed the tablet's pen/pad interface and processes a status report from
it before the kernel has a chance to probe the tablet's touchpad
interface. The suggested workaround of loading the module before
connecting the tablet only masks the issue by changing the timing of
events enough so that the kernel is able to finish probing both
interfaces before processing the status report.
This issue was addressed upstream by commit 44b9683 ("HID: wacom - make
sure touch_input is valid before using it") which is part of the 3.19
kernel. Both the Trusty (3.13) and Vivid (3.16) kernels are missing this
patch, however. Commit 44b9683 can be trivially backported; I've
attached such a backport for convenience.
** Patch added: "Upstream 44b9683 modified to apply against Ubuntu's 3.13 and
3.16 kernels"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310800/+attachment/4452940/+files/make-sure-touch_input-is-valid-before-using.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310800
Title:
056a:0302 Trusty Tahr, kernel 3.13: automatic load of wacom.ko driver
cause a "hard" kernel panic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310800/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
