Bug 10869 - X difficulties connecting to Sun Solaris
X difficulties connecting to Sun Solaris
Product: Red Hat Linux
Classification: Retired
Component: XFree86 (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Mike A. Harris
Depends On:
  Show dependency treegraph
Reported: 2000-04-17 09:31 EDT by Robert Teeter
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-04-24 12:28:24 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Robert Teeter 2000-04-17 09:31:26 EDT
I'm integrating RedHat Linux with my Sun Solaris boxes.
6.2 has some kind of X weirdness, that doesn't allow
all window operations.

Using Sun Solstice, Disk suite tool I cannot drag & drop
metadevices into the work area.  I get the "not allowed"
pointer when trying to drop them.  This first happened on
a x86 Redhat 6.2 I build specifically as a "head" for
an E-450.  When I tried it on a different  x86 5.2 machine it
worked fine.  I have since upgraded that x86 5.2 to 6.2
and find that I cannot drop the metadevices in the work
area again.

Most X operations seem to work ok.  I can open and
use most applications fine.

(I just retested the the drag and drop on a Sparc Solaris 7
 and it works ok - although sometimes the "not allowed" pointer
 is displayed, it allows the drag and drop as it should.)

-Monta Elkins
Computer Systems Senior Engineer
Virginia Tech
Comment 1 Mike A. Harris 2001-04-24 12:01:24 EDT
I do not have access to that software and as such have no way of reproducing
this at all.  I will be releasing errata shortly however.  Would you be
willing to beta test a potential errata release of XFree86-3.3.6?  It is
entirely possible that it might fix the problem for you.
Comment 2 Mike A. Harris 2001-05-20 18:20:21 EDT
Closing bug due to lack of response...

Note You need to log in before you can comment on or make changes to this bug.