shatur/optimus-manager-qt

An interface for Optimus Manager that allows to switch GPUs on Optimus laptops.

optimus-manager-qt's Issues

The app stopped working

I was using optimus-manager-qt-git version successfully for many months on Manjaro testing and a few days ago there was an update of this package.

As I noticed, it added hybrid mode which is nice if someone changed to Nvidia 435 driver series. However, this new version simply won't work. When I tried to switch, session reloads as always and it stays on Intel as before. I tried switching with terminal, all works correctly then.

Switching with with optimus-manager-qt-git produced:

wrz 24 21:40:08 alienware-PC systemd[1]: Started Optimus Manager Commands Daemon.
wrz 24 21:40:08 alienware-PC python3[909]: Optimus Manager (Daemon) version 1.1
wrz 24 21:40:08 alienware-PC python3[909]: Automatic log cropping
wrz 24 21:40:08 alienware-PC python3[909]: Loading config file
wrz 24 21:40:08 alienware-PC python3[909]: Opening UNIX socket
wrz 24 21:40:08 alienware-PC python3[909]: Awaiting commands
wrz 24 21:41:00 alienware-PC python3[909]: Received command : {
wrz 24 21:41:00 alienware-PC python3[909]:     "args": {
wrz 24 21:41:00 alienware-PC python3[909]:         "mode": "nvidia"
wrz 24 21:41:00 alienware-PC python3[909]:     },
wrz 24 21:41:00 alienware-PC python3[909]:     "type": "switch"
wrz 24 21:41:00 alienware-PC python3[909]: }
wrz 24 21:41:00 alienware-PC python3[909]: Invalid command !
wrz 24 21:41:41 alienware-PC python3[909]: Received command : {
wrz 24 21:41:41 alienware-PC python3[909]:     "args": {
wrz 24 21:41:41 alienware-PC python3[909]:         "mode": "nvidia"
wrz 24 21:41:41 alienware-PC python3[909]:     },
wrz 24 21:41:41 alienware-PC python3[909]:     "type": "switch"
wrz 24 21:41:41 alienware-PC python3[909]: }
wrz 24 21:41:41 alienware-PC python3[909]: Invalid command !

So I decided to change startup to Nvidia and... it didn't work either. The system correctly asks for the password and then nothing is changed. Intel is still the default. So basically, none of the actions in the optimus-manager-qt-git worked. Since git versions overwrite it other in pacman cache, there is no way to roll it back.

So the next thing to try was non-git version. It forced uninstalled optimus-manager-git as well and replaced it with non-git version too. The result? optimus-manager-qt is still not working but it gets worse, it doesn't even start. When I launch it in the terminal I get:

Unable to detect GPU
Aborting (segfault)

I'm still on 430 drivers if that matters.

I'm switching back to the git version that at least was starting correctly but that was all. I expect that I still can change configs manually so this isn't a big deal, but optimus-manager-qt-git is only a pretty tray icon and nothing more at this point. Too bad, it was a really nice and useful app.
I hope this is a temporary thing.

If you need some additional data to debug it, let me know.

EDIT: After installing git versions again, it's still not starting with the same problem. What is going on? Hmm... I'll try to figure it out.

UPDATE 1: Switching to nvidia mode from terminal works, so optimus-manager is not the problem here. After switching to nvidia, the app suprisingly shows up and I was able to switch through it to Intel, but on Intel session it's not loaded again. It means only Intel session somhow produces this problem.

Still can't make it work on Intel. Here is the status of optimus-manager after reboot (so before any switch attempts):

● optimus-manager.service - Optimus Manager Commands Daemon
Loaded: loaded (/usr/lib/systemd/system/optimus-manager.service; enabled; vendor preset: disabled)
Active: active (running) since Thu 2019-09-26 18:09:24 CEST; 35s ago
Process: 825 ExecStartPre=/usr/bin/prime-switch-boot (code=exited, status=0/SUCCESS)
Main PID: 917 (python3)
Tasks: 1
Memory: 38.9M
CGroup: /system.slice/optimus-manager.service
└─917 /usr/bin/python3 -u /usr/bin/optimus-manager-daemon

wrz 26 18:09:23 alienware-PC prime-switch-boot[825]: Loading nouveau module
wrz 26 18:09:24 alienware-PC prime-switch-boot[825]: Loaded extra Intel Xorg options (0 lines)
wrz 26 18:09:24 alienware-PC prime-switch-boot[825]: Loaded extra Nvidia Xorg options (0 lines)
wrz 26 18:09:24 alienware-PC prime-switch-boot[825]: Writing to /etc/X11/xorg.conf.d/10-optimus-manager.conf
wrz 26 18:09:24 alienware-PC systemd[1]: Started Optimus Manager Commands Daemon.
wrz 26 18:09:24 alienware-PC python3[917]: Optimus Manager (Daemon) version 1.2
wrz 26 18:09:24 alienware-PC python3[917]: Automatic log cropping
wrz 26 18:09:24 alienware-PC python3[917]: Loading config file
wrz 26 18:09:24 alienware-PC python3[917]: Opening UNIX socket
wrz 26 18:09:24 alienware-PC python3[917]: Awaiting commands

I checked my configs in /etc/X11/xorg.conf.d/ and /etc/X11/ and everything is all right, no additional, unwanted configs showed up, only optimus-manager is governing the gpu configs, as it should be. So I have no idea why optimus-manager-qt (git or non git) is not recognizing it). I may try to restore the recent backup where the app was at least starting correctly, alas it wasn't doing anything aside showing in which mode the desktop is.

Incorrect Nvidia drivers info pop-up

Since some time (a week maybe) I get this:

However, the nvidia session loads correctly. When the switch is done in terminal, all works as expected. In journal I can see this:

