https://bugs.winehq.org/show_bug.cgi?id=39663
Bug ID: 39663
Summary: GOG Galaxy slow to start (20 second delay)
Product: Wine
Version: 1.8-rc1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: abolte(a)systemsaviour.com
Distribution: ---
Created attachment 52879
--> https://bugs.winehq.org/attachment.cgi?id=52879
gog-galaxy-1.8-rc1-output.log
There is a 20+ delay starting GOG Galaxy. Confirming with 1.8-rc1, I believe
this has always been the case and is not a regression.
Specifically, you see the following output repeat every second for 20 seconds:
015-11-24 19:57:16 [galaxy_client][Information]: GalaxyCommunication started
properly.
2015-11-24 19:57:16 [galaxy_client][Information]: Exception during sending
request to service: Connection refused ()
fixme:process:WTSGetActiveConsoleSessionId stub
fixme:wtsapi:WTSQueryUserToken 1 0xfade7c
During this time, nothing seems to be happening. Then immediately after waiting
those 20 seconds, the Galaxy client seems to give up and continue anyway.
That's when you can see HDD activity actually start to kick in.
I am attaching the first 21+ seconds of console output when launching the
client, up until past the point of the delay. Let me know if you would like me
to recapture using any debug flags.
--
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=46520
Bug ID: 46520
Summary: Kindred Spirits on the Roof crashes
Product: Wine
Version: 4.0
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: msacm32
Assignee: wine-bugs(a)winehq.org
Reporter: zzhang(a)codeweavers.com
Distribution: ---
Created attachment 63377
--> https://bugs.winehq.org/attachment.cgi?id=63377
patch
One local driver can be assigned to multiple driver ids.
When releasing the driver id, check if the reference count
of a local driver is one before actually releasing the local driver.
related report: https://github.com/ValveSoftware/Proton/issues/210
--
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=45631
Bug ID: 45631
Summary: League client crashes
Product: Wine-staging
Version: 3.13
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ads200002(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
The League client tends to crash when queuing with premades. What logs can I
get to help diagnose this?
This is using Lutris' Wine Staging esync-3.13 (39cafb1) build found at
https://github.com/lutris/wine/commit/2da304b1195819d5df491d65c7ece1bc26e91…
and the Lutris installer (though I used a previous version that used a Wine
Staging with some custom League patches and then manually switched to the plain
Staging build): https://lutris.net/games/league-of-legends/
I'm sorry I can't provide a more vanilla example, League didn't run at all when
I tried to compile (on Ubuntu 18.04) a WoW64 build of Wine Staging master.
--
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=35516
Bug ID: 35516
Summary: Microworlds EX hangs when clicking toolbar button
Product: Wine
Version: 1.7.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: alkisg(a)gmail.com
Classification: Unclassified
Created attachment 47411
--> http://bugs.winehq.org/attachment.cgi?id=47411
Output of `bt all` when the problem happens
The program "Microworlds EX" hangs when I:
1) click on a toolbar button and hold the mouse button down,
2) move the mouse pointer anywhere outside the toolbar button, and then lift
the mouse button
To reproduce, install http://www.lcsi.ca/files/solutions/mwexdemo.exe, click
"Free mode" on the launcher, and then do the 2 steps mentioned above ^.
OS: Ubuntu Trusty 14.04
wine: 1.7.11-0ubuntu1~saucy1 (from wine PPA)
The issue happens with any Microworlds/Wine/Ubuntu versions we've tried, even
really old versions of them, and on whatever PCs.
In doesn't hang in any Windows versions that we've tried.
--
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=46442
Bug ID: 46442
Summary: FormatCurrency(9) returns .9.00 (period in front)
Product: Wine
Version: 4.0-rc5
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: wine(a)londonlight.org
Distribution: ---
Created attachment 63224
--> https://bugs.winehq.org/attachment.cgi?id=63224
compiled executable
Reproduced in wine-3.0.4 in Linux Mint, wine-3.18-staging in Sabayon (from its
package manager) as well as self-compiled (vanilla) wine-3.21-298-ge9231beb86
and wine-4.0-rc5-14-g0ff7fd1259
FormatCurrency(9) returns ".9.00", notice the period in the front.
Therefore, FormatCurrency(FormatCurrency(9)) will segfault.
Why does it add the period there?
Compiled exe attached, source code zipped and attached in next comment.
Steps:
1. Get winetricks:
wget
https://raw.githubusercontent.com/Winetricks/winetricks/master/src/winetric…
2. Install vb6run:
WINEARCH=win32 WINEPREFIX="$HOME/wine-ct" ~/winetricks vb6run
3. Run currencytest.exe
LC_ALL="en_US.utf8" WINEPREFIX="$HOME/wine-ct" currencytest.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=45473
Bug ID: 45473
Summary: Rogue Squadron 3D crashes on startup
Product: Wine
Version: 3.12
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-dsound
Assignee: wine-bugs(a)winehq.org
Reporter: leslie_alistair(a)hotmail.com
Distribution: ---
Created attachment 61818
--> https://bugs.winehq.org/attachment.cgi?id=61818
Dont destroy secondarybuffer in IDirectSoundNotify
Rogue Squadron 3D crashes on startup unless native dsound is used
--
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=46691
Bug ID: 46691
Summary: comctl32/tests/propsheet.c shows uninitalized memory
use
Product: Wine
Version: 4.2
Hardware: x86
OS: Linux
Status: NEW
Keywords: download, source, testcase, valgrind
Severity: normal
Priority: P2
Component: comctl32
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
CC: bunglehead(a)gmail.com
Distribution: Gentoo
../../../tools/runtest -q -P wine -T ../../.. -M comctl32.dll -p
comctl32_test.exe.so propsheet && touch propsheet.ok
==30493== Syscall param write(buf) points to uninitialised byte(s)
==30493== at 0x4253C7F: write (write.c:27)
==30493== by 0x7BC75AAB: send_request (server.c:213)
==30493== by 0x7BC767F0: server_call_unlocked (server.c:288)
==30493== by 0x7BC76845: wine_server_call (server.c:321)
==30493== by 0x4FA5FFD: PostQuitMessage (message.c:3762)
==30493== by 0x5975F8E: do_loop (propsheet.c:2781)
==30493== by 0x5976031: PROPSHEET_PropertySheet (propsheet.c:2815)
==30493== by 0x5976612: PropertySheetA (propsheet.c:2865)
==30493== by 0x4AE4E8F: test_bad_control_class (propsheet.c:1167)
==30493== by 0x4AE82D7: func_propsheet (propsheet.c:1208)
==30493== by 0x4B2C64C: run_test (test.h:617)
==30493== by 0x4B2D08A: main (test.h:701)
==30493== Address 0x4c6fb58 is on thread 1's stack
==30493== in frame #4, created by PostQuitMessage (message.c:3758)
==30493== Uninitialised value was created by a stack allocation
==30493== at 0x5975EC4: do_loop (propsheet.c:2762)
==30493==
--
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=46493
Bug ID: 46493
Summary: Functions ilogb* are not implemented
Product: Wine
Version: 4.0-rc7
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: msvcrt
Assignee: wine-bugs(a)winehq.org
Reporter: bunglehead(a)gmail.com
Distribution: ---
Created attachment 63331
--> https://bugs.winehq.org/attachment.cgi?id=63331
patch
This was reported via #winehq, application name wasn't mentioned.
--
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=46485
Bug ID: 46485
Summary: clrmamepro: crash when loading datfiles which contains
release elements
Product: Wine
Version: 4.0-rc7
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: comctl32
Assignee: wine-bugs(a)winehq.org
Reporter: tomgpdev(a)gmail.com
Distribution: ---
Created attachment 63322
--> https://bugs.winehq.org/attachment.cgi?id=63322
Crafted .dat file and the crash backtrace
The app crashes when trying to load LogiqX .DAT files which has "release"
elements inside the "game" elements. From the stack trace, it see something
about comctl32, but I don't know the reason about the crash itself.
For you to trigger the crash, I crafted an example .dat file. Here's the
procedure:
1. Download clrmame pro.
2. Copy the crash.dat file inside its datfiles dir.
3. Run clrmame pro.
4. Click OK in the welcome screen.
5. In [NEW DATAFILES], double click on "Crash test".
6. Click on "Default".
7. The crash should happen.
I checked on Windows 10 that it loads the crafted crash.dat file attached to
this bug report without crashing.
AppDB link:
https://appdb.winehq.org/objectManager.php?sClass=application&iId=5692
Program version: 4.035 64 bits
--
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=23863
Summary: The Bard's Tale (2005): unplayable due to almost
completely black screen
Product: Wine
Version: 1.3.0
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: gyebro69(a)gmail.com
Created an attachment (id=29959)
--> (http://bugs.winehq.org/attachment.cgi?id=29959)
terminal output (without any dll overrides)
After starting The Bard's Tale (published in 2005 by inXile Entertainment) the
screen in the menus is way too dark, so you can see almost nothing, unless you
turn up the gamma of the screen. The animated hero is also missing on the left
side of the screen, when you choose to generate a new character.
The biggest problem that makes the game unplayable is when you start a new
game, almost the whole screen is black, only the mini-map is shown in the
upper-right corner, and the health bar in the upper-left corner. Besides only
subtitles are shown. Majority of the screen is pure black.
This bug affects at least the Steam version of the game, but according to AppDB
the retail (DVD version) is also affected:
http://appdb.winehq.org/objectManager.php?sClass=version&iId=4041
I tried out several Wine versions but all of them showed the same issue,
including 1.1.0 which received Gold rating on AppDB.
However, the demo version of the game has no such issues: it displays
everything correctly, from the menus to the actual gameplay.
The only difference between the terminal output of the demo (working one) and
the retail version is the following line (repeated several times) when playing
the retail version:
'fixme:d3d:buffer_PreLoad Too many full buffer conversions, stopping
converting'
Wine-1.3.0
Fedora 13
Nvidia 7600 GT card / driver 195.36.31
--
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.