Bug 521310 - Installing Wine 1.1.28 from fedora-updates-testing cripples DNS resolution
Summary: Installing Wine 1.1.28 from fedora-updates-testing cripples DNS resolution
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: wine
Version: 11
Hardware: x86_64
OS: Linux
low
urgent
Target Milestone: ---
Assignee: Andreas Bierfert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-09-04 17:31 UTC by Bryan Christ
Modified: 2009-09-10 04:30 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-09-10 04:30:50 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Bryan Christ 2009-09-04 17:31:50 UTC
Description of problem:

Installing Wine 1.1.28 from fedora-updates-testing cripples nscd.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.  Updated to wine 1.1.28
2.  Reboot system
3.  Notice that DNS lookups are not working except if you us tools like dig or nslookup manually.
  
Actual results:


Expected results:


Additional info:

I was able to repair the situation by uninstalling wine and then re-enabling the nscd service.

Some related threads on FedoraForums

http://forums.fedoraforum.org/showthread.php?t=227791

http://forums.fedoraforum.org/showthread.php?t=229520

Comment 1 Bryan Christ 2009-09-09 20:54:16 UTC
I see that version 1.1.29 is now available in updates-testing.  Is the problem resolved in this version?

Comment 2 Andreas Bierfert 2009-09-10 04:30:50 UTC
You are probably on a x86_64 system. The problem is caused by a missing nss-mdns(x86-32) if you install the ix86 version of wine on x86-64. There is however no way to make the ix86 version pull in the x86-32 version of nss-mdns on x86-64. Either install nss-mdns(x86-32) manually or install the x86-64 version of the wine meta package which will pull in the 32bit version as well as the nss-mdns stuff.

If you see this problem on x86-32 please reopen the bug.


Note You need to log in before you can comment on or make changes to this bug.