WineHQ
Wine Forums

Board index » WineHQ » Wine Help » Linux




 Page 1 of 1 [ 15 posts ] 



 
Author Message
 Post Posted: Sat Jul 06, 2019 11:05 am 
Offline
Level 2
Level 2

Joined: Mon May 13, 2013 8:35 pm
Posts: 16
I just updated to Wine 4.12, and now whenever I start an application wineboot crashes:
Code:
Unhandled exception: page fault on write access to 0x0040b6e0 in 64-bit code (0x0000000000402545).
Register dump:
 rip:0000000000402545 rsp:000000000032eca0 rbp:0000000000000000 eflags:00010202 (  R- --  I   - - - )
 rax:0000000000000001 rbx:0000000000000000 rcx:0000000000000000 rdx:0000000000000000
 rsi:000000000040b6e0 rdi:0000000000000030  r8:0000000000000041  r9:0000000000000000 r10:00007fa674135cc0
 r11:0000000000000206 r12:0000000000000000 r13:0000000000000030 r14:0000000000000000 r15:000000000040a685
Stack dump:
0x000000000032eca0:  000000000032f450 0000000000402c9d
0x000000000032ecb0:  0000000000000000 0000000000000000
0x000000000032ecc0:  0000000000000000 0000000000000000
0x000000000032ecd0:  0000000000000000 0000000000000001
0x000000000032ece0:  000000000032f450 0000000000000030
0x000000000032ecf0:  0000000000000000 0000000000000000
0x000000000032ed00:  0000000000000000 0000000000000001
0x000000000032ed10:  000000000032f450 0000000000408134
0x000000000032ed20:  0000000000000000 0000000000000000
0x000000000032ed30:  000000000000000c 0000000000000000
0x000000000032ed40:  0000000000000030 0000000000000000
0x000000000032ed50:  0000000000000000 0000000000000000
Backtrace:
=>0 0x0000000000402545 in wineboot (+0x2545) (0x0000000000000000)
0x0000000000402545: movl   %eax,(%rsi)
Modules:
Module   Address               Debug info   Name (22 modules)
PE             400000-          40b000   Export          wineboot
PE           71040000-        7113e000   Deferred        kernelbase
ELF           7b400000-        7b863000   Deferred        kernel32<elf>
  \-PE           7b420000-        7b863000   \               kernel32
ELF           7bc00000-        7bd55000   Deferred        ntdll<elf>
  \-PE           7bc20000-        7bd55000   \               ntdll
ELF           7c000000-        7c004000   Deferred        <wine-loader>
ELF       7fa672839000-    7fa672924000   Deferred        msvcrt<elf>
  \-PE       7fa672860000-    7fa672924000   \               msvcrt
ELF       7fa672a24000-    7fa672abb000   Deferred        advapi32<elf>
  \-PE       7fa672a30000-    7fa672abb000   \               advapi32
ELF       7fa672d99000-    7fa672fab000   Deferred        libnss_files.so.2
ELF       7fa672fab000-    7fa6731c5000   Deferred        libnsl.so.1
ELF       7fa6731c5000-    7fa6733d1000   Deferred        libnss_nis.so.2
ELF       7fa6733d1000-    7fa6735db000   Deferred        libnss_compat.so.2
ELF       7fa6737db000-    7fa6739f3000   Deferred        libgcc_s.so.1
ELF       7fa6739f3000-    7fa673d91000   Deferred        libm.so.6
ELF       7fa673d93000-    7fa673f97000   Deferred        libdl.so.2
ELF       7fa673f97000-    7fa674388000   Deferred        libc.so.6
ELF       7fa674388000-    7fa6745a7000   Deferred        libpthread.so.0
ELF       7fa6745c4000-    7fa674969000   Dwarf           libwine.so.1
ELF       7fa67496b000-    7fa674b95000   Deferred        ld-linux-x86-64.so.2
Threads:
process  tid      prio (all id:s are in hex)
00000008 ntdll.dll
   00000009    0
0000000a (D) C:\windows\system32\wineboot.exe
   0000000b    0 <==
0000000f explorer.exe
   00000014    0
   00000013    0
   00000012    0
   00000011    0
   00000010    0
System information:
    Wine build: wine-4.12
    Platform: x86_64
    Version: Windows 7
    Host system: Linux
    Host version: 4.15.0-54-generic


Additionally, if I start winecfg from the terminal (even with a brand new wineprefix), I get:
Code:
wine: Unhandled page fault on write access to 0x0040b6e0 at address 0x402545 (thread 0014), starting debugger...
0014:err:seh:start_debugger Couldn't start debugger ("winedbg --auto 19 24") (2)
Read the Wine Developers Guide on how to set up winedbg or another debugger
0012:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)
0016:err:ole:marshal_object couldn't get IPSFactory buffer for interface {00000131-0000-0000-c000-000000000046}
0016:err:ole:marshal_object couldn't get IPSFactory buffer for interface {6d5140c1-7436-11ce-8034-00aa006009fa}
0016:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hres=0x80004002
0016:err:ole:CoMarshalInterface Failed to marshal the interface {6d5140c1-7436-11ce-8034-00aa006009fa}, 80004002
0016:err:ole:get_local_server_stream Failed: 80004002
0019:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)


