#3500 closed defect (fixed)
BUG: tightvnc 1.2.9 CleanupXErrorHandler error
| Reported by: | aalorbe@… | Owned by: | boeyms@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.0 |
| Keywords: | Cc: | aalorbe@…, boeyms@… | |
| Port: |
Description
$ Xvnc -version Xvnc version 3.3.tight1.2.9 $ port version Version: 1.001
Mac OS X 10.3.8 1 GHz 17" Powerbook Running CodeTek VirtualDesktop Pro 3.1 with "Enable Focus Follows Mouse"
vncviewer command: vncviewer -xrm '*desktop.translations: #override\n <Key>Pause: ToggleFullScreen()' -encodings 'copyrect hextile' -compresslevel 9 -quality 6 -nocursorshape sahp4960:7
When I leave the X11 program and come back, I'm finding on a regular bases (though not every time) that vnc has exited with the following error:
CleanupXErrorHandler called
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 42 (X_SetInputFocus) Serial number of failed request: 82692 Current serial number in output stream: 82695
Change History (8)
comment:1 Changed 19 years ago by jmpp@…
| Owner: | changed from darwinports-bugs@… to rshaw@… |
|---|
comment:2 Changed 19 years ago by rshaw@…
| Owner: | changed from rshaw@… to darwinports-bugs@… |
|---|
comment:3 Changed 19 years ago by mww@…
| Summary: | tightvnc 1.2.9 CleanupXErrorHandler error → BUG: tightvnc 1.2.9 CleanupXErrorHandler error |
|---|
comment:4 Changed 17 years ago by pipping@…
| Milestone: | → Available Ports |
|---|
comment:5 Changed 17 years ago by pipping@…
| Milestone: | Available Ports → Port Bugs |
|---|
comment:6 Changed 17 years ago by boeyms@…
| Cc: | aalorbe@… boeyms@… added |
|---|---|
| Owner: | changed from macports-tickets@… to boeyms@… |
Add reporter and myself to this ticket, given that I just updated TightVNC (r25231). Is this error still occurring with the new version of TightVNC?
comment:7 Changed 17 years ago by boeyms@…
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
No reply from reporter; assuming that the bug has been fixed. Will reopen this ticket if others report that the problem still occurs.
No longer maintaining these ports.