bug

[Marlon Inga]

.local/share/Steam/steamapps/common/Counter-Strike Global Offensive/csgo.sh' -steam", ProcID 13173
Jun 29 23:40:35 marlonric steam.desktop[11873]: ThreadGetProcessExitCode: no such process 13249
Jun 29 23:40:35 marlonric steam.desktop[11873]: ThreadGetProcessExitCode: no such process 13173
Jun 29 23:40:35 marlonric steam.desktop[11873]: ThreadGetProcessExitCode: no such process 13172
Jun 29 23:40:35 marlonric steam.desktop[11873]: ThreadGetProcessExitCode: no such process 13121
Jun 29 23:40:35 marlonric steam.desktop[11873]: ThreadGetProcessExitCode: no such process 13005
Jun 29 23:40:35 marlonric steam.desktop[11873]: ThreadGetProcessExitCode: no such process 13004
Jun 29 23:40:35 marlonric steam.desktop[11873]: ThreadGetProcessExitCode: no such process 13003
Jun 29 23:40:35 marlonric steam[11873]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
Jun 29 23:40:35 marlonric steam[11873]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 29 23:40:35 marlonric steam[11873]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
Jun 29 23:40:35 marlonric steam[11873]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 29 23:40:37 marlonric systemd[2497]: Started Application launched by gsd-media-keys.
Jun 29 23:40:37 marlonric dbus-daemon[2518]: [session uid=1000 pid=2518] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.239' (uid=1000 pid=13261 comm="/usr/bin/gnome-terminal.real --wait " label="unconfined")
Jun 29 23:40:37 marlonric systemd[2497]: Starting GNOME Terminal Server...
Jun 29 23:40:37 marlonric dbus-daemon[2518]: [session uid=1000 pid=2518] Successfully activated service 'org.gnome.Terminal'
Jun 29 23:40:37 marlonric systemd[2497]: Started GNOME Terminal Server.
Jun 29 23:40:37 marlonric systemd[2497]: Started VTE child process 13287 launched by gnome-terminal-server process 13264.
Jun 29 23:40:38 marlonric gnome-shell[2891]: Can't update stage views actor <unnamed>[<MetaWindowGroup>:0x564fe3b82350] is on because it needs an allocation.
Jun 29 23:40:38 marlonric gnome-shell[2891]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x564fe5375320] is on because it needs an allocation.
Jun 29 23:40:38 marlonric gnome-shell[2891]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x564fe5379860] is on because it needs an allocation.
Jun 29 23:40:38 marlonric gameoverlayui[13193]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 29 23:40:48 marlonric steam.desktop[11873]: reaping pid: 13193 -- gameoverlayui
Jun 29 23:41:43 marlonric gnome-shell[2891]: Can't update stage views actor <unnamed>[<MetaWindowGroup>:0x564fe3b82350] is on because it needs an allocation.
Jun 29 23:41:43 marlonric gnome-shell[2891]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x564fe5375320] is on because it needs an allocation.
Jun 29 23:41:43 marlonric gnome-shell[2891]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x564fe5379860] is on because it needs an allocation.
marlon@marlo

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.5-0ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-45-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Jun 29 23:50:26 2023
DisplayManager: gdm3
InstallationDate: Installed on 2022-09-17 (286 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1)
RelatedPackageVersions: mutter-common 42.5-0ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 2007742, so it 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. Feel free to continue to report any other bugs you may find.