Date: Tue, 9 Oct 2012 14:28:54 -0700 (PDT) From: "Ronald F.Guilmette" <rfg@tristatelogic.com> To: FreeBSD-gnats-submit@FreeBSD.org Cc: rfg@tristatelogic.com Subject: ports/172548: ports/xbmc wrong rasterizer selected when run as non-root Message-ID: <20121009212854.7E97350844@segfault.tristatelogic.com> Resent-Message-ID: <201210092230.q99MUQRR043700@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 172548 >Category: ports >Synopsis: ports/xbmc wrong rasterizer selected when run as non-root >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Oct 09 22:30:25 UTC 2012 >Closed-Date: >Last-Modified: >Originator: Ronald F. Guilmette >Release: FreeBSD 9.0-RELEASE amd64 >Organization: entr0py >Environment: FreeBSD 9.0-RELEASE amd64 >Description: NOTE: I have never before filed a FreeBSD PR with Severity=critical and Priority=high, but I do think that it is warranted in this case, because xbmc is utterly unusable (by any non-root user) due to this issue/problem/bug. As described in this thread: http://forum.xbmc.org/showthread.php?tid=133221 (see both pages of it, please) when xbmc is executed as an ordinary user, for some reason it chooses the built-in _software_ rasterizer, and this choice makes xbmc run as slow as old dog. However for equally unknown reasons, when xbmc is executed under root, the correct (hardrware) rasterizer is selected, and in that case, performance of xbmc is normal. (Note that it was *not* just ne who reported this problematic behavior. Somebody else did first, and that somebody else is, I would guess, probably running xbmc under Linux... so I would also guess that this problem in xbmc is not even FreeBSD-specific.) Anyway, I have verified this exact behavior under FreeBSD 9.0 on two different platforms... one with an AMD cpu and ATI graphics, and another with an Intel CPU and Intel graphics. So it is clearly not hardware dependent. It is however clearly a permissions problem lurking somwhere. (I don't know enough about xbmc, or Mesa, or DRI to even begin to guess where.) >How-To-Repeat: portinstall --batch xbmc {log in as normal user} xbmc {notice now how slow & unresponsive mouse is now} su root {give root password} xbmc {notice how now, xbmc runs at a reasonable rate & mouse is responsive} >Fix: I have no idea how to fix this. I am hoping and praying that the FreeBSD port maintainer for xbmc will send me a fix. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20121009212854.7E97350844>