https://bugs.winehq.org/show_bug.cgi?id=40510
Bug ID: 40510
Summary: Garena+: messenger window disappears after clicking on
it.
Product: Wine
Version: 1.9.8
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jeffrey_go(a)dlsu.edu.ph
Distribution: ---
Created attachment 54307
--> https://bugs.winehq.org/attachment.cgi?id=54307
a backtrace report
after entering the username/password
it will show that it is initializing
afterwards, wine crashes
--
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=34576
Bug #: 34576
Summary: Altova XML Spy 2013 rel.2 sp2: crashes during entering
registration code
Product: Wine
Version: 1.7.2
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wininet
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: kroman(a)hp.com
Classification: Unclassified
Created attachment 46028
--> http://bugs.winehq.org/attachment.cgi?id=46028
backtrace
Latest version of Altova crashes while entering (correct) permament
registration code. Steps to reproduce:
1. Download latest Altova XML Spy 32-bit, Enterprise Edition from
http://www.altova.com/download_current.html.
2. Install it (no .wine directory).
3. Run Xml Spy from Wine menu from application launcher.
4. Enter permament license key, my data:
Name: Kamil Roman
Company: Hewlett-Packard Co
Unfortunately, for obvious reasons I can't give you the registration key.
However, one may request for a trial key, which will probably result in the
same error as the application seems to crash while trying to download some data
from the Internet.
Running Kubuntu Running, wine 1.7.2 from wine ppa. Any workaround is very
welcome.
Installer's sha1 sum:
kamil@localhost:~/Downloads/instalki HP$ sha1sum XMLSpyEnt2013.exe
b6a8a921b67f358609ebf5092ba7b2a8fc94a5ac XMLSpyEnt2013.exe
--
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=50483
Bug ID: 50483
Summary: Starcraft Remastered: Unable to connect to Battle.net
servers or create LAN game
Product: Wine-staging
Version: 5.19
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: zculek(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
With wine-staging versions >5.18 (higher than 5.18) I am no longer able to
connect to Battle.net servers eaither at all (just hangs on "Connectiong...";
screenshot attached) or randomly to some specific server (most often Europe
doesn't work, but sometimes others as well), no error being given.
Sometimes connecting to Battle.net servers passes (mostly if I first go to
create a LAN game, then return from that menu to selecting between Battle.net
and LAN menu), but I am not able to create a game (error: "Failed to advertise
the game. Connection lost while trying to advertise the game. (Error 5:9)";
screenshot attached) nor join any of the games (error: "Unable to join game";
screenshot attached).
Creating a LAN game doesn't work either, it just hangs on "Creating game..."
(screenshot attached).
All of this works properly with wine-staging 5.18. The versions >5.18 that I
tested - 5.19, 5.20, 5.21, 6.0-rc1 - all of them have the same problematic
behavior, so I guess it must be something 5.18 > 5.19.
I can confirm that this is not the issue with Battle.net availability or
IP/account being temp blocked or anything similar, as everything works properly
with 5.18 (also with wine-staging 5.7) and when using the same Battle.net
account and connecting from the same IP/network using a Windows machine.
I have also seen other users reporting the same issue elsewhere on the
Internet, so this is not an isolated case/issue with my machine/setup, e.g.
https://lutris.net/games/starcraft-remastered/
Let me know if any additional details are needed. I was checking the logs and
console output, but I'm not sure any of it would be helpful.
System:
OS: Linux Mint 20 Ulyana
Kernel: 5.4.0-60-generic x86_64
Working wine-staging versions: 5.18, 5.7
Non-working wine-staging versions: 5.19, 5.20, 5.21, 6.0-rc3
Screenshots:
<a href="https://ibb.co/r57nHTZ"><img
src="https://i.ibb.co/r57nHTZ/2020-01-11-SCR-01-LAN-hang-create-game.png"
alt="2020-01-11-SCR-01-LAN-hang-create-game" border="0"></a> <a
href="https://ibb.co/g6BHLZ9"><img
src="https://i.ibb.co/g6BHLZ9/2020-01-11-SCR-02-Battlenet-hang-create-game.png"
alt="2020-01-11-SCR-02-Battlenet-hang-create-game" border="0"></a> <a
href="https://ibb.co/8sxV0Cy"><img
src="https://i.ibb.co/8sxV0Cy/2020-01-11-SCR-03-Battlenet-error-create-game.png"
alt="2020-01-11-SCR-03-Battlenet-error-create-game" border="0"></a> <a
href="https://ibb.co/BBk2Yq8"><img
src="https://i.ibb.co/BBk2Yq8/2020-01-11-SCR-04-Battlenet-error-join-game.png"
alt="2020-01-11-SCR-04-Battlenet-error-join-game" border="0"></a> <a
href="https://ibb.co/L5FcnzC"><img
src="https://i.ibb.co/L5FcnzC/2020-01-11-SCR-05-Battlenet-hang-connecting.png"
alt="2020-01-11-SCR-05-Battlenet-hang-connecting" border="0"></a>
--
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=49141
Bug ID: 49141
Summary: Unable to use winecfg to create a new WINEPREFIX
Product: Wine
Version: 5.8
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ahmed.com(a)tutanota.com
Distribution: ---
Created attachment 67143
--> https://bugs.winehq.org/attachment.cgi?id=67143
winecfg terminal output
I deleted the default WINEPREFIX, and I can't create a new WINEPREFIX using
winecfg.
I copied the terminal output of winecfg, in the attachments, and I will add the
terminal output of wineboot -u in the next comment.
--
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=46438
Bug ID: 46438
Summary: Fonts antialiasing does not work in Wine-i686 built on
a x86-64 host
Product: Wine
Version: 4.0-rc5
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdi32
Assignee: wine-bugs(a)winehq.org
Reporter: aros(a)gmx.com
Distribution: ---
Created attachment 63221
--> https://bugs.winehq.org/attachment.cgi?id=63221
winecfg
It's not the first time I'm facing this issue and now that I'm finally sick and
tired of it, I'm filing a bug report because I want to figure out once and for
all why I'm affected.
I run Fedora 29 64 and I'm building Wine this way:
export CFLAGS="-O2 -pipe -m32 -march=pentium-m"
export LDFLAGS="-Wl,-O1 -Wl,--hash-style=gnu"
./configure --prefix=/opt/wine --disable-tests && make && make install
Wine seemingly successfully finds and uses the necessary libraries:
$ strace -e file -fF notepad 2>&1 | egrep "freetype|libfontconf"
[pid 20804] openat(AT_FDCWD, "/lib/libfreetype.so.6",
O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 14
[pid 20804] openat(AT_FDCWD, "/lib/libfontconfig.so.1",
O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 14
[pid 20782] openat(AT_FDCWD, "/lib/libfreetype.so.6",
O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 5
[pid 20782] openat(AT_FDCWD, "/lib/libfontconfig.so.1",
O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 5
[pid 20775] openat(AT_FDCWD, "/lib/libfreetype.so.6",
O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 10
[pid 20775] openat(AT_FDCWD, "/lib/libfontconfig.so.1",
O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 10
[pid 20808] openat(AT_FDCWD, "/lib/libfreetype.so.6",
O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 8
[pid 20808] openat(AT_FDCWD, "/lib/libfontconfig.so.1",
O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 8
However fonts are not antialiased.
Please advise.
--
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=41946
Bug ID: 41946
Summary: Can't run SourceSafe over samba mount
Product: Wine
Version: 1.9.23
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: wineserver
Assignee: wine-bugs(a)winehq.org
Reporter: kelk1(a)hotmail.com
Distribution: ---
Hi,
Until maybe a year or so, I used to be able to use SourceSafe with the
executable on a mounted samba share. Then one day, it started failing after the
authentication dialog.
I get a Microsoft Visual SourceSafe dialog which says "Invalid Handle" and a
winerserver message on the console which says: "file_set_error() can't map
error: Operation not supported"
Here is my environment in Fedora 24:
${HOME}/gvfs is a symlink to /run/user/uid/gvfs
${SSAFE} is set to
"${HOME}/gvfs/smb-share:domain(...)/SourceSafe/somedir/vss6/win32/SSEXP.EXE"
When I run `wine "$SSAFE"` (which again used to work until fairly recently), I
get the Visual SourceSafe Login dialog and the "Invalid Handle" error.
$ rpm -q wine samba
wine-1.9.23-2.fc24.x86_64
samba-4.4.7-2.fc24.x86_64
--
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=41718
Bug ID: 41718
Summary: netapi32:access test regression
Product: Wine
Version: 1.9.8
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: netapi32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
Since the commit below, the newtb-w7u machine times out:
access.c:342: Local groupname:L"Administrators"
access.c:343: Comment: L"Administrators have complete and unrestricted access
to the computer/domain"
access.c:352: domain and name: L"wtbw7u\\Administrator"
access.c:352: domain and name: L"wtbw7u\\winetest"
test failed: timed out
See:
https://test.winehq.org/data/tests/netapi32:access.html
commit 199b0bf84eb8f4cc8ab2bc44f8e40f0b42d48575
Author: Hans Leidekker <hans(a)codeweavers.com>
Date: Mon Oct 24 10:04:19 2016 +0200
netapi32: Implement DavGetUNCFromHTTPPath.
Signed-off-by: Hans Leidekker <hans(a)codeweavers.com>
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
Hans is already aware of this issue and has determined that the first 3
DavGetUNCFromHTTPPath() calls take 15, 5 and 9 seconds, specifically on that
one box. Commenting one of these 3 calls means the next 3 will take this amount
of time.
It appears the only thing specific to that box is that it has a CD in the
CD-ROM drive. However it's a virtual CD drive accessing an ISO image so there
is no reason for it to be 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=49938
Bug ID: 49938
Summary: Repeating "00fc:err:service:validate_context_handle
Handle is of an invalid type (1, 2)" at startup
Product: Wine
Version: 5.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: advapi32
Assignee: wine-bugs(a)winehq.org
Reporter: b7.10110111(a)gmail.com
Distribution: ---
After Wine upgrade to current master (cce4f36e214125173a8df84d27ba5b33df8d1434)
I now have to wait for about half a minute to launch any program in Wine — even
winecfg. Here's what I see in the console (TICK prints are to show 0.5s
delays):
```
$ while sleep 0.5; do echo TICK; done & winecfg
[1] 15278
0050:err:service:validate_context_handle Handle is of an invalid type (1, 2)
TICK
0050:err:service:validate_context_handle Handle is of an invalid type (1, 2)
0060:err:ole:start_rpcss Failed to start RpcSs service
0060:err:ole:NDRCContextBinding invalid handle 00856188
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
0074:err:service:validate_context_handle Handle is of an invalid type (1, 2)
0060:err:ole:start_rpcss Failed to start RpcSs service
0060:err:ole:NDRCContextBinding invalid handle 00854A10
TICK
TICK
003c:fixme:service:scmdatabase_autostart_services Auto-start service L"NDIS"
failed to start: 1053
0074:err:service:validate_context_handle Handle is of an invalid type (1, 2)
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
003c:fixme:service:scmdatabase_autostart_services Auto-start service
L"PlugPlay" failed to start: 1053
009c:err:service:validate_context_handle Handle is of an invalid type (1, 2)
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
003c:fixme:service:scmdatabase_autostart_services Auto-start service L"WineBus"
failed to start: 1053
00b4:err:service:validate_context_handle Handle is of an invalid type (1, 2)
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
003c:fixme:service:scmdatabase_autostart_services Auto-start service L"wineusb"
failed to start: 1053
00cc:err:service:validate_context_handle Handle is of an invalid type (1, 2)
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
TICK
003c:fixme:service:scmdatabase_autostart_services Auto-start service
L"MountMgr" failed to start: 1053
TICK
00ec:err:service:validate_context_handle Handle is of an invalid type (1, 2)
00dc:err:ole:start_rpcss Failed to start RpcSs service
00dc:err:ole:NDRCContextBinding invalid handle 008566A0
```
At the end of this log the winecfg window finally appears.
This is a regression, to which git-bisect gave the following output:
e9090e1c903578b30118ce9559c1824361abc6da is the first bad commit
commit e9090e1c903578b30118ce9559c1824361abc6da
Author: Hans Leidekker <hans(a)codeweavers.com>
Date: Mon Sep 7 14:10:13 2020 +0200
advapi32: Reimplement SystemFunction036 using system interrupt information.
Signed-off-by: Hans Leidekker <hans(a)codeweavers.com>
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
:040000 040000 c6d1fe863cec8623d492795bb4c55031ba8bdd1f
a1213f0b61b72768e15e37c6dc60f98cc7565566 M dlls
--
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=49798
Bug ID: 49798
Summary: StarCraft 2 hangs on startup since 5.12
Product: Wine
Version: 5.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: kolAflash(a)kolahilft.de
Distribution: ---
Created attachment 68111
--> https://bugs.winehq.org/attachment.cgi?id=68111
log: wine-5.16 -> SC2 broken
Can't start StarCraft II with Wine >= 5.12.
Wine 5.11 works fine.
The SC2_x64.exe process uses a full cpu core for some seconds and then simply
stalls with this message. Any graphical window can be seen before this happens.
(wine-staging-5.13 on AMD Phenom II X4 955)
00e8:err:virtual:virtual_setup_exception stack overflow 1808 bytes in thread
00e8 addr 0x7bc8200d stack 0x9fc08f0 (0x9fc0000-0x9fc1000-0xa7c0000)
(wine-5.16 on AMD Ryzen-3500U)
00d0:err:virtual:virtual_setup_exception stack overflow 1776 bytes in thread
00d0 addr 0x7f833152cddc stack 0xa0a0910 (0xa0a0000-0xa0a1000-0xa8a0000)
Until from this message, the stdout/stderr only has very minor differences.
The attached logs have been created running:
C:\Program Files (x86)\StarCraft II\Support64\SC2Switcher_x64.exe
Results are the same when running from Blizzard launcher.
Tested with:
- wine-staging-5.11 (works)
- wine-staging 5.12 + 5.13 + 5.14 + 5.16 (broken)
- wine-5.16 (broken)
Prefix: Windows 7 - 64 bit
Same results on two Debian-11 (Beta/Testing) machines with different AMD Phenom
II and Ryzen-3500U processors.
These bugs look similar. But their Wine versions simply don't match up.
https://bugs.winehq.org/show_bug.cgi?id=49476
Overwatch doesn't start on 5.10, 5.11
https://bugs.winehq.org/show_bug.cgi?id=49436
64-bit Diablo III hangs on startup since 5.11
(fixed in 5.13 / 5.14, so that also doesn't match up)
Maybe related:
https://forum.winehq.org/viewtopic.php?t=34099
--
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=45829
Bug ID: 45829
Summary: SHGetNameFromIDList argument value differs in
different SDK version
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: shell32
Assignee: wine-bugs(a)winehq.org
Reporter: 137729898(a)qq.com
Distribution: ---
The second parameter for SHGetNameFromIDList are defined as this in different
version of Windows SDK. Note that the values for
SIGDN_PARENTRELATIVEFORADDRESSBAR differ in old and new versions:
// Windows SDK 5.0
typedef enum __MIDL_IShellItem_0001 {
SIGDN_NORMALDISPLAY = 0,
SIGDN_PARENTRELATIVEPARSING = 0x80018001,
SIGDN_PARENTRELATIVEFORADDRESSBAR = 0x8001c001,
SIGDN_DESKTOPABSOLUTEPARSING = 0x80028000,
SIGDN_PARENTRELATIVEEDITING = 0x80031001,
SIGDN_DESKTOPABSOLUTEEDITING = 0x8004c000,
SIGDN_FILESYSPATH = 0x80058000,
SIGDN_URL = 0x80068000
} SIGDN;
// Windows SDK 7.1A
typedef enum _SIGDN {
SIGDN_NORMALDISPLAY = 0,
SIGDN_PARENTRELATIVEPARSING = 0x80018001,
SIGDN_DESKTOPABSOLUTEPARSING = 0x80028000,
SIGDN_PARENTRELATIVEEDITING = 0x80031001,
SIGDN_DESKTOPABSOLUTEEDITING = 0x8004c000,
SIGDN_FILESYSPATH = 0x80058000,
SIGDN_URL = 0x80068000,
SIGDN_PARENTRELATIVEFORADDRESSBAR = 0x8007c001,
SIGDN_PARENTRELATIVE = 0x80080001
} SIGDN;
// Windows SDK 8.1
typedef enum _SIGDN {
SIGDN_NORMALDISPLAY = 0,
SIGDN_PARENTRELATIVEPARSING = 0x80018001,
SIGDN_DESKTOPABSOLUTEPARSING = 0x80028000,
SIGDN_PARENTRELATIVEEDITING = 0x80031001,
SIGDN_DESKTOPABSOLUTEEDITING = 0x8004c000,
SIGDN_FILESYSPATH = 0x80058000,
SIGDN_URL = 0x80068000,
SIGDN_PARENTRELATIVEFORADDRESSBAR = 0x8007c001,
SIGDN_PARENTRELATIVE = 0x80080001,
SIGDN_PARENTRELATIVEFORUI = 0x80094001
} SIGDN;
--
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.