Re: XDM cannot start desktop after Xorg upgrade
2013-06-09 07:46, Leslie Jensen skrev: 2013-06-08 17:28, Polytropon skrev: On Sat, 08 Jun 2013 12:20:56 +0200, Leslie Jensen wrote: I've been using XDM as login manager for years. Since the latest Xorg upgrade, XDM cannot start XFCE4 as it used to. Strange that this happens after an upgrade. What initalization mechanism do you use for your X session? Do you use the chained approach, i. e., ~/.xsession containing #!/bin/csh source ~/.cshrc exec ~/.xinitrc and all your session startup stuff in ~/xinitrc? (I'm using this approach for many years with XDM successfully.) Disabling XDM and starting X manually works. In this case, ~/.xinitrc will be processed. XDM does use ~/.xsession instead (same content can be used). This seems to indicate that the upgrade did not affect the programs called. I've done like this lrwxr-xr-x 1 user user 9 31 Dec 17:53 .xinitrc@ - .xsession These are the contents of .xsession # LANG=sv_SE.ISO8859-1; export LANG /usr/local/bin/startxfce4 ___ 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 I've disabled XDM for now starting X manually. When I exit X I see this on the console: Thanks /Leslie onStopListening called for active ServerSocket... (xfce4-session:2440): GLib-WARNING **: GError set over the top of a previous GEr ror or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Failed to connect to socket /var/run/dbus/sys tem_bus_socket: Filen eller katalogen finns ej (xfce4-session:2440): GLib-WARNING **: GError set over the top of a previous GEr ror or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Failed to connect to socket /var/run/dbus/sys tem_bus_socket: Filen eller katalogen finns ej xfce4-session: Querying suspend failed: Failed to connect to socket /var/run/dbu s/system_bus_socket: Filen eller katalogen finns ej xinit: connection to X server lost waiting for X server to shut down xfsettingsd: Fatal IO error 35 (Resursen är t illfälligt otillgänglig) on X server :0.0. .failed to unset mtrr: No such file or directory ___ 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: XDM cannot start desktop after Xorg upgrade
On Sat, 08 Jun 2013 12:20:56 +0200, Leslie Jensen wrote: I've been using XDM as login manager for years. Since the latest Xorg upgrade, XDM cannot start XFCE4 as it used to. Strange that this happens after an upgrade. What initalization mechanism do you use for your X session? Do you use the chained approach, i. e., ~/.xsession containing #!/bin/csh source ~/.cshrc exec ~/.xinitrc and all your session startup stuff in ~/xinitrc? (I'm using this approach for many years with XDM successfully.) Disabling XDM and starting X manually works. In this case, ~/.xinitrc will be processed. XDM does use ~/.xsession instead (same content can be used). This seems to indicate that the upgrade did not affect the programs called. -- Polytropon 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 freebsd-questions-unsubscr...@freebsd.org
Re: XDM cannot start desktop after Xorg upgrade
2013-06-08 17:28, Polytropon skrev: On Sat, 08 Jun 2013 12:20:56 +0200, Leslie Jensen wrote: I've been using XDM as login manager for years. Since the latest Xorg upgrade, XDM cannot start XFCE4 as it used to. Strange that this happens after an upgrade. What initalization mechanism do you use for your X session? Do you use the chained approach, i. e., ~/.xsession containing #!/bin/csh source ~/.cshrc exec ~/.xinitrc and all your session startup stuff in ~/xinitrc? (I'm using this approach for many years with XDM successfully.) Disabling XDM and starting X manually works. In this case, ~/.xinitrc will be processed. XDM does use ~/.xsession instead (same content can be used). This seems to indicate that the upgrade did not affect the programs called. I've done like this lrwxr-xr-x 1 user user 9 31 Dec 17:53 .xinitrc@ - .xsession These are the contents of .xsession # LANG=sv_SE.ISO8859-1; export LANG /usr/local/bin/startxfce4 ___ 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: xdm and gdm
On Sat, 21 Jul 2012 19:19:15 +0200 (CEST), Wojciech Puchar wrote: i run xdm normally. after logging it runs my $HOME/.xsession that starts things like fvwm2 i wanted to run gnome-session once, changed fvwm2 to /usr/local/bin/gnome-sessions ^ Is this a typo? According to the Handbook, /usr/local/bin/gnome-session (without trailing 's') should be executed. Source: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x11-wm.html See 6.7.1.2: Installing GNOME. after loggin in it just exits. no .xsession-errors is created. no idea where to seek error messages at all. Maybe errors are reported to the 1st virtual terminal where the XDM process outputs its messages to (currently not running xdm, so I can't check). with gdm loading gnome works. Do you have gdm_enable=YES gnome_enable=YES in /etc/rc.conf, and /proc mounted, as suggested in the Handbook? Maybe gdm has some preparations that aren't found by gnome-session when started autonomously. But the Handbook says it works without GDM, so it should work either per .xinitrc (startx command) _and_ also with xdm (and therefore with wdm and others). any ideas? (except: just use gdm please) Just use... computer. :-) -- Polytropon 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 freebsd-questions-unsubscr...@freebsd.org
Re: xdm and gdm
Is this a typo? According to the Handbook, /usr/local/bin/gnome-session (without trailing 's') should be executed. indeed a typo. thank you. after loggin in it just exits. no .xsession-errors is created. no idea where to seek error messages at all. Maybe errors are reported to the 1st virtual terminal where the XDM process outputs its messages to (currently not running xdm, so I can't check). there are imho nowhere. Do you have gdm_enable=YES gnome_enable=YES in /etc/rc.conf, and /proc mounted, as suggested in the Handbook? Maybe gdm has some preparations that aren't found by gnome-session when started autonomously. But the Handbook says it works without gdm is fine and works. the problem is that i wasn't able to my non-gnome .xsession work properly with gdm at all. at the same time i like xdm and want to use, RARELY use it to run gnome. Do you have any data about preparations that gdm do? ___ 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: xdm and gdm
On Sat, 21 Jul 2012 20:40:44 +0200 (CEST), Wojciech Puchar wrote: after loggin in it just exits. no .xsession-errors is created. no idea where to seek error messages at all. Maybe errors are reported to the 1st virtual terminal where the XDM process outputs its messages to (currently not running xdm, so I can't check). there are imho nowhere. When I do startx, the vitrual terminal from which I issue this command will capture the messages related to X. In case of xdm, I did assume that would be ttyv0 implicitely. Do you have any data about preparations that gdm do? The Handbook mentions /proc to be mounted, but that's not related. The settings gdm_enable=YES gnome_enable=YES in /etc/rc.conf would (if I understand the mechanism correctly) correspond to scripts /usr/local/etc/rc.d/gdm /usr/local/etc/rc.d/gnome respectively. So any possibly relevant preparations should be done by those scripts. I can't check those as I haven't got Gnome installed here. -- Polytropon 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 freebsd-questions-unsubscr...@freebsd.org
Re: xdm-options - non-bsd user needs bsd rc.d advice
On Thu, 03 Mar 2011 17:01:10 -0500 John D. Hendrickson and Sara Darnell johnandsa...@cox.net wrote: Hi. I'm a BSD idiot I use [Debian] linux. rc.d question I'm trying to release a project (just below) to the widest possible unix audience. I need a line in /etc/inittab and to have a start/stop in /etc/rc.d, nothing unusual I think. I read many freeBSD rc.d materials and it only convinced me as much as I'd learned: if I'm not running BSD I don't know enough to talk about it :) Usually FreeBSD rc.d scripts are maintained by the port maintainer rather than the upstream project. If you are unclear about it, I would suggest you don't bother. ___ 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: xdm-options - non-bsd user needs bsd rc.d advice
On Thu, 03 Mar 2011 17:01:10 -0500 John D. Hendrickson and Sara Darnell johnandsa...@cox.net wrote: [snip] If anyone would like to quickly comment I'd love to hear why bsd would be a better choice than ubantu (for what audience it is better). Thanks all, John ___ 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 Hi John, same with me as with Chad Perrin. Sadly, I cannot put my issue right and brief at the same time, so please excuse me being verbose. I started with Linux when being in high-school out of frustration of Windows forcing me to do things their way. After switching my entire environment to Suse Linux and after that to a version of RedHat, I quickly found out that I just switched to a different flavour of being forced to do things a certain way. When at university, I tried Gentoo Linux, learned a lot and solved problems my way. Having bought a notebook later on, I decided trying the then very much in vogue Ubuntu with a Xubuntu installation. Although satisfied with the very usable defaults, I was quickly unnerved by not being able to control things. Later, I tried OpenSolaris and FreeBSD and am now using FreeBSD due to the same reasons as Chad Perrin stated: Being a power-user, wanting to control things and (now diverting from Chad's reasons) wanting to use technology (most importantly ZFS) without being impeded for ideological reasons of viral GPLishness. So, same reasons here as with Chad Perrin, safe for an additionally and lately aquired GPL-allergy. @ Chad: Perhaps you might be happier being coerced to use a Linux with a GNU/Linux flavour like Gentoo or ArchLinux. I have never tried the latter, however, with Gentoo you are very much in control. Gentoo effectively forces you to do your own compiling via portage, so be prepared for a very long install. ArchLinux is to my knowledge binary based and might be quicker to install. Both Gentoo and ArchLinux have a reputation to put the user in charge. What drove me away from Gentoo apart from that GPL-flu was deteriorating quality of system tools. You install what is world in FreeBSD from portage in Gentoo, so when updating your portage, necessary system tools sometimes break. I was driven over the edge when some network-etc syntax changed without telling me and I lost my network connection as a result. I had something different in mind for the weekend and was just furious - so treat Gentoo with care. Cheers, -- Christopher J. Ruwe TZ GMT + 1 signature.asc Description: PGP signature
Re: xdm-options - non-bsd user needs bsd rc.d advice
On Fri, Mar 04, 2011 at 03:28:10PM +0100, Christopher J. Ruwe wrote: Later, I tried OpenSolaris and FreeBSD and am now using FreeBSD due to the same reasons as Chad Perrin stated: Being a power-user, wanting to control things and (now diverting from Chad's reasons) wanting to use technology (most importantly ZFS) without being impeded for ideological reasons of viral GPLishness. I'd say you diverted from what I satated -- though not from my reasons overall. That is actually among the reasons I prefer FreeBSD, even if I didn't mention it. So, same reasons here as with Chad Perrin, safe for an additionally and lately aquired GPL-allergy. My GPL-allergy has been around since late 2003, but has been growing in strength. 2006 was when it finally got to the point where I stopped using Linux-based systems for my own purposes until some video issues forced me back to it last month. @ Chad: Perhaps you might be happier being coerced to use a Linux with a GNU/Linux flavour like Gentoo or ArchLinux. I have never tried the latter, however, with Gentoo you are very much in control. Gentoo effectively forces you to do your own compiling via portage, so be prepared for a very long install. ArchLinux is to my knowledge binary based and might be quicker to install. Both Gentoo and ArchLinux have a reputation to put the user in charge. I'm considering ArchLinux. I've played with Gentoo in the past (2004ish), and did not much find it to my liking -- mostly because of software stability issues and a community overrun with ricers. What drove me away from Gentoo apart from that GPL-flu was deteriorating quality of system tools. You install what is world in FreeBSD from portage in Gentoo, so when updating your portage, necessary system tools sometimes break. I was driven over the edge when some network-etc syntax changed without telling me and I lost my network connection as a result. I had something different in mind for the weekend and was just furious - so treat Gentoo with care. That kind of breakage is among the reasons I didn't like Gentoo. Around that time, Debian was much more stable in practice (even Debian Testing), but things have changed in the Debian world since I last used it for my own purposes five years ago; now, it's prone to breakage as well, evidently. From your description, it sounds like Gentoo wouldn't solve the kinds of problems I'm having with Debian; it would just rearrange the deck chairs on the Titanic. I've heard Arch is a tolerable substitute for FreeBSD when you must use Linux-based systems for some reason. I'm probably going to wipe the system and reinstall this weekend to try to solve my networking issue, and Arch looks like the option I'll try -- though I'll probably check into whether OpenBSD has support for the graphics chipset in this laptop, too (I really doubt it). . . . and then, as soon as the graphics support gets sorted out in FreeBSD, I'll probably wipe again and install FreeBSD. I had FreeBSD installed on it briefly already, and everything about it worked exactly as expected except the graphics, after all. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] pgptAieZrb8Kp.pgp Description: PGP signature
Re: xdm-options - non-bsd user needs bsd rc.d advice
Readers will surely see more and more people having similar reasons why those who happily use FreeBSD do not want to go back to Linux, or even worse, Windows. I may include myself here, with the special case that I've never been a Windows user, so my mind is clean and healthy and unspoiled of MICROS~1's strange ideas of how things work. :-) On Fri, 4 Mar 2011 15:28:10 +0100, Christopher J. Ruwe c...@cruwe.de wrote: I started with Linux when being in high-school out of frustration of Windows forcing me to do things their way. In my case, it happened in school, simply because of the reason that I needed a versatile typesetting system (text, formulas, graphs) to print to a laser printer. As LaTeX was already available on Linux, I started with Slackware which was a very UNIX-like system (a positive opinion!) at that time. Later on, I did use PTS-Linux (derived from DLD, a german Linux distribution, if I remember correctly), as well as S.u.S.E.-Linux (its formal name at that time). While I found that generic UNIX knowledge was applicable everywhere, Linux knowledge was not, as you could see from file names and locations, procedures, and configuration statements which could not be transferred 1:1 between the systems. When at university, I tried Gentoo Linux, learned a lot and solved problems my way. Having bought a notebook later on, I decided trying the then very much in vogue Ubuntu with a Xubuntu installation. Although satisfied with the very usable defaults, I was quickly unnerved by not being able to control things. University was the time when I found out about FreeBSD. Having generic UNIX knowledge already (Linux, Solaris, IRIX) I could predict (!) where things are on a FreeBSD system, how they act, and what they do. This was my main reason to keep using this system, exlusively as a home desktop since version 4.0, without any disadvantages so far. I doubt that Linux would have delivered the quality I'm looking for: The quality of not being forced to abandon fully functional hardware simply because new defaults tell me I need a plentycore CPU and tenmelonhundred GB of RAM, just to keep doing the same things. As a developer, targetting Linux (as a family of operating systems) is not very easy, as they all do differ in some way. At least there is source code to consult if problems arise, but sometimes you're searching through header files to find out what *foo() is today. :-) What drove me away from Gentoo apart from that GPL-flu was deteriorating quality of system tools. You install what is world in FreeBSD from portage in Gentoo, so when updating your portage, necessary system tools sometimes break. Linux does not differentiate between the system and everything else; even the kernel can be seen as a package on the system. Along with different packaging systems, distributions differ in what packages they use to make their base system (default amount of installation). For developers, FreeBSD is an EXCELLENT operating system as it offers consistency, compatibility and interoperatbility at a good speed ratio (won't run slower after upgrading). The code quality and the availability of good documentation (man pages, handbook, FAQ), even accessible LOCALLY with no Internet connection at hand, makes it a strong partner for DURABLE solutions in software development. A friendly and intelligent community adds to the sum. The sum is SUPERIOR to what I could experience in my career. I know this is a quite general statement and doesn't help the OP in particular, but I thought it would be worth sharing it. I hope it was. :-) -- Polytropon 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 freebsd-questions-unsubscr...@freebsd.org
Re: xdm-options - non-bsd user needs bsd rc.d advice
On Fri, Mar 4, 2011 at 9:34 AM, Polytropon free...@edvax.de wrote: While I found that generic UNIX knowledge was applicable everywhere, Linux knowledge was not, as you could see from file names and locations, procedures, and configuration statements which could not be transferred 1:1 between the systems. I find that's true even going between true UNIX systems, like FreeBSD and Solaris. Maybe it was different back in the SunOS days, but modern Solaris has a lot of very Solaris-specific tools that work in opaque ways; for example, you don't edit links to /etc/init.d anymore, you create an XML service description file and use svcadm to manipulate it in some hidden database. There are still BSD-ish tools in Solaris (and GNU tools, too), but Solaris purists will strongly discourage you from using them. ___ 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: xdm-options - non-bsd user needs bsd rc.d advice
On Thu, Mar 03, 2011 at 05:01:10PM -0500, John D. Hendrickson and Sara Darnell wrote: Hi. I'm a BSD idiot I use [Debian] linux. [snip] If anyone would like to quickly comment I'd love to hear why bsd would be a better choice than ubantu (for what audience it is better). FreeBSD is definitely a better choice for *me* than Debian, or (worse yet) Ubuntu. I'm temporarily stuck in a hell of my own making, of sorts, because I installed Debian on a laptop I bought to make up for the fact that I managed to buy a laptop for which FreeBSD does not yet have complete graphics support (Intel HD video). The end result is significant annoyance. Debian, since I used it regularly about half a decade ago, has become increasingly complicated by attempts to guess what users want and provide it. This approach tends to result in making it very difficult to do things differently if you want to. Problems I'm encountering right now mostly center around networking issues -- for some asinine reason, it will connect to my WPA encrypted wireless network at home, but not to an open wireless network at a coffee shop. It makes no reasonable sense. With FreeBSD, it would be a trivial exercise to make it work. Worst-case scenario, I could just change a couple of lines in /etc/rc.d and enter the /etc/rc.d/netif restart command. On Debian, I've tried about half a dozen different approaches to getting it to connect to the coffee shop network, including more than one GUI with a seriously suboptimal interface, with no luck; it just keeps failing to get an IP address. I'm pretty sure there's some kind of automagical DWIMmery going on behind the scenes, trying to guess what I want it to do and doing it without my permission, and getting its guesses *wrong*. The upshot is this: FreeBSD is better for people who like essentially deterministic behavior out of their OSes, where the same input produces the same output, with (little or) no chance of it blowing up in your face or just stubbornly refusing to let you do what you want to do because some developer somewhere set up automagical default management based on what *he* thinks you *really* want to do. Debian to some extent, and Ubuntu to a far greater extent, is for people who don't want to know anything about what the system is doing under the hood, to the extent that if the system doesn't get it right automatically the person will refuse to actually spend any time learning enough about the system to fix the problem. Things are getting positively Microsoftish. In case you couldn't tell, I'm frustrated. I'm beginning to wonder whether having 4:3 resolution stretched out to a 16:9 aspect ratio display might be a lesser evil than using Debian, when it is even more annoying now (relative to FreeBSD) than it was five years ago. tl;dr summary: FreeBSD is power-user friendly. Linux-based systems are getting increasingly dumbed-down user obsequious, to the detriment of people who like being able to customize the system's behavior (or, y'know, actually troubleshoot it at all). -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] pgp9MT6EerY3q.pgp Description: PGP signature
Re: XDM not showing login screen
On 31/12/2010 7:07 μ.μ., Alain G. Fabry wrote: Hi, I'm trying to get my XDMCP to work, but for some reason the XDM daemon doesn't reply to XDMCP requests. I see the XDMCP packet arriving on my xdm server harley# tcpdump port 177 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on bge0, link-type EN10MB (Ethernet), capture size 96 bytes 10:33:42.930750 IP 192.168.1.200.1291 255.255.255.255.xdmcp: UDP, length 7 All seems to be running ok harley# ps ax | grep xdm 76517 ?? Ss 0:00.41 /usr/local/bin/X :0 -auth /usr/local/lib/X11/xdm/authdir/authfiles/A:0-Z5AiCR (Xorg) 76519 ?? Is 0:00.06 xdm: :0 (xdm) 6040 2 S+ 0:00.00 grep xdm 76515 5 I+ 0:00.01 xdm -nodaemon -debug 1 The XDM daemon does not reply with a login screen. I've commented out the following in my xdm-config file ! DisplayManager.requestPort: 0 following in my Xaccess file * #any host can get a login window xdm and X are running, and I see the following in my xdm.log file, even though I don't get a login screen, the log file indicates incorrect login Add a LISTEN line at the end of your Xaccess file, with the specific IP of your server rather then relying on LISTEN * I've had the same when I was setting up my XDMCP lab. ___ 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: XDM not showing login screen
On Fri, Dec 31, 2010 at 06:07:34PM +0100, Alain G. Fabry wrote:
Hi, I'm trying to get my XDMCP to work, but for some reason the XDM daemon
doesn't reply to XDMCP requests.
I see the XDMCP packet arriving on my xdm server
harley# tcpdump port 177
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on bge0, link-type EN10MB (Ethernet), capture size 96 bytes
10:33:42.930750 IP 192.168.1.200.1291 255.255.255.255.xdmcp: UDP, length 7
All seems to be running ok
harley# ps ax | grep xdm
76517 ?? Ss 0:00.41 /usr/local/bin/X :0 -auth
/usr/local/lib/X11/xdm/authdir/authfiles/A:0-Z5AiCR (Xorg)
76519 ?? Is 0:00.06 xdm: :0 (xdm)
6040 2 S+ 0:00.00 grep xdm
76515 5 I+ 0:00.01 xdm -nodaemon -debug 1
The XDM daemon does not reply with a login screen.
I've commented out the following in my xdm-config file
! DisplayManager.requestPort: 0
following in my Xaccess file
* #any host can get a login window
xdm and X are running, and I see the following in my xdm.log file, even
though I don't get a login screen, the log file indicates incorrect login
SetPrompt(1, NULL, LOGIN_PROMPT_ECHO_OFF(2))
SetPrompt(0, NULL, LOGIN_PROMPT_ECHO_ON(1))
source /usr/local/lib/X11/xdm/Xsetup_0
SetPrompt(0, NULL, LOGIN_PROMPT_NOT_SHOWN(0))
SetPrompt(1, NULL, LOGIN_PROMPT_NOT_SHOWN(0))
pam_msg: PAM_PROMPT_ECHO_ON (2): ' Login:'
SetPrompt(0,Login:, LOGIN_PROMPT_ECHO_ON(1))
RedrawFail('Login incorrect', 0)
dispatching :0
RedrawFail('Login incorrect', 0)
What more can I do to verify why it's not working, and what could be wrong.
Thanks,
Alain
not sure if it helps, I'll just describe my setup.
% grep xdm\ /etc/ttys
ttyv8 /usr/local/bin/xdmxterm off secure
% grep requestPort /usr/local/lib/X11/xdm/xdm-config
!DisplayManager.requestPort:0
% grep -v ^# /usr/local/lib/X11/xdm/Xaccess | uniq -u
aa.bb.cc.dd (these are ip addresses from which
aa.bb.cc.ee I connect to XDM server)
* # any host can get a login window
LISTEN aa.bb.cc.ff (this is the ip address of
the interface on the server
which listens for incoming
connections)
(Obviously using wildcard after specific ip addresses
makes those ip addresses unnecessary, I just
can't decide if I need to let myself access from
anywhere on campus or not).
I connect to the XDM server using
X -query aa.bb.cc.ff
Finally I think x11/xauth must be install on both
sides.
anton
--
Anton Shterenlikht
Room 2.6, Queen's Building
Mech Eng Dept
Bristol University
University Walk, Bristol BS8 1TR, UK
Tel: +44 (0)117 331 5944
Fax: +44 (0)117 929 4423
___
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: Re: xdm and xdmcp
On Thu, Jan 21, 2010 at 11:30:47PM +0200, Manolis Kiagias wrote: On 21/01/2010 8:54 μ.μ., rhin...@postmail.ch wrote: modifying Xaccess, starting xdm with parameter udpPort 177. The command netstat -a never indicates that a process is listening on that port. The notes in Xaccess seem to indicate that when a LISTEN line is not present, it works like LISTEN * I found this to be false. Please insert a LISTEN line with your IP address, i.e. LISTEN 10.14.28.10 With wdm, the listening is possible but I cannot start the X server even if the server alone is perfectly working and if it is correctly started by xdm. I don't want to use kdm or gdm since they are too heavy (almost all kde and gnome should be installed with them). Thanks, this was the correct point. I have added the LISTEN 0.0.0.0 directive in Xaccess file and it works. xdm is perfect for me, I have just tried wdm since I was not able to make xdm work like I wanted. Thanks for the help. Alain Aubord ___ 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: xdm and xdmcp
On 21/01/2010 8:54 μ.μ., rhin...@postmail.ch wrote: Hi All, Is-it possible to run xdm with remote access through XDMCP protocol on freebsd 8 ? Yes. I have an entire lab working this way :) I have tried almost anything: commenting line about port 0 in xdm-config, This is needed. modifying Xaccess, starting xdm with parameter udpPort 177. The command netstat -a never indicates that a process is listening on that port. The notes in Xaccess seem to indicate that when a LISTEN line is not present, it works like LISTEN * I found this to be false. Please insert a LISTEN line with your IP address, i.e. LISTEN 10.14.28.10 With wdm, the listening is possible but I cannot start the X server even if the server alone is perfectly working and if it is correctly started by xdm. I don't want to use kdm or gdm since they are too heavy (almost all kde and gnome should be installed with them). Same here, I use XDM for login - I don't need anything fancy. About 15 terminals running XFCE through a core2quad machine. ___ 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: xdm and xdmcp
On Thu, Jan 21, 2010 at 11:30:47PM +0200, Manolis Kiagias wrote: On 21/01/2010 8:54 ??.??., rhin...@postmail.ch wrote: Hi All, Is-it possible to run xdm with remote access through XDMCP protocol on freebsd 8 ? Yes. I have an entire lab working this way :) I have tried almost anything: commenting line about port 0 in xdm-config, This is needed. modifying Xaccess, starting xdm with parameter udpPort 177. The command netstat -a never indicates that a process is listening on that port. The notes in Xaccess seem to indicate that when a LISTEN line is not present, it works like LISTEN * I found this to be false. Please insert a LISTEN line with your IP address, i.e. LISTEN 10.14.28.10 With wdm, the listening is possible but I cannot start the X server even if the server alone is perfectly working and if it is correctly started by xdm. I don't want to use kdm or gdm since they are too heavy (almost all kde and gnome should be installed with them). Same here, I use XDM for login - I don't need anything fancy. About 15 terminals running XFCE through a core2quad machine. I'm running xdm on ia64 and connecting from sparc64, both 9.0-current, works fine. I could probably share my xdm config files, if this is useful. -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ 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: xdm freezes - 7.2-RELEASE installed
Hi, Daniel Underwood wrote: Just installed 7.2-RELEASE. After changing my /etc/ttys to default to xdm and rebooting, my machine opens xdm, but I cannot type or press enter. My keyboard isn't totally unresponsive, however, because I can Ctrl+Alt+F# to another virtual terminal. Try adding: Option AllowEmptyInput off .. to the ServerLayout section of your xorg.conf, see if that helps. See man xorg.conf too. -- Frederique ___ 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: xdm freezes - 7.2-RELEASE installed
I don't have an xorg.conf file. When I installed 7.1-RELEASE on this laptop (exact same machine) I didn't need to configure an xorg.conf file. But I'll certainly try your advice. Thanks! ___ 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: xdm freezes - 7.2-RELEASE installed
On Tue, May 5, 2009 at 2:23 PM, Daniel Underwood djuatde...@gmail.comwrote: Just installed 7.2-RELEASE. After changing my /etc/ttys to default to xdm and rebooting, my machine opens xdm, but I cannot type or press enter. My keyboard isn't totally unresponsive, however, because I can Ctrl+Alt+F# to another virtual terminal. Any ideas? Thanks, Daniel ___ 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 Could you use your mouse in xdm? I don't know if this is related; but I couldn't get my mouse to work in KDE or XFCE4 until I turned on hal. I added the following to /etc/rc.conf and rebooted: dbus_enable=YES hald_enable=YES Best of luck, Andrew ___ 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: xdm freezes - 7.2-RELEASE installed
Yep, that was it! I should have read the Handbook more thoroughly: http://www.freebsd.org/doc/en/books/handbook/x-config.html#AEN6615 ___ 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: xdm freezes - 7.2-RELEASE installed
On Tue, May 5, 2009 at 3:17 PM, Daniel Underwood djuatde...@gmail.comwrote: Yep, that was it! I should have read the Handbook more thoroughly: http://www.freebsd.org/doc/en/books/handbook/x-config.html#AEN6615 me too ;-) ___ 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: xdm freezes - 7.2-RELEASE installed
Andrew Gould wrote: On Tue, May 5, 2009 at 3:17 PM, Daniel Underwood djuatde...@gmail.comwrote: Yep, that was it! I should have read the Handbook more thoroughly: http://www.freebsd.org/doc/en/books/handbook/x-config.html#AEN6615 me too ;-) Taking this opportunity, allow me to remind to everyone that the Handbook is always work in progress and it is always useful to check again sections that you have already read, as new info is added regularly. This latest addition to the Handbook was in fact inspired by questions and info appearing on this same list :) ___ 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: xdm freezes - 7.2-RELEASE installed
On Wed, 06 May 2009 00:01:47 +0300, Manolis Kiagias son...@otenet.gr wrote: Taking this opportunity, allow me to remind to everyone that the Handbook is always work in progress and it is always useful to check again sections that you have already read, as new info is added regularly. This latest addition to the Handbook was in fact inspired by questions and info appearing on this same list :) A very polite addition of mine: It's always wise to study /usr/ports/UPDATING, a file that explains the reasons when your system suddenly went nuts. :-) -- 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 freebsd-questions-unsubscr...@freebsd.org
Re: xdm freezes - 7.2-RELEASE installed
I thought /usr/ports/UPDATING is only created when you appraise your ports with a view toward updating. I.e, after a fresh install of 7.2 (not an upgrade from 7.1), I didn't think the UPDATING file would be very helpful. ___ 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: xdm freezes - 7.2-RELEASE installed
On Tue, May 5, 2009 at 6:32 PM, Daniel Underwood djuatde...@gmail.comwrote: I thought /usr/ports/UPDATING is only created when you appraise your ports with a view toward updating. I.e, after a fresh install of 7.2 (not an upgrade from 7.1), I didn't think the UPDATING file would be very helpful. It's good, general advice. There are UPDATING files in various places for various updates, I think, including /usr/src/. It's almost as good as.(wait for it).. and always back up your data. (That one never gets old!) :-) Andrew ___ 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: xdm freezes - 7.2-RELEASE installed
Absolutely! (Sent from my iPhone) On May 5, 2009, at 7:45 PM, Andrew Gould andrewlylego...@gmail.com wrote: On Tue, May 5, 2009 at 6:32 PM, Daniel Underwood djuatde...@gmail.com wrote: I thought /usr/ports/UPDATING is only created when you appraise your ports with a view toward updating. I.e, after a fresh install of 7.2 (not an upgrade from 7.1), I didn't think the UPDATING file would be very helpful. It's good, general advice. There are UPDATING files in various places for various updates, I think, including /usr/src/. It's almost as good as.(wait for it).. and always back up your data. (That one never gets old!) :-) Andrew ___ 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: xdm freezes - 7.2-RELEASE installed
On Tue, 5 May 2009 18:45:02 -0500, Andrew Gould andrewlylego...@gmail.com wrote: It's good, general advice. There are UPDATING files in various places for various updates, I think, including /usr/src/. At least according to the history of problems with X that appeared on this list, /usr/ports/UPDATING hasn't received the attention it should. Things like the empty inputs and the crazy DBUS HAL stuff has been mentioned there. I didn't update my X yet, so I will have all this trouble in the future. :-) It's almost as good as.(wait for it).. and always back up your data. Customer: I've just done a new Word document, saved it, then accidentally deleted it. Is there anything you can do to get it back? Tech Support: Sorry, no, the backup isn't run until night time. Customer: Ohh, can we restore it tomorrow, then? :-) -- 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 freebsd-questions-unsubscr...@freebsd.org
Re: xdm freezes - 7.2-RELEASE installed
On Tue, May 5, 2009 at 7:21 PM, Polytropon free...@edvax.de wrote: On Tue, 5 May 2009 18:45:02 -0500, Andrew Gould andrewlylego...@gmail.com wrote: It's good, general advice. There are UPDATING files in various places for various updates, I think, including /usr/src/. At least according to the history of problems with X that appeared on this list, /usr/ports/UPDATING hasn't received the attention it should. Things like the empty inputs and the crazy DBUS HAL stuff has been mentioned there. I didn't update my X yet, so I will have all this trouble in the future. :-) It's almost as good as.(wait for it).. and always back up your data. Customer: I've just done a new Word document, saved it, then accidentally deleted it. Is there anything you can do to get it back? Tech Support: Sorry, no, the backup isn't run until night time. Customer: Ohh, can we restore it tomorrow, then? I'm not sure whether to laugh or cry over this one. ;-) :-) -- 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 freebsd-questions-unsubscr...@freebsd.org
Re: xdm -debug 1 = Nothing left to do, exiting
On Fri, Feb 13, 2009 at 10:13:08AM +, Anton Shterenlikht wrote: On 6.4-stable alpha I cannot get xdm to become a daemon, it exits immediately with empty /var/log/xdm.log. I tried to use -debug option, and this is the output: # xdm -debug 1 DisplayManager.errorLogFile/DisplayManager.ErrorLogFile value /var/log/xdm.log DisplayManager.daemonMode/DisplayManager.DaemonMode value true DisplayManager.pidFile/DisplayManager.PidFile value /var/run/xdm.pid DisplayManager.lockPidFile/DisplayManager.LockPidFile value true DisplayManager.authDir/DisplayManager.authDir value /usr/local/lib/X11/xdm DisplayManager.autoRescan/DisplayManager.AutoRescan value true DisplayManager.removeDomainname/DisplayManager.RemoveDomainname value true DisplayManager.keyFile/DisplayManager.KeyFile value /usr/local/lib/X11/xdm/xdm- keys DisplayManager.accessFile/DisplayManager.AccessFile value /usr/local/lib/X11/xd m/Xaccess DisplayManager.exportList/DisplayManager.ExportList value DisplayManager.randomDevice/DisplayManager.RandomDevice value /dev/urandom DisplayManager.greeterLib/DisplayManager.GreeterLib value /usr/local/lib/X11/xdm /libXdmGreet.so DisplayManager.choiceTimeout/DisplayManager.ChoiceTimeout value 15 DisplayManager.sourceAddress/DisplayManager.SourceAddress value false DisplayManager.willing/DisplayManager.Willing value su -m nobody -c /usr/local/ lib/X11/xdm/Xwilling Nothing left to do, exiting # Looking at xdm -debug .. logs on the net it seems the next line after the Willing should be creating socket 177 Perhaps xdm exits because it cannot create socket 177? Is that plausible? How can I test this? many thanks anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 928 8233 Fax: +44 (0)117 929 4423 ___ 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
SOLVED: Re: xdm -debug 1 = Nothing left to do, exiting
On Tue, Feb 17, 2009 at 04:30:49PM +, Anton Shterenlikht wrote: On Fri, Feb 13, 2009 at 10:13:08AM +, Anton Shterenlikht wrote: On 6.4-stable alpha I cannot get xdm to become a daemon, it exits immediately with empty /var/log/xdm.log. I tried to use -debug option, and this is the output: # xdm -debug 1 DisplayManager.errorLogFile/DisplayManager.ErrorLogFile value /var/log/xdm.log DisplayManager.daemonMode/DisplayManager.DaemonMode value true DisplayManager.pidFile/DisplayManager.PidFile value /var/run/xdm.pid DisplayManager.lockPidFile/DisplayManager.LockPidFile value true DisplayManager.authDir/DisplayManager.authDir value /usr/local/lib/X11/xdm DisplayManager.autoRescan/DisplayManager.AutoRescan value true DisplayManager.removeDomainname/DisplayManager.RemoveDomainname value true DisplayManager.keyFile/DisplayManager.KeyFile value /usr/local/lib/X11/xdm/xdm- keys DisplayManager.accessFile/DisplayManager.AccessFile value /usr/local/lib/X11/xd m/Xaccess DisplayManager.exportList/DisplayManager.ExportList value DisplayManager.randomDevice/DisplayManager.RandomDevice value /dev/urandom DisplayManager.greeterLib/DisplayManager.GreeterLib value /usr/local/lib/X11/xdm /libXdmGreet.so DisplayManager.choiceTimeout/DisplayManager.ChoiceTimeout value 15 DisplayManager.sourceAddress/DisplayManager.SourceAddress value false DisplayManager.willing/DisplayManager.Willing value su -m nobody -c /usr/local/ lib/X11/xdm/Xwilling Nothing left to do, exiting # Looking at xdm -debug .. logs on the net it seems the next line after the Willing should be creating socket 177 Perhaps xdm exits because it cannot create socket 177? Is that plausible? How can I test this? I think the xdm-config file got overwritten during the port upgrade with the default (secure?) settings. I had to comment out the last setting in xdm-config % tail -3 /usr/local/lib/X11/xdm/xdm-config ! SECURITY: do not listen for XDMCP or Chooser requests ! Comment out this line if you want to manage X terminals with xdm !DisplayManager.requestPort:0 % now seems to be working fine. -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 928 8233 Fax: +44 (0)117 929 4423 ___ 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: SOLVED: Re: xdm -debug 1 = Nothing left to do, exiting
On Tue, 17 Feb 2009, Anton Shterenlikht wrote: I think the xdm-config file got overwritten during the port upgrade with the default (secure?) settings. I had to comment out the last setting in xdm-config % tail -3 /usr/local/lib/X11/xdm/xdm-config ! SECURITY: do not listen for XDMCP or Chooser requests ! Comment out this line if you want to manage X terminals with xdm !DisplayManager.requestPort:0 % now seems to be working fine. That line is present here, and xdm works. From /etc/ttys and on localhost, anyway, don't have any X terminals. 'xhost +localhost' is in the user .xsession before X startup, but no other changes I can recall. -Warren Block * Rapid City, South Dakota USA ___ 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: XDM login freezes on boot
On Wed, Feb 11, 2009 at 08:32:20PM +1000, Warren Liddell wrote: AMD64 4gig RAM FreeBSD 7.1 KDE 4.2 I've noticed of late when i have had the misfortune of rebooting this machine due to severre storms and blackouts, when it boots everything loads fine, xdm initates an i get the standard logon screen, however, you cant do anything an the mouse dosent work. To solve this issue i go to console via CTRL + ALT + F1 kill tthe XDM pid an once it comes back up, everything is perfectly fine. Anyone else had this odd occurance ? no, but what I see is that xdm exits immediately. I just cannot get the daemon to run. This is on 6.4-stable alpha with xdm-1.1.8_1 -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 928 8233 Fax: +44 (0)117 929 4423 ___ 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: XDM login freezes on boot
On Wed, 2009-02-11 at 20:32 +1000, Warren Liddell wrote: AMD64 4gig RAM FreeBSD 7.1 KDE 4.2 I've noticed of late when i have had the misfortune of rebooting this machine due to severre storms and blackouts, when it boots everything loads fine, xdm initates an i get the standard logon screen, however, you cant do anything an the mouse dosent work. To solve this issue i go to console via CTRL + ALT + F1 kill tthe XDM pid an once it comes back up, everything is perfectly fine. Anyone else had this odd occurance ? Sounds like hald is starting after ttys is initiated. There's another thread here mentioning that- never read the answer though. Maybe start hald at the beginning of your rc.conf? Or set a sleep on your tty entry for x? ___ 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: XDM login freezes on boot
On Wed, Feb 11, 2009 at 08:49:51PM +1000, Da Rock wrote: On Wed, 2009-02-11 at 20:32 +1000, Warren Liddell wrote: AMD64 4gig RAM FreeBSD 7.1 KDE 4.2 I've noticed of late when i have had the misfortune of rebooting this machine due to severre storms and blackouts, when it boots everything loads fine, xdm initates an i get the standard logon screen, however, you cant do anything an the mouse dosent work. To solve this issue i go to console via CTRL + ALT + F1 kill tthe XDM pid an once it comes back up, everything is perfectly fine. Anyone else had this odd occurance ? Sounds like hald is starting after ttys is initiated. There's another thread here mentioning that- never read the answer though. Maybe start hald at the beginning of your rc.conf? Or set a sleep on your tty entry for x? I think there is a lack of understanding here of how exactly hal, dbus and xorg are interrelated. There are some pages on freebsd.org, but at least for me these didn't make it any clearer. The man pages aren't helpful either. They tell you how to do things, but there is not much on why. I'd like to have a better idea of 0. how do hal, dbus, xorg-server, xdm and clients interoperate? 1. why do I need hal and dbus? 2. where do I need to run hal and dbus daemons, on the X server side, on the clients side, or on both? In my case these are different systems, I rely on XDMCP). 3. what happens if hal support is not built into xorg-server? 4. why is the issue of auto keyboard and mouse detection still not clear, contrary to the statement in ports/UPDATE? Cleary something changes from 7.3 to 7.4 that gives all sorts of troubles to many people on different systems. If these questions have been answered already please point me to a link. anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 928 8233 Fax: +44 (0)117 929 4423 ___ 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: XDM login freezes on boot
On Wed, 11 Feb 2009, Warren Liddell wrote: AMD64 4gig RAM FreeBSD 7.1 KDE 4.2 I've noticed of late when i have had the misfortune of rebooting this machine due to severre storms and blackouts, when it boots everything loads fine, xdm initates an i get the standard logon screen, however, you cant do anything an the mouse dosent work. To solve this issue i go to console via CTRL + ALT + F1 kill tthe XDM pid an once it comes back up, everything is perfectly fine. Anyone else had this odd occurance ? Yes, up until the latest xorg-server update on Sunday (xorg-server-1.5.3_5,1). Now it works great. -Warren Block * Rapid City, South Dakota USA ___ 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: XDM login freezes on boot
On Wed, 11 Feb 2009, Da Rock wrote: On Wed, 2009-02-11 at 20:32 +1000, Warren Liddell wrote: AMD64 4gig RAM FreeBSD 7.1 KDE 4.2 I've noticed of late when i have had the misfortune of rebooting this machine due to severre storms and blackouts, when it boots everything loads fine, xdm initates an i get the standard logon screen, however, you cant do anything an the mouse dosent work. To solve this issue i go to console via CTRL + ALT + F1 kill tthe XDM pid an once it comes back up, everything is perfectly fine. Anyone else had this odd occurance ? Sounds like hald is starting after ttys is initiated. There's another thread here mentioning that- never read the answer though. Maybe start hald at the beginning of your rc.conf? Or set a sleep on your tty entry for x? rc.conf just sets variables; it's not order-sensitive. If xorg-server-1.5.3_5,1 along with all the previous patches doesn't fix the problem, then delaying xdm startup might be the way to go. -Warren Block * Rapid City, South Dakota USA ___ 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: xdm doesn't run as daemon
On Fri, Feb 06, 2009 at 09:39:23PM +0100, Roger Olofsson wrote: Anton Shterenlikht skrev: After upgrades of 23-24 Jan 2009 xdm is not working: # xdm # ps ax|grep xdm 75632 p1 S+ 0:00.01 grep xdm # cat /var/log/xdm.log # So no xdm daemon. My system: FreeBSD 6.4-STABLE alpha, xdm-1.1.8_1. Any ideas? Hi Anton, Tried detaching it? xdm It terminates straight away # xdm [1] 82938 # [1]Done xdm # with empty /var/log/xdm.log Perhaps I should check which libraries xdm is built with and try to rebuild those? But I think I've done this already. thanks anyway anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 928 8233 Fax: +44 (0)117 929 4423 ___ 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: xdm doesn't run as daemon
Anton Shterenlikht skrev: After upgrades of 23-24 Jan 2009 xdm is not working: # xdm # ps ax|grep xdm 75632 p1 S+ 0:00.01 grep xdm # cat /var/log/xdm.log # So no xdm daemon. My system: FreeBSD 6.4-STABLE alpha, xdm-1.1.8_1. Any ideas? No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.0.233 / Virus Database: 270.10.18/1935 - Release Date: 02/02/09 19:21:00 Hi Anton, Tried detaching it? xdm /R ___ 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: xdm doesn't run as daemon
On Thu, Feb 05, 2009 at 08:01:25AM -0500, Robert Huff wrote: Anton Shterenlikht writes: After upgrades of 23-24 Jan 2009 xdm is not working: # xdm # ps ax|grep xdm 75632 p1 S+ 0:00.01 grep xdm # cat /var/log/xdm.log Any ideas? 1) May we see /var/log/Xorg.0.log? 2) Does startx work? This is a headless box, I don't run X server on it. I connect to it via XDMCP and run clients. So I've neither /var/log/Xorg.0.log nor startx on this box. It worked fine until the upgrade. I'm now thoroughtly confused by dbus and hal issues. So in case it matters I run neither hald nor dbus-daemon on this box. many thanks anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 928 8233 Fax: +44 (0)117 929 4423 ___ 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: xdm woes
pushing aqnd releasing the power button, so the OS shuts down using ACPI). This happens every time. No matter what window manager I use. But it only happens when I use xdm. If I start X with startx, it shuts down cleanly and returns to the tty from which I ran startx. how you start xdm? from ttys or manually? strange - anyway ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xdm woes
Wojciech Puchar wrote: pushing aqnd releasing the power button, so the OS shuts down using ACPI). This happens every time. No matter what window manager I use. But it only happens when I use xdm. If I start X with startx, it shuts down cleanly and returns to the tty from which I ran startx. how you start xdm? from ttys or manually? strange - anyway I've started it from ttys a few times, but I gave up after a few days. Since then I've tried starting it manually (both with and without the -nodaemon option) every time I've upgraded something related to either the system or X. Last time a few hours ago, just before I wrote my original mail about this, after upgrading xorg-server from 1.4_2,1 to 1.4_3,1. -- Sincerly, Rolf Nielsen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xdm fails! can't find pcidata
On Thu, Aug 23, 2007 at 12:16:10AM +0400, Boris Samorodov wrote: On Wed, 22 Aug 2007 12:11:47 -0700 Gary Kline wrote: I just rebooted my DNS server and now X fails. I'm pretty sure I did everything re the xorg instructions in UPDATING. The error message in /var/lob/Xorg.0.log says exactly:: (II) Loader running on freebsd (II) LoadModule: pcidata (WW) Warning, couldn't open module pcidata (II) UnloadModule: pcidata (EE) Failed to load module pcidata (module does not exist, 0) How can I fix this? I find pcidata deep in the /usr/sys/src.../dev directory. Nothing in my KERNCONF=GENERIC file. Insights, anybody?? I've seen something like this after Xorg-6.9 to Xorg-7.1 update. Seems that I succeeded after deletting my old xorg.conf file, creating a new one and fitting it. Yeah, you're right; creating a new one would have been the most logical thing. But at least I learned that the modules have been moved to /usr/local/lib/xorg/modules. I did a wholesale 1,$s/X11R6/local/gp and that failed because the old path was /usr/X11R6/lib/modules. I'll know if this works in the morning localtime. My brain is fried. cheers, gary WBR -- bsam -- Gary Kline [EMAIL PROTECTED] www.thought.org Public Service Unix ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xdm fails! can't find pcidata
On Wed, Aug 22, 2007 at 12:11:47PM -0700, Gary Kline wrote: I just rebooted my DNS server and now X fails. I'm pretty sure I did everything re the xorg instructions in UPDATING. The error message in /var/lob/Xorg.0.log says exactly:: (II) Loader running on freebsd (II) LoadModule: pcidata (WW) Warning, couldn't open module pcidata (II) UnloadModule: pcidata (EE) Failed to load module pcidata (module does not exist, 0) How can I fix this? I find pcidata deep in the /usr/sys/src.../dev directory. Nothing in my KERNCONF=GENERIC file. Insights, anybody?? tia, gary -- Gary Kline [EMAIL PROTECTED] www.thought.org Public Service Unix Could you show us what is your ModulePath set to? (either from xorg.conf or from Xorg.0.log, should be /usr/local/lib/xorg/modules). Yuri ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xdm fails! can't find pcidata
On Wed, 22 Aug 2007 12:11:47 -0700 Gary Kline wrote: I just rebooted my DNS server and now X fails. I'm pretty sure I did everything re the xorg instructions in UPDATING. The error message in /var/lob/Xorg.0.log says exactly:: (II) Loader running on freebsd (II) LoadModule: pcidata (WW) Warning, couldn't open module pcidata (II) UnloadModule: pcidata (EE) Failed to load module pcidata (module does not exist, 0) How can I fix this? I find pcidata deep in the /usr/sys/src.../dev directory. Nothing in my KERNCONF=GENERIC file. Insights, anybody?? I've seen something like this after Xorg-6.9 to Xorg-7.1 update. Seems that I succeeded after deletting my old xorg.conf file, creating a new one and fitting it. WBR -- bsam ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: XDM Logon
Korn, Karl [EMAIL PROTECTED] writes: I have a fresh installed version of BSD 5.4 loaded onto a machine and when I attempt to logon using XDM it will not log me in. I'm using the correct credentials and it looks as if I'm being let into the system but the logon screen comes back up. Any ideas? This almost always mean that you have a problem with your .xsession file. [It's not executable, or it returns too quickly, etc.] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Xdm Securelevels revisited
On Friday 28 January 2005 01:13, markzero wrote: securelevel is raised before xdm can start which causes fireworks. just a thought: if you raise the securelevel after xdm has started and it dies, would you get fireworks again? -- /Xian Common sense is the collection of prejudices acquired by age eighteen. Albert Einstein ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Xdm Securelevels revisited
securelevel is raised before xdm can start which causes fireworks. just a thought: if you raise the securelevel after xdm has started and it dies, would you get fireworks again? I'm leaving the text consoles open for that very reason. If xdm dies, tries to restart (it will try every 30 seconds as init will sleep) I can drop to single user and disable xdm. The only problem with this is that I won't then be able to get X back without rebooting to securelevel -1. Correct me if I am wrong but all the documentation seems to suggest that the securelevel cannot be lowered even in single user mode? I am relying on xdm to be stable, which it does seem to be (I have used it at the default securelevel on other machines). -- PGP: http://www.darklogik.org/pub/pgp/pgp.txt B776 43DC 8A5D EAF9 2126 9A67 A7DA 390F DEFF 9DD1 pgph5xJLQOWE8.pgp Description: PGP signature
Re: xdm background ?
On Mon, 18 Oct 2004 00:32:05 +0200, h [EMAIL PROTECTED] wrote: how do you add a background picture to xdm ? so far i tried xli and xv in /usr/X11R6/lib/X11/xdm/Xsetup_0, both don't allow the login box to pop up. Add the -quit switch to xv to have it exit after setting the root window's image. -- Conrad J. Sabatier [EMAIL PROTECTED] -- In Unix veritas ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xdm background ?
that displays the picture until i press a key, then displays the login box with the awful black and white frame in the background. i'm trying to display the picture in the background of the login box and console log, and have it displayed until my wm shows up, kde style. how do i achieve this ? On Monday 18 October 2004 01:11, Conrad J. Sabatier wrote: On Mon, 18 Oct 2004 00:32:05 +0200, h [EMAIL PROTECTED] wrote: how do you add a background picture to xdm ? so far i tried xli and xv in /usr/X11R6/lib/X11/xdm/Xsetup_0, both don't allow the login box to pop up. Add the -quit switch to xv to have it exit after setting the root window's image. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xdm background ?
On Mon, 18 Oct 2004 01:30:24 +0200, h [EMAIL PROTECTED] wrote: that displays the picture until i press a key, then displays the login box with the awful black and white frame in the background. i'm trying to display the picture in the background of the login box and console log, and have it displayed until my wm shows up, kde style. how do i achieve this ? Perhaps you /should/ try installing kdm or gdm? It is very easy for kdm (which I use often) to have a background selected. -- If I write a signature, my emails will appear more personalised. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xdm background ?
On Mon, 18 Oct 2004 01:30:24 +0200, h [EMAIL PROTECTED] wrote: that displays the picture until i press a key, then displays the login box with the awful black and white frame in the background. i'm trying to display the picture in the background of the login box and console log, and have it displayed until my wm shows up, kde style. how do i achieve this ? Are you using the -root switch as well with xv? On Monday 18 October 2004 01:11, Conrad J. Sabatier wrote: On Mon, 18 Oct 2004 00:32:05 +0200, h [EMAIL PROTECTED] wrote: how do you add a background picture to xdm ? so far i tried xli and xv in /usr/X11R6/lib/X11/xdm/Xsetup_0, both don't allow the login box to pop up. Add the -quit switch to xv to have it exit after setting the root window's image. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Conrad J. Sabatier [EMAIL PROTECTED] -- In Unix veritas ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xdm background ?
On Monday 18 October 2004 03:32, Conrad J. Sabatier wrote: i'm trying to display the picture in the background of the login box and console log, and have it displayed until my wm shows up, kde style. how do i achieve this ? Are you using the -root switch as well with xv? thanks, that kind of fixed it. the correct syntax is: xv /home/bla/some_pic.jpg -root -quit ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xdm
Le 11/02/2004 à 15:51:55+0100, Christer Solskogen a écrit Is it possible to configure XDM so it wont run localy? like, X does not start on the machine running it. Modify the file /usr/X11R6/lib/X11/xdm/Xservers and make comment the line #:0 local /usr/X11R6/bin/X Regards. -- Albert SHIH Universite de Paris 7 (Denis DIDEROT) Heure local/Local time: Wed Feb 11 16:07:07 CET 2004 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Xdm/Kdm/Gmd
On Thursday 04 December 2003 01:07 pm, Payne wrote: Hi, Thanks for the help early, I am wanting to have either xdm/kdm/gdm to start once my system it up, how can I do this? Also which is best? http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-xdm.html This will detail the process for you. As to which is best, that's only valid if you are running Gnome AND KDE. I'm not familiar with gdm, but kdm is bundled w/ KDE, and xdm is bundled w/ XFree86. -- Thanks, Charles http://howse.homeunix.net:8080 Random Murphy's Law: An easily-understood, workable falsehood is more useful than a complex, incompreshensible truth. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Xdm/Kdm/Gmd
Charles Howse wrote: On Thursday 04 December 2003 01:07 pm, Payne wrote: Hi, Thanks for the help early, I am wanting to have either xdm/kdm/gdm to start once my system it up, how can I do this? Also which is best? http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-xdm.html This will detail the process for you. As to which is best, that's only valid if you are running Gnome AND KDE. I'm not familiar with gdm, but kdm is bundled w/ KDE, and xdm is bundled w/ XFree86. Thanks, I have printed out the mannual so I will take a look at. GMD = Gnome, I am old linux guy and I like kdm, I was hoping there was a wdm port, it suppose to be the best. Oh well. Payne ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Xdm/Kdm/Gmd
On Thursday 04 December 2003 02:39 pm, Payne wrote: Charles Howse wrote: On Thursday 04 December 2003 01:07 pm, Payne wrote: Hi, Thanks for the help early, I am wanting to have either xdm/kdm/gdm to start once my system it up, how can I do this? Also which is best? http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-xdm.html This will detail the process for you. As to which is best, that's only valid if you are running Gnome AND KDE. I'm not familiar with gdm, but kdm is bundled w/ KDE, and xdm is bundled w/ XFree86. Thanks, I have printed out the mannual so I will take a look at. GMD = Gnome, I am old linux guy and I like kdm, I was hoping there was a wdm port, it suppose to be the best. Oh well. [EMAIL PROTECTED] /usr/ports]$ make search key=wdm [snip] Port: wdm-1.25_1 Path: /usr/ports/x11/wdm Info: WINGs Display Manager; an xdm replacement Maint: [EMAIL PROTECTED] Index: x11 windowmaker B-deps: Hermes-1.3.3 XFree86-libraries-4.3.0_6 expat-1.95.6_1 fontconfig-2.2.90_3 freetype2-2.1.5_1 gettext-0.12.1 imake-4.3.0_1 jpeg-6b_1 libiconv-1.9.1_3 libungif-4.1.0b1_1 pkgconfig-0.15.0 png-1.2.5_2 tiff-3.6.0 windowmaker-0.80.2_1 wmicons-1.0 R-deps: Hermes-1.3.3 XFree86-libraries-4.3.0_6 expat-1.95.6_1 fontconfig-2.2.90_3 freetype2-2.1.5_1 gettext-0.12.1 imake-4.3.0_1 jpeg-6b_1 libiconv-1.9.1_3 libungif-4.1.0b1_1 pkgconfig-0.15.0 png-1.2.5_2 tiff-3.6.0 windowmaker-0.80.2_1 wmicons-1.0 -- Thanks, Charles http://howse.homeunix.net:8080 Random Murphy's Law: If you buy bananas or avocados before they are ripe, there won't be any left by the time they are ripe. If you buy them ripe, they rot before they are eaten. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xdm config files overwritten after upgrading Xfree86-clients from ports
Matthew Seaman wrote: On Fri, Sep 05, 2003 at 01:45:03PM +0200, Heinrich Rebehn wrote: Matthew Seaman wrote: However, I just keep a backup copy of the /usr/X11R6/lib/X11/xdm directory handy: # cd /usr/X11R6/lib/X11/ # rsync -avx --delete xdm/ xdm.bak/ Cheers, Matthew Ok, this would help for xdm. I wonder however, how many other packages are out there with similar behaviour and what other directories i should have a copy of handy. Or, to put it this way: I would like a port/package system that i can rely on :-) In practice, this really doesn't bite port/package users very often. The Porter's Handbook states: If your port requires some configuration files in PREFIX/etc, do not just install them and list them in pkg-plist. That will cause pkg_delete to delete files carefully edited by the user and a new installation to wipe them out. Instead, install sample files with a suffix (filename.sample will work well) and print out a message pointing out that the user has to copy and edit the file before the software can be made to work. (http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/dads-config.html) I filed a pr against XFree86-clients. See what happens... which perhaps should be generalized to configuration files installed anywhere, rather than just under PREFIX/etc. Of all the ports I have installed, which is several hundred encorporating general desktop usage, web serving, databases, etc., the only ones I've had problems with regarding trashing my original configuration files are XFree86-4-clients and the Horde, Imp, Turba etc. group of web apps. (These last, to be fair, always preserve my config files as filename.previous and updates do tend to involve non-compatible changes to the configuration file contents.) This is good to hear. Otherwise i would have considered moving to Debian/Linux. :-) The only other Gotcha! of this type is when a /usr/local/etc/rc.d startup script gets changed to the new rc.subr(8) style. Previously those scripts were generally held to be configurable files and you had to copy the sample file into place, edit it and make sure it was executable before the service would be set up to auto-start on reboot. With the new rc_subr style, the script doesn't need to be edited, but you generally have to add some lines to /etc/rc.conf to enable the service. Cheers, Matthew Cheers, Heinrich ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xdm config files overwritten after upgrading Xfree86-clients from ports
On Fri, Sep 05, 2003 at 12:59:38PM +0200, Heinrich Rebehn wrote: Hi lists, I upgraded Xfree86-clients from ports using portupgrade today and noticed that xdm was no longer working afterwards. After some searching i found that the config files in /usr/X11R6/lib/X11/xdm had been overwritten. Since i had a similar problem with another port the other day, i want to ask: - Is this expected behaviour? - Should i manually inspect my config files after each portupgrade? - Or is this just a bug in XFree86-clients (and possibly some other ports)? Luckily, my changes to the config files were only minor, so i did not have to restore them from tape :-) Anyway it's annoying.. Yes, I've been bitten by this in the past. In theory you can avoid re-installing the xdm config files by: % make install InstallXdmConfig=NO or by adding that variable to the MAKE_ARGS array in /usr/local/etc/pkgtools.conf is you're a portupgrade(1) user. However, I just keep a backup copy of the /usr/X11R6/lib/X11/xdm directory handy: # cd /usr/X11R6/lib/X11/ # rsync -avx --delete xdm/ xdm.bak/ Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp0.pgp Description: PGP signature
Re: xdm config files overwritten after upgrading Xfree86-clients from ports
Good Morning Heinrich. Yes, that's pretty much expected behaviour. Each port is different in the way that it treats it's configuration files. Some of them will have a file.config.sample that you usually copy over to file.config and modify. That way you don't lose your changes, but you can see if there are any new options you may want. As you found out, XFree86 (and related ones), don't do this (except for your XF86Config, which lives in /etc/X11). Each port has a file pkg_plist that usually lists the files it contains. Another way to find out is to use (before you delete the old one): portversion -v ( to get the full name of the package) pkg_info -L pkg_name to list the files it contains One thing you may want to consider: rcs is part of the default system. It doesn't take much to setup and keep track of changes you make to files like that. I do it everytime I make changes to my local config files, even .tcshrc and .emacs. It makes it easy to back track when you really screw up :) When you start to worry what other people think of you, it's time to go fishing ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xdm config files overwritten after upgrading Xfree86-clients from ports
Matthew Seaman wrote: On Fri, Sep 05, 2003 at 12:59:38PM +0200, Heinrich Rebehn wrote: Hi lists, I upgraded Xfree86-clients from ports using portupgrade today and noticed that xdm was no longer working afterwards. After some searching i found that the config files in /usr/X11R6/lib/X11/xdm had been overwritten. Since i had a similar problem with another port the other day, i want to ask: - Is this expected behaviour? - Should i manually inspect my config files after each portupgrade? - Or is this just a bug in XFree86-clients (and possibly some other ports)? Luckily, my changes to the config files were only minor, so i did not have to restore them from tape :-) Anyway it's annoying.. Yes, I've been bitten by this in the past. In theory you can avoid re-installing the xdm config files by: % make install InstallXdmConfig=NO or by adding that variable to the MAKE_ARGS array in /usr/local/etc/pkgtools.conf is you're a portupgrade(1) user. However, I just keep a backup copy of the /usr/X11R6/lib/X11/xdm directory handy: # cd /usr/X11R6/lib/X11/ # rsync -avx --delete xdm/ xdm.bak/ Cheers, Matthew Ok, this would help for xdm. I wonder however, how many other packages are out there with similar behaviour and what other directories i should have a copy of handy. Or, to put it this way: I would like a port/package system that i can rely on :-) - Heinrich ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xdm config files overwritten after upgrading Xfree86-clients from ports
On Fri, Sep 05, 2003 at 01:45:03PM +0200, Heinrich Rebehn wrote: Matthew Seaman wrote: However, I just keep a backup copy of the /usr/X11R6/lib/X11/xdm directory handy: # cd /usr/X11R6/lib/X11/ # rsync -avx --delete xdm/ xdm.bak/ Cheers, Matthew Ok, this would help for xdm. I wonder however, how many other packages are out there with similar behaviour and what other directories i should have a copy of handy. Or, to put it this way: I would like a port/package system that i can rely on :-) In practice, this really doesn't bite port/package users very often. The Porter's Handbook states: If your port requires some configuration files in PREFIX/etc, do not just install them and list them in pkg-plist. That will cause pkg_delete to delete files carefully edited by the user and a new installation to wipe them out. Instead, install sample files with a suffix (filename.sample will work well) and print out a message pointing out that the user has to copy and edit the file before the software can be made to work. (http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/dads-config.html) which perhaps should be generalized to configuration files installed anywhere, rather than just under PREFIX/etc. Of all the ports I have installed, which is several hundred encorporating general desktop usage, web serving, databases, etc., the only ones I've had problems with regarding trashing my original configuration files are XFree86-4-clients and the Horde, Imp, Turba etc. group of web apps. (These last, to be fair, always preserve my config files as filename.previous and updates do tend to involve non-compatible changes to the configuration file contents.) The only other Gotcha! of this type is when a /usr/local/etc/rc.d startup script gets changed to the new rc.subr(8) style. Previously those scripts were generally held to be configurable files and you had to copy the sample file into place, edit it and make sure it was executable before the service would be set up to auto-start on reboot. With the new rc_subr style, the script doesn't need to be edited, but you generally have to add some lines to /etc/rc.conf to enable the service. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp0.pgp Description: PGP signature
Re: XDM
After problems with GDM after updating to latest XFree86 et al, I am using XDM as a temporary solution. However, I have a xconsole window continuously open...Is there a way I can remove this? Not even sure if it needs to stay open or not... You can turn this off by commenting the line in /usr/X11R6/lib/X11/xdm/Xsession_0 I don't have the file available here so i can't provide you with the exact line to comment, but this should make it able to you to find the solution yourself. Marcel To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: XDM on multiple virutal X screens ( ALT-F9,ALT-F10...)
Hi, On Fri, Feb 28, 2003 at 10:09:24AM +1030, Malcolm Kay wrote: Noticed this, out of curiosity decided to try it. OK. This list is a good place to lurk on and read the topics that find intresting. Then forgot second X display was installed and next time the machine was started did not enter ALT-F10. Then on: $ shutdown -h now the machine hung with some complaint from fetchmail which I have running as a daemon. Only response was from the power switch. On rebooting and waiting for fsck the sam sequence of events recurred. Disabled second X display and problem disappeared. Coincidence? Seems unlikely! Had nothing to do with fetchmail? Possible. I don't know but properbly not but I have notice that Nvidias own drivers does not seem to like more than one X display. If i change between my virtual xdm screens then xdm trys to start again and again. But at least one virtual xdm login screen the one that I first log on to. Offcourse I want to too work but It does not seem to function to one hundred procent. I have get it working one time but then when I loged out on the one of the virtual xdm screens that one died. But Im thinkning of changing back to X own nvidia drivers because they seem to be more stable for me. And the do not crash the hole system. But then I can't get movies of getting fast enought to watch but perhaps its only an config error or using the right video output. I also have to use software rendring for GL/glx etc and that is not fast. Mvh Mattias Björk To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: XDM on multiple virutal X screens ( ALT-F9,ALT-F10...)
Hi, Adding the other entry to XServers does not have anything to do with running it on multiple monitors. There are three connectivity sections to every X window. Adding a line to Xservers (to my knowlege) does not have anything to do with running on two different monitors in a dual-head'd configuration. A second monitor/display would show up as :0.1, :1.1, etc. A third monitor would be :0.2 or :1.2, etc. Also note that the lack of a host name tells the X-Windows system to find the best way of communicating with the localhost. There are several other ways of communicating with the X-Server including UNIX sockets, IPX, etc. A simple way to remember it is Hostname:Window:Screen. Okej, I will try to remember that one should not be that hard. Thanks. Mvh Mattias Björk To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: XDM on multiple virutal X screens ( ALT-F9,ALT-F10...)
On Wed, Feb 26, 2003 at 06:03:50AM -0800, Aaron Burke wrote: This is the only file that you have to modify, however you need to make two seperate mods. The default file just says :0 local /usr/X11R6/bin/X Just change it to say the following. :0 local /usr/X11R6/bin/X :0 :1 local /usr/X11R6/bin/X :1 The only line that is in there is :0 local /usr/X11R6/bin/X Okej, then I almost did right. You have searched well enough. I remember playing with this for about a week in the past. (when I first got it working). Its amazing how easy the change is to make though. Perhaps folk does not like to run it for some reasons. But If i want it to get it running on diffrent screens I have to edit /usr/X11R6/lib/X11/XF86Config I guess and add the other graphic card there, and so forth. This is an unrelated problem. Feel free to ask about it on -questions though. I thinking of it. You should always be able to ssh into your box (provided your running the server, and you are). I know I do that, but the computer real crashes hard. Nothing to do there. Okie dokie Anyway thanks for reading and perhaps replying to this mail :) Thats what some of us are here for. I might not answer any mails on the list but I help my friends IRL istead. But I don't know that many IRL that runs FreeBSD. Any way this is getting of topic. Expect me to write more mail on other subjects. Mvh Mattias Bj?rk To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: XDM on multiple virutal X screens ( ALT-F9,ALT-F10...)
(snip) You have searched well enough. I remember playing with this for about a week in the past. (when I first got it working). Its amazing how easy the change is to make though. There are a few good reasons I can think of. Simply running an other instance of X-Windows takes up more resources. Most just run virtual-desktops to get around problems like this. Perhaps folk does not like to run it for some reasons. But If i want it to get it running on diffrent screens I have to edit /usr/X11R6/lib/X11/XF86Config I guess and add the other graphic card there, and so forth. Adding the other entry to XServers does not have anything to do with running it on multiple monitors. There are three connectivity sections to every X window. Adding a line to Xservers (to my knowlege) does not have anything to do with running on two different monitors in a dual-head'd configuration. A second monitor/display would show up as :0.1, :1.1, etc. A third monitor would be :0.2 or :1.2, etc. Also note that the lack of a host name tells the X-Windows system to find the best way of communicating with the localhost. There are several other ways of communicating with the X-Server including UNIX sockets, IPX, etc. A simple way to remember it is Hostname:Window:Screen. (snip) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: xdm across different networks
Glenn, I'm not 100% certain, but the X11 servers on your xxx.xxx.86.0 subnet my be relying upon XDMCP broadcasts to locate the FreeBSD machine on the same subnet. Broadcasts cannot be routed between subnets and therefore your Windows XP system on your xxx.xxx.87.0 subnet won't be responded to by your FreeBSD machine. Rather than using broadcasts, you should be able to configure the X11 server software on your Windows XP system to do a direct XDMCP query of the FreeBSD system by specifying it's hostname or IP address. Because a specific IP address is used the XDMCP query will properly traverse the subnets to establish an X11 session. Mike Thompson At 01:23 PM 2/6/03 -0600, Glenn Johnson wrote: I have a Windows XP machine at work that I am trying to get an X11 server to connect to a FreeBSD machine. The FreeBSD machine is on the xxx.xxx.86.0 network and the Windows XP machine is on the xxx.xxx.87.0 network. X11 servers on other machines on the xxx.xxx.86.0 network work fine with xdmcp. Is there some restriction on xdmcp to being on the same network or do I have to add some kind of special routing entry to handle this? Thanks. -- Glenn Johnson USDA, ARS, SRRC Phone: (504) 286-4252 New Orleans, LA 70124 e-mail: [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: xdm across different networks
On Thu, Feb 06, 2003 at 02:21:08PM -0800, Mike Thompson wrote: Glenn, I'm not 100% certain, but the X11 servers on your xxx.xxx.86.0 subnet my be relying upon XDMCP broadcasts to locate the FreeBSD machine on the same subnet. Broadcasts cannot be routed between subnets and therefore your Windows XP system on your xxx.xxx.87.0 subnet won't be responded to by your FreeBSD machine. Rather than using broadcasts, you should be able to configure the X11 server software on your Windows XP system to do a direct XDMCP query of the FreeBSD system by specifying it's hostname or IP address. Because a specific IP address is used the XDMCP query will properly traverse the subnets to establish an X11 session. Mike Thompson Thanks. I should have specified in my e-mail that I was using direct queries and not broadcasts. Sorry I forgot that detail. It turns out that there is a problem with a router here. The packets were getting from the xxx.xxx.87.0 to the xxx.xxx.86.0 network just fine but packets from xxx.xxx.86.0 were not getting to xxx.xxx.87.0. The network administrator moved the Windows machine over to the xxx.xxx.86.0 network so the machine could connect via the X server. I guess the answer to my question is that it should work, with direct query, as long as the routers are functioning properly. Thanks again. At 01:23 PM 2/6/03 -0600, Glenn Johnson wrote: I have a Windows XP machine at work that I am trying to get an X11 server to connect to a FreeBSD machine. The FreeBSD machine is on the xxx.xxx.86.0 network and the Windows XP machine is on the xxx.xxx.87.0 network. X11 servers on other machines on the xxx.xxx.86.0 network work fine with xdmcp. Is there some restriction on xdmcp to being on the same network or do I have to add some kind of special routing entry to handle this? Thanks. -- Glenn Johnson USDA, ARS, SRRC Phone: (504) 286-4252 New Orleans, LA 70124 e-mail: [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: xdm fails at startup
malcolm kay wrote: Finarfin wrote: I have a 'virgin' install of 4.7. When I boot, all the text mode stuff I want runs fine. I would like to show some stuff to others using X, but it won't start. In my /etc/ttys file, I had the following line installed by the installation process: ttyv8 /usr/X11R6/bin/xdm -nodaemon xterm off secure I modified this by changing the off to on. After a kill -HUP 1, I get the following message (repeated every 30 seconds) init: getty repeating too quickly on port /dev/ttyv8, sleeping 30 secs. I experienced a problem which may be the same on FreeBSD4.7. xdm won't work when the depth is set to 8 - a common setting and the default if left unspecified. Everything seems fine when set for greater depths. I've experienced this problem on two quite different machines with different video systems. It seems that the xdm login crashes with depth 8. When used with startx it runs but with some considereable problem with colors - it finds half a dozen or so but reports voluminous errors about unable to allocate color such and such, even though only a negligable portion of the possible 256 pallette is used. I eventually gave up and went back to FreeBSD 4.5 and XFree 4.1 though I suspect I need only have changed the XFree version. I have applications which must have 8 bit pseudo-color so can't live with 16 or 24 bit depth. Malcolm Kay I received e-mail in response to this with the suggestion that I inform the ng. That e-mail and my e-mail response follow: dean linford wrote: Hi, you wrote: I experienced a problem which may be the same on FreeBSD4.7. xdm won't work when the depth is set to 8 - a common setting and the default if left unspecified. Everything seems fine when set for greater depths. I've experienced this problem on two quite different machines The problem is likely Xresource. Here's _part_ of my diff: #if PLANES = 8 xlogin*logoFileName: /usr/X11R6/lib/X11/xdm/pixmaps/XFree86.xpm #else --- !#if PLANES = 8 !xlogin*logoFileName: /usr/X11R6/lib/X11/xdm/pixmaps/XFree86.xpm !#else The = likely should be taken out, instead but I just wanted the thing to be working. There are too many colours in the colour pixmap. I'd sent a comment off to xfree86 site, but am not so confident it was acted upon The pixmap doesn't have too many, but there are colors allocated by the server as well - oops! You may want to tell the group/list (comp.unix.bsd.freebsd.misc), as I don't usally post to public groups. I'm not sure whether or not the = should be removed, but FreeBSD4.5 with XFree4.1 has the same (i.e. with the =) and that works. In any case the colours are screwed up using startx which does not access the xlogin widget (at least I can't believe that it does). I'll also post this to the ng as you suggest. I have new suspicions w.r.t. the basis of the problem but this is so subtle as to be almost unbelievable. I had forgotten a problem I experienced on another FreeBSD4.5 machine running XFree3.??. On that machine while X-windows was running I changed the default lang: entry in login.conf to en_AU.US_ASCII to get a sensible national date time string instead of the crazy American version. Xdm started before the change was already displaying a login screen but now all attempts to login via xdm failed. The login disappeared in the normal way on completion of the mname and password; but a moment later reappeared instead of the windows manager display (ctwm in this case). Removing the lang entry cleared the problem. Now FreeBSD4.7 sets this parameter in login.conf when the time zone is set at installation. So based on somewhat slim evidence I'm of the opinion that X can't manage general national time/date strings. Now I want to find a machine free on which I can re-install FreeBSD4.7 and XFree 4.2 and explore further. Could the time/date string also be an issue with sendmail which was also giving me grief with FreeBSD4.7? Malcolm Kay To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: xdm keeps showing me login window
On Mon, Dec 09, 2002 at 12:31:06PM -, local.freebsd.questions wrote: On Mon, 9 Dec 2002 11:00:54 - , [EMAIL PROTECTED] (Matthew Seaman) wrote: On Mon, Dec 09, 2002 at 02:32:14AM -0800, Ali S. wrote: i have installed freebsd 4.7 on compaq proliant 1600 with cirrus 5446 vga card i have configured X with xf86config but when i run xdm and enter my username password it refreshes the screen and shows me the login window again... any idea? You should have a script ~/.xsession which contains a shell script to run the various X programs you require during your login session. That script should not exit until you decide to end your session. Typically that's done by running a session manager or a window manager in the foreground. eg. this is what I use: (details snipped) But you shouldn't *have* to do this. I did a 4.7 install, added XFree86-4 from ports, did the XF86Config, and new users (with empty home directories) get dropped into twm. The ~/.xsession should only be needed if you want something other than this. Yes. Quite so. xdm(8) will cope with a completely missing ~/.xsession by giving you some sort of default session --- if twm(1) does it for you, then all is fine and dandy. What xdm(8) doesn't manage in a very friendly manner is a broken ~/.xsession file. However, if you want to customise your X desktop and you don't have sufficient access or you prefer not to fiddle with the system-wide default session, then you're going to be writing yourself your own ~/.xsession, which can be tricky for the inexperienced. The more heavy weight X environments like KDE or GNOME move most of that configuration step into their own window or session managers, which have a user friendly point'n'drool^Wclick interface. Even so, they will still need something in the ~/.xsession to get themselves going. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: xdm keeps showing me login window
- Original Message - From: Ali S. [EMAIL PROTECTED] Date: Mon, 9 Dec 2002 02:32:14 -0800 (PST) To: [EMAIL PROTECTED] Subject: xdm keeps showing me login window i have installed freebsd 4.7 on compaq proliant 1600 with cirrus 5446 vga card i have configured X with xf86config but when i run xdm and enter my username password it refreshes the screen and shows me the login window again... any idea? I have this recurring dream of running it as root . . . Wilford Brimley plays a high-powered lawyer who DOES NOT SELL OATMEAL. But to stay on topic, I never had any luck at all with xdm, nor any skill, as if that would help, but I never thought to try running it as root until I'd given up and gone back to using startx. suid mght be dangerous, reasons why? (this is a chance for that essay on the hazards of suid, wmd, ssh, and robotech to see the light of day) cos chmod 4766 /usr/X11R6/bin/xdm ain't hard to type . . . I fear. Love, Franklin Pierce -- ___ Get your free email from http://mymail.operamail.com Powered by Outblaze To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: xdm is not working in 4.6-RELEASE
On Tue, Sep 17, 2002 at 02:59:27PM -0500, Eduardo Viruena Silva wrote: I have installed FreeBSD 4.6-RELEASE in a new computer, I also installed X and KDE, verything is working fine except xdm. I'm sure X is working because startx works. In my /etc/ttys, I changed: ttyv8 /usr/local/bin/xdm -nodaemon xterm off secure ^^ on to: ttyv8 /usr/local/bin/xdm -nodaemon xterm on secure and then: kill -HUP 1 my computer started blinking but even X did not start. The blinking you're seeing is X starting up, then almost immediately dying, after which init restarts xdm and around we go again. Look at /var/log/xdm-errors and /var/log/XFree86.0.log for clues as to why X is continually failing so soon after it starts up. Note that recent versions of XFree86 4.x now expect to find most configuration files in /usr/X11R6/lib/X11, rather than in /etc/X11 which is what XFree86 3.x used to use. (The exception is the XF86config file which is searched for on a complicated path detailed in the XF86Config(5) man page) Otherwise, you seem to have done everything right. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
