[xrandr]: gnome-settings-daemon crashed with SIGSEGV

Bug #1545248 reported by Francois Thirioux
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-settings-daemon (Ubuntu)
New
Medium
Unassigned

Bug Description

(Using Gnome shell)

When I hot-plug my hdmi external monitor through mini-DP dongle, my screens are messed up. I can obtain the following config : 2nd monitor and laptop screen cloned. But the other setups fail : 2nd monitor only, extended desktop. When reaching these modes, the laptop screen begins to flicker and if I don't quickly press the screens mode-changing key, the X server (?) ends up to a crash (return to GDM).

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: gnome-settings-daemon 3.18.2-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-5.20-generic 4.4.1
Uname: Linux 4.4.0-5-generic x86_64
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Feb 13 09:45:01 2016
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationDate: Installed on 2014-03-05 (709 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226)
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
SegvAnalysis:
 Segfault happened at: 0x7fc4fbba248d: mov (%rax),%r12
 PC (0x7fc4fbba248d) ok
 source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%r12" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgnome-desktop-3.so.12
 ?? () from /usr/lib/x86_64-linux-gnu/libgnome-desktop-3.so.12
 ?? () from /usr/lib/x86_64-linux-gnu/libgnome-desktop-3.so.12
 ?? () from /usr/lib/gnome-settings-daemon-3.0/libxrandr.so
 ?? () from /usr/lib/gnome-settings-daemon-3.0/libxrandr.so
Title: [xrandr]: gnome-settings-daemon crashed with SIGSEGV
UpgradeStatus: Upgraded to xenial on 2015-11-02 (102 days ago)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

Revision history for this message
Francois Thirioux (fthx) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 real_assign_crtcs (screen=screen@entry=0x885430, outputs=outputs@entry=0x107d190, assignment=assignment@entry=0x9252d0, error=error@entry=0x7ffe61e5b450) at gnome-rr-config.c:941
 crtc_assignment_new (screen=0x885430, outputs=outputs@entry=0x107d190, error=error@entry=0x7ffe61e5b450) at gnome-rr-config.c:1068
 gnome_rr_config_apply_helper (config=config@entry=0x7fc4e801d3b0, screen=<optimized out>, persistent=persistent@entry=0, error=error@entry=0x7ffe61e5b450) at gnome-rr-config.c:628
 gnome_rr_config_apply (config=config@entry=0x7fc4e801d3b0, screen=<optimized out>, error=error@entry=0x7ffe61e5b450) at gnome-rr-config.c:650
 apply_configuration (manager=manager@entry=0x7fc4e4003f00, config=0x7fc4e801d3b0, timestamp=timestamp@entry=3169159) at gsd-xrandr-manager.c:347

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-settings-daemon (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
information type: Private → Public
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.