paź 12 05:56:53 alienware-PC python3[1039]: }
paź 12 05:56:53 alienware-PC python3[1039]: Writing requested GPU mode nvidia
paź 12 05:57:26 alienware-PC python3[1039]: Received command : {
paź 12 05:57:26 alienware-PC python3[1039]:     "args": {
paź 12 05:57:26 alienware-PC python3[1039]:         "mode": "intel"
paź 12 05:57:26 alienware-PC python3[1039]:     },
paź 12 05:57:26 alienware-PC python3[1039]:     "type": "switch"
paź 12 05:57:26 alienware-PC python3[1039]: }
paź 12 05:57:26 alienware-PC python3[1039]: Writing requested GPU mode intel
paź 12 05:58:54 alienware-PC python3[1039]: Received command : {
paź 12 05:58:54 alienware-PC python3[1039]:     "args": {
paź 12 05:58:54 alienware-PC python3[1039]:         "path": "/tmp/optimus-manager.conf"
paź 12 05:58:54 alienware-PC python3[1039]:     },
paź 12 05:58:54 alienware-PC python3[1039]:     "type": "user_config"
paź 12 05:58:54 alienware-PC python3[1039]: }
paź 12 05:58:54 alienware-PC python3[1039]: ERROR : cannot replace persistent config : /tmp/optimus-manager.conf does not exist
paź 12 05:58:54 alienware-PC python3[1039]: Received command : {
paź 12 05:58:54 alienware-PC python3[1039]:     "args": {
paź 12 05:58:54 alienware-PC python3[1039]:         "path": ""
paź 12 05:58:54 alienware-PC python3[1039]:     },
paź 12 05:58:54 alienware-PC python3[1039]:     "type": "temp_config"
paź 12 05:58:54 alienware-PC python3[1039]: }
paź 12 05:58:54 alienware-PC python3[1039]: Removing temporary config file path
paź 12 05:58:54 alienware-PC python3[1039]: Received command : {
paź 12 05:58:54 alienware-PC python3[1039]:     "args": {
paź 12 05:58:54 alienware-PC python3[1039]:         "mode": "intel"
paź 12 05:58:54 alienware-PC python3[1039]:     },
paź 12 05:58:54 alienware-PC python3[1039]:     "type": "startup"
paź 12 05:58:54 alienware-PC python3[1039]: }
paź 12 05:58:54 alienware-PC python3[1039]: Writing startup mode intel

This seems more like an issue on my side. I didn't mess with any GPU related settings thou. It happened by itself. Just as usual, updated system (kerlnel, gpu drivers update, optimus-manager-git and optimus-manager-qt-git).

The additional thing that I have done that may has something to do with it is that I plugged in and configured a second monitor. I don't have the second monitor connected all the time but it works quite nicely. However, I noticed when the other monitor is available, the switch to nvidia takes longer. Also, although monitors were configured in Intel, after switching to nvidia they lost all their configuration and had to set it up again, but now the system remembers those settings so all is fine in Intel and Nvidia session.

I'm not sure about this ERROR : cannot replace persistent config : /tmp/optimus-manager.conf does not exist
What does it mean? How can I fix it? Maybe it's about permissions? This is the current ownership and permissions.

srw-rw-rw- 1 root root 0 10-12 05:48 optimus-manager

Ah, or maybe it's about the naming? there is indeed not optimus-manager.conf there but only optimus-manager. So is this the wrong named file or maybe this is a different file and the conf file is missing? Why is it missing thou? Something should write it to tmp if needed. Right?

Thanks for your help.

EDIT: The issue persists after installing the latest git update.

"custom" switching method saved as "none"

Bug description
When you select "custom" as a switching method, it actually ends up as "none" in the config file.

Steps to reproduce
Steps to reproduce the behavior:

1. Right click on tray
2. Click on Settings
3. Click on Optimus
4. Set switching method to Custom
5. Click OK
6. Redo step 1-3, you will see switching method is set to None

Expected behavior
Switching method saved as "custom".

Screenshots
If applicable, add screenshots to help explain your problem.

Environment

• OS: Manjaro
• Desktop environment: KDE
• Optimus Manager version: 1.3
• Optimus Manager Qt version: 1.5.3 (but the About page still shows 1.5.2)

Additional context
It can also be debugged by watching daemon log of optimus manager. When custom is selected, upon clicking OK this is sent:

[intel]\nDRI=3\naccel=\ndriver=modesetting\nmodeset=no\ntearfree=yes\n\n[nvidia]\nDPI=96\nPAT=yes\nallow_external_gpus=no\nignore_abi=yes\nmodeset=yes\noptions=overclocking, triple_buffer\n\n[optimus]\nauto_logout=yes\npci_power_control=yes\npci_remove=yes\npci_reset=no\nstartup_auto_battery_mode=intel\nstartup_auto_extpower_mode=nvidia\nstartup_mode=hybrid\nswitching=\n

as you can see, the switching value is empty.

From what I can see, it's due to optimussettings.cpp:31 is missing string mapping for custom. Whereas in optimussettings.cpp:65 it is used to get the key, however since no value exists for custom, it returns the default key, which is none.

Can't use Optimus Manager QT

So, I installed optimus-manager-qt using AUR but I can't find it in the "Add Widget" menu. Using ArchLinux with KDE Plasma and _plasma is set to true.

Switch to Hybrid option is missing

Hi @Shatur95 I noticed that in the new update of optimus-manager and optimus-manager-qt it is possible to switch to hybrid where prime render offload is supported. Thus, shouldn't be the option to "Switch to Hybrid" likewise to "Switch ot Intel" and "Switch to Nvidia" once you press right click on the tray icon?

Wrong Icon showed

I updated optimus-manager-qt -git today and got nearly a heart attack, because no matter what I chose, I always landed on hybrid, or so I thought. The problem is, on hybrid multiple monitors won't work. I know, they should work by now, but it's still problematic, and I get black both screens when I enable the secondary screen on hybrid mode.

Anyway, I need my Intel mode for multiple monitors and hybrid mode to play games on Nvidia, which rarely happens, while other monitors I use for work very often. So when I thought that switching isn't happening, I was scared.

Luckily, when I checked:

optimus-manager --print-mode

I got:

Current GPU mode : integrated

However, I still see a hybrid icon, which caused all the confusion. The issue is not so bad, still, seeing the wrong icon is a big bug for this tool nevertheless.

Generated config file and autostart script filename are badly encoded

Bug description

The config file generated at /etc/optimus-manager/optimus-manager.conf is badly encoded. Basically looks like this:

[intel]
DRI=3
accel=
driver=modesetting
modeset=yes
tearfree=

[nvidia]
DPI=96
PAT=yes
allow_external_gpus=no
ignore_abi=no
modeset=yes
options=overclocking

