Hi, quickly “duckduckgoing” your pasted string, lead me to this relatively recent Fedora Bug Report:
Red Hat Bugzilla – Bug 1398424
It seems it has been reopened in late July ‘17. Looking over the bug history, I couldn’t notice the same fix you mentioned being suggested likewise, redirecting to a Arch Linux Forums’ thread, where it was stated that appending this boot flag apparently seemed to fix the problem.
Did you saw this solution looking for your error on web like I did?
I’m asking this because I wonder why would ever anyone think of adding this KMS parameter, as basically
video=SVIDEO-1:d disables output for a S-Video connector on default port 1. Since I doubt anyone still uses S-Video monitors in 2017, this really looks weird.
The thing looks all the more strange If you notice all references online practically point to that same Arch Linux thread, and any more in-depth research resulted for me in drawing in a blank. So it seems no open knows where this bug comes from and why disabling S-Video output should fix it.
On the Fedora bug report, someone mentions a possible problem with the i915kms driver, inside its S-Video related code section, which would arise only when dealing with certain GPUs: it seems nothing more than a supposition.
Anyway, unless someone here provides a proper solution, in order to solve at least the logout/lock screen problems, I would first try (blind tentative) to switch from
xf86-video-intel to Xorg’s modesetting(4), the framebuffer driver that allows sharing KMS console drivers with a X session. To do this, you should first of all edit
/etc/X11/xorg.conf and replace
"intel", next toDriver entry for your Intel GPU Device section, with
"modesetting". A common Section should look like that:
Option "AccelMethod" "glamor"
Change BusID value to match yours (If not specified already in your xorg.conf ignore this line)
AccelMethod Option forces 3D video acceleration;
Remember also that:
Option "ZaphodHeads" "string"
Can be used to specify output, as listed in
xrandr (for example
Otherwise, you can try the other way round: disabling i915 and launching Xorg with
xf86-video-intel. I think this is more likely going to work, as problem is suspected affecting i915. Xorg will still work normally as before using the
intel driver, but you’ll loose your tty* console resolution and smooth fonts. If you don’t use virtual console very much, and always stay on Xorg, you could bare with that. To disable i915 KMS, just add
i915.modeset=0 kernel boot parameters, the way you did with
video=..., depending on your bootloader.
With a stroke of luck, an update in i915, xf86-video-intel or maybe even Linux Kernel shall work out your problem. It would be good to understand where the problem lies actually, to know at least which update to wait