[kwin] [Bug 403390] Activation of compositor causes endless resetting [drm] GPU on Raspberry Pi 2B

2019-01-21 Thread Michael Grosskopf
https://bugs.kde.org/show_bug.cgi?id=403390

--- Comment #6 from Michael Grosskopf  ---
p, li { white-space: pre-wrap; }
If it is interesting for you to see this working, there is an option to 

connect by TeamViewer or Remote-Desktop.

I am in Bangkok, -appointment required- to make sure that the internet is 

connected. (connected to a not very fast Hotspot via USB-dongle in the 

apartment house. It drops sometimes)

Just let me know.








-Original Message-
From: Martin Flöser 
To: mikegrosskopf 
Sent: Sun, Jan 20, 2019 6:58 pm
Subject: [kwin] [Bug 403390] Activation of compositor causes endless resetting
[drm] GPU on Raspberry Pi 2B

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

--- Comment #5 from Martin Flöser  ---
I cannot change the fact that the gpu is crap. Sorry. If we get graphics reset
errors it means the driver has an issue and not that our code has issues.

I intensively tested KWin on the raspberry pi. I even tested with customized
setups not running the de, but just KWin. It's just not up to the task. The gpu
hard froze when switching a window to fullscreen.

I would love to be able to run Plasma on it, but it's just not possible.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 403390] Activation of compositor causes endless resetting [drm] GPU on Raspberry Pi 2B

2019-01-20 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=403390

--- Comment #5 from Martin Flöser  ---
I cannot change the fact that the gpu is crap. Sorry. If we get graphics reset
errors it means the driver has an issue and not that our code has issues.

I intensively tested KWin on the raspberry pi. I even tested with customized
setups not running the de, but just KWin. It's just not up to the task. The gpu
hard froze when switching a window to fullscreen.

I would love to be able to run Plasma on it, but it's just not possible.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 403390] Activation of compositor causes endless resetting [drm] GPU on Raspberry Pi 2B

2019-01-19 Thread Michael Grosskopf
https://bugs.kde.org/show_bug.cgi?id=403390

--- Comment #4 from Michael Grosskopf  ---
On Saturday, 19 January 2019 16:52:35 +07 you wrote:
> https://bugs.kde.org/show_bug.cgi?id=403390
> 
> Martin Fl?ser  changed:
> 
>What|Removed |Added
> 
> Resolution|WAITINGFORINFO  |UPSTREAM
>  Status|NEEDSINFO   |RESOLVED
> 
> --- Comment #3 from Martin Fl?ser  ---
> The raspberry pi has a very bad gpu to say it friendly. It's not possible to
> run a de like plasma on it. Sorry.
Martin.

I have written my experience with a flying pig, so why are you telling me that 
pigs can't fly?  ;-)

I am sorry too. Please read the whole report again.
I wrote that this system is working 24/7, I reported some flaws I encountered 
during setup.
The report should be helpful for developers and possibly for people who want 
to switch from "Windoofs" to Linux. Don't turn them off.
I enjoy using KDE, having just one UI, so that every user in my network does 
not need to become familiar with different desktops.
I can access this pi from the local network as well as via internet. 
Kontact has an archive mail-folder on a partition of a USB-Drive, which can be 
mounted/accessed by sshfs  on every further machine with KDE

The keys to get KDE running on Raspberry (reduce X11-spamming and usage of 
Zram) have been explained in my report.

Regards

Mike

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 403390] Activation of compositor causes endless resetting [drm] GPU on Raspberry Pi 2B

2019-01-19 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=403390

Martin Flöser  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |UPSTREAM
 Status|NEEDSINFO   |RESOLVED

--- Comment #3 from Martin Flöser  ---
The raspberry pi has a very bad gpu to say it friendly. It's not possible to
run a de like plasma on it. Sorry.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 403390] Activation of compositor causes endless resetting [drm] GPU on Raspberry Pi 2B

2019-01-19 Thread Michael Grosskopf
t: 10

font: Noto Sans,10,-1,5,50,0,0,0,0,0

smallSpacing: 2

largeSpacing: 10




Options

===

focusPolicy: 0

nextFocusPrefersMouse: false

clickRaise: true

autoRaise: false

autoRaiseInterval: 0

delayFocusInterval: 0

shadeHover: false

shadeHoverInterval: 250

separateScreenFocus: false

placement: 4

focusPolicyIsReasonable: true

borderSnapZone: 10

windowSnapZone: 10

centerSnapZone: 0

snapOnlyWhenOverlapping: false

rollOverDesktops: false

focusStealingPreventionLevel: 1

legacyFullscreenSupport: false

operationTitlebarDblClick: 5000

operationMaxButtonLeftClick: 5000

operationMaxButtonMiddleClick: 5015

operationMaxButtonRightClick: 5014

commandActiveTitlebar1: 0

commandActiveTitlebar2: 30

commandActiveTitlebar3: 2

commandInactiveTitlebar1: 4

commandInactiveTitlebar2: 30

commandInactiveTitlebar3: 2

commandWindow1: 7

commandWindow2: 8

commandWindow3: 8

commandWindowWheel: 31

commandAll1: 10

commandAll2: 3

commandAll3: 14

keyCmdAllModKey: 16777251

showGeometryTip: false

condensedTitle: false

electricBorderMaximize: false

electricBorderTiling: false

electricBorderCornerRatio: 0.25

borderlessMaximizedWindows: false

killPingTimeout: 5000

hideUtilityWindowsForInactive: true

inactiveTabsSkipTaskbar: false

autogroupSimilarWindows: false

autogroupInForeground: true

compositingMode: 1

useCompositing: true

compositingInitialized: true

hiddenPreviews: 1

glSmoothScale: 0

colorCorrected: false

xrenderSmoothScale: false

maxFpsInterval: 1666

refreshRate: 0

vBlankTime: 600

glStrictBinding: false

glStrictBindingFollowsDriver: true

glCoreProfile: false

glPreferBufferSwap: 101

glPlatformInterface: 2

windowsBlockCompositing: false




Screen Edges



desktopSwitching: false

desktopSwitchingMovingClients: false

cursorPushBackDistance: 1x1

timeThreshold: 150

reActivateThreshold: 350

actionTopLeft: 0

actionTop: 0

actionTopRight: 0

actionRight: 0

actionBottomRight: 0

actionBottom: 0

actionBottomLeft: 0

actionLeft: 0




Screens

===

Multi-Head: no

Active screen follows mouse: no

Number of Screens: 1




Screen 0:

-

Name: HDMI-1

Geometry: 0,0,1360x768

Refresh Rate: 59.9493







Compositing

===

Compositing is active

Compositing Type: OpenGL ES 2.0

OpenGL vendor string: Broadcom

OpenGL renderer string: Gallium 0.4 on VC4 V3D 2.1

OpenGL version string: OpenGL ES 2.0 Mesa 13.0.6

OpenGL platform interface: EGL

OpenGL shading language version string: OpenGL ES GLSL ES 1.0.16

Driver: Unknown

GPU class: Unknown

OpenGL version: 2.0

GLSL version: 1.0.16

Mesa version: 13.0.6

X server version: 1.19.2

Linux kernel version: 4.14.79

Direct rendering: Requires strict binding: no

GLSL shaders: yes

Texture NPOT support: yes

Virtual Machine: no

OpenGL 2 Shaders are used

Painting blocks for vertical retrace: no




Loaded Effects:

---

screenshot

cubeslide

cube

highlightwindow

blur

contrast

startupfeedback

kscreen




Currently Active Effects:

-

blur

contrast




Effect Settings:



screenshot:




cubeslide:

rotationDuration: 1

dontSlidePanels: true

dontSlideStickyWindows: false

usePagerLayout: true

useWindowMoving: false




cube:

cubeOpacity: 0.80011920929

opacityDesktopOnly: false

displayDesktopName: true

reflection: true

rotationDuration: 1

backgroundColor: #00

capColor: #eff0f1

paintCaps: true

closeOnMouseRelease: false

zPosition: 100

useForTabBox: false

invertKeys: false

invertMouse: false

capDeformationFactor: 0

useZOrdering: false

texturedCaps: true




highlightwindow:




blur:

blurRadius: 12

cacheTexture: true




contrast:




startupfeedback:

type: 1




kscreen:

___

first visible effect after enabling: conky background is transparent

I have reset the system immediately after the test to "unticked"

>From earlier tests I know that even 'cube' is working on this system, but as 

mentioned, every mouse action causes a long resetting of [drm]GPU. Especially 

changing a wireless network or other clicks in the panel are blocking the 

usage for minutes.

Please let me know whether you need more details. I can do some tests if that 

would help. As emphasized before, I don't need the effects. It is just about 

how other people will react, when coming from Windows and trying to setting up 

Linux with such effects.

Regards

Mike 





-Original Message-----
From: David Edmundson 
To: mikegrosskopf 
Sent: Sat, Jan 19, 2019 9:05 pm
Subject: [kwin] [Bug 403390] Activation of compositor causes endless resetting
[drm] GPU on Raspberry Pi 2B

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

David Edmundson  changed:

          What    |Removed                    |Added

        Resolution|---      

[kwin] [Bug 403390] Activation of compositor causes endless resetting [drm] GPU on Raspberry Pi 2B

2019-01-19 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=403390

David Edmundson  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|REPORTED|NEEDSINFO
 CC||k...@davidedmundson.co.uk
   Severity|critical|normal

--- Comment #1 from David Edmundson  ---
>kwin version: 8.5.6

Can you check this please.

>1. tick the box 'enable Compositor at startup' in System Settings

What was the default out of the box state?


Please include output of:
qdbus org.kde.KWin /KWin org.kde.KWin.supportInformation

-- 
You are receiving this mail because:
You are watching all bug changes.