[optimus]
%23%20%20%20%20%20%20%20%20%20Also%2C%20it%20will%20perform%20a%20PCI%20remove%20even%20if%20pci_remove=no.
%23%20GPU%20mode%20to%20select%20when%20startup_mode=auto and the computer is running on external power.
%23%20Ignored%20if%20switching="nouveau or switching=bbswitch."
auto_logout=yes
pci_power_control=no
pci_remove=no
pci_reset=no
startup_auto_battery_mode=intel
startup_auto_extpower_mode=hybrid
startup_mode=auto
switching=bbswitch

The name of the .desktop file generated in ~/.config/autostart was as also badly encoded.

Steps to reproduce

Steps to reproduce the behavior:

1. Go to settings and set config file type to "Permanent"
2. Enable "Launch at startup"
3. Modify some settings and save them
4. Check the output

Environment

• OS: Arch Linux
• Desktop environment: Gnome
• Optimus Manager version: 1.3
• Optimus Manager Qt version: 1.5.1

Do not initialize as regular user

I'm using Arch Linux and aur/optimus-manager-qt on a Plasma including kde-applications DE nearly installed and optimus-manager is not opening as a user. It only works when I run it as sudo.

It works if I keep _plasma=false.

System tray doesn't show optimus-manager-qt after upgrading qt to 5.15.1

Bug description
This is exactly like #29. I don't see the tray icon. It was working until yesterday, but it doesn't show anymore.

Screenshots

What I've tried already

• As requested in issue #29, I tried installing qbittorrent, and I can see the icon as seen in the screenshot above.
• I have KStatusNotifierItem/AppIndicator installed and enabled.
• Uninstalled and reinstalled the optimus-manager-qt package.
• Several reboots.

Environment

• Distro: Manjaro Linux
• Desktop: GNOME 3.36.6 tk: GTK 3.24.23 wm: gnome-shell dm: GDM 3.36.3
• Optimus Manager version: 1.3.1-1
• Optimus Manager Qt version: 1.5.3-1

Additional context
I'm not entirely sure, but I think this started happening after performing a full system upgrade using sudo pacman -Syu to install the latest Manjaro update.

No system tray icon after installing optimus-manager-qt

Hello so i have installed optimus-manager and its working very good!!, I'm using GDM and Gnome.
But one thing not have working is the tray icon, I tried to find in the settings maybe i need to enable it but could not find anything there.
Please have a look maybe need to update the package?
My laptop model is asus gl753ve
arch linux 5.3.7-arch1-1-ARCH
Thanks!!!

Launch at startup is not being saved

In the settings panel, launch at startup is not being saved.

Steps to reproduce

1. Go to Settings
2. Check "launch at startup"
3. Close the panel
4. Exit
5. Re-open optimus manager qt
6. Open settings, to see "launch at startup" is still unchecked

Environment

• OS: Manjaro
• Window Manager: i3
• Optimus Manager version: 1.3.1
• Optimus Manager Qt version: 1.5.3

Can't switch to nvidia after upgrade to 1.3.1

After upgrade to 1.3.1 on Manjaro with Cinnamon I can't switch to nvidia drivers. It through the power management warning, I press "y" to switch but nothing happened.

GNOME: Application icon disappear after reboot

Hi,

I just installed the optimus-manager-qt and it works quite nicely to switch from my nvidia to my integrated intel graphics. But after i reboot the system the icon disappear from the gnome tool bar. I tried to run it manually from the terminal but i got no output. The service optimus-manager still works fine, the problems seems only in the QT GUI.

I'm on Manjaro 20.2, Gnome 3.38.2, running X11.

The same thing happens with Optimus-manager-qt and optimus-manager-qt-git

Thanks for this amazing program !

Can't install the latest version (1.5.1) on Manjaro

Bug description
When I try to update to the latest version via AUR, I get the message

could not satisfy dependencies:

• unable to satisfy dependency 'optimus-manager>=1.3' required by optimus-manager-qt

Steps to reproduce

1. Open Pamac
2. Go to Updates
3. Hit "Apply"
4. Message pops up.

Expected behavior
Application being updated.

Environment

• OS: Manjaro
• Desktop environment: KDE
• Optimus Manager version: (e.g. 1.3-1)
• Optimus Manager Qt version: current: 1.5.0-1, target: 1.5.1-1

Integrated graphics icon looks too big

Bug description
Integrated graphics icon looks a little too big in a thin KDE latte dock. It might just be the icon design, but I think it stands out a little too much.

Steps to reproduce
Steps to reproduce the behavior:

1. Install on KDE with latte dock
2. Put system tray in latte panel
3. Set item size to 22px absolute in the panel settings

Expected behavior
Icon is comparable in size to other tray icons.

Screenshots

Environment

• OS: Arch Linux
• Desktop environment: KDE
• Optimus Manager version: 1.4
• Optimus Manager Qt version: 1.6.0

Tray icon shows Intel in Hybrid mode

Tray icon dissapears upon changing wallpaper

I'm using manjaro i3.

I tried having the tray icon launch as I boot i3, like my other icons, like nm-applet for example.But I found that it kept disappearing. I found that it disappears every time I change wallpapers (and i3 starts with a blank wallpaper, and with its startup process, fetches a random wallpaper and applies it).

