230224 – if "deactivate ipv6" is chosen during install, KDE_USE_IPV6 is not set to "no"

Bug 230224 - if "deactivate ipv6" is chosen during install, KDE_USE_IPV6 is not set to "no"

Summary: if "deactivate ipv6" is chosen during install, KDE_USE_IPV6 is not set to "no"

Status:	RESOLVED DUPLICATE of bug 150207

Alias:	None

Product:	openSUSE 10.2
Classification:	openSUSE
Component:	KDE (show other bugs)
Version:	Final
Hardware:	Other Other

Priority:	P5 - None Severity: Normal (vote)
Target Milestone:	---
Assignee:	E-mail List
QA Contact:	E-mail List

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Clone This Bug

Reported:	2006-12-21 13:23 UTC by Forgotten User --EoyBps8f
Modified:	2007-01-22 14:59 UTC (History)
CC List:	2 users (show)

See Also:
Found By:	Other
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 Forgotten User --EoyBps8f 2006-12-21 13:23:48 UTC

I disabled the use of IPv6 during installation. However, KDE_USE_IPV6 was still set to "yes" according to the sysconfig-editor.

If the user chooses to disable IPv6, this variable should be set to "no".

Comment 1 Matej Horvath 2006-12-22 13:54:04 UTC

Please post your yast logs and /var/log/messages.

Comment 2 Forgotten User --EoyBps8f 2006-12-23 00:15:09 UTC

It's quite easy to reproduce, if you need the logs: install openSuSE 10.2, you could even use XEN or Vmware, and deactivate IPv6 via the provided "link" (clickable text) when configuring the network. After installation has finished, check the variable mentioned above.

Or did you try and could not reproduce it?

Comment 4 Marcel Hilzinger 2007-01-05 13:09:08 UTC

No need to reproduce. Can confirm this bug.  Developers just forgot about this KDE-Setting. Please assign

Comment 6 Michal Zugec 2007-01-22 14:59:14 UTC

it's in /etc/sysconfig/windowmanager.KDE_USE_IPV6
But this is already handled (therefor fixed) by YaST (in version yast2-network-2.15.9)

*** This bug has been marked as a duplicate of bug 150207 ***