xchat-gnome crashed with SIGSEGV in gtk_clipboard_set_contents()

Bug #844003 reported by Ted Gould
214
This bug affects 30 people
Affects Status Importance Assigned to Milestone
XChat-GNOME
Fix Released
Critical
xchat-gnome (Ubuntu)
Fix Released
Medium
Canonical Desktop Team
Precise
Won't Fix
Medium
Unassigned
Quantal
Fix Released
Medium
Canonical Desktop Team

Bug Description

Selecting text quickly.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: xchat-gnome 1:0.30.0~git20100421.29cc76-1ubuntu4
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Wed Sep 7 10:41:42 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/xchat-gnome
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcCmdline: xchat-gnome
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7ffaff02b8d8 <gtk_clipboard_set_contents+40>: mov 0x48(%rdi),%rdi
 PC (0x7ffaff02b8d8) ok
 source "0x48(%rdi)" (0xffffffffec008b58) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: xchat-gnome
StacktraceTop:
 gtk_clipboard_set_contents (clipboard=0xffffffffec008b10, targets=0x16e3400, n_targets=6, get_func=0x7ffaff02b550 <text_get_func>, clear_func=0x7ffaff02b200 <text_clear_func>, user_data=0x139a730, have_owner=0) at /build/buildd/gtk+2.0-2.24.5/gtk/gtkclipboard.c:507
 IA__gtk_clipboard_set_with_data (clipboard=<optimized out>, targets=<optimized out>, n_targets=<optimized out>, get_func=<optimized out>, clear_func=<optimized out>, user_data=<optimized out>) at /build/buildd/gtk+2.0-2.24.5/gtk/gtkclipboard.c:596
 IA__gtk_clipboard_set_text (clipboard=0xffffffffec008b10, text=0x12a84b0 " on adding \"Unity\" to the list of desktops. Really, a bunch of discussion happened, and someone arbitrarily made a decision.\n<seb128> what's your goal? getting standards out? specs on protocols? cros"..., len=220) at /build/buildd/gtk+2.0-2.24.5/gtk/gtkclipboard.c:774
 ?? ()
 ?? ()
Title: xchat-gnome crashed with SIGSEGV in gtk_clipboard_set_contents()
UpgradeStatus: Upgraded to oneiric on 2011-06-17 (81 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse libvirtd lpadmin netdev plugdev sambashare tape video

Revision history for this message
Ted Gould (ted) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 gtk_clipboard_set_contents (clipboard=0xffffffffec008b10, targets=0x16e3400, n_targets=6, get_func=0x7ffaff02b550 <text_get_func>, clear_func=0x7ffaff02b200 <text_clear_func>, user_data=0x139a730, have_owner=0) at /build/buildd/gtk+2.0-2.24.5/gtk/gtkclipboard.c:507
 IA__gtk_clipboard_set_with_data (clipboard=<optimized out>, targets=<optimized out>, n_targets=<optimized out>, get_func=<optimized out>, clear_func=<optimized out>, user_data=<optimized out>) at /build/buildd/gtk+2.0-2.24.5/gtk/gtkclipboard.c:596
 IA__gtk_clipboard_set_text (clipboard=0xffffffffec008b10, text=0x12a84b0 " on adding \"Unity\" to the list of desktops. Really, a bunch of discussion happened, and someone arbitrarily made a decision.\n<seb128> what's your goal? getting standards out? specs on protocols? cros"..., len=220) at /build/buildd/gtk+2.0-2.24.5/gtk/gtkclipboard.c:774
 gtk_xtext_set_clip_owner (xtext=0xba59b0, event=<optimized out>) at xtext.c:2070
 gtk_xtext_button_release (widget=0xba59b0, event=0x131a580) at xtext.c:2146

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.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
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at:
https://bugzilla.gnome.org/show_bug.cgi?id=658502

Changed in xchat-gnome (Ubuntu):
status: New → Triaged
Changed in xchat-gnome:
importance: Unknown → Critical
status: Unknown → New
Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

Does anyone know how to reproduce this?

Revision history for this message
Ted Gould (ted) wrote : Re: [Bug 844003] Re: xchat-gnome crashed with SIGSEGV in gtk_clipboard_set_contents()

On Wed, 2012-02-22 at 17:00 +0000, Marc Deslauriers wrote:
> Does anyone know how to reproduce this?

Yeah, basically just click and select and just keep clicking.
Eventually you hit it. Basically if you're playing with your track pad
over an XChat window it'll happen. Which, sadly, I do more often than
I'd like to admit. ;-) This bug kills XChat at least once a week for
me.

Revision history for this message
Rick Spencer (rick-rickspencer3) wrote :

I realize this is a universe package, but we use it a lot. I thought the desktop team might want to consider taking a look. Please unassign as appropriate.

Changed in xchat-gnome (Ubuntu):
assignee: nobody → Canonical Desktop Team (canonical-desktop-team)
Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

This is actually in main.

tags: added: bugpattern-needed
tags: added: precise
tags: added: quantal
Changed in xchat-gnome (Ubuntu Precise):
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

I can't seems to reproduce this when clicking around try to select text over and over again in the chat scrolling window. Is there some detail I'm missing to be able to reproduce this bug?

Looking at the stack trace, disassembly/registers and the gtk code for that version, seems to me like the issue is the use of gtk_clipboard_get() to get the clipboard to pass to gtk_clipboard_set_text() in xtext.c. It would appear as though the widget window can't be determined, not sure why.

In xchat (not xchat-gnome) similar code, and elsewhere in xchat-gnome, looks like gtk_widget_get_clipboard() is used instead. Maybe it would be sufficient to replace the gtk_clipboard_get() call with this to solve the issue.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package xchat-gnome - 1:0.30.0~git20110821.e2a400-0.2ubuntu7

---------------
xchat-gnome (1:0.30.0~git20110821.e2a400-0.2ubuntu7) quantal; urgency=low

  * debian/patches/120-fix-clipboard-segfault.patch: Don't set the
    CLIPBOARD buffer when selecting text. CLIPBOARD should only be used
    when specifically selecting copy from a context menu. This may also
    have the side effect of fixing the common but hard to reproduce
    clipboard segfault. (LP: #844003)
 -- Marc Deslauriers <email address hidden> Tue, 21 Aug 2012 11:58:38 -0400

Changed in xchat-gnome (Ubuntu Quantal):
status: Triaged → Fix Released
Changed in xchat-gnome:
status: New → Fix Released
Revision history for this message
Steve Langasek (vorlon) wrote :

The Precise Pangolin has reached end of life, so this bug will not be fixed for that release

Changed in xchat-gnome (Ubuntu Precise):
status: Triaged → Won't Fix
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.