Bug 790190
Summary: | Invalid write in gtk3-3.2.3 causes crashes | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Yann Droneaud <yann> | ||||||||||||||||
Component: | gtk3 | Assignee: | Matthias Clasen <mclasen> | ||||||||||||||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||||||||
Priority: | unspecified | ||||||||||||||||||
Version: | 16 | CC: | collura, lucilanga, mbarnes, mclasen, mcrha | ||||||||||||||||
Target Milestone: | --- | ||||||||||||||||||
Target Release: | --- | ||||||||||||||||||
Hardware: | x86_64 | ||||||||||||||||||
OS: | Unspecified | ||||||||||||||||||
Whiteboard: | abrt_hash:950a01806bcc51dc88d7e42535c5e4c94155b919 | ||||||||||||||||||
Fixed In Version: | gtk3-3.2.3-2.fc16 | Doc Type: | Bug Fix | ||||||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||||||
Clone Of: | Environment: | ||||||||||||||||||
Last Closed: | 2012-03-01 09:33:58 UTC | Type: | --- | ||||||||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||||||||
Documentation: | --- | CRM: | |||||||||||||||||
Verified Versions: | Category: | --- | |||||||||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||
Embargoed: | |||||||||||||||||||
Attachments: |
|
Description
Yann Droneaud
2012-02-13 21:09:17 UTC
Created attachment 561680 [details]
File: dso_list
Created attachment 561681 [details]
File: build_ids
Created attachment 561682 [details]
File: xsession_errors
Created attachment 561683 [details]
File: maps
Created attachment 561684 [details]
File: backtrace
Same thing as bug #790011 Saving settings in the send/outgoing mail settings pane. backtrace_rating: 4 Package: evolution-3.2.2-1.fc16 OS Release: Fedora release 16 (Verne) Created attachment 561686 [details]
File: backtrace
In .xsession-errors, the message is: GSlice: MemChecker: attempt to release non-allocated block: 0x5d1da20 size=40 I have the problem only with: G_SLICE=always-malloc,debug-blocks G_DEBUG=resident-modules,gc-friendly *** Bug 790011 has been marked as a duplicate of this bug. *** It seems to me that this is not an issue with Evolution. I was able to reproduce this, but with change from [1] it works as expected. Could you try with [2], which has the change included, whether it'll help for you too, please? Thanks in advance. [1] https://bugzilla.gnome.org/show_bug.cgi?id=455900 [2] http://koji.fedoraproject.org/koji/taskinfo?taskID=3790063 Settings -> Cancel backtrace_rating: 4 Package: evolution-3.2.2-1.fc16 OS Release: Fedora release 16 (Verne) Created attachment 562145 [details]
File: backtrace
(In reply to comment #12) > It seems to me that this is not an issue with Evolution. I was able to > reproduce this, but with change from [1] it works as expected. Could you try > with [2], which has the change included, whether it'll help for you too, > please? Thanks in advance. > > [1] https://bugzilla.gnome.org/show_bug.cgi?id=455900 > [2] http://koji.fedoraproject.org/koji/taskinfo?taskID=3790063 I have installed the gtk proposed package (and the latest evolution package). I'm not able to reproduce the bug currently. Seems good for now. Good, thanks for the update. I'll ask gtk+ maintainers to include the fix in the next update of gtk3. gtk3-3.2.3-2.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/gtk3-3.2.3-2.fc16 Package gtk3-3.2.3-2.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gtk3-3.2.3-2.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-1720/gtk3-3.2.3-2.fc16 then log in and leave karma (feedback). gtk3-3.2.3-2.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. |