You are not logged in.

#1 2012-07-30 10:24:52

using_GNU
Member
Registered: 2012-07-30
Posts: 32

[solved]Problems with wine in x86_64 machine.

Hello, I have problems after I installed wine using "pacman -S wine":

[root@irya sherlock]# pacman -S wine
resolving dependencies...
looking for inter-conflicts...

Targets (1): wine-1.5.9-1

Total Download Size:    27.67 MiB
Total Installed Size:   235.86 MiB

Proceed with installation? [Y/n]
:: Retrieving packages from multilib...
wine-1.5.9-1-x86_64       27.7 MiB   162K/s 02:55 [######################] 100%
(1/1) checking package integrity                   [######################] 100%
(1/1) loading package files                        [######################] 100%
(1/1) checking for file conflicts                  [######################] 100%
(1/1) checking available disk space                [######################] 100%
(1/1) installing wine                              [######################] 100%
Optional dependencies for wine
    giflib
    lib32-giflib
    libpng
    lib32-libpng
    libldap
    lib32-libldap
    gnutls
    lib32-gnutls
    lcms
    lib32-lcms
    libxml2
    lib32-libxml2
    mpg123
    lib32-mpg123
    openal
    lib32-openal
    v4l-utils
    lib32-v4l-utils
    libpulse
    lib32-libpulse
    alsa-plugins
    lib32-alsa-plugins
    alsa-lib
    lib32-alsa-lib
    oss
    cups
    samba
-------------------------------------------------------------------------------------------------

This seems normal, but when i run "winecfg":


$ winecfg
bash: /usr/local/bin/winecfg: No such file or directory

-----------------------------------------------------------------------
My reaction is to look up for the binary winecfg:



[root@irya sherlock]# find / -name winecfg
/usr/bin/winecfg
-----------------------------------------------------------

You can easily see that "winecfg" is located in other place.
Knowing that I did the following:

[sherlock@irya ~]$ /usr/bin/winecfg
/usr/bin/winecfg: line 29: /usr/bin/wine: No such file or directory
-----------------------------------------------------------------------------------------
Well, then I use the find command to know where "wine" binary is located:

[root@irya sherlock]# find / -name wine   
/usr/bin/wine
/usr/lib/wine
/usr/share/wine
/usr/include/wine
/usr/lib32/wine
-------------------------------------------------------------------------------

I see that "wine" is located in usr/bin/wine, and I don't know why this isn't working.
I've tried a lot of things, including compiling wine from source and the wine64 thing in the wine wiki... and nothing seems to work.

Please, would you try to help me?
-----------------------------------------------
Oh, and I almost forget if I execute" winecfg" without priviletges:



[sherlock@irya ~]$ winecfg
bash: /usr/local/bin/winecfg: No such file or directory


But if i run it as super user:



[root@irya sherlock]# winecfg
/usr/bin/winecfg: line 29: /usr/bin/wine: No such file or directory

--------------------------------------------------------------------------------------------------

thank you, a lot.

Last edited by using_GNU (2012-08-03 17:37:44)

Offline

#2 2012-07-30 12:14:15

karol
Archivist
Registered: 2009-05-06
Posts: 25,440

Re: [solved]Problems with wine in x86_64 machine.

Please post the output of 'uname -m' and 'file /usr/bin/wine'.

Why is bash looking for the files in /local/ e.g.  /usr/local/bin/winecfg ?
Edit: Ah, why did you run 'pacman -S wine' as root?


Please edit your title, no need to use CAPS.

Last edited by karol (2012-07-30 12:15:26)

Offline

#3 2012-07-30 13:05:05

using_GNU
Member
Registered: 2012-07-30
Posts: 32

Re: [solved]Problems with wine in x86_64 machine.

Ok, Here it comes

---------------------------
[root@irya sherlock]# uname -m
x86_64
----------------------------------------------
file /usr/bin/wine
/usr/bin/wine: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=0xf9080e796b56f807fdbe8a6673880dc11ead0dbd, stripped

-------------------------------------------------------------------------

And i runed 'pacman -S wine' as root because i need to be administrator to being able to isntall packages on my sistem... if there is something wrong tell me,
I'm quite new in archlinux.


And, you are right, there is no need to use CAPS in the title, i will edit it.  Sorry

Last edited by using_GNU (2012-07-30 13:09:57)

Offline

#4 2012-07-30 13:35:01

karol
Archivist
Registered: 2009-05-06
Posts: 25,440

Re: [solved]Problems with wine in x86_64 machine.

You get "No such file or directory" error when trying to use a 32-bit binary on a 64-bit system or vice-versa.
Try running /usr/bin/wine64 instead.

You should use e.g. 'sudo' https://wiki.archlinux.org/index.php/Sudo to install stuff as a user, not root.

Offline

#5 2012-07-30 14:52:38

using_GNU
Member
Registered: 2012-07-30
Posts: 32

Re: [solved]Problems with wine in x86_64 machine.

Ok, wine64 seems to work, but when i run winecfg:




[sherlock@irya ~]$ winecfg
/usr/bin/winecfg: line 29: /usr/bin/wine: No such file or directory
------------------------------------------------------------------------------------------------

It seems the is looking ofr wine instead of wine64.
How can I fix that?
------------------------------------------------------------------

I used sudo this time.

Offline

#6 2012-07-30 20:46:41

using_GNU
Member
Registered: 2012-07-30
Posts: 32

Re: [solved]Problems with wine in x86_64 machine.

Ok, after that i thinked and if it cannot use the wine64 binary, the i should change the names..

I called wine wine32 and wine64 wine and this is the result:

[sherlock@irya ~]$ winecfg
/usr/bin/wine: not an i386 ELF binary... don't know how to load it
----------------------------------------------------------------------------------------------+

I have to reinstall archlinux because i did the partitions wrong and i have very limited space in rootfs partition, so I will install archlinux with i686 instead of x86_64
and see if it works.

I've tried a lot of things during days: compiling from source, installing from AUR...

And later realized that i have to think how to set the partitions better because I have "rootfs" full and "home" empty... that means reinstall.

Thank you for the suport and for watching this post.

I've find a lot of people with the same problem, I hope this post could help some people if someone knows how to solve the problem.

Offline

#7 2012-07-30 20:52:42

progandy
Member
Registered: 2012-05-17
Posts: 5,321

Re: [solved]Problems with wine in x86_64 machine.

You should try to reinstall lib32-glibc If the 32bit executables are not working.


| alias CUTF='LANG=en_XX.UTF-8@POSIX ' | alias ENGLISH='LANG=C.UTF-8 ' |

Offline

#8 2012-07-30 22:03:29

using_GNU
Member
Registered: 2012-07-30
Posts: 32

Re: [solved]Problems with wine in x86_64 machine.

I tried, doesn't work.

Thank you

Offline

#9 2012-07-31 09:43:42

using_GNU
Member
Registered: 2012-07-30
Posts: 32

Re: [solved]Problems with wine in x86_64 machine.

I tried to install almost every single lib32 package and it still doesn't work.

My computer can't execute the 32-bit binary wine even with the lib32-glibc.

i'm running out of ideas

Offline

#10 2012-07-31 10:33:10

bzt
Member
From: Germany
Registered: 2010-04-11
Posts: 39

Re: [solved]Problems with wine in x86_64 machine.

using_GNU wrote:

This seems normal, but when i run "winecfg":


$ winecfg
bash: /usr/local/bin/winecfg: No such file or directory

This puzzles me somewhat. Prior to pacman -S wine, have you installed wine by compiling and 'make install' command?

Just out of curiousity, what does 'echo $PATH' return for your regular user?

Also have you made sure you don't have any alias commands in .bash_profile which might twist around the wine commands?

EDIT: Also a 'ls -l /usr/bin/wine' would be interesting, too.

Last edited by bzt (2012-07-31 10:40:09)

Offline

#11 2012-07-31 21:01:40

using_GNU
Member
Registered: 2012-07-30
Posts: 32

Re: [solved]Problems with wine in x86_64 machine.

[sherlock@irya ~]$ echo $PATH
/opt/opencascade/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/usr/bin/vendor_perl:/usr/bin/core_perl

---------------------------------------------------------------------------------------------------------------------------------------------------------------------

No i didn't install wine from source previous ot pacman instalation, but i think i will try again, shortly
---------------------------------------------------------------------------------------------------------------------------------


The only thing i have in .bash_profile is this:


[sherlock@irya ~]$ echo $PATH
/opt/opencascade/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/usr/bin/vendor_perl:/usr/bin/core_perl

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------

-rwxr-xr-x 1 root root 9696 Jul 18 11:13 /usr/bin/wine

[sherlock@irya ~]$ ls -l /usr/bin/wine                                   
-rwxr-xr-x 1 root root 9696 Jul 18 11:13 /usr/bin/wine
----------------------------------------------------------------------------------------------

You can see that the executable exist and:

[sherlock@irya ~]$ file /usr/bin/wine
/usr/bin/wine: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=0xf9080e796b56f807fdbe8a6673880dc11ead0dbd, stripped

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------


I think the problem is that i can only run 64-bit executable, "prograndy" told me that if i install lib32-glibc i should be able to execute the 32-bit executable...

but it still doesn't work.

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Ok, and while trying to remove lib32-glibc to install it again later, i've just broke completly my archlinux system.

That means that i learned how dangerous"pacman -Rc" is...   [i'm really clumsy  sad    ]

So i will be out for a little while while i reinstall this thing... again.(no pacman, xterm, and i even removed the kernel)


I think i will install the "i686 arch", i know that x86_64 is better but i'm a student, and sadly my companions don't want to use free software, so i have to use wine to emulate some of the propietary software.




Thank you for your help. i will try x86-64 again and if it works, i will tell you, and if it doesn't, i will try with i686 and tell you too.

Last edited by using_GNU (2012-08-01 12:57:48)

Offline

#12 2012-08-01 08:21:06

sorrat
Member
Registered: 2011-06-18
Posts: 2

Re: [solved]Problems with wine in x86_64 machine.

Hi, have the same problem: after system update bin32 apps won't start. Problem was in version glibc - 2.16.0.1 - system update was not completed.
After upgrading to 2.16.0.2 by guide (part 'Issue 2: The final "pacman -Su" still has conflicts in /lib') apps run.

Last edited by sorrat (2012-08-01 08:23:18)

Offline

#13 2012-08-01 13:52:01

using_GNU
Member
Registered: 2012-07-30
Posts: 32

Re: [solved]Problems with wine in x86_64 machine.

Ok, after i install arch again i will try it.

I need to read the documentation closely because arch has change during this month and the installation method too.

Thank you "sorrat" I didn't know why i was not allowed to execute 32-bit programs.

Well, thank you everyone, I will report the results.

Offline

#14 2012-08-03 17:43:13

using_GNU
Member
Registered: 2012-07-30
Posts: 32

Re: [solved]Problems with wine in x86_64 machine.

Ok, I reinstall archlinux due to my clumsiness.

I realised with the help from you that lib32 packages were not fully upgraded and all i had to do to make it work is to upgrade the system.

well, i learned a lot during this process(manual installation).

wine is solved, now i have to check for other 32-bin to work properly.

thank you, archlinux community, until next time

Offline

Board footer

Powered by FluxBB