# A few problems with Slicer 4.13
**URL:** https://discourse.slicer.org/t/a-few-problems-with-slicer-4-13/13973
**Category:** Support
**Created:** [October 10, 2020, 2:17pm UTC](https://discourse.slicer.org/t/a-few-problems-with-slicer-4-13/13973 "2020-10-10T14:17:34Z")
**Posts on this page:** 13
**Page:** 1
### Author:  [@chir.set](https://discourse.slicer.org/u/chir.set)
#### Post date: [October 10, 2020, 2:17pm UTC](https://discourse.slicer.org/t/a-few-problems-with-slicer-4-13/13973/1 "2020-10-10T14:17:34Z")
I know you are in a big process of upgrading Slicer with VTK9 in particular, and some runtime problems can be expected. Just reporting what I found so far on Arch Linux / Qt 5.15.1.
Factory built Slicer
1. Only Slicer appearence themes are proposed in Application Settings, and not system themes like Breeze and Oxygen.
2. 2D slice views are black empty.
Home built Slicer
1. 2D slice views are black empty.
2. Rotating 3D view with left mouse button down changes window state from maximized to ‘restored’ without rotating the view. When left mouse button is released, moving around the mouse rotates the view. Please see [attached](https://yadi.sk/i/gy3Iu-Z6JfrhvQ) screen capture.
In both cases, no particular error messages are in console or python console. In case it might be useful :
```
Session start time .......: 2020-10-10 15:47:57
Slicer version ...........: 4.13.0-2020-10-09 (revision 29425 / 5da4da2) linux-amd64 - installed release
Operating system .........: Linux / 5.9.0-rc7-git / #161 SMP Sun Oct 4 10:49:07 CEST 2020 - 64-bit
Memory ...................: 15018 MB physical, 15359 MB virtual
CPU ......................: AuthenticAMD AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx, 4 cores, 8 logical processors
VTK configuration ........: OpenGL2 rendering, Sequential threading
Qt configuration .........: version 5.15.1, with SSL, requested OpenGL 3.2 (core profile)
Developer mode enabled ...: yes
Prefer executable CLI ....: no
Application path .........: /home/user/programs/Slicer-4.13.0-2020-10-09-linux-amd64/bin
Additional module paths ..: (none)
Reversing DICOM dictionary so can look up tag from a keyword...
Scripted subject hierarchy plugin registered: Annotations
Scripted subject hierarchy plugin registered: SegmentEditor
DeserializeTerminologyEntry: Invalid type component
Scripted subject hierarchy plugin registered: SegmentStatistics
Switch to module: "Volumes"
Assertion `this->Table->columnWidth(j) == newWidth` failed in /home/arc/src/Slicer-SuperBuild/CTK/Libs/Widgets/ctkMatrixWidget.cpp line 242
Assertion `this->Table->columnWidth(j) == newWidth` failed in /home/arc/src/Slicer-SuperBuild/CTK/Libs/Widgets/ctkMatrixWidget.cpp line 242
...
Loading Slicer RC file [/home/user/.slicerrc.py]
Loaded volume from file: /home/user/Desktop/BIG/Slicer/CTA-cardio.nrrd. Dimensions: 512x512x321. Number of components: 1. Pixel type: short.
"Volume" Reader has successfully read the file "/home/user/Desktop/BIG/Slicer/CTA-cardio.nrrd" "[1.04s]"
```
---
### Author:  [@chir.set](https://discourse.slicer.org/u/chir.set)
#### Post date: [October 10, 2020, 2:39pm UTC](https://discourse.slicer.org/t/a-few-problems-with-slicer-4-13/13973/2 "2020-10-10T14:39:18Z")
This line appears in console when trying to move around the 3D view :
> QGestureManager::deliverEvent: could not find the target for gesture
---
### Author:  [@lassoan](https://discourse.slicer.org/u/lassoan)
#### Post date: [October 10, 2020, 3:31pm UTC](https://discourse.slicer.org/t/a-few-problems-with-slicer-4-13/13973/3 "2020-10-10T15:31:50Z")
> [@chir.set](#):
>
> Only Slicer appearence themes are proposed in Application Settings, and not system themes like Breeze and Oxygen.
“Slicer” uses default color palette that we get from Qt, while “Dark Slicer” and “Light Slicer” are color palettes defined by Slicer. Qt capabilities for getting colors from system theme are different depending on the operating system and we also need to do some overrides for colors that don’t make sense. As Qt improves dark mode support on all operating systems, Slicer will improve, too.
> [@chir.set](#):
>
> 2D slice views are black empty.
Yes, we know about this - [https://github.com/Slicer/Slicer/issues/5220](https://github.com/Slicer/Slicer/issues/5220)
> [@chir.set](#):
>
> Rotating 3D view with left mouse button down changes window state from maximized to ‘restored’ without rotating the view. When left mouse button is released, moving around the mouse rotates the view. Please see [attached](https://yadi.sk/i/gy3Iu-Z6JfrhvQ) screen capture.
What Qt version do you use? Linux requires very latest Qt (5.15.1), as Wayland support in previous versions was very buggy.
---
### Author:  [@chir.set](https://discourse.slicer.org/u/chir.set)
#### Post date: [October 10, 2020, 3:59pm UTC](https://discourse.slicer.org/t/a-few-problems-with-slicer-4-13/13973/4 "2020-10-10T15:59:16Z")
> [@lassoan](#):
>
> What Qt version do you use?
I’m indeed using Qt 5.15.1.
I must add that this 3D view rotating issue described above is observed in KDE X11 only. The view rotates normally in KDE Wayland, and the main window is not restored.
---
### Author:  [@lassoan](https://discourse.slicer.org/u/lassoan)
#### Post date: [October 10, 2020, 5:42pm UTC](https://discourse.slicer.org/t/a-few-problems-with-slicer-4-13/13973/5 "2020-10-10T17:42:34Z")
Probably a few X11 bugs were introduced as they fixed the Wayland bugs. Probably these errors will be fixed in upcoming patch releases. What is interesting that the problem does not occur with the official build. Can you copy-paste here the application log of running Slicer that you have built?
---
### Author:  [@chir.set](https://discourse.slicer.org/u/chir.set)
#### Post date: [October 10, 2020, 6:38pm UTC](https://discourse.slicer.org/t/a-few-problems-with-slicer-4-13/13973/6 "2020-10-10T18:38:52Z")
> [@lassoan](#):
>
> the application log
I’m afraid I need some precision here.
Do you refer to console stdout messages ? Error log in Slicer UI (Ctrl+0) ? Some other source of messages ?
---
### Author:  [@lassoan](https://discourse.slicer.org/u/lassoan)
#### Post date: [October 10, 2020, 6:49pm UTC](https://discourse.slicer.org/t/a-few-problems-with-slicer-4-13/13973/7 "2020-10-10T18:49:02Z")
I mean the same log for your custom-built Slicer, as you posted before for the installed Slicer (available from menu: Help / Report a bug).
---
### Author:  [@chir.set](https://discourse.slicer.org/u/chir.set)
#### Post date: [October 10, 2020, 7:06pm UTC](https://discourse.slicer.org/t/a-few-problems-with-slicer-4-13/13973/8 "2020-10-10T19:06:17Z")
Here is the log from ‘Help/Report a bug’ after loading CTA-Cardio, Volume Rendering, moving the 3D view and closing the scene.
> [DEBUG][Qt] 10.10.2020 20:59:17 (unknown:0) - Session start time …: 2020-10-10 20:59:17
> [DEBUG][Qt] 10.10.2020 20:59:17 (unknown:0) - Slicer version …: 4.13.0-2020-10-09 (revision 29425 / 5da4da2) linux-amd64 - installed release
> [DEBUG][Qt] 10.10.2020 20:59:17 (unknown:0) - Operating system …: Linux / 5.9.0-rc7-git / #161 SMP Sun Oct 4 10:49:07 CEST 2020 - 64-bit
> [DEBUG][Qt] 10.10.2020 20:59:17 (unknown:0) - Memory …: 15018 MB physical, 15359 MB virtual
> [DEBUG][Qt] 10.10.2020 20:59:17 (unknown:0) - CPU …: AuthenticAMD AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx, 4 cores, 8 logical processors
> [DEBUG][Qt] 10.10.2020 20:59:17 (unknown:0) - VTK configuration …: OpenGL2 rendering, Sequential threading
> [DEBUG][Qt] 10.10.2020 20:59:17 (unknown:0) - Qt configuration …: version 5.15.1, with SSL, requested OpenGL 3.2 (core profile)
> [DEBUG][Qt] 10.10.2020 20:59:17 (unknown:0) - Developer mode enabled …: yes
> [DEBUG][Qt] 10.10.2020 20:59:17 (unknown:0) - Prefer executable CLI …: no
> [DEBUG][Qt] 10.10.2020 20:59:17 (unknown:0) - Application path …: /home/user/programs/Slicer-4.13.0-2020-10-09-linux-amd64/bin
> [DEBUG][Qt] 10.10.2020 20:59:17 (unknown:0) - Additional module paths …: (none)
> [DEBUG][Python] 10.10.2020 20:59:18 [Python] (/home/user/programs/Slicer-4.13.0-2020-10-09-linux-amd64/lib/Python/lib/python3.6/site-packages/pydicom/datadict.py:432) - Reversing DICOM dictionary so can look up tag from a keyword…
> [DEBUG][Python] 10.10.2020 20:59:20 [Python] (/home/user/programs/Slicer-4.13.0-2020-10-09-linux-amd64/lib/Slicer-4.13/qt-scripted-modules/SubjectHierarchyPlugins/AbstractScriptedSubjectHierarchyPlugin.py:36) - Scripted subject hierarchy plugin registered: Annotations
> [DEBUG][Python] 10.10.2020 20:59:21 [Python] (/home/user/programs/Slicer-4.13.0-2020-10-09-linux-amd64/lib/Slicer-4.13/qt-scripted-modules/SubjectHierarchyPlugins/AbstractScriptedSubjectHierarchyPlugin.py:36) - Scripted subject hierarchy plugin registered: SegmentEditor
> [ERROR][VTK] 10.10.2020 20:59:21 [vtkSlicerTerminologyEntry (0x563f5b35d670)] (/home/arc/src/Slicer/Modules/Loadable/Terminologies/Logic/vtkSlicerTerminologiesModuleLogic.cxx:2079) - DeserializeTerminologyEntry: Invalid type component
> [DEBUG][Python] 10.10.2020 20:59:21 [Python] (/home/user/programs/Slicer-4.13.0-2020-10-09-linux-amd64/lib/Slicer-4.13/qt-scripted-modules/SubjectHierarchyPlugins/AbstractScriptedSubjectHierarchyPlugin.py:36) - Scripted subject hierarchy plugin registered: SegmentStatistics
> [DEBUG][Qt] 10.10.2020 20:59:21 (unknown:0) - Switch to module: “Volumes”
> [WARNING][Qt] 10.10.2020 20:59:22 (unknown:0) - Assertion `this->Table->columnWidth(j) == newWidth` failed in /home/arc/src/Slicer-SuperBuild/CTK/Libs/Widgets/ctkMatrixWidget.cpp line 242
> [WARNING][Qt] 10.10.2020 20:59:22 (unknown:0) - Assertion `this->Table->columnWidth(j) == newWidth` failed in /home/arc/src/Slicer-SuperBuild/CTK/Libs/Widgets/ctkMatrixWidget.cpp line 242
> [WARNING][Qt] 10.10.2020 20:59:22 (unknown:0) - Assertion `this->Table->columnWidth(j) == newWidth` failed in /home/arc/src/Slicer-SuperBuild/CTK/Libs/Widgets/ctkMatrixWidget.cpp line 242
> [WARNING][Qt] 10.10.2020 20:59:22 (unknown:0) - Assertion `this->Table->columnWidth(j) == newWidth` failed in /home/arc/src/Slicer-SuperBuild/CTK/Libs/Widgets/ctkMatrixWidget.cpp line 242
> [WARNING][Qt] 10.10.2020 20:59:22 (unknown:0) - Assertion `this->Table->rowHeight(i) == newHeight` failed in /home/arc/src/Slicer-SuperBuild/CTK/Libs/Widgets/ctkMatrixWidget.cpp line 253
> [WARNING][Qt] 10.10.2020 20:59:22 (unknown:0) - Assertion `this->Table->rowHeight(i) == newHeight` failed in /home/arc/src/Slicer-SuperBuild/CTK/Libs/Widgets/ctkMatrixWidget.cpp line 253
> [WARNING][Qt] 10.10.2020 20:59:22 (unknown:0) - Assertion `this->Table->rowHeight(i) == newHeight` failed in /home/arc/src/Slicer-SuperBuild/CTK/Libs/Widgets/ctkMatrixWidget.cpp line 253
> [WARNING][Qt] 10.10.2020 20:59:22 (unknown:0) - Assertion `this->Table->rowHeight(i) == newHeight` failed in /home/arc/src/Slicer-SuperBuild/CTK/Libs/Widgets/ctkMatrixWidget.cpp line 253
> [WARNING][Qt] 10.10.2020 20:59:22 (unknown:0) - Assertion `this->Table->columnWidth(j) == newWidth` failed in /home/arc/src/Slicer-SuperBuild/CTK/Libs/Widgets/ctkMatrixWidget.cpp line 242
> [WARNING][Qt] 10.10.2020 20:59:22 (unknown:0) - Assertion `this->Table->columnWidth(j) == newWidth` failed in /home/arc/src/Slicer-SuperBuild/CTK/Libs/Widgets/ctkMatrixWidget.cpp line 242
> [WARNING][Qt] 10.10.2020 20:59:22 (unknown:0) - Assertion `this->Table->columnWidth(j) == newWidth` failed in /home/arc/src/Slicer-SuperBuild/CTK/Libs/Widgets/ctkMatrixWidget.cpp line 242
> [WARNING][Qt] 10.10.2020 20:59:22 (unknown:0) - Assertion `this->Table->rowHeight(i) == newHeight` failed in /home/arc/src/Slicer-SuperBuild/CTK/Libs/Widgets/ctkMatrixWidget.cpp line 253
> [WARNING][Qt] 10.10.2020 20:59:22 (unknown:0) - Assertion `this->Table->rowHeight(i) == newHeight` failed in /home/arc/src/Slicer-SuperBuild/CTK/Libs/Widgets/ctkMatrixWidget.cpp line 253
> [WARNING][Qt] 10.10.2020 20:59:22 (unknown:0) - Assertion `this->Table->rowHeight(i) == newHeight` failed in /home/arc/src/Slicer-SuperBuild/CTK/Libs/Widgets/ctkMatrixWidget.cpp line 253
> [WARNING][Qt] 10.10.2020 20:59:22 (unknown:0) - Assertion `this->Table->rowHeight(i) == newHeight` failed in /home/arc/src/Slicer-SuperBuild/CTK/Libs/Widgets/ctkMatrixWidget.cpp line 253
> [WARNING][Qt] 10.10.2020 20:59:22 (unknown:0) - Assertion `this->Table->columnWidth(j) == newWidth` failed in /home/arc/src/Slicer-SuperBuild/CTK/Libs/Widgets/ctkMatrixWidget.cpp line 242
> [WARNING][Qt] 10.10.2020 20:59:22 (unknown:0) - Assertion `this->Table->columnWidth(j) == newWidth` failed in /home/arc/src/Slicer-SuperBuild/CTK/Libs/Widgets/ctkMatrixWidget.cpp line 242
> [WARNING][Qt] 10.10.2020 20:59:22 (unknown:0) - Assertion `this->Table->columnWidth(j) == newWidth` failed in /home/arc/src/Slicer-SuperBuild/CTK/Libs/Widgets/ctkMatrixWidget.cpp line 242
> [WARNING][Qt] 10.10.2020 20:59:22 (unknown:0) - Assertion `this->Table->rowHeight(i) == newHeight` failed in /home/arc/src/Slicer-SuperBuild/CTK/Libs/Widgets/ctkMatrixWidget.cpp line 253
> [WARNING][Qt] 10.10.2020 20:59:22 (unknown:0) - Assertion `this->Table->rowHeight(i) == newHeight` failed in /home/arc/src/Slicer-SuperBuild/CTK/Libs/Widgets/ctkMatrixWidget.cpp line 253
> [WARNING][Qt] 10.10.2020 20:59:22 (unknown:0) - Assertion `this->Table->rowHeight(i) == newHeight` failed in /home/arc/src/Slicer-SuperBuild/CTK/Libs/Widgets/ctkMatrixWidget.cpp line 253
> [WARNING][Qt] 10.10.2020 20:59:22 (unknown:0) - Assertion `this->Table->rowHeight(i) == newHeight` failed in /home/arc/src/Slicer-SuperBuild/CTK/Libs/Widgets/ctkMatrixWidget.cpp line 253
> [WARNING][Qt] 10.10.2020 20:59:22 (unknown:0) - Assertion `this->Table->rowHeight(i) == newHeight` failed in /home/arc/src/Slicer-SuperBuild/CTK/Libs/Widgets/ctkMatrixWidget.cpp line 253
> [WARNING][Qt] 10.10.2020 20:59:22 (unknown:0) - Assertion `this->Table->rowHeight(i) == newHeight` failed in /home/arc/src/Slicer-SuperBuild/CTK/Libs/Widgets/ctkMatrixWidget.cpp line 253
> [INFO][Stream] 10.10.2020 20:59:23 (unknown:0) - Loading Slicer RC file [/home/user/.slicerrc.py]
> [INFO][VTK] 10.10.2020 21:00:00 [vtkMRMLVolumeArchetypeStorageNode (0x563f5f73dd70)] (/home/arc/src/Slicer/Libs/MRML/Core/vtkMRMLVolumeArchetypeStorageNode.cxx:470) - Loaded volume from file: /home/user/Desktop/BIG/Slicer/CTA-cardio.nrrd. Dimensions: 512x512x321. Number of components: 1. Pixel type: short.
> [DEBUG][Qt] 10.10.2020 21:00:00 (unknown:0) - “Volume” Reader has successfully read the file “/home/user/Desktop/BIG/Slicer/CTA-cardio.nrrd” “[1.15s]”
> [DEBUG][Qt] 10.10.2020 21:01:18 (unknown:0) - Switch to module: “VolumeRendering”
> [WARNING][Qt] 10.10.2020 21:01:29 (unknown:0) - QGestureManager::deliverEvent: could not find the target for gesture
> [WARNING][Qt] 10.10.2020 21:01:34 (unknown:0) - QGestureManager::deliverEvent: could not find the target for gesture
> [DEBUG][Qt] 10.10.2020 21:01:50 (unknown:0) - Close main MRML scene
> [ERROR][VTK] 10.10.2020 21:01:50 [vtkImageMapToColors (0x563f5f5aea80)] (/home/arc/src/Slicer-SuperBuild/VTK/Imaging/Core/vtkImageMapToColors.cxx:151) - RequestInformation: No LookupTable was set but number of components in input doesn’t match OutputFormat, therefore input can’t be passed through!
> [ERROR][VTK] 10.10.2020 21:01:50 [vtkImageExtractComponents (0x563f5f776800)] (/home/arc/src/Slicer-SuperBuild/VTK/Imaging/Core/vtkImageExtractComponents.cxx:230) - Execute: Component 1 is not in input.
> [ERROR][VTK] 10.10.2020 21:01:50 [vtkImageExtractComponents (0x563f5f776800)] (/home/arc/src/Slicer-SuperBuild/VTK/Imaging/Core/vtkImageExtractComponents.cxx:230) - Execute: Component 1 is not in input.
> [ERROR][VTK] 10.10.2020 21:01:50 [vtkImageExtractComponents (0x563f5f776800)] (/home/arc/src/Slicer-SuperBuild/VTK/Imaging/Core/vtkImageExtractComponents.cxx:230) - Execute: Component 1 is not in input.
> [ERROR][VTK] 10.10.2020 21:01:50 [vtkImageExtractComponents (0x563f5f776800)] (/home/arc/src/Slicer-SuperBuild/VTK/Imaging/Core/vtkImageExtractComponents.cxx:230) - Execute: Component 1 is not in input.
> [ERROR][VTK] 10.10.2020 21:01:50 [vtkImageExtractComponents (0x563f5f776800)] (/home/arc/src/Slicer-SuperBuild/VTK/Imaging/Core/vtkImageExtractComponents.cxx:230) - Execute: Component 1 is not in input.
> [ERROR][VTK] 10.10.2020 21:01:50 [vtkImageExtractComponents (0x563f5f776800)] (/home/arc/src/Slicer-SuperBuild/VTK/Imaging/Core/vtkImageExtractComponents.cxx:230) - Execute: Component 1 is not in input.
> [ERROR][VTK] 10.10.2020 21:01:50 [vtkImageExtractComponents (0x563f5f776800)] (/home/arc/src/Slicer-SuperBuild/VTK/Imaging/Core/vtkImageExtractComponents.cxx:230) - Execute: Component 1 is not in input.
> [ERROR][VTK] 10.10.2020 21:01:50 [vtkImageExtractComponents (0x563f5f776800)] (/home/arc/src/Slicer-SuperBuild/VTK/Imaging/Core/vtkImageExtractComponents.cxx:230) - Execute: Component 1 is not in input.
> [ERROR][VTK] 10.10.2020 21:01:50 [vtkImageExtractComponents (0x7fa8d400e5e0)] (/home/arc/src/Slicer-SuperBuild/VTK/Imaging/Core/vtkImageExtractComponents.cxx:230) - Execute: Component 3 is not in input.
> [ERROR][VTK] 10.10.2020 21:01:50 [vtkImageExtractComponents (0x7fa8d400e5e0)] (/home/arc/src/Slicer-SuperBuild/VTK/Imaging/Core/vtkImageExtractComponents.cxx:230) - Execute: Component 3 is not in input.
> [ERROR][VTK] 10.10.2020 21:01:50 [vtkImageExtractComponents (0x7fa8d400e5e0)] (/home/arc/src/Slicer-SuperBuild/VTK/Imaging/Core/vtkImageExtractComponents.cxx:230) - Execute: Component 3 is not in input.
> [ERROR][VTK] 10.10.2020 21:01:50 [vtkImageExtractComponents (0x7fa8d400e5e0)] (/home/arc/src/Slicer-SuperBuild/VTK/Imaging/Core/vtkImageExtractComponents.cxx:230) - Execute: Component 3 is not in input.
> [ERROR][VTK] 10.10.2020 21:01:50 [vtkImageExtractComponents (0x7fa8d400e5e0)] (/home/arc/src/Slicer-SuperBuild/VTK/Imaging/Core/vtkImageExtractComponents.cxx:230) - Execute: Component 3 is not in input.
> [ERROR][VTK] 10.10.2020 21:01:50 [vtkImageExtractComponents (0x7fa8d400e5e0)] (/home/arc/src/Slicer-SuperBuild/VTK/Imaging/Core/vtkImageExtractComponents.cxx:230) - Execute: Component 3 is not in input.
> [ERROR][VTK] 10.10.2020 21:01:50 [vtkImageExtractComponents (0x7fa8d400e5e0)] (/home/arc/src/Slicer-SuperBuild/VTK/Imaging/Core/vtkImageExtractComponents.cxx:230) - Execute: Component 3 is not in input.
> [ERROR][VTK] 10.10.2020 21:01:50 [vtkImageExtractComponents (0x7fa8d400e5e0)] (/home/arc/src/Slicer-SuperBuild/VTK/Imaging/Core/vtkImageExtractComponents.cxx:230) - Execute: Component 3 is not in input.
---
### Author:  [@chir.set](https://discourse.slicer.org/u/chir.set)
#### Post date: [October 10, 2020, 7:07pm UTC](https://discourse.slicer.org/t/a-few-problems-with-slicer-4-13/13973/9 "2020-10-10T19:07:39Z")
On one previous run, I had this in console, can’t remember what I did exactly.
> Assertion `this->Table->rowHeight(i) == newHeight` failed in /home/arc/src/Slicer-SuperBuild/CTK/Libs/Widgets/ctkMatrixWidget.cpp line 253
> Loading Slicer RC file [/home/user/.slicerrc.py]
> An OpenGL Core Profile was requested, but it is not supported on the current platform. Falling back to a non-Core profile. Note that this might cause rendering issues.
> Error: Unknown module: ext.SmjCDN.mobile
> libpng warning: iCCP: known incorrect sRGB profile
> Switch to module: “”
> Switch to module: “”
> vtkDebugLeaks has found no leaks.
---
### Author:  [@lassoan](https://discourse.slicer.org/u/lassoan)
#### Post date: [October 10, 2020, 7:16pm UTC](https://discourse.slicer.org/t/a-few-problems-with-slicer-4-13/13973/10 "2020-10-10T19:16:40Z")
The warnings look harmless. The OpenGL core profile complaint is somewhat surprising. Try to use [compatibility profile](https://slicer.readthedocs.io/en/latest/developer_guide/build_instructions/overview.html#runtime-environment-variables) (set SLICER\_OPENGL\_PROFILE=compatibility) and see if it makes any difference.
---
### Author:  [@chir.set](https://discourse.slicer.org/u/chir.set)
#### Post date: [October 10, 2020, 10:17pm UTC](https://discourse.slicer.org/t/a-few-problems-with-slicer-4-13/13973/11 "2020-10-10T22:17:05Z")
> [@lassoan](#):
>
> SLICER\_OPENGL\_PROFILE=compatibility
No better luck with either no, core and compatibility. I won’t waste your time further as it’s custom built. It may well get fixed unintentionally next. 4.11 will still run on Arch until ICU libs get upgraded here. Thanks.
---
### Author:  [@chir.set](https://discourse.slicer.org/u/chir.set)
#### Post date: [October 11, 2020, 12:05pm UTC](https://discourse.slicer.org/t/a-few-problems-with-slicer-4-13/13973/12 "2020-10-11T12:05:30Z")
I could trace the 3D rotation issue to the selected Appearance Style.
System Breeze and Oxygen styles trigger the window resize to ‘restored’.
System QtCurve does not misbehave.
The 3 Slicer styles do not misbehave.
Switching to Slicer Dark, and hoping the 2D view issue gets fixed soon.
Thanks for your consideration.
---
### Author:  [@Harry-Muzart](https://discourse.slicer.org/u/Harry-Muzart)
#### Post date: [October 13, 2020, 8:55am UTC](https://discourse.slicer.org/t/a-few-problems-with-slicer-4-13/13973/13 "2020-10-13T08:55:27Z")
thanks all for the info