gnome-shell crashed with SIGSEGV in init_config_from_preferred_mode()

Bug #1503420 reported by m0rtal
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Expired
Medium
Unassigned

Bug Description

just crashed

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: gnome-shell 3.16.3-1ubuntu6
ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
Uname: Linux 4.2.0-14-generic x86_64
ApportVersion: 2.19-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Oct 6 23:17:20 2015
DisplayManager: gdm
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
InstallationDate: Installed on 2015-03-20 (200 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fe10d9c3442 <meta_monitor_config_make_default+642>: mov 0x10(%rdi),%r9d
 PC (0x7fe10d9c3442) ok
 source "0x10(%rdi)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%r9d" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 meta_monitor_config_make_default () from /usr/lib/libmutter.so.0
 meta_monitor_manager_xrandr_handle_xevent () from /usr/lib/libmutter.so.0
 ?? () from /usr/lib/libmutter.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gnome-shell crashed with SIGSEGV in meta_monitor_config_make_default()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
m0rtal (alexander-nagorny) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 init_config_from_preferred_mode (output=0x5136e90, config=0x6356260) at backends/meta-monitor-config.c:1104
 make_linear_config (self=<optimized out>, max_width=<optimized out>, max_height=<optimized out>, config=0x58e4680, n_outputs=2, outputs=0x5136e90) at backends/meta-monitor-config.c:1182
 make_default_config (use_stored_config=<optimized out>, max_height=<optimized out>, max_width=<optimized out>, n_outputs=<optimized out>, outputs=0x5136e90, self=0x3bf2120) at backends/meta-monitor-config.c:1296
 meta_monitor_config_make_default (self=0x3bf2120, manager=0x26602a0) at backends/meta-monitor-config.c:1381
 meta_monitor_manager_on_hotplug (manager=<optimized out>) at backends/meta-monitor-manager.c:1286

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-shell (Ubuntu):
importance: Undecided → Medium
summary: - gnome-shell crashed with SIGSEGV in meta_monitor_config_make_default()
+ gnome-shell crashed with SIGSEGV in init_config_from_preferred_mode()
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-shell (Ubuntu):
status: New → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test.

Changed in gnome-shell (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]

Changed in gnome-shell (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.