[Bug 1870454] Re: gnome-shell crashed with SIGSEGV in meta_monitor_get_outputs (monitor=0x0) from meta_monitor_config_manager_assign()

2022-05-02 Thread Daniel van Vugt
** Description changed:

  https://errors.ubuntu.com/problem/930950abdb6648752bc30584d0833b348c68f0ba
  https://errors.ubuntu.com/problem/50192237f22f17593e486f3349bf4770a1e28002
+ https://errors.ubuntu.com/problem/717fc039791d35516db85b1057b844960bb16d57
  
  ---
  
  I don't really know what caused this, I didn't notice anything out of
  the ordinary, so I'm not sure exactly when it occurred. I usually plug
  and unplug an external monitor, this seems related.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Apr  2 19:31:02 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-12-14 (475 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7fdf6e50156b :  mov
0x8(%rax,%rdi,1),%rax
   PC (0x7fdf6e50156b) ok
   source "0x8(%rax,%rdi,1)" (0xffb8) not located in a known VMA 
region (needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_monitor_get_outputs () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0
   meta_monitor_config_manager_assign () at 
/usr/lib/x86_64-linux-gnu/libmutter-6.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_monitor_get_outputs()
  UpgradeStatus: Upgraded to focal on 2020-03-25 (8 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare 
sudo vboxusers
  separator:

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870454

Title:
  gnome-shell crashed with SIGSEGV in meta_monitor_get_outputs
  (monitor=0x0) from meta_monitor_config_manager_assign()

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1870454] Re: gnome-shell crashed with SIGSEGV in meta_monitor_get_outputs (monitor=0x0) from meta_monitor_config_manager_assign()

2020-04-02 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-shell (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870454

Title:
  gnome-shell crashed with SIGSEGV in meta_monitor_get_outputs
  (monitor=0x0) from meta_monitor_config_manager_assign()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1870454] Re: gnome-shell crashed with SIGSEGV in meta_monitor_get_outputs (monitor=0x0) from meta_monitor_config_manager_assign()

2020-04-02 Thread Daniel van Vugt
Tracking in
https://errors.ubuntu.com/problem/930950abdb6648752bc30584d0833b348c68f0ba

but see also
https://errors.ubuntu.com/problem/50192237f22f17593e486f3349bf4770a1e28002

** Description changed:

+ https://errors.ubuntu.com/problem/930950abdb6648752bc30584d0833b348c68f0ba
+ https://errors.ubuntu.com/problem/50192237f22f17593e486f3349bf4770a1e28002
+ 
+ ---
+ 
  I don't really know what caused this, I didn't notice anything out of
  the ordinary, so I'm not sure exactly when it occurred. I usually plug
  and unplug an external monitor, this seems related.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Apr  2 19:31:02 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-12-14 (475 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  SegvAnalysis:
-  Segfault happened at: 0x7fdf6e50156b :  mov
0x8(%rax,%rdi,1),%rax
-  PC (0x7fdf6e50156b) ok
-  source "0x8(%rax,%rdi,1)" (0xffb8) not located in a known VMA 
region (needed readable region)!
-  destination "%rax" ok
+  Segfault happened at: 0x7fdf6e50156b :  mov
0x8(%rax,%rdi,1),%rax
+  PC (0x7fdf6e50156b) ok
+  source "0x8(%rax,%rdi,1)" (0xffb8) not located in a known VMA 
region (needed readable region)!
+  destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
-  meta_monitor_get_outputs () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0
-  meta_monitor_config_manager_assign () at 
/usr/lib/x86_64-linux-gnu/libmutter-6.so.0
-  () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0
-  () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0
-  () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0
+  meta_monitor_get_outputs () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0
+  meta_monitor_config_manager_assign () at 
/usr/lib/x86_64-linux-gnu/libmutter-6.so.0
+  () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0
+  () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0
+  () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_monitor_get_outputs()
  UpgradeStatus: Upgraded to focal on 2020-03-25 (8 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare 
sudo vboxusers
  separator:

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870454

Title:
  gnome-shell crashed with SIGSEGV in meta_monitor_get_outputs
  (monitor=0x0) from meta_monitor_config_manager_assign()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1870454] Re: gnome-shell crashed with SIGSEGV in meta_monitor_get_outputs (monitor=0x0) from meta_monitor_config_manager_assign()

2020-04-02 Thread Daniel van Vugt
** Summary changed:

- gnome-shell crashed with SIGSEGV in meta_monitor_get_outputs()
+ gnome-shell crashed with SIGSEGV in meta_monitor_get_outputs (monitor=0x0) 
from meta_monitor_config_manager_assign()

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870454

Title:
  gnome-shell crashed with SIGSEGV in meta_monitor_get_outputs
  (monitor=0x0) from meta_monitor_config_manager_assign()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs