Bug 191640 - Pan just falls down dead for no reason
Summary: Pan just falls down dead for no reason
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: pan
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Michael A. Peters
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-05-14 11:54 UTC by Paul F. Johnson
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-06-02 14:17:37 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Paul F. Johnson 2006-05-14 11:54:23 UTC
Description of problem:
I've subscribed to a number of groups (some being binaries) and just been
reading groups when Pan dies suddenly. No throwback (even if run from the
terminal). On restart, all subscribed groups have been lost though the server
settings remain in tact.

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

How reproducible:
Always happens

Steps to Reproduce:
1. Start Pan and use it for a while.
2.
3.
  
Actual results:
Pan dies with no throwback to either a terminal or via bug-buddy

Expected results:
Pan shouldn't die so quietly!

Additional info:
I have removed my previous Pan configuration files prior to upgrading to 0.96

Comment 1 Michael A. Peters 2006-05-14 18:05:45 UTC
0.97 will be pushed as soon as rawhide building is no longer broken.

With respect to losing groups - I also have seen it lose groups when crashing,
if the groups have just been added. Try subscribing to the groups you want and
then quiting before doing anything else.

Comment 2 Paul F. Johnson 2006-05-21 10:25:27 UTC
It's now collapsing and not remembering settings (such as wanting the postings
in chronological order, refreshing every 5 mins etc)

I've updated to 0.97

Comment 3 Paul F. Johnson 2006-06-02 14:17:37 UTC
Seems to be much happier now. Closing the bug


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