| 2017-10-17 08:08:41 |
Daniel Told |
bug |
|
|
added bug |
| 2017-10-17 08:09:18 |
Daniel Told |
description |
This is a more detailed report for a previously reported bug occurring with Ubuntu 17.10 in a dual screen setup. Crashes appear to be linked to notifications appearing. Initially they would just result in the session crashing and going back to the login screen, but in the meantime I had a few occasions where the shell would just lock up and not allow any further interaction.
However, this might have been lack of patience on my part, since this time it did go back to the login screen after while and left behind the .crash file used for this bug report.
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
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 17 10:01:14 2017
DisplayManager: gdm3
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2017-07-03 (105 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/bin/gnome-shell
SegvAnalysis:
Segfault happened at: 0x7f66b85aecdf <g_type_check_instance_is_fundamentally_a+15>: mov (%rdx),%rdx
PC (0x7f66b85aecdf) ok
source "(%rdx)" (0x1e8126810e26816a) not located in a known VMA region (needed readable region)!
destination "%rdx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
g_type_check_instance_is_fundamentally_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_value_set_object () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_object_get_property () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
?? () from /usr/lib/libgjs.so.0
?? () from /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
UpgradeStatus: Upgraded to artful on 2017-10-09 (7 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo |
This is a more detailed report for a previously reported bug (#1723882) occurring with Ubuntu 17.10 in a dual screen setup. Crashes appear to be linked to notifications appearing. Initially they would just result in the session crashing and going back to the login screen, but in the meantime I had a few occasions where the shell would just lock up and not allow any further interaction.
However, this might have been lack of patience on my part, since this time it did go back to the login screen after while and left behind the .crash file used for this bug report.
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
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 17 10:01:14 2017
DisplayManager: gdm3
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2017-07-03 (105 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/bin/gnome-shell
SegvAnalysis:
Segfault happened at: 0x7f66b85aecdf <g_type_check_instance_is_fundamentally_a+15>: mov (%rdx),%rdx
PC (0x7f66b85aecdf) ok
source "(%rdx)" (0x1e8126810e26816a) not located in a known VMA region (needed readable region)!
destination "%rdx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
g_type_check_instance_is_fundamentally_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_value_set_object () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_object_get_property () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
?? () from /usr/lib/libgjs.so.0
?? () from /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
UpgradeStatus: Upgraded to artful on 2017-10-09 (7 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo |
|
| 2017-10-17 08:13:16 |
Apport retracing service |
bug |
|
|
added subscriber Crash bug triagers for Ubuntu packages |
| 2017-10-17 08:13:18 |
Apport retracing service |
attachment removed |
CoreDump.gz https://bugs.launchpad.net/bugs/1724159/+attachment/4973314/+files/CoreDump.gz |
|
|
| 2017-10-17 08:13:18 |
Apport retracing service |
attachment removed |
Disassembly.txt https://bugs.launchpad.net/bugs/1724159/+attachment/4973316/+files/Disassembly.txt |
|
|
| 2017-10-17 08:13:19 |
Apport retracing service |
attachment removed |
ProcMaps.txt https://bugs.launchpad.net/bugs/1724159/+attachment/4973321/+files/ProcMaps.txt |
|
|
| 2017-10-17 08:13:19 |
Apport retracing service |
attachment removed |
ProcStatus.txt https://bugs.launchpad.net/bugs/1724159/+attachment/4973322/+files/ProcStatus.txt |
|
|
| 2017-10-17 08:13:20 |
Apport retracing service |
attachment removed |
Registers.txt https://bugs.launchpad.net/bugs/1724159/+attachment/4973323/+files/Registers.txt |
|
|
| 2017-10-17 08:13:20 |
Apport retracing service |
attachment removed |
Stacktrace.txt https://bugs.launchpad.net/bugs/1724159/+attachment/4973324/+files/Stacktrace.txt |
|
|
| 2017-10-17 08:13:21 |
Apport retracing service |
attachment removed |
ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1724159/+attachment/4973325/+files/ThreadStacktrace.txt |
|
|
| 2017-10-17 08:13:23 |
Apport retracing service |
marked as duplicate |
|
1723705 |
|
| 2017-10-17 08:13:23 |
Apport retracing service |
information type |
Private |
Public |
|
| 2017-10-17 08:13:27 |
Apport retracing service |
tags |
amd64 apport-crash artful need-amd64-retrace wayland-session |
amd64 apport-crash artful wayland-session |
|
