Bug 87760
Summary: | "sizing" cursor looks like space ship ("trek") | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Jeff Epler <jepler> |
Component: | redhat-artwork | Assignee: | Alexander Larsson <alexl> |
Status: | CLOSED DUPLICATE | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | CC: | garrett, mharris |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-21 18:52:26 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jeff Epler
2003-04-02 03:47:36 UTC
Yeah, it's in the wrong slot. Garrett, can you take a look at this. I don't see a resize cursor in the redhat ones. Possibly related to 85422 The "sizing" cursor certainly seems to come from the bluecurve theme: $ rpm -qf /usr/share/icons/Bluecurve/cursors/sizing redhat-artwork-0.73-1 $ cat /etc/redhat-release Red Hat Linux release 9 (Shrike) Moreover, "wish" clearly opens that file when configured for the sizing cursor (spaceship on my system): $ echo ". configure -cursor sizing" | strace -e open wish 2>&1 | grep Bluecurve/cursors open("/net/filesrv1/sd3a/users/jepler/.icons/Bluecurve/cursors/sizing", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/icons/Bluecurve/cursors/sizing", O_RDONLY) = 4 However, the "sizing" and "trek" cursors aren't actually identical: $ md5sum /usr/share/icons/Bluecurve/cursors/{sizing,trek} 0f76b0285cb1da2794ae3699ab1961e1 /usr/share/icons/Bluecurve/cursors/sizing 836d5e12394370959b18a9c97377d44c /usr/share/icons/Bluecurve/cursors/trek *** This bug has been marked as a duplicate of 85422 *** Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |