https://bugs.winehq.org/show_bug.cgi?id=56463
Bug ID: 56463
Summary: Warframe launcher is rendered incorrectly
Product: Wine
Version: 9.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winewayland
Assignee: wine-bugs(a)winehq.org
Reporter: pmargeti34(a)gmail.com
Distribution: ---
Created attachment 76228
--> https://bugs.winehq.org/attachment.cgi?id=76228
Only few controls aren't rendered black
Warframe launcher window paints most of it's surface area black. Exception are
control located in the top right corner. It can still be interacted with,
cursor changes to hand pointer over the PLAY button and it does launch the game
(which works flawlessly in wayland mode otherwise)
Possibly related? https://bugs.winehq.org/show_bug.cgi?id=56014#c1
--
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=56924
Bug ID: 56924
Summary: wrong keyboard layout when using native wayland
instead of xwayland
Product: Wine
Version: 9.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: bob(a)carnesa.biz.st
Distribution: ---
wrong keyboard layout when using native wayland instead of xwayland
it worked fine previously (~9.10)
edited registry:
[HKEY_CURRENT_USER\Software\Wine\Drivers]
"Graphics"="x11,wayland"
command for xwayland:
wine game.exe
command for wayland native:
DISPLAY='' wine game.exe
what I tried:
setxkbmap ch
swaymsg input type:keyboard xkb_switch_layout next
LC_ALL=fr_CH.UTF-8 DISPLAY='' wine game.exe
--
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=38909
Bug ID: 38909
Summary: Notepad corrupts files saved as utf-8 without a byte
order mark (BOM)
Product: Wine
Version: 1.1.19
Hardware: x86
OS: Linux
Status: NEW
Keywords: download, source
Severity: minor
Priority: P2
Component: programs
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Distribution: ---
Created attachment 51843
--> https://bugs.winehq.org/attachment.cgi?id=51843
screenshot
See attached screenshot and test files (from bug 18191).
--
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=52250
Bug ID: 52250
Summary: windows.h WINE_NOWINSOCK check has been removed
Product: Wine
Version: 6.8
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winelib
Assignee: wine-bugs(a)winehq.org
Reporter: sacrom(a)gmail.com
Distribution: ---
I'm using winelib to compile a Windows/Linux application, where we want to use
the Linux code for threads, files system handling, network code, shared
memory... and we want WINE just for the Win32 GUI code (as we did not implement
a GUI in the Linux/Unix side just on Windows)
Since WINE 6.8 (due this commit
https://source.winehq.org/git/wine.git/commit/9603fba8943f9699e3af6fcfe4acb…)
the WINE_NOWINSOCK check:
#ifndef WINE_NOWINSOCK
#include <winsock.h>
#endif /* WINE_NOWINSOCK */
Has been removed, now my application does not compile as I'm mixing Linux
socket definitions with the WINE/Windows "winsock.h" file.
If I add this check to the file, the application does compile as with WINE 6.7
Is it possible to add the check back? or should this be done in another way
now?
--
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=54261
Bug ID: 54261
Summary: State of Survival got stuck at the end of the loading
screen (fixme:dxgi:d3d11_swapchain_Present1?)
Product: Wine
Version: 8.0-rc2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: thierry.vignaud(a)gmail.com
Distribution: ---
Created attachment 73817
--> https://bugs.winehq.org/attachment.cgi?id=73817
Wine logs when starting the game
State of Survival got stuck at the end of the loading screen
See https://appdb.winehq.org/objectManager.php?sClass=version&iId=41243
We can install the game using
https://sos-pc.kingsgroupgames.com/dlfile/?clickcode=official
It then downloads the game contents but doesn't progress near the end: it got
gets stuck on the Loading game resources screen.
Then there's a "dnrepair" popup that's unreadable due to squares in place of
most letters.
-----------------------
The game FAQ talk about that;
https://sos.kingsgroupgames.com/pc/faq?seq=error&p=ss_global&t=8Yim9FAR&l=en
"How do I solve the problem where the game gets stuck on the Loading game
resources screen?
1. Make sure that your VT (Virtualization Technology) is turned on. Please
refer to this tutorial: How to Turn on VT>>
2.
Close your security/anti-virus software, run the repair program,
restart your PC, and then re-enter the game. You can find the repair
program here: C:\Program Files (x86)\FunPlus\State of
Survival\engine\1.0.8\dnrepairer.exe"
-----------------------
Which is the famous dnrepair popup we're seeing above
On the terminal, wine displays tons of this message:
0158:fixme:dxgi:d3d11_swapchain_Present1 Ignored present parameters 0089D778.
Sometimes another value is displayed:
0158:fixme:dxgi:d3d11_swapchain_Present1 Ignored present parameters 0089AD58.
--
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=50065
Bug ID: 50065
Summary: its too old to use
Product: Wine
Version: 5.20
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lankorchang1(a)gmail.com
its too old to use
--
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=47957
Bug ID: 47957
Summary: critical error when trying to start pCLAMP
Product: Wine
Version: 4.0.1
Hardware: x86
OS: Mac OS X
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: winedbg
Assignee: wine-bugs(a)winehq.org
Reporter: katiekim3088(a)gmail.com
Created attachment 65462
--> https://bugs.winehq.org/attachment.cgi?id=65462
this is the backtrace that it gave me
I am unable to use my app
--
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=22080
Summary: Wine removes custom drive mappings
Product: Wine
Version: 1.1.40
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: sub.mesa(a)gmail.com
Wine appears to be forgetting or removing my drive mappings. I have an NFS
filesystem mouned on /nfs, i am the owner of that directory with appropriate
write permissions. I do something like this:
# create new wine directory
mkdir /nfs/winetest
# populate wine directory
WINEPREFIX=/nfs/winetest/ winecfg
# Now i go to Drives tab, make a new D-drive, set it to /nfs, then click Apply
# close winecfg
# when i launch winecfg again, the /nfs D-drive is still there
# so far so good
# now launch some random application on the NFS-mount
cd /nfs/
WINEPREFIX=/nfs/winetest/ wine "D:\\prip\\setup.exe"
# result: wine: module not found; application does not start properly
# now check winecfg again:
WINEPREFIX=/nfs/winetest/ winecfg
# now our D-drive mapping isn't set to anything; its empty.
So it appears wine removes my custom drive mappings whenever an application is
launched or tries to access its DLLs located there. If i did something wrong,
i'm not aware of it. Wine should just accept the D-drive and launch the
application, not removing my drive mapping.
I also tested without using NFS; on my home directory.
mkdir ~/winetest
mkdir ~/driveD
WINEPREFIX=/home/<user>/winetest winecfg
# set drive D to map to /home/<user>/driveD/ type Local Disk
# click apply & close winecfg
cp -p ~/nfs/prip/setup.exe ~/driveD/
WINEPREFIX=/home/<user>/winetest/ wine "D:\\setup.exe"
# result: fails again, drive D gone.
I'm using Ubuntu 9.10 64-bit, wine 1.1.40 per winehq.org PPA; no modifications.
The latest .41 versions is not in your PPA yet, so i can't test. Can anyone
confirm this bug?
--
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=57808
Bug ID: 57808
Summary: crash when switching linux virtual consoles:
XI_BadDevice
Product: Wine-staging
Version: 9.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: forestix(a)nom.one
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Whenever I switch away from the current virtual console on linux (using
Control+Alt+F2 etc.) wine processes crash with output like this:
X Error of failed request: XI_BadDevice (invalid Device parameter)
Major opcode of failed request: 131 (XInputExtension)
Minor opcode of failed request: 3 (X_OpenDevice)
Device id in failed request: 0xXXXXXXX
Serial number of failed request: 251
Current serial number in output stream: 251
X Error of failed request: XI_BadDevice (invalid Device parameter)
Major opcode of failed request: 131 (XInputExtension)
Minor opcode of failed request: 3 (X_OpenDevice)
Device id in failed request: 0xXXX
Serial number of failed request: 222
Current serial number in output stream: 222
(I have replaced the actual device IDs with X characters above.)
As far as I have seen, it affects all applications. Even winecfg crashes on VC
switch.
The problem occurs only in wine-staging; not in wine-devel or wine-stable.
The problem is present in versions 9.4, 9.8, 10.0, and presumably all versions
in between.
The problem is not present in version 9.3.
Tested with official debian builds from dl.winehq.org.
This looks similar to bug 57123. I opened a new report instead of commenting in
that one because in my case, no devices are unplugged or plugged in to cause
the crash, and because I have no easy way to test that scenario.
--
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=18234
Summary: Approach: Maximizing internalal minimized icon give
"About Wine"
Product: Wine
Version: 1.1.20
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: ToddAndMargo(a)verizon.net
Created an attachment (id=20742)
--> (http://bugs.winehq.org/attachment.cgi?id=20742)
About wine instead of a maximized window
Hi All,
In Lotus Approach, if you use the internal windows control (the low set of
caption buttons) to minimize a single database, it will appear as an icon in
the lower right of Approach's window. If you double click on the icon to
maximize the window again, you get "About Wine 1.1.20" (and no maximized
window)
Many thanks,
-T
--
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.