http://bugs.winehq.org/show_bug.cgi?id=35294
Bug ID: 35294
Summary: Window borders shown over other windows
Product: Wine
Version: 1.7.9
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: p91paul(a)gmail.com
Classification: Unclassified
Created attachment 47074
--> http://bugs.winehq.org/attachment.cgi?id=47074
Opened Line window on top
Workflow: open a Line (http://line.naver.jp/en/) chat window. (window.png
attachment)
Switch to another window, so that the line window moves back.
Line window borders will remain visible(borders.png attachment: watch were
there was the window in window.png, you will see the borders)
I'm also unable to minimize the window, the button does nothing. The bug is
reproducible with "Allow window manager to manage the windows" checked; if I
uncheck it before launching wine, simply Line window stays over all other
windows (you will stay in the situation of window.png also if you focus another
window).
Running cinnamon on 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=46964
Bug ID: 46964
Summary: Port Royale 3 Pirates and Merchants: In-game error
starting game
Product: Wine
Version: 4.5
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: odecif(a)gmail.com
Distribution: ---
Created attachment 64115
--> https://bugs.winehq.org/attachment.cgi?id=64115
Debug log
Installing the game works fine
Winetricks dotnet30 is executed
When launching the game a popup show saying
"Internal error"
"App.cpp(1159): Error in 'App::Initialize':"
"Launcher failed return code: -5:0xfffffffb"
Clean wine prefix.
Attached you may find debug log.
This game runs fine in wine-3.0 but not wine-3.20
If there is anything missing and needed, please let me know and I'll do my best
o aid.
--
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=47608
Bug ID: 47608
Summary: SmartGames Stratajams: Required resolution not found,
need at least 638 by 478
Product: Wine
Version: 4.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: odecif(a)gmail.com
Distribution: ---
Created attachment 65034
--> https://bugs.winehq.org/attachment.cgi?id=65034
warn+all debug log
When launching the game SmartGames Stratajams, the game throws an error saying
"Required resolution not found. This program requires a resolution of at least
638 by 478. Please refer to the "Troubleshooting" section of the product manual
or on-line help".
Attached is is a log of warn+all.
--
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=15505
Summary: STM_SETIMAGE does not handle bitmaps with alpha
correctly
Product: Wine
Version: 1.1.5
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P2
Component: user32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: thestig(a)google.com
In XP, STM_SETIMAGE makes a copy of bitmaps with alpha, which allows
applications to delete the bitmaps they passed in. Many programmers expect this
as the default behavior, since they don't test on older Windows platforms.
Our STM_SETIMAGE implementation still follows the pre-XP behavior, which may
cause rendering problems for apps that use STM_SETIMAGE extensively.
I don't have a minimal test case just yet...
--
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=43347
Bug ID: 43347
Summary: valgrind shows an unintialized read in
dlls/iphlpapi/tests/iphlpapi.c
Product: Wine
Version: 2.12
Hardware: x86
OS: Linux
Status: NEW
Keywords: download, source, testcase, valgrind
Severity: normal
Priority: P2
Component: iphlpapi
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Distribution: Gentoo
../../../tools/runtest -q -P wine -T ../../.. -M iphlpapi.dll -p
iphlpapi_test.exe.so iphlpapi && touch iphlpapi.ok
==10952== Syscall param ioctl(SIOCGIFINDEX) points to uninitialised byte(s)
==10952== at 0x4338F79: ioctl (syscall-template.S:84)
==10952== by 0x435916D: if_nametoindex (if_index.c:47)
==10952== by 0x4B25E43: getInterfaceIndexByName (ifenum.c:143)
==10952== by 0x4B2EC7E: IPHLP_if_nametoindex (iphlpapi_main.c:3233)
==10952== by 0x488198E: test_interface_identifier_conversion
(iphlpapi.c:1958)
==10952== by 0x48831AB: func_iphlpapi (iphlpapi.c:2230)
==10952== by 0x4884014: run_test (test.h:603)
==10952== by 0x4884465: main (test.h:687)
==10952== Address 0x4b0f8c0 is on thread 1's stack
==10952== in frame #1, created by if_nametoindex (if_index.c:35)
==10952== Uninitialised value was created by a stack allocation
==10952== at 0x4359141: if_nametoindex (if_index.c:41)
==10952==
--
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=44337
Bug ID: 44337
Summary: d3d9/tests/device.ok fails on Nvidia (Nouveau drivers)
in test_occlusion_query()
Product: Wine
Version: 3.0-rc5
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: z.figura12(a)gmail.com
Distribution: ---
with the following lines:
device.c:5915: Test failed: Got unexpected hr 0x1.
device.c:5919: Test failed: Got unexpected hr 0x1.
device.c:5920: Test failed: Got unexpected query result 0xffffffffffffffff.
It would be nice to fix this as this is currently the only D3D test failure on
the cw2 test machine.
--
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=35765
Bug ID: 35765
Summary: gdi32:font / richedit:editor / msvcrt:locale /
msvcrt:string fails on newtb-w7u
Product: Wine
Version: 1.7.14
Hardware: x86
OS: Linux
Status: NEW
Keywords: source, testcase
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fracting(a)gmail.com
CC: fgouget(a)codeweavers.com
http://test.winehq.org/data/770213e16c6918728f69ea33545fafabd59dbc8e/win7_n…
It seems these tests are all related to locales, and they fail much more on
this machine than other machine.
SystemDefaultLCID 411
UserDefaultLCID 409
ThreadLocale 411
UserDefaultUILanguage 411
ThreadUILanguage 411
It doesn't happen frequently that we have a vm with different UserDefaultLCID
and SystemDefaultLCID. I'm not very sure if we want to support such a case, it
maybe useful in real world for some body. (I personally don't care too much
lol)
François, is there any chance to try:
1. set all LCIDs to 0x409 (Simplified Chinese)
2. set all LCIDs to 0x411 (Japanese)
Then reboot the vm, then resubmit the tests, to see if there is any
improvement?
Thanks for your great work! Everyone wants your patch/work :)
--
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=32083
Bug #: 32083
Summary: Diablo III: Missing logo on startup
Product: Wine
Version: 1.5.16
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: sworddragon2(a)aol.com
Classification: Unclassified
On starting Diablo III the logo before the game starts is transparent. If I'm
going with the mouse over it the cursor will be hidden.
--
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.