Can't select cursor theme in mir demo servers

Bug #1466880 reported by William Hua
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Triaged
Medium
Unassigned
mir (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

The mir demo shell defaults to the 'default' X cursor theme with no way to override it.

Revision history for this message
Cemil Azizoglu (cemil-azizoglu) wrote :

Hi William, can you add some comments as to the importance of this bug that will help me prioritize? Thanks Cemil

Revision history for this message
William Hua (attente) wrote :

Hi Cemil, it's a low-priority wishlist item, the cursor wasn't changing for me. The workaround I used was just to add a symlink from 'default' to whatever cursor theme I wanted to use.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Duplicate of bug 1380463, I think?

tags: added: cursor
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Oh, bug 1380463 is about clients setting their own cursors. This bug however is a simple enhancement request for our demo servers to choose between X cursor themes.

summary: - Can't set cursor theme in mir demo shell
+ Can't change cursor theme in mir demo servers
Changed in mir:
importance: Undecided → Medium
status: New → Triaged
tags: added: enhancement
Revision history for this message
William Hua (attente) wrote : Re: Can't change cursor theme in mir demo servers

Thanks, would we be able to get client API for setting the cursor theme in general? So that it would also work for non-demo servers.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I'm not sure we want to expose that in the client API. That would be setting in stone the information that Mir servers are using X cursor themes, whereas we aspire to something more modern (and more scalable) in future.

summary: - Can't change cursor theme in mir demo servers
+ Can't select cursor theme in mir demo servers
description: updated
Revision history for this message
Alan Griffiths (alan-griffiths) wrote :

Hmm, from the description and comment #2 I assumed that this was a request for code in the example server to enable configuring the cursor theme. A client API implies setting a theme per session (or surface)?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

That's true too. I don't think this is a client API thing. Just a server thing.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

On the other hand, we do eventually want a GUI to change the current default theme used in the server. That probably would have to be some form of client API connected through to the system compositor. :P

Revision history for this message
Alan Griffiths (alan-griffiths) wrote :

/me doubts that a client (of a session compositor) should be talking to the /system/ compositor via Mir APIs.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

It may well be just Unity8 talking to USC but that's still using the client API. Unity8 is a server but it's also a client and it uses the Mir client API to talk to USC, naturally.

So, client API it would be, in theory. In practice I say we still don't want to implement it because right now that would tie our client API design to X cursor themes.

Revision history for this message
Michał Sawicz (saviq) wrote :

Syncing task from Mir.

Changed in mir (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
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.