https://bugs.winehq.org/show_bug.cgi?id=48070
Bug ID: 48070
Summary: Regression: Virtual Desktop not decorated anymore by
the window manager
Product: Wine
Version: 4.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: adrian.kalla(a)gmail.com
Distribution: ---
OS: Kubuntu 18.04 x64
Since Wine 4.17 when using the "Emulate a virtual desktop" the virtual
desktop-window is not decorated anymore by the window manager even if "Allow
the window manager to decorate the windows" is checked.
This results not only in the fact, that the window cannot be moved by drag&drop
of the title-bar (which can be work-arounded using the taskbar, at least with
KDE).
Steps to reproduce:
1. Check "Emulate a virtual desktop"
2. Check "Allow the window manager to decorate the windows"
3. Open winecfg
4. See, that the virtual desktop is not decorated
Expected result:
-Virtual desktop is decorated
The worst thing is, that any full-screen application leaving full-screen
results now in the "virtual desktop" expanding to the full size of the display
the app was on making it unusable.
Steps to reproduce:
1. Check "Emulate a virtual desktop"
2. Check "Allow the window manager to decorate the windows"
3. Open winecfg
4. In the same Wine environment open a full-screen game, e.g. the demo version
of The Settlers 3:
http://s3de.siedler3.net/ftp.bluebyte.com/demos/eng/settlers3amazons/s3a_de…
5. See, that the virtual desktop is not decorated
6. Exit the game
7. See, that the complete display was now overtaken by the virtual desktop
(though the usable area is only in the top-left of the display and in the size
of virtual desktop).
8. Only killing the other open apps in the Wine env makes the display usable
again.
Expected result:
-Virtual desktop does not make the display unusable
--
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=48073
Bug ID: 48073
Summary: ANSI plugin window breaks in Unicode host (Synth1 /
OpenMPT)
Product: Wine
Version: 4.0.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: wine(a)sagagames.de
Distribution: ---
An OpenMPT user has observed an issue with the Synth1 VST which does not happen
in Windows. It boils down to OpenMPT being compiled with Unicode support.
Compiling it as an ANSI application instead makes the Synth1 feature in
question work again.
Downloads:
Synth1: https://daichilab.sakura.ne.jp/softsynth/#down
OpenMPT: https://openmpt.org/download (use the 32-bit version)
Last official OpenMPT ANSI version:
https://download.openmpt.org/archive/openmpt/1.26/OpenMPT-1.26.14.00.zip
To reproduce:
Steps to reproduce:
1) Create a new module in OpenMPT.
2) Open the plugin manager ("Select" button at the bottom of the created
module's window) and add Synth1 VST.dll (or Synth1 VST64.dll if you installed
the 64-bit version of OpenMPT)
3) Click "Put in FX01" to load the plugin.
4) Click the "Edit" button next to the "Select" button to open the plugin's UI.
5) Click the "opt" button in the Synth1 UI to configure at least two sound
banks. There is one valid soundbank in the "soundbank00" folder. For the sake
of testing, you can copy the sy1 files in that folder to e.g. "soundbank01"
and then add that folder as a second bank.
6. Next to the "opt" button is the bank switcher. Click on the text field to
open the bank switcher and try switching between the two banks by selecting
them in the treeview on the left, then choosing a patch from that bank on the
right side (another unrelated bug can be observed here: you cannot see the
patch names in Wine, wine bug 24945)
If you are using the latest OpenMPT version (Unicode), the last step should
fail and you will always stay in the bank that was already selected. With
OpenMPT 1.26, the bank switch will happen as intended. I have verified that
compiling later OpenMPT version as ANSI applications make them work as expected
as well, so I assume that there must be a bug in Wine that is related to mixing
ANSI and Unicode window classes.
--
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=4066
Ken Sharp <imwellcushtymelike(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #60345|0 |1
is obsolete| |
Attachment #60345|1 |0
is patch| |
--
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=13273
Summary: Wine does not remember disk labels set through winecfg
Product: Wine
Version: 1.0-rc1
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: ccf2egd02(a)sneakemail.com
Wine does not seem to remember disk labels or serial numbers when set via
winecfg.
Steps to reproduce:
1) create a disk entry in ~/.wine/dosdevices
ln -s /someplace_with_CD_image ~/.wine/dosdevices/q\:
2) run winecfg, select disk tab.
3) Select q:
4) Show advanced
5) Set to manual setup, disk label to "SOMETHING", disk ID to "FEEDBE"
6) APPLY
7) verify data by selecting some other drive, then re-selecting q:
8) quit winecfg
9) Restart winecfg and reselect the disk tab. Reselect q:
Expected results
Disk label should be "SOMETHING", id should be "FEEDBE"
Actual results
Disk label unset, disk ID 0
--
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=38933
Bug ID: 38933
Summary: In LiveCode 5.0.2, modal dialog prompts are created
behind all windows, hanging Wine.
Product: Wine
Version: 1.7.47
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: alexchandel(a)gmail.com
In LiveCode 5.0.2, whenever a dialog prompt is created, wine creates the modal
window behind the main window. Since the application is blocked until the modal
window is acknowledged, there is no way to continue, and LiveCode is
effectively hung.
Note this does not apply to system prompts, such as the file chooser; only
popups containing custom text, often created with a LiveCode script such as
`ask "foo bar"`, which when run immediately hangs Wine, since a dialog window
is created behind a much larger primary window (assuming one exists).
This error actually effects all LiveCode windows, but it is only critical for
dialogue windows, since those halt the program.
This *may* be related to 16346, although that was documented on X11, not Aqua.
--
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=16346
Summary: App hangs creating modal dialog from WM_ACTIVATEAPP
Product: Wine
Version: 1.1.10
Platform: Other
OS/Version: other
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: user32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jmiller-wine(a)tanner.com
CC: jmiller-wine(a)tanner.com
Created an attachment (id=17660)
--> (http://bugs.winehq.org/attachment.cgi?id=17660)
Simple windows app with source that brings up a message box every time the
window is activated.
I have an app which opens a modal dialog under some circumstances when the
window is activated. Under Windows this works perfectly, but under wine it
causes the app to hang. I have attached a trivial sample app showing this
behavior.
I poked around a bit, and the app is no longer receiving any messages (mouse
moves, keyboard, paint, etc), but I'm not sure where to go from here.
Also under Windows, since the app checks for the wParam (bActive) on
WM_ACTIVATEAPP, it only brings up one copy of the dialog box even after
multiple window activations. Under wine it will bring up another copy of the
dialog if there is already a modal dialog on that app.
--
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=46001
Bug ID: 46001
Summary: MANY com.apple.xbs/Sources/AppleFSCompression errors
from every wine process
Product: Wine
Version: 3.18
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: alexchandel(a)gmail.com
Distribution: ---
Every wine process I run prints the following error message at some point:
/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.200.3/Common/ChunkCompression.cpp:49:
Error: unsupported compressor 8
/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.200.3/Libraries/CompressData/CompressData.c:353:
Error: Unknown compression scheme encountered for file
'/System/Library/CoreServices/CoreTypes.bundle/Contents/Resources/Exceptions.plist'
/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.200.3/Common/ChunkCompression.cpp:49:
Error: unsupported compressor 8
/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.200.3/Libraries/CompressData/CompressData.c:353:
Error: Unknown compression scheme encountered for file
'/System/Library/CoreServices/CoreTypes.bundle/Contents/Library/AppExceptions.bundle/Exceptions.plist'
The simplest replication is just running `winecfg` with a new wine prefix. I'm
using macOS 10.14, but this has happened since at least 10.13. I've never seen
it from any non-wine program ever.
--
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=46002
Bug ID: 46002
Summary: "0011:err:display:macdrv_ChangeDisplaySettingsEx No
matching mode found 1680x1050x32 @60!" every time wine
starts
Product: Wine
Version: 3.18
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: alexchandel(a)gmail.com
Distribution: ---
Every single time wine starts, it displays the error message
0011:err:display:macdrv_ChangeDisplaySettingsEx No matching mode found
1680x1050x32 @60!
at some point. 1680x1050 is indeed the effective resolution of the display,
though the actual resolution is 2560x1600. What error is happening?
--
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=4971
Maik Wagner <maiktapwagner(a)aol.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |maiktapwagner(a)aol.com
--- Comment #32 from Maik Wagner <maiktapwagner(a)aol.com> ---
Created attachment 65627
--> https://bugs.winehq.org/attachment.cgi?id=65627
Console output - wine 4.19 (staging) - EDU Version CD-ROM
Hello everyone,
I am not sure if this belongs here but I have an EDU-Version of the Corel Draw
12 CD a friend borrowed me.
Installation works fine without any winetricks.
--
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=48074
Bug ID: 48074
Summary: Record and Replay Framework doesn't work with wine\how
to bypass the loader - execute native
Product: Wine
Version: 4.19
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winelib
Assignee: wine-bugs(a)winehq.org
Reporter: sasho648(a)gmail.com
Distribution: ---
Mozilla rr(https://github.com/mozilla/rr) stops recording at the loader.
I'm open to suggestions.
I've disassembled and reassembled my application just so i can link it with
winegcc but surprise, surprise - the output still requires a loader.
--
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.