[SOLVED] Installing latest wine from repos and running applications

Head_on_a_Stick · 2017-01-07 11:26:26

That allows you to download different "bottles" (versions) of WINE to use with different programs.

I have to say though that Arch will provide the best WINE experience: they have WINE-staging in [Multilib]

https://www.archlinux.org/packages/mult … e-staging/

linux_user · 2017-01-07 11:40:50

I haven't tried playonlinux. Will give it a shot when I get time.

It was Arch that I first tried to install in my system, but wan't unable to boot from the USB. Most users had the same error (I forgot it), I never found a way around. Then I found BL.

I guess it was good thing that Arch USB wasn't booting. So much to learn in linux, now I am too sure that I would have just reinstalled some simpler distros had it been Arch I first installed. I think BL is a sweet spot. For now, I am sticking onto it.

MAC the Bloody · 2017-01-07 18:20:03

I simply add "deb https://dl.winehq.org/wine-builds/debian/ jessie main" to my sources list minus quotes of course. It has pulled in some updates automagically since installing and that has worked without any issues for me.

For other methods see https://wiki.winehq.org/Wine_User's_Guide#Wine_Installation_Methods

Last edited by MAC the Bloody (2017-01-07 18:20:30)

cloverskull · 2017-01-07 18:57:20

I'm a bit sketchy on using multiple apt sources when it's not completely necessary. I'd advocate, in this case, for using PlayOnLinux. It's the ideal way to manage wine installations.

Head_on_a_Stick · 2017-01-07 19:36:01

Anaconda wrote:

I simply add "deb https://dl.winehq.org/wine-builds/debian/ jessie main" to my sources list minus quotes of course.

This method relies on the repository maintainers not adding stuff that may break a Debian system and is probably not worth the risk, IMO.

We have seen quite a few problems of this sort from the deb-multimedia repositories and that sort of thing can cause major difficulties if a `dist-upgrade` to the next release is attempted.

stevep · 2017-01-07 20:38:56

If you want to try the bleeding edge, you could install wine-staging from their repositories: https://github.com/wine-compholio/wine- … stretchsid

They know what they are doing to keep it compatible, at least in my experience. There are some configuration tweaks needed if you want to run 32-bit Wine apps on a 32-bit Wine on a 64-bit system, just as there are for the standard Wine--i.e., Space Engine on a 32-bit wine-staging on 64-bit, using the Nvidia GPU on an Optimus System with Bumblebee presents some issues that can be overcome, at least on my laptop.

MAC the Bloody · 2017-01-07 21:34:56

Head_on_a_Stick wrote:

Anaconda wrote:
I simply add "deb https://dl.winehq.org/wine-builds/debian/ jessie main" to my sources list minus quotes of course.
This method relies on the repository maintainers not adding stuff that may break a Debian system and is probably not worth the risk, IMO.
We have seen quite a few problems of this sort from the deb-multimedia repositories and that sort of thing can cause major difficulties if a `dist-upgrade` to the next release is attempted.

In response to linux_user's interest in newer versions of wine you mentioned using backports. My reply was basically aimed at that. What I failed to mention was that I had a program that would not run in either the debian stable or backports version of wine. Going to the wine repos directly fixed that for me. For the record wine has both stable and development repos. I used their stable version. Somewhere on the wine site they mention that many distros repos use versions of wine that don't work as well as the current stable version from wine hq and they suggest using this method. It has always worked for me without issue.

I can't say how well this will play with dist-upgrade to the next release of Debian.

Oh and the link I posted earlier to the install methods at wine hq https://wiki.winehq.org/Wine_User's_Gui … on_Methods does not work for me when I click on it here in the forums but is the correct url. For some reason the apostrophe in "User's" drops out in firefox when I click it here. Anyone else seeing that?

Last edited by Head_on_a_Stick (2017-01-07 21:43:39)

Head_on_a_Stick · 2017-01-07 21:44:37

Anaconda wrote:

For some reason the apostrophe in "User's" drops out in firefox when I click it here. Anyone else seeing that?

You used url= along with the actual URL between the tags, I think this "confuses" the system.

I have edited your post — does it work now?

