Bug 315 : PortInUseException or "Error inside Serial.<init>()" with serial for 0111+ on Mac OS X
Last modified: 2006-05-12 09:08




Status:
RESOLVED
Resolution:
FIXED -
Priority:
P2
Severity:
normal

 

Reporter:
fry
Assigned To:
fry

Attachment Type Created Size Actions

Description:   Opened: 2006-03-31 09:37
from the board:
http://processing.org/discourse/yabb_beta/YaBB.cgi?board=Collaboration;action=display;num=1137337064

I'm getting the
gnu.io.PortInUseException: Unknown Application
error message too. Have run the setup command, rebooted a number of times -
is there anything else I can try doing.
Am able to get readings with z term (I quit out of that before trying
Processing)

java.lang.RuntimeException: Error inside Serial.<init>()
at processing.serial.Serial.errorMessage(Serial.java:575)
at processing.serial.Serial.<init>(Serial.java:148)
at processing.serial.Serial.<init>(Serial.java:102)
at Temporary_7286_2531.setup(Temporary_7286_2531.java:131)
at processing.core.PApplet.handleDisplay(PApplet.java:1263)
at processing.core.PGraphics.requestDisplay(PGraphics.java:538)
at processing.core.PApplet.run(PApplet.java:1146)
at java.lang.Thread.run(Thread.java:552)

The only difference I've noticed is that 0108 and 0109 always warn:
RXTX Warning: Removing stale lock file. /var/spool/uucp/LK.003.009.004
But 0111 doesn't.
Additional Comment #1 From fry 2006-03-31 09:45
thoughts on things to try:
- see if there's anything that's changed in the rxtx install instructions
or the release notes that covers a different way to handle the device
setup. the macosx_setup.command script may be exacerbating the problem
(i.e. no longer be needed) or may need edits for other rxtx changes.
- see if lock files are being left around and just need to be removed by hand
- check the rxtx source to see what sort of events are kicking off the
exception
- check the diffs between the 2.1_6 and 2.1_7 source to see what might have
changed in this regard
- verify that ppc is also broken (one poster mentioned it was working ok on
some ppc macs)
- figure out whether it's limited to certain kinds of devices, i.e.
bluetooth or serial adapters or what.

i'm surprised that there would be such a glaring problem with the release.
the fixes for the universal build were submitted by someone with a @mac.com
address so it doesn't sound as though they just hit 'recompile' on a
borrowed mactel box and hoped that the new build would work.

i won't be able to work on this one for a while, probably, because it's a
fairly time-consuming thing to fix (balancing its time to fix + priority vs
the time to fix other issues and their priority).
Additional Comment #2 From nick 2006-03-31 23:10
> - verify that ppc is also broken (one poster mentioned it was working ok on
> some ppc macs)

My post was misleading - I had got serial working on previous versions of
Processing with ppc macs so was fairly confident that had followed the faq
and troubleshooting stuff from the website.

Have tested on one ppc and am getting serial working on ppc with previous
versions of processing, PortInUseException with ver111
Additional Comment #3 From fry 2006-04-01 14:21
k, bummer. thanks for the clarification.
Additional Comment #4 From nick 2006-04-05 02:13
from the rxtx mailing list this might help

mailman.qbang.org/pipermail/rxtx/Week-of-Mon-20060306/006521.html
Additional Comment #5 From fry 2006-04-05 05:10
cool, thanks for tracking this down. looks like it was the first item from
the 'things to try' post. i'll fix it up for the next release.
Additional Comment #6 From fry 2006-04-13 18:33
fixed but untested for revision 0112, please verify if it's working and
we'll close the bug.
Additional Comment #7 From nick 2006-04-13 22:29
Working for me on Macbook with bluetooth serial device.

Cheers

Nick
Additional Comment #8 From fry 2006-04-14 03:54
great, thanks for checking in. closing the bug.
Additional Comment #9 From fry 2006-05-12 09:05
for people who come across this bug, the way to resolve this issue is to
re-run macosx_setup.command with the latest release of processing.

i'll also be adding this to the faq.
Additional Comment #10 From fry 2006-05-12 09:06
*** Bug 344 has been marked as a duplicate of this bug. ***
Additional Comment #11 From fry 2006-05-12 09:08
*** Bug 340 has been marked as a duplicate of this bug. ***