After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 148074 - [RFE]Braille port numbering should start from 0
[RFE]Braille port numbering should start from 0
Status: RESOLVED DUPLICATE of bug 167221
Product: gnopernicus
Classification: Deprecated
Component: GUI
unspecified
Other Linux
: High normal
: ---
Assigned To: Alexandra Telescu
Alexandra Telescu
AP1
Depends on:
Blocks:
 
 
Reported: 2004-07-21 12:02 UTC by Alexandra Telescu
Modified: 2005-03-23 08:54 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
proposed patch (3.33 KB, text/plain)
2005-02-21 14:27 UTC, Alexandra Telescu 		Details

Description Alexandra Telescu 2004-07-21 12:02:45 UTC 
In Linux the serial port numbering starts from 0, not from 1.
Comment 1 bill.haneman 2005-02-18 13:43:41 UTC 
should be higher priority since this prevents users from using port 0, doesn't it?
Comment 2 korn 2005-02-18 18:49:22 UTC 
Hmmm... I have but one serial port on my Linux box - ttyS0 - and when I select
port 1 in the Gnopernicus GUI, it works just fine.  It appears to me that this
is just a nomenclature preference issue, not a serious problem.
Comment 3 remus draica 2005-02-21 10:01:31 UTC 
The request is to display 0 instead 1, 1 instead 2, and so on. So, this is not a
real bug, but a RFE.
Comment 4 bill.haneman 2005-02-21 10:35:50 UTC 
But in linux the correct port numbering is '0', showing '1' is actually an
error.  So it's a bug, and an important one!
Comment 5 Alexandra Telescu 2005-02-21 14:27:05 UTC 
Created attachment 37747 [details]
proposed patch

To see the effect of this patch Gnopernicus must be removed from the system and
then reinstalled.
Comment 6 bill.haneman 2005-02-21 17:16:28 UTC 
I'd like to see this patch combined with the fix for bug 167221.
Comment 7 remus draica 2005-03-07 10:31:13 UTC 
Patch for this bug is now part of patch for bug 167221.
Comment 8 remus draica 2005-03-23 08:54:00 UTC 


*** This bug has been marked as a duplicate of 167221 ***