gedit crashed with SIGSEGV in wl_proxy_get_user_data()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GTK+ |
Fix Released
|
Medium
|
|||
gtk+3.0 (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Ran gedit in Wayland.
I started weston via dbus-launch.
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: gedit 3.6.2-0ubuntu1
ProcVersionSign
Uname: Linux 3.8.0-4-generic x86_64
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Sat Feb 2 04:31:40 2013
ExecutablePath: /usr/bin/gedit
InstallationDate: Installed on 2011-10-21 (469 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MarkForUpload: True
ProcCmdline: gedit
SegvAnalysis:
Segfault happened at: 0x7f2d78929430 <wl_proxy_
PC (0x7f2d78929430) ok
source "0x30(%rdi)" (0x00000030) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gedit
StacktraceTop:
wl_proxy_
?? () from /usr/lib/
ffi_call_unix64 () from /usr/lib/
ffi_call () from /usr/lib/
?? () from /usr/lib/
Title: gedit crashed with SIGSEGV in wl_proxy_
UpgradeStatus: Upgraded to raring on 2013-01-20 (12 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
information type: | Private → Public |
affects: | gedit (Ubuntu) → wayland (Ubuntu) |
Changed in gtk: | |
importance: | Unknown → Medium |
status: | Unknown → Fix Released |
StacktraceTop: get_user_ data (proxy= proxy@entry= 0x0) at ../../src/ wayland- client. c:1114 get_user_ data (wl_surface=0x0) at /usr/include/ wayland- client- protocol. h:1217 handle_ enter (data=0x15d2830, pointer=<optimized out>, serial=<optimized out>, surface=0x0, sx=19968, sy=0) at /build/ buildd/ gtk+3.0- 3.6.4/. /gdk/wayland/ gdkdevice- wayland. c:963 unix64_ inner (closure=0x4e00, rvalue=0x15ea770, reg_args=0x16b, argp=0x7fffe8ddaeb4 "\001") at ../src/ x86/ffi64. c:671
wl_proxy_
wl_surface_
pointer_
ffi_closure_
?? ()