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 114235 - Restricts the range of proxy ports
Restricts the range of proxy ports
Status: RESOLVED DUPLICATE of bug 108930
Product: gnome-control-center
Classification: Core
Component: Network
2.2.x
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-06-02 08:48 UTC by Christian Marillat
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.1/2.2



Description Christian Marillat 2003-06-02 08:48:50 UTC
Hi,

http://bugs.debian.org/195644

When editing proxy ports in gnome-network-preferences, the GUI doesn't
allow port numbers higher than 10000. This is silly, since the port
numbers really go up to 65535. My proxy, for example, is at port 60001.

This can be trivially fixed with a s/10000/65535/ in
gnome-network-preferences.glade.
Comment 1 Andrew Sobala 2003-06-02 10:47:34 UTC
Thanks for the bug report. This particular bug has already been
reported into our bug tracking system, but please feel free to report
any further bugs you find.

*** This bug has been marked as a duplicate of 108930 ***
Comment 2 Christian Marillat 2003-06-02 10:56:25 UTC
of course I've checked bugzilla before reporting this bug and why this
bug has been fixed in 2.2.2 ? To hard ?
Comment 3 Christian Marillat 2003-06-02 10:59:15 UTC
Correction, has been not fixed in 2.2.2
Comment 4 Andrew Sobala 2003-06-02 12:00:46 UTC
It hasn't been fixed yet because this is a free software project and
no sufficiently priviledged individual has had time to review the
patch yet.
Comment 5 Christian Marillat 2003-06-02 14:17:50 UTC
Move your mouse over my name to knnow how many time I spend in Free
software. And this take 5 minutes to very this patch.
Comment 6 Andrew Sobala 2003-06-02 14:33:11 UTC
The bug hasn't been fixed because a maintainer needs to find time to
review the patch. There are lots of bugs in bugzilla and it takes time
to get to them all. The patch is less than 2 weeks old; for GNOME,
that's normal.