MAC the Bloody · 2017-01-07 21:49:47

Head_on_a_Stick wrote:

Anaconda wrote:
For some reason the apostrophe in "User's" drops out in firefox when I click it here. Anyone else seeing that?
You used url= along with the actual URL between the tags, I think this "confuses" the system.
I have edited your post — does it work now?

Yes that works. Thanks.

Just one more comment about things generally. The warning from HoaS about not adding other repos is generally justified. It's just that in the case of wine specifically I have found the wine repos to be more reliable for getting the programs I use it for to run. That has been my experience.

linux_user · 2017-01-08 14:10:19

Since I wanted the latest stable release, I decided to uninstall wine 1.6.2 and installed wine 1.8.6 from the source tarball. Faced some errors. Created a new thread for that this that was beyond the scope of this thread.

https://forums.bunsenlabs.org/viewtopic.php?id=3195

Last edited by linux_user (2017-01-08 14:36:27)

linux_user · 2017-01-08 14:16:46

Anaconda wrote:

I simply add "deb https://dl.winehq.org/wine-builds/debian/ jessie main" to my sources list minus quotes of course. It has pulled in some updates automagically since installing and that has worked without any issues for me.

Done that, following this method. Still stuck with 1.6.2. Hence decided to try source tarball installation.

Last edited by linux_user (2017-01-08 14:36:10)

MAC the Bloody · 2017-01-08 18:08:51

Looks like my memory is faulty. It's been a while since I did this.
I had installed wine-devel which is now at 2.0~rc3~jessie and working flawlessly for me.

Sorry for the confusion. At some point I was using the stable version but I have upgraded it since then. The devel version has been so rock solid that I simply forgot about it. Not stable but also not staging. I took the middle road.

Edit: I'd say if wine 1.8.6 is working for you, stick with it.

Also HoaS mentioned playonlinux for using multiple versions-bottles of wine. That can be useful if you find that program-x only works in an older version while program-y only works in a newer version.

In the words of Brian Wilson "Oh wouldn't it be nice" if all the software we wanted to run was cross platform compatible?

Last edited by MAC the Bloody (2017-01-08 18:23:16)

linux_user · 2017-01-08 19:28:31

Anaconda wrote:

Looks like my memory is faulty. It's been a while since I did this.
I had installed wine-devel which is now at 2.0~rc3~jessie and working flawlessly for me.

How did you add 2.0~rc3~jessie to the sourcelist? All I have is this: https://packages.debian.org/source/jessie/natbraille

Last edited by linux_user (2017-01-08 19:28:48)

MAC the Bloody · 2017-01-09 00:33:14

linux_user wrote:

Anaconda wrote:
Looks like my memory is faulty. It's been a while since I did this.
I had installed wine-devel which is now at 2.0~rc3~jessie and working flawlessly for me.
How did you add 2.0~rc3~jessie to the sourcelist? All I have is this: https://packages.debian.org/source/jessie/natbraille

Added "deb https://dl.winehq.org/wine-builds/debian/ jessie main" to sources list as mentioned earlier. Then instead of installing wine I installed wine-devel.

I noticed in your other thread that you tried a source install. The source page you linked goes to 1.6.2 and not the 1.8.6 you mentioned.
Earlier you had tried installing from the repos.
If you have not given up on this I would suggest making sure you have got rid of any other installs of wine before trying wine-devel.
(unless of course you got that source install working)

If you get back to where you are starting from a clean slate, installing from the winehq repos is pretty much just apt install wine-devel if you have the above mentioned repo in your sources list and have enabled i386 architecture. Easy to try and easy to undo if it does not work for you.

It worked for me running sketchup and another CAD based program I use. I have no idea if any of this will help you with WoW64

Last edited by MAC the Bloody (2017-01-09 00:46:58)

linux_user · 2017-01-09 05:09:04

Anaconda wrote:

I noticed in your other thread that you tried a source install. The source page you linked goes to 1.6.2 and not the 1.8.6 you mentioned.

Oh sorry, that was a wrong url copied. I am sure what I downloaded was 1.8; even the download archive says that. I have corrected the url in my post.

