*** This bug is a duplicate of bug 1723615 ***
    https://bugs.launchpad.net/bugs/1723615

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 #1723615, 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.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1769982/+attachment/5136315/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1769982/+attachment/5136317/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1769982/+attachment/5136322/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1769982/+attachment/5136323/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1769982/+attachment/5136324/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1769982/+attachment/5136325/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1769982/+attachment/5136326/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1723615
   gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
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/1769982

Title:
  gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Submitting crash as instructed in bug 1769720.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  8 14:34:19 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-05-19 (354 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7f399f4fa210 <meta_monitor_mode_get_resolution>:     
mov    0x8(%rdi),%eax
   PC (0x7f399f4fa210) ok
   source "0x8(%rdi)" (0x00000008) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_monitor_mode_get_resolution () at 
/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   meta_monitor_calculate_mode_scale () at 
/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   meta_monitor_manager_update_logical_state_derived () at 
/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   meta_monitor_manager_rebuild_derived () at 
/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   meta_monitor_manager_xrandr_handle_xevent () at 
/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution()
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (11 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo 
vboxusers wireshark

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769982/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to