Bug 5376 - xmoto help menu causes mouse cursor related locks to appear
Summary: xmoto help menu causes mouse cursor related locks to appear
Status: RESOLVED INVALID
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/r300 (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
: 8299 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-12-19 00:42 UTC by Aapo Tahkola
Modified: 2009-11-04 11:39 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments

Description Aapo Tahkola 2005-12-19 00:42:25 UTC 
Moving mouse around when this menu is open locks my box hard.
I have reproduced this over five times in a row.
SWcursor seems to fix this problem.

http://www.rasterburn.org/~aet/menu.png
Comment 1 Aapo Tahkola 2006-09-17 07:41:09 UTC 
*** Bug 8299 has been marked as a duplicate of this bug. ***
Comment 2 Michel Dänzer 2006-09-18 06:06:38 UTC 
Is this with MergedFB enabled or disabled? Does disabling SilkenMouse also work
around it?
Comment 3 Aapo Tahkola 2006-09-18 06:52:40 UTC 
(In reply to comment #2)
> Is this with MergedFB enabled or disabled?

Enabled. Even with cloned displays.

> Does disabling SilkenMouse also work around it?

With xmoto-0.1.14 it would seem to.

Haven't been able to reproduce this with xmoto-0.2.1 . Probably due to the stats
bar on the right...

And yes, I believe this is the same bug that Vladimir experienced.
Comment 4 Michel Dänzer 2006-09-18 07:22:48 UTC 
(In reply to comment #3)
> > Is this with MergedFB enabled or disabled?
> 
> Enabled. Even with cloned displays.

If it doesn't happen with MergedFB disabled, then I'd guess it's related to
RADEONChooseCursorCRTC().
Comment 5 Matthias Bläsing 2006-09-18 11:23:00 UTC 
Followup from Bug 8299:

There blender locks the display and either -nosilk when starting X, setting
SWCursor in xorg.conf or running with MergedFramebuffer disabled prevents it.
Comment 6 Aapo Tahkola 2006-09-18 18:32:11 UTC 
(In reply to comment #5)
> Followup from Bug 8299:
> 
> There blender locks the display and either -nosilk when starting X, setting
> SWCursor in xorg.conf or running with MergedFramebuffer disabled prevents it.

Both SilkenMouse and SWCursor work for me with blender.
Comment 7 Michel Dänzer 2006-09-19 08:25:02 UTC 
My guess would be the card doesn't like getting hammered on
RADEON_CRTC2_GEN_CNTL. Maybe you guys can play with making
RADEONChooseCursorCRTC() a little cleverer wrt that.
Comment 8 Maciej Cencora 2009-06-07 15:58:20 UTC 
Is this still an issue?
Comment 9 Maciej Cencora 2009-11-04 11:39:37 UTC 
Closing due to lack of user feedback.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.