Unable to reload SDDM about optimus-manager HOT 9 CLOSED

Boot directly in Nvidia mode works.

Here is requested log :)

from optimus-manager.

Partially fixed it by changing switching=nouveau to switching=bbswitch.
With this configuration, after changing the mode from Intel to Nvidia, I see the cursor and the message "Could not sync environment to dbus". And if I press the Ctrl + Alt + Backspace key combination (restart Xorg), the desktop environment starts up normally on the desired video card.
Here is my /var/log/Xorg.0.log for "Could not sync environment to dbus" error.

Also I have tried all this solitions.

from optimus-manager.

Do you have any issues if you boot directly in Nvidia mode ? (optimus-manager --set-startup nvidia)

To help me debug, please do the following with switching=bbswitch enabled :

• Boot into Intel mode
• Try to switch to nvidia mode and do that Ctrl + Alt + Backspace trick to recover the session
• Paste the log of the sddm service here (You can redirect it to a file like this : journalctl -u sddm -b0 --no-pager > /path/to/file.txt)

from optimus-manager.

I can confirm this exact issue. If more logs are needed, I can also provide them.

from optimus-manager.

Sorry of the lack of updates. Could you test the current github master branch ?

from optimus-manager.

I'll test it today and I'll update this comment.
EDIT: It works! The reported error: "Could not sync environment to dbus" is no longer present and I successfully enter the KDE plasma session without requiring any key combination trick. It also goes faster during the loading of the desktop and inside the desktop itself on both modes. no issues were encountered so far.
EDIT2: It still happens when reloading. The behaviour is the exact same one as the report. So far, this is the only issue. Booting from NVIDIA also still works.

from optimus-manager.

Yes, with the latest changes from the master branch everything works fine. Switching works both ways without any problems.

@Destroyerrrocket, what version of the kernel are you using? I tested on linux-lts.

from optimus-manager.

@Shatur95 linux, I'll check linux-lts and update this comment. Could you also check if reloading works for you?
EDIT: For some reason, linux-lts does not cause the reloading error. Also, it doesn't seems to happen in all reloads on linux. I've managed to cause the error to happen once when I quickly reloaded the intel card when the desktop had just finished loading, but it is not a consistent error, so for the moment, thank you so much @Askannz for the info!

from optimus-manager.

@Destroyerrrocket, yes, linux work for me too :)

from optimus-manager.