Bug 78350 – vim won't die

Bug 78350 - vim won't die

Summary:	vim won't die

Status:	CLOSED DUPLICATE of bug 83700

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	gnome-core (Show other bugs)
Sub Component:
Version:	8.0
Hardware:	i686 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Karsten Hopp
QA Contact:	David Lawrence
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2002-11-21 12:07 EST by Steve Dum
Modified:	2007-04-18 12:48 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2006-02-21 13:50:11 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Steve Dum 2002-11-21 12:07:17 EST

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020827

Description of problem:
Vim sessions active when logging out don't die.  (I assume gnome isn't
passing a hup to the session).

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.Start up gnome
2.in a xterm run vim
3.logout without first exiting from vim.

	

Actual Results:  the vim session, not only doesn't die but it goes into an
infinite loop pegging the cpu

Expected Results:  vim should have died.  Either by getting a hup from the
shutdown or
by detecting that it's stdin has been closed, or both.

Additional info:

Comment 1 Karsten Hopp 2002-12-03 04:07:01 EST

It gets the correct signal with KDE and aborts. It seems than gnome doesn't pass
the right signal.
Changing component to gnome

Comment 2 Karsten Hopp 2003-06-20 07:51:40 EDT


*** This bug has been marked as a duplicate of 83700 ***

Comment 3 Red Hat Bugzilla 2006-02-21 13:50:11 EST

Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.