Wine Problem!

jbs1136 · 03-17-2010, 09:23 AM

Here is the output:

Code:

bash-3.1$ strace /usr/bin/wine
execve("/usr/bin/wine", ["/usr/bin/wine"], [/* 49 vars */]) = -1 ENOENT (No such file or directory)
dup(2)                                  = 3
fcntl(3, F_GETFL)                       = 0x8002 (flags O_RDWR|O_LARGEFILE)
fstat(3, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 1), ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fa93aca8000
lseek(3, 0, SEEK_CUR)                   = -1 ESPIPE (Illegal seek)
write(3, "strace: exec: No such file or dir"..., 40strace: exec: No such file or directory
) = 40
close(3)                                = 0
munmap(0x7fa93aca8000, 4096)            = 0
exit_group(1)                           = ?

john

nimnull22 · 03-17-2010, 10:35 AM

ENOENT

No such file or directory

This error occurs when a file or directory cannot be found. Note, this can happen when creating a file if one of the parent directories doesn't exist, eg:
touch /etc/doesnotexist/foo

will complain with "No such file or directory" since /etc/doesnotexist does not exist.

This error can be returned by many system calls that work with files.

29 pages link to ENOENT:
link(2) mknod(2) fstatfs(2) creat(2) chown(2) open(2) msgget(2) bind(2) readlink(2) getdents(2) readdir(2) chmod(2) lstat(2) fchown(2) fchdir(2) delete_module(2) acct(2) access(2) chdir(2) chroot(2) lchown(2) mkdir(2) rename(2) fstat(2) execve(2) mount(2) packet(7) rmdir(2) query_module(2)

Looks like, you have to write to Slackware developers.

nimnull22 · 03-17-2010, 10:59 AM

Another suggestion.

Put "wine" to any USER home directory, make it executable for user and then try to execute it like:
/home/directory/wine

jbs1136 · 03-17-2010, 02:53 PM

That didn't work either.

Quote:

bash-3.1# /home/john/wine
bash: /home/john/wine: No such file or directory
bash-3.1#

At this point I think I would be better off starting from scratch. I am going to install wine and the one program I use, Quicken, on another computer that is running 32 Slack. Not my main computer but it will work for this.

Thank you for your patience and your help. It could all be that somewhere in installing multilib I messed up something. But, on the bright side I did learn something new about strace, I have never used it before. Got to get out of the gui more.

john

nimnull22 · 03-17-2010, 03:04 PM

Last question, please.
Change directory to: cd /home/john/ or to /usr/bin and then in console type:
file wine

What will be the output.
Mine is:
wine: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.6.4, dynamically linked (uses shared libs), stripped

jbs1136 · 03-17-2010, 11:53 PM

Code:

bash-3.1$ cd /home/john
bash-3.1$ file wine
wine: cannot open `wine' (No such file or directory)
bash-3.1$ cd /usr/bin
bash-3.1$ file wine
wine: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), stripped
bash-3.1$

Code you requested. Sorry, but this tells me nothing, way over my head.

john

nimnull22 · 03-18-2010, 06:22 AM

You have wine 32-bit, but Slackware 64-bit x86_64. I do not know, but will this type of wine work?

jbs1136 · 03-18-2010, 08:43 AM

It will work but not perfectly. I had it installed and everything worked well but I had problems with a hard drive and had to reinstall Slackware and then I ran into problems when I added wine. It worked after I installed it but after I rebooted the computer it quick working. That is why I decided to just put it on an older 32 bit machine running slackware 13-32. At this point it is more trouble than it is worth. I will just wait until it is improved.

Thanks again for all of your help.

john

t3st · 03-19-2010, 06:39 AM

since it comes with the default installition I must agree that this is an issue that needs to be reported to Slackware.

missionsix · 12-10-2011, 06:49 PM

This is a known bug. You can see other people are having problems too.

http://askubuntu.com/questions/76151...i-installed-it

Launchpad bug: https://bugs.launchpad.net/ubuntu/+s...bs/+bug/852101

Workaround:

reinstall libc6-i386 by running: sudo apt-get install --reinstall libc6-i386

John VV · 12-10-2011, 10:32 PM

missionsix
please do not post a Ubuntu bug to a Slackware post
And one that is almost two years old

the OP was using Slackware and NOT using ubuntu