The process is still running (it's there in htop) so I can't just relaunch the program. I need to kill the process, then launch it again t be able to see the tray icon again.

It's far from a real issue, but as this is supposed to be a nice thing on top of optimus-manager, might as well make it even nicer ^^

May i know if i need to configuration nvidia and sddm on archlinux

Archlinux plasma sddm
I have install nvidia sddm and optimus-manager(have set switching=bbswitch driver=modesetting etc).
May i know if i shoud configure nvidia and sddm somewhere(like defauld/grub /etc/sddm.conf etc).
Many thanks.

Setting DPI to zero results in `DPI=@Invalid()`

Bug description
I noticed optimus-manager --status was complaining about an invalid DPI setting, so I checked /etc/optimus-manager/optimus-manager.conf and found

DPI=@Invalid()

Setting it to a number works normally.

Environment

• OS: Arch Linux
• Desktop environment: Plasma
• Optimus Manager version: 1.3
• Optimus Manager Qt version: 1.5.2

Thanks

Format security issue

Bug description
A clear and concise description of what the bug is.

Just little thing if '--Werror=format-security' is applied

optimus-manager-qt-1.6.0/src/optimusmanager.cpp:415:50: error: 
format not a string literal and no format arguments [-Werror=format-security]
  415 |             qFatal("Unknown provider: " + gpuName);
      |                                                  ^

Solves if added like this format example:

qFatal("Unknown provider: " + gpuName, " (%s)" );

Missing icons

Describe the bug
Unfortunately all icons in the application and tray are missing. At the same time other qt applications have icons (i.e. Telegram, qBittorrent).

Screenshots

Environment (please complete the following information):

• OS: Arch Linux
• Desktop environment: XFCE4
• Optimus Manager version: 1.2.2
• Optimus Manager Qt version: 1.4.2

P.S. I use papirus-dark-theme of icons, if it is relevant info for investigation.

App does not detect available nvidia module

Hi. So the pop up that says "nvidia module is not available" appears right before the switch even though I have everything installed and the switch itself works properly. I recently switched from LTS kernel to Zen kernel and this didn't happen before on LTS kernel. I have "linux-zen linux-zen-headers dkms nvidia-dkms bbswitch-dkms optimus-manager optimus-manager-qt" installed and they are all at the latest version. Maybe it is because zen doesn't have a specific package of its own for nvidia drivers?

Btw, I am not that much familiar with GitHub and issue reporting so I apologize for that and also my bad English. If there is anything I can do to help like post some command line output I would gladly do so.

Specs:
Arch Linux
i5-8250u
MX150+UHD620
8GB Memory

Thank you and sorry for taking your time

error when installing: ‘const class QByteArray’ has no member named ‘chopped’

Bug description
When I install optimus-manager-qt through yay, I get this error

Steps to reproduce
Steps to reproduce the behavior:

1. yay -S optimus-manager-qt
2. enter, enter ...
3. See error

Expected behavior
optimus-manager-qt is successfully installed!

Environment

• OS: manjaro
• Desktop environment: dwm
• Optimus Manager version: 1.3
• Optimus Manager Qt version: 1.5.3

Missing icons

I tried optimus-manager-qtand optimus-manager-qt-git from the AUR. In both cases icons are missing.

Broken generated config for nvidia

Hello,

When both Overclocking options and Triple buffer are disabled in app settings, instead of empty string, @Invalid() is written to disk.

Like this:

[nvidia]
DPI=96
PAT=yes
modeset=yes
options=@Invalid() 

So it breaks the configuration for optimus-manager.

Thx! :)

Wrong Icon Bug

Bug description
The Optimus Manager Qt is displaying hybrid icon when the GPU mode is Nvidia.

The output of optimus-manager --print-mode is Current GPU mode : nvidia

Expected behavior
To Display the Nvidia icon on nvidia mode.

Screenshots
If applicable, add screenshots to help explain your problem.

Environment

• OS: Manjaro
• Desktop environment: KDE
• Optimus Manager version: 1.3
• Optimus Manager Qt version: 1.5.3

Additional context
Add any other context about the problem here.
On printing the gpuName in detectGpu method i found it is showing both gpu names even when the Current Gpu Mode is Nvidia according to optimus-manager.

Missing icons in settings

xfce, AUR, 1.7.1

While the icons were probably fixed with #1, the settings dialog is still weird (1.7.1):

In the left panel, the icons are missing. In the tray however, they are displayed correctly. And when I click on either of the tray icon selection buttons and click on "cancel":

the action is not actually cancelled. The icon gets actually set to "".

But these are only minor annoyances, do not actually matter much. Thought I'd report anyways. :-)

Optimus manager QT closes after leaving the settings menu (XFCE)

Describe the bug
Optimus manager QT's tray icon closes after leaving the settings menu. It doesn't matter if I close it pressing OK, Cancel, or using the window manager. optimus-manager-qt closes after that.

System info
Please include :

• Arch Antergos (Latest)
• XFCE4
• LightDM
• package: optimus-manager-qt-git

Logs
see file

Note: The message of the log is generated when I launch optimus-manager-qt. No warning or error is showed when the program is automatically closed.

Settings won't save

For example, when I want to switch Intel from Modesetting to Intel and then try different subsettings, I save it and then check again, nothing has changed, still, modesetting is used.

I probably can change it manually in confs but the GUI should have worked too. I'm unsure if that is just on my side or general bug. How can I debug it?

To be honest, I never played with settings before so I don't know how long this issue exists. I just left it all by default and it was fine. However, with two-monitor setup I noticed synchronization problems that produced weird distortions when watching YouTube on the other monitor. When using nvidia, all those distractions weren't there, all was perfect, so this is happening only on the Intel session. That is why I want to try out other settings to see if it can't be improved. I also must research what is this modesetting anyway. I assumed I use intel drivers so I'm surprised to see modesetting as a driver.

Or actually, if the settings are supposed to change /etc/optimus-manager/optimus-manager.conf shouldn't I be asked for sudo or root password? I get no such thing and that is most likely why the settings won't save. The lack of proper rights. So now the question is, why I won't get authorization pop-up?

Thanks.

EDIT: I did change the settings manually, optimus-manager-qt sees it correctly. So in the backed it all works fine but the issue remains: optimus-manager-qt does not ask for sudo/root credentials and is unable to save any changes made to settings.

Icon Fails to Switch With Optimus Mode

Bug description Failure to change icon in system tray
Steps to reproduce:
1. Open optimus-manager-qt via left click.
2. Change to anything but Intel iGPU
3. The icon still shows the Intel iGPU in the system tray after a logout/login
Expected behavior The icon shifting to either Hybrid or NVidia
Screenshots If applicable, add screenshots to help explain your problem.
Environment
• OS: Manjaro stable
• Desktop environment: KDE
• Optimus Manager version: (1.2.22)
• Optimus Manager Qt version: (1.4.5)
Additional context This happened after a recent update. No errors are reported, and I think the switch is working. Either that, or my iGPU is a beast.

Can't set startup mode to AMD or integrated

Bug description
No option for the same in the drop down

Steps to reproduce
OptimusManagerQT Settings > Optimus > StartupMode

Screenshots

Environment
Arch Linux KDE (Kernel 5.9.9)

Just having a common "integrated" option will suffice

Flatpak for optimus-manager-qt

nice project , i like .
i see ,that this software is not avaible for all the linux distributions ,
would be great ,if you make a flatpak for optimus-manager-qt

https://flathub.org/home

Is this "Tripple" a typo?

I found this when I am translating...

I think this "tripple" should be "triple"?
Here is a arch wiki entry which use "triple".

Intel and nvidia icons are missing

I installed the package from AUR and the prime-intel and prime-nivida icons are missing, and I don't see in the repository

Unable to create autorun file

