Bug#956811: cura: UI not usable because of OpenGL renderer
On Sat, Dec 26, 2020 at 11:19 PM Christoph Berg wrote: > > 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. > does the current version 4.8 still exhibit this problem? > > The 4.8.0 from the testing repository has the same issues and some additional, such as when choosing "Preview", the application dumps a core because of a segmentation fault. -- Peter Felecan
Bug#956811: [3dprinter-general] Bug#956811: cura: UI not usable because of OpenGL renderer
> does the current version 4.8 still exhibit this problem? For me at least, the UI is still broken in 4.8. If the issue was in fact fixed by https://github.com/Ultimaker/Cura/pull/7139 , it's not in 4.8 yet. That PR was only merged 19 days ago and 4.8 was released on Nov 27.
Bug#956811: cura: UI not usable because of OpenGL renderer
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@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. (0x) > Device: llvmpipe (LLVM 9.0.1, 256 bits) (0x) > 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
Bug#956811: [3dprinter-general] Bug#956811: cura: UI not usable because of OpenGL renderer
Re: Gregor Riepl > > I do not have much experience debugging OpenGL stuff either, but > > from the description I would say that this could be a bug in Cura, or > > it could be a bug in the OpenGL implementation for AMD VEGAM, whatever > > that is. Perhaps it is an idea to identify the package being used > > by X.org for this card, and pass the bug report over to them for > > comments is a way forward? > > It happens with Intel graphics as well, so I don't think it's a driver > issue. What issue are talking about here? Cura starts fine for me (X11): 2020-11-01 22:23:28,829 - DEBUG - [MainThread] UM.Qt.QtRenderer._initialize [210]: Support for Vertex Array Objects: True 2020-11-01 22:23:28,834 - DEBUG - [MainThread] UM.View.GL.OpenGL.__init__ [112]: Initialized OpenGL subsystems. 2020-11-01 22:23:28,834 - DEBUG - [MainThread] UM.View.GL.OpenGL.__init__ [113]: OpenGL Version: 4.6 (Core Profile) Mesa 20.1.9 2020-11-01 22:23:28,835 - DEBUG - [MainThread] UM.View.GL.OpenGL.__init__ [114]: OpenGL Vendor: Intel 2020-11-01 22:23:28,835 - DEBUG - [MainThread] UM.View.GL.OpenGL.__init__ [115]: OpenGL Renderer: Mesa Intel(R) Iris(R) Pro Graphics 580 (SKL GT4) 2020-11-01 22:23:28,835 - DEBUG - [MainThread] UM.View.GL.OpenGL.__init__ [116]: GLSL Version:4.60.0 2020-11-01 22:23:28,835 - DEBUG - [MainThread] UM.View.GL.ShaderProgram.load [58]: Loading shader file [/usr/share/uranium/resources/shaders/default.shader]... 2020-11-01 22:23:28,841 - DEBUG - [MainThread] UM.View.GL.ShaderProgram.load [58]: Loading shader file [/usr/share/uranium/resources/shaders/selection.shader]... 2020-11-01 22:23:28,842 - DEBUG - [MainThread] UM.View.GL.ShaderProgram.load [58]: Loading shader file [/usr/share/uranium/resources/shaders/select_face.shader]... 2020-11-01 22:23:28,842 - DEBUG - [MainThread] UM.View.GL.ShaderProgram.load [58]: Loading shader file [/usr/share/uranium/resources/shaders/default.shader]... 2020-11-01 22:23:28,843 - DEBUG - [MainThread] UM.View.GL.ShaderProgram.load [58]: Loading shader file [/usr/share/uranium/resources/shaders/composite.shader]... /usr/lib/python3/dist-packages/UM/Qt/QtRenderer.py:225: DeprecationWarning: tostring() is deprecated. Use tobytes() instead. data = numpy.array([ /usr/lib/python3/dist-packages/UM/Qt/QtRenderer.py:132: DeprecationWarning: an integer is required (got type float). Implicit conversion to integers using __int__ is deprecated, and may be removed in a future version of Python. self._gl.glViewport(0, 0, self._viewport_width, self._viewport_height) 2020-11-01 22:23:28,846 - DEBUG - [MainThread] UM.View.GL.ShaderProgram.load [58]: Loading shader file [/usr/share/cura/resources/shaders/overhang.shader]... 2020-11-01 22:23:28,847 - DEBUG - [MainThread] UM.View.GL.ShaderProgram.load [58]: Loading shader file [/usr/share/cura/resources/shaders/striped.shader]... 2020-11-01 22:23:28,848 - DEBUG - [MainThread] UM.View.GL.ShaderProgram.load [58]: Loading shader file [/usr/share/cura/resources/shaders/transparent_object.shader]... 2020-11-01 22:23:28,850 - DEBUG - [MainThread] UM.View.GL.ShaderProgram.load [58]: Loading shader file [/usr/share/cura/resources/shaders/striped.shader]... 2020-11-01 22:23:28,851 - DEBUG - [MainThread] UM.View.GL.ShaderProgram.load [58]: Loading shader file [/usr/share/cura/resources/shaders/xray.shader]... 2020-11-01 22:23:28,852 - DEBUG - [MainThread] UM.View.GL.ShaderProgram.load [58]: Loading shader file [/usr/share/cura/resources/shaders/xray_composite.shader]... 2020-11-01 22:23:28,853 - DEBUG - [MainThread] UM.View.GL.ShaderProgram.load [58]: Loading shader file [/usr/share/uranium/resources/shaders/default.shader]... 2020-11-01 22:23:28,854 - DEBUG - [MainThread] UM.View.GL.ShaderProgram.load [58]: Loading shader file [/usr/share/cura/resources/shaders/grid.shader]... 2020-11-01 22:23:28,855 - DEBUG - [MainThread] UM.View.GL.ShaderProgram.load [58]: Loading shader file [/usr/share/uranium/resources/shaders/platform.shader]... /usr/lib/python3/dist-packages/UM/View/GL/FrameBufferObject.py:18: DeprecationWarning: an integer is required (got type float). Implicit conversion to integers using __int__ is deprecated, and may be removed in a future version of Python. self._fbo = QOpenGLFramebufferObject(width, height, buffer_format) /usr/lib/python3/dist-packages/UM/View/GL/ShaderProgram.py:336: DeprecationWarning: an integer is required (got type float). Implicit conversion to integers using __int__ is deprecated, and may be removed in a future version of Python. QColor(value.r * 255, value.g * 255, value.b * 255, value.a * 255)) /usr/lib/python3/dist-packages/UM/Mesh/MeshData.py:238: DeprecationWarning: tostring() is deprecated. Use tobytes() instead. return self._vertices.tostring() 2020-11-01 22:23:28,869 - DEBUG - [MainThread] UM.View.GL.ShaderProgram.load [58]: Loading shader file [/usr/share/cura/resources/shaders/xray.shader]... 2020-11-01 22:23:29,034 - DEBUG - [Thread-7]
Bug#956811: [3dprinter-general] Bug#956811: cura: UI not usable because of OpenGL renderer
> I do not have much experience debugging OpenGL stuff either, but > from the description I would say that this could be a bug in Cura, or > it could be a bug in the OpenGL implementation for AMD VEGAM, whatever > that is. Perhaps it is an idea to identify the package being used > by X.org for this card, and pass the bug report over to them for > comments is a way forward? It happens with Intel graphics as well, so I don't think it's a driver issue.
Bug#956811: cura: UI not usable because of OpenGL renderer
I do not have much experience debugging OpenGL stuff either, but from the description I would say that this could be a bug in Cura, or it could be a bug in the OpenGL implementation for AMD VEGAM, whatever that is. Perhaps it is an idea to identify the package being used by X.org for this card, and pass the bug report over to them for comments is a way forward? -- Happy hacking Petter Reinholdtsen
Bug#956811: cura: UI not usable because of OpenGL renderer
Control: tag -1 help Re: Peter Felecan > The only difference that I found is the OpenGL renderer used in the 2 > situations: [...] > 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, I don't have experience in debugging this either, so the best I can do at the moment is to tag this bug "help". I'll be switching machines soon at home, so maybe if that problem pops up there as well, I'll have more insight... At the moment cura works for me. Christoph
Bug#956811: cura: UI not usable because of OpenGL renderer
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@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. (0x) Device: llvmpipe (LLVM 9.0.1, 256 bits) (0x) 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. Thank you in advance -- System Information: Debian Release: bullseye/sid APT prefers bullseye APT policy: (500, 'bullseye') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF8), LANGUAGE=en_US (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cura depends on: ii cura-engine 1:4.5.0-2+b1 ii fdm-materials 4.5.0-1 ii fonts-open-sans 1.11-1 ii python3 3.8.2-2 ii python3-charon 4.5.0-1 ii python3-pyqt5 5.14.2+dfsg-1 ii python3-pyqt5.qtopengl 5.14.2+dfsg-1 ii python3-requests2.23.0+dfsg-2 ii python3-savitar 4.5.0-1+b1 ii python3-serial 3.4-5.1 ii python3-shapely 1.7.0-1 ii python3-uranium 4.5.0-1 ii qml-module-qt-labs-folderlistmodel 5.12.5-5 ii qml-module-qt-labs-settings 5.12.5-5 ii qml-module-qtqml-models25.12.5-5 ii qml-module-qtquick-controls 5.12.5-1+b1 ii qml-module-qtquick-controls25.12.5+dfsg-2+b1 ii qml-module-qtquick-dialogs 5.12.5-1+b1 ii uranium-plugins 4.5.0-1 Versions of packages cura recommends: ii python3-zeroconf 0.23.0-1 cura suggests no packages. -- no debconf information
