Description of problem: Dial-up modem users often find GNOME lacks support for configuring external modems, especially USB ones. kppp is an option but it means users have to install all of the base KDE from the install CD-ROMs, overkill if you only want one utility. An ideal solution would be including gppp, a GNOME equivalent of kppp on the install disks: http://www.linuxsoft.cz/en/sw_detail.php?id_item=725 Ubuntu are using this as a GNOME dialler as well but they have created a "chicken and egg" problem by only including it on their fileshare repositories. Without access to the internet via such a tool, people cannot access the fileshares. Therefore, for GNOME, this will need to be added to the install disks. Steps to Reproduce: 1. Add the gppp modem configuration utility as an option to install from CD-ROMS. Actual results: Users with USB and other dial-up modems, should be able to configure these succcessfully without resorting to the need to install all of KDE to access kppp. Expected results: Additional info:
The GNOME-PPP tool discussed here is another option: http://www.osnews.com/story.php?news_id=7253 As the article states, it does provide a solution for something "sorely missing" from GNOME, even in 2006.
Reassigning to distribution. Network Manager is unrelated to modem dialers
Has anybody packaged this for Extras? Can't include a package that doesn't exist... Its pretty late in the game to add a new package also....
I'm confused. How does system-config-network *not* solve this?
Hello Bill, It does not support external USB modems. I have logged a bug with GNOME about this, too. There is no provision for USB ports in the drop-down list and whilst you can type it in, this will not connect to the modem. It is not an unsupported device at the kernel level as KDE's kppp does find it. It seems to be GNOME-specific, so using a GNOME dialler like the tool mentioned would resolve this.
system-config-network is not a GNOME tool, it's a Fedora tool. So issues with USB modems are probably best handled there. Out of curiousity, if you manually edit the wvdial.conf/ifcfg file after running system-config-network, does it work?
Some prior bugs about s-c-n and USB: Bug 102368 Bug 177472 Bug 109671
"Out of curiousity, if you manually edit the wvdial.conf/ifcfg file after running system-config-network, does it work?" Don't know. I will have a look at it when I go home tonight. Thanks for your interest in this.
Based on the date this bug was created, it appears to have been reported against rawhide during the development of a Fedora release that is no longer maintained. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained. If this bug remains in NEEDINFO thirty (30) days from now, we will automatically close it. If you can reproduce this bug in a maintained Fedora version (7, 8, or rawhide), please change this bug to the respective version and change the status to ASSIGNED. (If you're unable to change the bug's version or status, add a comment to the bug and someone will change it for you.) Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we're following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again.
This bug has been in NEEDINFO for more than 30 days since feedback was first requested. As a result we are closing it. If you can reproduce this bug in the future against a maintained Fedora version please feel free to reopen it against that version. The process we're following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp