|
Bugzilla – Full Text Bug Listing |
| Summary: | network not set up because of pppoe (was: dhcp not running on eth0 after installation) | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Martin Vidner <mvidner> |
| Component: | Installation | Assignee: | Michal Zugec <mzugec> |
| Status: | RESOLVED FIXED | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | frank, ke |
| Version: | RC 1 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | SUSE Other | ||
| Whiteboard: | |||
| Found By: | Beta-Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Bug Depends on: | |||
| Bug Blocks: | 112744 | ||
|
Description
Martin Vidner
2005-09-09 11:38:07 UTC
Yes, please supply a new .pot file. And assign the bug to me. Inés does not like this text change. Is it really that confusing? I also vote to leave it as-is for 10.0 It has been reported as bug 106836 and bug 73692 too. 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. 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 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. *** Bug 194106 has been marked as a duplicate of this bug. *** Reassigning to the new maintainer of yast2-network. What is this report about? What do I have to do? 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. fixed in yast2-network-2.15.8 and yast2-network-2.13.88 I hope warning in red color is enought |