This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 132572 - java.io.IOException: Owner timed out
Summary: java.io.IOException: Owner timed out
Status: RESOLVED WORKSFORME
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: David Simonek
URL: http://statistics.netbeans.org/except...
Keywords: RANDOM
Depends on:
Blocks:
 
Reported: 2008-04-10 20:07 UTC by Michel Graciano
Modified: 2009-09-29 01:12 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 3378

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michel Graciano 2008-04-10 20:07:56 UTC 
Build: NetBeans IDE Dev (Build 200709070000)
VM: Java HotSpot(TM) Client VM, 1.6.0_01-b06
OS: Linux, 2.6.18-4-686, i386
User comments: i was opening the ide after updating components. I've also copied the directory complibs in root folder
of nb trunk.
STACKTRACE: (first 10 lines)
java.io.IOException: Owner timed out
        at sun.awt.X11.XSelection.getData(XSelection.java:348)
        at sun.awt.X11.XClipboard.getClipboardData(XClipboard.java:98)
        at sun.awt.datatransfer.ClipboardTransferable.fetchOneFlavor(ClipboardTransferable.java:101)
        at sun.awt.datatransfer.ClipboardTransferable.<init>(ClipboardTransferable.java:80)
        at sun.awt.X11.XClipboard.getContents(XClipboard.java:84)
        at org.netbeans.core.NbClipboard.run(NbClipboard.java:226)
        at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:539)
        at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:964)
Comment 1 David Simonek 2008-04-23 13:51:29 UTC 
Can't reproduce and not enough info to detect where the error may be and how to fix it. Reproducible scenario is needed
in order to chase this bug down. Please reopen with reproducible scenario if it appears again for you, thanks.