This bug was fixed in the package mutter - 3.28.1-1

---------------
mutter (3.28.1-1) unstable; urgency=medium

  [ Jeremy Bicha ]
  * New upstream release
    - Fix window button spacing when display is scaled (LP: #1725133)
  * Bump Standards-Version to 4.1.4

  [ Marco Trevisan (Treviño) ]
  * Add patches proposed upstream:
  * theme-frames-Use-surface-device-scale-instead-of-cairo_sc.patch:
    - theme, frames: Use surface device scale instead of cairo_scale
      (LP: #1764554)
  * theme-use-gtk_render_icon_suface-to-paint-button-icon.patch:
    - theme: use gtk_render_icon_suface to paint button icon
      (LP: #1764558)
  * theme-load-icons-as-Gtk-does-with-fallback-and-RTL-suppor.patch:
    - theme: load icons as Gtk does with fallback and RTL support
  * clutter-Smooth-out-master-clock-to-smooth-visuals.patch:
    - clutter: Smooth out master clock to smooth visuals
  * core-Return-1-if-meta_window_get_monitor-is-called-on-an-.patch:
    - core: Return -1 if meta_window_get_monitor is called on an
      unmanaged window (LP: #1724439)
  * backends-Move-MetaOutput-crtc-field-into-private-struct.patch:
    - backends: Move MetaOutput::crtc field into private struct
      (LP: #1703668)
  * backends-Add-logical-monitor-monitor-output-crtc-ref-chai.patch:
    - backends: Add logical monitor -> monitor -> output -> crtc ref
      chain (LP: #1703668)

 -- Jeremy Bicha <[email protected]>  Mon, 16 Apr 2018 22:35:14 -0400

** Changed in: mutter (Ubuntu)
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1703668

Title:
  gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output()
  from meta_monitor_get_vendor() from
  meta_input_settings_find_logical_monitor()

Status in Mutter:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/bfdb8ffc57978ae7c23f78fdf44266fa56985fe9

  ---

  The only thing i recognize from the crash is the crash report.
  everything works as expected

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu7
  ProcVersionSignature: Ubuntu 4.12.0-6.7-generic 4.12.0
  Uname: Linux 4.12.0-6-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Jul  9 21:56:54 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2017-07-07 (3 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170630)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7fd10dc9e103 <meta_monitor_get_main_output+3>:       
jmpq   *0x88(%rax)
   PC (0x7fd10dc9e103) ok
   source "*0x88(%rax)" ok
   SP (0x7ffe42d50508) ok
   Reason could not be automatically determined.
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_monitor_get_main_output () from 
/usr/lib/x86_64-linux-gnu/libmutter-0.so.0
   meta_monitor_get_vendor () from /usr/lib/x86_64-linux-gnu/libmutter-0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-0.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1703668/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to