Bug description
"Unable to create autorun file from '/usr/share/applications/io.optimus_manager.OptimusManagerQt.desktop'"

Steps to reproduce

1. Run optimus-manager-qt from terminal
2. Right click icon tray and choose settings
3. Check Launch at startup
4. Click ok

Expected behavior
Software save configuration state and make manager auto start.

Environment

• EndeavourOS
• KDE
• Optimus Manager 1.3
• Optimus Manager Qt 1.5.2

Additional context
even with sudo error still occurs. _plasma=true in PKGBUILDS

Broken icons on Plasma 5.21

With Plasma 5.21 it looks like the package lost its ability to use the icons from the desktop theme and reverted to the default icon. Moreover, it was nvidia green icon for all the modes, so I couldn't know which GPU mode is currently on.

I recompiled the package, restarted, and now it shows correctly various mode icons: intel, blue-hybrid, green-nvidia. However, this is still the default icon, not from the desktop theme.

I cannot post any images as the new Plasma broke the ability to drag and drop images :( and I can't see a way to add images here. I already submitted a bug to Plasma bugzilla about it.

Unable to detect GPU after 7172f6a

Unable to detect AMD iGPU

Bug description
If installed on a system with an AMD iGPU and Nvidia dGPU running optimus-manager-amd-git from the AUR, the AMD iGPU is not detected an causes a crash

Steps to reproduce

1. Use laptop with AMD iGPU (eg Zephyrus G14)
2. Install optimus-manager-amd-git from AUR
3. Start and enable optimus-manager using systemctl
4. Install optimus-manager-qt-git from AUR
5. Start optimus-manager-qt

Expected behavior
Detect AMD as an iGPU and offer options to switch between AMD iGPU and Nvidia GPU

Environment

• OS: Arch Linux
• Desktop environment: i3-gaps
• Optimus Manager version: 1.2.2 amd_support branch
• Optimus Manager Qt version: 1.5.3.r6.geb92a21-1

Additional context

$ optimus-manager-qt --version
Unable to detect GPU
[1]    246781 abort (core dumped)  optimus-manager-qt --version

$ optimus-manager --print-mode

Current GPU mode : amd

Message on startup: The application is already running (XFCE)

Another minor bug:
When the option "launch at startup is enabled", I get the next dialog when I start session

And I think I've found the reason for it. It's creating an entry for both, session:

And autostart

Removing one of the 2 entries s̶h̶o̶u̶l̶d̶ fixes the problem (I removed the one from autostart). If you know the line/file, I can test this one too in QTCreator.

This is the last minor bug I have on my end. Cheers

GNOME: Broken icons at startup

Bug description

Icons aren't shown properly when the program is launched at startup.

Screenshots

Expected behavior

Environment

• OS: Arch Linux
• Desktop environment: GNOME
• Optimus Manager version: 1.3.1.r48.g0aed196-1
• Optimus Manager Qt version: 1.5.2

Additional context

My best guess is that the program is launched before the system can load its icons, in fact I managed to fix the issue by delaying optimus-manager-qt's autostart by 1 second editing the launch command in .config/autostart/io.optimus_manager.OptimusManagerQt.desktop:

Exec=bash -c "sleep 1 && optimus-manager-qt"

Switch to Hybrid fails

It may not be a bug per se but The Hybrid mode once selected is defaulting to intel on my laptop.
Intel mode / Nvidia mode are working fine.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'Systray
2. Click on '....'Hybrid

Expected behavior
I expected the hybrid icon to appear on the systray after logout/login.

Environment (please complete the following information):

• OS: (Manjaro)
• Desktop environment: (KDE)
• Optimus Manager version: (e.g. 1.0.0)
• Optimus Manager Qt version: (optimus-manager-qt 1.4.3-1)

In fact i dont know what hybrid would do , is it Prime offloading or just blumblebee ?

Missing icons

Bug description
A clear and concise description of what the bug is.

New version: 1.6.0
Missing device icons on sidebar of settings dialog. (appearance in previous versions was good of icons)

Install fail

Bug description
Install failure.

Steps to reproduce
Steps to reproduce the behaviour:

1. yay -S optimus-manager
2. Enable the optimus-manager daemon systemctl (if not done)
3. yay -S optimus-manager-qt
4. Type 1 then enter
5. Get this:

==> Starting build()...
/home/maxie/anaconda3/bin/uic src/settingsdialog.ui -o ui_settingsdialog.h
g++ -c -pipe -O2 -std=gnu++1z -Wall -W -D_REENTRANT -fPIC -DQAPPLICATION_CLASS=QApplication -DQT_DEPRECATED_WARNINGS -DQT_NO_DEBUG -DQT_WIDGETS_LIB -DQT_X11EXTRAS_LIB -DQT_GUI_LIB -DQT_DBUS_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I. -Isrc/third-party/singleapplication -I/home/maxie/anaconda3/include/qt -I/home/maxie/anaconda3/include/qt/QtWidgets -I/home/maxie/anaconda3/include/qt/QtX11Extras -I/home/maxie/anaconda3/include/qt/QtGui -I/home/maxie/anaconda3/include/qt/QtDBus -I/home/maxie/anaconda3/include/qt/QtNetwork -I/home/maxie/anaconda3/include/qt/QtCore -I. -I. -I/home/maxie/anaconda3/mkspecs/linux-g++ -o singleapplication.o src/third-party/singleapplication/singleapplication.cpp
In file included from /home/maxie/anaconda3/include/qt/QtCore/qlocale.h:37,
                 from /home/maxie/anaconda3/include/qt/QtCore/qtextstream.h:40,
                 from /home/maxie/anaconda3/include/qt/QtCore/qdebug.h:42,
                 from /home/maxie/anaconda3/include/qt/QtNetwork/qabstractsocket.h:40,
                 from /home/maxie/anaconda3/include/qt/QtNetwork/qlocalsocket.h:38,
                 from /home/maxie/anaconda3/include/qt/QtNetwork/QLocalSocket:1,
                 from src/third-party/singleapplication/singleapplication.h:27,
                 from src/third-party/singleapplication/singleapplication.cpp:29:
/home/maxie/anaconda3/include/qt/QtCore/qvariant.h: In constructor ‘QVariant::QVariant(QVariant&&)’:
/home/maxie/anaconda3/include/qt/QtCore/qvariant.h:259:25: warning: implicitly-declared ‘constexpr QVariant::Private& QVariant::Private::operator=(const QVariant::Private&)’ is deprecated [-Wdeprecated-copy]
  259 |     { other.d = Private(); }
      |                         ^
/home/maxie/anaconda3/include/qt/QtCore/qvariant.h:374:16: note: because ‘QVariant::Private’ has user-provided ‘QVariant::Private::Private(const QVariant::Private&)’
  374 |         inline Private(const Private &other) Q_DECL_NOTHROW
      |                ^~~~~~~
g++ -c -pipe -O2 -std=gnu++1z -Wall -W -D_REENTRANT -fPIC -DQAPPLICATION_CLASS=QApplication -DQT_DEPRECATED_WARNINGS -DQT_NO_DEBUG -DQT_WIDGETS_LIB -DQT_X11EXTRAS_LIB -DQT_GUI_LIB -DQT_DBUS_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I. -Isrc/third-party/singleapplication -I/home/maxie/anaconda3/include/qt -I/home/maxie/anaconda3/include/qt/QtWidgets -I/home/maxie/anaconda3/include/qt/QtX11Extras -I/home/maxie/anaconda3/include/qt/QtGui -I/home/maxie/anaconda3/include/qt/QtDBus -I/home/maxie/anaconda3/include/qt/QtNetwork -I/home/maxie/anaconda3/include/qt/QtCore -I. -I. -I/home/maxie/anaconda3/mkspecs/linux-g++ -o singleapplication_p.o src/third-party/singleapplication/singleapplication_p.cpp
In file included from /home/maxie/anaconda3/include/qt/QtCore/qlocale.h:37,
                 from /home/maxie/anaconda3/include/qt/QtCore/qtextstream.h:40,
                 from /home/maxie/anaconda3/include/qt/QtCore/qdebug.h:42,
                 from /home/maxie/anaconda3/include/qt/QtNetwork/qabstractsocket.h:40,
                 from /home/maxie/anaconda3/include/qt/QtNetwork/qlocalserver.h:37,
                 from /home/maxie/anaconda3/include/qt/QtNetwork/QLocalServer:1,
                 from src/third-party/singleapplication/singleapplication_p.cpp:39:
/home/maxie/anaconda3/include/qt/QtCore/qvariant.h: In constructor ‘QVariant::QVariant(QVariant&&)’:
/home/maxie/anaconda3/include/qt/QtCore/qvariant.h:259:25: warning: implicitly-declared ‘constexpr QVariant::Private& QVariant::Private::operator=(const QVariant::Private&)’ is deprecated [-Wdeprecated-copy]
  259 |     { other.d = Private(); }
      |                         ^
/home/maxie/anaconda3/include/qt/QtCore/qvariant.h:374:16: note: because ‘QVariant::Private’ has user-provided ‘QVariant::Private::Private(const QVariant::Private&)’
  374 |         inline Private(const Private &other) Q_DECL_NOTHROW
      |                ^~~~~~~
g++ -c -pipe -O2 -std=gnu++1z -Wall -W -D_REENTRANT -fPIC -DQAPPLICATION_CLASS=QApplication -DQT_DEPRECATED_WARNINGS -DQT_NO_DEBUG -DQT_WIDGETS_LIB -DQT_X11EXTRAS_LIB -DQT_GUI_LIB -DQT_DBUS_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I. -Isrc/third-party/singleapplication -I/home/maxie/anaconda3/include/qt -I/home/maxie/anaconda3/include/qt/QtWidgets -I/home/maxie/anaconda3/include/qt/QtX11Extras -I/home/maxie/anaconda3/include/qt/QtGui -I/home/maxie/anaconda3/include/qt/QtDBus -I/home/maxie/anaconda3/include/qt/QtNetwork -I/home/maxie/anaconda3/include/qt/QtCore -I. -I. -I/home/maxie/anaconda3/mkspecs/linux-g++ -o main.o src/main.cpp
In file included from /home/maxie/anaconda3/include/qt/QtCore/qsettings.h:38,
                 from /home/maxie/anaconda3/include/qt/QtCore/QSettings:1,
                 from src/appsettings.h:26,
                 from src/main.cpp:22:
/home/maxie/anaconda3/include/qt/QtCore/qvariant.h: In constructor ‘QVariant::QVariant(QVariant&&)’:
/home/maxie/anaconda3/include/qt/QtCore/qvariant.h:259:25: warning: implicitly-declared ‘constexpr QVariant::Private& QVariant::Private::operator=(const QVariant::Private&)’ is deprecated [-Wdeprecated-copy]
  259 |     { other.d = Private(); }
      |                         ^
/home/maxie/anaconda3/include/qt/QtCore/qvariant.h:374:16: note: because ‘QVariant::Private’ has user-provided ‘QVariant::Private::Private(const QVariant::Private&)’
  374 |         inline Private(const Private &other) Q_DECL_NOTHROW
      |                ^~~~~~~
src/main.cpp: In function ‘int main(int, char**)’:
src/main.cpp:31:24: error: ‘setDesktopFileName’ is not a member of ‘SingleApplication’
   31 |     SingleApplication::setDesktopFileName(QStringLiteral("io.optimus_manager.OptimusManagerQt.desktop"));
      |                        ^~~~~~~~~~~~~~~~~~
make: *** [Makefile:1302: main.o] Error 1
==> ERROR: A failure occurred in build().
    Aborting...
Error making: optimus-manager-qt

Expected behaviour
A successful installation to have the tray as shown

Screenshots
If applicable, add screenshots to help explain your problem.

Environment

• OS: ArchLinux
• Desktop environment: AwesomeWM
• Optimus Manager version: 1.2.2
• Optimus Manager Qt version: which ever should have been installed
• Linux Kernel version: 5.5.8-arch1-1

Additional context
Add any other context about the problem here.

build error WITH_PLASMA

Cannot build with Qt 5.15.1 + Plasma 5.19.4 if WITH_PLASMA is ON

Scanning dependencies of target optimus-manager-qt
[ 65%] Building CXX object CMakeFiles/optimus-manager-qt.dir/optimus-manager-qt_autogen/mocs_compilation.cpp.o
[ 69%] Building CXX object CMakeFiles/optimus-manager-qt.dir/src/appsettings.cpp.o
[ 73%] Building CXX object CMakeFiles/optimus-manager-qt.dir/src/daemonclient.cpp.o
[ 76%] Building CXX object CMakeFiles/optimus-manager-qt.dir/src/main.cpp.o
[ 80%] Building CXX object CMakeFiles/optimus-manager-qt.dir/src/optimusmanager.cpp.o
In file included from /usr/include/qt5/QtCore/qflags.h:40,
                 from /usr/include/qt5/QtCore/QFlags:1,
                 from /home/build/rpmbuild/SOURCES/optimus-manager-qt/src/optimussettings.h:24,
                 from /home/build/rpmbuild/SOURCES/optimus-manager-qt/src/optimusmanager.h:24,
                 from /home/build/rpmbuild/SOURCES/optimus-manager-qt/src/optimusmanager.cpp:21:
/usr/include/qt5/QtCore/qmetaobject.h: In instantiation of ‘static QMetaEnum QMetaEnum::fromType() [with T = AppSettings::Gpu]’:
/home/build/rpmbuild/SOURCES/optimus-manager-qt/src/optimusmanager.cpp:80:107:   required from here
/usr/include/qt5/QtCore/qmetaobject.h:231:9: error: static assertion failed: QMetaEnum::fromType only works with enums declared as Q_ENUM, Q_ENUM_NS, Q_FLAG or Q_FLAG_NS
  231 |         Q_STATIC_ASSERT_X(QtPrivate::IsQEnumHelper<T>::Value,
      |         ^~~~~~~~~~~~~~~~~
In file included from /usr/include/qt5/QtCore/QMetaEnum:1,
                 from /home/build/rpmbuild/SOURCES/optimus-manager-qt/src/optimusmanager.cpp:35:
/usr/include/qt5/QtCore/qmetaobject.h:234:61: error: ‘qt_getEnumMetaObject’ was not declared in this scope
  234 |         const QMetaObject *metaObject = qt_getEnumMetaObject(T());
      |                                         ~~~~~~~~~~~~~~~~~~~~^~~~~
/usr/include/qt5/QtCore/qmetaobject.h:234:61: note: suggested alternatives:
In file included from /usr/include/qt5/QtCore/qobject.h:54,
                 from /usr/include/qt5/QtCore/qsettings.h:43,
                 from /usr/include/qt5/QtCore/QSettings:1,
                 from /home/build/rpmbuild/SOURCES/optimus-manager-qt/src/optimussettings.h:25,
                 from /home/build/rpmbuild/SOURCES/optimus-manager-qt/src/optimusmanager.h:24,
                 from /home/build/rpmbuild/SOURCES/optimus-manager-qt/src/optimusmanager.cpp:21:
/usr/include/qt5/QtCore/qmetatype.h:1564:31: note:   ‘QtPrivate::qt_getEnumMetaObject’
 1564 |     template<typename T> char qt_getEnumMetaObject(const T&);
      |                               ^~~~~~~~~~~~~~~~~~~~
In file included from /usr/include/qt5/QtCore/qobjectdefs.h:48,
                 from /usr/include/qt5/QtCore/qobject.h:46,
                 from /usr/include/qt5/QtCore/qsettings.h:43,
                 from /usr/include/qt5/QtCore/QSettings:1,
                 from /home/build/rpmbuild/SOURCES/optimus-manager-qt/src/optimussettings.h:25,
                 from /home/build/rpmbuild/SOURCES/optimus-manager-qt/src/optimusmanager.h:24,
                 from /home/build/rpmbuild/SOURCES/optimus-manager-qt/src/optimusmanager.cpp:21:
/usr/include/qt5/QtCore/qnamespace.h:1868:5: note:   ‘Qt::qt_getEnumMetaObject’
 1868 |     QT_Q_ENUM(TabFocusBehavior)
      |     ^~~~~~~~~
In file included from /usr/include/qt5/QtCore/QMetaEnum:1,
                 from /home/build/rpmbuild/SOURCES/optimus-manager-qt/src/optimusmanager.cpp:35:
/usr/include/qt5/QtCore/qmetaobject.h:235:42: error: ‘qt_getEnumName’ was not declared in this scope; did you mean ‘Qt::qt_getEnumName’?
  235 |         const char *name = qt_getEnumName(T());
      |                            ~~~~~~~~~~~~~~^~~~~
      |                            Qt::qt_getEnumName
In file included from /usr/include/qt5/QtCore/qobjectdefs.h:48,
                 from /usr/include/qt5/QtCore/qobject.h:46,
                 from /usr/include/qt5/QtCore/qsettings.h:43,
                 from /usr/include/qt5/QtCore/QSettings:1,
                 from /home/build/rpmbuild/SOURCES/optimus-manager-qt/src/optimussettings.h:25,
                 from /home/build/rpmbuild/SOURCES/optimus-manager-qt/src/optimusmanager.h:24,
                 from /home/build/rpmbuild/SOURCES/optimus-manager-qt/src/optimusmanager.cpp:21:
/usr/include/qt5/QtCore/qnamespace.h:1868:5: note: ‘Qt::qt_getEnumName’ declared here
 1868 |     QT_Q_ENUM(TabFocusBehavior)
      |     ^~~~~~~~~
make[2]: *** [CMakeFiles/optimus-manager-qt.dir/build.make:186: CMakeFiles/optimus-manager-qt.dir/src/optimusmanager.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:118: CMakeFiles/optimus-manager-qt.dir/all] Error 2
make: *** [Makefile:149: all] Error 2

Build successful if PLASMA is OFF

建议在AUR包中添加`qt5-svg`依赖关系解决图标问题

建议添加一个依赖关系来解决QSystemTrayIcon::setVisible: No Icon set图标设置失败的问题
依赖包：extra/qt5-svg

Switching from Intel to Nvidia renders black screen instead of login screen (KDE Plasma)

As stated in the title, when I switch to Nvidia using optimus-manager-qt instead of a login screen the screen remains black. Inserting the user password and hitting enter logs me in, but is annoying if I misspell my password because I need to blindly delete it and reinsert it.

I want to mention also that I have replaced PLASMA=false with PLASMA=true in PKGBUILD before building optimus-manager-qt.

Thank you!

OS: Manjaro Linux x86_64
Host: 20217 Lenovo IdeaPad Y510P
Kernel: 5.0.5-1-MANJARO
Resolution: 1920x1080
DE: KDE 5.15.3-1
CPU: Intel i7-4700MQ (8) @ 3.400GHz
GPU: Intel 4th Gen Core Processor
GPU: NVIDIA GeForce GT 750M
Memory: 1958MiB / 7892MiB

Switching doesn't work anymore after upgrade to optimums manager v1.0

Problem
Switching doesn't work anymore after upgrade to optimums manager v1.0. To switch I have to type "optimus-manager --switch mode". Switching using optimus-manager-qt doesn't work.
After clicking to switch, "journalctl -u optimus-manager" prints:

May 27 12:43:13 franciszek-pc python[842]: Received command : intel
May 27 12:43:13 franciszek-pc python[842]: Writing requested mode

But nothing happens.

Laptop
Lenovo legion y530
Manjaro
Cinnamon
gdm-prime

Thank you!

Application fails to launch GUI

Bug description
Fails to launch, with or without sudo permissions : I don't get the GUI. If launched from console I get the following error :

QFont::fromString: Invalid description '(empty)'
QFont::fromString: Invalid description '(empty)'
qt5ct: using qt5ct plugin
qt5ct: D-Bus system tray: no
QSystemTrayIcon::setVisible: No Icon set

then nothing (doesn't crash, but not GUI).

If launched with sudo, the errors change a little :

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
qt5ct: using qt5ct plugin
qt5ct: D-Bus system tray: no

but still no GUI

optimus-manager does work well from command line.

Steps to reproduce
Install it and try to launch from console.

Environment

• OS: (Manjaro)
• Desktop environment: (Gnome 3.36.2)
• Optimus Manager version: 1.3
• Optimus Manager Qt version: don't know, but up to date in aur (bug happens with both optimus-manager-qt and optimus-manager-qt-git)

Issue building from AUR

Hey all, im having trouble building from the aur with pamac build optimus-manager-qt on manjaro
Arch Linux/Manjaro
KDE

Heres the output:

pamac build optimus-manager-qt                                                                                                                                                        ─╯
Preparing...
Cloning optimus-manager-qt build files...
Checking optimus-manager-qt dependencies...
Cloning optimus-manager build files...
Checking optimus-manager dependencies...
Resolving dependencies...
Checking inter-conflicts...

To build (2):
  optimus-manager     1.4-1    (1.3.1-2)  AUR
  optimus-manager-qt  1.6.0-1             AUR


Edit build files : [e] 
Apply transaction ? [e/y/N] y


Building optimus-manager...
==> Making package: optimus-manager 1.4-1 (Sun 28 Feb 2021 07:03:00 PM EST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Updating optimus-manager git repo...
Fetching origin
==> Validating source files with sha256sums...
    optimus-manager ... Skipped
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Creating working copy of optimus-manager git repo...
Cloning into 'optimus-manager'...
done.
Switched to a new branch 'makepkg'
==> Removing existing $pkgdir/ directory...
==> Starting build()...
running build
running build_py
creating build
creating build/lib
creating build/lib/optimus_manager
copying optimus_manager/checks.py -> build/lib/optimus_manager
copying optimus_manager/kernel_parameters.py -> build/lib/optimus_manager
copying optimus_manager/sessions.py -> build/lib/optimus_manager
copying optimus_manager/acpi_data.py -> build/lib/optimus_manager
copying optimus_manager/var.py -> build/lib/optimus_manager
copying optimus_manager/pci.py -> build/lib/optimus_manager
copying optimus_manager/xorg.py -> build/lib/optimus_manager
copying optimus_manager/__init__.py -> build/lib/optimus_manager
copying optimus_manager/envs.py -> build/lib/optimus_manager
copying optimus_manager/kernel.py -> build/lib/optimus_manager
copying optimus_manager/log_utils.py -> build/lib/optimus_manager
copying optimus_manager/daemon.py -> build/lib/optimus_manager
copying optimus_manager/processes.py -> build/lib/optimus_manager
copying optimus_manager/config.py -> build/lib/optimus_manager
creating build/lib/optimus_manager/hooks
copying optimus_manager/hooks/pre_daemon_start.py -> build/lib/optimus_manager/hooks
copying optimus_manager/hooks/post_daemon_stop.py -> build/lib/optimus_manager/hooks
copying optimus_manager/hooks/post_resume.py -> build/lib/optimus_manager/hooks
copying optimus_manager/hooks/pre_xorg_start.py -> build/lib/optimus_manager/hooks
copying optimus_manager/hooks/post_xorg_start.py -> build/lib/optimus_manager/hooks
copying optimus_manager/hooks/pre_suspend.py -> build/lib/optimus_manager/hooks
copying optimus_manager/hooks/__init__.py -> build/lib/optimus_manager/hooks
creating build/lib/optimus_manager/hacks
copying optimus_manager/hacks/manjaro.py -> build/lib/optimus_manager/hacks
copying optimus_manager/hacks/__init__.py -> build/lib/optimus_manager/hacks
creating build/lib/optimus_manager/client
copying optimus_manager/client/error_reporting.py -> build/lib/optimus_manager/client
copying optimus_manager/client/args.py -> build/lib/optimus_manager/client
copying optimus_manager/client/utils.py -> build/lib/optimus_manager/client
copying optimus_manager/client/client_checks.py -> build/lib/optimus_manager/client
copying optimus_manager/client/__init__.py -> build/lib/optimus_manager/client
copying optimus_manager/config_schema.json -> build/lib/optimus_manager
==> Entering fakeroot environment...
==> Starting package()...
install: cannot stat 'config/xsetup-intel.sh': No such file or directory
==> ERROR: A failure occurred in package().
    Aborting...

The specified icon for prime-hybrid for the current gpu is invalid

Bug description
using master branch to build package on arch based Distro (EndeavourOS) works fine, but it shows an error that the icon:
prime-hybrid can not be found:

Icon set in use is breeze, but it shows the same on other default icon themes.

Steps to reproduce
Steps to reproduce the behavior:

1. edit PKGBUILD to enable PLASMA feature
2. build and install package with makepkg -si
3. check if optimus-manager is running (systemctl status optimus-manager)
4. start the app

Expected behavior
icons are available and show up

Screenshots
If applicable, add screenshots to help explain your problem.

Environment
PLASMA (from archlinux repositories) installed on EndeavourOS

• Desktop environment: (e.g. KDE, GNOME)
• optimus-manager-git 1.3.1.r51.gd79cb51-1
• optimus-manager-qt-git 1.5.3.r62.ga35fe7f-1

Additional context
see here:
https://forum.endeavouros.com/t/cant-boot-os/11742/31