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
XDM cannot start desktop after Xorg upgrade
I've been using XDM as login manager for years. Since the latest Xorg upgrade, XDM cannot start XFCE4 as it used to. What happens is that after I've given my password and hit enter, the screen goes black and after a while it returns to the XDM log in dialogue. I've attached the users .xsession-errors and the system xdm.log Disabling XDM and starting X manually works. Of and on logging in via XDM works but there's no pattern to when it does and does not. Thanks /Leslie xdm info (pid 2391): Starting xdm info (pid 2391): Starting X server on :0 X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 9.1-RELEASE amd64 Current Operating System: FreeBSD bljbsd01.no-ip.org 9.1-RELEASE-p3 FreeBSD 9.1-RELEASE-p3 #0: Mon Apr 29 18:27:25 UTC 2013 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 Build Date: 29 January 2013 05:30:35PM Current version of pixman: 0.28.2 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Sat Jun 8 11:50:02 2013 (==) Using config file: /etc/X11/xorg.conf failed to set mtrr: Invalid argument The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Type ONE_LEVEL has 1 levels, but RALT has 2 symbols Ignoring extra symbols Errors from xkbcomp are not fatal to the X server xdm info (pid 2396): sourcing /usr/local/lib/X11/xdm/Xsetup_0 must specify a background color xdm info (pid 2396): sourcing /usr/local/lib/X11/xdm/GiveConsole xdm info (pid 2408): executing session /usr/local/lib/X11/xdm/Xsession xdm info (pid 2396): sourcing /usr/local/lib/X11/xdm/TakeConsole xdm info (pid 2391): Starting X server on :0 The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Type ONE_LEVEL has 1 levels, but RALT has 2 symbols Ignoring extra symbols Errors from xkbcomp are not fatal to the X server xdm info (pid 2424): sourcing /usr/local/lib/X11/xdm/Xsetup_0 must specify a background color xdm info (pid 2424): sourcing /usr/local/lib/X11/xdm/GiveConsole xdm info (pid 2438): executing session /usr/local/lib/X11/xdm/Xsession xdm info (pid 2424): sourcing /usr/local/lib/X11/xdm/TakeConsole xdm info (pid 2391): Starting X server on :0 The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Type ONE_LEVEL has 1 levels, but RALT has 2 symbols Ignoring extra symbols Errors from xkbcomp are not fatal to the X server xdm info (pid 2454): sourcing /usr/local/lib/X11/xdm/Xsetup_0 must specify a background color xdm info (pid 2454): sourcing /usr/local/lib/X11/xdm/GiveConsole xdm info (pid 2468): executing session /usr/local/lib/X11/xdm/Xsession xdm info (pid 2454): sourcing /usr/local/lib/X11/xdm/TakeConsole xdm info (pid 2391): Starting X server on :0 The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Type ONE_LEVEL has 1 levels, but RALT has 2 symbols Ignoring extra symbols Errors from xkbcomp are not fatal to the X server xdm info (pid 2484): sourcing /usr/local/lib/X11/xdm/Xsetup_0 must specify a background color .xsession-errors Description: Binary data ___ 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
