Bug 532282
| Summary: | Crash with XKB bell for undecorated windows | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Bernie Innocenti <bernie+fedora> | ||||
| Component: | metacity | Assignee: | Owen Taylor <otaylor> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 12 | CC: | damien.schoof, jeremy, mads, otaylor, sandmann, tagoh | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | abrt_hash:fe754f3be59bebcf6857200f52f8b816cc986139 | ||||||
| Fixed In Version: | 2.28.0-13.fc12 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2009-12-27 20:27:16 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
Bernie Innocenti
2009-11-01 06:50:33 UTC
Created attachment 366994 [details]
File: backtrace
This is what I've found in ~/.xsession-errors: metacity:ERROR:core/bell.c:211:bell_flash_window_frame: assertion failed: (window->frame != NULL) Window manager warning: Workarounds for broken applications disabled. Some applications may not behave properly. Window manager warning: "" found in configuration database is not a valid value for keybinding "maximize" Window manager warning: "" found in configuration database is not a valid value for keybinding "unmaximize" handle_message(member:'Crash') This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Sounds like: https://bugzilla.gnome.org/show_bug.cgi?id=598231 Are you using Chromium? (It's not actually Chromium specific, but that seems to be a frequent trigger.) *** Bug 540608 has been marked as a duplicate of this bug. *** FWIW I (the duplicate guy) do not have chromium installed, but I don't know what trigged the crash. I have these xsession errors: metacity:ERROR:core/bell.c:211:bell_flash_window_frame: assertion failed: (window->frame != NULL) handle_message(member:'Crash') Window manager warning: Failed to read saved session file /home/mk/.config/metacity/sessions/10f8c5f46f457299c2125898848734261100000015040024.ms: Failed to open file '/home/mk/.config/metacity/sessions/10f8c5f46f457299c2125898848734261100000015040024.ms': No such file or directory (I have no /home/mk/.config/metacity/ ) *** Bug 542074 has been marked as a duplicate of this bug. *** *** Bug 544622 has been marked as a duplicate of this bug. *** metacity-2.28.0-12.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/metacity-2.28.0-12.fc12 metacity-2.28.0-12.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update metacity'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2009-13084 *** Bug 547388 has been marked as a duplicate of this bug. *** *** Bug 542966 has been marked as a duplicate of this bug. *** metacity-2.28.0-13.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update metacity'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2009-13084 metacity-2.28.0-13.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report. *** Bug 552141 has been marked as a duplicate of this bug. *** |