Anaconda wrote:

Earlier you had tried installing from the repos.
If you have not given up on this I would suggest making sure you have got rid of any other installs of wine before trying wine-devel.
(unless of course you got that source install working)

My intention is to use the stable version. I would like to see how far does the tarball installated wine64 go. If that's showing errors too, I shall probably uninstall everything and start up from zero, pretty much with wine-devel.

linux_user · 2017-01-09 06:37:16

I installed winehq-devel using following this post and the Wine official help page.

It's 2.0.

Anaconda wrote:

Added "deb https://dl.winehq.org/wine-builds/debian/ jessie main" to sources list as mentioned earlier. Then instead of installing wine I installed wine-devel.

Instead of wine-devl, I entered winehq-devel as mentioned in the Wine office help page. Tell me what's the difference.

Also, realized that in Debian, it isn't possible to setup WoW64.

Last edited by linux_user (2017-01-09 06:43:22)

Head_on_a_Stick · 2017-01-09 07:33:15

linux_user wrote:

in Debian, it isn't possible to setup WoW64.

This statement in your link:

Debian's implementation of Multiarch is still incomplete, so for now you can't simply install 32-bit and 64-bit libraries alongside each other.

Is completely wrong — Debian has had full Multiarch support since wheezy, that's how Steam works on my 64-bit system.

linux_user · 2017-01-10 05:31:07

So now I have wine devel and I run an application in terminal. The application opens and I can use it all well. However some output in terminal during the application launch.

