<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:freedesktop-bugs@PaulSD.com" title="Paul Donohue <freedesktop-bugs@PaulSD.com>"> <span class="fn">Paul Donohue</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTOURBUG - [GM45 SNA] No screen updates in some programs on Ubuntu 13.10"
href="https://bugs.freedesktop.org/show_bug.cgi?id=71171">bug 71171</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEEDINFO
</td>
<td>RESOLVED
</td>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>NOTOURBUG
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTOURBUG - [GM45 SNA] No screen updates in some programs on Ubuntu 13.10"
href="https://bugs.freedesktop.org/show_bug.cgi?id=71171#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTOURBUG - [GM45 SNA] No screen updates in some programs on Ubuntu 13.10"
href="https://bugs.freedesktop.org/show_bug.cgi?id=71171">bug 71171</a>
from <span class="vcard"><a class="email" href="mailto:freedesktop-bugs@PaulSD.com" title="Paul Donohue <freedesktop-bugs@PaulSD.com>"> <span class="fn">Paul Donohue</span></a>
</span></b>
<pre>I've found the problem.
I always run X via `startx` from a terminal instead of using a graphical login
manager. In 13.04, ConsoleKit was used to manage session-based permissions,
and /etc/X11/Xsession.d/90consolekit took care of preparing a ConsoleKit
session via `ck-launch-session` when X is started via `startx` instead of a
graphical login manager. In 13.10, ConsoleKit was replaced with
systemd-logind, but nothing was done to ensure that X sessions started via
`startx` are properly managed via systemd-logind.
Everything works fine (with either the old or new xf86-video-intel) after
replacing my /etc/X11/xinit/xserverrc with:
#!/bin/bash
TTY="${TTY:-$(tty)}"
TTY="${TTY#/dev/}"
if [[ $TTY != tty* ]]; then
printf '==> ERROR: invalid TTY\n' >&2
exit 1
fi
printf -v VT 'vt%02d' "${TTY#tty}"
exec /usr/bin/X -nolisten tcp -dpi 100 "$VT" "$@"
(This script came from
<a href="http://blog.falconindy.com/articles/back-to-basics-with-x-and-systemd.html">http://blog.falconindy.com/articles/back-to-basics-with-x-and-systemd.html</a>)
Reverting to the original xserverrc brings back the previous rendering issues
again, so I'm confident that this is the issue.
I'm not sure how PolicyKit has anything to do with rendering, but clearly it
does. (If anything, I would expect hardware rendering to fail entirely ... not
to fail in some cases and work fine in others.) Is PolicyKit known to impact
rendering behavior like this?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>