Indeed. From a user point of view, it's hard to know what changes will affect a lot of projects and people, that's the developer task. Firstly, this bug has to gain visibility to Canonical and xserver-xorg, so appropriate developers can take a look at it. Since this bug has 52 people affected, this makes it visible in page two of hot bugs, which means that it has probably been already considered by Canonical.
Since a major change in clipboard was already considered by xserver-xorg developers in the past, it's most likely that it will eventually done. But since it far more than a normal bugfix, I don't see anything else we can do without expertise in xserver-xorg and collaboration with the upstream project. If anyone know a developer that knows very well xserver-xorg that is wiling to put enough time on this and work with the upstream project, then things might accelerate. The bug report itself is complete and does not require any other information.
The popularity of the bug, the amount of work necessary and the consequences of changing the specification is what will affect the correction of this bug for Canonical and xserver-xorg in my opinion.
Indeed. From a user point of view, it's hard to know what changes will affect a lot of projects and people, that's the developer task. Firstly, this bug has to gain visibility to Canonical and xserver-xorg, so appropriate developers can take a look at it. Since this bug has 52 people affected, this makes it visible in page two of hot bugs, which means that it has probably been already considered by Canonical.
Since a major change in clipboard was already considered by xserver-xorg developers in the past, it's most likely that it will eventually done. But since it far more than a normal bugfix, I don't see anything else we can do without expertise in xserver-xorg and collaboration with the upstream project. If anyone know a developer that knows very well xserver-xorg that is wiling to put enough time on this and work with the upstream project, then things might accelerate. The bug report itself is complete and does not require any other information.
The popularity of the bug, the amount of work necessary and the consequences of changing the specification is what will affect the correction of this bug for Canonical and xserver-xorg in my opinion.