winefile is also not able to see any files and the Drives tab of winecfg has a "failed to connect to the mount manager" error. Looks like something broke badly in the latest version!

I have Linux Mint 19 Cinnamon


Top 
 Post Posted: Sat Jul 06, 2019 11:21 am 
Offline
Level 12
Level 12
User avatar

Joined: Sat Oct 16, 2010 7:40 pm
Posts: 2684
Location: Cambridge
@vdeane

Don't use the Wine or Wine Staging 4.12 package!
See: Bug 47464 - 64-bit WINEPREFIX creation/update fails with Wine 4.12 (wineboot crashes after building as PE file)
This build can potentially corrupt an existing WINEPREFIX.

It seems somewhat bizarre that no checks were done...
Either before releasing the source code, or the packages, for Wine / Wine Staging 4.12 ...
I haven't released builds of these to my Gentoo Overlay. Since I always run rudimentary sanity / build tests.
This problem was not hard to discover (since the release is fundamentally borked).

The offending commit was: 4a8483044ea346e09b4f2769fd1f869a6e4533f6 wineboot: Build with msvcrt.

I'd recommend rolling back to Wine 4.11 - and await a re-release of the Wine 4.12 package.
AJ has stated he will do a re-release / fix-up release, on the wine-devel mailing list.

Bob


Top 
 Post Posted: Sat Jul 06, 2019 11:24 am 
Offline
Level 2
Level 2

Joined: Mon May 13, 2013 8:35 pm
Posts: 16
How do you roll back? My update manager doesn't appear to have an option to roll back a package update.


Top 
 Post Posted: Sat Jul 06, 2019 12:14 pm 
Offline
Level 12
Level 12
User avatar

Joined: Sat Oct 16, 2010 7:40 pm
Posts: 2684
Location: Cambridge
vdeane wrote:
How do you roll back? My update manager doesn't appear to have an option to roll back a package update.


See: Ask Ubuntu: How to downgrade a package via apt-get?

Bob


Top 
 Post Posted: Sat Jul 06, 2019 12:19 pm 
Offline
Level 2
Level 2

Joined: Mon May 13, 2013 8:35 pm
Posts: 16
I eventually figured it out. Had to use aptitude and reject the first proposed solution (which was to just leave everything as-is) before it suggested downgrading the other wine packages beyond the "main" one that actually shows up in update manager.


Top 
 Post Posted: Sat Jul 06, 2019 12:39 pm 
Offline
Level 12
Level 12
User avatar

Joined: Sat Oct 16, 2010 7:40 pm
Posts: 2684
Location: Cambridge
vdeane wrote:
I eventually figured it out. Had to use aptitude and reject the first proposed solution (which was to just leave everything as-is) before it suggested downgrading the other wine packages beyond the "main" one that actually shows up in update manager.


@vdeane

You might want to post a complete explanation... A simple list of instructions and commands, using the forum Code tags:
Code:
...

would probably help out other Ubuntu (Debian) users, in the Wine community. 8)

I expect there will be a flood of identical questions - in the next few days. :|
These folks could then be pointed at this thread, for guidance...

Speaking as a Gentoo user (and part-time packager) - I'm not really "personally invested" in this problem.

Thanks
Bob


Top 
 Post Posted: Sat Jul 06, 2019 12:56 pm 
Offline
Level 2
Level 2

Joined: Mon May 13, 2013 8:35 pm
Posts: 16
Note: all commands ran under sudo except the last.

I was figuring things out for a while, so this first step may not actually be necessary. Nonetheless, I did it, so I'm including it just in case:
Code:
apt-get remove winehq-devel


apt-cache can get the package name needed for that version:
Code:
apt-cache showpkg winehq-devel | grep 4.11


I finished off with aptitude (replace "bionic" with the output from apt-cache if you're on a different Mint/Ubuntu version):
Code:
aptitude install winehq-devel=4.11~bionic


The first proposed solution was to remove a couple packages that had become extraneous with the removal of wine-devel and leave everything else be, since even remove wine-devel still leaves other wine packages at 4.12. I hit n and then it proposed downgrading those other wine packages as well and installing winehq-devel 4.11, which is what we wanted, so I hit Y and it installed.

Finished up with:
Code:
winecfg


which took a while and spit out an error in the terminal but eventually ran OK, in order to restore the wineprefix to working order. Just hit cancel once it popped up.

For good measure (and because I don't feel like manually checking to see if there are updates to other packages), I went into the update manager and told it to ignore updates for wine once it had figured out what I did. At least on Mint, the preferences window has a blacklist tab where I can remove it from that list once this issue is fixed.


Top 
 Post Posted: Sat Jul 06, 2019 4:17 pm 
Offline
Level 12
Level 12
User avatar

Joined: Sat Oct 16, 2010 7:40 pm
Posts: 2684
Location: Cambridge
Thanks. :)

That's actually easier than I though it would be.
Probably because aptitude is much better than apt at resolving dependencies.

I would add that it's probably easier to state:
Code:
apt-mark hold <package-name>

to temporarily block updates on the rolled back winehq-devel (or winehq-staging) package.

To unhold the package, is just the reverse operation:
Code:
apt-mark unhold <package-name>


The command line is distribution agnostic! 8)

