| 2017-10-14 15:20:06 |
Rachel Greenham |
bug |
|
|
added bug |
| 2017-10-14 15:27:34 |
Apport retracing service |
bug |
|
|
added subscriber Crash bug triagers for Ubuntu packages |
| 2017-10-14 15:27:36 |
Apport retracing service |
attachment added |
|
Stacktrace.txt https://bugs.launchpad.net/bugs/1723615/+attachment/4971011/+files/Stacktrace.txt |
|
| 2017-10-14 15:27:37 |
Apport retracing service |
attachment added |
|
StacktraceSource.txt https://bugs.launchpad.net/bugs/1723615/+attachment/4971012/+files/StacktraceSource.txt |
|
| 2017-10-14 15:27:38 |
Apport retracing service |
attachment added |
|
ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1723615/+attachment/4971013/+files/ThreadStacktrace.txt |
|
| 2017-10-14 15:27:40 |
Apport retracing service |
attachment removed |
CoreDump.gz https://bugs.launchpad.net/bugs/1723615/+attachment/4971001/+files/CoreDump.gz |
|
|
| 2017-10-14 15:27:41 |
Apport retracing service |
gnome-shell (Ubuntu): importance |
Undecided |
Medium |
|
| 2017-10-14 15:27:43 |
Apport retracing service |
tags |
amd64 apport-crash artful need-amd64-retrace |
amd64 apport-crash artful |
|
| 2017-10-16 02:52:20 |
Daniel van Vugt |
information type |
Private |
Public |
|
| 2017-10-31 13:54:35 |
Launchpad Janitor |
gnome-shell (Ubuntu): status |
New |
Confirmed |
|
| 2017-10-31 14:03:21 |
Steven Harms |
bug |
|
|
added subscriber Steven Harms |
| 2018-03-27 08:15:43 |
Daniel van Vugt |
description |
This happened while I was away from the computer. By the timing it should have been well after the time it should have gone *into* displaysleep, and was also about 45min before I returned, so certainly wasn't the wake-up process either.
What I observed when I did return: My 4K monitor didn't wake up (that's a known problem with this monitor, Dell P2715Q), the second monitor (Dell U2711) did wake up, showing the login screen.
So although I've considered my Dell 4K problem a problem with waking up, I wonder if it might be actually a problem with it apparently going away completely after a longer displaysleep (it's usually fine if I just do a short sleep of a minute or two).
Another possibility is the cat stepped on the keyboard and thus triggered an attempted display-wake. But that would actually be out of character (for the cat).
Either way is a bug because the session should survive monitor shenanigans... :-)
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME-Greeter:GNOME
Date: Sat Oct 14 15:39:50 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
InstallationDate: Installed on 2017-07-30 (75 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_GB.UTF-8
SHELL=/bin/false
SegvAnalysis:
Segfault happened at: 0x7fae20ab44a0 <meta_monitor_mode_get_resolution>: mov 0x8(%rdi),%eax
PC (0x7fae20ab44a0) 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-1.so.0
meta_monitor_calculate_mode_scale () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
meta_monitor_manager_update_logical_state_derived () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
meta_monitor_manager_rebuild_derived () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
meta_monitor_manager_xrandr_handle_xevent () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
Title: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution()
UpgradeStatus: Upgraded to artful on 2017-08-22 (53 days ago)
UserGroups: |
https://errors.ubuntu.com/problem/84e05b052e88b79520a684d6113084e9be8bc339
---
This happened while I was away from the computer. By the timing it should have been well after the time it should have gone *into* displaysleep, and was also about 45min before I returned, so certainly wasn't the wake-up process either.
What I observed when I did return: My 4K monitor didn't wake up (that's a known problem with this monitor, Dell P2715Q), the second monitor (Dell U2711) did wake up, showing the login screen.
So although I've considered my Dell 4K problem a problem with waking up, I wonder if it might be actually a problem with it apparently going away completely after a longer displaysleep (it's usually fine if I just do a short sleep of a minute or two).
Another possibility is the cat stepped on the keyboard and thus triggered an attempted display-wake. But that would actually be out of character (for the cat).
Either way is a bug because the session should survive monitor shenanigans... :-)
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME-Greeter:GNOME
Date: Sat Oct 14 15:39:50 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
InstallationDate: Installed on 2017-07-30 (75 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_GB.UTF-8
SHELL=/bin/false
SegvAnalysis:
Segfault happened at: 0x7fae20ab44a0 <meta_monitor_mode_get_resolution>: mov 0x8(%rdi),%eax
PC (0x7fae20ab44a0) 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-1.so.0
meta_monitor_calculate_mode_scale () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
meta_monitor_manager_update_logical_state_derived () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
meta_monitor_manager_rebuild_derived () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
meta_monitor_manager_xrandr_handle_xevent () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
Title: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution()
UpgradeStatus: Upgraded to artful on 2017-08-22 (53 days ago)
UserGroups: |
|
| 2018-04-25 09:00:43 |
Marco Trevisan (Treviño) |
gnome-shell (Ubuntu): status |
Confirmed |
In Progress |
|
| 2018-04-25 09:01:39 |
Marco Trevisan (Treviño) |
gnome-shell (Ubuntu): assignee |
|
Jeremy Bicha (jbicha) |
|
| 2018-04-26 07:19:25 |
Daniel van Vugt |
description |
https://errors.ubuntu.com/problem/84e05b052e88b79520a684d6113084e9be8bc339
---
This happened while I was away from the computer. By the timing it should have been well after the time it should have gone *into* displaysleep, and was also about 45min before I returned, so certainly wasn't the wake-up process either.
What I observed when I did return: My 4K monitor didn't wake up (that's a known problem with this monitor, Dell P2715Q), the second monitor (Dell U2711) did wake up, showing the login screen.
So although I've considered my Dell 4K problem a problem with waking up, I wonder if it might be actually a problem with it apparently going away completely after a longer displaysleep (it's usually fine if I just do a short sleep of a minute or two).
Another possibility is the cat stepped on the keyboard and thus triggered an attempted display-wake. But that would actually be out of character (for the cat).
Either way is a bug because the session should survive monitor shenanigans... :-)
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME-Greeter:GNOME
Date: Sat Oct 14 15:39:50 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
InstallationDate: Installed on 2017-07-30 (75 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_GB.UTF-8
SHELL=/bin/false
SegvAnalysis:
Segfault happened at: 0x7fae20ab44a0 <meta_monitor_mode_get_resolution>: mov 0x8(%rdi),%eax
PC (0x7fae20ab44a0) 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-1.so.0
meta_monitor_calculate_mode_scale () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
meta_monitor_manager_update_logical_state_derived () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
meta_monitor_manager_rebuild_derived () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
meta_monitor_manager_xrandr_handle_xevent () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
Title: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution()
UpgradeStatus: Upgraded to artful on 2017-08-22 (53 days ago)
UserGroups: |
https://gitlab.gnome.org/GNOME/mutter/issues/130
https://errors.ubuntu.com/problem/84e05b052e88b79520a684d6113084e9be8bc339
---
This happened while I was away from the computer. By the timing it should have been well after the time it should have gone *into* displaysleep, and was also about 45min before I returned, so certainly wasn't the wake-up process either.
What I observed when I did return: My 4K monitor didn't wake up (that's a known problem with this monitor, Dell P2715Q), the second monitor (Dell U2711) did wake up, showing the login screen.
So although I've considered my Dell 4K problem a problem with waking up, I wonder if it might be actually a problem with it apparently going away completely after a longer displaysleep (it's usually fine if I just do a short sleep of a minute or two).
Another possibility is the cat stepped on the keyboard and thus triggered an attempted display-wake. But that would actually be out of character (for the cat).
Either way is a bug because the session should survive monitor shenanigans... :-)
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME-Greeter:GNOME
Date: Sat Oct 14 15:39:50 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
InstallationDate: Installed on 2017-07-30 (75 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_GB.UTF-8
SHELL=/bin/false
SegvAnalysis:
Segfault happened at: 0x7fae20ab44a0 <meta_monitor_mode_get_resolution>: mov 0x8(%rdi),%eax
PC (0x7fae20ab44a0) 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-1.so.0
meta_monitor_calculate_mode_scale () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
meta_monitor_manager_update_logical_state_derived () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
meta_monitor_manager_rebuild_derived () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
meta_monitor_manager_xrandr_handle_xevent () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
Title: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution()
UpgradeStatus: Upgraded to artful on 2017-08-22 (53 days ago)
UserGroups: |
|
| 2018-04-27 03:08:23 |
Daniel van Vugt |
tags |
amd64 apport-crash artful |
amd64 apport-crash artful fixed-in-3.28.2 fixed-in-3.29.1 |
|
| 2018-05-08 19:05:59 |
Apport retracing service |
tags |
amd64 apport-crash artful fixed-in-3.28.2 fixed-in-3.29.1 |
amd64 apport-crash artful bionic fixed-in-3.28.2 fixed-in-3.29.1 |
|
| 2018-05-28 08:11:34 |
Daniel van Vugt |
gnome-shell (Ubuntu): status |
In Progress |
Fix Released |
|
| 2018-05-28 08:11:34 |
Daniel van Vugt |
gnome-shell (Ubuntu): assignee |
Jeremy Bicha (jbicha) |
|
|
| 2018-05-28 08:11:44 |
Daniel van Vugt |
nominated for series |
|
Ubuntu Bionic |
|
| 2018-05-28 08:12:41 |
Daniel van Vugt |
affects |
gnome-shell (Ubuntu) |
mutter (Ubuntu) |
|
| 2018-05-29 11:10:29 |
Jonathan Kamens |
bug |
|
|
added subscriber Jonathan Kamens |
| 2018-07-05 15:38:37 |
Colan Schwartz |
bug |
|
|
added subscriber Colan Schwartz |
| 2018-07-31 12:51:19 |
Marco Trevisan (Treviño) |
mutter (Ubuntu): status |
Fix Released |
In Progress |
|
| 2018-08-01 01:37:37 |
Launchpad Janitor |
mutter (Ubuntu): status |
In Progress |
Fix Released |
|
| 2018-08-02 18:21:59 |
Marco Trevisan (Treviño) |
description |
https://gitlab.gnome.org/GNOME/mutter/issues/130
https://errors.ubuntu.com/problem/84e05b052e88b79520a684d6113084e9be8bc339
---
This happened while I was away from the computer. By the timing it should have been well after the time it should have gone *into* displaysleep, and was also about 45min before I returned, so certainly wasn't the wake-up process either.
What I observed when I did return: My 4K monitor didn't wake up (that's a known problem with this monitor, Dell P2715Q), the second monitor (Dell U2711) did wake up, showing the login screen.
So although I've considered my Dell 4K problem a problem with waking up, I wonder if it might be actually a problem with it apparently going away completely after a longer displaysleep (it's usually fine if I just do a short sleep of a minute or two).
Another possibility is the cat stepped on the keyboard and thus triggered an attempted display-wake. But that would actually be out of character (for the cat).
Either way is a bug because the session should survive monitor shenanigans... :-)
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME-Greeter:GNOME
Date: Sat Oct 14 15:39:50 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
InstallationDate: Installed on 2017-07-30 (75 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_GB.UTF-8
SHELL=/bin/false
SegvAnalysis:
Segfault happened at: 0x7fae20ab44a0 <meta_monitor_mode_get_resolution>: mov 0x8(%rdi),%eax
PC (0x7fae20ab44a0) 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-1.so.0
meta_monitor_calculate_mode_scale () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
meta_monitor_manager_update_logical_state_derived () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
meta_monitor_manager_rebuild_derived () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
meta_monitor_manager_xrandr_handle_xevent () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
Title: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution()
UpgradeStatus: Upgraded to artful on 2017-08-22 (53 days ago)
UserGroups: |
https://gitlab.gnome.org/GNOME/mutter/issues/130
https://errors.ubuntu.com/problem/84e05b052e88b79520a684d6113084e9be8bc339
---
[ Description ]
This happened while I was away from the computer. By the timing it should have been well after the time it should have gone *into* displaysleep, and was also about 45min before I returned, so certainly wasn't the wake-up process either.
What I observed when I did return: My 4K monitor didn't wake up (that's a known problem with this monitor, Dell P2715Q), the second monitor (Dell U2711) did wake up, showing the login screen.
So although I've considered my Dell 4K problem a problem with waking up, I wonder if it might be actually a problem with it apparently going away completely after a longer displaysleep (it's usually fine if I just do a short sleep of a minute or two).
Another possibility is the cat stepped on the keyboard and thus triggered an attempted display-wake. But that would actually be out of character (for the cat).
Either way is a bug because the session should survive monitor shenanigans... :-)
In some not known conditions, g-s might crash while computing global resolution for monitors.
[ Test case ]
There's really no test case for this bug, a part that g-s should not crash with this stacktrace. Unforuntaltey this is quite hard to reproduce, it might happen while resetting the crtc when setting up a (new) monitor or at wake up, but so far nobody has reported a way for reproducing this.
[ Regression potential ]
Global scale for attached monitors could not be properly computed, and thus if attaching an HiDPI device, the UI could not be scaled properly
---
ProblemType: CrashDistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME-Greeter:GNOME
Date: Sat Oct 14 15:39:50 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
InstallationDate: Installed on 2017-07-30 (75 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_GB.UTF-8
SHELL=/bin/false
SegvAnalysis:
Segfault happened at: 0x7fae20ab44a0 <meta_monitor_mode_get_resolution>: mov 0x8(%rdi),%eax
PC (0x7fae20ab44a0) ok
source "0x8(%rdi)" (0x00000008) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11SourcePackage: gnome-shell
StacktraceTop:
meta_monitor_mode_get_resolution () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
meta_monitor_calculate_mode_scale () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
meta_monitor_manager_update_logical_state_derived () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
meta_monitor_manager_rebuild_derived () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
meta_monitor_manager_xrandr_handle_xevent () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
Title: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution()
UpgradeStatus: Upgraded to artful on 2017-08-22 (53 days ago)
UserGroups: |
|
| 2018-08-03 04:15:30 |
Iain Lane |
bug task added |
|
mutter (Ubuntu Bionic) |
|
| 2018-08-03 10:32:34 |
Marco Trevisan (Treviño) |
mutter (Ubuntu): assignee |
|
Marco Trevisan (Treviño) (3v1n0) |
|
| 2018-08-03 10:32:41 |
Marco Trevisan (Treviño) |
mutter (Ubuntu Bionic): assignee |
|
Marco Trevisan (Treviño) (3v1n0) |
|
| 2018-08-03 10:32:46 |
Marco Trevisan (Treviño) |
mutter (Ubuntu Bionic): status |
New |
In Progress |
|
| 2018-08-03 10:33:05 |
Marco Trevisan (Treviño) |
bug task added |
|
gnome-shell (Ubuntu) |
|
| 2018-08-03 10:33:13 |
Marco Trevisan (Treviño) |
gnome-shell (Ubuntu): status |
New |
Fix Released |
|
| 2018-08-03 10:33:18 |
Marco Trevisan (Treviño) |
bug task deleted |
gnome-shell (Ubuntu Bionic) |
|
|
| 2018-08-13 15:30:33 |
Łukasz Zemczak |
mutter (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2018-08-13 15:30:35 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2018-08-13 15:30:38 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2018-08-13 15:30:44 |
Łukasz Zemczak |
tags |
amd64 apport-crash artful bionic fixed-in-3.28.2 fixed-in-3.29.1 |
amd64 apport-crash artful bionic fixed-in-3.28.2 fixed-in-3.29.1 verification-needed verification-needed-bionic |
|
| 2018-08-22 15:11:05 |
Marco Trevisan (Treviño) |
tags |
amd64 apport-crash artful bionic fixed-in-3.28.2 fixed-in-3.29.1 verification-needed verification-needed-bionic |
amd64 apport-crash artful bionic done fixed-in-3.28.2 fixed-in-3.29.1 needed verification-done-bionic |
|
| 2018-08-23 01:54:26 |
Daniel van Vugt |
summary |
gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution() |
gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution → calculate_scale → meta_monitor_calculate_mode_scale → calculate_monitor_scale → derive_calculated_global_scale |
|
| 2018-08-23 13:31:17 |
Launchpad Janitor |
mutter (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2018-08-23 13:31:30 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2018-10-30 11:35:57 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~3v1n0/ubuntu/+source/mutter/+git/mutter/+merge/358005 |
|
| 2018-10-30 11:39:14 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~3v1n0/ubuntu/+source/mutter/+git/mutter/+merge/358006 |
|
