gnome-terminal crashed with signal 5 in gdk_x_error()

Bug #620763 reported by Yura Tolstik on 2010-08-19
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-terminal (Ubuntu)

Bug Description

Binary package hint: gnome-terminal

lsb_release -rd
Description: Ubuntu maverick (development branch)
Release: 10.10

apt-cache policy gnome-terminal
  Installed: 2.31.90-0ubuntu1
  Candidate: 2.31.90-0ubuntu1
  Version table:
 *** 2.31.90-0ubuntu1 0
        500 maverick/main i386 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gnome-terminal 2.31.90-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-16.22-generic
Uname: Linux 2.6.35-16-generic i686
Architecture: i386
Date: Fri Aug 20 01:47:30 2010
ExecutablePath: /usr/bin/gnome-terminal
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcCmdline: gnome-terminal
 PATH=(custom, user)
Signal: 5
SourcePackage: gnome-terminal
 gdk_x_error (display=0x8b7c5c0, error=0xbfdede7c)
 _XError () from /usr/lib/
 ?? () from /usr/lib/
 _XReply () from /usr/lib/
 XGetWindowProperty () from /usr/lib/
Title: gnome-terminal crashed with signal 5 in gdk_x_error()
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse libvirtd lpadmin netdev plugdev sambashare tape vboxusers video

Yura Tolstik (yltsrc) wrote :

 g_log_remove_handler () from /lib/
 ?? () from /lib/
 IA__gdk_error_trap_push ()
 _XError (dpy=0x8b7c5c0, rep=0xbfdede7c)
 process_responses (dpy=0x8b7c5c0,

Changed in gnome-terminal (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as detailed as possible.
This will help us to find and resolve the problem.

visibility: private → public
Changed in gnome-terminal (Ubuntu):
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers