[3dprinter-general] Bug#956811: cura: UI not usable because of OpenGL renderer
Christoph Berg
myon at debian.org
Sat Dec 26 22:19:46 GMT 2020
Re: Peter Felecan
> Package: cura
> Version: 4.5.0-1
> Severity: important
>
> Dear maintainers,
>
> I have a very annoying behavior since a long time but only recently I
> understood the origin of the problem. By the way, it's similar to the
> bug report #951033 "cura: UI not usable in 4.4.1" by having a garbled
> user interface, with buttons not sown and other annoying issues.
>
> The problem appear when logged in my graphical session, KDE
> Plasma. However, when I open a session through ssh, for example
> "ssh -X myself at localhost" the problem disappears and I have a well
> behaved user interface.
>
> The only difference that I found is the OpenGL renderer used in the 2
> situations:
>
> 1. When I'm connected in my graphical session, the renderer is, as
> provided by 'glxinfo':
>
> Vendor: X.Org (0x1002)
> Device: AMD VEGAM (DRM 3.35.0, 5.4.0-4-amd64, LLVM 9.0.1) (0x694e)
> Version: 19.3.3
> Accelerated: yes
> Video memory: 4096MB
> Unified memory: no
> Preferred profile: core (0x1)
> Max core profile version: 4.5
> Max compat profile version: 4.5
> Max GLES1 profile version: 1.1
> Max GLES[23] profile version: 3.2
>
> 2. When I open a session, in the same graphical environment but
> through ssh, as shown above, the renderer is, as provided by
> 'glxinfo':
>
> Vendor: VMware, Inc. (0xffffffff)
> Device: llvmpipe (LLVM 9.0.1, 256 bits) (0xffffffff)
> Version: 19.3.3
> Accelerated: no
> Video memory: 32104MB
> Unified memory: no
> Preferred profile: core (0x1)
> Max core profile version: 3.3
> Max compat profile version: 3.1
> Max GLES1 profile version: 1.1
> Max GLES[23] profile version: 3.1
>
> My conclusion is that the Cura user interface is not working correctly
> when the renderer used is the one provided by my GPU but works
> correctly on a software renderer.
>
> Unfortunately I do not have enough experience in the OpenGL context
> but willing to provide more information to or try experiments from
> more experienced users.
Hi Peter,
does the current version 4.8 still exhibit this problem?
Christoph
More information about the 3dprinter-general
mailing list