Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 193030

Summary: net-news/raggle-0.4.4 unexpected crash and loss of cache and configuration
Product: Gentoo Linux Reporter: Michele Martone <dezperado>
Component: Current packagesAssignee: Gentoo Ruby Team <ruby>
Status: RESOLVED UPSTREAM    
Severity: normal    
Priority: High    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Michele Martone 2007-09-19 08:15:02 UTC
raggle v0.4.4 (an RSS aggregator written in ruby, based on ncurses) unexpectedly crashes and looses of cache all of its configuration (the ~/.raggle/feeds.yaml file).

it crashed while browsing headlines, in the headlines window.

/usr/bin/raggle:3563:in `select_item': undefined method `[]=' for nil:NilClass (NoMethodError)                | Press Q to exit
        from /usr/bin/raggle:2881:in `select_win_item'
        from /usr/bin/raggle:2976:in `adjust_to'
        from /usr/bin/raggle:2990:in `activate'
        from /usr/bin/raggle:3048:in `scroll_down'
        from /usr/bin/raggle:2244:in `scroll_down'
        from (eval):1:in `_load'
        from /usr/bin/raggle:4299:in `call'
        from /usr/bin/raggle:4299:in `main_loop'
        from /usr/bin/raggle:5643:in `main'
        from /usr/bin/raggle:6654
Thanks for using Raggle!

i wasn't able to reproduce this error.

reading from the main website (http://www.raggle.org) and related mailing list raggle seems unmantained and the author doesn't care about the bugs, sadly.


Reproducible: Couldn't Reproduce
Comment 1 Michele Martone 2007-09-19 08:16:46 UTC
(In reply to comment #0)
> unexpectedly crashes and looses of cache all of its configuration
I meant:
"unexpectedly crashes and looses all of its configuration"
Comment 2 Hans de Graaff gentoo-dev Security 2007-09-19 18:36:02 UTC
Looking at the mailing list archives it seems to be a known problem for which no fix has been found. With upstream seemingly inactive I'm afraid there isn't much we can do about it, so I'm closing this bug as UPSTREAM for now even though I realize there isn't much of an upstream. Feel free to re-open if you create or find a patch for the issue that we could apply.