Wacom Intuos S stop working after upgrading to Ubuntu 23.10

Bug #2043027 reported by Gonzalo Rodríguez Carrera
64
This bug affects 8 people
Affects Status Importance Assigned to Milestone
mutter (Ubuntu)
Fix Released
Medium
Unassigned
Mantic
Fix Released
Medium
Unassigned

Bug Description

Impact
------
Clicking does not work correctly with Wacom tablets in the Ubuntu/GNOME X11 sessions

Test Case
---------
One of the people affected by this issue will verify whether their Wacom tablet is working noticably better with the upgraded Mutter packages

What Could Go Wrong
-------------------
The fix for this issue is included in upstream's mutter 45.2 release so please see bug 2043000 as the master bug for this upgrade

Original Bug Report
-------------------
Tablet seems to work until I open Krita (as I could read on Internet, it may be related with Qt Apps).

When Krita is open, mouse movement works ok with the tablet, but when it comes to click action it doesn't work and any further action with mouse is not captured (even outside Krita!).

To regain control of the mouse I have to Alt+Tab and then I can click again.

Some details that may be handy:
- I've got two monitors
- Maybe Qt apps related
- My graphic card is nVidia GTX 1060 6Gb, driver used nvidia-driver-535

Thanks for your effort. I love Ubuntu!

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus.0000.06.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.129.03 Thu Oct 19 18:56:32 UTC 2023
 GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 8 17:20:34 2023
DistUpgraded: 2023-11-08 00:54:28,961 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
 nvidia/535.129.03, 6.2.0-36-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!)
 nvidia/535.129.03, 6.5.0-10-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!)
 virtualbox/7.0.10, 6.2.0-36-generic, x86_64: installed
 virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 6GB] [19da:1438]
