http://bugs.winehq.org/show_bug.cgi?id=34374
Bug #: 34374
Summary: Mac driver does not respect "Emulate a virtual
desktop" option
Product: Wine
Version: 1.7.0
Platform: x86
OS/Version: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winemac.drv
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: samael5(a)verizon.net
Classification: Unclassified
The Mac driver launches all apps in fullscreen mode, regardless of whether
"Emulate a virtual desktop" is set. Virtual desktop still functions as expected
when using the X11 driver on Mac.
--
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=39012
Bug ID: 39012
Summary: Game "Yesterday" crashes while being played (OS X
Yosemite)
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: deka95500(a)hotmail.com
Hi everyone,
I have a version of Yesterday that was built using a wrapper from this
website(external link).
Everything worked fine until I reached the 3rd stage. The game was stuck on a
loading screen and eventually crashed before showing a message saying:
"Yesterday.exe has encountered a serious problem and needs to close."
The wrapper is using Wineskin 2.5.8 / WS8Wine1.3.16. I'm using Mac OS X
Yosemite 10.10.3 on a 2013 MBP.
Can you please help me figure out what the issue is?
Thank you!
--
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=14713
Summary: Xara Xtreme 4: Resizing handles not visible
Product: Wine
Version: 1.1.2
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: info(a)linopus.de
Xara Xtreme 4: Resizing handles not visible
Xara Xtreme 4, the latest edition of the vector drawing application from Xara
(30 days trial available at http://www.xara.com/us/downloads/xtreme/ ), shows
no resizing handles when selecting an object. The resizing handles should be
visible when clicking an object with the select tool.
By contrast, the turning/shearing handles are visible. The turning/shearing
handels appear when clicking an object twice with the select tool.
Additionally, Bezier handles and points on curves do appear, but in wrong
colors (cyan instead of red). Bezier handles and points appear when using the
edit shape tool.
This is on a wine 1.1.2 install on Ubuntu Linux 8.04 in its standard settings.
The same bug is present when using Xara Xtreme X1, which is the thirdlast
edition. The bug is also present in earlier versions of wine (e.g. 0.9.56) and
CrossOver (e.g. 7.0.1).
Yours sincerely
Tobias Hilbricht
--
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=10471
Summary: Radmin viewer 3.1: Ungrayed disabled menu item in the
"Connection Properties" window
Product: Wine
Version: 0.9.48.
Platform: PC
URL: http://www.famatech.com/download/rview31.exe
OS/Version: Linux
Status: UNCONFIRMED
Severity: trivial
Priority: P2
Component: wine-gui
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: bugs.radmin(a)gmail.com
We got an error:
1. Installed Radmin server 3.1 (http://www.famatech.com/download/rserv31.exe)
on a windows computer.
2. Installed Radmin viewer 3.1 on a linux computer with wine installed.
3. Started Radmin viewer and open "Connection Properties" window (can be
reached "Right click on connection icon" --> "Properties" or "Connection" -->
"Connect to").
The list of intermediate hosts in "Advanced settings" should be grayed
(disabled) until checkbox "Connect through host" is marked.
The error was tested on Fedora Core 7 installation with the last wine package
from fedora update site (fedora_mirror/fedora/linux/updates/7/i386/).
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=41267
Bug ID: 41267
Summary: Black ops 2 crashes with "Unhandled exception caught"
Product: Wine
Version: 1.9.18
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: spleefer90(a)gmail.com
Distribution: ---
Created attachment 55567
--> https://bugs.winehq.org/attachment.cgi?id=55567
crash log when trying to launch the game(BO2:MP) from Steam
Game crashes on startup with the message:
"Error during initialization:
Unhandled exception caught"
--
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=54664
Bug ID: 54664
Summary: ZeroMQ 4.3.4#6 (from vcpkg) hangs in wine on macOS
Catalina
Product: Wine
Version: 8.3
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winsock
Assignee: wine-bugs(a)winehq.org
Reporter: steven.schumacher(a)dtn.com
Created attachment 74179
--> https://bugs.winehq.org/attachment.cgi?id=74179
Example app with source and results
Attached is a sample ZMQ pub/sub app including source (and project files but
they might need tweaking) code built against zeromq4.0.5 as a static lib vs
zeromq4.3.4#6 as a dll from vcpkg (at the time of submission, this is the
current version).
Unfortunately I've had issue building newer versions of zmq from source and zmq
no longer maintains windows builds ever since MS took over with vcpkg.
The build environment is VS 2019 on windows 10 (both fully updated).
Both versions of the app run the same on windows. On macOS Catalina (not sure
about earlier or later...my macOS resources are slim) under wine (both
Crossover 22.0.1 and bare wine 8.3), only the version usign zmq4.0.5 works with
the 4.3.4 version of zmq hangs as soon as zmq is initialized.
Text files with output for both on both OS is also included.
--
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=50206
Bug ID: 50206
Summary: Cinebench R23 fails to start (needs dcomp.dll
implementation?)
Product: Wine
Version: 5.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: aidas957(a)gmail.com
Distribution: ---
Created attachment 68717
--> https://bugs.winehq.org/attachment.cgi?id=68717
Cinebench R23 Windows 10 Wine log
As I've said in the title, CInebench R23 fails to start probably because of
missing dcomp.dll which is needed by one of the app's important libraries and
thus the app spits out a bunch of warnings and then closes (with both Windows 7
and Windows 10 versions set in Wine)
I've tried to copy a 64-bit dcomp.dll from a Windows 10 installation, but there
are even more errors of libraries missing (and I can't locate them all)
I'm also using wine-staging. but I doubt that's going to affect anything in
this case
Log with Windows 10 version is attached
--
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=50459
Bug ID: 50459
Summary: Unimplemented function
dcomp.dll.DCompositionCreateDevice called in 64-bit
code (Studio One 5)
Product: Wine
Version: 6.0-rc5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: moseskim84(a)gmail.com
Distribution: ---
Created attachment 69083
--> https://bugs.winehq.org/attachment.cgi?id=69083
Winedbg log file
I'm running Ubuntu 20.10, Wine-6.0-rc5 and have installed Studio One 5
Professional (music production program) into it's own prefix. The program does
not open at all and crashes when I run it with the following error:
wine: Call from 000000007B01135E to unimplemented function
dcomp.dll.DCompositionCreateDevice, aborting
wine: Unimplemented function dcomp.dll.DCompositionCreateDevice called at
address 000000007B01135E (thread 0244), starting debugger...
I have installed the following libraries: corefonts, atmlib, d3dcompiler43,
d3dx9, d9vk/dxvk, fontsmooth-rgb, gdiplus_winxp, msxml3, msxml6, vcrun2008,
vcrun2010, vcrun2012
I have tried it on wine-stable as well (5.0) but it still won't load. Any help
would be appreciated. Thanks!
--
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=50357
Bug ID: 50357
Summary: Star Stable Online crashes with unimplemented function
dcomp.dll.DCompositionCreateDevice2
Product: Wine
Version: 6.0-rc2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: vojtech.dockal(a)gmail.com
Distribution: ---
Created attachment 68955
--> https://bugs.winehq.org/attachment.cgi?id=68955
Backtrace
Star Stable Online crashes with unimplemented function
dcomp.dll.DCompositionCreateDevice2 called in 32-bit code (0x7b010bf6).
Steps to reproduce:
1) Download installer from
https://launcher-data.starstable.com/Star+Stable+Online+Setup+2.6.0.exe and
install it
- Run launcher
- Launcher crashes
Backtrace is included in attachment.
--
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=54933
Bug ID: 54933
Summary: Wine slow on certain fuse filesystems, with fix
Product: Wine
Version: 8.8
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: hwertz10(a)gmail.com
Distribution: ---
Created attachment 74452
--> https://bugs.winehq.org/attachment.cgi?id=74452
CIOPFS speed patch
I found a description of users experiencing slowdowns (even using explorer.exe)
on an MTP filesystem, and I experienced similar slowdowns on an s3ql
filesystem. In short, even using explorer on certain filesystems is slow, and
opening programs that open up more than a handful of files is very slow off
these filesystems.:
https://forum.winehq.org/viewtopic.php?t=36400
I found the root cause courtesy of strace -- in dlls/ntdll/unix/file.c in
get_dir_case_sensitivity_stat (which is called very frequently, I think on any
file open or creation, among others), there is a fstatat system call, then a
check on that result to see if the filesystem is a FUSE filesystem, then if it
is it looks for a .ciopfs directory (because presumably CIOPFS -- Case
Insensitive On Purpose Filesystem -- places a .ciopfs in every directory
specifically so wine can do this test.) It turns out the fstatat call gets
used and free inode count, used and free disk space, etc. along with filesystem
type, and on my large s3ql filesystem at least this takes *8/10ths* of a
second, versus the .ciopfs lookup being in dentry cache -- I don't recall if it
used 0.0001 or 0.00001 seconds, but either way extremely fast compared to the
other call.
Reversing the order of these calls (check for .ciopfs first, then if it's there
run fstatat and check result to see if it's a FUSE filesystem) should not cause
a performance regression on any filesystem (since it's usually going to be out
of the dentry cache) while avoiding this slowdown on a filesystems with slow
filesystem stats.
Just a note, I see the equivalent "is filesystem case sensitive?" check for
MacOS actually only runs any tests once then caches the results; using a
similar "case sensitivity" cache for Linux would also be effective (since it
would only run this piece of code once per wine run then.)
Finally, I wonder if CIOPFS is actually used? I see the last update on it is
from 2011, it may have turned out that Wine's case insensitivity support is
fast enough that CIOPFS did not prove useful. If it's not actually being used
by anyone, removing the CIOPFS tests from file.c could be a reasonable thing to
do.
Please find attached a small patch to implement this change for Linux -- it
simply reverses the order of 3 lines of code, so it runs the (fast) .ciopfs
directory existence test first, then only runs the (on some filesystems much
slower) fstatat call and "is it FUSE filesystem?" test if the.ciopfs directory
actually exists.
Thanks, and keep up the good work!!!
--Henry
--
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.