| Summary: | Sussen 0.22 crashes on scanning | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Markus Saarinen <pied.piper1600> |
| Component: | Current packages | Assignee: | Gentoo Netmon project <netmon> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | pva |
| Priority: | High | ||
| Version: | 2006.0 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Markus Saarinen
2006-06-04 03:39:00 UTC
Thank you for report! I've managed to reproduce problem with cancel and forwardered bug upstream [1], while I could see results of scanning opened in bluefish html editor :) Reference: 1. https://dev.mmgsecurity.com/bugs/show_bug.cgi?id=56 BTW. To get debugging information it was enough for me to start sussen from console and look at output. sussen-0.22-r1.ebuild in cvs. Please test it. Crash when cancel button is pressed during execution should be fixed. About another issue, please take a look at upstream bugzilla. Seems that without backtrace there is nothing to do here. :) Plot thickens :) The reason it didn't open the results earlier was that there was no default handler for html files (which is odd as I had firefox-bin installed), but after manually setting Firefox as html handler, the opening started to work. So with new version the situation is as follows. when starting with sussen-applet --tray-icon: Everything works perfectly. Cancel exits, and execute opens the results. No errors - patch helped. when starting thru normal panel applet: Cancel crashes as before. Execute opens the report (as I now have changed the html handler to Firefox), but also crashes. I didn't see any errors in my console at any point as you did. Maybe I'm missing some debug flags somewhere... Thank you for report, Markus. sussen-0.22-r2.ebuild in portage. Please test it. I hope crash of gnome panel aplet should be fixed there. :) (In reply to comment #3) > I didn't see any errors in my console at any point as you did. Maybe I'm > missing some debug flags somewhere... Strange. I do not know :( Ok, seems we're all set. No more crashing anywhere. Report opens as it should and no more unexpected exits. Case closed, as far as I'm concerned :). I'm very glad to read that. Thank you! |