compiz crashed with SIGSEGV in CompWindow::id() when trying to launch gitk from the commandline
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
1. I was using guake terminal
2. I typed "gitk &" to launch gitk in the background
3. subsequent launches from gnome terminal and guake terminal using "gitk" and "gitk &" worked fine.
Output from 'lsb_release -rd':
Description: Ubuntu Natty (development branch)
Release: 11.04
gitk:
Installed: 1:1.7.4.1-3
Candidate: 1:1.7.4.1-3
Version table:
*** 1:1.7.4.1-3 0
500 http://
100 /var/lib/
guake:
Installed: 0.4.2-4ubuntu1
Candidate: 0.4.2-4ubuntu1
Version table:
*** 0.4.2-4ubuntu1 0
500 http://
100 /var/lib/
git:
Installed: 1:1.7.4.1-3
Candidate: 1:1.7.4.1-3
Version table:
*** 1:1.7.4.1-3 0
500 http://
100 /var/lib/
I expected gitk to launch as normal. I didn't expect the screen to flicker and for compiz to die and relaunch itself.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: unity 3.6.8-0ubuntu3
ProcVersionSign
Uname: Linux 2.6.38-7-generic x86_64
Architecture: amd64
Date: Sat Mar 26 20:28:21 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302)
ProcCmdline: compiz
ProcEnviron:
LANGUAGE=en_GB:en
LANG=en_GB.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x43bef0 <_ZN10CompWindo
PC (0x0043bef0) ok
source "0x58(%rdi)" (0x00000058) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
CompWindow::id() ()
CompScreen:
PrivateComposi
CompScreen:
PrivateGLScree
Title: compiz crashed with SIGSEGV in CompWindow::id()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #743685, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.