2024-07-08 08:45 AM
Hello,
in KDE/plasma environment I can't use MEMS-studio because it doesn't show file dialogs.
For example: MEMS-studio is connected to the STEVAL-MKI109V3 board, in "Advanced Features" -> "FSM" I click the "Load state machine from file“ button, but nothing happens, the file dialog does not appear.
Is there any solution to allow MEMS-studio to work properly in the KDE/plasma environment?
When I run MEMS-studio from the command line I get this output from the console:
Searching in: "/home/senbuvis/STMicroelectronics/STM32Cube/STM32CubeProgrammer/bin"
Searching in: "/home/senbuvis/STMicroelectronics/STM32CubeProgrammer/bin"
Searching in: "/home/senbuvis/STMicroelectronics/STM32Cube/bin"
Searching in: "/home/senbuvis/STMicroelectronics/bin"
Searching in: "/opt/STMicroelectronics/STM32Cube/STM32CubeProgrammer/bin"
Searching in: "/opt/STMicroelectronics/STM32CubeProgrammer/bin"
Searching in: "/opt/STMicroelectronics/STM32Cube/bin"
Searching in: "/opt/STMicroelectronics/bin"
Searching in: "/usr/STMicroelectronics/STM32Cube/STM32CubeProgrammer/bin"
Searching in: "/usr/STMicroelectronics/STM32CubeProgrammer/bin"
Searching in: "/usr/STMicroelectronics/STM32Cube/bin"
Searching in: "/usr/STMicroelectronics/bin"
Searching in: "/usr/local/STMicroelectronics/STM32Cube/STM32CubeProgrammer/bin"
Searching in: "/usr/local/STMicroelectronics/STM32CubeProgrammer/bin"
Searching in: "/usr/local/STMicroelectronics/STM32Cube/bin"
Searching in: "/usr/local/STMicroelectronics/bin"
Searching in: "/home/senbuvis/ST/STEdgeAI/1.0/Utilities/linux"
Searching in: "/opt/ST/STEdgeAI/1.0/Utilities/linux"
Searching in: "/usr/ST/STEdgeAI/1.0/Utilities/linux"
Searching in: "/usr/local/ST/STEdgeAI/1.0/Utilities/linux"
void DeviceManagerInterface::setIsBusy(bool) false false
void AfsManager::initParamsToDefault()
file:///home/senbuvis/Poligonas/MEMSstudio_1.3.0/opt/mems-studio/qml/QtQuick/Dialogs/DefaultFileDialog.qml:413:17: QML ToolButton: Binding loop detected for property "implicitHeight"
file:///home/senbuvis/Poligonas/MEMSstudio_1.3.0/opt/mems-studio/qml/QtQuick/Dialogs/DefaultFileDialog.qml:309:21: QML Button: Binding loop detected for property "implicitHeight"
file:///home/senbuvis/Poligonas/MEMSstudio_1.3.0/opt/mems-studio/qml/QtQuick/Dialogs/DefaultFileDialog.qml:309:21: QML Button: Binding loop detected for property "implicitHeight"
qml: OS DETECTED: linux
plugin.communication:
app.monitoringDataModel:
mems-studio Started, processing run parameters..
I'm using MEMS-studio v1.3.0.
My system specs:
Operating System: Arch Linux
KDE Plasma Version: 6.1.1
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.2
Kernel Version: 6.6.36-1-lts (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 1700X Eight-Core Processor
Memory: 62.7 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2
Solved! Go to Solution.
2024-07-09 01:50 AM
Hi @zmogas ,
Welcome to ST Community!
Thank you for using MEMS Studio, we are sorry you are facing some issues. MEMS Studio is officially supported on Ubuntu Linux 20.04 or higher however it shall also run on Arch Linux.
File dialogs should work correctly when application is started using provided mems-studio.desktop file. If this is not the case, you can start the application from console using this command:
QT_QPA_PLATFORMTHEME=gtk3 QT_QPA_PLATFORM=xcb /opt/mems-studio/bin/mems-studio
2024-07-09 01:50 AM
Hi @zmogas ,
Welcome to ST Community!
Thank you for using MEMS Studio, we are sorry you are facing some issues. MEMS Studio is officially supported on Ubuntu Linux 20.04 or higher however it shall also run on Arch Linux.
File dialogs should work correctly when application is started using provided mems-studio.desktop file. If this is not the case, you can start the application from console using this command:
QT_QPA_PLATFORMTHEME=gtk3 QT_QPA_PLATFORM=xcb /opt/mems-studio/bin/mems-studio
2024-07-09 07:06 AM
It works, thanks!
Yes, I tried running the mems-studio.desktop file, but the file dialogs didn't show up either.
The exported variable "QT_QPA_PLATFORM=xcb" fixed the problem with file dialogs.
But I found it strange that MEMS-studio (which uses Qt libraries) does not work out of the box in Qt-based KDE/plasma environment, but it works correctly in Ubuntu, where the graphical environment is GTK...
2024-10-13 12:04 PM
I have the same problem with mems-studio Version 1.3.0 on Lubuntu 24.04.
The solution fixed the problem, and it seems for me that "QT_QPA_PLATFORMTHEME=gtk3" does the fix.
As I had mentioned that I use Lubuntu 24.04 and the QT_QPA_PLATFORMTHEME environment is been set to "lxqt" somewhere from init.
The mems-studio was installed under /opt/mems-studio/ . Here I have a question is where to find mems-studio.desktop file? It seems nowhere neither /opt/mems-studio/ nor my home directory.
I tried to created my own mems-studio.desktop, and put "Exec=env QT_QPA_PLATFORM=xcb QT_QPA_PLATFORMTHEME=gtk3 /opt/mems-studio/bin/mems-studio" within and it works. However I can't find a nice icon for mems-studio . Can someone help?
2024-10-13 12:47 PM
According to the .deb file downloaded form ST website, the "desktop" file is located in /usr/share/applications/, and all the icons are located in /usr/share/icons/hicolor/
2024-10-13 03:19 PM
Thanks for quick reply.
Now I find the mems-studio.desktop file under /usr/share/applications/ and all different size of mems-studio.png under /usr/share/icons/hicolor/dddxddd/ .
cat /usr/share/applications/mems-studio.desktop shows
[Desktop Entry]
Name=MEMS Studio
Exec=env QT_QPA_PLATFORMTHEME=gtk3 /opt/mems-studio/bin/mems-studio
Version=1.3.0
Type=Application
Terminal=false
Icon=mems-studio
Comment=Software solution for MEMS sensors with graphical no-code design of algorithms and development of embedded AI features
Categories=Utility;
I guess because of "Categories=Utility" and in my Lubuntu 24.04 Program Menu doesn't provide Utility category and so it wasn't show up. Manually change it to "Categories=Development".
desktop-file-validate complains "Version=1.3.0" , so move it to Comment .
sudo desktop-file-install /usr/share/applications/mems-studio.desktop
Now it seems working fine.