| Summary: | [abrt] xfce4-mixer-4.8.0-1.fc16: Process /usr/bin/xfce4-mixer was killed by signal 6 (SIGABRT) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mho <mdatye> | ||||||||
| Component: | xfce4-mixer | Assignee: | Kevin Fenzi <kevin> | ||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 16 | CC: | kevin | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | i686 | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | abrt_hash:7617af3637a7591d5ceb46646a1ef9ce61631c67 | ||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2012-03-30 14:47:27 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
Mho
2011-12-10 19:54:05 UTC
Created attachment 544979 [details]
File: smolt_data
Created attachment 544980 [details]
File: maps
Created attachment 544981 [details]
File: backtrace
What were you doing when this crash happened? Can you duplicate it? Backtrace analysis found this bug to be similar to bug #767482, closing as duplicate. This bug seems to belong to component gtk2, gtk2-engines, cairo, libXrender or libX11. Bugs which were found to be similar to this bug: Thunar: bug #766176, bug #767482 empathy: bug #658675 firefox: bug #547889, bug #586293, bug #625008, bug #646049 gnome-keyring: bug #688078 gthumb: bug #770022 gtk2: bug #747832 lxpanel: bug #748311 openoffice.org: bug #576682, bug #725124 This comment is automatically generated. *** This bug has been marked as a duplicate of bug 767482 *** |