InstallationDate: Installed on 2022-04-09 (578 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
 LANG=es_ES.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic root=UUID=9dd904a0-11bb-40fa-9fe8-2f10449a416c ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-11-07 (1 days ago)
dmi.bios.date: 06/15/2020
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0608
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING B550-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0608:bd06/15/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGB550-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

Revision history for this message
Gonzalo Rodríguez Carrera (zaroca) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in xorg (Ubuntu):
status: New → Confirmed
affects: xorg (Ubuntu) → mutter (Ubuntu)
tags: added: wacom
Revision history for this message
Rüdiger Marwein (keinerweisss) wrote :

Hi,

if it is of any help, this problem occurs primarily in GNOME for me.
With XFCE and i3 I tried it as well and there the tablet works fine.

The stylus press freezes the cursor and when I then move the mouse it appears as if it was still pressing down.

Happy to produce any logfiles to debug this, but I do not know how. Advise appreciated.

Best,
Rüdiger

Revision history for this message
Valentin Svilenov Stoyanov (val10) wrote :

Hello,

Might I add, I experience the same issue. My machine is a Lenovo Yoga 7 14ARP8, which is a 2-in-1 convertible. Issue was not present before I upgraded to 23.10 from 22.04.03. If I may augment the "handy details" above:
- I've no dedicated graphics card - AMD Radeon 680M integrated into the CPU;
- The issue persists on tablet mode (fully-folded backwards), laptop mode and when wired to 1 or 2 monitors.

Even if it's an GNOME issue, I would really like to use it for the out-of-the-box touchscreen gestures it offers right away.

Best,
Valentin

Revision history for this message
Jeremy Bícha (jbicha) wrote :

Daniel, this sounds to me like https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3393 which I am cherry-picking into Ubuntu 24.04 and should be in the Ubuntu 23.10 SRU of Mutter 45.2 I hope to propose next week after 45.2 is released.

Jeremy Bícha (jbicha)
Changed in mutter (Ubuntu):
status: Confirmed → Fix Committed
Jeremy Bícha (jbicha)
Changed in mutter (Ubuntu Mantic):
status: New → In Progress
importance: Undecided → Medium
Changed in mutter (Ubuntu):
importance: Undecided → Medium
description: updated
Revision history for this message
Andreas Hasenack (ahasenack) wrote : Please test proposed package

Hello Gonzalo, or anyone else affected,

Accepted mutter into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/45.2-0ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-mantic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in mutter (Ubuntu Mantic):
status: In Progress → Fix Committed
tags: added: verification-needed verification-needed-mantic
Revision history for this message
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (mutter/45.2-0ubuntu1)

All autopkgtests for the newly accepted mutter (45.2-0ubuntu1) for mantic have finished running.
The following regressions have been reported in tests triggered by the package:

mutter/45.2-0ubuntu1 (armhf)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/mantic/update_excuses.html#mutter

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

Revision history for this message
Christopher Vollick (psycotica0) wrote :

I am not the original poster, but I had all of the same symptoms. I manually tried the 45.2-0ubuntu1 version of mutter mentioned above, and the tablet works now!

Tested Krita, Inkscape, Blender (and general system navigation)

Jeremy Bícha (jbicha)
tags: added: verification-done verification-done-mantic
removed: verification-needed verification-needed-mantic
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mutter - 45.2-1ubuntu1

---------------
mutter (45.2-1ubuntu1) noble; urgency=medium

  * Merge with Debian. Remaining changes:
    - Add x11-Add-support-for-fractional-scaling-using-Randr.patch
    - Add window-Add-ability-to-override-the-edge-constraints.patch
      + Make possible for extensions (such as Tiling Assistant) to override
        window constraints

mutter (45.2-1) experimental; urgency=medium

  * New upstream release (LP: #2043000)
  * Drop patches applied in new release
  * Drop unimportant patch not included in the mutter 45.2 backports

 -- Jeremy Bícha <email address hidden> Fri, 08 Dec 2023 15:19:05 -0500

Changed in mutter (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Gonzalo Rodríguez Carrera (zaroca) wrote (last edit ):

Hello again, I'm the original poster, and first things first: thanks to everyone involved.

[OLD - UPDATED BELOW]
I apologize, as I'm not sure how to upgrade my Mutter to version 45.2. I've only been fully immersed in Linux for the past year and have never encountered this kind of issue before. I've already activated non-published updates (mantic-proposed) and nothing happens.

If someone could provide me with guidance or related documentation, I'm willing to perform any tests you may need.

I'm particularly into in this fix because I require it for my work with Krita (I've reinstalled Ubuntu 22.04 these days to be able to work and reupdated to 23.10 just to check this)

[UPDATE]
I'm not very sure how, but I managed to update through aptitude and now it seems to work properly. I can open Krita and everything seems to be ok.

Thank you!

Thanks!

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mutter - 45.2-0ubuntu1

---------------
mutter (45.2-0ubuntu1) mantic; urgency=medium

  [ Jeremy Bícha ]
  * New upstream release (LP: #2043000)
    - Fix entering capital accent letters with Caps Lock (LP: #2035076)
    - Fix Wacom on X11 issues (LP: #2043027)
  * debian/libmutter-13-0.symbols: Add new symbols
  * Drop patches applied in new release
  * Rebase X11 fractional scaling patch

  [ Daniel van Vugt ]
  * Rebase triple buffering patch

 -- Jeremy Bícha <email address hidden> Mon, 04 Dec 2023 13:45:25 -0500

Changed in mutter (Ubuntu Mantic):
status: Fix Committed → Fix Released
Revision history for this message
Andreas Hasenack (ahasenack) wrote : Update Released

The verification of the Stable Release Update for mutter has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Revision history for this message
Kevin Missett (kmissett) wrote :

I encountered this exact problem a few weeks back (Ubuntu 23.10, Wacom Intuos CTH-680) but it was fixed by installing mutter 45.2-0ubuntu1, as indicated. However, this morning, the exact issue reappeared. I tried updating to the latest version of mutter (45.2-0ubuntu2~really45.0) via aptitude, but it has not resolved the problem. My guess is that either the patch was removed with the shift to the new version, or something else updated that has created a new conflict.

I created this UbuntuOne account specifically to file this issue; thus if I am incorrect in adding to this thread rather than creating a new one/filing a new bug, my apologies. Please let me know what further information I should provide, or where else to post the issue. Thank you in advance!

Revision history for this message
Jeremy Bícha (jbicha) wrote :

I am reopening this issue because this update was reverted to avoid a regression. The update will be proposed again in January.

https://launchpad.net/ubuntu/+source/mutter/45.2-0ubuntu2~really45.0

Changed in mutter (Ubuntu Mantic):
status: Fix Released → Triaged
Jeremy Bícha (jbicha)
tags: removed: ubuntu verification-done verification-done-mantic
Changed in mutter (Ubuntu Mantic):
status: Triaged → In Progress
Revision history for this message
Gonzalo Rodríguez Carrera (zaroca) wrote (last edit ):

(Edited)
I'm in the same situation as Kevin Missett. Today problem reappeared and is unusable again.

Any expected fix date? (Just to know what's better for now, wait a little or reinstall a previous version of ubuntu)

Thanks.

Revision history for this message
Steve Langasek (vorlon) wrote : Please test proposed package

Hello Gonzalo, or anyone else affected,

Accepted mutter into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/45.2-0ubuntu3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-mantic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in mutter (Ubuntu Mantic):
status: In Progress → Fix Committed
tags: added: verification-needed verification-needed-mantic
Revision history for this message
Kevin Missett (kmissett) wrote :

First, thank you to Jeremy Bicha and Steve Langasek, and anyone else involved in bringing the update to mutter.

I've been trying for the past few days to install the update. I enabled -proposed, but every time I try to install the newer version of mutter (whether directly by the version name, or by "mantic-proposed", I get this message:

The following packages have unmet dependencies:
 mutter : Depends: mutter-common (>= 45.2-0ubuntu3) but 45.2-0ubuntu2~really45.0 is installed

The set of fixes does not include updating mutter-common; when I check versions in aptitude, it does not list that version. I've tried uninstalling both mutter and mutter-common, but when I go to reinstall, it all defaults back to the 45.2-0ubuntu2~really45.0 versions. While I do see 45.2-0ubuntu3 in the list of versions for mutter, mutter-common only lists the version I have installed.

All that said, I know that the seven-day window will soon pass, and maybe this will just become part of the regular updates; however, if this problem has prevented others from testing, my guess is that it will hold things up until there's been direct verification.

I realize this thread is not for support for this type of problem -- i.e., there may just be some command I'm not familiar with that would resolve this whole thing, and so there may be no larger issue at all other than my own lack of experience -- but I wanted to mention this in case it isn't just me. I would be happy to install and test the new package, but until either mutter-common is also updated, or I can find out what I'm doing wrong, I can't provide any more feedback.

Revision history for this message
Jeremy Bícha (jbicha) wrote :

I agree that there is an issue with making it difficult for people to easily and fully test -proposed updates.

I wrote a blog post about the way I install packages from -proposed. Steps 0-3

https://jeremy.bicha.net/2022/03/29/how-to-install-a-bunch-of-debs/

Revision history for this message
Gonzalo Rodríguez Carrera (zaroca) wrote :

Hi @Jeremy!

I've installed the upgrade following your instructions and it worked!

I have tested it for around 30 mins in Krita now and it seems to be.

Please let me know if you need me to test anything in particular you may need

Thank you and everyone involved in solving this issue!!

Revision history for this message
Jeremy Bícha (jbicha) wrote :

Gonzalo, please leave a comment with the exact version of mutter you tested and which version number of Ubuntu you are using.

Revision history for this message
Gonzalo Rodríguez Carrera (zaroca) wrote :

Hi again!

Following the instructions on your post I've executed "pull-lp-debs mutter 45.2-0ubuntu3" and downloaded:
 - gir1.2-mutter-13_45.2-0ubuntu3_amd64.deb
 - libmutter-13-0_45.2-0ubuntu3_amd64.deb
 - libmutter-13-dev_45.2-0ubuntu3_amd64.deb
 - libmutter-test-13_45.2-0ubuntu3_amd64.deb
 - mutter-13-tests_45.2-0ubuntu3_amd64.deb
 - mutter_45.2-0ubuntu3_amd64.deb
 - mutter-common_45.2-0ubuntu3_all.deb
 - mutter-common-bin_45.2-0ubuntu3_amd64.deb

Installed with "sudo apt install --only-upgrade --mark-auto ./*.deb"

Versions:

mutter --version
 - mutter 45.2

lsb_release -a
 - No LSB modules are available.
 - Distributor ID: Ubuntu
 - Description: Ubuntu 23.10
 - Release: 23.10
 - Codename: mantic

Is it ok?

Revision history for this message
Jeremy Bícha (jbicha) wrote :

Yes, thank you!

tags: added: verification-done verification-done-mantic
removed: verification-needed verification-needed-mantic
Revision history for this message
Kevin Missett (kmissett) wrote :

I was also able to download the upgrade per Jeremy Bicha's instructions, which seems to have resolved the issue for me as well. (Again, mutter=45.2-0ubuntu3, on Ubuntu 23.10.)

Thanks again to all involved! (Also, my thanks, and an apology, to Gonzalo Rodríguez Carrera. I neglected to thank you specifically in my message of a few days ago. I should have included you, especially as it was your reporting of the initial issue that brought me here, and allowed me to implement the fix in the first place.)

Revision history for this message
Gonzalo Rodríguez Carrera (zaroca) wrote :

Don't worry Kevin!!

The real ones to be thanked are Jeremy, Steve and other who were involved in this fix!

Thanks to all the community. I'm a newby in Linux/Ubuntu... and day by day I enjoy it more and more.

Leonhard Küper (mogoh)
information type: Public → Public Security
Revision history for this message
Jeremy Bícha (jbicha) wrote :

Unmarking as a security issue

information type: Public Security → Public
Revision history for this message
Rob Frohne (frohro) wrote :

Thanks Jeremy, this worked for me too!

Jeremy Bícha (jbicha)
Changed in mutter (Ubuntu Mantic):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.