| Summary: | [GTK] WebKitGtk+ 2.5.2 crashes using Facebook | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Andres Gomez Garcia <agomez> |
| Component: | WebKitGTK | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | berto, cgarcia, mcatanzaro, mrobinson, zan |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
|
Description
Andres Gomez Garcia
2014-08-13 00:25:10 PDT
This was not happening in 2.5.1 then? I haven't checked the time frame of his work and whether it would affect 2.5.2, but Edu's crypto patches that landed over the past few weeks required bumping the version of the libgnutls library. Might that be related? (In reply to comment #1) > This was not happening in 2.5.1 then? No. Removed myself from CC. I can't reproduce this. Is it still happening, Andres? If so, with what versions of WebKitGTK+, GnuTLS, and glib-networking? (In reply to comment #5) > I can't reproduce this. Is it still happening, Andres? If so, with what > versions of WebKitGTK+, GnuTLS, and glib-networking? I have no longer that version. I can re-try in some days, though, but it will take time. However, being a development version I assume it would make more sense to test with a more modern one. FWIW, I'm using 2.6.4 nowadays and I'm not having that problem any more. But 2.5.2 is from the unstable branch, isn't it? Do we have a scenario where people can't upgrade from 2.5.2 to some 2.6? If not, does it make sense to keep this bug open? (In reply to comment #7) > But 2.5.2 is from the unstable branch, isn't it? Do we have a scenario where > people can't upgrade from 2.5.2 to some 2.6? If not, does it make sense to > keep this bug open? That's what I was saying ... but I didn't know if there was any interest on checking the actual bug or just assume that something fixed the problem without really knowing the cause. Anyway, I suppose there is none ... |