| Summary: | [abrt] claws-mail-3.7.10-5.fc16: soup_socket_is_ssl: Process /usr/bin/claws-mail was killed by signal 11 (SIGSEGV) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Kevin Fenzi <kevin> | ||||||
| Component: | claws-mail | Assignee: | Andreas Bierfert <andreas.bierfert> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 16 | CC: | andreas.bierfert, bugs.michael, tomspur | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | abrt_hash:3f9631408f994a87717a7060014fdcd1a3f9b911 | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2013-02-13 08:48:07 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
|
Description
Kevin Fenzi
2011-10-14 17:50:47 UTC
Created attachment 528250 [details]
File: maps
Created attachment 528251 [details]
File: backtrace
Ah ha. This isn't a claws-mail bug at all. I had the 'use gnome proxy settings' enabled in the fancy plugin. Seems there is a bug where if you don't have a https proxy set there it tries to use your http proxy and blows up. Not sure if that problem is in gnome-control-center or what. ;( Looks like a libsoup problem, from soup-socket.c:
1074 gboolean
1075 soup_socket_is_ssl (SoupSocket *sock)
1076 {
1077 SoupSocketPrivate *priv = SOUP_SOCKET_GET_PRIVATE (sock);
1078
1079 return priv->ssl_creds != NULL;
1080 }
And you provided a 0x0 sock, so SOUP_SOCKET_GET_PRIVATE tries to get access to a zero pointer.
Did you set nothing as proxy, but configured one?
(That could explain, why there is a 0x0 pointer.)
Maybe a if (!sock) return False; could help above.
I did have a proxy set, but it was http only. The https proxy was empty/unset/unfilled in. I did see this once with the gdata stuff as well although I had nothing configured... This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |