Bug in window manager: Failed to find destination workspace in layout ; GNOME Shell crashed with signal 6
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gnome-shell (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
After closing Clion, which was installed as a snap, the gnome desktop environment crashed.
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.2-0ubuntu0.2
ProcVersionSign
Uname: Linux 5.15.0-
NonfreeKernelMo
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul 19 11:36:00 2022
DisplayManager: gdm3
ExecutablePath: /usr/bin/
ExecutableTimes
GsettingsChanges:
InstallationDate: Installed on 2022-05-08 (72 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
ProcCmdline: /usr/bin/
ProcCwd: /home/gregorio
ProcEnviron:
LANG=pt_BR.UTF-8
LANGUAGE=
PATH=(custom, user)
SHELL=/bin/bash
XDG_RUNTIME_
RelatedPackageV
Signal: 6
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
modified.
mtime.conffile.
| Gregório Assagra de Almeida Filho (galdutro) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| information type: | Private → Public |
| tags: | removed: need-amd64-retrace |
| Daniel van Vugt (vanvugt) wrote Re: Gnome crashed after closing CLion IDE | #3 |
| Daniel van Vugt (vanvugt) wrote | #4 |
| summary: |
- Gnome crashed after closing CLion IDE + Bug in window manager: Failed to find destination workspace in layout ; + GNOME Shell crashed with signal 6 |
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1959507, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.