Bug 116092 - network not set up because of pppoe (was: dhcp not running on eth0 after installation)
Summary: network not set up because of pppoe (was: dhcp not running on eth0 after inst...
Status: RESOLVED FIXED
: 194106 (view as bug list)
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Installation (show other bugs)
Version: RC 1
Hardware: All SUSE Other
: P5 - None : Major
Target Milestone: ---
Assignee: Michal Zugec
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 112744
  Show dependency tree / graph
 
Reported: 2005-09-09 11:38 UTC by Martin Vidner
Modified: 2007-01-09 12:37 UTC (History)
2 users (show)

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

Attachments
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 Martin Vidner 2005-09-09 11:38:07 UTC 
(Continuing from bug 112909)   
   
The log shows that a PPPoE device wes detected on the network and so the    
network card was set up without an address. 
The text is confusing so I will change "Congfigured." to "Configured without  
an address.".  
Karl, can you add the translation to network.po at least in yast2-trans-de?  
 
There's nothing about changing the hostname in the logs. But it is true that   
editing a card which has been proposed to have no address does not make it  
possible to leave it without an address. It is a known bug that I have to look  
up.
Comment 1 Karl Eichwalder 2005-09-09 12:16:29 UTC 
Yes, please supply a new .pot file.  And assign the bug to me.
Comment 2 Karl Eichwalder 2005-09-09 12:25:14 UTC 
Inés does not like this text change.  Is it really that confusing?  I also vote
to leave it as-is for 10.0
Comment 3 Martin Vidner 2005-09-09 12:36:06 UTC 
It has been reported as bug 106836 and bug 73692 too.
Comment 4 Ines Pozo 2005-09-09 13:16:47 UTC 
It is not that I don't like it. If I understand it right, changing the text 
will cause the affected strings to become "fuzzy", and thus the text will be 
displayed in English in ALL languages. Since there is no time to fix any 
translations now, I would prefer not to change anything at this stage unless 
really absolutely necessary.
Comment 5 Craig Jeffares 2005-09-09 13:21:26 UTC 
I agree. There is no time for me to get the translations completed for the 
priority languages so please only change it if it is critical otherwise as Ines 
said all the localised products are going to have an untranslated strings 
appear.

Fuzzy strings do appear as english when complied to a .mo
Comment 6 Martin Vidner 2005-09-09 14:28:29 UTC 
Hmm, okay. The string change might not help much anyway because people just 
click Next. A better fix is to change the proposal so that everything is done 
in the DSL module.
Comment 7 Martin Vidner 2006-07-31 13:06:07 UTC 
*** Bug 194106 has been marked as a duplicate of this bug. ***
Comment 8 Martin Vidner 2006-08-28 11:52:26 UTC 
Reassigning to the new maintainer of yast2-network.
Comment 9 Michal Zugec 2006-11-07 11:26:40 UTC 
What is this report about?
What do I have to do?
Comment 10 Martin Vidner 2006-11-07 13:23:50 UTC 
The text change is already there since December 2005, simply search the sources for "Configured without".

The real problem is that while the current automatic proposal works for home users, those who are in a company LAN (like suse.de) might be taken by surprise when there is someone running a pppoe server which makes yast automatically assume a DSL connection.
We could make the DSL setup optional in that case, perhaps using the popular hyperlink method.
Comment 11 Michal Zugec 2007-01-09 12:37:36 UTC 
fixed in yast2-network-2.15.8 and yast2-network-2.13.88
I hope warning in red color is enought