Ubuntu
xchat-indicator package

xchat-gnome crashed with SIGSEGV in XSendEvent()

Bug #1391885 reported by Michał Sawicz
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xchat-indicator (Ubuntu)
Fix Released
Medium
Marc Deslauriers

Bug Description

This happens whenever I interact with the messaging indicator for xchat-gnome.

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: xchat-gnome 1:0.30.0~git20141005.816798-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
Uname: Linux 3.16.0-24-generic x86_64
ApportVersion: 2.14.7-0ubuntu10
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Nov 12 14:23:44 2014
ExecutablePath: /usr/bin/xchat-gnome
ProcCmdline: xchat-gnome
SegvAnalysis:
 Segfault happened at: 0x7fc389a8ce3b <XSendEvent+43>: mov 0x968(%rdi),%rax
 PC (0x7fc389a8ce3b) ok
 source "0x968(%rdi)" (0x00000968) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: xchat-gnome
StacktraceTop:
 XSendEvent () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/xchat-gnome/plugins/indicator.so
 g_cclosure_marshal_VOID__STRINGv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.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: xchat-gnome crashed with SIGSEGV in XSendEvent()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sbuild sudo

Revision history for this message
Michał Sawicz (saviq) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 XSendEvent (dpy=0x0, w=156, propagate=propagate@entry=0, event_mask=event_mask@entry=1572864, event=event@entry=0x7fff3b7b6ec0) at ../../src/SendEvent.c:57
 really_activate_window (window=0x15d4510) at indicator.c:301
 source_display (mmapp=<optimized out>, channel=0x44eb3b0 "mzanetti", user_data=<optimized out>) at indicator.c:84
 g_cclosure_marshal_VOID__STRINGv (closure=0x3a50d10, return_value=<optimized out>, instance=<optimized out>, args=<optimized out>, marshal_data=<optimized out>, n_params=<optimized out>, param_types=0x3a35940) at /build/buildd/glib2.0-2.42.0/./gobject/gmarshal.c:1004
 _g_closure_invoke_va (closure=0x0, closure@entry=0x3a50d10, return_value=0x9c, return_value@entry=0x0, instance=0x0, instance@entry=0x168f5d0, args=0x180000, args@entry=0x7fff3b7b7210, n_params=997945024, param_types=0x22) at /build/buildd/glib2.0-2.42.0/./gobject/gclosure.c:831

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 xchat-gnome (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Michał Sawicz (saviq)
information type: Private → Public
Marc Deslauriers (mdeslaur)
affects: xchat-gnome (Ubuntu) → xchat-indicator (Ubuntu)
Changed in xchat-indicator (Ubuntu):
assignee: nobody → Marc Deslauriers (mdeslaur)
status: New → In Progress
Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

This should now be fixed with the new gtk3 xchat-gnome-indicator package in vivid:

https://launchpad.net/ubuntu/+source/xchat-gnome-indicator

Changed in xchat-indicator (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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