Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to reload SDDM #52

Closed
ghost opened this issue Feb 19, 2019 · 9 comments
Closed

Unable to reload SDDM #52

ghost opened this issue Feb 19, 2019 · 9 comments

Comments

@ghost
Copy link

ghost commented Feb 19, 2019

Describe the bug
When I switch video card, SDDM does not start, hangs on "Reaching graphical target". But after rebooting the system, the video card change is applied and works as expected. Is short I need to reboot OS to change card.

System info
Please include :
Operating System: Arch Linux
KDE Plasma Version: 5.15.0
KDE Frameworks Version: 5.55.0
Qt Version: 5.12.1
Kernel Version: 4.20.10-arch1-1-ARCH
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz
Memory: 19,5 ГиБ

Logs

dmesg

Xorg

journalctl -u display-manager -b0 --no-pager
-- Logs begin at Mon 2019-02-18 21:06:12 EET, end at Tue 2019-02-19 15:22:37 EET. --
-- No entries --
journalctl -u optimus-manager -b0 --no-pager
-- Logs begin at Mon 2019-02-18 21:06:12 EET, end at Tue 2019-02-19 15:24:24 EET. --
фев 19 15:17:24 AcerAspire5 systemd[1]: Started Optimus Manager Commands Daemon.
фев 19 15:17:24 AcerAspire5 python[532]: Optimus Manager (Daemon) version 0.7.1
фев 19 15:17:24 AcerAspire5 python[532]: Awaiting commands

/etc/X11/ contains nothing related to GPUs except 10-optimus-manager.conf

@Shatur
Copy link
Contributor

Shatur commented Feb 23, 2019

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.

@Askannz
Copy link
Owner

Askannz commented Mar 3, 2019

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)

@Shatur
Copy link
Contributor

Shatur commented Mar 3, 2019

Boot directly in Nvidia mode works.

Here is requested log :)

@Destroyerrrocket
Copy link

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

@Askannz
Copy link
Owner

Askannz commented Mar 18, 2019

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

@Destroyerrrocket
Copy link

Destroyerrrocket commented Mar 18, 2019

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.

@Shatur
Copy link
Contributor

Shatur commented Mar 18, 2019

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.

@Destroyerrrocket
Copy link

Destroyerrrocket commented Mar 18, 2019

@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!

@Shatur
Copy link
Contributor

Shatur commented Mar 18, 2019

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

@ghost ghost closed this as completed Mar 18, 2019
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants