Bug 502295
| Summary: | xfce4-xkb-plugin disappears from xfce panel | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Luis Garrido <luisgarrido> |
| Component: | xfce4-xkb-plugin | Assignee: | Christoph Wickert <christoph.wickert> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 10 | CC: | christoph.wickert |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | 0.5.3-1.fc11 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-11-22 16:58:14 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: | |||
|
Description
Luis Garrido
2009-05-23 09:31:29 UTC
Apologies for the delay. You need to help me debugging this. Please install the debuginfo packages and follow the instructions from http://wiki.xfce.org/howto/panel_plugin_debug I need this info to file a bug upstream. TIA! Hi! I followed the instructions, installed the debuginfos and created an instance of the plugin running under gdb to try to get a backtrace for you, but I am afraid I will have to desist :-( I can't find the sequence of events to purposefully trigger this bug, so I'd have to keep using the debugging instance of the plugin around until it crashes. However, this debugging instance makes xfce4-panel CPU usage shoot up to 90%, which slows down my system and has my fan spinning like mad the whole time. It can be days until the bug bites again and it would be rather uncomfortable to keep using my system like this. If there is any alternative that doesn't bring my CPU to its knees I am willing to try it. Thanks, anyway. Regarding my previous post, apparently I had two xfce4-panel processes and the one burning my CPU was an old one, probably from when I was fiddling trying to get the debugging version of the plugin into the panel. Now it seems to be ok, so I'll keep it around and see if I can get back to you with some useful info. Cheers. The plugin definitely is a little crashy, so any info you could deliver is highly appreciated. TIA. This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. 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 '10'. 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 10'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 10 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 This was fixed a long time ago in 0.5.2-1.fc10, however I have no intentions to push this version to Fedora 10. Please upgrade to a newer release as the support for Fedora 10 is going to end soon. |