https://bugs.winehq.org/show_bug.cgi?id=49301
Bug ID: 49301
Summary: pthread_exit hangs on unwind through
call_thread_exit_func on arm64
Product: Wine
Version: unspecified
Hardware: aarch64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: stefan(a)codeweavers.com
Distribution: ---
Created attachment 67309
--> https://bugs.winehq.org/attachment.cgi?id=67309
Workaround
My arm64 Wine build spins in services.exe after starting up anything. The
backtrace points into pthread_exit() - see attached file backtrace.txt.
I placed pthread_exit calls throughout the thread creation / shutdown code and
it works up to the point where signal_exit_thread() calls
call_thread_exit_func(). After call_thread_exit_func() passes control to the C
function exit_thread() pthread_exit() will hang.
I previously had this problem only in a gcc wine build (with 8fb8cc03
reverted), but recently, presumably after an update to clang-10, the problem
also happens when building Wine with clang. The attached backtrace is from a
build with clang 10.
Calling exit_thread() directly from signal_exit_thread() without going through
call_thread_exit_func works around the problem. See attached file noasm.diff
--
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=51187
Bug ID: 51187
Summary: Regression : Medal of Honor Allied Assault error after
upgrading from wine 5 -> 6.9
Product: Wine
Version: 6.9
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: cf91(a)protonmail.com
Distribution: ---
Created attachment 70059
--> https://bugs.winehq.org/attachment.cgi?id=70059
output
Hi,
I upgraded from stock wine on ubuntu to the repo release, and the game doesnt
start anymore, i formated and retried, even tried arch. I haven't been able to
get wine 6 to work with MoHAA. I have an nvidia GPU, and tried the tweaks
workarounds (registry patch + export __GL_ExtensionStringVersion=17700).
Here's a screenshot, I also attached more output https://imgur.com/Gk1Vgae
--
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=49378
Bug ID: 49378
Summary: kernel32.WriteFile with multi byte characters reports
incorrect number of written bytes
Product: Wine
Version: 5.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: suokkos(a)gmail.com
Distribution: ---
Created attachment 67438
--> https://bugs.winehq.org/attachment.cgi?id=67438
Wine test case to trigger the bug
Writing utf-8 multibyte characters to stdout using stdio led to uncovering this
bug. Attached test case is a simple way to trigger the underlying issue.
Minimal steps leading to issue:
1. Set console output to CP_UTF8
2. Use WriteFile with multibyte characters
Expect outcome:
WriteFile reports number of bytes written.
Actual outcome:
WriteFile reports number of characters written.
Other observations while writing test case:
I first run same test case using kernelbase.WriteFile. Base version seems to
behavior differently because my test case passed. I only then noticed the
important detail that there is multiple WriteFile entry points.
--
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=51170
Bug ID: 51170
Summary: Can't run at all the application
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gsbusy508(a)gmail.com
Created attachment 70039
--> https://bugs.winehq.org/attachment.cgi?id=70039
.
I want run a poker application, but when i use wine nothing happen at all.
Then I try to create the application with wine and i received this log problem.
Sorry to not be more clear, im new on this application.
--
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=45110
Bug ID: 45110
Summary: Crash when running courselab 2.4
Product: Wine
Version: 1.6.2
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: cjrw42(a)gmail.com
Distribution: ---
Created attachment 61295
--> https://bugs.winehq.org/attachment.cgi?id=61295
courselab 2.4 backtrace
I have installed courselab 2.4 (educational resource dev package which creates
HTML based sites), using the MSI, and all appears to have gone OK. Courselab
runs, grabs credentials, generates the licence key which is emailed and entered
fine, but as soon as you begin to create a new project it crashes out.
backtrace included.
--
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=40223
Bug ID: 40223
Summary: Mesa: User error: GL_INVALID_OPERATION in
glTexImage3D(bad target for depth texture)
Product: Wine
Version: 1.9.4
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ovariegata(a)yahoo.com
Distribution: Slackware
When starting the GOG version of Deus Ex with wine-staging 1.9.4 and a debug
version of mesa this error is printed several times.
Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth
texture)
Here is the full output:
$ deusex
preloader: Warning: failed to reserve range 00010000-00110000
preloader: Warning: failed to reserve range 00010000-00110000
fixme:winediag:start_process Wine Staging 1.9.4 is a testing version containing
experimental patches.
fixme:winediag:start_process Please mention your exact version when filing bug
reports on winehq.org.
preloader: Warning: failed to reserve range 00010000-00110000
preloader: Warning: failed to reserve range 00010000-00110000
preloader: Warning: failed to reserve range 00010000-00110000
preloader: Warning: failed to reserve range 00010000-00110000
preloader: Warning: failed to reserve range 00010000-00110000
fixme:module:load_dll Loader redirect from L"uxtheme.dll" to L"uxtheme-gtk.dll"
fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet
fixme:process:GetProcessWorkingSetSize (0xffffffff,0x32f314,0x32f30c): stub
Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth
texture)
Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth
texture)
Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth
texture)
Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth
texture)
Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth
texture)
Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth
texture)
Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth
texture)
Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth
texture)
Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth
texture)
Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth
texture)
Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth
texture)
Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth
texture)
Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth
texture)
Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth
texture)
Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth
texture)
Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth
texture)
Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth
texture)
Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth
texture)
Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth
texture)
Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth
texture)
err:ole:CoGetClassObject class {92fa2c24-253c-11d2-90fb-006008a1f441} not
registered
err:ole:CoGetClassObject no class object {92fa2c24-253c-11d2-90fb-006008a1f441}
could be created for context 0x1
err:ole:CoGetClassObject class {d8f1eee0-f634-11cf-8700-00a0245d918b} not
registered
err:ole:CoGetClassObject no class object {d8f1eee0-f634-11cf-8700-00a0245d918b}
could be created for context 0x1
fixme:winediag:IKsPropertySetImpl_QuerySupport EAX sound effects are enabled -
try to disable it if your app crashes unexpectedly
fixme:ddraw:ddraw7_FlipToGDISurface iface 0x16e2a8 stub!
OS: Slackware-current
Relevant packages:
wine-staging-1.9.4-x86_64-1_SBo
mesa-compat32-847f1cc_2015.12.16_master-x86_64-1_gitcompat32
libdrm-compat32-4274539_2016.02.26_master-x86_64-1_gitcompat32
--
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=43433
Bug ID: 43433
Summary: Sony Vegas Pro 8
Product: Wine
Version: 2.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: bameylan(a)bluewin.ch
Distribution: ---
Created attachment 58799
--> https://bugs.winehq.org/attachment.cgi?id=58799
Backtrace genered at the crash
This are the problems I encountered
I am using Linux Mint 18.2 x64.
I installed Sony Vegas Pro 8.0 on wine 2.13. Installation without problem.
But when I tried to run it, it stop at the moment that he "Adding GStreamer
AudioConvert filter"
--
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=50776
Bug ID: 50776
Summary: In Sketchup Make 2017, the display lags by one user
action.
Product: Wine
Version: 6.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: walt+wine(a)wzjz.us
Distribution: ---
In Sketchup Make 2017, open a 3D model. If you click on a face of the model,
the app should highlight it but it doesn't. If you click the same place again,
now it displays the highlight. You could also click one face, then click a
second face. After clicking the second face, the first face will be
highlighted.
I'm using nvidia-driver-460 if that matters.
--
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=49583
Bug ID: 49583
Summary: Assassin's Creed Odyssey displays black bars on top
and bottom.
Product: Wine
Version: 5.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: GloriousEggroll(a)gmail.com
Distribution: ---
Created attachment 67739
--> https://bugs.winehq.org/attachment.cgi?id=67739
AC Odyssey black bar fix
It's been a long known issue that AC: Odyssey renders with black bars on the
top and bottom of the screen (see screenshot 1).
Derek Lesho came up with a stub patch that both fixed this -and- allowed STEEP
to run (it would not display previously). That patch can be found here:
https://github.com/GloriousEggroll/proton-ge-custom/blob/5.12-GE-1/patches/…
Recently, the relevant function QueryDisplayConfig was implemented, however it
did not contain some of the changes Derek's patch adds. This allowed steep to
work, however AC: Odyssey still retained the black bar issue.
I modified Derek's patch by adding the relevant parts to QueryDisplayConfig,
and removing the relevant flag checks (Derek's patch did this previously), and
this allowed AC: Odyssey to render properly without the black bars. (see
screenshot 2). The patch is hacky but may provide more information towards
fixing this properly.
--
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.