http://bugs.winehq.org/show_bug.cgi?id=13656
Summary: Testout navigator does not dispaly menus or vodeo
correctly
Product: Wine
Version: 1.0-rc2
Platform: Other
OS/Version: other
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: keith_kw_muir(a)blueyonder.co.uk
Testout navigator Starts but grey pane where the course video would play and
the menu bar is empty.
--
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=40283
Bug ID: 40283
Summary: Cheat Engine Access Violation
Product: Wine
Version: 1.8.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: pavluk6(a)mail.ru
Distribution: ---
You still can edit applications' data, but speedhack doesn't works (DLL
injection failed)
--
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=48668
Bug ID: 48668
Summary: rFactor2 - Physics thread slower on multiplayer mode
Product: Wine
Version: 5.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: alex.brrsclnt(a)gmail.com
Distribution: Ubuntu
Created attachment 66525
--> https://bugs.winehq.org/attachment.cgi?id=66525
Steam rfactor2 proton log
This bug is created after the one that exists in the Proton github issue
tracker
https://github.com/ValveSoftware/Proton/issues/245
The game runs fine in single player mode since version 4.11 to the newest
versions of Proton, but there is a problem in multiplayer mode that makes the
game run slower.
We have asked to the game devs in their discord server for some info, try to
get some logs of the multiplayer execution, and finally, one dev told us that
despite the graphics thread was fine, there is something wrong affecting to the
physics thread in the game, and this only happens in online races, so the issue
may be in the network code of Proton/Wine. (@leillo1975 tried to run the game
in vanilla Wine, and the problem was also there).
Is there any way to trace the network execution to find what could be the
problem?
I added a log file in the proton issue tracker generated running the game with
the "PROTON_LOG=1 %command%" but don't know if that contains enough
information.
Let me know if I can add any other info.
Thanks!
--
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=38409
Bug ID: 38409
Summary: Wine Task Tray does is not in the taskbar KDE 5
Product: Wine
Version: 1.7.40
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jack(a)emoss.org
Distribution: ---
The wine System Tray is not linked to the KDE desktop at all in KDE 5 but it
worked fine in KDE 4.
--
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=45364
Bug ID: 45364
Summary: Frostpunk
Product: Wine
Version: 3.10
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: hewanci(a)gmail.com
Distribution: ---
Frostpunk is so dark that it's unplayable due to not being able to see what's
happening.
Steam version
Staging 3.10
Arch Linux
There is already a bug about glitches but I doN't know how related that is: bug
45098
--
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=17638
Summary: NOLF GotY: Sluggish mouse reaction when in zoom mode
Product: Wine
Version: 1.1.16
Platform: PC-x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: liquid.acid(a)gmx.net
CC: jb.faq(a)gmx.de
Mouse input in NOLF is generally a bit "inprecise", but one thing is broken for
sure.
Some weapons feature a zoom mode, but when this zoom mode is switched on it's
almost impossible to accurately use it since the mouse input becomes very
sluggish then. Turn zoom off again and mouse input stabilizes again.
I suppose that's a dinput problem, but I'm not sure about that.
The wine-0.9.46 testresult here
(http://appdb.winehq.org/objectManager.php?sClass=version&iId=305&iTestingId…)
mentions a "weird mouse problem", but I'm not sure if that's what I'm
encountering.
Haven't tried any native DLLs though.
--
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=31157
Bug #: 31157
Summary: Filemaker Pro 12 Trial crashes
Product: Wine
Version: 1.2.3
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: maikwagner(a)yahoo.com
Classification: Unclassified
Created attachment 40903
--> http://bugs.winehq.org/attachment.cgi?id=40903
Crash Output on Filemaker 12
I would like to report some issues with Filemaker 12 Trial which can be
downloaded from Filemaker.com.
The application installs okay and I can start "Filemaker 12" from the command
line. When opening a sample solution (I selected "Invoices") the application
crashes. I have attached my console output.
--
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=30666
Bug #: 30666
Summary: MPEG movie does not play in Capitalism 2 demo
Product: Wine
Version: 1.5.4
Platform: x86
URL: http://www.cnwcentral.com/capitalism-2/demo.shtml
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winegstreamer
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jeremielapuree(a)yahoo.fr
Classification: Unclassified
Created attachment 40144
--> http://bugs.winehq.org/attachment.cgi?id=40144
console output
While playing intro movie of Capitalism 2 demo, one can hear the sound, but
video is playing.
--
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=48209
Bug ID: 48209
Summary: Ignore random parts of test failure messages
Product: Wine-Testbot
Version: unspecified
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
The TestBot needs to detect if a patch introduces NEW test failures. To do so
it compares the failure messages with those from reference WineTest runs. But
in some cases part of the message changes from one run to the next, causing the
failure to look new.
Of course in all cases the ideal solution is to fix the test so it does not
fail.
Barring that there are also cases where the varying value is not really useful
(e.g. handle or pointer values) and in that case it should just be removed from
the message.
But there may be cases where knowing the value is still useful. So one solution
would be to tag such values so the TestBot knows it can ignore them when
comparing failure messages. For instance they could be enclosed in double
braces, curly braces, or other.
--
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=36103
Bug ID: 36103
Summary: kernel32/tests/loader shows lots of invalid reads in
thread.c
Product: Wine
Version: 1.7.17
Hardware: x86
OS: Linux
Status: NEW
Keywords: download, testcase
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
==9219== Invalid read of size 4
==9219== at 0x7BC55D91: MODULE_DllThreadAttach (loader.c:1287)
==9219== by 0x7BC8E3D2: start_thread (thread.c:423)
==9219== by 0x4218F92: start_thread (pthread_create.c:309)
==9219== by 0x431D7ED: clone (clone.S:129)
==9219== Address 0x611eb04 is on thread 1's stack
==9219==
==9219== Invalid read of size 4
==9219== at 0x7BC1EAF3: __x86.get_pc_thunk.bx (in
/home/austin/wine-valgrind/dlls/ntdll/ntdll.dll.so)
==9219== by 0x7BC8E3D2: start_thread (thread.c:423)
==9219== by 0x4218F92: start_thread (pthread_create.c:309)
==9219== by 0x431D7ED: clone (clone.S:129)
==9219== Address 0x611eacc is on thread 1's stack
==9219==
there's also one:
==30099== 2,020 bytes in 1 blocks are possibly lost in loss record 225 of 244
==30099== at 0x7BC4C735: notify_alloc (heap.c:255)
==30099== by 0x7BC50F79: RtlAllocateHeap (heap.c:1716)
==30099== by 0x4E07A19: get_tls_data (test.h:244)
==30099== by 0x4E07B03: winetest_set_location (test.h:279)
==30099== by 0x4D836B8: dll_entry_point (loader.c:1433)
==30099== by 0x7BC52FC0: ??? (loader.c:138)
==30099== by 0x7BC555FE: MODULE_InitDLL (loader.c:1068)
==30099== by 0x7BC55DE7: MODULE_DllThreadAttach (loader.c:1281)
==30099== by 0x7BC8E446: start_thread (thread.c:423)
==30099== by 0x4EA7BD89: start_thread (in /usr/lib/libpthread-2.18.so)
==30099== by 0x4E95CA0D: clone (in /usr/lib/libc-2.18.so)
==30099==
--
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.