You are not logged in.
Whenever i try to run some application through wine i get this error:
wine: created the configuration directory '/home/ender/.wine'
002c:err:seh:NtRaiseException Unhandled exception code c0000005 flags 0 addr 0x6fffffc0db3f
wine: could not load kernel32.dll, status c000013
This issue has been occurring since wine 10.9-1.
when i do
WINEDEBUG=+heap winecfg
it seems like it's doing something but just gets stuck at the creating prefix pop up window
I am using the linux-zen kernel version 6.15.6
lscpu:
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 36 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 2
On-line CPU(s) list: 0,1
Vendor ID: GenuineIntel
Model name: Intel(R) Pentium(R) CPU B960 @ 2.20GHz
CPU family: 6
Model: 42
Thread(s) per core: 1
Core(s) per socket: 2
Socket(s): 1
Stepping: 7
CPU(s) scaling MHz: 93%
CPU max MHz: 2200.0000
CPU min MHz: 800.0000
BogoMIPS: 4390.05
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmo
n pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt
tsc_deadline_timer xsave lahf_lm epb pti xsaveopt dtherm arat pln pts
Caches (sum of all):
L1d: 64 KiB (2 instances)
L1i: 64 KiB (2 instances)
L2: 512 KiB (2 instances)
L3: 2 MiB (1 instance)
NUMA:
NUMA node(s): 1
NUMA node0 CPU(s): 0,1
Vulnerabilities:
Gather data sampling: Not affected
Ghostwrite: Not affected
Indirect target selection: Not affected
Itlb multihit: KVM: Mitigation: VMX unsupported
L1tf: Mitigation; PTE Inversion
Mds: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled
Meltdown: Mitigation; PTI
Mmio stale data: Unknown: No mitigations
Reg file data sampling: Not affected
Retbleed: Not affected
Spec rstack overflow: Not affected
Spec store bypass: Vulnerable
Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Spectre v2: Mitigation; Retpolines; STIBP disabled; RSB filling; PBRSB-eIBRS Not affected; BHI Not affected
Srbds: Not affected
Tsa: Not affected
Tsx async abort: Not affected
pacman -Qikk wine:
wine: 3939 total files, 0 altered files
Last edited by voldemort (2025-09-06 06:19:14)
Offline
I am using the linux-zen kernel version 6.15.6
Does this also occur with linux & linux-lts ?
Create a test user , perform minimal configuration.
Does this user also get the error ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
I am using the linux-zen kernel version 6.15.6
Does this also occur with linux & linux-lts ?
Create a test user , perform minimal configuration.
Does this user also get the error ?
Yup, this error still happens in linux and linux-lts, and the test user also gets this error
Offline
Are you running X or wayland ?
Which window manager / desktop environment / compositor and what are you using to start the gui ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Are you running X or wayland ?
Which window manager / desktop environment / compositor and what are you using to start the gui ?
I am using X and i used awesome to start the gui but i have also tried running wine under wayland on hyprland it still doesnot work
Offline
So the cause is not in those.
I'm beginning to think that the cause is in wine itself and the only way to find it is bisecting wine .
Before going into that we need to be sure that no other factors are involved .
Please downgrade only wine to 10.8-2 to verify that is enough to make things work.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
So the cause is not in those.
I'm beginning to think that the cause is in wine itself and the only way to find it is bisecting wine .
Before going into that we need to be sure that no other factors are involved .
Please downgrade only wine to 10.8-2 to verify that is enough to make things work.
I can confirm wine 10.8-2 works as intended
Offline
Great, that gives a known bad and good point.
Read Bisecting bugs with git .
Do you have experience with building from sourcecode and how powerful is your hardware (laptop or desktop, processor model, amount of memory) ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Great, that gives a known bad and good point.
Read Bisecting bugs with git .
Do you have experience with building from sourcecode and how powerful is your hardware (laptop or desktop, processor model, amount of memory) ?
I don't have much experience building from source code.
My laptop is not very powerful like 8gigs of ram, an intel b960 and integrated graphics
Last edited by voldemort (2025-07-22 10:41:51)
Offline
Ok, then I'll do the building part.
Setting things up now.
Added
$ git bisect start
status: waiting for both good and bad commits
$ git bisect good 7f833db11ffea4f3f4fa07be31d30559aff9c5fb
status: waiting for bad commit, 1 good commit known
[panoramix@silverbolt wine]$ git bisect bad ffcbbf8f0152cd6919eabe19f0a9d5e015fe1a80
Bisecting: 133 revisions left to test after this (roughly 7 steps)
[e834740e44669e43985da74141d5b713c847a874] win32u: Implement OpenGL pixel formats over EGL configs.
$ Download the binary package for that revision from https://app.box.com/s/1n8ztsq6l6gbtm87t8gt2pze7w913d4u .
install with pacman -U and test it.
Last edited by Lone_Wolf (2025-07-22 11:59:17)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Ok, then I'll do the building part.
Setting things up now.
Added
$ git bisect start status: waiting for both good and bad commits $ git bisect good 7f833db11ffea4f3f4fa07be31d30559aff9c5fb status: waiting for bad commit, 1 good commit known [panoramix@silverbolt wine]$ git bisect bad ffcbbf8f0152cd6919eabe19f0a9d5e015fe1a80 Bisecting: 133 revisions left to test after this (roughly 7 steps) [e834740e44669e43985da74141d5b713c847a874] win32u: Implement OpenGL pixel formats over EGL configs. $Download the binary package for that revision from https://app.box.com/s/1n8ztsq6l6gbtm87t8gt2pze7w913d4u .
install with pacman -U and test it.
The binary that you provided is working
Offline
I think this was already bisected. https://bugs.winehq.org/show_bug.cgi?id=58335#c97
Offline
That bisect was done with a Core2 Quad Q9550 from 2008 / yorkfield generation while the intel b960 used by voldemort is from 2011 / SandyBridge .
I think that's enough of a difference to continue bisecting, but it's voldemorts decision .
$ git bisect good e834740e44669e43985da74141d5b713c847a874
Bisecting: 66 revisions left to test after this (roughly 6 steps)
[8148f4e47d2b86a3cc03760f38326fd41db33f17] ntdll: Implement RtlCreateServiceSid.
$ Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
That bisect was done with a Core2 Quad Q9550 from 2008 / yorkfield generation while the intel b960 used by voldemort is from 2011 / SandyBridge .
I think that's enough of a difference to continue bisecting, but it's voldemorts decision .
$ git bisect good e834740e44669e43985da74141d5b713c847a874 Bisecting: 66 revisions left to test after this (roughly 6 steps) [8148f4e47d2b86a3cc03760f38326fd41db33f17] ntdll: Implement RtlCreateServiceSid. $
This is where it seems to stop working
002c:err:seh:NtRaiseException Unhandled exception code c0000005 flags 0 addr 0x6fffffc0daf6
wine: could not load kernel32.dll, status c0000135Last edited by voldemort (2025-07-22 14:26:08)
Offline
Each revision we test reduces the range of potential causes (commits) by 50% so it gets smaller with every bisect test.
Once the size gets to 1 we'll know which commit introduced the problem.
$ git bisect bad 8148f4e47d2b86a3cc03760f38326fd41db33f17
Bisecting: 33 revisions left to test after this (roughly 5 steps)
[4b4a47ac8d76a9117fed20b899c1bd1817436329] wintypes: Implement IReference<FLOAT>.
$Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Each revision we test reduces the range of potential causes (commits) by 50% so it gets smaller with every bisect test.
Once the size gets to 1 we'll know which commit introduced the problem.$ git bisect bad 8148f4e47d2b86a3cc03760f38326fd41db33f17 Bisecting: 33 revisions left to test after this (roughly 5 steps) [4b4a47ac8d76a9117fed20b899c1bd1817436329] wintypes: Implement IReference<FLOAT>. $
The binary that you provided is working
Offline
$ git bisect good 4b4a47ac8d76a9117fed20b899c1bd1817436329
Bisecting: 16 revisions left to test after this (roughly 4 steps)
[122144b6fadc3b590852ea2e0e11eec12f9b7432] wintypes: Implement IReference<Size>.
$Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
$ git bisect good 4b4a47ac8d76a9117fed20b899c1bd1817436329 Bisecting: 16 revisions left to test after this (roughly 4 steps) [122144b6fadc3b590852ea2e0e11eec12f9b7432] wintypes: Implement IReference<Size>. $
Working
Offline
$ git bisect good 122144b6fad
Bisecting: 8 revisions left to test after this (roughly 3 steps)
[6b65ae4e9bab070694e932d6c2120726088fb1a7] ntdll: Check processor features from the user shared data.
$wine-git-10.8.r192.g6b65ae4e9ba-1-x86_64.pkg.tar.zst
Please don't quote full posts, only quote relevant parts . (for this bisect the package name is enough).
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
wine-git-10.8.r192.g6b65ae4e9ba-1-x86_64.pkg.tar.zst
Not working
Offline
$ git bisect bad 6b65ae4e9ba
Bisecting: 3 revisions left to test after this (roughly 2 steps)
[beddc6f22c7e51c2e796c648d5a31e52766783ac] ntdll: Fetch the XState features mask from the user shared data.
$ Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
wine-git-10.8.r188.gbeddc6f22c7-1-x86_64.pkg.tar.zst
Not working
Offline
We're almost there.
$ git bisect bad beddc6f22c7
Bisecting: 1 revision left to test after this (roughly 1 step)
[d9172b0acf052d0f3c087a9f5f5ece29cd917c55] ntdll: Avoid excessive committed range scan in NtProtectVirtualMemory().
$ Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
wine-git-10.8.r186.gd9172b0acf0-1-x86_64.pkg.tar.zst
Working
Offline
$ git bisect good d9172b0acf0
Bisecting: 0 revisions left to test after this (roughly 0 steps)
[745a11a231816a7d82490156c72a18c39216a14c] ntdll: Fetch the XState supported features mask from the user shared data.
$ Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline