https://bugs.winehq.org/show_bug.cgi?id=4666
Joo <julianmelvynjones(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|julianmelvynjones(a)gmail.com |
--
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=50743
Bug ID: 50743
Summary: .NET Core WPF applications with layered windows do not
initially render
Product: Wine
Version: 6.3
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: winex11.drv
Assignee: wine-bugs(a)winehq.org
Reporter: madewokherd(a)gmail.com
Distribution: ---
Found while working on WPF in Wine Mono. I've committed a work-around to Wine
Mono (not yet in a release), but the bug is present in .NET Core as well.
For any application using a WPF window with AllowsTransparency set to true
(which makes it a layered window), the window's contents are initially an
opaque black fill. Fully transparent areas are still transparent. If part of
the window redraws (such as from a hover effect), the refreshed area draws
correctly.
I'm working on uploading a self-contained test case. Unfortunately, the archive
exceeds the file size limit.
The work-around in Wine Mono is to redraw the entire window in response to
WM_WINDOWPOSCHANGED messages.
The code that controls this can be found here:
https://github.com/dotnet/wpf/blob/release/3.1/src/Microsoft.DotNet.Wpf/src…
There are a lot of cases where they redraw, but the relevant ones here are
probably WM_SIZE and WM_SHOWWINDOW.
I tried the test program in CrossOver Mac 20, and it rendered correctly. This
makes me think it's an X11-specific issue, but it could also be related to
version difference.
--
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=4666
--- Comment #64 from Bernd Buschinski <b.buschinski(a)googlemail.com> ---
I just tried to play
KalOnline, but failed, my account is blocked for regional reasons, I can no
longer test.
Then I tried
AirRivals, but it just told me the server is offline.
--
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=52499
Bug ID: 52499
Summary: .exe doesnt execute
Product: Wine
Version: 7.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: crb26official(a)gmail.com
Distribution: ---
Created attachment 71794
--> https://bugs.winehq.org/attachment.cgi?id=71794
backtrace file
not sure what this bug is
--
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=52335
Bug ID: 52335
Summary: StarCraft Remastered hangs in Multiplayer screen
Product: Wine-staging
Version: 7.0-rc4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dimich.dmb(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 71502
--> https://bugs.winehq.org/attachment.cgi?id=71502
Screenshot
With wine-staging 7.0rc4 run StarCraft Remastered from Battle.net launcher, in
main menu select "Multiplayer" -> "Expansion". The game hangs. "Select
Connection" list is empty, buttons are empty (see attached screenshot).
After downgrading wine-staging to 7.0rc3 the issue disappears and everything
works fine.
Distro: Arch Linux.
--
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=52496
Bug ID: 52496
Summary: supermemo18 's render become so slow when text has
foreign style.
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: wuyudi1109(a)gmail.com
Distribution: ---
Created attachment 71791
--> https://bugs.winehq.org/attachment.cgi?id=71791
by `WINEPREFIX="xxx" wine sm18.exe &> log1.txt`
The text rendered in SuperMemo18 is so slow.
wine-7.0
Linux archlinux 5.16.3-arch1-1 #1 SMP PREEMPT Thu, 27 Jan 2022 14:18:25 +0000
x86_64 GNU/Linux
repo address
https://github.com/wuyudi/sm18-lazy-package
It's ok to redistribute this, see readme.
---
According to this repo.
https://github.com/alessivs/supermemo-wine/blob/master/verbs/supermemo18.ve…
run below one by one(or there will be too many bugs to show this problem.)
```
WINEPREFIX="xxx" winetricks ie8
WINEPREFIX="xxx" winetricks gdiplus_winxp
WINEPREFIX="xxx" winetricks tahoma
WINEPREFIX="xxx" winetricks fontsmooth=rgb
WINEPREFIX="xxx" winetricks winxp
```
Then
`WINEPREFIX="xxx" wine sm18.exe`
Click File on the Manu bar.
New collection
Change the name or just click ok.
Click Add on the left.
the right will show a frame to input text.
Go to any website, copy-paste some text into it,
(for example, this website
https://suulnnka.github.io/BullshitGenerator/index.html?%E4%B8%BB%E9%A2%98=…
is used to generate a lot of meaningless Chinese words to test text render.)
then, it begins slowly.
select some words. Alt+X, becomes very slow.
--
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=52481
Bug ID: 52481
Summary: Windows 7 Aero theme support
Product: Wine
Version: 7.1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: uxtheme
Assignee: wine-bugs(a)winehq.org
Reporter: aros(a)gmx.com
Distribution: ---
Would be great if it were possible to use Windows 7 Aero theme in Wine.
Currently Wine doesn't "see" it. There are no messages in console whatsoever.
2. I've tried using https://www.nirsoft.net/utils/dll_export_viewer.html but it
doesn't show anything for aero.msstyles as if it's not a valid DLL file.
3. I've tried running the style as an application after renaming it to
aero.exe:
Application could not be started, or no application associated with the
specified file. ShellExecuteEx failed: File not found.
Just to check if it maybe imports something which Wine doesn't support. Nope,
it's just missing main().
4. strings aero.msstyles | grep -i dll
Produces nothing. There are no imports per se.
sha256sum aero.msstyles
cae5a560fe3603dc8c8ad3ca08e6b93a5e277e44c3ea06146083ea859ce745c2 aero.msstyles
FileVersion: 6.1.7601.17514 (win7sp1_rtm.101119-1850)
--
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=52422
Bug ID: 52422
Summary: USB CH Pro Pedals do not show up as a joystick device
in 7.0
Product: Wine
Version: 7.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: hid
Assignee: wine-bugs(a)winehq.org
Reporter: twhitehead(a)gmail.com
Distribution: ---
Created attachment 71679
--> https://bugs.winehq.org/attachment.cgi?id=71679
Full trace.log file
Using the just released wine 7.0, I no longer see my Pro Pedals as a joystick
device (e.g., in the control panel). I expect this is related to all the
joystick input device stack work that occurred in this release.
I know that it is enumerating/processing my /dev/input/event* devices, as, if I
manually make them all read/writable (instead of the system default which is
just the Pro Pedals one), then my Wacom tablet shows up as a joystick device in
the control panel.
I am totally guessing, but maybe there is an issue properly categorizing the
device? I know in the past, in other projects, it has been misclassified due to
not having any buttons.
Anyway, I looked through the code, but couldn't really follow it other than
noting that it does look at the udev classification. Here is what my udev is
reporting
tyson@tux ~> udevadm info /dev/input/event14
...
E: ID_INPUT=1
E: ID_INPUT_ACCELEROMETER=0
E: ID_INPUT_JOYSTICK=1
E: ID_VENDOR=CH_PRODUCTS
E: ID_VENDOR_ENC=CH\x20PRODUCTS
E: ID_VENDOR_ID=068e
E: ID_MODEL=CH_PRO_PEDALS_USB
E: ID_MODEL_ENC=CH\x20PRO\x20PEDALS\x20USB\x20
E: ID_MODEL_ID=00f2
E: ID_REVISION=0000
E: ID_SERIAL=CH_PRODUCTS_CH_PRO_PEDALS_USB
Here you can see systemd has granted my account full read/write access to the
device due to its classification
tyson@tux ~> getfacl /dev/input/event14
...
user:tyson:rw-
group::rw-
mask::rw-
...
And here is a partial dump of starting the control panel (full trace is
attached) showing it is successfully opening the device and making various
ioctl calls to enumerate its capabilities
tyson@tux ~> strace -ff -s 4096 -P /dev/input/event14 -E
WINEDEBUG=+dinput,+hid,+plugplay wine control 2>&1 | tee trace.log
...
009c:trace:hid:bus_main_thread L"SDL" main loop starting
009c:trace:hid:sdl_bus_init args 0xd8f6b4
[pid 1861507] fstatat64(AT_FDCWD, "/dev/input/event14", {st_mode=S_IFCHR|0660,
st_rdev=makedev(0xd, 0x4e), ...}, 0) = 0
[pid 1861507] openat(AT_FDCWD, "/dev/input/event14", O_RDONLY) = 40
[pid 1861507] ioctl(40, EVIOCGBIT(0, 4), [EV_SYN EV_ABS]) = 4
[pid 1861507] ioctl(40, EVIOCGBIT(EV_KEY, 96), []) = 96
[pid 1861507] ioctl(40, EVIOCGBIT(EV_REL, 4), []) = 4
[pid 1861507] ioctl(40, EVIOCGBIT(EV_ABS, 8), [ABS_X ABS_Y ABS_Z]) = 8
[pid 1861507] close(40) = 0
[pid 1861507] fstatat64(AT_FDCWD, "/dev/input/event14", {st_mode=S_IFCHR|0660,
st_rdev=makedev(0xd, 0x4e), ...}, 0) = 0
[pid 1861507] openat(AT_FDCWD, "/dev/input/event14", O_RDWR) = 39
[pid 1861507] ioctl(39, EVIOCGBIT(EV_FF, 128), []) = 16
[pid 1861507] close(39) = 0
009c:trace:hid:bus_main_thread L"SDL" main loop started
...
Here is a dump of the HID info
root@tux /h/tyson# usbhid-dump -m 068e
003:059:000:DESCRIPTOR 1642627470.833610
05 01 09 04 A1 01 05 01 09 01 A1 00 09 30 09 31
09 32 15 00 26 FF 00 75 08 95 03 81 02 C0 C0
root@tux /h/tyson# usbhid-dump -m 068e | grep -v : | xxd -r -p | hidrd-convert
-o spec
Usage Page (Desktop), ; Generic desktop controls (01h)
Usage (Joystick), ; Joystick (04h, application collection)
Collection (Application),
Usage Page (Desktop), ; Generic desktop controls (01h)
Usage (Pointer), ; Pointer (01h, physical collection)
Collection (Physical),
Usage (X), ; X (30h, dynamic value)
Usage (Y), ; Y (31h, dynamic value)
Usage (Z), ; Z (32h, dynamic value)
Logical Minimum (0),
Logical Maximum (255),
Report Size (8),
Report Count (3),
Input (Variable),
End Collection,
End Collection
I am happy to provide any other details that I can/run any test you want. Just
let me know.
Thanks! -Tyson
--
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=52489
Bug ID: 52489
Summary: supermemo18 's render become so slow.
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: wuyudi1109(a)gmail.com
Distribution: ---
Created attachment 71782
--> https://bugs.winehq.org/attachment.cgi?id=71782
by `wine sm18.exe &> log.txt`
The text rendered in SuperMemo18 is so slow and often tells me lack of RAM(pop
up a window says "内存不足"), but obviously, my RAM was enough.
wine-7.0
Linux archlinux 5.16.3-arch1-1 #1 SMP PREEMPT Thu, 27 Jan 2022 14:18:25 +0000
x86_64 GNU/Linux
repo address
https://github.com/wuyudi/sm18-lazy-package
It's ok to redistribute this, see readme.
--
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=51551
Bug ID: 51551
Summary: Medibang Paint Pro: Pen pressure and opacity on Wine
6.14 not working
Product: Wine
Version: 6.14
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: wintab32
Assignee: wine-bugs(a)winehq.org
Reporter: crxtrtupgm(a)gmail.com
Distribution: ---
Created attachment 70394
--> https://bugs.winehq.org/attachment.cgi?id=70394
Log.txt - Log for wintab32.
OS: Pop!_OS 21.04 x86-64
App in question: Medibang Paint Pro 26.2
Wine ver: 6.14
Machine: Acer Nitro 5
Tablet used: XP-PEN Star 03 (Old version)
Driver for tablet: Pentablet 1.2.14.1 (Old driver provided by XP-PEN Support)
The application works just as well, can connect to the Medibang Cloud and all
that.
Drawing in the tablet does work, you can draw with it and it registers
properly. The right click of the tablet also works. Issue is the pen pressure
and opacity not working.
This is not the case in native applications such as Krita. Pressure and opacity
works on those applications.
Before you say it, I tried the newer driver from the XP-PEN website and I have
not made it to work on the OS. In fact the driver I used for windows is also in
the older side. Apparently the tablet is old enough that modern support for it
is now unavailable.
I have already replied in the issue Bug 40199 but reported this new bug ID
anyway for investigation for newer Wine versions.
--
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.