Ubuntu
gimp package

Gimp causes session to close immediately

Bug #1024961 reported by Zordid on 2012-07-15

This bug report is a duplicate of: Bug #1021517: Xorg-server crashes reproducible with GIMP usage. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	gimp (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

Whenever I use Gimp, with the first mouse click in the image (e.g. selecting a region or ANYTHING else) - my Ubuntu session is immediately killed - all windows disappear and I return to the login screen of Ubuntu.

No matter what was running - it is closed and lost.

There are no other signs I can see, simply nothing. I have never experienced anything like this before and I do only get this when using Gimp, no other programs cause problems!

How can I track this down? I am using the regular Ubuntu version of Gimp 2.6 that comes from the repositories!

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: gimp 2.6.12-1ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
Uname: Linux 3.2.0-27-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu11
Architecture: amd64
Date: Sun Jul 15 16:03:05 2012
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
SourcePackage: gimp
UpgradeStatus: Upgraded to precise on 2012-04-30 (76 days ago)

Tags:

Revision history for this message

Zordid (zordid-gmx) wrote on 2012-07-15:

Dependencies.txt Edit (4.2 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (146 bytes, text/plain; charset="utf-8")

Revision history for this message

a (tuomasjjrasanen) wrote on 2012-07-15:

I can confirm this.

/usr/bin/X encounters a segmentation fault and aborts.

Changed in gimp (Ubuntu):
status:	New → Confirmed

Revision history for this message

a (tuomasjjrasanen) wrote on 2012-07-15:

Xorg.log Edit (876 bytes, text/plain)

Revision history for this message

a (tuomasjjrasanen) wrote on 2012-07-15:

After browsing the bug database, I am quite sure that this particular bug is a duplicate of bug #1021517, so I am marking it 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. Feel free to continue to report any other bugs you may find.