2 mouse pointers when running gedit with gtk mir on Unity8

[dinamic]

ubuntu 16.04
i get 2 mouse pointers when running gedit with gtk mir on Unity8. they also have diff sizes and positions. even after closing gedit i'm left with 2 mouse pointers. i don't need 2, one is enough. it gets really confusing using 2 mouse pointers at the same time, uh

[Michael Zanetti (mzanetti)]

Adding Libertine as I think we want to keep unity8's cursor and hide compiz' one.

Please reopen for unity8 if I'm wrong.

[dinamic (dinamic6661)]

i have a simple .desktop file that runs gedit

[Christopher Townsend (townsend)]

I don't think this has anything to do with Libertine as the bug reporter is indicating they are running Gedit w/ the Mir Gtk backend, ie, without the Libertine container.

Reopening for Unity8 and marking the Libertine task Invalid.

Thanks!

[Christopher Townsend (townsend)]

I just confirmed this behavior.

I added 'X-Ubuntu-Touch=true' to /usr/share/applications/gedit.desktop, refreshed the App Scope, launched Gedit, and as soon as the cursor hits the Gedit window, another cursor is shown.

[Christopher Townsend (townsend)]

As an aside, I do see this with Xapps running in a Libertine container, but as mentioned in the last comment, it's not Libertine causing this.

[Daniel d'Andrada (dandrader)]

Run gedit in a "unity8 mir" session on my laptop and still see only one cursor. What Ubuntu version are you using and what are the mir, unity8 and qtmir versions you have?

[Christopher Townsend (townsend)]

For me, I'm running 16.04 Xenial.

mir: 0.17.0+15.10.20151008.2-0ubuntu1
unity8: 8.11+16.04.20151104-0ubuntu1
qtmir-desktop: 0.4.6+16.04.20151102-0ubuntu1

[dinamic (dinamic6661)]

same here 16.04
mir: 0.17.0+15.10.20151008.2-0ubuntu1
unity8: 8.11+16.04.20151104-0ubuntu1
qtmir-desktop: 0.4.6+16.04.20151102-0ubuntu1

[Christopher Townsend (townsend)]

After some investigation, this is due to lightdm hard coding an option passed to unity-system-compositor to enable the hardware cursor. Since Unity 8 now provides its own cursor, this option is no longer needed.

I opened a new bug against lightm to specifically disable the "--enable-hardware-cursor=true" option. I think it's best to dup this bug to that bug (bug #1517615).