http://bugs.winehq.org/show_bug.cgi?id=29460
Bug #: 29460
Summary: Ruijie Supplicant crash at start
Product: Wine
Version: 1.3.35
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: fracting(a)gmail.com
Classification: Unclassified
Created attachment 38142
--> http://bugs.winehq.org/attachment.cgi?id=38142
Log: Ruijie Supplicant crash
1. Download RGSupplicant4.10_1026.exe
http://115.com/file/cmr79xxh
2. winetricks vcrun6 ( for mfc42)
3. install RGSupplicant4.10_1026.exe with wine
4. Start RuijieSupplicant.exe
$ cd ".wine/drive_c/Program Files/Ruijie Networks/Ruijie Supplicant"
$ wine RuijieSupplicant.exe
Actual result:
Crash
Expect result:
Display the main GUI for RuijieSupplicant.exe
Log:
fixme:ntoskrnl:IoGetCurrentProcess () stub
wine: Unhandled page fault on read access to 0x00000000 at address 0x78010765
(thread 0027), starting debugger...
Backtrace:
=>0 0x78010765 in msvcrt (+0x10765) (0x0053e618)
1 0x005404ab in su1xdriver.sys (+0x4aa) (0x0053e6a8)
2 0x7ec1651a load_driver+0x58a()
[/home/fracting/wine-git/programs/winedevice/device.c:253] in winedevice
(0x0053e938)
3 0x7ec167be ServiceMain+0x11e(argc=0x1, argv=0x110af8)
[/home/fracting/wine-git/programs/winedevice/device.c:307] in winedevice
(0x0053e9a8)
4 0x7ebbd0e8 service_thread+0x161(arg=0x1108c0)
[/home/fracting/wine-git/dlls/advapi32/service.c:291] in advapi32 (0x0053ea28)
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=31101
Bug #: 31101
Summary: ScoobyRom fails to start
(mscoree:ConfigFileHandler_startElement: unknown
elements)
Product: Wine
Version: 1.5.7
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: mscoree
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: fschaefer.oss(a)googlemail.com
Classification: Unclassified
ScoobyRom (https://github.com/SubaruDieselCrew/ScoobyRom) fails to start.
Instead I get the following console output:
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"appSettings" in
state 1
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"add" in state 3
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"add" in state 3
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"add" in state 3
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"add" in state 3
Unhandled Exception: System.TypeLoadException: Could not load type
'ScoobyRom.MainClass' from assembly 'ScoobyRom, Version=0.6.2.32780,
Culture=neutral, PublicKeyToken=null'.
[ERROR] FATAL UNHANDLED EXCEPTION: System.TypeLoadException: Could not load
type 'ScoobyRom.MainClass' from assembly 'ScoobyRom, Version=0.6.2.32780,
Culture=neutral, PublicKeyToken=null'.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=42420
Bug ID: 42420
Summary: MidiIllustrator Virtuoso 3 crashes when using any File
open dialog
Product: Wine-staging
Version: 2.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: shawn.starr(a)rogers.com
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Created attachment 57240
--> https://bugs.winehq.org/attachment.cgi?id=57240
Crash backtrace
When running MidiIllustrator Virtuoso 3, it starts it works fine except for
when opening a File dialog crashes.
Attached is backtrace.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=40256
Bug ID: 40256
Summary: user32:input fails on non-qwerty keyboards
Product: Wine
Version: 1.9.3
Hardware: x86
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Since the commit below, user32:input has the following failures on azerty
keyboards:
input.c:1688: Test failed: 12: got 1 expected 0
input.c:1690: Test failed: 12: got L"\001d" expected L""
input.c:1688: Test failed: 17: got 1 expected 0
input.c:1690: Test failed: 17: got L"\001c" expected L""
input.c:1688: Test failed: 25: got 1 expected 0
input.c:1690: Test failed: 25: got L"\001c" expected L""
input.c:1688: Test failed: 30: got 0 expected 1
input.c:1688: Test failed: 31: got 0 expected 1
input.c:1688: Test failed: 32: got 0 expected 1
input.c:1690: Test failed: 33: got L"\001b" expected L"\001e"
input.c:1688: Test failed: 34: got 0 expected 1
Unfortunately we don't have TestBot VMs with non-qwerty keyboards so far but
this can be seen on the fg-eeepc-xp and fg-acer64-* Windows test results.
winspool's dr-w8-E1-1200-x64 has slightly different test failures which is most
likely because it has a qwertz keyboard (based on the German locale):
https://test.winehq.org/data/0806b06f2ba7a690661d6ae417270bdbc7370953/win8_…
input.c:1688: Test failed: 10: got 1 expected 0
input.c:1688: Test failed: 11: got 1 expected 0
input.c:1690: Test failed: 11: got L"\001c" expected L""
input.c:1688: Test failed: 18: got 1 expected 0
input.c:1690: Test failed: 18: got L"\001d" expected L""
input.c:1690: Test failed: 29: got L"\0011" expected L""
input.c:1688: Test failed: 30: got 0 expected 1
input.c:1688: Test failed: 31: got 0 expected 1
input.c:1688: Test failed: 32: got 0 expected 1
input.c:1688: Test failed: 33: got 0 expected 1
And gang65 at poczta.onet.pl's win7sp1 machine has yet another set of failures,
probably due to the presence of a Polish keyboard:
https://test.winehq.org/data/b190a72bfe53a41a83ae55d75de8327c24512bee/win7_…
input.c:1688: Test failed: 10: got 1 expected 0
input.c:1688: Test failed: 28: got 1 expected 0
input.c:1690: Test failed: 28: got L"\001f" expected L""
input.c:1690: Test failed: 29: got L"\0016" expected L""
input.c:1690: Test failed: 31: got L"\0011" expected L"\001c"
input.c:1688: Test failed: 33: got 0 expected 1
input.c:1688: Test failed: 34: got 0 expected 1
mshtml:script results on test.winehq.org:
https://test.winehq.org/data/tests/user32:input.html
commit 10556c25e468768d1422e872f16dbc1ae85ef968
Author: Huw Davies <huw(a)codeweavers.com>
Date: Thu May 28 11:35:05 2015 +0100
winex11: Fix ctrl-<symbol> to generate codes below 0x20 where necessary.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30231
Bug #: 30231
Summary: Adode Reader X 10.2.1 fails to install
Product: Wine
Version: 1.5.0
Platform: Other
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: robert.munteanu(a)gmail.com
Classification: Unclassified
The installation starts up but does not finish.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=33471
Bug #: 33471
Summary: Adobe Reader 11 do not install on Linux Mint 14
Product: Wine
Version: 1.4.1
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: mybugs.mail(a)gmail.com
Classification: Unclassified
Created attachment 44306
--> http://bugs.winehq.org/attachment.cgi?id=44306
Terminal output for wine-1.4.1
I just downloaded AdbeRdr11002_en_US.exe from
http://get.adobe.com/br/reader/otherversions/
and when I tried to install the program on wine-1.4.1 (using Linux Mint 14
Nadia) with the command
$ wine AdbeRdr11002_en_US.exe &> log.txt
(and clicking "Next" in the GUI and then "Install"
I got a screen with the message
"Setup was interrupted before Adobe Reader XI (11.0.02) could be completely
installed"
and the software was not installed.
See the terminal output in the attachment.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=32857
Bug #: 32857
Summary: Can't install Adobe Reader
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: tael67(a)gmail.com
Classification: Unclassified
Created attachment 43393
--> http://bugs.winehq.org/attachment.cgi?id=43393
Log
The Adobe Reader installer does not work with Wine :
"Setup was interrupted before Adobe Reader XI could be completely installed."
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=34108
Bug #: 34108
Summary: Rally Trophy: Controller configuration is very buggy
Product: Wine
Version: 1.6
Platform: x86-64
URL: http://games.softpedia.com/get/Games-Demo/Rally-Trophy
.shtml
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-dinput
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jettis(a)gmail.com
Classification: Unclassified
Created attachment 45353
--> http://bugs.winehq.org/attachment.cgi?id=45353
Rally Trophy log trace+dinput
Rally Trophy uses DirectInput's device configuration window. There are some
bugs that make device configuration difficult and for example a racing wheel
impossible to use.
Device configuration usually doesn't show the currently mapped keys for
keyboard especially when a racing wheel is connected. If it shows they are only
default keys and not the currently mapped keys.
If a function is already mapped to a key by you, you can't change it to an
another key anymore. For example you set 'shift up' to 's' key and go to play,
then you go back to device configuration and set 'shift up' to 'd' key and
again go to play. You will notice that 'd' key does not change a gear.
In full version of Rally Trophy the key mappings are saved, but in Rally Trophy
Demo in wine they are not. The keys are always the default ones when you start
the game.
In Windows you can select a player (Pelaaja 1/Player 1) for the device when you
want to use it. Wine does not see the player and shows only a blank list, so
you can't get a racing wheel in to use.
However a racing wheel becomes usable if keyboard and mouse enumeration is
deleted from IDirectInput8AImpl_EnumDevicesBySemantics from wine's code.
Logs are made with these steps:
1. Start the game
2. Go to device configuration
3. Set key 's' to 'shift up'
4. Go to in game
5. Close the game with alt+f4
A racing wheel is connected when logging.
Tested wine version is the latest git.
Demo can be downloaded from:
http://games.softpedia.com/get/Games-Demo/Rally-Trophy.shtml
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.