err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0)
fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
fixme:ntdll:EtwEventRegister ({5eec90ab-c022-44b2-a5dd-fd716a222a15}, 0x401373, 0xa58c60, 0xa58c78) stub.
fixme:ntdll:EtwEventSetInformation (deadbeef, 2, 0xa293a0, 43) stub
fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
fixme:mountmgr:harddisk_ioctl returning zero-filled buffer for IOCTL_VOLUME_GET_VOLUME_DISK_EXTENTS
fixme:mountmgr:harddisk_ioctl Unsupported ioctl 74080 (device=7 access=1 func=20 method=0)
fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0)
fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d0c10 (device=2d access=0 func=304 method=0)
fixme:nls:GetThreadPreferredUILanguages 00000038, 0x33f558, 0x33f568 0x33f55c
fixme:nls:get_dummy_preferred_ui_language (0x38 0x33f558 0x33f568 0x33f55c) returning a dummy value (current locale)
fixme:module:load_library unsupported flag(s) used (flags: 0x00000060)
fixme:module:load_library unsupported flag(s) used (flags: 0x00000060)
fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
err:toolbar:ToolbarWindowProc unknown msg 0465 wp=00000000 lp=0033ed48
err:toolbar:ToolbarWindowProc unknown msg 0466 wp=00000000 lp=0033ed48
err:toolbar:ToolbarWindowProc unknown msg 0465 wp=00000000 lp=0033ed48
err:toolbar:ToolbarWindowProc unknown msg 0466 wp=00000000 lp=0033ed48
err:toolbar:ToolbarWindowProc unknown msg 0465 wp=00000000 lp=0033ed48
err:toolbar:ToolbarWindowProc unknown msg 0466 wp=00000000 lp=0033ed48
err:toolbar:ToolbarWindowProc unknown msg 0465 wp=00000000 lp=0033ed48
err:toolbar:ToolbarWindowProc unknown msg 0466 wp=00000000 lp=0033ed48
fixme:ieframe:PersistStreamInit_InitNew (0x2bef728)
fixme:iphlpapi:NotifyIpInterfaceChange (family 0, callback 0x6a0cb608, context 0xbe683e8, init_notify 0, handle 0xc69e7a4): stub
fixme:imm:ImmGetDescriptionW (0x4090409, (nil), 0): semi stub
fixme:imm:ImmGetDescriptionW (0x4090409, 0xe7452a0, 9): semi stub
fixme:imm:ImmGetOpenStatus (0x35dbcf0): semi-stub
fixme:imm:ImmReleaseContext (0x10130, 0x35dbcf0): stub
fixme:ntdll:NtLockFile I/O completion on lock not implemented yet
fixme:ieframe:BrowserService_GetTravelLog 0x2c08528 0x33b238
fixme:ieframe:ClientSite_GetContainer (0x2bef7f4)->(0x33b20c)
fixme:mshtml:nsChannel_GetContentDisposition (0x35e2b60)->(0x33aa68)
fixme:mshtml:nsChannel_GetContentDispositionHeader (0x35e2b60)->(0x33a1bc)
fixme:ieframe:ClientSite_GetContainer (0x2bef7f4)->(0x33bfcc)
fixme:win:EnumDisplayDevicesW ((null),0,0x33b654,0x00000000), stub!
fixme:ieframe:PersistStreamInit_InitNew (0x35e7b48)
fixme:ieframe:BrowserService_GetTravelLog 0x35e8488 0x33a3b8
fixme:ieframe:ClientSite_GetContainer (0x35e7c14)->(0x33a38c)
fixme:mshtml:nsChannel_GetContentDisposition (0x35ea228)->(0x339be8)
fixme:mshtml:nsChannel_GetContentDispositionHeader (0x35ea228)->(0x33933c)
fixme:ieframe:ClientSite_GetContainer (0x35e7c14)->(0x33b14c)
fixme:ieframe:PersistStreamInit_InitNew (0x35ece68)
fixme:ieframe:PersistStreamInit_InitNew (0x35eb3f8)
fixme:ieframe:BrowserService_GetTravelLog 0x35f3f00 0x33b1e8
fixme:ieframe:ClientSite_GetContainer (0x35eb4c4)->(0x33b1bc)
fixme:mshtml:nsChannel_GetContentDisposition (0x35f6170)->(0x33aa18)
fixme:mshtml:nsChannel_GetContentDispositionHeader (0x35f6170)->(0x33a16c)
fixme:ieframe:ClientSite_GetContainer (0x35eb4c4)->(0x33bf7c)
fixme:ieframe:PersistStreamInit_InitNew (0x35f7868)
fixme:ieframe:DocHostUIHandler_GetDropTarget (0x2bef7f4)
fixme:ieframe:DocHostUIHandler_GetDropTarget (0x35e7c14)
fixme:ieframe:DocHostUIHandler_GetDropTarget (0x35eb4c4)
fixme:mshtml:OleInPlaceActiveObject_TranslateAccelerator (0x2c099f8)->(0x134c18)
fixme:mshtml:OleInPlaceActiveObject_TranslateAccelerator (0x35e9260)->(0x134c18)
fixme:mshtml:OleInPlaceActiveObject_TranslateAccelerator (0x35f4cd8)->(0x134c18)
fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
fixme:ver:GetCurrentPackageId (0xfdbe9b8 (nil)): stub
fixme:iphlpapi:SendARP (DestIP 0x812aa8c0, SrcIP 0x00000000, pMacAddr 0xfdbabe0, PhyAddrLen 0xfdbabec): stub
fixme:ntdll:EtwRegisterTraceGuidsW (0x69edfc08, 0xee01f48, {509962e0-406b-46f4-99ba-5a009f8d2225}, 3, 0xee020a8, (null), (null), 0xee01f78): stub
fixme:ntdll:EtwRegisterTraceGuidsW   register trace class {a3da04e0-57d7-482a-a1c1-61da5f95bacb}
fixme:ntdll:EtwRegisterTraceGuidsW   register trace class {917b96b1-ecad-4dab-a760-8d49027748ae}
fixme:ntdll:EtwRegisterTraceGuidsW   register trace class {26d1e091-0ae7-4f49-a554-4214445c505c}
fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0)
fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0)
fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0)
fixme:ieframe:PropertyNotifySink_OnChanged unimplemented dispid 1005
fixme:ieframe:PropertyNotifySink_OnChanged unimplemented dispid 1005
fixme:ieframe:PropertyNotifySink_OnChanged unimplemented dispid 1005
fixme:mshtml:OleInPlaceActiveObject_TranslateAccelerator (0x2c099f8)->(0x134c18)
fixme:mshtml:OleInPlaceActiveObject_TranslateAccelerator (0x35e9260)->(0x134c18)
fixme:mshtml:OleInPlaceActiveObject_TranslateAccelerator (0x35f4cd8)->(0x134c18)
err:ole:CoInitializeEx Attempt to change threading model of this apartment from multi-threaded to apartment threaded

