You are not logged in.

#1 2019-12-05 04:56:36

AmagicalFishy
Member
Registered: 2016-12-10
Posts: 69

Logging into Arch after logging out of Windows breaks X11 (KDE)

I dual boot Windows on an Optimus enabled Laptop (I switch to windows to play videogames wink so it's using the discrete card pretty heavily). When I'm done on Windows and switch to Arch w/ KDE, the screen goes black before SDDM makes any visible attempt to start up—and, after a minute or so, the whole computer shuts down.

If I turn it back on after this, everything works as expected. Here's [what I believe is] the relevant part of my journalctl.

Dec 05 04:12:05 computer systemd[692]: run-user-975.mount: Succeeded.
Dec 05 04:12:28 computer klauncher[718]: Qt: failed to retrieve the virtual modifier names from XKB
Dec 05 04:12:28 computer klauncher[718]: Qt: failed to retrieve the virtual modifier map from XKB
Dec 05 04:12:28 computer org.kde.kglobalaccel[705]: XIO:  fatal IO error 25 (Inappropriate ioctl for device) on X server ":0"
Dec 05 04:12:28 computer org.kde.kglobalaccel[705]:       after 677 requests (677 known processed) with 0 events remaining.
Dec 05 04:12:28 computer klauncher[718]: qt.qpa.xkeyboard: failed to compile a keymap
Dec 05 04:12:28 computer kdeinit5[724]: The X11 connection broke: I/O error (code 1)
Dec 05 04:12:28 computer kactivitymanagerd[754]: Qt: failed to retrieve the virtual modifier names from XKB
Dec 05 04:12:28 computer kactivitymanagerd[754]: Qt: failed to retrieve the virtual modifier map from XKB
Dec 05 04:12:28 computer kactivitymanagerd[754]: qt.qpa.xkeyboard: failed to compile a keymap
Dec 05 04:12:28 computer kglobalaccel5[742]: The X11 connection broke: I/O error (code 1)
Dec 05 04:12:28 computer kactivitymanagerd[754]: The X11 connection broke (error 1). Did the X11 server die?
Dec 05 04:12:28 computer systemd[692]: Stopped target Main User Target.
Dec 05 04:12:28 computer systemd[692]: Stopping D-Bus User Message Bus...
Dec 05 04:12:28 computer systemd[692]: dbus.service: Succeeded.
Dec 05 04:12:28 computer systemd[692]: Stopped D-Bus User Message Bus.

I'm using the xf86-video-intel and xf86-video-nouveau drivers:

Provider 0: id: 0x47 cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 4 outputs: 4 associated providers: 1 name:Intel
Provider 1: id: 0xcf cap: 0x7, Source Output, Sink Output, Source Offload crtcs: 4 outputs: 2 associated providers: 1 name:nouveau

This is a pretty clean install (reinstalled Arch a few days ago). I actually had a similar problem trying to use proprietary Nvidia drivers and Optimus-Manager before reinstalling—and reinstalled because of this (I needed it anyway). I'm not using Optimus-Manager now, just the regular ol' PRIME stuff.

The only seemingly relevant thing in Xorg.log is:

[   110.138] (EE) Failed to open authorization file "/var/run/sddm/{b57113b9-99ab-40b9-a7c3-d10aab6cea2f}": No such file or directory

... but I suspect this isn't the problem, because I can't even switch to a different TTY when this is happening.

I think the key things here are that this only happens when I move from Windows (which uses the NVIDIA card) to Arch, and that the whole system shuts down after trying to boot into Arch (no cursor or TTY or anything, just a shut down). Might it be that there's some Arch-expects-startup-on-Intel while Windows-shut-down-on-NVIDIA conflicts?

Last edited by AmagicalFishy (2019-12-05 12:52:58)

Offline

#2 2019-12-05 08:27:09

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,728

Re: Logging into Arch after logging out of Windows breaks X11 (KDE)

How do you "switch" reboot or shutdown? In general, ensure: https://wiki.archlinux.org/index.php/Du … t_Start-Up

If you've done that then this is likely to be a BIOS/Firmware bug in that it doesn't properly clean up state. Try to get yourself an update here.

Online

#3 2019-12-05 12:54:48

AmagicalFishy
Member
Registered: 2016-12-10
Posts: 69

Re: Logging into Arch after logging out of Windows breaks X11 (KDE)

Ah! I didn't know about that. On Linux, I generally "shutdown -r now" if I want to switch to Windows, and on Windows I use the restart button. I turned off fast start up to see if that changed anything, restarted Windows, booted into Arch, and ran into the same problem. I'll do some more involved testing later today.

Last edited by AmagicalFishy (2019-12-05 12:54:59)

Offline

#4 2019-12-05 13:08:34

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,728

Re: Logging into Arch after logging out of Windows breaks X11 (KDE)

Reboot from Windows should not invoke the implications from the fast startup option, so in that regard it should be "safe", so yes this does sound like a BIOS/UEFI bug

Online

#5 2019-12-06 04:51:48

AmagicalFishy
Member
Registered: 2016-12-10
Posts: 69

Re: Logging into Arch after logging out of Windows breaks X11 (KDE)

Strange, there were no options relevant to the video card in the BIOS. Actually, it was surprisingly sparse (I'd expect it to be unlocked or something given that I got the computer from Sager).

I tried messing with some stupid settings, like nomodeset, but that didn't do anything. Or, it did something. When I removed the nomodeset option (putting the boot parameters back to what they were before), I could log into SDDM. That is, even going from Windows to Arch, the SDDM login screen pops up.

Now, though, when I try to login, the screen goes black and the computer shuts down. Similarly, when I try to switch to another TTY, the screen goes black and the computer shuts down. What a mess this is. sad

I'll check out what the logs say in the morning via Live USB

Edit: I left it off overnight, logged into Arch this morning and everything worked fine... ? I can't even speculate on what's happening anymore.

Last edited by AmagicalFishy (2019-12-06 13:08:22)

Offline

Board footer

Powered by FluxBB