You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using my Bamboo in Blender. I can use it for about 30-40 minutes generally, then the stylus buttons start interacting strangely for a minute (as if I'm holding one of the function buttons) before crashing GNOME and dumping me back to a login screen. This was not happening before the upgrade, in Ubuntu 22.04.
This seems similar to this issue, but that issue was fixed and merged into mutter 46.0. Likewise, this seems to be similar behaviour.
Versions:
Ubuntu 24.04 LTS
GNOME 46.0
mutter 46.2
/sys/module/wacom/version v2.00
dmesg after the crash only displays information after the crash, starting again at timestamp 0 so not particularly helpful. Other than that, I'm not sure what logs or troubleshooting steps would help.
The text was updated successfully, but these errors were encountered:
It might be helpful to gather some of the debug info about this crash. I just updated our wiki with some instructions on how to gather information about crashes. Please follow the instructions here https://github.com/linuxwacom/input-wacom/wiki/Getting-Crash-Dumps-on-Ubuntu and reply back with a Stacktrace for review.
Also, are you running GNOME in an X11 or Wayland session?
I'm using my Bamboo in Blender. I can use it for about 30-40 minutes generally, then the stylus buttons start interacting strangely for a minute (as if I'm holding one of the function buttons) before crashing GNOME and dumping me back to a login screen. This was not happening before the upgrade, in Ubuntu 22.04.
This seems similar to this issue, but that issue was fixed and merged into mutter 46.0. Likewise, this seems to be similar behaviour.
Versions:
Ubuntu 24.04 LTS
GNOME 46.0
mutter 46.2
/sys/module/wacom/version v2.00
dmesg
after the crash only displays information after the crash, starting again at timestamp 0 so not particularly helpful. Other than that, I'm not sure what logs or troubleshooting steps would help.The text was updated successfully, but these errors were encountered: