Bug 1010615 - kdmrc: ServerCmd= key not working
Summary: kdmrc: ServerCmd= key not working
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kde-workspace
Version: 19
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-22 03:30 UTC by Bob Gleitsmann
Modified: 2013-10-07 04:39 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-07 04:39:44 UTC
Type: Bug


Attachments (Terms of Use)

Description Bob Gleitsmann 2013-09-22 03:30:27 UTC
Description of problem:
First of all, I can't find the source code. There is no SRPM for the package that yum reports /usr/bin/kdm as being part of (indicated  immediately below). Second, if the X server is changed in kdmrc from the default location, kdm doesn't recognize this and loads the default X server. Yes, some people set up an alternate graphics stack on their machine to test graphics drivers. 
Maybe I should just use xdm. At least the source code can be found.

Version-Release number of selected component (if applicable):
kdm-4.11.1-2.fc19.x86_64

How reproducible:
It always happens. 

Steps to Reproduce:
1. setup kdmrc with with a ServerCmd statement pointing to a non-default Xorg server
2.Reboot and take a look at the Xorg.0.log file and you will see that the default Xorg server is running
3. That's all there is to it.

Actual results:


Expected results:


Additional info:
I've been able to do this for a couple of years and it just changed. I just loaded a pile of updates, and I guess a new version of kdm was among them.

Comment 1 Martin Bříza 2013-09-23 09:53:46 UTC
Hi Bob,
KDM is part of the kde-workspace SRPM.
Also, when I was last testing it (at 4.10.90), it definitely did load ServerCmd from kdmrc. Only exception for that is when the display that it is loading the command for is on a seat different from seat0, then it uses /lib/systemd/systemd-multi-seat-x to start it on a different seat.
Is this your use case, too, please?
Thanks,
Martin

Comment 2 Bob Gleitsmann 2013-09-23 17:01:30 UTC
Hi Martin,

The version that you tested works (or worked) correctly. The new one doesn't. I am not using multi-seat, or multi-head either. Just one monitor. 
I will try again retrieving the source RPM. It would be nice if you could do that with yum, but that didn't work, Actually, source RPMs do not need to install at any particular location, and I would prefer that they didn't install somewhere in /usr. I usually put source code somewhere under my home directory to avoid access rights problems. The package name reported by yum for the source is not locatable by yum. Perhaps there is a different repo for source code? If it were my world, the documentation for and tools for retrieving source code would be easy to find and easy to use. At present, that doesn't seem to be the case.

Anyway, thanks for your reply. I appreciate your help.

Bob

Comment 3 Martin Bříza 2013-09-24 11:42:15 UTC
Before I look into the ServerCmd issue, you can download the source rpm by this command:
 yumdownloader --source kde-workspace

Comment 4 Bob Gleitsmann 2013-10-07 04:39:44 UTC
OK, here's the story. Not really in kdm. kdm dutifully passes the ServerCmd value in kdmrc to systemd-multi-seat-x which ignores it. Removing systemd-multi-seat-x from /lib/systemd solves the problem for now. I see that you were trying to tell me about this. However, I have no idea where one would specify what seat one is trying to start. I didn't tell it any other seat than I always have (which is probably nothing). 
So I guess I should file a bug report against systemd.  But I am closing this one.
Or maybe kdm could have a multi-seat option. I don't know for sure, but I think multi-seat is the exception and you should have to intentionally turn it on. From what I read, multi-seat means two keyboards, not two screens. How many people have that? 

Best Wishes,

Bob


Note You need to log in before you can comment on or make changes to this bug.