My bug #1763850 got marked as a dupplicate (and probably is). It's seems to 
only occur once after a fresh install on my system. I tried to reproduced and 
What I did was:
a fresh install with encrypted drive, 
login to regular "ubuntu"-session,
update all software, 
login to "ubuntu wayland"-session -> image freezes -> thrown-back to login 
login to regular "ubuntu"-session,
do things for a few minutes (I was surfing with firefox both times) -> crash 
report appears on-screen.

You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.

  gnome-shell crashed with SIGSEGV in cogl_object_unref() from
  iter_remove_or_steal() from g_hash_table_iter_remove() from
  st_texture_cache_evict_icons() from on_icon_theme_changed()

Status in gnome-shell package in Ubuntu:

Bug description:


  i don´t know

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Mar  8 20:18:43 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell

  InstallationDate: Installed on 2018-03-08 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180308)
  ProcCmdline: /usr/bin/gnome-shell
   Segfault happened at: 0x7f921c91b510 <cogl_object_unref>:    mov    
   PC (0x7f921c91b510) ok
   source "(%rdi)" (0x00000000) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
   cogl_object_unref () from 
   ?? () from /lib/x86_64-linux-gnu/
   ?? () from /usr/lib/gnome-shell/
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/
   ?? () from /usr/lib/x86_64-linux-gnu/
  Title: gnome-shell crashed with SIGSEGV in cogl_object_unref()
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to