Bug 308971 - YAST network show wireless card twice
Summary: YAST network show wireless card twice
Status: RESOLVED FIXED
Alias: None
Product: openSUSE 10.3
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Beta 3
Hardware: 64bit Linux
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Katarina Machalkova
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-08 11:31 UTC by Fred van Zwieten
Modified: 2008-04-03 16:02 UTC (History)
2 users (show)

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

Attachments
yast duplicate wireless network card (90.10 KB, image/png)
2007-09-08 11:32 UTC, Fred van Zwieten 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Fred van Zwieten 2007-09-08 11:31:28 UTC 
There is a configured and a unconfigured card. There the same card. The unconfirud cannot be removed. So, I remove the configured and configure the unconfigured. This seemes to work, but going to yast network settings again, gives the exact same situation: 2 wireless cards, 1 configured, 1 unconfigured. I'll add a screenshot
Comment 1 Fred van Zwieten 2007-09-08 11:32:31 UTC 
Created attachment 162848 [details]
yast duplicate wireless network card
Comment 2 Fred van Zwieten 2007-09-09 19:49:34 UTC 
OK, I solved this problem by deleting BOTH wireless card defintions from Yast, Finish Yast Network Card, Start YAST Network Card again. It then shows yust one wireless card. Configure it and finish Yast Network Card. Now the duplicate card is gone.

It think it has something to to with the fact that both the ipw3945 _and_ iwl3945 was installed. I've filed bug 308830 for that.
Comment 3 Katarina Machalkova 2007-09-14 08:22:58 UTC 
Please, attach y2logs
Comment 4 Fred van Zwieten 2007-09-20 21:17:35 UTC 
This doesn't happen in a fresh install of RC1, so I close it.
Comment 5 Matej Horvath 2007-10-15 13:41:05 UTC 
Reopening due to Bug 332138.
Comment 6 Matej Horvath 2007-10-15 13:41:24 UTC 
*** Bug 332138 has been marked as a duplicate of this bug. ***
Comment 7 Matej Horvath 2007-10-15 13:42:26 UTC 
The requested logs are included in Bug 332138.
Comment 8 Katarina Machalkova 2008-04-03 16:02:28 UTC 
Bug 332138 is not a dupe of this one. The original issue reported here is obviously fixed