After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 753587 - GNOME crashes when unchecking "Map to single monitor" in Wacom tablet settings
GNOME crashes when unchecking "Map to single monitor" in Wacom tablet settings
Status: RESOLVED DUPLICATE of bug 749844
Product: gnome-control-center
Classification: Core
Component: Wacom
3.16.x
Other Linux
: Normal critical
: ---
Assigned To: Carlos Garnacho
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-08-13 14:38 UTC by Jehan
Modified: 2015-08-20 10:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jehan 2015-08-13 14:38:54 UTC 
With several screens.

Reproduction steps:
- Go in the Wacom tablet settings.
- Click "Map to Monitor".
- "Map to single monitor" is checked by default. Uncheck it.
- GNOME crashes with the big generic screen "Oh no something has gone wrong." (which is kind in between both screens) with only proposed choice is to log out.
- On logging back in, you get immediately the same screen again forcing you to log back out.

The only workaround I found to log back in is to unplug the tablet, then log in. Then when you replug the tablet, fortunately the crash does not happen again.

Tested on 2 different machines, both with Fedora 22 and GNOME-shell 3.16.3-1.fc22, one with an Intuos 5, and one with Wacom Bamboo. Crash both times the same way.
Comment 1 Jehan 2015-08-16 12:22:16 UTC 
While testing on another dual-screen computer, also with Fedora 22, this time with a Wacom Bamboo, the same crash occured. Looks like a very reproducible crash!
Comment 2 Carlos Garnacho 2015-08-20 10:40:19 UTC 
Thanks for the bug report! AFAICS I get the same backtrace than bug #749844 on stock f22, and effectively running master/gnome-3-16 doesn't trigger any crash. So this should be fixed on gnome-settings-daemon 3.16.3, although it apparently didn't make its way to Fedora repos, I'll look into fixing that.

*** This bug has been marked as a duplicate of bug 749844 ***