gnome-shell crashed with SIGSEGV in find_output_by_key() from real_assign_crtcs() from meta_monitor_config_assign_crtcs() from apply_configuration()

[Fo2adZz]

After wake-up the system just displayed this message.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: gnome-shell 3.10.3-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0
Uname: Linux 3.13.0-6-generic x86_64
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Feb 3 18:38:52 2014
DisplayManager: gdm
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
 b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
 b'org.gnome.desktop.interface' b'clock-show-date' b'true'
InstallationDate: Installed on 2014-01-30 (4 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140129)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f3283efc618: mov (%rdx),%rbp
 PC (0x7f3283efc618) ok
 source "(%rdx)" (0x00000001) not located in a known VMA region (needed readable region)!
 destination "%rbp" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 ?? () from /usr/lib/libmutter.so.0
 ?? () from /usr/lib/libmutter.so.0
 ?? () from /usr/lib/libmutter.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-shell crashed with SIGSEGV in g_signal_emit_valist()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 find_output_by_key (outputs=0x50f2200, n_outputs=<optimized out>, key=key@entry=0x1) at core/monitor-config.c:1670
 real_assign_crtcs (assignment=assignment@entry=0x7fff463870d0, output_num=output_num@entry=0) at core/monitor-config.c:1734
 meta_monitor_config_assign_crtcs (outputs=0x4eb9760, crtcs=0x4dbca00, manager=0x14b82a0, config=0x3864f40) at core/monitor-config.c:1805
 apply_configuration (self=0x15412a0, config=0x3864f40, manager=0x14b82a0, stored=0) at core/monitor-config.c:864
 ?? ()

[Tim Lunn (darkxst)]

I think this was fixed in 3.10.4

[Cristian Aravena Romero (caravena)]

This looks like a problem in a stored display configuration. Can you obtain the
monitors.xml file of the affected user, or ask him to try reproduce the bug
without that file?

[Fo2adZz (fouad-hassouneh)]

attached is the monitors.xml file

On Mon, Mar 24, 2014 at 3:09 PM, Cristian Aravena Romero <<email address hidden>
> wrote:

> This looks like a problem in a stored display configuration. Can you
> obtain the
> monitors.xml file of the affected user, or ask him to try reproduce the bug
> without that file?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1275969
>
> Title:
> gnome-shell crashed with SIGSEGV in find_output_by_key()
>
> Status in GNOME Shell:
> Incomplete
> Status in "gnome-shell" package in Ubuntu:
> New
>
> Bug description:
> After wake-up the system just displayed this message.
>
> ProblemType: Crash
> DistroRelease: Ubuntu 14.04
> Package: gnome-shell 3.10.3-0ubuntu2
> ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0
> Uname: Linux 3.13.0-6-generic x86_64
> ApportVersion: 2.13.2-0ubuntu2
> Architecture: amd64
> CurrentDesktop: GNOME
> Date: Mon Feb 3 18:38:52 2014
> DisplayManager: gdm
> ExecutablePath: /usr/bin/gnome-shell
> GsettingsChanges:
> b'org.gnome.desktop.interface' b'gtk-im-module'
> b"'gtk-im-context-simple'"
> b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
> b'org.gnome.desktop.interface' b'clock-show-date' b'true'
> InstallationDate: Installed on 2014-01-30 (4 days ago)
> InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64
> (20140129)
> ProcCmdline: /usr/bin/gnome-shell
> ProcEnviron:
> LANGUAGE=en_CA:en
> PATH=(custom, user)
> XDG_RUNTIME_DIR=<set>
> LANG=en_CA.UTF-8
> SHELL=/bin/bash
> SegvAnalysis:
> Segfault happened at: 0x7f3283efc618: mov (%rdx),%rbp
> PC (0x7f3283efc618) ok
> source "(%rdx)" (0x00000001) not located in a known VMA region (needed
> readable region)!
> destination "%rbp" ok
> SegvReason: reading NULL VMA
> Signal: 11
> SourcePackage: gnome-shell
> StacktraceTop:
> ?? () from /usr/lib/libmutter.so.0
> ?? () from /usr/lib/libmutter.so.0
> ?? () from /usr/lib/libmutter.so.0
> ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> g_signal_emit_valist () from
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> Title: gnome-shell crashed with SIGSEGV in g_signal_emit_valist()
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-shell/+bug/1275969/+subscriptions
>

[Launchpad Janitor (janitor)]

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