https://bugs.winehq.org/show_bug.cgi?id=52995
Bug ID: 52995
Summary: shell32:shelllink crashes in Wine cause
shell32:shellpath's test_PathResolve() to fail
(test.bat file)
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: shell32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
shell32:shellpath's test_PathResolve() fails seemingly randomly:
shellpath.c:3049: Test failed: test 4: expected
L"C:\\users\\winetest\\Temp\\test.lnk", got
L"C:\\users\\winetest\\Temp\\test.bat"
shellpath.c:3049: Test failed: test 8: expected
L"C:\\users\\winetest\\Temp\\test.lnk", got
L"C:\\users\\winetest\\Temp\\test.bat"
shellpath.c:3048: Test failed: test 14: expected 0, got 1
shellpath.c:3049: Test failed: test 14: expected
L"C:\\users\\winetest\\Temp\\test", got L"C:\\users\\winetest\\Temp\\test.bat"
shellpath.c:3049: Test failed: test 16: expected
L"C:\\users\\winetest\\Temp\\test.lnk", got
L"C:\\users\\winetest\\Temp\\test.bat"
shellpath.c:3049: Test failed: test 19: expected
L"C:\\users\\winetest\\Temp\\test.lnk", got
L"C:\\users\\winetest\\Temp\\test.bat"
shellpath.c:3049: Test failed: test 20: expected
L"C:\\users\\winetest\\Temp\\test.lnk", got
L"C:\\users\\winetest\\Temp\\test.bat"
shellpath.c:3049: Test failed: test 24: expected
L"C:\\users\\winetest\\Temp\\test.lnk", got
L"C:\\users\\winetest\\Temp\\test.bat"
shellpath.c:3048: Test failed: test 26: expected 0, got 1
shellpath.c:3049: Test failed: test 26: expected
L"C:\\users\\winetest\\Temp\\test", got L"C:\\users\\winetest\\Temp\\test.bat"
https://test.winehq.org/data/patterns.html#shell32:shellpath
But it turns out the dates when shell32:shellpath failures all match dates when
shell32:shelllink crashed:
https://test.winehq.org/data/patterns.html#shell32:shelllink
What happens is that shell32:shellpath looks for a "test.lnk" file. But if one
creates a "c:\users\...\Temp\test.bat" file before starting the test, that's
what gets returned instead, thus causing the failures. shell32:shelllink just
happens to use a file by that name. Normally it gets cleaned up but that just
does not happen when shell32:shelllink crashes!
So I think the right fix would be to make shell32:shellpath more resilient:
* Delete "test.*" before checking for test.lnk. But that runs the risk of
deleting files dear to the person running the test (they are in a Temp
directory but still).
* Use some GetTempFileName() or some similar API to generate a unique filename.
* Or just use a name that's less likely to be a leftover from a previous test,
"shellpath.lnk" for instance. Very basic but maybe sufficient.
--
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=52752
Bug ID: 52752
Summary: Rich Edit Control does not support drawing OLE objects
Product: Wine
Version: 7.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: richedit
Assignee: wine-bugs(a)winehq.org
Reporter: jinoh.kang.kr(a)gmail.com
CC: kellnerp(a)earthlink.net, lorentz0021(a)gmail.com
Distribution: ---
Originally reported by Dongwan Kim.
Rich Edit control does not support rendering OLE objects inside text. Instead
it outputs the following log entry:
fixme:richedit:draw_ole Couldn't get storage medium
Affected applications:
- KakaoTalk cannot render emoticons and @mentions in the chat input box.
--
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=46782
Bug ID: 46782
Summary: CompareStringEx does not support SORT_DIGITSASNUMBERS
flag
Product: Wine
Version: 4.2
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: winehq(a)lanrules.de
Distribution: ---
This flag is supported by all Windows versions down to at least Windows 7.
It is used, for example, by Qt in QCollator.
See https://bugreports.qt.io/browse/QTBUG-74209 for reference.
CompareStringEx:
https://docs.microsoft.com/en-us/windows/desktop/api/stringapiset/nf-string…
Wine implementation list of supported flags: dlls/kernel32/locale.c#L3912-L3913
--
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=49232
Bug ID: 49232
Summary: Saints Row The Third Remastered shows floating black
rectangles
Product: Wine
Version: 5.8
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: rca(a)psy-q.ch
Distribution: ---
Created attachment 67236
--> https://bugs.winehq.org/attachment.cgi?id=67236
Screenshot showing black rectangles in the scene
The game shows floating black rectangles in your view. They don't appear when
looking straight down at the ground and also not in indoor scenes. Attached
screenshot shows the effect
I am guessing it might have something to do with street lamp halos or an effect
like that.
The log mentions:
0170:fixme:d3d:wined3d_device_update_sub_resource Ignoring flags 0x2.
00d0:err:d3d:wined3d_debug_callback 0x3a1967e0: "GL_INVALID_OPERATION in
glCopyImageSubData(internalFormat mismatch)".
--
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=32224
Bug #: 32224
Summary: LTspice: selected text/component after Ctrl+F not
highlighted
Product: Wine
Version: unspecified
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: testelor(a)yahoo.com
Classification: Unclassified
Steps to reproduce:
1) Download and install LTspice -
http://ltspice.linear.com/software/LTspiceIV.exe
2) Run LTspice using:
$ wine scad3.exe -nowine
3) Create a new schematic, press 'R' (resistor), for example, and place
it twice by clicking. There should be R1 and R2 on the schematic.
4) Press Ctrl+F and search for "r2", no quotes, it should be highlighted in
yellow, but they're not.
Side note:
- create a new schematic, press F2 to bring up the device list.
- select current, place it on the schematic
- right-click on it and type '1', no quotes, then OK
- press 'R', place it next to the current source, in parallel
- right click on it and replace "R" with '1', no quotes, then OK
- press 'G' and place ground on the lower pins of both components
- press F3 and draw a net by clicking on the unconnected current source's pin,
then on the resistor's
- press 'S' and write ".tran 1", no quotes, don't forget the dot, place it on
the schematic
- in the toolbar, press the 'running man' button, or right-click on the
schematic and choose "run"
- it should be almost instant, a new empty window will pop up, above
- move the mouse cursor over the resistor until the cursor changes into a
current-clamp (something black with a red arrow), then click once to display
the current through the resistor
- in the newly created window, there will be a trace displayed and a label at
the top, reading I(R1)
Alt+left-clicking on the label will highlight the resistor. That's how it
should look like after Ctrl+F. Alternatively, you can just run "wine
scad3.exe", no "-nowine" switch, and repeat the 4 steps in the beginning.
No screenshot as it doesn't make sense to show what doesn't happen...
--
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=28282
Summary: Sound constantly crackling in StarCraft II
Product: Wine
Version: 1.3.26
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: pitlicek(a)gmail.com
Sound is crackling since 1.3.26 (and still does in 27) and console is spammed
with "err:alsa:wine_snd_pcm_recover underrun occurred".
Using ALSA in Wine (PulseAudio in Ubuntu 11.04), full acceleration (changing to
emulation doesn't fix it), 48 kHz (my SoundBlaster can handle it, and again,
change makes no difference), 16 bps. Using OSS and padsp results in no sound at
all.
But it's still better than no sound in 1.3.25 after mmdevapi
rewrite/implementation. ;)
--
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=52951
Bug ID: 52951
Summary: gdi32:font - test_GetGlyphOutline() fails on "VL
Gothic" in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: gdi32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
gdi32:font - test_GetGlyphOutline() fails on "VL Gothic" in Wine:
font.c:4885: Test failed: expected 36, got 19 (VL Gothic:136)
font.c:4903: Test failed: expected 36, got 19 (VL Gothic:136)
https://test.winehq.org/data/patterns.html#gdi32:font
This begs two questions:
1. Is this a bug in the font, or a bug in the test?
2. Why does this happen on the debian11 (and debiant) VMs, but not on fg-deb64
(my development machine)?
On Debian VL Gothic is brought in by this package dependency chain:
libsane -> libpoppler-glib8 -> libpoppler102 -> poppler-data -(suggest)->
fonts-vlgothic
Interestingly poppler-data has alternatives to fonts-vlgothic one of which is
already installed:
fonts-ipaexfont-gothic
fonts-ipfont-gothic (installed)
fonts-ipafont-nonfree-jisx0208
fonts-mona
fonts-takao-gothic
fonts-umeplus-cl
fonts-vlgothic (installed)
But the reason for the difference is that fg-deb64 has the AR PL UMing CN font
(from the fonts-arphic-uming package) and not the TestBot VMs. The lack of
UMing also causes a test to be skipped on the TestBot VMs:
1: (IPAGothic:128)
2: (NanumGothicCoding:129)
font.c:4867: Tests skipped: Fixed-pitch TrueType font for charset 134 is not
available
4: (VL Gothic:136)
So I'm going to install fonts-arphic-uming on the TestBot VMs which should
swipe these two failures under the rug.
Note: I don't have information on how much this will increase the runtime (see
bug 51367) but it seems like it shouldn't be too bad.
--
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=51433
Bug ID: 51433
Summary: Battle.Net: Installer terminates with
BLZBNTBTS0000005C error screen
Product: Wine
Version: 6.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: pep(a)bouah.net
Distribution: ---
Created attachment 70285
--> https://bugs.winehq.org/attachment.cgi?id=70285
Wine logs
Hi there,
Trying to install Heartstone (Blizzard), it failed when updating the battle.net
updater. I reproduced with the Battle.Net Installer directly, downloaded from
here:
https://www.blizzard.com/en-us/download/confirmation?platform=windows&local…
(shasum seems to give me something different each time I download it again)
The error dialog the installer shows says "More help: BLZBNTBTS0000005C".
Logs from the installer in attachments. I get the same error with wine and wine
and wine-staging 6.12 with a fresh profile.
--
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=53026
Bug ID: 53026
Summary: F.E.A.R. (original) has "Disconneted from server"
massage every time starting a new game
Product: Wine
Version: 7.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: VladimirVSC(a)yandex.ru
Distribution: ---
It is impossible to start a new game because of this (however the benchmark
works good). Don't know, if it is a Wine bug or a game quirk, but for Windows 7
(x64) the same copy of the game works fine.
--
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.