this is in Fedora 22 using the Gnome environment a random bug which appears to only take place when my initial monitor placement and resolution set up isnt applied prior to bootup and doing so i have to reboot the system to have the mouse work on all areas the biggest example is that my 2nd screen runs at 720p, so when i switch over to my other monitor at 1080p, anything below about halfway down on that screen, the mouse wont interact with, but no amount of disabling or reenabling will fix it until i reboot. i understand that this is sort of how Wayland currently works from what i read in the fedora wiki about it, needing to set up display areas prior to launch, but hopefully can be fixed when you hit "apply" in the monitors settings soon enough. 2nd issue: none of the file navigation using the Files browser that comes with Gnome works with mouse clicks, if i want to navigate into folders or directories i have to use the right click "open" menu, and clicking and draging items around also dont seem to work either, i have to click it, then use the keyboard function to copy and past with Ctrl+C/V ect...
GNOME uses its own implementation of a Wayland server, called Mutter. And, funnily enough, I reported the same bug against Mutter just this morning: https://bugzilla.gnome.org/show_bug.cgi?id=755103
(But the Files issue is something separate, so please report that separately at bugzilla.gnome.org; I will warn you though that they'll almost certainly ask you to try the very latest development version and see if it's fixed there. Fedora 22's GNOME Wayland support was very poor.)
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.