Bug 27419

Summary: E-FancyLauncer clones itself over and over again
Product: Ports & Packages Reporter: jmcoopr <jmcoopr>
Component: Individual Port(s)Assignee: freebsd-ports-bugs (Nobody) <ports-bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   

Description jmcoopr 2001-05-18 01:10:01 UTC
	On upgrading by GNOME+enlightenment to gnome-1.4, I've discovered a
nuisance bug in E-FancyLauncher.  The damn thing clones itself
forever--filling the screen with more and more copies of itself each
time X is restarted.  Apparently, gnome-1.4 now defaults to "save
settings on exist" (it was defaulted to OFF in gnome-1.2).  There
appears to be some sort of interaction between this change and
E-FancyLauncher.  The only way I've succeeded (temporarily) in turning
this bug off is to delete the .gnome and .enlightenment subdirectories
and start over.  But of course, this lasts only until the next restart.

At least the "ESC" key works well at killing all of the offspring off .
. . :)

Fix: 

None other than "ESC"aping the buggers . . .
How-To-Repeat: 
	Enable "Save Session" under GNOME
Comment 1 Tetsurou Okazaki freebsd_committer freebsd_triage 2001-05-21 11:44:26 UTC
Responsible Changed
From-To: freebsd-ports->jhb

over to maintainer
Comment 2 jmcoopr 2001-08-15 17:08:52 UTC
It looks like the bug is actually in libepplet.  There's some discussion
of this on www.enlightenment.org.  It apparently affects ALL epplets.
Someone needs to figure out libepplet, put in code to check if an
instance is already running, and prevent further spawning (unless
overridden for some reason).

jmc
Comment 3 John Baldwin freebsd_committer freebsd_triage 2002-06-03 19:24:57 UTC
Responsible Changed
From-To: jhb->ports

This is a libepplet problem, not an E-FancyLauncher problem as the originator 
noted, so kick this back over to ports.
Comment 4 Pete Fritchman freebsd_committer freebsd_triage 2002-06-03 19:54:55 UTC
Responsible Changed
From-To: ports->freebsd-ports

Misfiled.
Comment 5 Edwin Groothuis freebsd_committer freebsd_triage 2003-02-13 01:15:40 UTC
State Changed
From-To: open->closed

libepplets has been updated recently, probably fixing the problem.