Date: Thu, 7 Oct 1999 10:57:21 -0700 (PDT) From: kientzle@acm.org To: freebsd-gnats-submit@freebsd.org Subject: ports/14188: kdm bug and workaround Message-ID: <19991007175721.D313C158B6@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 14188 >Category: ports >Synopsis: kdm bug and workaround >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-ports >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Oct 7 11:00:00 PDT 1999 >Closed-Date: >Last-Modified: >Originator: Tim Kientzle >Release: 3.3-RELEASE >Organization: >Environment: FreeBSD clover.kientzle.com 3.3-RELEASE FreeBSD 3.3-RELEASE #0: Fri, Oct 1, 18:39:21 PDT 1999 root@clover.kientzle.com:/usr/src/sys/compile/CLOVER i386 >Description: The kdm included with kdebase 1.1 by default does not terminate the server after each session. However, it forgets the server is running and still needs to be managed. Thus, kdm simply exits after the first login session, leaving the X server running. >How-To-Repeat: Install the kde11 packages. Recompile kdebase11 from the ports collection. (I've filed another bug report about the kdebase11 package not being correctly compiled.) Run kdm, login and log back out again. You should see the X server still running, but kdm is no longer running. >Fix: 1) Fix kdm so it doesn't forget about running X servers ;-) 2) Workaround: Include the following line in the supplied xdm-config file so that people who try to use kdm won't encounter this bug. terminateServer: true is probably a good idea anyway. DisplayManager._0.terminateServer: true >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991007175721.D313C158B6>