Bug 119631 - modem: Request for "No provider"
Summary: modem: Request for "No provider"
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Final
Hardware: Other All
: P5 - None : Enhancement
Target Milestone: ---
Assignee: Michal Zugec
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-30 11:52 UTC by Stanislav Brabec
Modified: 2008-06-25 09:52 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stanislav Brabec 2005-09-30 11:52:38 UTC
I have a modem connected to my computer.

I am using it for sending faxes and for sending SMS via proprietary software and
don't want to configure any provider.

Both these programs expect /dev/modem.

But YaST2 module does not allow to configure only /dev/modem without defining of
any provider.

Having "No provider" radio button in provider selection would be useful for this
particular purpose.
Comment 1 Martin Vidner 2006-08-28 11:52:27 UTC
Reassigning to the new maintainer of yast2-network.
Comment 2 Michal Zugec 2006-08-30 06:47:12 UTC
move to later
Comment 3 Stephan Kulow 2008-06-25 09:33:33 UTC
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 4 Stephan Kulow 2008-06-25 09:35:15 UTC
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 5 Stephan Kulow 2008-06-25 09:41:17 UTC
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 6 Stephan Kulow 2008-06-25 09:52:51 UTC
Closing old LATER+REMIND bugs as WONTFIX - if you still plan to work on it, feel free to reopen and set to ASSIGNED.

In case the report saw repeated reopen comments, it's due to bugzilla timing out on the huge request ;(