https://bugs.winehq.org/show_bug.cgi?id=40660
Bug ID: 40660
Summary: latest update Sega Genesis & Mega Drive update no
longer running after May 18, 2016 update
Product: Wine
Version: 1.9.10
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: te_lanus(a)yahoo.co.uk
Distribution: ---
The latest update of the game from Steam no longer run. They fixed a bunch of
controller problems, and that causes problems running under wine.
Wine prints this text then exit:
Call from 0x7b43fb52 to unimplemented function
bthprops.cpl.BluetoothFindFirstDevice, aborting
Steam linky:
http://steamcommunity.com/games/34270/announcements/detail/9573913140181864…
My system:
Linux Mint 17.3 Cinnamon 2.8.8
Using the latest from the http://ppa.launchpad.net/wine/wine-builds/ubuntu PPA
done with a clean .wine
--
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=31971
Bug #: 31971
Summary: windows 8 cp mspaint.exe didnt run.
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: shell32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: me(a)mailinator.com
Classification: Unclassified
Created attachment 42126
--> http://bugs.winehq.org/attachment.cgi?id=42126
the log file describing what happened
I tried to run mspaint from windows 8 consumer preview and it crashed before it
even came up.
--
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=34557
Bug #: 34557
Summary: Lemmings Revolution: can't rotate playing field
Product: Wine
Version: 1.7.2
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-dinput
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: mondane.woodworker(a)gmail.com
Classification: Unclassified
As of 1.7.x, the mouse moves normal now, but rotating the playing field isn't
possible. Before only rotating to the left was broken (
http://bugs.winehq.org/show_bug.cgi?id=20582 ).
How to rotate:
- Start the game and choose a level
- When the timer is started, click and hold the right mouse button
- The cursor is changed to a hand
- Move the mouse while holding the button to rotate
You'll probably notice not much happening.
After releasing the button, it also seems the mouse cursor can't move to all
positions on screen.
--
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=37096
Bug ID: 37096
Summary: Problems with DC Universe Online and Virtual Desktops
Product: Wine
Version: 1.7.24
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: apcullen(a)yahoo.com
Created attachment 49318
--> http://bugs.winehq.org/attachment.cgi?id=49318
Comparison of wine 1.2 and 1.7.24
DC Universe starts itself up in a multi-stop process using a launcher. When
"Play" is clicked on the launcher, the game appears to start in a blank dos
window that changes to full screen. Then a screen appears where one can select
or create a character. Pressing play here begins actual game play.
To install and run, DC Universe requires "winetricks xact ie8 vcrun2005
vcrun2010"
My machine is a core i5 desktop with radeon graphics (catalyst 13.35). I run
opensuse 13.1 KDE with three virtual desktops which I switch between using
ctrl-f1/ctrl-f2/ctrl-f3.
For stable play, the game has to be run using the "Emulate Virtual Desktop"
option from winecfg. Behavior (or misbehavior) changes using recent wine
versions. I am attaching an annotated log file comparing wine version 1.2.2
Summary
with wine version 1.2: if one does not run "emulate virtual desktop" the
launcher appears and pressing play results in a minimized game window. If you
open the window right away it is blank, and if you don't open it right away
you'll eventually know when the game is ready to play because you'll hear the
music played at the character screen. Then you can maximize the window and
play, but switching virtual desktops caused the game to crash. With "emulate
virtual desktop" selected in winecfg and set to full screen you can see that
the launcher opens what appears to be a dos window (minimized). Opening it
gives a blank window until the full screen game starts. If you leave it
minimized you can always see the minimized window icon even after the full
screen game starts (does not interfere with game play).
With more recent versions of wine:
With "emulate virtual desktop" off in winecfg the game launcher will appear and
pressing "play" will cause the game to start minimized just like in 1.2, but if
you don't open the minimized window the game will freeze and crash. With
"emulate virtual desktop" on the game will start normally and run will but will
freeze when switching KDE virtual desktops.
Sorry if all that was long winded.
--
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=39896
Bug ID: 39896
Summary: Robot animations glitch in main lobby of Lego
Mindstorms EV3 software
Product: Wine
Version: 1.9.0
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: asdfghrbljzmkd(a)outlook.com
Distribution: ---
Created attachment 53286
--> https://bugs.winehq.org/attachment.cgi?id=53286
How it should look
The robot animations glitch in main lobby of Lego Mindstorms EV3 software, as
seen in this screenshot:
https://appdb.winehq.org/screenshots.php?iAppId=15648&iVersionId=33051
Not the most important, but gives a bad first impression when using Wine to run
the software. Note that most robots are in the wrong positions on the screen
along with scrolling, etc. See attachment to see how it should look.
--
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=23954
Summary: Threads not allocated to multiple processors.
Product: Wine
Version: 1.3.0
Platform: x86
URL: http://systester.sourceforge.net/
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: kphillisjr(a)gmail.com
when running systester with multiple threads, the program does not properly run
in parallel... Threads are created, and run, but they are not parallel.
Example Single-Thread run: (512k digits)
systester-cli.exe -gausslg 512K -turns 1 -threads 1
Result: 19 512K N/A 0h 0m 5.318s
Example multi-threaded run: (512k digits)
systester-cli.exe -gausslg 512K -turns 1 -threads 4
Result: 19 512K OK 0h 0m 15.864s
Expected result: around 7s.
Example Single-Thread run: (1M digits)
systester-cli.exe -gausslg 1M -turns 1 -threads 1
result: 20 1M N/A 0h 0m 13.438s
Example multi-threaded run: (1M digits, 4 threads)
systester-cli.exe -gausslg 1M -turns 1 -threads 4
result: 20 1M OK 0h 0m 53.486s
Expected Result: about 15s.
example single-thread run: (1M digits, 1 thread, benchmark mode)
systester-cli.exe -gausslg 1M -turns 1 -threads 1 -bench
result: 20 1M N/A 0h 0m 13.418s
Example multi-threaded run: (1M digits, 4 threads, benchmark mode)
systester-cli.exe -gausslg 1M -turns 1 -threads 4 -bench
result: 20 1M N/A 0h 0m 50.798s
expected result: around 15s.
Test system:
Athlon II x4 630
Ubuntu 10.04 (amd64)
--
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=11898
Summary: Dance eJay Demo 7 crashes due to unimplemented interface
relating to devenum
Product: Wine
Version: 0.9.57.
Platform: PC
URL: http://support.empireinteractive.com/default.aspx?MID=8F
F6D156CB73&PID=D70EED24-7412-4A36-A7B2-879837165C8C
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: nodisgod(a)yahoo.com
Created an attachment (id=11192)
--> (http://bugs.winehq.org/attachment.cgi?id=11192)
Output with devenum and qcap traces
As per bug #11863, a separate bug is filed for other issues in this
application. When starting the Dance eJay 7 Demo, after the trial time dialog,
a page fault is incurred. The devenum trace seems to suggest that the issue
lies in that particular component, as per comment 3 of bug 11863. Attached are
logs pertaining to this issue.
--
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=40335
Bug ID: 40335
Summary: Hardware Detection Possibly Limiting Hardware Via
Render Drivers
Product: Wine
Version: 1.9.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ph4nt0m117(a)gmail.com
Distribution: ---
Through games such as Skyrim, Deus Ex Human Revolution, and games with similar
launchers, my R7 370 is detected as an HD 5600 series card. My 370 is still
labeled, but the render drivers are set back to the newest drivers to work with
the 5600 and limits the game as such, despite that the 370 can render Skyrim in
Ultra and the launcher suggests ultra. I wonder if the hardware detection
limits to render drivers and limits the card that you are using.
--
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=16550
Summary: ConnectNamedPort should never return OK in overlapped
mode
Product: Wine
Version: 1.1.10
Platform: Other
URL: http://chromium.org
OS/Version: other
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: kernel32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
Chromium contains the following code in
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/ipc_channel_w…
BOOL ok = ConnectNamedPipe(pipe_, &input_state_.context.overlapped);
DWORD err = GetLastError();
if (ok) {
// Uhm, the API documentation says that this function should never
// return success when used in overlapped mode.
NOTREACHED();
return false;
}
switch (err) {
case ERROR_IO_PENDING:
input_state_.is_pending = true;
break;
case ERROR_PIPE_CONNECTED:
waiting_connect_ = false;
break;
default:
NOTREACHED();
return false;
}
This triggers, for instance, if you build and run Debug/ui_tests.exe:
[1217/155712:FATAL:ipc_channel_win.cc(206)] Check failed: false.
The obvious one-line change to our ConnectNamedPipe lets the test
get further. I'll post a patch once I have a test case.
--
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=40408
Bug ID: 40408
Summary: Photoshop CC 2015 now crashes when adjusting levels
Product: Wine
Version: 1.9.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sluggo(a)unknown.nu
Distribution: ---
Created attachment 54142
--> https://bugs.winehq.org/attachment.cgi?id=54142
Backtrace from crash
Starting with Wine 1.9.7, Adobe Photoshop CC 2015 (32-bit) crashes whenever I
go to "Levels" and attempt to adjust them.
--
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.