After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 61945 - always crashes on a password-protected url (mozilla works)
always crashes on a password-protected url (mozilla works)
Status: VERIFIED DUPLICATE of bug 60723
Product: galeon
Classification: Deprecated
Component: Mozilla interaction
0.x
Other Linux
: Normal major
: ---
Assigned To: Philip Langdale
Philip Langdale
Depends on:
Blocks:
 
 
Reported: 2001-10-08 14:33 UTC by Marius Andreiana
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
gziped strace of galeon crash (108.40 KB, application/octet-stream)
2001-10-08 14:34 UTC, Marius Andreiana 		Details

Description Marius Andreiana 2001-10-08 14:33:38 UTC 
I try to access an url which is password protected (with .htaccess). The
password was already remembered by pass manager, but it has changed. Now I
don't even get to password prompt dialog, galeon just crashes. 

It crashes frequently on other password protected site; sometimes I get the
password prompt  but it crashes after entering the right password.
Sometimes works....

I've attaced the complete strace (start galeon, enter url, crash)
Comment 1 Marius Andreiana 2001-10-08 14:34:51 UTC 
Created attachment 5787 [details]
gziped strace of galeon crash
Comment 2 Yanko Kaneti 2001-10-08 15:50:16 UTC 
well. a gdb backtrace would have been more helpfull but i am pretty
sure this is a duplicate of 60723

*** This bug has been marked as a duplicate of 60723 ***
Comment 3 Marius Andreiana 2001-10-08 18:25:20 UTC 
please provide instructions how to get the gdb backtrace and I'll
attach it, I'd really love to see this fixed.
Comment 4 Yanko Kaneti 2001-10-08 18:40:59 UTC 
when a bug is marked duplicate it means its closed

please add your comments to the bug that yours is duplicate of

in this case there is no need to do that this bug has been fixed
before 0.12.3

so you should simply upgrade
Comment 5 Marius Andreiana 2001-10-11 12:12:59 UTC 
closing this, upgrading solved it