Wineconfig doesn't detect Wine

You installed the wine package from the Ubuntu repository?
Could you post the output of
ls -ld /usr/lib/wine

drwxr-xr-x 2 root root 20480 2007-10-18 10:41 /usr/lib/wine

Yes, I only have the official repositories enabled (plus debugging symbols repositories).

I had this problem, I noticed it was being caused by wineconfig on 7.10 64-bit. Its looking for wine in the wrong place -- it looks in /usr/lib/wine instead of its actual location of /usr/lib32/wine. A symlink will fix it.

thank you, however, there was no wine in /usr/lib32 ..

On Thu, 27 Dec 2007 19:02:22 -0500, SalsaDoom <email address hidden> wrote:

> I had this problem, I noticed it was being caused by wineconfig on 7.10
> 64-bit. Its looking for wine in the wrong place -- it looks in
> /usr/lib/wine instead of its actual location of /usr/lib32/wine. A
> symlink will fix it.
>

--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

I've also experienced this bug, and the reason for the bug is that the file wineread.py in guidance-backends has paths hard-coded to look only for /usr/lib/wine and /usr/local/lib/wine, but on amd64 wine installs into /usr/lib32/wine
I've made an easy hackish-patch that fixes this, it can probably be improved by making python find out what the arch of the system is and check lib32 if it's a 64-bit one, but I don't know enough about python to do that.

I've applied the above fix in SVN (upstream), but that won't fix Martin's original problem, I have no idea what's going wrong there.

I applied a nicer fix :-)

I made a symlink, as SalsaDoom says, from /usr/lib32/wine to /urs/lib/wine and everithing works fine now.

Alejandro, the 64-bit bug is confirmed and fix committed. However the original problem is still unsolved and only Martin seems to be experiencing it.
Martin, do you still have this issue?

As I have switched to Arch Linux, I am unable to confirm.

In that case, I'll leave this as the tracker for the 64-bit bug (fix committed). Please reopen and file a new bug if you run into this again with a different configuration.

This bug was fixed in the package kde-guidance - 0.8.0svn20080103-0ubuntu2~ppa3

---------------
kde-guidance (0.8.0svn20080103-0ubuntu2~ppa3) hardy; urgency=low

  * Add kubuntu_10_displayconfig_tryagain.patch so that if displayconfig
    thinks a proprietary driver is installed, but it can't find it, it
    will try to find a non-proprietary driver instead of crashing (LP: #198269)
  * Add kubuntu_11_wineconfg_amd64.patch so that wineconfig looks in the right
    dir for wine on AMD64 (LP: #151982) - Patch should be removed for the next
    svn snapshot or release as a fix has been committed upstream already
  * Add kubuntu_12_powermanager_survive_no_brightness.patch so that if the old
    brightness cannot be gotten from DBUS, powermanager won't crash
    (LP: #183656) and (LP: #198071)
  * Add kubuntu13_displayconfig_add_new_monitors.patch to support additional
    ViewSonic VA702 variants (LP: #192899)

 -- Scott Kitterman <email address hidden> Tue, 04 Mar 2008 11:14:41 -0500

Fix is not actually released yet. Please test the updated kde-guidance-powermanager in my PPA:

https://launchpad.net/~kitterman/+archive

If I get confirmation the fix works, I'll include it in the next upload.

kde-guidance rather.

This bug was fixed in the package kde-guidance - 0.8.0svn20080103-0ubuntu3

---------------
kde-guidance (0.8.0svn20080103-0ubuntu3) hardy; urgency=low

  * Add Add kubuntu_09_mountconfig_no_extensions.patch to remove uneeded call
    to pykdeextensions in mountconfig so that pyqt3 no longer needs to be
    patched to provide -dev files in the regular package (LP: #197867)
  * Add kubuntu_10_displayconfig_tryagain.patch so that if displayconfig
    thinks a proprietary driver is installed, but it can't find it, it
    will try to find a non-proprietary driver instead of crashing (LP: #198269)
  * Add kubuntu_11_wineconfg_amd64.patch so that wineconfig looks in the right
    dir for wine on AMD64 (LP: #151982) - Patch should be removed for the next
    svn snapshot or release as a fix has been committed upstream already
  * Add kubuntu_12_powermanager_survive_no_brightness.patch so that if the old
    brightness cannot be gotten from DBUS, powermanager won't crash
    (LP: #183656) and (LP: #198071)
  * Add kununtu_13_displayconfig_add_new_monitors.patch to update MonitorsDB
    with a upstream snapshot of MonitorsDB from hwdata (LP: #192899)

 -- Scott Kitterman <email address hidden> Sun, 09 Mar 2008 19:53:42 -0400