Bug 196953
| Summary: | xchat stops responding during notification | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | simon |
| Component: | xchat-gnome | Assignee: | Brian Pepple <bdpepple> |
| Status: | CLOSED CANTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5 | CC: | extras-qa |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2006-09-24 16:55:45 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
simon
2006-06-27 20:01:05 UTC
Could you you run the following: 'gconftool-2 -g /apps/xchat/plugins/loaded', and provide me with the results? gconf output: [/usr/lib/xchat-gnome/plugins/netmonitor.so,/usr/lib/xchat-gnome/plugins/notification.so,/usr/lib/xchat-gnome/plugins/notifyosd.so,/usr/lib/xchat-gnome/plugins/dbus.so] A little bit more info. If somebody says "hi somenick" where somenick is my nick, then a message appears on screen saying "message in roomname". If xchat is running in a different desktop, then all is well. However, if it is iin the current desktop, that is when the problem occurs. When the on-screen message appears, it stays there until somebody speaks in irc. Until then, I am unable to do anything. The mouse and keyboard do not have any effect on my desktop. I am not sure whether xchat needs to be in focus or not, but I am pretty sure the channnel the message is related to needs to be open. Usually I talking in irc, then swtich to reading a webpage until somebody speaks. Are you still experiencing this problem with the latest version? I've been unable to reproduce this bug. I have been running with the OSD disabled to avoid the problem. I have now re-enabled it and will report back. I've had no re-occurance of this issue. Ok, I'll close it for now then, since I've been unable to reproduce this. If you experience it again, it can always be reopened. |