Crash

Bug #2055006 reported by guillaume le louet
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu
Incomplete
Undecided
Unassigned

Bug Description

happens when I start wine.
Checked /var/log/syslog and noticed GNOME Shell crashed with signal 5

reproduction :
start wine. System slows, then crashes and asks me to relog .
After that extensions are disabled, same issue

I tried to change the nvidia drivers since there are some warning in dmesg

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8
Uname: Linux 6.5.0-21-generic x86_64
NonfreeKernelModules: 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.01.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 535.154.05 Thu Dec 28 15:37:48 UTC 2023
 GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Feb 26 07:32:22 2024
DistUpgraded: 2023-12-12 18:06:14,008 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GA104 [GeForce RTX 3070 Ti] [10de:2482] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd GA104 [GeForce RTX 3070 Ti] [1458:408f]
InstallationDate: Installed on 2022-12-22 (430 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic root=UUID=6bb46864-3883-4516-a1d5-eda3cd8908a7 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: Upgraded to mantic on 2023-12-12 (76 days ago)
dmi.bios.date: 11/15/2022
dmi.bios.release: 5.27
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F21
dmi.board.asset.tag: Default string
dmi.board.name: B660 GAMING X DDR4
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF21:bd11/15/2022:br5.27:svnMATERIEL.NET:pnBLACKBIRD:pvrV1:rvnGigabyteTechnologyCo.,Ltd.:rnB660GAMINGXDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuAR202209190058:
dmi.product.family: CMA
dmi.product.name: BLACKBIRD
dmi.product.sku: AR202209190058
dmi.product.version: V1
dmi.sys.vendor: MATERIEL.NET
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

Revision history for this message
guillaume le louet (guillaume-lelouet) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

CurrentDmesg.txt shows the Nvidia kernel driver crashing, which is probably not helpful. But also...

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

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.

summary: - Xorg crash
+ Crash
affects: xorg (Ubuntu) → ubuntu
Changed in ubuntu:
status: New → Incomplete
Revision history for this message
guillaume le louet (guillaume-lelouet) wrote :
Revision history for this message
guillaume le louet (guillaume-lelouet) wrote :
Revision history for this message
guillaume le louet (guillaume-lelouet) wrote :

I found several .crash files along with .upload and .uploaded files.
When trying to sudo ubuntu-bug _usr_lib_xorg_Xorg.0.crash
It crashed, too. I told it to "send a report"

I checked my recently sent bug reports. I believe it is
https://errors.ubuntu.com/oops/2a5a9e86-d46b-11ee-9d13-fa163ec44ecd
But I don't have the rights to see it.

Revision history for this message
guillaume le louet (guillaume-lelouet) wrote :

I think it's wine bug, I switched back to winehq-stable and it's gone.

I'm ready to make more tests if needed.

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

If 'ubuntu-bug' fails then try using 'apport-cli' to handle crash files instead.

The crash report you linked to is bug 1861609.

Revision history for this message
guillaume le louet (guillaume-lelouet) wrote :

thank you

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.