Bug 396462 - kscreen-doctor can't parse output name if it contains "." character (e.g. "Dell Inc. ")
Summary: kscreen-doctor can't parse output name if it contains "." character (e.g. "De...
Status: RESOLVED DUPLICATE of bug 441653
Alias: None
Product: KScreen
Classification: Plasma
Component: common (other bugs)
Version First Reported In: 5.13.2
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Sebastian Kügler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-07-13 02:53 UTC by bugreporter11
Modified: 2022-11-08 20:21 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bugreporter11 2018-07-13 02:53:32 UTC
kscreen-doctor -o reports:

Output: 446 DP-0.8 enabled connected  DisplayPort etc.

However, when I attempt to use DP-0.8 as a parameter to kscreen-doctor, it results in an error:

Unable to parse argumentsoutput.DP-0.8.enable

escaping the dot with a backslash or quoting the name does not resolve the error. I'm not sure if this is a bug. My guess is that screen names that include dots are possibly not expected and are not handled properly.
Comment 1 Frederik Gladhorn 2018-07-17 06:08:20 UTC
Hi, does xrandr report the same connector name? kscreen-doctor simply doesn't handle "." in connector names, so this is indeed a bug, the question is how to work around it - maybe there could be an alternative separator for the commands (instead of the ".").
Comment 2 bugreporter11 2018-07-17 06:21:16 UTC
(In reply to Frederik Gladhorn from comment #1)
> Hi, does xrandr report the same connector name? kscreen-doctor simply
> doesn't handle "." in connector names, so this is indeed a bug, the question
> is how to work around it - maybe there could be an alternative separator for
> the commands (instead of the ".").

Yes, xrandr reports the screen as "DP-0.8". It is a relatively new Dell monitor and the GPU is a relatively new nvidia card.

If you need more info, please let me know. Thank you.
Comment 3 Nate Graham 2022-11-08 20:21:43 UTC

*** This bug has been marked as a duplicate of bug 441653 ***