kdm with no local X starting
When starting /usr/local/bin/kdm (e.g. from /etc/ttys), this starts kdm-bin (KDM window manager) but also a local X server. On a server machine this often is not needed. How to configure xdm to not start a local X server? So far I came up only with # vi /usr/local/share/config/kdm/kdmrc ServerCmd= (instead of ServerCmd=/usr/local/bin/X -br) but there are probably more clean ways ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
How to make kdm not pass an option -nolisten tcp to Xserver?
kdm just always sets this flag. How to get rid of it? Yuri ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to make kdm not pass an option -nolisten tcp to Xserver?
kdm just always sets this flag. How to get rid of it? :-) I found the answer myself: disable it in /usr/local/kde4/share/config/kdm/kdmrc Yuri ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: kde/kdm + nsswitch + ldap = nologon
I'd like to duplicate your setup none-the-less to learn. Can you provide
all the pam files, showconfig for the openldap and kdm-related port so I
can run with the same port?
gdm offers pam integration by the description. I'd be looking at options
in pam, and making sure the console logins work off pam too to make the
comparison to apples to apples the same.
Please give me the showconfig from the items above.
Was going to send as an e-mail to keep the gigantic post off the list, but
my mailer went stupid this morning...
OK...we'll start with the server. Note that while I'm using the SASL
portion of the port, I'm not using any of the SASL type functionality yet.
Just incase you missed the part from the original post... I ran into a bug
report from last summer that appears to still be open with exactly the same
issue (http://www.freebsd.org/cgi/query-pr.cgi?pr=124321). I get the same
error messages and such, with any luck it's based on misconfiguration of
something.
I hope all of this helps.
Joe.
From the ldap server:
shadow# uname -a
FreeBSD shadow.casa.local 6.3-STABLE FreeBSD 6.3-STABLE #1: Sat Apr 5
14:49:53 EDT 2008 j...@shadow.casa.local:/usr/obj/usr/src/sys/GENERIC i386
shadow# pkg_info |grep ldap
nss_ldap-1.257 RFC 2307 NSS module
openldap-sasl-client-2.4.11 Open source LDAP client implementation with
SASL2 support
openldap-sasl-server-2.4.11_2 Open source LDAP server implementation
pam_ldap-1.8.4 A pam module for authenticating with LDAP
shadow# cd /usr/ports/net/openldap24-server
shadow# make showconfig
=== The following configuration options are available for
openldap-sasl-server-2.4.11_2:
SASL=on With (Cyrus) SASL2 support
DNSSRV=off With Dnssrv backend
PASSWD=off With Passwd backend
PERL=off With Perl backend
RELAY=off With Relay backend
SHELL=off With Shell backend (disables threading)
SOCK=off With Sock backend
ODBC=off With SQL backend
RLOOKUPS=off With reverse lookups of client hostnames
SLP=off With SLPv2 (RFC 2608) support
SLAPI=off With Netscape SLAPI plugin API
TCP_WRAPPERS=on With tcp wrapper support
BDB=on With BerkeleyDB support
ACCESSLOG=off With In-Directory Access Logging overlay
AUDITLOG=off With Audit Logging overlay
CONSTRAINT=off With Attribute Constraint overlay
DDS=off Dynamic Directory Services overlay
DENYOP=off With Deny Operation overlay
DYNGROUP=off With Dynamic Group overlay
DYNLIST=off With Dynamic List overlay
LASTMOD=off With Last Modification overlay
MEMBEROF=off With Reverse Group Membership overlay
PPOLICY=off With Password Policy overlay
PROXYCACHE=off With Proxy Cache overlay
REFINT=off With Referential Integrity overlay
RETCODE=off With Return Code testing overlay
RWM=off With Rewrite/Remap overlay
SEQMOD=on Sequential Modify overlay
SYNCPROV=on With Syncrepl Provider overlay
TRANSLUCENT=off With Translucent Proxy overlay
UNIQUE=off With attribute Uniqueness overlay
VALSORT=off With Value Sorting overlay
SMBPWD=off With Samba Password hashes overlay
DYNAMIC_BACKENDS=on Build dynamic backends
=== Use 'make config' to modify these settings
shadow# cat slapd.conf
#
# See slapd.conf(5) for details on configuration options.
# This file should NOT be world readable.
#
include /usr/local/etc/openldap/schema/core.schema
include /usr/local/etc/openldap/schema/cosine.schema
include /usr/local/etc/openldap/schema/inetorgperson.schema
include /usr/local/etc/openldap/schema/nis.schema
include /usr/local/etc/openldap/schema/samba.schema
pidfile /var/run/openldap/slapd.pid
argsfile/var/run/openldap/slapd.args
# Load dynamic backend modules:
modulepath /usr/local/libexec/openldap
moduleload back_bdb
###
###
## BDB database definitions
###
###
## main part ##
databasebdb
directory /var/db/openldap-data
suffix dc=casa,dc=local
rootdn cn=Manager,dc=casa,dc=local
rootpw {crypt}PasswordGoesHere
access control #
access to * by * write
# users can authenticate and change their password
access to
attrs=userPassword,sambaNTPassword,sambaLMPassword,sambaPwdLastSet,sambaPwdMustChange,shadowLastChange,shadowMax
by dn=cn=samba,ou=DSA,dc=casa,dc=local write
by dn=cn=smbldap-tools,ou=DSA,dc=casa,dc=local write
by dn=cn=nssldap,ou=DSA,dc=casa,dc=local write
by self write
by anonymous auth
by * none
# some attributes need to be readable anonymously so that 'id user' can
answer correctly
access to
attrs=objectClass,entry,homeDirectory,uid,uidNumber,gidNumber,memberUid
kde/kdm + nsswitch + ldap = nologon
I'm trying to implement SSO using Samba-3.2.4 with an LDAP backend. The intent is to use ldap directly for FBSD clients and Samba for MS Windows clients. The LDAP server (openldap 2.4.11) is running on a FBSD 6.3 server and is setup and seems to be working fine, I can log in locally or through SSH using the ldap accounts. I'm working on the first client which is a FBSD 7.1 machine. I can use ldap to login on this machine, but I'm having issues with logging in using kdm. I can see all the users both from local files and from ldap, but I can't log in using either. Even when kdm won't allow a login, I can ctrlaltF8 and get a normal login shell and login with local or ldap accounts. The ldap lines are included in my /etc/pam.d/kde file. If I remove ldap from the nsswitch.conf file it will start working with local logins on kdm again. I ran into a bug report from last summer that appears to still be open with exactly the same issue (http://www.freebsd.org/cgi/query-pr.cgi?pr=124321). Does anyone know a workaround or have a patch for the issue? I can provide config files and such if anyone thinks it might help. Thanks, Joe. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: kde/kdm + nsswitch + ldap = nologon
I guess it's probably worth mentioning that I'm working with KDE 3.5.10 right now. Is this something likely solved in KDE 4.2 so I've hit my reason to upgrade? Joe. Joe Kraft wrote: I'm trying to implement SSO using Samba-3.2.4 with an LDAP backend. The intent is to use ldap directly for FBSD clients and Samba for MS Windows clients. The LDAP server (openldap 2.4.11) is running on a FBSD 6.3 server and is setup and seems to be working fine, I can log in locally or through SSH using the ldap accounts. I'm working on the first client which is a FBSD 7.1 machine. I can use ldap to login on this machine, but I'm having issues with logging in using kdm. I can see all the users both from local files and from ldap, but I can't log in using either. Even when kdm won't allow a login, I can ctrlaltF8 and get a normal login shell and login with local or ldap accounts. The ldap lines are included in my /etc/pam.d/kde file. If I remove ldap from the nsswitch.conf file it will start working with local logins on kdm again. I ran into a bug report from last summer that appears to still be open with exactly the same issue (http://www.freebsd.org/cgi/query-pr.cgi?pr=124321). Does anyone know a workaround or have a patch for the issue? I can provide config files and such if anyone thinks it might help. Thanks, Joe. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: kde/kdm + nsswitch + ldap = nologon
On Sat, Mar 7, 2009 at 7:59 AM, Joe Kraft jvk-l...@thekrafts.org wrote: I'm trying to implement SSO using Samba-3.2.4 with an LDAP backend. The intent is to use ldap directly for FBSD clients and Samba for MS Windows clients. The LDAP server (openldap 2.4.11) is running on a FBSD 6.3 server and is setup and seems to be working fine, I can log in locally or through SSH using the ldap accounts. I'm working on the first client which is a FBSD 7.1 machine. I can use ldap to login on this machine, but I'm having issues with logging in using kdm. I can see all the users both from local files and from ldap, but I can't log in using either. Even when kdm won't allow a login, I can ctrlaltF8 and get a normal login shell and login with local or ldap accounts. The ldap lines are included in my /etc/pam.d/kde file. If I remove ldap from the nsswitch.conf file it will start working with local logins on kdm again. I ran into a bug report from last summer that appears to still be open with exactly the same issue (http://www.freebsd.org/cgi/query-pr.cgi?pr=124321 ). Does anyone know a workaround or have a patch for the issue? I can provide config files and such if anyone thinks it might help. Thanks, Joe. True SSO is accomplished by Kerberos. Your LDAP implementation is re-authenticating/re-authorizing on every service. I'm by NO means an expert with pam -- it confuses me, but there are some basic concepts that I think there might be missing in your setup. First question I've got is shouldn't you need to create the rules for kdm in a file called 'kdm' in pam? Second is that some options/arguments that pam can use such as USE_FIRST_PASS would probably help you here. Third is whether the sufficient/required column in the pam file is there. Now we have to deal weather kdm uses pam or nsswitch. And if it uses nsswitch, then we have to go through all that troubleshooting all over again. Or maybe it doesn't even have any concept to use alternate auth mechanisms other than just the local files... I'm only providing an insight to something your eyes may have overlooked. I hope this triggers something to get it working. G'luck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: kde/kdm + nsswitch + ldap = nologon
Tim Judd wrote: On Sat, Mar 7, 2009 at 7:59 AM, Joe Kraft jvk-l...@thekrafts.org wrote: I'm trying to implement SSO using Samba-3.2.4 with an LDAP backend. The intent is to use ldap directly for FBSD clients and Samba for MS Windows clients. The LDAP server (openldap 2.4.11) is running on a FBSD 6.3 server and is setup and seems to be working fine, I can log in locally or through SSH using the ldap accounts. I'm working on the first client which is a FBSD 7.1 machine. I can use ldap to login on this machine, but I'm having issues with logging in using kdm. I can see all the users both from local files and from ldap, but I can't log in using either. Even when kdm won't allow a login, I can ctrlaltF8 and get a normal login shell and login with local or ldap accounts. The ldap lines are included in my /etc/pam.d/kde file. If I remove ldap from the nsswitch.conf file it will start working with local logins on kdm again. I ran into a bug report from last summer that appears to still be open with exactly the same issue (http://www.freebsd.org/cgi/query-pr.cgi?pr=124321 ). Does anyone know a workaround or have a patch for the issue? I can provide config files and such if anyone thinks it might help. Thanks, Joe. True SSO is accomplished by Kerberos. Your LDAP implementation is re-authenticating/re-authorizing on every service. I'm by NO means an expert with pam -- it confuses me, but there are some basic concepts that I think there might be missing in your setup. First question I've got is shouldn't you need to create the rules for kdm in a file called 'kdm' in pam? Second is that some options/arguments that pam can use such as USE_FIRST_PASS would probably help you here. Third is whether the sufficient/required column in the pam file is there. Now we have to deal weather kdm uses pam or nsswitch. And if it uses nsswitch, then we have to go through all that troubleshooting all over again. Or maybe it doesn't even have any concept to use alternate auth mechanisms other than just the local files... I'm only providing an insight to something your eyes may have overlooked. I hope this triggers something to get it working. G'luck Thanks for the thoughts, I had Kerberos set up once when I was going the other way...with all clients working through an AD domain. I'm trying to go the other way now and get everything working through a Samba Domain. I might look into it again in the future once I get the basics working. I thought maybe I had it when you mentioned creating rules for kdm instead of kde in pam. Unfortunately it didn't work. kdm seems to use nsswitch to get the names, because if I use the line passwd: files ldap in nsswitch.conf kdm shows me all the ldap users as well as the local users with their icons down the left side of the login window. I just can't use them to login, no matter what I do it tells me my password is invalid. I can't even get it to login with a local account from 'files'. What I can do is drop to one of the other ttys and use an accounts with the same password that failed in kdm to login. I'm using the same pam file for login as I am for kde (and now kdm). All I have to do is change the line to passwd: files and I can login again with the local accounts through kdm again. Certainly doesn't make sense to me right now... Joe. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: kde/kdm + nsswitch + ldap = nologon
On Sat, Mar 7, 2009 at 4:10 PM, Joe Kraft jvk-l...@thekrafts.org wrote: Tim Judd wrote: On Sat, Mar 7, 2009 at 7:59 AM, Joe Kraft jvk-l...@thekrafts.org wrote: I'm trying to implement SSO using Samba-3.2.4 with an LDAP backend. The intent is to use ldap directly for FBSD clients and Samba for MS Windows clients. The LDAP server (openldap 2.4.11) is running on a FBSD 6.3 server and is setup and seems to be working fine, I can log in locally or through SSH using the ldap accounts. I'm working on the first client which is a FBSD 7.1 machine. I can use ldap to login on this machine, but I'm having issues with logging in using kdm. I can see all the users both from local files and from ldap, but I can't log in using either. Even when kdm won't allow a login, I can ctrlaltF8 and get a normal login shell and login with local or ldap accounts. The ldap lines are included in my /etc/pam.d/kde file. If I remove ldap from the nsswitch.conf file it will start working with local logins on kdm again. I ran into a bug report from last summer that appears to still be open with exactly the same issue (http://www.freebsd.org/cgi/query-pr.cgi?pr=124321 ). Does anyone know a workaround or have a patch for the issue? I can provide config files and such if anyone thinks it might help. Thanks, Joe. True SSO is accomplished by Kerberos. Your LDAP implementation is re-authenticating/re-authorizing on every service. I'm by NO means an expert with pam -- it confuses me, but there are some basic concepts that I think there might be missing in your setup. First question I've got is shouldn't you need to create the rules for kdm in a file called 'kdm' in pam? Second is that some options/arguments that pam can use such as USE_FIRST_PASS would probably help you here. Third is whether the sufficient/required column in the pam file is there. Now we have to deal weather kdm uses pam or nsswitch. And if it uses nsswitch, then we have to go through all that troubleshooting all over again. Or maybe it doesn't even have any concept to use alternate auth mechanisms other than just the local files... I'm only providing an insight to something your eyes may have overlooked. I hope this triggers something to get it working. G'luck Thanks for the thoughts, I had Kerberos set up once when I was going the other way...with all clients working through an AD domain. I'm trying to go the other way now and get everything working through a Samba Domain. I might look into it again in the future once I get the basics working. I thought maybe I had it when you mentioned creating rules for kdm instead of kde in pam. Unfortunately it didn't work. kdm seems to use nsswitch to get the names, because if I use the line passwd: files ldap in nsswitch.conf kdm shows me all the ldap users as well as the local users with their icons down the left side of the login window. I just can't use them to login, no matter what I do it tells me my password is invalid. I can't even get it to login with a local account from 'files'. What I can do is drop to one of the other ttys and use an accounts with the same password that failed in kdm to login. I'm using the same pam file for login as I am for kde (and now kdm). All I have to do is change the line to passwd: files and I can login again with the local accounts through kdm again. Certainly doesn't make sense to me right now... Joe. I'd like to duplicate your setup none-the-less to learn. Can you provide all the pam files, showconfig for the openldap and kdm-related port so I can run with the same port? I use gnome at the moment, so here's what I did.. $ pkg_info -W gdm /usr/local/sbin/gdm was installed by package gdm-2.20.8 $ pkg_info -qo gdm-2.20.8 x11/gdm $ cd /usr/ports/x11/gdm $ make showconfig === The following configuration options are available for gdm-2.20.8: IPV6=off (default) Enable IPv6 support KEYRING=on (default) Enable GnomeKeyring/PAM integration LOG_LIMIT=on (default) Limit ~/.xsession-errors size === Use 'make config' to modify these settings gdm offers pam integration by the description. I'd be looking at options in pam, and making sure the console logins work off pam too to make the comparison to apples to apples the same. Please give me the showconfig from the items above. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
passwordless login not working in KDM
Hello! The instructions at: http://freebsd.kde.org/faq.php#HowdoIenablepasswordlessconvenienceloginsinKDMIcheckedthecheckboxintheLoginManagerControlbutKDMwontlogmein seem perfectly clear and, I believe, I followed them correctly: m...@corbulon:~ (1004) ls -l /etc/pam.d/kde* -rw-r--r-- 1 root wheel 458 Dec 2 2007 /etc/pam.d/kde -rw-r--r-- 2 root wheel 459 Dec 29 2007 /etc/pam.d/kde-np m...@corbulon:~ (1005) diff -U2 /etc/pam.d/kde* --- /etc/pam.d/kde 2007-12-02 12:12:44.0 -0500 +++ /etc/pam.d/kde-np 2007-12-29 17:51:31.0 -0500 @@ -8,5 +8,5 @@ #auth sufficient pam_krb5.so no_warn try_first_pass #auth sufficient pam_ssh.so no_warn try_first_pass -auth requiredpam_unix.so no_warn try_first_pass +#auth requiredpam_unix.so no_warn try_first_pass # account Unfortunately, the password-less logins are still rejected for the two users, who are listed: m...@corbulon:~ (1006) grep NoPass /opt/share/config/kdm/kdmrc NoPassEnable=true NoPassUsers=mi,tulik Please, advise... Thanks! -mi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: KDM stopping
On Thu, 27 Nov 2008, Lowell Gilbert wrote: Pieter Donche [EMAIL PROTECTED] writes: FreeBSD-7.0-RELEASE, with KDE as desktop environment and KDM as display manager. I have 2 users, say user1 and user2. Boot, KDM login as user1, OK. Then I do a close session. OK, KDM presents me again with the KDM login screen, login as user2, OK. Then again, close session. Now, the KDM login screen does not come back. I am stuck with a cursor blinking at the upper left corner. Ctrl-Alt-F1 brings me to the console, Ctrl-Alt-F7: no X, just a login:prompt If I reboot and do the same thing, but now first with user2, then user1 - exactly same behaviour (X dies at the second close session). So, it's not connected with user2. Anyone a idea what could be wrong? Below are some log details: Does this happen with xdm as well? Have you checked with the FreeBSD kde mailing list? If I switch in KDM to using TWM window manager (instead of KDE), login and then logout, I'm stuck in the same way. XDM: If I edit /etc/ttys to use xdm instead of kdm and reboot I get login/password prompt, then a very primitive TWM window manager, When choose exit on the menu (with one gets by left-clicking the mouse) the frames arround the windows disappear and I don't get the menu back, the only thing I can do is to to console mode and shutdown -r now (and first edit /etc/ttys again for kdm) Is there a command to - restart the kdm window manager (after it died) from a root console prompt? - stop en start a running kwm window manager from a root console prompt? Concerning my initial problem - I remember that I wanted to change the home-dir of both user1 and user2, therefore in console as root did a rmuser, then adduser for both. Can this cause this dying of KDM manager? The /var/log/kdm-log shows: -- ... X.Org X Server 1.4.0 Release Date: 5 September 2007 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 7.0-RELEASE i386 Current Operating System: FreeBSD pclinwi74.cmi.ua.ac.be 7.0-RELEASE FreeBSD 7. 0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008 [EMAIL PROTECTED]:/usr/ obj/usr/src/sys/GENERIC i386 Build Date: 13 February 2008 05:50:12PM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Wed Nov 26 16:27:31 2008 (EE) Unable to locate/open config file New driver is i810 (==) Using default built-in configuration (55 lines) (EE) Failed to load module fbdev (module does not exist, 0) (II) Module ddc already built-in (II) Module ramdac already built-in FreeFontPath: FPE /usr/local/lib/X11/fonts/misc/ refcount is 2, should be 1; fixing. FreeFontPath: FPE /usr/local/lib/X11/fonts/misc/ refcount is 2, should be 1; fixing. (EE) I810(0): V_BIOS address 0x0 out of range Fatal server error: Caught signal 11. Server aborting X.Org X Server 1.4.0 Release Date: 5 September 2007 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 7.0-RELEASE i386 Current Operating System: FreeBSD pclinwi74.cmi.ua.ac.be 7.0-RELEASE FreeBSD 7. 0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008 [EMAIL PROTECTED]:/usr/ obj/usr/src/sys/GENERIC i386 Build Date: 13 February 2008 05:50:12PM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Wed Nov 26 16:43:42 2008 (EE) Unable to locate/open config file New driver is i810 (==) Using default built-in configuration (55 lines) (EE) Failed to load module fbdev (module does not exist, 0) (EE) I810(0): V_BIOS address 0x0 out of range (EE) I810(0): VBE initialization failed. (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found --- /var/log/messages contains: -- .. Nov 26 16:29:03 pclinwi74 kernel: pid 853 (Xorg), uid 0: exited on signal 11 (c ore dumped) Nov 26 16:29:03 pclinwi74 kdm-bin[850]: X server for display :0 terminated unex pectedly Nov 26 16:29:03 pclinwi74 kdm-bin: :0[1137]: IO Error in XOpenDisplay Nov 26 16:29:03 pclinwi74 kdm-bin[850]: Display :0 cannot be opened Nov 26 16:29:03 pclinwi74 kdm-bin[850]: Unable to fire up local display :0; dis abling. Nov 26 16:29:30 pclinwi74 login: ROOT LOGIN (root) ON ttyv0 Nov 26 16:43:40 pclinwi74 shutdown: reboot by root: Nov 26 16:43:42 pclinwi74 kdm-bin[850]: X server for display :0 terminated unex pectedly Nov 26 16:43:42 pclinwi74 kdm-bin[850]: Unable to fire up local display :0; dis abling. Nov 26 16:43:42 pclinwi74 syslogd
Re: KDM stopping
On Fri, 28 Nov 2008 09:37:24 +0100 (CET), Pieter Donche [EMAIL PROTECTED] wrote: XDM: If I edit /etc/ttys to use xdm instead of kdm and reboot I get login/password prompt, then a very primitive TWM window manager, These are the default settings (TWM with some xterms). You can edit your ~/.xinitrc in order to launch the window manager or desktop environment you like. When choose exit on the menu (with one gets by left-clicking the mouse) the frames arround the windows disappear and I don't get the menu back, the only thing I can do is to to console mode and shutdown -r now (and first edit /etc/ttys again for kdm) The session controller for this setting isn't the window manager, it is one of the xterms which you can close using the exit command or pressing Ctrl+D when focused. What you did: You terminated the window manager so the xterms are there on their own, without any window manager (you see that you can still select focus, but there are no window decorations). Is there a command to - restart the kdm window manager (after it died) from a root console prompt? I think you can do this using the kdm command. - stop en start a running kwm window manager from a root console prompt? At last, kill X with Ctrl+Alt+Backspace, then run kdm again. Concerning my initial problem - I remember that I wanted to change the home-dir of both user1 and user2, therefore in console as root did a rmuser, then adduser for both. Can this cause this dying of KDM manager? I don't think so, because kdm works on a higher level where the user settings are not important. But... the more I think about it... it could be possible because KDM remembers users that have been logged in and presents a list of users on the system. Maybe it fails to retrieve the needed data, maybe the user database is corrupted or entries refer to non-existing home directories or login shells? -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KDM stopping
Pieter Donche [EMAIL PROTECTED] writes: FreeBSD-7.0-RELEASE, with KDE as desktop environment and KDM as display manager. I have 2 users, say user1 and user2. Boot, KDM login as user1, OK. Then I do a close session. OK, KDM presents me again with the KDM login screen, login as user2, OK. Then again, close session. Now, the KDM login screen does not come back. I am stuck with a cursor blinking at the upper left corner. Ctrl-Alt-F1 brings me to the console, Ctrl-Alt-F7: no X, just a login:prompt If I reboot and do the same thing, but now first with user2, then user1 - exactly same behaviour (X dies at the second close session). So, it's not connected with user2. Anyone a idea what could be wrong? Below are some log details: Does this happen with xdm as well? Have you checked with the FreeBSD kde mailing list? The /var/log/kdm-log shows: -- ... X.Org X Server 1.4.0 Release Date: 5 September 2007 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 7.0-RELEASE i386 Current Operating System: FreeBSD pclinwi74.cmi.ua.ac.be 7.0-RELEASE FreeBSD 7. 0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008 [EMAIL PROTECTED]:/usr/ obj/usr/src/sys/GENERIC i386 Build Date: 13 February 2008 05:50:12PM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Wed Nov 26 16:27:31 2008 (EE) Unable to locate/open config file New driver is i810 (==) Using default built-in configuration (55 lines) (EE) Failed to load module fbdev (module does not exist, 0) (II) Module ddc already built-in (II) Module ramdac already built-in FreeFontPath: FPE /usr/local/lib/X11/fonts/misc/ refcount is 2, should be 1; fixing. FreeFontPath: FPE /usr/local/lib/X11/fonts/misc/ refcount is 2, should be 1; fixing. (EE) I810(0): V_BIOS address 0x0 out of range Fatal server error: Caught signal 11. Server aborting X.Org X Server 1.4.0 Release Date: 5 September 2007 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 7.0-RELEASE i386 Current Operating System: FreeBSD pclinwi74.cmi.ua.ac.be 7.0-RELEASE FreeBSD 7. 0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008 [EMAIL PROTECTED]:/usr/ obj/usr/src/sys/GENERIC i386 Build Date: 13 February 2008 05:50:12PM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Wed Nov 26 16:43:42 2008 (EE) Unable to locate/open config file New driver is i810 (==) Using default built-in configuration (55 lines) (EE) Failed to load module fbdev (module does not exist, 0) (EE) I810(0): V_BIOS address 0x0 out of range (EE) I810(0): VBE initialization failed. (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found --- /var/log/messages contains: -- .. Nov 26 16:29:03 pclinwi74 kernel: pid 853 (Xorg), uid 0: exited on signal 11 (c ore dumped) Nov 26 16:29:03 pclinwi74 kdm-bin[850]: X server for display :0 terminated unex pectedly Nov 26 16:29:03 pclinwi74 kdm-bin: :0[1137]: IO Error in XOpenDisplay Nov 26 16:29:03 pclinwi74 kdm-bin[850]: Display :0 cannot be opened Nov 26 16:29:03 pclinwi74 kdm-bin[850]: Unable to fire up local display :0; dis abling. Nov 26 16:29:30 pclinwi74 login: ROOT LOGIN (root) ON ttyv0 Nov 26 16:43:40 pclinwi74 shutdown: reboot by root: Nov 26 16:43:42 pclinwi74 kdm-bin[850]: X server for display :0 terminated unex pectedly Nov 26 16:43:42 pclinwi74 kdm-bin[850]: Unable to fire up local display :0; dis abling. Nov 26 16:43:42 pclinwi74 syslogd: exiting on signal 15 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
KDM stopping
FreeBSD-7.0-RELEASE, with KDE as desktop environment and KDM as display manager. I have 2 users, say user1 and user2. Boot, KDM login as user1, OK. Then I do a close session. OK, KDM presents me again with the KDM login screen, login as user2, OK. Then again, close session. Now, the KDM login screen does not come back. I am stuck with a cursor blinking at the upper left corner. Ctrl-Alt-F1 brings me to the console, Ctrl-Alt-F7: no X, just a login:prompt If I reboot and do the same thing, but now first with user2, then user1 - exactly same behaviour (X dies at the second close session). So, it's not connected with user2. Anyone a idea what could be wrong? Below are some log details: The /var/log/kdm-log shows: -- ... X.Org X Server 1.4.0 Release Date: 5 September 2007 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 7.0-RELEASE i386 Current Operating System: FreeBSD pclinwi74.cmi.ua.ac.be 7.0-RELEASE FreeBSD 7. 0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008 [EMAIL PROTECTED]:/usr/ obj/usr/src/sys/GENERIC i386 Build Date: 13 February 2008 05:50:12PM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Wed Nov 26 16:27:31 2008 (EE) Unable to locate/open config file New driver is i810 (==) Using default built-in configuration (55 lines) (EE) Failed to load module fbdev (module does not exist, 0) (II) Module ddc already built-in (II) Module ramdac already built-in FreeFontPath: FPE /usr/local/lib/X11/fonts/misc/ refcount is 2, should be 1; fixing. FreeFontPath: FPE /usr/local/lib/X11/fonts/misc/ refcount is 2, should be 1; fixing. (EE) I810(0): V_BIOS address 0x0 out of range Fatal server error: Caught signal 11. Server aborting X.Org X Server 1.4.0 Release Date: 5 September 2007 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 7.0-RELEASE i386 Current Operating System: FreeBSD pclinwi74.cmi.ua.ac.be 7.0-RELEASE FreeBSD 7. 0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008 [EMAIL PROTECTED]:/usr/ obj/usr/src/sys/GENERIC i386 Build Date: 13 February 2008 05:50:12PM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Wed Nov 26 16:43:42 2008 (EE) Unable to locate/open config file New driver is i810 (==) Using default built-in configuration (55 lines) (EE) Failed to load module fbdev (module does not exist, 0) (EE) I810(0): V_BIOS address 0x0 out of range (EE) I810(0): VBE initialization failed. (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found --- /var/log/messages contains: -- .. Nov 26 16:29:03 pclinwi74 kernel: pid 853 (Xorg), uid 0: exited on signal 11 (c ore dumped) Nov 26 16:29:03 pclinwi74 kdm-bin[850]: X server for display :0 terminated unex pectedly Nov 26 16:29:03 pclinwi74 kdm-bin: :0[1137]: IO Error in XOpenDisplay Nov 26 16:29:03 pclinwi74 kdm-bin[850]: Display :0 cannot be opened Nov 26 16:29:03 pclinwi74 kdm-bin[850]: Unable to fire up local display :0; dis abling. Nov 26 16:29:30 pclinwi74 login: ROOT LOGIN (root) ON ttyv0 Nov 26 16:43:40 pclinwi74 shutdown: reboot by root: Nov 26 16:43:42 pclinwi74 kdm-bin[850]: X server for display :0 terminated unex pectedly Nov 26 16:43:42 pclinwi74 kdm-bin[850]: Unable to fire up local display :0; dis abling. Nov 26 16:43:42 pclinwi74 syslogd: exiting on signal 15 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
non-US keyboard and KDM
I installed KDE and the KDM display manager in FreeBSD. On my portable I have a non-US keyboard (a european country layout), in KDE I can set it to the appropriate keyboard layout. KDM login window is still in US qwerty keyboard, which makes me have to enter my password with different keystrokes :-) How to set an appropriate keyboard in KDM? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: non-US keyboard and KDM
On Tue, 11 Nov 2008 07:47:37 +0100 (CET), Pieter Donche [EMAIL PROTECTED] wrote: I installed KDE and the KDM display manager in FreeBSD. On my portable I have a non-US keyboard (a european country layout), in KDE I can set it to the appropriate keyboard layout. KDM login window is still in US qwerty keyboard, which makes me have to enter my password with different keystrokes :-) How to set an appropriate keyboard in KDM? I don't know, but you can set your keyboard layout generally for X, so you have this layout everywhere (e. g. when you're running something different than KDE, as well as in xdm or kdm). Just change your /etc/X11/xorg.conf to fit your needs, according to this example: Section InputDevice Identifier Keyboard0 Driver kbd Option XkbModel pc105 Option XkbLayout de Option AutoRepeat250 30 EndSection -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Still, no-joy with kdm......
Gary Kline wrote: Im looking at the kdmrc file but don't see anything wrong. Any ideas where to llook next? Hello, i had recently a problem with kdm myself. Running kdm-bin under ktrace i discovered it was a locking problem. Something changed about locks in FreeBSD-Stable, and this killed some programs (tin, mutt, kdm, etc.) who do locking. I recompiled tin,mutt, etc. but i did not want to recompile kdebase, so i took a kdebase package from FreBSD-7.0-RELEASE and extracted the kdm-bin out of here. It works on my FreeBSD-STABLE box without problem. -- Michel TALON ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Still, no-joy with kdm......
--On Monday, August 18, 2008 16:43:23 -0700 Gary Kline [EMAIL PROTECTED] wrote: Guys, Im looking at the kdmrc file but don't see anything wrong. Any ideas where to llook next? I use kde every day, and I don't have a kdmrc file. You can start kde several ways. One way is to login as root and type kdm at the prompt. Another is to edit /etc/ttys the way the Handbook describes. (You can read that yourself.) Another way is to use an xinitrc file. (That's in the Handbook as well.) The reason kdm can't create its pid file is most likely because you're trying to start it under your account instead of root. gary PS: what is the startup for exec'ing gnome?? echo 'gnome_enable=YES' /etc/rc.conf That's in the Handbook as well. -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** Check the headers before clicking on Reply. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Still, no-joy with kdm......
On Tue, Aug 19, 2008 at 02:26:10AM +0200, Martin Tournoij wrote: On Mon, Aug 18, 2008 at 04:43:23PM -0700, Gary Kline wrote: Guys, Im looking at the kdmrc file but don't see anything wrong. Any ideas where to llook next? gary PS: what is the startup for exec'ing gnome?? I can't see anything wrong with your kdmrc file either ... In fact, I can't see your kdmrc file at all ... You should really post more information, at the very least: o What exactly you are trying to accomplish. o Your kdmrc file. o What exactly isn't working. o The error message, if any (full, copied exactly). Well, I managed to capture the [f]printf'd message. This was clearly to stdout, not stderr: Updating KDM configuration Information: reading current kdmrc /usr/local/share/config/kdm/kdmrc (from kde = 2.2.x) Information: current kdmrc is from kde = 3.1 (config version 2.3) This is with no /var/run/kdm.pid; if that file of zero-length inode entry is present, kdm yelps. Either way, nothing happens. No entry into the KDE environment. gary -- Gary Kline [EMAIL PROTECTED] http://www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Still, no-joy with kdm......
On Tue, Aug 19, 2008 at 11:41:08AM -0500, Paul Schmehl wrote: --On Monday, August 18, 2008 16:43:23 -0700 Gary Kline [EMAIL PROTECTED] wrote: Guys, Im looking at the kdmrc file but don't see anything wrong. Any ideas where to llook next? I use kde every day, and I don't have a kdmrc file. If you installed KDE, you have it. In kde3 it's at /usr/local/share/config/kdm/kdmrc You can start kde several ways. One way is to login as root and type kdm at the prompt. Another is to edit /etc/ttys the way the Handbook describes. (You can read that yourself.) Another way is to use an xinitrc file. (That's in the Handbook as well.) I haven't edited /etc/ttys yet; I may. But I think something got broken [mis-CLEANED by fsck or otherwise damanaged during the weekend power-out]. It may be easier to completely remove v3 and re-install kde4. The reason kdm can't create its pid file is most likely because you're trying to start it under your account instead of root. I'm pretty sure I was in ./root or slash when I logged in. I'm using KDE now, sort-of, by virture of startx. Still, lots of misc things were not initialized. gary gary gary PS: what is the startup for exec'ing gnome?? echo 'gnome_enable=YES' /etc/rc.conf That's in the Handbook as well. -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** Check the headers before clicking on Reply. -- Gary Kline [EMAIL PROTECTED] http://www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Still, no-joy with kdm......
On Tue, 19 Aug 2008 11:25:42 -0700, Gary Kline [EMAIL PROTECTED] wrote: I haven't edited /etc/ttys yet; I may. But I think something got broken [mis-CLEANED by fsck or otherwise damanaged during the weekend power-out]. When I had my big problem... haha... some structures in /, some in /var and the whole /usr/X11R6 disappeared. Well, that doesn't matter to me because all this stuff can easily be reinstalled (which would be a good advice to do when you think that parts of the system may be missing, just to be sure). It may be easier to completely remove v3 and re-install kde4. Yes, this should leave the system in a default state where KDE4 should run fine without complaining about stuff from version 3. I'm pretty sure I was in ./root or slash when I logged in. Display managers (xdm, gdm, kdm, wdm), when run manually, have to be run as user root: Login: root # xdm # exit X sessions started via the xinitrc command and a proper ~/.xinitrc file should not be run as root, but from a regular user account: Login: bob % startx To run a display manager automatically, /etc/ttys needs to contain the correct line: # name getty typestatus comments ttyv8 /usr/local/bin/xdm -nodaemon xterm on secure For gdm, kdm and wdm, use /usr/local/bin/[gkw]dm respectively. Finally, there's an easy way to automatically login a user (ATTENTION, SECURITY RISK!) and start an X session for him. Therefore, /etc/gettytab needs a little modification: default:\ ... autologin:\ :al=username:tc=Pc: a|std.110|110-baud:\ ... As well, the user's ~/.login file needs to start X; last line: [ -f /tmp/.X0-lock ] startx For this solution, xdm may not be loaded via /etc/ttys - only one instance of X will run (except you put some extra stuff there). But please, keep in mind that this procedure enables anyone with physical access to the machine can click around stupidly and mess up things. -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Still, no-joy with kdm......
Guys, Im looking at the kdmrc file but don't see anything wrong. Any ideas where to llook next? gary PS: what is the startup for exec'ing gnome?? -- Gary Kline [EMAIL PROTECTED] http://www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Still, no-joy with kdm......
On Mon, Aug 18, 2008 at 04:43:23PM -0700, Gary Kline wrote: Guys, Im looking at the kdmrc file but don't see anything wrong. Any ideas where to llook next? gary PS: what is the startup for exec'ing gnome?? I can't see anything wrong with your kdmrc file either ... In fact, I can't see your kdmrc file at all ... You should really post more information, at the very least: o What exactly you are trying to accomplish. o Your kdmrc file. o What exactly isn't working. o The error message, if any (full, copied exactly). o What you have already tried to solve the problem. o The version of software (FreeBSD, KDM, KDE, etc.). -- Martin Tournoij [EMAIL PROTECTED] http://www.daemonforums.org QOTD: The jig's up, Elman. Which jig? -- Jeff Elman ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Still, no-joy with kdm......
On Mon, 18 Aug 2008 16:43:23 -0700, Gary Kline [EMAIL PROTECTED] wrote: Guys, Im looking at the kdmrc file but don't see anything wrong. I'd like to look at your kdmrc file, too. Any ideas where to llook next? Except /etc/ttys, /etc/X11/xorg.conf and kdm's rc file? Hnmmm... can't imagine something else at the moment. PS: what is the startup for exec'ing gnome?? The display manager for Gnome is gdm (used similar to kdm), the Gnome session is started via exec gnome-session, if I remember correctly. I'm not a Gnome user (as I am not a KDE user), so forgive me my answers of guessing. And I don't have one of them installed so I can't check. They wouldn't run on my system anyway. -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Still, no-joy with kdm......
On Mon August 18 2008 17:26:10 Martin Tournoij wrote: On Mon, Aug 18, 2008 at 04:43:23PM -0700, Gary Kline wrote: Guys, Im looking at the kdmrc file but don't see anything wrong. Any ideas where to llook next? gary PS: what is the startup for exec'ing gnome?? I can't see anything wrong with your kdmrc file either ... In fact, I can't see your kdmrc file at all ... p0 17:59 tao [5030] locate kdmrc /usr/local/share/con fig/kdm/kdmrc which is a general collection of miscellaneous X* that have been clumped together in the /usr/local/share/con fig/kdm directory. This file is mentioned each time I try to exec kdm [as root]. This has been an ongoing discussion in recent days since the typical results state that kdm cannot create kdm.pid in /var/run. The only work-around is to logging as root from consonsole, then su kline, then type % startup. After several moments my usual KDM is all there. You should really post more information, at the very least: o What exactly you are trying to accomplish. o Your kdmrc file. Everyone who had kde3 had this file; it is very long; posting it would burn more than 20K of bandwidth per listmember. It is 0644, and text, so putting in trace is a no-go. o What exactly isn't working. Well, according to the kdm binary, I can't create /var/run/kdm.pid. But since a zer-length file is created, I think the problem is earlier. It may be, e.g., that the binary cannot be completed. o The error message, if any (full, copied exactly). I don't know exactly how much good that would do, assuming that I *could* do a ``# kdm 21/tmp/message. o What you have already tried to solve the problem. Massively removed every socket from ~/. and /tmp/. , plus, of course rm'ing the zer-len kdm.pid file. o The version of software (FreeBSD, KDM, KDE, etc.). 7.0 rev 3, upgraded in March. I did a complete ports upgrade this morning; then a reboot. Nada. kdm still can write is pid into kdm.pid. -g -- Gary Kline [EMAIL PROTECTED] www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
small kdm fonts at login promt
After installing FreeBSD 7.0 Release i found the kdm login promt to be tiny, so much so i cant actually make out the text at all. I have since been in kcontrol as su and put the font sizes all the why upto 48, this has only made a marginal difference ( i can now only just make out what the promt says ) but cant think what else to change to bring the prompt back to a normal size? anyone seen this or have any ideas to sort it LtCdData http://www.davids-website.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
small kdm fonts at login promt
Hi... After installing FreeBSD 7.0 Release i found the kdm login promt to be tiny, so much so i cant actually make out the text at all. I have since been in kcontrol as su and put the font sizes all the why upto 48, this has only made a marginal difference ( i can now only just make out what the promt says ) but cant think what else to change to bring the prompt back to a normal size? anyone seen this or have any ideas to sort it LtCdData http://www.davids-website.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
KDE won't allow me to logout and restart kdm after upgrade to xorg 7.3
Hi, About two months ago (yes, I'm only now getting around to fixing this), I decided it was time to upgrade my Xorg install from 6.9 to the current. I followed the instructions in /usr/ports/UPDATING from 20070519. After the upgrade, everything was going ok, until I logged out of KDE. I ended the session and was redirected to ttyv0. The following was on the system console: Jan 18 20:22:36 sniper kdm-bin[788]: X server for display :0 terminated unexpectedly Jan 18 20:22:36 sniper kdm-bin: :0[948]: IO Error in XOpenDisplay Jan 18 20:22:36 sniper kdm-bin[788]: Display :0 cannot be opened Jan 18 20:22:36 sniper kdm-bin[788]: Unable to fire up local display :0; disabling. I then went to another console and, as root, did: sniper# sockstat | grep x root kdm-bin788 9 stream /var/run/xdmctl/dmctl/socket Which cleared out whatever was wrong and restarted kdm-bin and allowed me to start another session. What exactly is going on here? The reason it isn't too big a deal, and took me until now to mention it is because I'm about the only person who uses FreeBSD here at home and so when I logout, it's usually to shut off the computer. Any thoughts on how to fix this? Andy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
kdm/startkde problem after upgrade
Hi everyone! $ uname -a FreeBSD ABC.DEF.com 6.2-STABLE FreeBSD 6.2-STABLE #0: Wed Jul 11 06:07:39 PDT 2007 root@:/usr/obj/usr/src/sys/AMD64 amd64 kdm is configured as a login manager in /etc/ttys. After upgrade to KDE 3.5.7 and X server 7.2 (that was time consuming, but no errors) I receive an error message on startup: Jul 16 00:13:10 FreeBSD-amd64 kdm-bin[792]: X server /usr/X11R6/bin/X cannot be executed Jul 16 00:13:10 FreeBSD-amd64 kdm-bin[789]: X server for display :0 can't be started, session disabled When I logged in, startkde brings another error message: xsetroot: unable to open display '' Warning: kbuildsycoca is unable to register with DCOP. kbuildsycoca running... kdeinit: Aborting. $DISPLAY is not set. There was an error setting up inter-process communications for KDE. The message returned by the system was: Could not read network connection list. /home/andrey/.DCOPserver_FreeBSD-amd64.kde.com_NODISPLAY Please check that the dcopserver program is running! Reusing existing ksycoca kbuildsycoca: WARNING: '/usr/local/share/applications/kde/ark.desktop' specifies undefined mimetype/servicetype 'application/x-tbz2' ... A lot of messages of the same nature about undefined mimetype/servicetype. ... xset: unable to open display xset: unable to open display xsetroot: unable to open display '' startkde: Starting up... ksplash: cannot connect to X server xprop: unable to open display '' kdeinit: Aborting. $DISPLAY is not set. Warning: connect() failed: : No such file or directory ksmserver: cannot connect to X server ERROR: Couldn't attach to DCOP server! startkde: Shutting down... Warning: connect() failed: : No such file or directory Error: Can't contact kdeinit! startkde: Running shutdown scripts... Interesting, when I issue startx, KDE is up and running. I ran X -configure, and then X -config /root/xorg.conf.new as root; X server starts properly, so I copied new config to /etc/X11. I assume my problem is KDE related. Errors are about DCOP server, as I can see. Could anyone help me fix this problem? Thank you in advance! Andriy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kdm/startkde problem after upgrade
Written by Andriy Babiy on 07/16/07 02:52 Hi everyone! $ uname -a FreeBSD ABC.DEF.com 6.2-STABLE FreeBSD 6.2-STABLE #0: Wed Jul 11 06:07:39 PDT 2007 root@:/usr/obj/usr/src/sys/AMD64 amd64 kdm is configured as a login manager in /etc/ttys. After upgrade to KDE 3.5.7 and X server 7.2 (that was time consuming, but no errors) I receive an error message on startup: Jul 16 00:13:10 FreeBSD-amd64 kdm-bin[792]: X server /usr/X11R6/bin/X cannot be executed Jul 16 00:13:10 FreeBSD-amd64 kdm-bin[789]: X server for display :0 can't be started, session disabled When I logged in, startkde brings another error message: xsetroot: unable to open display '' Warning: kbuildsycoca is unable to register with DCOP. kbuildsycoca running... kdeinit: Aborting. $DISPLAY is not set. There was an error setting up inter-process communications for KDE. The message returned by the system was: Could not read network connection list. /home/andrey/.DCOPserver_FreeBSD-amd64.kde.com_NODISPLAY Please check that the dcopserver program is running! Reusing existing ksycoca kbuildsycoca: WARNING: '/usr/local/share/applications/kde/ark.desktop' specifies undefined mimetype/servicetype 'application/x-tbz2' ... A lot of messages of the same nature about undefined mimetype/servicetype. ... xset: unable to open display xset: unable to open display xsetroot: unable to open display '' startkde: Starting up... ksplash: cannot connect to X server xprop: unable to open display '' kdeinit: Aborting. $DISPLAY is not set. Warning: connect() failed: : No such file or directory ksmserver: cannot connect to X server ERROR: Couldn't attach to DCOP server! startkde: Shutting down... Warning: connect() failed: : No such file or directory Error: Can't contact kdeinit! startkde: Running shutdown scripts... Interesting, when I issue startx, KDE is up and running. I ran X -configure, and then X -config /root/xorg.conf.new as root; X server starts properly, so I copied new config to /etc/X11. I assume my problem is KDE related. Errors are about DCOP server, as I can see. Could anyone help me fix this problem? Thank you in advance! Andriy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] # ls -lF /usr/X11R6 lrwxr-xr-x 1 root wheel 10 Jun 18 08:29 /usr/X11R6@ - /usr/local If yours does not look like that, then you forgot to merge /usr/X11R6 into /usr/local, which by the looks of the first message (Jul 16 00:13:10 FreeBSD-amd64 kdm-bin[792]: X server /usr/X11R6/bin/X cannot be executed) is exactly what has happened. As of Xorg 7, X11BASE is now /usr/local rather than /usr/X11R6, so the Xorg servers will not be at /usr/X11R6/bin. Read the Xorg 7.2 entry in /usr/ports/UPDATING. Specifically, there is a tool (mergebase.sh) included to make the merge step extremely easy. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kdm/startkde problem after upgrade
$ uname -a FreeBSD ABC.DEF.com 6.2-STABLE FreeBSD 6.2-STABLE #0: Wed Jul 11 06:07:39 PDT 2007 root@:/usr/obj/usr/src/sys/AMD64 amd64 kdm is configured as a login manager in /etc/ttys. After upgrade to KDE 3.5.7 and X server 7.2 (that was time consuming, but no errors) I receive an error message on startup: Jul 16 00:13:10 FreeBSD-amd64 kdm-bin[792]: X server /usr/X11R6/bin/X cannot be executed Jul 16 00:13:10 FreeBSD-amd64 kdm-bin[789]: X server for display :0 can't be started, session disabled When I logged in, startkde brings another error message: xsetroot: unable to open display '' Warning: kbuildsycoca is unable to register with DCOP. kbuildsycoca running... kdeinit: Aborting. $DISPLAY is not set. There was an error setting up inter-process communications for KDE. The message returned by the system was: Could not read network connection list. /home/andrey/.DCOPserver_FreeBSD-amd64.kde.com_NODISPLAY Please check that the dcopserver program is running! Reusing existing ksycoca kbuildsycoca: WARNING: '/usr/local/share/applications/kde/ark.desktop' specifies undefined mimetype/servicetype 'application/x-tbz2' ... A lot of messages of the same nature about undefined mimetype/servicetype. ... xset: unable to open display xset: unable to open display xsetroot: unable to open display '' startkde: Starting up... ksplash: cannot connect to X server xprop: unable to open display '' kdeinit: Aborting. $DISPLAY is not set. Warning: connect() failed: : No such file or directory ksmserver: cannot connect to X server ERROR: Couldn't attach to DCOP server! startkde: Shutting down... Warning: connect() failed: : No such file or directory Error: Can't contact kdeinit! startkde: Running shutdown scripts... Interesting, when I issue startx, KDE is up and running. I ran X -configure, and then X -config /root/xorg.conf.new as root; X server starts properly, so I copied new config to /etc/X11. I assume my problem is KDE related. Errors are about DCOP server, as I can see. Could anyone help me fix this problem? Thank you in advance! # ls -lF /usr/X11R6 lrwxr-xr-x 1 root wheel 10 Jun 18 08:29 /usr/X11R6@ - /usr/local If yours does not look like that, then you forgot to merge /usr/X11R6 into /usr/local, which by the looks of the first message (Jul 16 00:13:10 FreeBSD-amd64 kdm-bin[792]: X server /usr/X11R6/bin/X cannot be executed) is exactly what has happened. As of Xorg 7, X11BASE is now /usr/local rather than /usr/X11R6, so the Xorg servers will not be at /usr/X11R6/bin. Read the Xorg 7.2 entry in /usr/ports/UPDATING. Specifically, there is a tool (mergebase.sh) included to make the merge step extremely easy. Yes. Sure. Thank you. Perhaps I was too sleepy. My fault. Everything is OK. Andriy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
KDM terminates unexpectedly
I've just installed freeBSD v6.2 and installed the updated xorg from sources. After kdm is called I see: Jul 9 17:41:29 rock kdm-bin[817]: X server for display :0 terminated unexpectedly Jul 9 17:41:29 rock kdm-bin: :0[821]: IO Error in XOpenDisplay Jul 9 17:41:29 rock kdm-bin[817]: Unable to fire up local display :0; disabling Any advice? malcolm ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KDM terminates unexpectedly
On Tue, 10 Jul 2007 13:07:04 +1000
Malcolm Fitzgerald [EMAIL PROTECTED] wrote:
I've just installed freeBSD v6.2 and installed the updated xorg from
sources.
After kdm is called I see:
Jul 9 17:41:29 rock kdm-bin[817]: X server for display :0 terminated
unexpectedly
Jul 9 17:41:29 rock kdm-bin: :0[821]: IO Error in XOpenDisplay
Jul 9 17:41:29 rock kdm-bin[817]: Unable to fire up local display :0;
disabling
Any advice?
any information @ the end of /var/log/Xorg.0.log ?
_
{Beto|Norberto|Numard} Meijome
Quality is never an accident, it is always the result of intelligent effort.
John Ruskin (1819-1900)
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KDM at boot
Tim Daneliuk ha scritto: Eric Crist wrote: On Jun 25, 2007, at 7:39 PMJun 25, 2007, Cyrus wrote: ive done this before with Slackware 11, but read up on freebsd on how to do it, and its completley different. How do I go about having KDM start automaticly on boot? Edit /etc/ttys and modify line 45 as follows: ttyv8 /usr/local/bin/kdm xterm on secure Save the file, reboot. Of course, you need to have KDE installed. Shouldn't have to reboot. 'kill -HUP 1' should do it. If not, 'shutdown now', hit return, followed by ^D will do it ... This is even easier to remember: # init q It's the same for 'kill -HUP 1' ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KDM at boot
On Tue, 26 Jun 2007 22:44:25 +0200
Sereno Ternullo [EMAIL PROTECTED] wrote:
This is even easier to remember:
# init q
It's the same for 'kill -HUP 1'
well...not really.
init q is specific to init.
kill -HUP {pid}
is the standard unix way to tell {pid} to reload its configuration file. Most
apps handle the HUP signal specifically.
_
{Beto|Norberto|Numard} Meijome
He has Van Gogh's ear for music.
Billy Wilder
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
KDM at boot
ive done this before with Slackware 11, but read up on freebsd on how to do it, and its completley different. How do I go about having KDM start automaticly on boot? Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KDM at boot
On Jun 25, 2007, at 7:39 PMJun 25, 2007, Cyrus wrote: ive done this before with Slackware 11, but read up on freebsd on how to do it, and its completley different. How do I go about having KDM start automaticly on boot? Edit /etc/ttys and modify line 45 as follows: ttyv8 /usr/local/bin/kdm xterm on secure Save the file, reboot. Of course, you need to have KDE installed. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KDM at boot
Eric Crist wrote: On Jun 25, 2007, at 7:39 PMJun 25, 2007, Cyrus wrote: ive done this before with Slackware 11, but read up on freebsd on how to do it, and its completley different. How do I go about having KDM start automaticly on boot? Edit /etc/ttys and modify line 45 as follows: ttyv8 /usr/local/bin/kdm xterm on secure Save the file, reboot. Of course, you need to have KDE installed. Shouldn't have to reboot. 'kill -HUP 1' should do it. If not, 'shutdown now', hit return, followed by ^D will do it ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD X11/GNOME/KDM issue
Christian Walther wrote: On 30/03/07, Joseph Marah [EMAIL PROTECTED] wrote: Hi KK, thanks. I have tried ctrl+ald+bspace but got a black screen for a split sec abd got right back to KDM login. ALT+CTRL+Backspace shuts down the X Server the hard way. A Desktop Manager (KDM, GDM, XDM) is supposed to restart after a session is ended, which means that the login screen comes back... Also tried ctrl+f1, ctrl+f1 etc but go nowhere. Yepp, but if you try ALT+CTRL+Fx (where 1 = x = 8) you'll get a console login screen. Here you'll be able to login as root. Joseph, I'm sorry; as you can see, Christian caught my error; CTL-*ALT*-F1, etc., is correct. KDK -- Nuke them till they glow, then shoot them in the dark. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD X11/GNOME/KDM issue
Thanks everyone for your help. I will let you know of my next confusion. Kevin Kinsey [EMAIL PROTECTED] wrote: Christian Walther wrote: On 30/03/07, Joseph Marah wrote: Hi KK, thanks. I have tried ctrl+ald+bspace but got a black screen for a split sec abd got right back to KDM login. ALT+CTRL+Backspace shuts down the X Server the hard way. A Desktop Manager (KDM, GDM, XDM) is supposed to restart after a session is ended, which means that the login screen comes back... Also tried ctrl+f1, ctrl+f1 etc but go nowhere. Yepp, but if you try ALT+CTRL+Fx (where 1 = x = 8) you'll get a console login screen. Here you'll be able to login as root. Joseph, I'm sorry; as you can see, Christian caught my error; CTL-*ALT*-F1, etc., is correct. KDK -- Nuke them till they glow, then shoot them in the dark. Regards Joseph Marah ** IF YOU THINK YOU HAVE EVERYTHING UNDER CONTROL YOU ARE NOT GOING FAST ENOUGH - Mario Andretti, race car driver. ** ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD X11/GNOME/KDM issue
Hi Andriy, I finally got in. At first I tried single user mode but had no editing permissions. Then I noticed that I had only thr root slice mounted. So I found out how to mount the rest of the file system(mount -a) and did that. Then I used the logon command to logon as root. Then I made the necessary changes. Thanks for your suggestion, I will sure try it. Andriy Babiy [EMAIL PROTECTED] wrote: Hi KK, thanks. I have tried ctrl+ald+bspace but got a black screen for a split sec abd got right back to KDM login. Also tried ctrl+f1, ctrl+f1 etc but go nowhere. I can get in single user mode but no edit previleges as I am not root. still trying different things. hanks tho. Hi. You may want to try sysinstall - Fixit, then fix the problem in the shell. Andriy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD X11/GNOME/KDM issue
Hi KK, thanks. I have tried ctrl+ald+bspace but got a black screen for a split sec abd got right back to KDM login. Also tried ctrl+f1, ctrl+f1 etc but go nowhere. I can get in single user mode but no edit previleges as I am not root. still trying different things. hanks tho. Kevin Kinsey [EMAIL PROTECTED] wrote: Joseph Marah wrote: [Snip description of issue, basically KDM/GDM conflicting config or similar.] To cut matters short, I have been locked out of my system. how can I get back in? Any help will be appreciated. Thanks. Hi, Joseph! I wrapped the text of your last paragraph, because you had only placed newlines at the end of each paragraph. It's helpful to place a newline every 72 characters or so. In short, I've not got an answer for KDM, but you should be able to drop to the console with CTL-ALT-BKSP --- and, if that doesn't work, you should be able to access a virtual console with CTL-F1, CTL-F2, etc. Edit the offending file (rc.conf?, /etc/ttys?) and try kill -HUP `pgrep Xorg`. And, if you can't get a virtual console, you'll want to reboot into single-user mode, I guess. HTH, Kevin Kinsey -- 1 + 1 = 3, for large values of 1. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD X11/GNOME/KDM issue
On 30/03/07, Joseph Marah [EMAIL PROTECTED] wrote: Hi KK, thanks. I have tried ctrl+ald+bspace but got a black screen for a split sec abd got right back to KDM login. ALT+CTRL+Backspace shuts down the X Server the hard way. A Desktop Manager (KDM, GDM, XDM) is supposed to restart after a session is ended, which means that the login screen comes back... Also tried ctrl+f1, ctrl+f1 etc but go nowhere. Yepp, but if you try ALT+CTRL+Fx (where 1 = x = 8) you'll get a console login screen. Here you'll be able to login as root. I can get in single user mode but no edit previleges as I am not root. still trying different things. hanks tho. Nope, you're root if you boot into single user mode. But / is mounted readonly, only. If you boot into single user mode the savest thing to do is: fsck -p mount / -o rw mount -a fsck will first check your file systems so that you don't operate on a dirty FS, e.g. after a crash. If you rebooted into Single User mode and there was no crash before, you can skip this step. mount / -o rw remounts the root filesystem read/writable. mount -a mounts every fs listed in /etc/fstab (that doesn't has noauto set as an option). Make sure you'll do a umount -a mount / -o ro before you reboot, otherwise your file systems will be fscked. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD X11/GNOME/KDM issue
Hi KK, thanks. I have tried ctrl+ald+bspace but got a black screen for a split sec abd got right back to KDM login. Also tried ctrl+f1, ctrl+f1 etc but go nowhere. I can get in single user mode but no edit previleges as I am not root. still trying different things. hanks tho. Hi. You may want to try sysinstall - Fixit, then fix the problem in the shell. Andriy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD X11/GNOME/KDM issue
I am new to FreeBSD and been out of touch with UNIX for a while. I just bought a new system i386 (Intel 3.0 Ghz CPU, 2.0G mem, 500G disk space etc). I think I successfully downloaded the install files and burnt my cds. I think I installed the system OK. I think I installed X11 from ports. I then installed GNOME from ports( Maaan it took so long). I entered into /etc/rc.conf gdm_enable = YES ... shut down and loggen in through GDM successfully. Played with it for a while. All utilities showed up fine. I browsed the Internet too. Then I decided to try KDE and installed it from ports (took lng). After install I looged in through GDM. I saw everything KDE brought with it using GNOME interface and read the KDE mannual a bit. Then I used the user administration tab and added myself as a user in addition to root. I also changed kde_enable = YES in /etc/rc.conf in place of gdm_enable = YES hoping to be able to log back in using KDM. I shutdown and restarted. I got the KDM logon interface but the introduction showed my username I last added, as my default login. I entered root as user but a message came saying root logons are not allowed. I tried logging in as myself and entered my correct password but I was sent to a window which read : Could not start kstartupconfig. Check your installation. I clicked OKAY. This took me back to the KDM logon manager. To cut matters short, I have been locked out of my system. how can I get back in? Any help will be appreciated. Thanks. Regards Joseph Marah ** IF YOU THINK YOU HAVE EVERYTHING UNDER CONTROL YOU ARE NOT GOING FAST ENOUGH - Mario Andretti, race car driver. ** ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD X11/GNOME/KDM issue
Joseph Marah wrote: [Snip description of issue, basically KDM/GDM conflicting config or similar.] To cut matters short, I have been locked out of my system. how can I get back in? Any help will be appreciated. Thanks. Hi, Joseph! I wrapped the text of your last paragraph, because you had only placed newlines at the end of each paragraph. It's helpful to place a newline every 72 characters or so. In short, I've not got an answer for KDM, but you should be able to drop to the console with CTL-ALT-BKSP --- and, if that doesn't work, you should be able to access a virtual console with CTL-F1, CTL-F2, etc. Edit the offending file (rc.conf?, /etc/ttys?) and try kill -HUP `pgrep Xorg`. And, if you can't get a virtual console, you'll want to reboot into single-user mode, I guess. HTH, Kevin Kinsey -- 1 + 1 = 3, for large values of 1. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD X11/GNOME/KDM issue
On Thu, 29 Mar 2007 12:51:16 -0700 (PDT) Joseph Marah [EMAIL PROTECTED] wrote: After install I looged in through GDM. I saw everything KDE brought with it using GNOME interface and read the KDE mannual a bit. Then I used the user administration tab and added myself as a user in addition to root. I also changed kde_enable = YES in /etc/rc.conf in place of gdm_enable = YES hoping to be able to log back in using KDM. AFAIK KDE doesn't install a local rc.d script for KDM, so I'm curious as to how you did that. The FreeBSD hand book has a section on starting KDM ,and also on starting KDE without a login manager, via startx. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problem with kdm
Hi I have a little problem with kdm. When I try to sign on the screen reverts back to the login dialog after a few seconds. I can use xdm without any problems. The problem started when I switched my soundcard from an external soundblaster to the onboard Intel. I'm using the Intel HDA driver and it works! The KDE sound does not work but mplayer for example has sound. I've recompiled KDE but there's no change. I need suggestions on how to analyze this problem and to get kdm to work again. Thanks Leslie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with kdm
On 12/03/07, Leslie Jensen [EMAIL PROTECTED] wrote: Hi I have a little problem with kdm. When I try to sign on the screen reverts back to the login dialog after a few seconds. I can use xdm without any problems. The problem started when I switched my soundcard from an external soundblaster to the onboard Intel. I'm using the Intel HDA driver and it works! The KDE sound does not work but mplayer for example has sound. I don't think that these two are actually related. The Display Manager hasn't anything to do with the sound card, at least not after you entered username and password. So my guess is that you broke your KDM configuration somehow. The situation you describe usually means that the session you're trying to execute is invalid. This can have a variety of reasons. I can't help you here because I don't know what session you're trying to execute. Are you using KDE or Gnome, or do you have a ~/.xsession defined? If the latter is the case I doubt that kdm did work for you, because AFAIK KDM doesn't support Xsession. First check what session is execute upon login. There is a Session menu somewhere on the kdm login screen. Choose a session that you know does exist. I've recompiled KDE but there's no change. I need suggestions on how to analyze this problem and to get kdm to work again. HTH Christian Thanks Leslie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Hard disk problem? kdm bug? What is going on here...
The last two days I've had freezes when booting up my old 6-STABLE/i386 desktop. It gets as far as kdm (3.5.2) which then freezes. When I reboot into single user mode and after I've fscked the disk (or apparently something that sounds very similar) I can't start bash: # bash /libexec/ld-elf.so.1: Shared object libintl.so.6 not found, required by bash However, the file exists and gettext, which also depends on the library, still runs! Forcing a recompile of gettext fixes bash. However, I only noticed this as a side effect of kdm hanging (simply because the first thing I do when I want to work in SU mode is mount -a bash). First time it happened I recompiled bash and kdm started; this morning I tried it and kdm hung again. I rebooted and sure enough bash was complaining about libintl.so.6, so this time I disabled kdm, recompiled gettext and did a startx after booting into multi-user mode. Works fine. fsck is reporting no errors on /usr/local (dev/ad0s1e) I'm stumped - I can't work out what the connection is between the symptoms. Any ideas anyone? Thanks Ashley ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
kdm restart and back into root shell from KDE
Hi all, I got two KDE-related newby questions: 1. How do I restart a KDE session after I changed some config files? In Linux this is /etc/init.d/kdm restart But since there is no init.d on FreeBSD, I'm stuck. 2. Is there any way I can shutdown KDE and get back to a root shell? If I choose 'log out' from KDE, I am still in the KDE environment and fixed to choose another user to login again. If I choose 'shutdown KDE', it issues a shutdown command to shutdown my PC, and that's also not what I want. I just want to shutdown KDE and get back into a root shell. Think it's an easy thing to configure, but where? btw, I'm running KDE 3.5.1 on FreeBSD 6.0. any help would be appreciated, %Bram ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kdm restart and back into root shell from KDE
--On April 15, 2006 12:58:02 PM +0200 Bram Kuijper [EMAIL PROTECTED]
wrote:
Hi all,
I got two KDE-related newby questions:
1. How do I restart a KDE session after I changed some config files? In
Linux this is
/etc/init.d/kdm restart
But since there is no init.d on FreeBSD, I'm stuck.
Ctrl-Alt-Backspace restarts X and kdm. I haven't tried it, but I suppose
you could run /usr/local/bin/startkde and see what happens. Or you could
issue a command like this kill -HUP `cat /var/run/kdm.pid`.
2. Is there any way I can shutdown KDE and get back to a root shell? If I
choose 'log out' from KDE, I am still in the KDE environment and fixed to
choose another user to login again.
If all you need is a root shell, Ctrl-Alt-F1-F7 will get you all the root
shells you'd ever need.
If you mean you want to kill the Xserver and not have it restart, kill
-TERM `ps -auxw | grep X11R6/bin/X | grep -v grep | awk '{print $2}'`
should do the trick.
If I choose 'shutdown KDE', it issues a shutdown command to shutdown my
PC, and that's also not what I want. I just want to shutdown KDE and get
back into a root shell. Think it's an easy thing to configure, but where?
btw, I'm running KDE 3.5.1 on FreeBSD 6.0.
So am I.
Paul Schmehl ([EMAIL PROTECTED])
Adjunct Information Security Officer
University of Texas at Dallas
AVIEN Founding Member
http://www.utdallas.edu/
Re: kdm and fluxbox
- Original Message - From: Norberto Meijome [EMAIL PROTECTED] To: RYAN M. vAN GINNEKEN [EMAIL PROTECTED] Cc: Norberto Meijome [EMAIL PROTECTED], freebsd-questions@freebsd.org Sent: Sun Feb 19 19:12:03 2006 Subject: Re: kdm and fluxbox RYAN M. vAN GINNEKEN wrote: Thanks to all and i will take your advice Norberto as i do not really like kde that much anyway. If i wanted window i would just install windowsxp or maybe vista would be more like Kde any how i digress. I am tiring to set up wdm and added this line to my /etc/ttys ttyv8 /usr/X11R6/bin/wdm -nodaemon xterm on secure followed the instructions below found on the fulxbox site but it does not quite work http://fluxbox-wiki.org/index.php/Howto_add_fluxbox_to_wdm I get the wdm ok beasty is there, very cool backgound i might add, seen it used in a theme somewhere. No matter what i pick for a windows manager i get the stock Freebsd one wmaker i think? u know the one with the terminal and green menu bars very vanilla. green menu bars = twm wmaker = much better, check it out @ http://www.windowmaker.org An exception to this kde still works and failsafe gives me control of the terminal window bottom right. Also i removed a bunch of managers out of the wdm-config file as i was not using them like this. DisplayManager*wdmWm: wmaker:enlightenment:gnome:kde:fluxbox I still get failsafe and wmaker where do us suppose these come from. Kde still works but not enlightenment gnome or flux box After editing the wdm-config, you need to restart wdm. Ctrl-Alt-Backspace will kill the X server and re-read all the configs. I did that can you please post your wdm-config and a list of your package installed ? (or make them available online) I have tried to attached them but my mail server is giving me grief with attachment right now. the relevant section in my config: --- ! It will run .xsession !DisplayManager*wdmWm: None --- which means it will read .xsession in my home. my .xsession is : $ cat ~/.xsession ## RUNNING bbkeys from Blackbox because it feels more powerful ## to avoid conflicts with fluxbox's key mgr, I emptied .fluxbox/keys bbkeys xscreensaver -no-splash fbpager -w #wmwifi sleep 1 gkrellm -w #fbdesk torsmo tilda skype gaim fluxbox --- though I realise that I should be simply running startfluxbox and adding all the other cmds to ~/.fluxbox/startup I do not have an .xsession file in my home dir in fact i do not seem to have an .xsession or an xsession file anywhere on my system just Xsession see below [EMAIL PROTECTED] find / -name xsession [EMAIL PROTECTED] find / -name .xsession [EMAIL PROTECTED] find / -name .Xsession [EMAIL PROTECTED] find / -name Xsession /usr/local/share/config/kdm/Xsession /usr/X11R6/etc/gdm/Xsession /usr/X11R6/lib/X11/xdm/Xsession /usr/X11R6/lib/X11/wdm/Xsession the contents of the wdm one is also attached HIH, beto ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Computer King/CaNMail http://www.computerking.ca http://www.canmail.org Sales, Service, and Hosting Email, Data, and Web Packages Ask about web design specials Affiliates http://www.computerking.ca/pages/links/affiliates/affiliates.htm Maybe Computer Science should be in the College of Theology. -- R. S. Barton ImageMagick-6.2.5.5 Image processing tools ORBit-0.5.17_2 High-performance CORBA ORB with support for the C language ORBit2-2.12.5_1 High-performance CORBA ORB with support for the C language OpenEXR-1.2.2_1 A high dynamic-range (HDR) image file format aalib-1.4.r5_1 An ascii art library akode-2.0,1 Default KDE audio backend akode-plugins-mpc-2.0,1 Musepack decoder plugin for akode akode-plugins-mpeg-2.0,1 MPEG audio decoder plugin for akode akode-plugins-oss-2.0,1 OSS output plugin for akode akode-plugins-resampler-2.0,1 Resampler plugin for akode akode-plugins-xiph-2.0,1 FLAC/Speex/Vorbis decoder plugin for akode amspsfnt-1.0_3 AMSFonts PostScript Fonts (Adobe Type 1 format) apache-ant-1.6.5_1 Java- and XML-based build tool, conceptually similar to mak apr-db4-1.2.2_2 The Apache Group's Portability Library arts-1.5.1,1Audio system for the KDE integrated X11 desktop artswrapper-1.2.2 Setuid wrapper for arts aspell-0.60.4_2 Spelling checker with better suggestion logic than ispell at-spi-1.6.6_1 An Assistive Technology Service Provider Interface atk-1.10.3 A GNOME accessibility toolkit (ATK) autoconf-2.13.000227_5 Automatically configure source code on many Un*x platforms autoconf-2.59_2 Automatically configure source code on many Un*x platforms automake-1.4.6_2GNU Standards-compliant Makefile generator (1.4) automake-1.9.6 GNU Standards-compliant Makefile generator (1.9) bash-3.0.16_1 The GNU Project's Bourne Again SHell bison-2.1_1
Re: kdm and fluxbox
RYAN M. vAN GINNEKEN wrote: Thanks to all and i will take your advice Norberto as i do not really like kde that much anyway. If i wanted window i would just install windowsxp or maybe vista would be more like Kde any how i digress. I am tiring to set up wdm and added this line to my /etc/ttys ttyv8 /usr/X11R6/bin/wdm -nodaemon xterm on secure followed the instructions below found on the fulxbox site but it does not quite work http://fluxbox-wiki.org/index.php/Howto_add_fluxbox_to_wdm I get the wdm ok beasty is there, very cool backgound i might add, seen it used in a theme somewhere. No matter what i pick for a windows manager i get the stock Freebsd one wmaker i think? u know the one with the terminal and green menu bars very vanilla. green menu bars = twm wmaker = much better, check it out @ http://www.windowmaker.org An exception to this kde still works and failsafe gives me control of the terminal window bottom right. Also i removed a bunch of managers out of the wdm-config file as i was not using them like this. DisplayManager*wdmWm: wmaker:enlightenment:gnome:kde:fluxbox I still get failsafe and wmaker where do us suppose these come from. Kde still works but not enlightenment gnome or flux box After editing the wdm-config, you need to restart wdm. Ctrl-Alt-Backspace will kill the X server and re-read all the configs. can you please post your wdm-config and a list of your package installed ? (or make them available online) the relevant section in my config: --- ! It will run .xsession !DisplayManager*wdmWm: None --- which means it will read .xsession in my home. my .xsession is : $ cat ~/.xsession ## RUNNING bbkeys from Blackbox because it feels more powerful ## to avoid conflicts with fluxbox's key mgr, I emptied .fluxbox/keys bbkeys xscreensaver -no-splash fbpager -w #wmwifi sleep 1 gkrellm -w #fbdesk torsmo tilda skype gaim fluxbox --- though I realise that I should be simply running startfluxbox and adding all the other cmds to ~/.fluxbox/startup HIH, beto ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kdm and fluxbox
RYAN M. vAN GINNEKEN wrote: usr/X11R6/lib/X11/xdm/Xsession notice this file is for XDM, not KDM. try searching in /usr/X11R6/lib/X11/kdm :) WHERE IS KDM GETTING ITS SESSION INFO FROM AND HOW DO I TELL IT TO ADD FLUXBOX not sure, probably from its config file. Or just set it to custom, and use ~/.xsession to launch your stuff at will. Just curious, why use kdm with all it's KDE dependencies, when you can use xdm, or wdm (what I use). Beto ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kdm and fluxbox
On Wed, 2006-02-15 at 22:35 -0700, RYAN M. vAN GINNEKEN wrote: I am tring to get kdm to log me into fluxbox i have followed the handbook to the letter and can login to gnome kde and enlightnment also options for defaut and failsafe and some others none of which i have tried yet. However flux box is not there and i cannot seem to find where kde is getting these sessions from. There does not seem to be any option in kcontrol for session like mentioned in the freebsd handbook i did go into usr/X11R6/lib/X11/xdm/Xsession and added some lines but nothing happened failsafe) exec /usr/X11R6/bin/xterm -geometry 80x24-0-0 ;; kde) exec /usr/local/bin/startkde ;; GNOME) exec /usr/X11R6/bin/gnome-session ;; FluxBox) exec /usr/X11R6/bin/fluxbox ;; esac esac WHERE IS KDM GETTING ITS SESSION INFO FROM AND HOW DO I TELL IT TO ADD FLUXBOX Look in /usr/local/share/config/kdm -- Mike Jeays http://ca.geocities.com/[EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kdm and fluxbox
On Thursday 16 February 2006 06:35, RYAN M. vAN GINNEKEN wrote: I am tring to get kdm to log me into fluxbox i have followed the handbook to the letter and can login to gnome kde and enlightnment also options for defaut and failsafe and some others none of which i have tried yet. However flux box is not there and i cannot seem to find where kde is getting these sessions from. There does not seem to be any option in kcontrol for session like mentioned in the freebsd handbook i did go into usr/X11R6/lib/X11/xdm/Xsession and added some lines but nothing happened failsafe) exec /usr/X11R6/bin/xterm -geometry 80x24-0-0 ;; kde) exec /usr/local/bin/startkde ;; GNOME) exec /usr/X11R6/bin/gnome-session ;; FluxBox) exec /usr/X11R6/bin/fluxbox ;; esac esac WHERE IS KDM GETTING ITS SESSION INFO FROM AND HOW DO I TELL IT TO ADD FLUXBOX Normally you shouldn't have to touch any file at all, but I think there's an error in /usr/local/share/apps/kdm/sessions/fluxbox.desktop In that file change lines 4-5 to Exec=fluxbox TryExec=fluxbox ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kdm and fluxbox
FluxBox) exec /usr/X11R6/bin/fluxbox ;; I lost the original email so rather that misquote I'm not quoting at all. Just thought I'd mention you should probably use the command startfluxbox as opposed to fluxbox, to start your fluxbox session. Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kdm and fluxbox
Thanks to all and i will take your advice Norberto as i do not really like kde that much anyway. If i wanted window i would just install windowsxp or maybe vista would be more like Kde any how i digress. I am tiring to set up wdm and added this line to my /etc/ttys ttyv8 /usr/X11R6/bin/wdm -nodaemon xterm on secure followed the instructions below found on the fulxbox site but it does not quite work http://fluxbox-wiki.org/index.php/Howto_add_fluxbox_to_wdm I get the wdm ok beasty is there, very cool backgound i might add, seen it used in a theme somewhere. No matter what i pick for a windows manager i get the stock Freebsd one wmaker i think? u know the one with the terminal and green menu bars very vanilla. An exception to this kde still works and failsafe gives me control of the terminal window bottom right. Also i removed a bunch of managers out of the wdm-config file as i was not using them like this. DisplayManager*wdmWm: wmaker:enlightenment:gnome:kde:fluxbox I still get failsafe and wmaker where do us suppose these come from. Kde still works but not enlightenment gnome or flux box please help - Original Message - From: Norberto Meijome [EMAIL PROTECTED] To: RYAN M. vAN GINNEKEN [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Sent: Thursday, February 16, 2006 4:51:43 AM Subject: Re: kdm and fluxbox RYAN M. vAN GINNEKEN wrote: usr/X11R6/lib/X11/xdm/Xsession notice this file is for XDM, not KDM. try searching in /usr/X11R6/lib/X11/kdm :) WHERE IS KDM GETTING ITS SESSION INFO FROM AND HOW DO I TELL IT TO ADD FLUXBOX not sure, probably from its config file. Or just set it to custom, and use ~/.xsession to launch your stuff at will. Just curious, why use kdm with all it's KDE dependencies, when you can use xdm, or wdm (what I use). Beto ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Computer King/CaNMail http://www.computerking.ca http://www.canmail.org Sales, Service, and Hosting Email, Data, and Web Packages Ask about web design specials Affiliates http://www.computerking.ca/pages/links/affiliates/affiliates.htm Maybe Computer Science should be in the College of Theology. -- R. S. Barton ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
kdm and fluxbox
I am tring to get kdm to log me into fluxbox i have followed the handbook to the letter and can login to gnome kde and enlightnment also options for defaut and failsafe and some others none of which i have tried yet. However flux box is not there and i cannot seem to find where kde is getting these sessions from. There does not seem to be any option in kcontrol for session like mentioned in the freebsd handbook i did go into usr/X11R6/lib/X11/xdm/Xsession and added some lines but nothing happened failsafe) exec /usr/X11R6/bin/xterm -geometry 80x24-0-0 ;; kde) exec /usr/local/bin/startkde ;; GNOME) exec /usr/X11R6/bin/gnome-session ;; FluxBox) exec /usr/X11R6/bin/fluxbox ;; esac esac WHERE IS KDM GETTING ITS SESSION INFO FROM AND HOW DO I TELL IT TO ADD FLUXBOX -- Computer King/CaNMail http://www.computerking.ca http://www.canmail.org Sales, Service, and Hosting Email, Data, and Web Packages Ask about web design specials Affiliates http://www.computerking.ca/pages/links/affiliates/affiliates.htm Maybe Computer Science should be in the College of Theology. -- R. S. Barton ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
kdm setup for remote login
Hi, I have been reading man pages, the freebsd manual, kde.org (now offline?) pages, I've been experimenting with different setups, but I do not manage to setup X as I wish. I have a server called beastie, and a desktop called wodan. Both machines start kdm on ttyv8 and allow for local login. When I use xfce4 on wodan (before I had ttyv8 on) and use xhost+, I can ssh to beastie, setup display=wodan:0 and start e.g. emacs, gnucash etc... When I use kdm/kde on wodan, xhost+ isn't enough. I can still ssh to beastie, but apps on beastie do not get acces to wodan:0, although I've done xhost+ on wodan. I do not know how to set up kde so that apps from another machine get access to the display. What I really would like, is to be able to login to beastie using the wodan kdm. I have not been able to figure out how to do this. Any help would be really appreciated. Guido ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
remote requests make KDM dump core
I have a FreeBSD 6.0 box that I access remotely using Cygwin/X from time to time. I use XDMCP to connect up to it from my desktop. Up till about a week ago this was working like a champ, but that has changed since I ran portmanager. Now KDM dumps core the moment I probe it for a connection from a remote box. here is a bit from /var/log/messages: Nov 21 13:56:42 jerseygirl kernel: pid 91116 (kdm), uid 0: exited on signal 11 (core dumped) Nov 21 13:56:42 jerseygirl kdm[630]: Unknown session exit code 0 (sig 11) from manager process Nov 21 13:56:42 jerseygirl kernel: pid 91128 (kdm), uid 0: exited on signal 11 (core dumped) Nov 21 13:56:42 jerseygirl kdm[630]: Unknown session exit code 0 (sig 11) from manager process Nov 21 13:56:44 jerseygirl kernel: pid 91140 (kdm), uid 0: exited on signal 11 (core dumped) Nov 21 13:56:44 jerseygirl kdm[630]: Unknown session exit code 0 (sig 11) from manager process KDM works fine from the console, I am able to log in just fine when I am sitting in front of the box in question, but as soon as I try to connect remotely KDM crashes is promptly revived only to crash again. In Cygwin/X on the remote box I get the traditional X windows gray hash screen the X cursor for a split second then KDM crashes the process starts anew. I have run into one other user who has the same problem. It presented itself to them after upgrading from KDE 3.4.2 to 3.4.3. I noticed the issue after portmanager rebuilt KDE after libidn (/usr/ports/dns/libidn) was moved from /usr/ports/devel to /usr/ports/dns. If you have the ability to check seem if KDM is accepting remote requests could you please do so to confirm the problem? Also, any advice on how to track this issue down would be much appreciated! -Will ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Starting kdm
On 09/19/05 09:21 PM, Eric Schuele sat at the `puter and typed: stan wrote: I'm trying to figure out the current way (on a 4.11 STABLE machine) of having kdm startup on boot. Surpisingly neither the handbook, nor a Google search really led me anywhere on this, and I don't see a script for this in /usr/local/etc/rc.d Do I put it in /etc/tys? If so what's teh proper invocation? Handbook reads (I assume it applies to 4.11 as well): 5.7.3.1 The KDE Display Manager ... snip lots ... Now, make sure kdm is listed in /etc/ttys to be started at the next bootup. To do this, simply follow the instructions from the previous section on XDM and replace references to the /usr/X11R6/bin/xdm program with /usr/local/bin/kdm. Previous Section reads: 5.6.2 Using XDM The XDM daemon program is located in /usr/X11R6/bin/xdm. This program can be run at any time as root and it will start managing the X display on the local machine. If XDM is to be run every time the machine boots up, a convenient way to do this is by adding an entry to /etc/ttys. For more information about the format and usage of this file, see Section 21.3.2.1. There is a line in the default /etc/ttys file for running the XDM daemon on a virtual terminal: ttyv8 /usr/X11R6/bin/xdm -nodaemon xterm off secure By default this entry is disabled; in order to enable it change field 5 from off to on and restart init(8) using the directions in Section 21.3.2.2. The first field, the name of the terminal this program will manage, is ttyv8. This means that XDM will start running on the 9th virtual terminal. Does anyone know if adding ttyv9 /usr/local/bin/kdm -nodaemon xterm off secure but leaving ttyv8 /usr/X11R6/bin/xdm -nodaemon xterm off secure intact would cause any conflict? This would be a lot for most systems, I'm sure, and probably not realistic for a typical system, but I'm curious whether the display managers would conflict. TIA Lou -- Louis LeBlanc FreeBSD-at-keyslapper-DOT-net Fully Funded Hobbyist, KeySlapper Extrordinaire :) Please send off-list email to: leblanc at keyslapper d.t net Key fingerprint = C5E7 4762 F071 CE3B ED51 4FB8 AF85 A2FE 80C8 D9A2 Mitchell's Law of Committees: Any simple problem can be made insoluble if enough meetings are held to discuss it. pgpufvwM2cGDb.pgp Description: PGP signature
Starting kdm
I'm trying to figure out the current way (on a 4.11 STABLE machine) of having kdm startup on boot. Surpisingly neither the handbook, nor a Google search really led me anywhere on this, and I don't see a script for this in /usr/local/etc/rc.d Do I put it in /etc/tys? If so what's teh proper invocation? -- U.S. Encouraged by Vietnam Vote - Officials Cite 83% Turnout Despite Vietcong Terror - New York Times 9/3/1967 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Starting kdm
stan wrote: I'm trying to figure out the current way (on a 4.11 STABLE machine) of having kdm startup on boot. Surpisingly neither the handbook, nor a Google search really led me anywhere on this, and I don't see a script for this in /usr/local/etc/rc.d Do I put it in /etc/tys? If so what's teh proper invocation? Handbook reads (I assume it applies to 4.11 as well): 5.7.3.1 The KDE Display Manager ... snip lots ... Now, make sure kdm is listed in /etc/ttys to be started at the next bootup. To do this, simply follow the instructions from the previous section on XDM and replace references to the /usr/X11R6/bin/xdm program with /usr/local/bin/kdm. Previous Section reads: 5.6.2 Using XDM The XDM daemon program is located in /usr/X11R6/bin/xdm. This program can be run at any time as root and it will start managing the X display on the local machine. If XDM is to be run every time the machine boots up, a convenient way to do this is by adding an entry to /etc/ttys. For more information about the format and usage of this file, see Section 21.3.2.1. There is a line in the default /etc/ttys file for running the XDM daemon on a virtual terminal: ttyv8 /usr/X11R6/bin/xdm -nodaemon xterm off secure By default this entry is disabled; in order to enable it change field 5 from off to on and restart init(8) using the directions in Section 21.3.2.2. The first field, the name of the terminal this program will manage, is ttyv8. This means that XDM will start running on the 9th virtual terminal. HTH -- Regards, Eric ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
What is KDM Console Login?
On the KDM menu there is an option Console Login. When I select this, nothing happens. What's it supposed to do, and how can I make it do it? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What is KDM Console Login?
RW wrote: On the KDM menu there is an option Console Login. When I select this, nothing happens. What's it supposed to do, and how can I make it do it? The world as we know it, ends... -- Best regards, Chris Hindsight is an exact science. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
KDM and .bash_profile problem
I think it used to be the case that if you used kdm to login, then .bash_profile would not get sourced by bash (because it's not a login shell). However it appears that the Xsession script in /usr/local/share/config/kdm now sources .bash_profile explicitly if bash is your shell. My problem is that when .bash_profile is sourced this way, I only pick-up environmental variables, and any aliases or bash functions don't work. They work as expected when I login via a virtual-terminal, so I don't think it is my script. For those who don't have kdm, this is the Xsession file: -- #! /bin/sh # Xsession - run as user session=$1 # Note that the respective logout scripts are not sourced. case $SHELL in */bash) [ -z $BASH ] exec $SHELL $0 $@ set +o posix [ -f /etc/profile ] . /etc/profile if [ -f $HOME/.bash_profile ]; then . $HOME/.bash_profile elif [ -f $HOME/.bash_login ]; then . $HOME/.bash_login elif [ -f $HOME/.profile ]; then . $HOME/.profile fi ;; # ...OTHER SHELL CASE ENTRIES SNIPPED # esac [ -f /etc/xprofile ] . /etc/xprofile [ -f $HOME/.xprofile ] . $HOME/.xprofile case $session in ) exec xmessage -center -buttons OK:0 -default OK Sorry, $DESKTOP_SESSION is no valid session. ;; failsafe) exec xterm -geometry 80x24-0-0 ;; custom) exec $HOME/.xsession ;; default) exec /usr/local/bin/startkde ;; *) eval exec $session ;; esac exec xmessage -center -buttons OK:0 -default OK Sorry, cannot execute $session. Check $DESKTOP_SESSION.desktop. -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
kde kdm mouse - AGAIN
I have the latest installation of freebsd 5.4 on my laptop, kde kdm 3.4. The laptop has a synaptic mousepad endowed of two buttons that in normal conditions are not used at all being enough to double-hit on the pad to have the same effect as that of pressing the left button. Now at boot time I enabled moused # ps ax|grep moused 493 ?? Ss 0:00.54 /usr/sbin/moused -p /dev/psm0 -t auto And the following in /etc/X11/xorg.conf Section InputDevice Identifier Mouse0 Driver mouse Option Protocol Auto Option Device /dev/sysmouse Option ZAxisMapping 4 5 EndSection . Now it happens that: 1) If I start kde as a user by means of the command startx (having put startkde into .xinitrc) the mouse(-pad) works as expected: I can move around the screen and select and launch programs just moving on the pad and double hitting the pad . No problems! In a nutshell no need to press the left button. 2) If at boot time I start kde by means of kdm having put in /etc/ttys: ttyv8 /usr/local/bin/kdm -nodaemon xterm on secure and modified /etc/pam.d as required to autologin, I immediatedly and automagically login into kde as a user and the mouse works BUT... with the pad I can only move around the screen and the double-hit doesn't work anymore so that I have to use the left button cumpulsorily (and annoyingly). My feeling is that moused is both somewhat slow and one of the last services to be executed. Therefore I highly suspect that the execution of moused in some way overlaps with the execution of autologin kdm at boot time causing the malfunctioning mousepad behaviour. Now I'm trying to delay a bit the execution of kdm by adding something like ttyv8 /bin/sleep 2;/usr/local/bin/kdm -nodaemon xterm on secure ttyv8 /bin/sleep 2 /usr/local/bin/kdm -nodaemon xterm on secure but FreeBSD doesn't seem to like either: it doesn't execute kdm and issue a warning about a delay of 60 seconds?? How could I delay a bit the autologin kdm? Ciao Vittorio --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
kde kdm mouse
I have the latest installation of freebsd 5.4 on my laptop, kde kdm 3.4. The laptop has a synaptic mousepad endowed of two buttons that in normal conditions are not used at all being enough to double-hit on the pad to have the same effect as that of pressing the left button. Now at boot time I enabled moused # ps ax|grep moused 493 ?? Ss 0:00.54 /usr/sbin/moused -p /dev/psm0 -t auto And the following in /etc/X11/xorg.conf Section InputDevice Identifier Mouse0 Driver mouse Option Protocol Auto Option Device /dev/sysmouse Option ZAxisMapping 4 5 EndSection . Now it happens that: 1) If I start kde as a user by means of the command startx (having put startkde into .xinitrc) the mouse(-pad) works as expected: I can move around the screen and select and launch programs just moving on the pad and double hitting the pad . No problems! In a nutshell no need to press the left button. 2) If at boot time I start kde by means of kdm having put in /etc/ttys: ttyv8 /usr/local/bin/kdm -nodaemon xterm on secure and modified /etc/pam.d as required to autologin, I immediatedly and automagically login into kde as a user and the mouse works BUT... with the pad I can only move around the screen and the double-hit doesn't work anymore so that I have to use the left button cumpulsorily (and annoyingly). Why in your opinion is that crazy behavior and what should I do? Ciao Vittorio ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kde kdm mouse
On Sun, 15 May 2005, Vittorio De Martino wrote: I have the latest installation of freebsd 5.4 on my laptop, kde kdm 3.4. The laptop has a synaptic mousepad endowed of two buttons that in normal conditions are not used at all being enough to double-hit on the pad to have the same effect as that of pressing the left button. Now at boot time I enabled moused # ps ax|grep moused 493 ?? Ss 0:00.54 /usr/sbin/moused -p /dev/psm0 -t auto And the following in /etc/X11/xorg.conf Section InputDevice Identifier Mouse0 Driver mouse Option Protocol Auto Option Device /dev/sysmouse Option ZAxisMapping 4 5 EndSection . Now it happens that: 1) If I start kde as a user by means of the command startx (having put startkde into .xinitrc) the mouse(-pad) works as expected: I can move around the screen and select and launch programs just moving on the pad and double hitting the pad . No problems! In a nutshell no need to press the left button. 2) If at boot time I start kde by means of kdm having put in /etc/ttys: ttyv8 /usr/local/bin/kdm -nodaemon xterm on secure and modified /etc/pam.d as required to autologin, I immediatedly and automagically login into kde as a user and the mouse works BUT... with the pad I can only move around the screen and the double-hit doesn't work anymore so that I have to use the left button cumpulsorily (and annoyingly). Why in your opinion is that crazy behavior and what should I do? Are the startx-launched and kdm-launched X daemons using the same config file? Check the top of /var/log/Xorg.*.log for sure. If you ran X -configure at some point it might be using a config out of your home directory and not in one of the system locations. When kdm starts it it doesn't look in your homedir :) -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Kdm problem
Hi, I have problem running kdm on a FreeBSD 5.3 server. When I start the kdm, I receive following error in /var/log/messages: May 3 20:45:10 test kdm[567]: XDMCP socket creation failed, errno 43 I was not able to find any answer searching with google, so I hope you can help me. Kdm is set for broadcasting, allowing everyone to establish a communication. Regards, Ivailo Tanusheff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kdm problem
Ivailo Tanusheff [EMAIL PROTECTED] writes: I have problem running kdm on a FreeBSD 5.3 server. When I start the kdm, I receive following error in /var/log/messages: May 3 20:45:10 test kdm[567]: XDMCP socket creation failed, errno 43 I was not able to find any answer searching with google, so I hope you can help me. Kdm is set for broadcasting, allowing everyone to establish a communication. You aren't running at a raised securelevel, are you? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
How do I get KDM to launch KDE ?
Hi, I selected KDM to run at startup by editing /etc/ttys : ttyv8 ³/usr/local/bin/kdm nodaemon² xterm on secure I also created a .xsession file both in /root and in my home directory with the line : exec startkde When I reboot, KDM starts up but when I login (correct password), the login windows disappears, the KDM background remains and KDE doesn¹t start. However, KDE starts fine when I run startx in a terminal session. Is there something I didn¹t do properly ? Thanks, Edward BTW, I use FreeBSD 5.3, Xorg 6.7.0-9, KDE 3.3.0-4 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
re:How do i get KDM to launch KDE?
Tried a .xinitrc instead of a .xsession ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How do I get KDM to launch KDE ?
On Thu, 24 Feb 2005, Edward Lichtner wrote: Hi, I selected KDM to run at startup by editing /etc/ttys : ttyv8 ³/usr/local/bin/kdm nodaemon² xterm on secure I also created a .xsession file both in /root and in my home directory with the line : exec startkde When I reboot, KDM starts up but when I login (correct password), the login windows disappears, the KDM background remains and KDE doesn¹t start. However, KDE starts fine when I run startx in a terminal session. Is there something I didn¹t do properly ? Thanks, Edward See the handbook for more informations (5.7.3.1 The KDE Display Manager): [...] To make sure kdm understands what the labels (KDE, GNOME etc) mean, edit the files used by XDM. In a terminal window, as root, edit the file /usr/X11R6/lib/X11/xdm/Xsession. There is a section in the middle like this: case $# in 1) case $1 in failsafe) exec xterm -geometry 80x24-0-0 ;; esac esac A few lines need to be added to this section. Assuming the labels from used were ``KDE'' and ``GNOME'', use the following: case $# in 1) case $1 in kde) exec /usr/local/bin/startkde ;; GNOME) exec /usr/X11R6/bin/gnome-session ;; failsafe) exec xterm -geometry 80x24-0-0 ;; esac esac [...] Oliver -- ... don't touch the bang bang fruit ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
KDM doesn't launch any WindowManager
Hello, I've just installed the last version of FreeBSD (5.3), after the reference, but I cannot launch any WindowManager using KDM : KDM closes and restart immediatly... I think that it's the same about XDM. But my Window Managers works using startx ! I think it's because there is no X-configuration menu during the installation with sysinstall... But what's the name of the new tool ? Thanks Hugo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KDM doesn't launch any WindowManager
On Thursday 10 February 2005 11:36 am, HuGo Herter wrote: Hello, I've just installed the last version of FreeBSD (5.3), after the reference, but I cannot launch any WindowManager using KDM : KDM closes and restart immediatly... I think that it's the same about XDM. But my Window Managers works using startx ! I think it's because there is no X-configuration menu during the installation with sysinstall... But what's the name of the new tool ? Thanks Hugo See the X Configuration section of the online manual: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.html Best of luck, Andrew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KDM doesn't launch any WindowManager
HuGo Herter [EMAIL PROTECTED] writes: HuGo Herter [EMAIL PROTECTED] writes: Hello, I've just installed the last version of FreeBSD (5.3), after the reference, but I cannot launch any WindowManager using KDM : KDM closes and restart immediatly... I think that it's the same about XDM. But my Window Managers works using startx ! In that case, it's almost certainly a problem with your .xsession file. Is it different than your .xinitrc? I think it's because there is no X-configuration menu during the installation with sysinstall... But what's the name of the new tool ? A lot of people don't need to configure X to have it just work. The tool you're looking for is xorgcfg or xorgconfig, but your configuration is probably fine if it works with startx. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Starting kdm
Is kdm still run from /etc/ttys? The reason I aks is that I have a machine that I use gdm on, and I kow it's not run from /etc/ttys anymore. -- They that would give up essential liberty for temporary safety deserve neither liberty nor safety. -- Benjamin Franklin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KDM, KDE 3.3 and xmodmap
On Saturday 15 January 2005 21:56, Maarten wrote: Does anyone know how to configure KDM or KDE so that is uses xmodmap? The configuration is pretty much out of the box, 5.3. For some reason using custom from the KDM menu with .xsession: #!/bin/sh xmodmap -e 'keycode 203=F13' exec startkde Does start kde but ignores the xmodmap entry. If i do 'sh .xsession' after login xmodmap is processed and I get a message KDE is already running :-) Thanks, Maarten I think KDM completely ignores ~/.xsession and ~/.xinit files out of the box. I don't know how to change this. If you want to test your ~/.xsession and ~/.xinit files you can type startx -- :1 to start up another Xserver. Also I can't seem to find any logic to what uses ~/.xsession and what uses ~/.xinit so I hard linked them to the same file. -- /Xian If you can stay calm, while all around you is chaos...then you probably haven't completely understood the seriousness of the situation unknown author ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
KDM, KDE 3.3 and xmodmap
Does anyone know how to configure KDM or KDE so that is uses xmodmap? The configuration is pretty much out of the box, 5.3. For some reason using custom from the KDM menu with .xsession: #!/bin/sh xmodmap -e 'keycode 203=F13' exec startkde Does start kde but ignores the xmodmap entry. If i do 'sh .xsession' after login xmodmap is processed and I get a message KDE is already running :-) Thanks, Maarten ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
KDM problems on fresh install of 5.3
Hi, I just installed FreeBSD 5.3 on a Dell Latitude, and installation went without a hitch. While trying to configure KDM for graphical login, though, I ran into some problems. startx works fine as both root and as a regular user. However, when I run KDM and enter my username and password all that loads is another instance of KDM. This is very frustrating. The same issue occurs when I try XDM, so I think the problem is with BSD and not KDE. I've searched around for a solution to this, and though I've seen that a lot of other people have had the same problem, I have not found any help solving it. Any help would be appreciated. Thanks, Peter ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KDM problems on fresh install of 5.3
A couple of problems that might cause this have been discussed recently in the freebsd-kde mailing list. One of them involved not having the correct KDE startup files in /usr/local/share/config/kdm (where kdmrc lives, apparently) and another had to do with commands in the shell startup scripts failing (such as user .profile or system /etc/profile). I've also seen this happen when a previous attempt to start X failed and left trash in the user's home directory and in the /tmp directory. I think the command to create the kdm startup files is genkdmconf; however, there are no associated man pages with it but it should be documented on the kde.org Web site. Mike Squires On Fri, 24 Dec 2004, Peter McMahan wrote: Hi, I just installed FreeBSD 5.3 on a Dell Latitude, and installation went without a hitch. While trying to configure KDM for graphical login, though, I ran into some problems. startx works fine as both root and as a regular user. However, when I run KDM and enter my username and password all that loads is another instance of KDM. This is very frustrating. The same issue occurs when I try XDM, so I think the problem is with BSD and not KDE. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
gdm/kdm and synergy
I have two machines infront of me. A FreeBSD 5.2.1 system and a Gentoo system. The gentoo system has a mouse and keyboard plugged into it. The FreeBSD system doesn't. How do I add synergyc -f onan to the gdm startup script. I would rather use gdm, because I don't want to install qt/kde on the machine. TIA -John ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gdm/kdm and synergy
I have a similar setup, FreeBSD, Fedora and a win2k box.. My Fedora is a client without a mout and keyboard.. I have a file with the command synergyc -n IP_address_of_Client/Fedora IP_address_of_Synergy_Server Move this file into your init.d directory and then make a link to your systems normal run level directory, i.e. rc#.d, where # is your systems normal run level.. Hope this helps resolve your problem Dee --- John Oxley [EMAIL PROTECTED] wrote: I have two machines infront of me. A FreeBSD 5.2.1 system and a Gentoo system. The gentoo system has a mouse and keyboard plugged into it. The FreeBSD system doesn't. How do I add synergyc -f onan to the gdm startup script. I would rather use gdm, because I don't want to install qt/kde on the machine. TIA -John ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Mail is new and improved - Check it out! http://promotions.yahoo.com/new_mail ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kdm refuses to allow non-root login to kde
On Sun, Aug 15, 2004 at 12:05:00AM -0400, Tim Kellers wrote: I've been battling this on and off (mostly off) since April. If I put exec startkde in .xesession in a non-root folder and I enable xdm in /etc/ttys, I can log into xorg's xdm and kde starts just fine -- even as a non-root user. If I enable kdm in /etc/ttys, I get the kdm login screen, and if I login with a non-root account, the display just stays at it's default background until I kill it with CNTRL-ALT-BACKSPACE. Sounds like a DNS problem (yes, I know, why the heck does kdm want with a DNS lookup - but there it is). If you put the output of hostname(1) into /etc/hosts as an alias for 127.0.0.1 (localhost), your problem _may_ go away. Cheers. -- Jonathan Chen [EMAIL PROTECTED] -- Do not take life too seriously. You will never get out of it alive. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kdm refuses to allow non-root login to kde
On Sunday 15 August 2004 02:33 am, Jonathan Chen wrote: On Sun, Aug 15, 2004 at 12:05:00AM -0400, Tim Kellers wrote: I've been battling this on and off (mostly off) since April. If I put exec startkde in .xesession in a non-root folder and I enable xdm in /etc/ttys, I can log into xorg's xdm and kde starts just fine -- even as a non-root user. If I enable kdm in /etc/ttys, I get the kdm login screen, and if I login with a non-root account, the display just stays at it's default background until I kill it with CNTRL-ALT-BACKSPACE. Sounds like a DNS problem (yes, I know, why the heck does kdm want with a DNS lookup - but there it is). If you put the output of hostname(1) into /etc/hosts as an alias for 127.0.0.1 (localhost), your problem _may_ go away. Cheers. No Joy... root still brings up the kde splash screen, everyone else sits frozen at the kde background screen. xdm still works. I'm at a complete loss how to explan this. $vi /etc/hosts 127.0.0.1 www.smsdesign.org localhost 10.0.1.7www.smsdesign.org www 10.0.1.7www.smsdesign.org. 10.0.1.7mail.smsdesign.org mail 10.0.1.7smsdesign.org. 128.235.112.11 eris.njit.edu eris I rebooted, too, just in case. ~ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
kdm refuses to allow non-root login to kde
I've been battling this on and off (mostly off) since April. If I put exec startkde in .xesession in a non-root folder and I enable xdm in /etc/ttys, I can log into xorg's xdm and kde starts just fine -- even as a non-root user. If I enable kdm in /etc/ttys, I get the kdm login screen, and if I login with a non-root account, the display just stays at it's default background until I kill it with CNTRL-ALT-BACKSPACE. At the kdm login screen, if I login as root, the kde desktop loads and starts just fine. I've read and implemented the commands in /usr/src/UPDATING regarding kde/kdm and I'm running the latest kde-everything as of a few hours ago. I do like Xorg's xdm, but I do like kdm/KDE better, but, apparently, kdm/kde doesn't like me at all. The box I'm currently testing this on is i386 FreeBSD-Current as of 8/7/2004, but I've also had this difficulty on 4.9/4.10 -STABLE installs at work. Any advice on wht I'm doing wrong (or a pointer to docs so I can RTFM) would be greatly appreciated. Tim Kellers CPE/NJIT ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
kdm refuses to allow non-root login to kde
[If this gets posted twice, I apologize for the noise] I've been battling this on and off (mostly off) since April. If I put exec startkde in .xesession in a non-root folder and I enable xdm in /etc/ttys, I can log into xorg's xdm and kde starts just fine -- even as a non-root user. If I enable kdm in /etc/ttys, I get the kdm login screen, and if I login with a non-root account, the display just stays at it's default background until I kill it with CNTRL-ALT-BACKSPACE. At the kdm login screen, if I login as root, the kde desktop loads and starts just fine. I've read and implemented the commands in /usr/src/UPDATING regarding kde/kdm and I'm running the latest kde-everything as of a few hours ago. I do like Xorg's xdm, but I do like kdm/KDE better, but, apparently, kdm/kde doesn't like me at all. The box I'm currently testing this on is i386 FreeBSD-Current as of 8/7/2004, but I've also had this difficulty on 4.9/4.10 -STABLE installs at work. Any advice on wht I'm doing wrong (or a pointer to docs so I can RTFM) would be greatly appreciated. Tim Kellers CPE/NJIT ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
kdm or GNOME-session hangs?
I'm using FreeBSD 4.10 with a custom kernel. I have two problems: 1) If ACPI support activated, my fdc0 does not work (the kernel can not reserve I/O port addresses for it). Without ACPI, everything works OK, but: 2) When using kdm as display manager, if I select GNOME session as root and then try to halt/reboot directly from the GNOME's logout menu, the system appears to hang until I press Ctrl-Alt-Del. After that, the system reboots (of course). What's the problem? How can I solve it? This is not encountered in Linux, for example. Thank you. Home, no matter how far... http://www.home.ro ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: kdm and startkde
Show us your ~/.xinit ! for kdm/xdm/gdm, - check your hostname. Try to run xdm, gdm and kdm manually and let us know if there is any difference between them. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brett Wiggins Sent: Thursday, June 17, 2004 8:50 AM To: [EMAIL PROTECTED] Subject: kdm and startkde hello, I am having some problems with startkde and kdm. When I run startkde i get the following outpit; xset: unable to open dispaly xsetroot: unable to open display '' startkde: starting up... ksplash cannot connect to X server kdeinit: Aborting. $DISPLAY is not set Warning: connect() failed: : no such file or directory ksmserver : cannot connect to X server startkde: shutting down Warning: connect() failed: : no such file or directory Error : Can't contact kdeinit! startkde: Running shutdown scripts startkde: done When I run startx kde runs fine. When I edit /etc/ttys to enable a graphical login, kdm runs but nothing happens when I log in. The login screen is just reloaded. Any help would be great. Brett ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
kdm and startkde
hello, I am having some problems with startkde and kdm. When I run startkde i get the following outpit; xset: unable to open dispaly xsetroot: unable to open display '' startkde: starting up... ksplash cannot connect to X server kdeinit: Aborting. $DISPLAY is not set Warning: connect() failed: : no such file or directory ksmserver : cannot connect to X server startkde: shutting down Warning: connect() failed: : no such file or directory Error : Can't contact kdeinit! startkde: Running shutdown scripts startkde: done When I run startx kde runs fine. When I edit /etc/ttys to enable a graphical login, kdm runs but nothing happens when I log in. The login screen is just reloaded. Any help would be great. Brett ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kdm and startkde
Brett Wiggins wrote: hello, I am having some problems with startkde and kdm. When I run startkde i get the following outpit; xset: unable to open dispaly xsetroot: unable to open display '' startkde: starting up... ksplash cannot connect to X server kdeinit: Aborting. $DISPLAY is not set Warning: connect() failed: : no such file or directory ksmserver : cannot connect to X server startkde: shutting down Warning: connect() failed: : no such file or directory Error : Can't contact kdeinit! startkde: Running shutdown scripts startkde: done When I run startx kde runs fine. I thinks it's because startx launches X before it starts startkde, and startkde only attempts to launch KDE, which isn't going to work if there is no X server running. When I edit /etc/ttys to enable a graphical login, kdm runs but nothing happens when I log in. The login screen is just reloaded. Any help would be great. What about XDM? Is that working? Is your /var/log/XFree86 giving you any useful output? (connection refused or something?) Cheers, Jorn ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
kdm questions
hello (again), I am still having some problems with kdm, I have searched (again) the archives and the handbook. Below are the steps I took, files I edited during setup. After I installed the X window system and KDE I created the file ~/.xinitrc which contains; exec startkde after I created the file I could use startx to run KDE. I then setup KDM by editing the file /usr/X11R6/lib/X11/xdm/Xsession. I added the following to the file; case $# in 1) case $1 in kde) exec /usr/local/bin/startkde ;; failsafe) exec xtem -geometry 80x24-0-0 ;; esac esac Finally I added the following to /usr/X11R6/lib/X11/xdm/Xsetup_0; /usr/local/bin/kdmdesktop KDM loads but when I log in nothing happens, I just end up back at the login screen. This is all the info I can think of. If I missed any please let me know. Thanks again Brett ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
more kdm questions
hello again, Did you set the hostname ? This is going to sound like a stupid question but how do I set the hostname? I searched the archive for 'kdm hostname' and found nothing. Thanks again Brett hello (again), I am still having some problems with kdm, I have searched (again) the archives and the handbook. Below are the steps I took, files I edited during setup. After I installed the X window system and KDE I created the file ~/.xinitrc which contains; exec startkde after I created the file I could use startx to run KDE. I then setup KDM by editing the file /usr/X11R6/lib/X11/xdm/Xsession. I added the following to the file; case $# in 1) case $1 in kde) exec /usr/local/bin/startkde ;; failsafe) exec xtem -geometry 80x24-0-0 ;; esac esac Finally I added the following to /usr/X11R6/lib/X11/xdm/Xsetup_0; /usr/local/bin/kdmdesktop KDM loads but when I log in nothing happens, I just end up back at the login screen. This is all the info I can think of. If I missed any please let me know. Thanks again Brett ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: more kdm questions
Brett Wiggins [EMAIL PROTECTED] wrote: Did you set the hostname ? This is going to sound like a stupid question but how do I set the hostname? I searched the archive for 'kdm hostname' and found nothing. Set the hostname for the machine. For temporary (and testing) you can use the hostname command from a shell prompt. To get it set for good, add a line like: hostname=my.host.name in /etc/rc.conf Make sure that the name you choose is either in DNS, or you enter a matching record in /etc/hosts. Otherwise, you'll have problems with applications running slowly, or not starting at all because they try to verify the hostname. Thanks again Brett hello (again), I am still having some problems with kdm, I have searched (again) the archives and the handbook. Below are the steps I took, files I edited during setup. After I installed the X window system and KDE I created the file ~/.xinitrc which contains; exec startkde after I created the file I could use startx to run KDE. I then setup KDM by editing the file /usr/X11R6/lib/X11/xdm/Xsession. I added the following to the file; case $# in 1) case $1 in kde) exec /usr/local/bin/startkde ;; failsafe) exec xtem -geometry 80x24-0-0 ;; esac esac Finally I added the following to /usr/X11R6/lib/X11/xdm/Xsetup_0; /usr/local/bin/kdmdesktop KDM loads but when I log in nothing happens, I just end up back at the login screen. This is all the info I can think of. If I missed any please let me know. Thanks again Brett ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: more kdm questions
Hi: Did you remember to change the line in /etc/ttys From: ttyv8 /usr/X11R6/bin/xdm -nodaemon xterm off secure To: ttyv8 /usr/X11R6/bin/kdm -nodaemon xterm on secure You can look at section 5.6.2 in the FreeBSD Handbook for more details. Also if you have any other troubles, then you may want to askk at the Kde FreeBSD site http://freebsd.kde.org/. Those pople are quite freindly and helpful. -- Original message from Bill Moran : -- Brett Wiggins wrote: Did you set the hostname ? This is going to sound like a stupid question but how do I set the hostname? I searched the archive for 'kdm hostname' and found nothing. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: more kdm questions
Forgot to cc the list -Original Message- From: Ruben Bloemgarten [mailto:[EMAIL PROTECTED] Sent: Friday, June 18, 2004 8:13 PM To: 'Brett Wiggins' Subject: RE: more kdm questions # vi /etc/rc.conf Add hostname=yourhostname to the file Reboot will make the change permanent. For a temprary hostname : #hostname yourhostname To verify if the hostname was set : #hostname The hostname is not related to X nor xdm/gdm/kdm, but is a system parameter. Many applications will not function properly or at all without the machine knowing who it is. Xdm/kdm/gdm are amongst those appz that won't work without the hostname. Also, I always take the xinitrc template from /usr/X11R6/lib/X11/xinit, copy it to my home directory and modify at will. Good luck. -Original Message- From: Brett Wiggins [mailto:[EMAIL PROTECTED] Sent: Friday, June 18, 2004 6:21 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: more kdm questions hello again, Did you set the hostname ? This is going to sound like a stupid question but how do I set the hostname? I searched the archive for 'kdm hostname' and found nothing. Thanks again Brett hello (again), I am still having some problems with kdm, I have searched (again) the archives and the handbook. Below are the steps I took, files I edited during setup. After I installed the X window system and KDE I created the file ~/.xinitrc which contains; exec startkde after I created the file I could use startx to run KDE. I then setup KDM by editing the file /usr/X11R6/lib/X11/xdm/Xsession. I added the following to the file; case $# in 1) case $1 in kde) exec /usr/local/bin/startkde ;; failsafe) exec xtem -geometry 80x24-0-0 ;; esac esac Finally I added the following to /usr/X11R6/lib/X11/xdm/Xsetup_0; /usr/local/bin/kdmdesktop KDM loads but when I log in nothing happens, I just end up back at the login screen. This is all the info I can think of. If I missed any please let me know. Thanks again Brett ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: more kdm questions
You don't need do this to get kdm working. Only if you want it to start at boot. I suggest you do this when you get kdm working properly, not before. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Friday, June 18, 2004 8:01 PM To: [EMAIL PROTECTED] Subject: Re: more kdm questions Hi: Did you remember to change the line in /etc/ttys From: ttyv8 /usr/X11R6/bin/xdm -nodaemon xterm off secure To: ttyv8 /usr/X11R6/bin/kdm -nodaemon xterm on secure You can look at section 5.6.2 in the FreeBSD Handbook for more details. Also if you have any other troubles, then you may want to askk at the Kde FreeBSD site http://freebsd.kde.org/. Those pople are quite freindly and helpful. -- Original message from Bill Moran : -- Brett Wiggins wrote: Did you set the hostname ? This is going to sound like a stupid question but how do I set the hostname? I searched the archive for 'kdm hostname' and found nothing. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
