[Bug 15676] New: Network card starts always disabled after 'Breezy' restart within VMWare 4.5.2

bugzilla-daemon at bugzilla.ubuntu.com bugzilla-daemon at bugzilla.ubuntu.com
Sat Sep 17 17:30:17 UTC 2005


Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=15676
Ubuntu | UNKNOWN

           Summary: Network card starts always disabled after 'Breezy'
                    restart within VMWare 4.5.2
           Product: Ubuntu
           Version: unspecified
          Platform: i386
               URL: http://www.hpcmail.ch
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: UNKNOWN
        AssignedTo: debzilla at ubuntu.com
        ReportedBy: schrott at hpcmail.ch
         QAContact: kubuntu-bugs at lists.ubuntu.com


The AMDPCNet network card starts always disabled after 'Breezy' start/restart within VMWare 4.5.2 
(I test 'Breezy' within VMWare to be faster).

Symptoms: 
- The card can be activated if you do: sudo konqueror-->click settings-->Inet&Network-->Network 
settings
- The card always returns to a disabled state after restarting the system (even if in above 
setting dialog, you choose 'Configure interface' and check the 'Activate when the computer 
starts')
- After apt-get update, apt-get upgrade (@September 17, 2005) the Network card (VMWare virtual 
hardware) cannot anymore be activated at all within 'Breezy'
- Complete reinstall of 'Breezy' doesn't solve this problem (means, the problem is reproducable)

-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.




More information about the kubuntu-bugs mailing list