Bug 186624 - Segfault after responding to Password Manager dialog
Summary: Segfault after responding to Password Manager dialog
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: rssowl
Version: 5
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Anthony Green
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-03-24 20:08 UTC by Robin Green
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: 2007-11-11 21:36:45 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Robin Green 2006-03-24 20:08:27 UTC
Description of problem:
rssowl segfaults if you try to log in to a site in the internal browser, after
you click No in the Password Manager dialog.

I think the problem is that SWT has not been updated to be compatible with the
version of mozilla shipped in FC5.

Version-Release number of selected component (if applicable):
rssowl-1.2-11.fc5

How reproducible:
Always

Steps to Reproduce:
1. Help -> Homepage
2. Fill in anything in the username and password boxes
3. Click login
4. Click No in the password manager dialog
  
Actual results:
Crash

Expected results:
No crash

Comment 1 Robin Green 2006-03-25 17:19:22 UTC
(In reply to comment #0)
> I think the problem is that SWT has not been updated to be compatible with the
> version of mozilla shipped in FC5.

Or maybe not. I installed the mozilla, mozilla-nss and mozilla-nspr RPMs from
Fedora Core 4, and restarted rssowl, but I still got the crash. But according to 
http://www.eclipse.org/swt/faq.php#browserlinux
mozilla 1.7.8 (which is the version I installed) is supposed to be supported.


Comment 2 Anthony Green 2006-04-02 17:40:51 UTC
I can't reproduce this on 32-bit x86.  I'll try x86-64 later today.


Comment 3 Anthony Green 2007-11-11 21:36:45 UTC
RSSOwl is no longer part of Fedora due to licensing concerns.  I'm going to
WONTFIX this one.


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