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

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 #1725160, 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/1752518/+attachment/5065870/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1725160
   gnome-shell crashed with SIGSEGV in 
meta_monitor_manager_kms_apply_crtc_mode() from 
meta_renderer_native_finish_frame()

** 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/1752518

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  
  graphical interface freezing or becoming unresponsive 

  in shell view (ctrl+alt+F2) a number of the following error messages
  also appears

  'failed command READ FPDMA QUEUED'

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu3
  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  1 09:06:09 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2015-03-19 (1077 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7f1a9e78a35f 
<meta_monitor_manager_kms_apply_crtc_mode+207>: mov    0x8(%rax),%rcx
   PC (0x7f1a9e78a35f) ok
   source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed 
readable region)!
   destination "%rcx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_monitor_manager_kms_apply_crtc_mode () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_renderer_native_finish_frame () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.so
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.so
  Title: gnome-shell crashed with SIGSEGV in 
meta_monitor_manager_kms_apply_crtc_mode()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1752518/+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