[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [neon] [Bug 365678] Massive flicker and repaint problems with Neon 5.7 on remote X
From:       Jan-Marek Glogowski via KDE Bugzilla <bugzilla_noreply () kde ! org>
Date:       2016-08-01 13:21:42
Message-ID: bug-365678-17878-SCjIK5AcL0 () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=365678

--- Comment #14 from Jan-Marek Glogowski <glogow@fbihome.de> ---
So this time I can confirm, that "Alt + Shift + F12" stops the compositing and
the flickering.
Guess I hit the wrong key combo last time, or I had a different problem, but
xsession-errors and dmesg show almost the same messages:

Today:
[18199.442243] radeon 0000:01:00.0: r600_check_texture_resource:1566 tex pitch
(888, 0x40, 1) invalid
[18199.442334] [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream !

Previous:
[26610.825302] radeon 0000:01:00.0: r600_check_texture_resource:1566 tex pitch
(792, 0x40, 1) invalid
[26610.825349] [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream !

What's the preferred way to set a different QT_MESSAGE_PATTERN? Edit startkde?

Guess the example from the Qt docs is ok for you: QT_MESSAGE_PATTERN="[%{type}]
%{appname} (%{file}:%{line}) - %{message}"

This proves my theory about the "late at day" is wrong, as I neither installed
new software, nor intensively used the system. Actually this time it happened
almost instantly after the first start of LO, when opening a dialog.

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]