Ubuntu

crash post virtual box and wine installation

Bug #2066348 reported by Fayd'herbe on 2024-05-22

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

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Ubuntu	Incomplete	Undecided	Unassigned

Bug Description

slow

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.9-0ubuntu2.1
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
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed May 22 10:29:38 2024
DisplayManager: gdm3
InstallationDate: Installed on 2023-10-05 (229 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2)
RelatedPackageVersions: mutter-common 42.9-0ubuntu7.1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Fayd'herbe (alexisfaydherbe) wrote on 2024-05-22:

Dependencies.txt Edit (24.9 KiB, text/plain; charset="utf-8")
GsettingsChanges.txt Edit (2.8 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (310 bytes, text/plain; charset="utf-8")
ShellJournal.txt Edit (7.6 KiB, text/plain; charset="utf-8")

Daniel van Vugt (vanvugt) on 2024-05-27

affects:	gnome-shell (Ubuntu) → ubuntu
Changed in ubuntu:
status:	New → Incomplete

Revision history for this message

Launchpad Janitor (janitor) wrote on 2024-07-27:

[Expired for Ubuntu because there has been no activity for 60 days.]

Changed in ubuntu:
status:	Incomplete → Expired

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2024-07-29:

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.