Bug 538799
| Summary: | Segfault inside gtk_style_realize [ClearlooksStyle] whilst running mumbles | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Tim Waugh <twaugh> | ||||
| Component: | gtk2 | Assignee: | Matthias Clasen <mclasen> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 12 | CC: | aalam, aymeric.rateau, chandrams, dmalcolm, guy.carmin, ivazqueznet, james.antill, jonathansteffan, katzj, mclasen, rasool_nasr | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | abrt_hash:9c4c1e2e597412d6e8b60482af43a87f83170b36 | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2010-12-04 03:10:02 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
Tim Waugh
2009-11-19 12:57:47 UTC
Created attachment 370330 [details]
File: backtrace
Are you able to reproduce this? What graphical theme were you using? Looking at the backtrace, looks like a segmentation fault in thread 1 inside gtk_settings_notify (frame 5); it looks like mumbles was trying to respond to a change to the graphical theme settings, and that the ClearLooksStyle backend may have been trying to dereference a NULL pointer. Reassigning component from "python" to "gtk2" (please reassign as appropriate) and updating the Summary. It's the ClearLooks theme (with Nodoka window border). The mumbles theme is 'glass'. Yes, by changing the theme a few times I can reproduce it (bug #539487). *** Bug 539487 has been marked as a duplicate of this bug. *** *** Bug 539828 has been marked as a duplicate of this bug. *** *** Bug 545740 has been marked as a duplicate of this bug. *** *** Bug 547010 has been marked as a duplicate of this bug. *** *** Bug 547059 has been marked as a duplicate of this bug. *** *** Bug 554086 has been marked as a duplicate of this bug. *** This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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. |