[Bug 71345] intel-virtual-output only updates mouse

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Nov 7 12:54:50 PST 2013


https://bugs.freedesktop.org/show_bug.cgi?id=71345

--- Comment #11 from Chris Wilson <chris at chris-wilson.co.uk> ---
(In reply to comment #10)
> Created attachment 88843 [details]
> KDE4 crash report
> 
> I did as you said in Comment 5 (git clone, compile, make&makeinstall) and
> then rebooted. Unfortunatelly -d -f didn't work as espected:
> >>>
> f.erfurth at Precision-M6600:~$ sudo optirun -c yuv true
> f.erfurth at Precision-M6600:~$ intel-virtual-output -d -f > i-v-o.txt
> Unable to connect to "-f".
> f.erfurth at Precision-M6600:~$ intel-virtual-output -f > i-v-o.txt
> ^Cf.erfurth at Precision-M6600:~$ cat i-v-o.txt
> f.erfurth at Precision-M6600:~$ 
> <<<
> 
> As you see... i-v-o.txt is empty. :/ I tried moving around any window in
> third screen but still no output.
> With -d I only got error 'Unable to connect to "-f"'. Maybe wrong
> parameters? Or am I missing somewhat?

Silly me. -f -v (-f == stay in foreground and don't detach, -v == verbose).

> Unfortunatelly I cannot send you dmesg and /sys/class/drm/card0/error
> because I rebooted my machine in the meanwhile. But its known issue which is
> already reported by someone else (Sorry I don't remember where...).
> Sometimes display is freezed for several seconds, but continued working then
> without problems.
> Of course I can provide you dmesg/error file if display freezes again if
> you'd like to see this.
> 
> Not sure if this is important for you:
> When I call `intel-virtual-output -f` I a crash-report-dialog appears.
> Please see attachment. Crash doesn't happens everytime but... the funny
> thing is... KDE4 is running well. Maybe KDE4 crashed on Display :8? Or its
> just any library.

No idea. Seems unrelated.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20131107/626de509/attachment.html>


More information about the intel-gfx-bugs mailing list