Seems, I don't have the winbind package installed. The question is, should I install the amd64 or i386 version?

toor@linux:~$ sudo dpkg -l | grep wine
ii  wine-devel                             2.0~rc3~jessie                       amd64        official WineHQ build of the popular Wine software
ii  wine-devel-amd64                       2.0~rc3~jessie                       amd64        official WineHQ build of the popular Wine software
ii  wine-devel-i386                        2.0~rc3~jessie                       i386         official WineHQ build of the popular Wine software
ii  winehq-devel                           2.0~rc3~jessie                       amd64        official WineHQ build of the popular Wine software
toor@linux:~$

Head_on_a_Stick wrote:

This statement in your link [] is completely wrong — Debian has had full Multiarch support since wheezy, that's how Steam works on my 64-bit system.

Oh! Well, then I guess, I still have to do some work to set up WoW64. By the way, can you tell me whether I already have a WoW64 set up from my dpkg -l | grep wine output?

Last edited by linux_user (2017-01-10 13:43:05)

Head_on_a_Stick · 2017-01-10 07:41:53

linux_user wrote:

Seems, I don't have the windbind package installed.
The question is, should I install the amd64 or i386 version?

I would use:

sudo apt install winbind

Just like with any other package

can you tell me whether I already have a WoW64 set up from my dpkg -l | grep wine output?

I have no idea, I just had to startpage "WoW64"

cloverskull · 2017-01-10 23:50:15

Hey linux_user, have you heard of winetricks?

Also, quick follow up here, but the absolute ideal way to manage custom wine builds with all kinds of special runtime libraries and bits of software is to use PlayOnLinux. I can't recommend this highly enough. Building "one wine to rule them all" is somewhat a fool's errand on linux these days.

Last edited by cloverskull (2017-01-10 23:51:50)

#21 2017-01-07 11:26:26

Re: [SOLVED] Installing latest wine from repos and running applications

#22 2017-01-07 11:40:50

Re: [SOLVED] Installing latest wine from repos and running applications

#23 2017-01-07 18:20:03

Re: [SOLVED] Installing latest wine from repos and running applications

#24 2017-01-07 18:57:20

Re: [SOLVED] Installing latest wine from repos and running applications

#25 2017-01-07 19:36:01

Re: [SOLVED] Installing latest wine from repos and running applications

#26 2017-01-07 20:38:56

Re: [SOLVED] Installing latest wine from repos and running applications

#27 2017-01-07 21:34:56

Re: [SOLVED] Installing latest wine from repos and running applications

#28 2017-01-07 21:44:37

Re: [SOLVED] Installing latest wine from repos and running applications

#29 2017-01-07 21:49:47

Re: [SOLVED] Installing latest wine from repos and running applications

#30 2017-01-08 14:10:19

Re: [SOLVED] Installing latest wine from repos and running applications

#31 2017-01-08 14:16:46

Re: [SOLVED] Installing latest wine from repos and running applications

#32 2017-01-08 18:08:51

Re: [SOLVED] Installing latest wine from repos and running applications

#33 2017-01-08 19:28:31

Re: [SOLVED] Installing latest wine from repos and running applications

#34 2017-01-09 00:33:14

Re: [SOLVED] Installing latest wine from repos and running applications

#35 2017-01-09 05:09:04

Re: [SOLVED] Installing latest wine from repos and running applications

#36 2017-01-09 06:37:16

Re: [SOLVED] Installing latest wine from repos and running applications

#37 2017-01-09 07:33:15

Re: [SOLVED] Installing latest wine from repos and running applications

#38 2017-01-10 05:31:07

Re: [SOLVED] Installing latest wine from repos and running applications

#39 2017-01-10 07:41:53

Re: [SOLVED] Installing latest wine from repos and running applications

#40 2017-01-10 23:50:15

Re: [SOLVED] Installing latest wine from repos and running applications

Board footer