I'm using LM 13 MATE.
3 Windows open when I launch an app or game with Wine 1.4. [images attached].
It does not seem to affect the app/game but they are a nuisance.
Any fix for this

winecfgwine: Unhandled page fault on read access to 0xffffffff at address 0x54b89f (thread 0027), starting debugger...
wine: Unhandled page fault on read access to 0xffffffff at address 0x55521a (thread 002f), starting debugger...
wine: Unhandled page fault on write access to 0x00549000 at address 0x7bc4b907 (thread 003d), starting debugger...
fixme:ntoskrnl:KeInitializeEvent stub: 0x540748 1 0
fixme:ntoskrnl:PsSetCreateThreadNotifyRoutine stub: 0x5405c0
fixme:ntoskrnl:IoCreateSynchronizationEvent (0x53e6f0 0x53e6fc) stub
fixme:ntoskrnl:IoAllocateErrorLogEntry stub: 0x6838c4a0, 48
WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-8B6HYV/pkcs11: No such file or directory
feadanaigh wrote:I had a couple of problems with 1.4 as well, but 1.5 is there, maybe you want to give it a try?
via ppa:
sudo add-apt-repository ppa:ubuntu-wine/ppa
sudo apt-get update
sudo apt-get install wine1.5




Garvan wrote:Never seen this before.
Does this happen with every windows program, or just some? What happens when you run the supplied version of Notepad?
If you are set up to log in automatically, try changing it to log in with user-name and password. I am curious why you get this message
WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-8B6HYV/pkcs11: No such file or directory
Garvan



Garvan wrote:It does not happen here on Mint 13 Cinnamon either, so now I think it must be a MATE bug.
Garvan



Garvan wrote:Not sure .. I just checked my version of wine, it is wine 1.4-i386. Is this what you are using?
Gar.



Garvan wrote:If you have 64-bit installed, check this post
viewtopic.php?f=47&t=103612&p=594389
Garvan.

+-WineDbg
| |
| +->BreakOnFirstChance
| | [DWORD value. Set this to "0" to let applications handle exceptions themselves.
| | winedbg then only catches exceptions that are not handled by the app,
| | which makes debugging a bit easier.
| | Default value is "1" (enabled)]
| |
| +->ShowCrashDialog
| [DWORD value. Set this to "0" to disable the GUI crash dialog.
| Default value is "1" (enabled)]
|




RytronII wrote:No! The 3 error windows problem is back!![]()
![]()
That must have been a temp fix.


Garvan wrote:RytronII wrote:No! The 3 error windows problem is back!![]()
![]()
That must have been a temp fix.
Did you try creating the key ShowCrashDialog and sets its value to 0, as per the documentation I copied above?



Garvan wrote:Hexadecimal 0 = Decimal 0 so they are both correct. Unfortunately I have run out of ideas for now, as nobody else is reporting this error. If I find anything I will post back.
Garvan


Users browsing this forum: librin.so.1 and 5 guests