Bug#632030: libxcursor1: Wrong cursor icon in first X session, but not in second.
On Sam, 2011-07-02 at 11:53 +0200, Andreas Neudecker wrote:
>
> > BUT: When hovering over some programs (i.e. iceweasel, thunar, medit
> > etc.) the correct black cursor appears. Other cursor status icons (like that
> > for "being busy", the text cursor mouse icon, etc.) do appear in the design of
> > dmz-black).
>
> I have to modify the description a little:
>
> I have now tested with a different cursor set to rule out the
> possibility that the white cursors appear because the cursor icon gets
> displayed inverted (difficult to say when using DMZ black): I installed
> and selected Chameleon blue.
>
> Before starting Thunar in the first X(FCE) session after booting the
> machine the default mouse pointer is white as described. After starting
> Thunar, the mousepointer is Chameleon outside Thunar, but white when
> hovering over Thunar, over XFCE4 panel, and may other programs, it is
> white again. - Even weirder: with several programs the mouse pointer
> colour changes from white (over the window's head bar) to Chameleon
> (inside the window).
>
> E.g. Icedove (writing this in it): Mouse over the window: Chameleon
> default pointer; mouse over window head bar: white default pointer -
> AND: white resize pointer when over the window's edge or any corner but
> the bottom right corner, but Chameleon resize pointer when mouse over
> the bottom right corner.
If by 'head bar' you mean the title bar, that's most likely actually a
different X11 window which belongs to the window manager. Does
restarting xfwm4 fix the wrong cursor in the window decorations? And
similar for other apps whose windows exhibit the wrong cursors?
> As I read libxcursor is responsible for LOADING cursors I am not sure
> any more that this is a problem in libxcursor. Might it be GTK or even
> the X server who is responsible for picking the wrong cursor icons?
If restarting apps fixes the cursors for them, it's most likely a
problem in GTK or some Xfce library / daemon. The problem might occur or
not depending on the order in which certain processes of the session
start up, which is probably different / more random on the first login
due to the caches being cold.
--
Earthling Michel Dänzer | http://www.amd.com
Libre software enthusiast | Debian, X and DRI developer
Reply to: