Bug 136769

Summary:	xcursor-themes missing symlinks (firefox/kwin issues)
Product:	Gentoo Linux	Reporter:	satmd <satmd>
Component:	New packages	Assignee:	Gentoo X packagers <x11>
Status:	RESOLVED NEEDINFO
Severity:	major	Keywords:	Inclusion
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	patched ebuild

Description satmd 2006-06-14 05:54:21 UTC

The x11-themes/xcursor-themes handhelds, redglass and whiteglass are missing some symlinks.

Result: (at least) firefox does not show the waiting cursor and the resize cursors were missing in KDE kwin.

I will attach a patched ebuild.

Comment 1 satmd 2006-06-14 05:57:17 UTC

Created attachment 89145 [details]
patched ebuild

While I don't believe this is the best coding style (incoporated an existing shell script), it works for me.

I wonder if this is something that should be inherited from an eclass.

Comment 2 Donnie Berkholz (RETIRED) gentoo-dev

2006-06-14 08:55:45 UTC

Yeah, that style is really wacky, but it gives the idea of what needs to be done.

Comment 3 Donnie Berkholz (RETIRED) gentoo-dev

2006-07-04 00:00:53 UTC

So I talked to keithp about this. Those hashes are generated using XcursorImageHash(), which is an exported function in libXcursor. We could write a small app that just takes cursor names, calls XcursorImageHash() and spits out the hash. That would be the more correct way to do this.

Comment 4 Rémi Cardona (RETIRED) gentoo-dev

2009-08-17 23:13:07 UTC

Donnie, do you remember what's going on here?

Thanks

Comment 5 satmd 2009-08-18 12:03:43 UTC

This bug was somewhat resolved, but I was waiting for another solution after comment #2 ... and eventually forgot about the bug.

I'm still using this patch.

Comment 6 Da Fox 2009-08-25 13:18:57 UTC

I tried the approach Donnie Berkholz mentioned (using XcursorImageHash()), but I ran in to a problem. XCreateImage() expects an XImage*, not an XcursorImage*, which is what for example XcursorFileLoadAllImages() returns. Manually creating an XImage from the pixeldata of an XcursorImage leads to different hashes. This is likely because there is something more going on, because a single cursor can have many XImages. For example sb_v_double_arrow contains 5 XcursorImages.