Ubuntu
gtk+3.0 package

unity-greeter crashed with SIGSEGV in gdk_device_get_source()

Bug #983677 reported by A. sleeping.li0n on 2012-04-17

10

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	gtk+3.0 (Ubuntu)	New	Medium	Unassigned

Bug Description

I don't know. This error was occured after updated and rebooted my pc.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity-greeter 0.2.7-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.0.1-0ubuntu4
Architecture: amd64
Date: Tue Apr 17 14:39:19 2012
ExecutablePath: /usr/sbin/unity-greeter
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
ProcCmdline: /usr/sbin/unity-greeter
ProcEnviron:
PATH=(custom, no user)
LANG=ja_JP.UTF-8
SHELL=/bin/false
SegvAnalysis:
Segfault happened at: 0x7fa1a1294c96 <gdk_device_get_source+22>: cmp %rax,(%rdx)
PC (0x7fa1a1294c96) ok
source "%rax" ok
destination "(%rdx)" (0x0000000a) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: unity-greeter
StacktraceTop:
gdk_device_get_source () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
gdk_display_get_event () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: unity-greeter crashed with SIGSEGV in gdk_device_get_source()
UpgradeStatus: Upgraded to precise on 2012-04-02 (15 days ago)
UserGroups:

Tags:

Revision history for this message

A. sleeping.li0n (lureandfly-deactivatedaccount) wrote on 2012-04-17:

#1

Dependencies.txt Edit (4.7 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (52.7 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (786 bytes, text/plain; charset="utf-8")
Registers.txt Edit (756 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (1.7 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (5.6 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2012-04-17:

#2

StacktraceTop:
gdk_device_get_source (device=<optimized out>) at /build/buildd/gtk+3.0-3.4.1/./gdk/gdkdevice.c:643
_gdk_display_get_pointer_info (display=0xcdf060, device=0xceebd0) at /build/buildd/gtk+3.0-3.4.1/./gdk/gdkdisplay.c:1232
_gdk_windowing_got_event (display=0xcdf060, event_link=0xe78b00, event=0x100ee10, serial=1659) at /build/buildd/gtk+3.0-3.4.1/./gdk/gdkwindow.c:9911
_gdk_x11_display_queue_events (display=0xcdf060) at /build/buildd/gtk+3.0-3.4.1/./gdk/x11/gdkeventsource.c:339
gdk_display_get_event (display=0xcdf060) at /build/buildd/gtk+3.0-3.4.1/./gdk/gdkdisplay.c:310

Revision history for this message

Apport retracing service (apport) wrote on 2012-04-17: Stacktrace.txt

#3

Stacktrace.txt Edit (10.6 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2012-04-17: ThreadStacktrace.txt

#4

ThreadStacktrace.txt Edit (19.5 KiB, text/plain)

Changed in unity-greeter (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-amd64-retrace

Revision history for this message

Sebastien Bacher (seb128) wrote on 2012-04-20:

#5

Seems like a gtk issue rather

visibility:	private → public
affects:	unity-greeter (Ubuntu) → gtk+3.0 (Ubuntu)

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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