unity-control-center crashed with SIGSEGV in gnome_rr_screen_get_output_by_name()

Bug #1300011 reported by Goryachkin Alexandr
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity-control-center (Ubuntu)
New
Medium
Unassigned

Bug Description

notebook + 2 iiyama prolite xb3485wsu

one iiyama connected via displaylink adapter
(hp usb graphics adapter)

Description: Ubuntu Trusty Tahr (development branch)
Release: 14.04

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: unity-control-center 14.04.3+14.04.20140328-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
Uname: Linux 3.13.0-20-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Mar 31 09:03:07 2014
ExecutablePath: /usr/bin/unity-control-center
InstallationDate: Installed on 2014-03-28 (2 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
ProcCmdline: unity-control-center appearance
SegvAnalysis:
 Segfault happened at: 0x7f36141f8b7e <__strcmp_sse2_unaligned+30>: movdqu (%rsi),%xmm0
 PC (0x7f36141f8b7e) ok
 source "(%rsi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%xmm0" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity-control-center
StacktraceTop:
 gnome_rr_screen_get_output_by_name () from /usr/lib/libgnome-desktop-3.so.7
 ?? () from /usr/lib/x86_64-linux-gnu/unity-control-center-1/panels/libdisplay.so
 ?? () from /usr/lib/x86_64-linux-gnu/unity-control-center-1/panels/libdisplay.so
 ?? () from /usr/lib/x86_64-linux-gnu/unity-control-center-1/panels/libdisplay.so
 ?? () from /usr/lib/x86_64-linux-gnu/unity-control-center-1/panels/libdisplay.so
Title: unity-control-center crashed with SIGSEGV in gnome_rr_screen_get_output_by_name()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
usr_lib_unity-control-center:
 activity-log-manager 0.9.7-0ubuntu12
 deja-dup 30.0-0ubuntu2

Revision history for this message
Goryachkin Alexandr (avgoryachkin) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 gnome_rr_screen_get_output_by_name (screen=<optimized out>, name=0x0) at gnome-rr.c:1954
 get_current_modes (self=0x249c7d0) at cc-display-panel.c:517
 rebuild_resolution_combo (self=0x249c7d0) at cc-display-panel.c:911
 rebuild_gui (self=0x249c7d0) at cc-display-panel.c:968
 on_output_event (area=0x2125e50, event=0x7fff2e1ad760, data=0x27d96a0) at cc-display-panel.c:1939

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 unity-control-center (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.