Bug 504588

Summary:	EPIC4 client sometimes hangs
Product:	[Fedora] Fedora	Reporter:	Jan ONDREJ <ondrejj>
Component:	epic	Assignee:	Vitezslav Crhonek <vcrhonek>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	11	CC:	scott, vcrhonek
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-04-09 05:57:19 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jan ONDREJ 2009-06-08 12:01:33 UTC

Description of problem:
Sometimes EPIC4 client hangs. There is no core dumped, only error message is displayed on screen. There is no call stack displayed.
Epic hangs in different situations, but I only can reproduce ctrl+c problem.
Even if ctrl+c problem is not very important, other problems are.

Version-Release number of selected component (if applicable):
epic-2.10-3.fc11.i586

How reproducible:
always

Steps to Reproduce:
1. run epic (you can run it without loading a script or connection to server): epic -v -s
2. press ctrl+c
  
Actual results:
* * * * * * * * * * * * * * * * * * * * * * * * 
IRC-II has trapped a critical protection error. 
This is probably due to a bug in the program.   

If you have access to the 'BUG_FORM' in the ircII source distribution,  
we would appreciate your filling it out if you feel doing so would
be helpful in finding the cause of your problem.

If you do not know what the 'BUG_FORM' is or you do not have access
to it, please dont worry about filling it out.  You might try talking   
to the person who is in charge of IRC at your site and see if you can   
get them to help you.   

This version of IRC II is  --->[EPIC4-2.10 (769)]
The date of release is     --->[20080329]

* * * * * * * * * * * * * * * * * * * * * * * * 
The program will now terminate. 
Call stack
End of call stack


Expected results:
running epic client

Comment 1 Jan ONDREJ 2009-06-08 12:10:44 UTC

(In reply to comment #0)

> 1. run epic (you can run it without loading a script or connection to server):
> epic -v -s

Sorry, wrong command, should be:
  epic -q -s
But you can run it without arguments too.

Comment 2 Scott van Looy 2009-06-12 11:59:47 UTC

I'm also seeing this. I run EPIC in screen, 4-5 times a day it crashes.

Fedora 11, x86_64
epic-2.10-3.fc11.x86_64

Let me know if there's anything I can do to help debug it...

Comment 3 Jan ONDREJ 2009-06-12 12:04:01 UTC

Just for information, I have my own packages of epic5-1.0 and epic4 package recompiled from fc10.
epic5 is something different, my scripts are not working properly and looks like something different, not a replacement for epic4.
Epic4 package from fc10 has no similar problems, works fine. May be we should:
- downgrade to version from fc10
or
- contact upstream to fix these bugs in a new version.

Comment 4 Jan ONDREJ 2010-04-09 05:57:19 UTC

This was fixed by epic-2.10-7.fc12.i686.
Closing bug.

Comment 5 Vitezslav Crhonek 2010-04-12 10:10:36 UTC

Thanks for closing it Jan, I overlooked this BZ entry by mistake...