Bug 753067
| Summary: | [abrt] ccsm-0.9.5.92-1.fc16: Process /usr/bin/python was killed by signal 11 (SIGSEGV) | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | ptaack | ||||||||||||
| Component: | compizconfig-python | Assignee: | Wolfgang Ulbrich <fedora> | ||||||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||
| Priority: | unspecified | ||||||||||||||
| Version: | 16 | CC: | akshayvyas29, andremontes, dmalcolm, ivazqueznet, joe, jonathansteffan, kloutvor, leigh123linux, octaviolh86, sarrab1976, stuart, tomspur | ||||||||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | i686 | ||||||||||||||
| OS: | Unspecified | ||||||||||||||
| Whiteboard: | abrt_hash:790168edc6b9b059f2c622f2de885b3d747bb60d | ||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2013-02-14 00:56:59 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
ptaack
2011-11-11 08:59:41 UTC
Created attachment 532994 [details]
File: event_log
Created attachment 532995 [details]
File: coredump
Created attachment 532996 [details]
File: smolt_data
Created attachment 532997 [details]
File: maps
Created attachment 532998 [details]
File: backtrace
Please post steps to reproduce the bug if not I will have to close it. yum instal compiz-gnome-shell ccsm reboot open ccsm from user menu (through the same console), ccsm window appears, but the mouse click on any item leads to the error. sorry, compiz-gnome (session)... Package: ccsm-0.9.5.92-1.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne) Comment ----- Did nothing Package: ccsm-0.9.5.92-1.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne) Comment ----- Change config in ccsm Exact same crash details here in FC16 under both Gnome and LXDE. i was triyin to configurate the compiz when it closed rating: 4 Package: ccsm-0.9.5.92-1.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne) ccsm-0.9.5.92-1.fc16 is a old version, run yum update. No newer version is available in updates or in updates-testing. (In reply to comment #14) > No newer version is available in updates or in updates-testing. This update should sort this bug as well. FYI I haven't been able to replicate the issue here on my F16 x86_64 install. (In reply to comment #15) > (In reply to comment #14) > > No newer version is available in updates or in updates-testing. > > This update should sort this bug as well. > FYI I haven't been able to replicate the issue here on my F16 x86_64 install. I forgot to add the link https://admin.fedoraproject.org/updates/FEDORA-2011-16726/compizconfig-python-0.9.5.94-0.1.gitb02413d104573641f293d535537821316ecb8f36.fc16 *** Bug 760389 has been marked as a duplicate of this bug. *** *** Bug 759335 has been marked as a duplicate of this bug. *** Ok, the last crash of ccsm was on Dec 11, and compizconfig-python was updated Dec 12, so I tried it again. It works now! Now the only compiz problem for me is the "flash" when switching workspaces, bug#767269. Backtrace analysis of bugs across components suggests the actual bug is in component python or compizconfig-python instead of component ccsm, reassigning to python. Bugs which were found to be similar to this bug: ccsm: bug #759335, bug #760389, bug #766124 fusion-icon: bug #751073, bug #756209, bug #758867 This comment is automatically generated. *** Bug 756209 has been marked as a duplicate of this bug. *** *** Bug 758867 has been marked as a duplicate of this bug. *** *** Bug 751073 has been marked as a duplicate of this bug. *** *** Bug 766124 has been marked as a duplicate of this bug. *** Looking at attachment 532998 [details], the segfault is happening at:
#0 __pyx_f_12compizconfig_GetType (__pyx_v_value=0x0) at src/compizconfig.c:1487
Reassigning to compizconfig-python
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. 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. |