Bug 695438
| Summary: | spice client hangs because it waits for IO from xserver | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | David Jaša <djasa> | ||||
| Component: | libxcb | Assignee: | Søren Sandmann Pedersen <sandmann> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | desktop-bugs <desktop-bugs> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 6.2 | CC: | hdegoede, kem, sandmann, spice-qe-bugs | ||||
| Target Milestone: | rc | Keywords: | Triaged | ||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-04-12 07:19:49 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: |
|
||||||
CCing Hans because this might also be a spice-client issue This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative. Hmm, This sound a lot like a dup of bug 692833, was xorg perhaps using a lot of CPU at the time this happened? If spicec goes into an endless self triggered event loop, the traceback will look likely like what you see, because most of the time (99%) it will be in XReply. Regards, Hans (In reply to comment #4) > Hmm, > > This sound a lot like a dup of bug 692833, was xorg perhaps using a lot of CPU > at the time this happened? I'm not sure about this, as I was changing my resolution back and "quad" core easily hides a single cpu-intensive thread. (In reply to comment #5) > (In reply to comment #4) > > Hmm, > > > > This sound a lot like a dup of bug 692833, was xorg perhaps using a lot of CPU > > at the time this happened? > > I'm not sure about this, as I was changing my resolution back and "quad" core > easily hides a single cpu-intensive thread. I'm pretty sure this is a dup, given that switching to / from fullscreen is what triggered it. Marking it as a dup. *** This bug has been marked as a duplicate of bug 692833 *** |
Created attachment 491305 [details] hang backtrace Description of problem: Version-Release number of selected component (if applicable): spice-client-0.8.0-2.el6.x86_64 spice-xpi-2.4-4.el6.x86_64 xorg-x11-server-Xorg-1.7.7-28.el6.x86_64 libxcb-1.5-1.el6.x86_64 How reproducible: didn't manage to reproduce with steps that led to hang Steps to Reproduce: 1. using User Portal, open spice connection to guest that doesn' have guest tools installed 2. hit shift-F11 to enter fullscreen and shift-F11 again to revert back to windowed mode 3. Actual results: spicec hangs and resolution is left to guest's one Expected results: spicec continues normal operation and resolution reverts to client's original one Additional info: