[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[pkg-wine-party] Bug#481826: marked as done (unable to start (wine: could not exec wine-pthread))



Your message dated Mon, 19 May 2008 10:56:57 +0200
with message-id <483140D9.9030300@arcticnet.no>
and subject line Re: [pkg-wine-party] Bug#481826: Bug#481826: unable to start (wine: could not exec wine-pthread)
has caused the Debian Bug report #481826,
regarding unable to start (wine: could not exec wine-pthread)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
481826: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=481826
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- Package: wine
Version: 1.0-rc1-1
Severity: grave
Justification: renders package unusable

When I launch wine from console I get a message:
> wine: could not exec wine-pthread
It's something wrong with /usr/lib/wine/wine-pthread. Direct launching
with "--version" causes following error:
> /usr/lib/wine/wine-pthread: relocation error: /usr/lib/wine/wine-pthread: symbol wine_get_build_id, version WINE_1.0 not defined in file libwine.so.1 with link time reference
And direct launching with some executable (like winecfg) as argument
causes:
> wine: could not exec wineserver
But wineserver works right (I think).

Note that I've already compiled some wine versions (like 0.9.57) and they
work right. I use unstable's wine as of 0.9.58-59 version, and initially
it was not unusable.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.24-1-amd64 (SMP w/1 CPU core)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages wine depends on:
ii libwine-alsa 1.0-rc1-1 Windows API implementation - ALSA 
ii libwine-cms 1.0-rc1-1 Windows API implementation - color
ii libwine-gl 1.0-rc1-1 Windows API implementation - OpenG
ii libwine-gphoto2 1.0-rc1-1 Windows API implementation - camer
ii libwine-ldap 1.0-rc1-1 Windows API implementation - LDAP 
ii libwine-print 1.0-rc1-1 Windows API implementation - print
ii libwine-sane 1.0-rc1-1 Windows API implementation - scann
ii wine-bin 1.0-rc1-1 Windows API implementation - binar
ii wine-utils 1.0-rc1-1 Windows API implementation - utili

wine recommends no packages.

Versions of packages libwine depends on:
ii ia32-libs 2.5 ia32 shared libraries for use on a
ii libc6-i386 2.7-11 GNU C Library: 32bit shared librar

-- no debconf information



--- End Message ---
--- Begin Message ---
Gustaw Smolarczyk skrev:
2008/5/19, Ove Kaaven <ovek@arcticnet.no <mailto:ovek@arcticnet.no>>:
    Then you should uninstall them to make sure they're not conflicting
    with the packages. You could use ldd /usr/lib/wine/wine-pthread to
    see the path of the libwine.so it's loading. Make sure it's the one
    comes from the libwine package, and not whatever you compiled.

It was problem with wine in /usr/local (sid's wine links with /usr/local/lib/libwine.so.1), sorry for that, but earlier there was no problem with sid's wine with that.

I think that symbol was introduced in 0.9.59, so perhaps your earlier packaged version was older than that or something? Anyway, be careful about mixing different Wine versions like that. Closing.


--- End Message ---

Reply to: