Closing Sims 4 kills Xephyr

Bug #2067121 reported by Ken Sharp

This bug report will be marked for expiration in 37 days if no further activity occurs. (find out why)

8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Running Sims 4 with Wine 9.9 and VGL works surprisingly well, but on exiting the game everything (Xephyr, marco, EA App and all related processes) is instantly killed except for a CEF process and some Wine background tasks. The CEF process runs at around 120% and has to be killed.

I'm often told that Wine cannot kill a desktop environment so there must be a bug in one of the components in-between. It is, of course, possible that Wine does have a bug that triggers the issue also, but there's nothing in the console log from Wine that suggests what that might be.

In host user (me) session:

$ xhost +si:localuser:test
$ Xephyr :666 -screen 1024x768

In "test" session:

$ DISPLAY=:666 vglrun -d :0 marco
$ DISPLAY=:666 vglrun -d :0 wine 'c:\ProgramData\Microsoft\Windows\Start Menu\Programs\EA\EA.lnk'

And from there
1. Log in.
2. Run Sims 4.
3. Click X in the window manager (of the Sims 4 app, not the Xephyr window).

X connection to :666 broken (explicit kill or server shutdown).
0030:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFA, 0051FECC
free(): corrupted unsorted chunks

"winetricks arial" required to get this far, but no other workarounds used.

So far I have not seen this occur in any other app.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xserver-xephyr 2:21.1.4-2ubuntu1.7~22.04.10
ProcVersionSignature: Ubuntu 6.5.0-35.35~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-35-generic x86_64
NonfreeKernelModules: zfs nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus.0000.04.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.239.06 Sat Feb 3 06:03:07 UTC 2024
 GCC version: gcc version 12.3.0 (Ubuntu 12.3.0-1ubuntu1~22.04)
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: MATE
Date: Sat May 25 00:47:39 2024
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 nvidia/470.239.06, 6.5.0-28-generic, x86_64: installed
 nvidia/470.239.06, 6.5.0-35-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GK104GL [Quadro K5000] [10de:11ba] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: NVIDIA Corporation GK104GL [Quadro K5000] [10de:0965]
MachineType: LENOVO 0606AD5
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-35-generic root=UUID=83ed7b7f-ef51-49d7-a6be-a8efee1cdd32 ro rootflags=subvol=@ quiet splash vt.handoff=7
SourcePackage: xorg-server
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/15/2016
dmi.bios.release: 0.60
dmi.bios.vendor: LENOVO
dmi.bios.version: A0KT60AUS
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: LENOVO
dmi.board.vendor: LENOVO
dmi.board.version: NONE
dmi.chassis.type: 7
dmi.chassis.vendor: LENOVO
dmi.chassis.version: NONE
dmi.modalias: dmi:bvnLENOVO:bvrA0KT60AUS:bd12/15/2016:br0.60:svnLENOVO:pn0606AD5:pvrThinkStationS30:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct7:cvrNONE:skuLENOVO_BI_A0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: 0606AD5
dmi.product.sku: LENOVO_BI_A0
dmi.product.version: ThinkStation S30
dmi.sys.vendor: LENOVO
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2019-08-06T11:56:22.315382
version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.10
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

Revision history for this message
Ken Sharp (kennybobs) wrote :
Revision history for this message
Ken Sharp (kennybobs) wrote :
Revision history for this message
Ken Sharp (kennybobs) wrote :
Revision history for this message
Ken Sharp (kennybobs) wrote :

From my syslog:

May 25 00:58:43 ken whoopsie[533235]: [00:58:43] Parsing /var/crash/_opt_wine-devel_bin_wine64-preloader.1001.crash.
May 25 00:58:46 ken whoopsie[533235]: [00:58:46] Uploading /var/crash/_opt_wine-devel_bin_wine64-preloader.1001.crash.
May 25 00:58:47 ken whoopsie[533235]: [00:58:47] Sent; server replied with: No error
May 25 00:58:47 ken whoopsie[533235]: [00:58:47] Response code: 200
May 25 00:58:47 ken whoopsie[533235]: [00:58:47] Reported OOPS ID 8ef87a8a-1a29-11ef-bb9d-fa163e171f02

So someone with access should be able to grab the OOPS report?

description: updated
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

https://errors.ubuntu.com/oops/8ef87a8a-1a29-11ef-bb9d-fa163e171f02 just shows /opt/wine-devel/bin/wine64-preloader has crashed when running C:\\Program\ Files\\EA\ Games\\The\ Sims\ 4\\Game\\Bin\\TS4_x64.exe so that's not really the main issue even if it was the trigger. We need to look for other crashes so please follow these steps next time the problem occurs:

1. Run these commands:
    journalctl -b0 > journal.txt
    journalctl -b-1 > prevjournal.txt
and attach the resulting text files here.

2. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

Changed in xorg-server (Ubuntu):
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.