Bob


Top 
 Post Posted: Sun Jul 07, 2019 3:51 am 
Offline
Level 6
Level 6

Joined: Thu Aug 14, 2014 10:10 am
Posts: 512
There is no need to uninstall the wine packages.
The following command will downgrade all WineHQ packages:

If needed replace buster with disco, cosmic, bionic or xenial
Code:
sudo apt install winehq-devel=4.11~buster wine-devel=4.11~buster wine-devel-amd64=4.11~buster wine-devel-i386=4.11~buster


Top 
 Post Posted: Sun Jul 07, 2019 10:20 am 
Offline
Moderator
Moderator
User avatar

Joined: Tue Mar 25, 2008 10:30 pm
Posts: 12620
4.12.1 packages are in the repository now.


Top 
 Post Posted: Wed Jul 10, 2019 2:37 am 
Offline
Level 1
Level 1

Joined: Sun Sep 02, 2018 7:33 am
Posts: 5
Manjaro xfce just got update today to 4.12 and It also crash the same way as reported but apparently still continue normally after I close the error window. Is 4.12.1 a fix for that to ? If yes, Manjaro need to be updated I will report to them.


Top 
 Post Posted: Wed Jul 10, 2019 7:18 am 
Offline
Level 12
Level 12
User avatar

Joined: Sat Oct 16, 2010 7:40 pm
Posts: 2684
Location: Cambridge
mariodesc wrote:
Manjaro xfce just got update today to 4.12 and It also crash the same way as reported but apparently still continue normally after I close the error window. Is 4.12.1 a fix for that to ? If yes, Manjaro need to be updated I will report to them.


Wine 4.12 is generally broken, yes. You can't even create or update a 64-bit WINEPREFIX.
It should never have been released/packaged, by the distributions (and certainly wasn't on Gentoo).

I can confirm that 4.12.1 is the replacement (re-release) Wine version.

Bob


Top 
 Post Posted: Sat Jul 13, 2019 5:06 am 
Offline
Newbie
Newbie

Joined: Sat Jul 13, 2019 4:46 am
Posts: 1
Hello,

BattleNet is bugging since I updated wine a few days ago. I can launch the application, but it shows a black screen...

I tried to put a previous version of wine but it wasn't working too. Now I am at version 4.12.1, and it is still not working. I always have a hard time figuring out what is wrong when wine is not working, has someone any idea of how I could debug this ?

Cheers


Top 
 Post Posted: Sat Jul 13, 2019 8:06 am 
Offline
Level 12
Level 12
User avatar

Joined: Sat Oct 16, 2010 7:40 pm
Posts: 2684
Location: Cambridge
john01 wrote:
...
BattleNet is buggy... Since I updated wine a few days ago. I can launch the application, but it only shows a black screen...

I tried to use a previous version of wine, but it wasn't working either. Now I am at version 4.12.1, and it is still not working. I always have a hard time figuring out what is wrong when wine is not working, has someone any idea of how I could debug this ?
...


@john01

According to some users on #winehq (irc)... Downgrading to Wine 4.11 - is a workaround.
Obviously feel free to file a WineHQ bug report (since they haven't bothered to)...

Bob


Top 
 Post Posted: Sun Jul 14, 2019 5:21 am 
Offline
Level 1
Level 1

Joined: Sun Sep 02, 2018 7:33 am
Posts: 5
Bob Wya wrote:
mariodesc wrote:
Manjaro xfce just got update today to 4.12 and It also crash the same way as reported but apparently still continue normally after I close the error window. Is 4.12.1 a fix for that to ? If yes, Manjaro need to be updated I will report to them.


Wine 4.12 is generally broken, yes. You can't even create or update a 64-bit WINEPREFIX.
It should never have been released/packaged, by the distributions (and certainly wasn't on Gentoo).

I can confirm that 4.12.1 is the replacement (re-release) Wine version.

Bob


Ok Manjaro, at least the testing branch, has update to 4.12.1 and it is all good (for me at least). I mention them the broken 4.12 and the availability of the update, they were quick to supply it.
Two steps forward, one step backward but the general direction is still forward. :lol:
Thanks for the help !!


Top 
Display posts from previous:  Sort by  
 
 Page 1 of 1 [ 15 posts ] 




Board index » WineHQ » Wine Help » Linux


Who is online

Users browsing this forum: No registered users and 14 guests

 
 

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to: