Bug 4262 - Serial port crash on ttyUSB0
Summary: Serial port crash on ttyUSB0
Status: NEW
Alias: None
Product: Class Libraries
Classification: Mono
Component: System (show other bugs)
Version: 2.10.x
Hardware: PC Linux
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-04-05 09:58 UTC by velteyn
Modified: 2013-02-23 01:36 UTC (History)
2 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report for Bug 4262 on GitHub or Developer Community if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: GitHub Markdown or Developer Community HTML
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:
Status:
NEW

Description velteyn 2012-04-05 09:58:31 UTC
If you open a /dev/ttyS0 no problem
if you open a /dev/ttyUSB0 mono runtime crashes with a strange error in
System.IO.Ports.SerialportStream.setSignal method   it gives <filename unknown>:0
Comment 1 Timothy 2013-02-23 01:36:23 UTC
We use a modem connected to /dev/ttyUSB0 in a production environment,
previously using Mono 2.10 now using Mono 2.11 without any issues.
So this may be a localized issue very specific to your setup.