gedit usually sleeps indefinitely when launched by unity-2d-places

Bug #808918 reported by Eliah Kagan
24
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gedit (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

In a unity-2d session on an Oneiric i386 system with gedit 3.1.1-0ubuntu4 and unity-2d/unity-2d-places 3.8.10-0ubuntu2, running gedit from unity-2d-places (by clicking the home button, typing in gedit, and clicking Text Editor in the search results; or by pressing Alt+F2, typing in gedit, and pressing enter) almost always results in gedit sleeping indefinitely and never becoming usable or creating any visible windows:

ek@Zim:~$ ps ax | grep -v grep | grep gedit
 1911 ? Sl 0:00 gedit

When this happens, I see the gedit icon appear in the unity-2d launcher for a short time, but then the icon disappears (and gedit continues running nonfunctionally in the background). Usually, gedit can be killed by SIGTERM; occasionally, it seems that SIGKILL is required. On rare occasion, gedit runs successfully when launched in this way.

When I run gedit from a Terminal window (by running the command: gedit), it almost always works correctly, but on rare occasion, it sleeps indefinitely (in these cases, ps shows it as having state Sl+ rather than Sl, but I don't think that's a relevant difference). In these cases, SIGINT (from Ctrl+C) and SIGTERM have always been successful at terminating it, but I have only gotten the problem to occur a few times when running gedit from the Terminal.

When I run gedit from unity-2d-launcher (I am able to pin it to the launcher when it is running from the Terminal), it also works OK. I have not run it from the launcher frequently enough to know if it ever fails when launched that way, though I suppose it probably does.

I strongly suspect that this is due to a deadlock. I would be pleased to attempt to furnish any further information required for the investigation of this bug.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: gedit 3.1.1-0ubuntu4
ProcVersionSignature: Ubuntu 3.0.0-4.5-generic 3.0.0-rc6
Uname: Linux 3.0.0-4-generic i686
Architecture: i386
Date: Mon Jul 11 13:15:44 2011
ExecutablePath: /usr/bin/gedit
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110705.1)
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
SourcePackage: gedit
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Eliah Kagan (degeneracypressure) wrote :
description: updated
tags: added: iso-testing
Changed in gedit (Ubuntu):
status: New → Confirmed
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Pedro, could you look at this please, it seems to be a problem when gedit is launched directly from a terminal as well. IIRC there are dups.

Changed in gedit (Ubuntu):
assignee: nobody → Pedro Villavicencio (pvillavi)
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Could somebody please get a strace log? just run gedit as: strace strace -Ff -tt gedit 2>&1 | tee strace-gedit.log ; then compress the file and upload it to the report, thanks.

Changed in gedit (Ubuntu):
assignee: Pedro Villavicencio (pvillavi) → nobody
Revision history for this message
Eliah Kagan (degeneracypressure) wrote :

Since it is very difficult for me to produce this bug by running gedit from the Terminal (or by any means other than from unity-2d-places), Jean-Baptiste Lallement will probably have to obtain the strace log.

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Pedro I think the problem is not a crash but close to what Curtis describes in bug 827414 and both are duplicates.

Revision history for this message
David Barth (dbarth) wrote :

So that bug and bug 827414 seem to indicate that this is not a problem in either u2d, u3d or bamf, but more a regression in gedit. It was working in natty, and the part of the code that starts applications didn't change in that regard. Besides the anomaly is limited to gedit and other programs don't exhibit the same issue.

Brad Figg (brad-figg)
tags: added: rls-mgr-o-tracking
Revision history for this message
Jan Rathmann (kaiserclaudius) wrote :

This still happens in Oneric Beta 2.

Revision history for this message
Sebastien Bacher (seb128) wrote :

seems a duplicate indeed and not a gedit issue, see the other bug

Revision history for this message
Eliah Kagan (degeneracypressure) wrote :

I suspect that this may *not* be a duplicate of bug 827414. This just happened with on a fully updated Precise i386 system (obtained by replacing oneiric with precise in sources.list, dist-upgrading, and rebooting) with gedit 3.2.1-0ubuntu1 and unity-2d 4.12.0-0ubuntu1. Here's process information for gedit:

ek@Gnar:~$ ps ax | grep -v grep | grep gedit
15906 ? Sl 0:00 gedit

Running gedit a second time from unity-2d-places (or the launcher, or the Terminal) is successful. But running gedit a first time from the launcher or the Terminal is also successful, whereas running it the first time from unity-2d-places is not. This seems to be reproducible.

tags: added: precise
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.