Bug 573868 - dialup networking requires kudzu
Summary: dialup networking requires kudzu
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-network
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Harald Hoyer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F13Beta, F13BetaBlocker
TreeView+ depends on / blocked
 
Reported: 2010-03-15 23:22 UTC by Jim Haynes
Modified: 2010-03-23 02:00 UTC (History)
4 users (show)

Fixed In Version: system-config-network-1.6.0-2.fc12
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-03-23 02:00:47 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jim Haynes 2010-03-15 23:22:44 UTC
Description of problem:  Selecting dialup networking during software 
customization at install time results in Modem connection being among
the kinds of new network connections that can be selected in
system-config-network.  But when you choose that selection it tells
you that kudzu is required.  Kudzu is not included in the installation
CD ROM set, so if you only have dialup networking you can't get the
network up to download it from the repository.


Version-Release number of selected component (if applicable):

system-config-network-1.5.99-1.fc12.noarch  (In Fedora 13 Alpha distribution)

How reproducible: absolutely


Steps to Reproduce:
1. During installation, select dialup networking support during software
   customization
2.After system is up, system->administration->network, click New,
   click Modem connection
3.Read message saying kudzu is required.  (At least this is better than
it wuz - it used to crash the program.)
  
Need to either install kudzu automatically as a result of selecting
dialup networking support, or rewrite the application so it doesn't
need kudzu.





Additional info:

Comment 1 Adam Williamson 2010-03-16 00:38:57 UTC

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 2 Fedora Update System 2010-03-16 12:53:13 UTC
system-config-network-1.6.0-2.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/system-config-network-1.6.0-2.fc12

Comment 3 Fedora Update System 2010-03-16 12:57:13 UTC
system-config-network-1.6.0-2.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/system-config-network-1.6.0-2.fc13

Comment 4 Fedora Update System 2010-03-18 03:30:36 UTC
system-config-network-1.6.0-2.fc12 has been pushed to the Fedora 12 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update system-config-network'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/system-config-network-1.6.0-2.fc12

Comment 5 Jim Haynes 2010-03-19 16:52:15 UTC
Good fix.  On F13 Alpha system I removed old system-config-network and
kudzu and the existing modem connection.  Then installed the new
system-config-netowrk-1.6.0-2.  and was able to create the modem connection.
It said it couldn't find a modem, but that's OK as I know the modem is
ttyS1 and put that in and it worked.

Comment 6 Adam Williamson 2010-03-19 17:43:04 UTC
yeah, that's the trade-off: the Kudzu code did the detection, so without it, you need to know the device node for the modem.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 7 Fedora Update System 2010-03-23 01:58:49 UTC
system-config-network-1.6.0-2.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2010-03-23 02:00:20 UTC
system-config-network-1.6.0-2.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.