Bug#612681: x11-common: treat empty session names silently as default session
On Mon, May 16, 2011 at 10:21:14PM +0200, Marko Macek wrote:
> On 05/16/2011 03:51 PM, Agustin Martin wrote:
> >These are the .xsession-error messages for the failing icewm-session invocation
> >from wdm (lines with AMD-WARNING are the extra info I requested)
> >
> >Xsession: X session started for testuser at Mon May 16 15:26:28 CEST 2011
> >Xsession: AMD-WARNING: Running "/etc/X11/wdm/Xsession" with arguments "icewm-session"
> >Xsession: AMD-WARNING: Passing session as argument "icewm-session"
> >/home/testuser/.Xresources:1:24: warning: missing terminating ' character
> >/home/testuser/.Xresources:13:28: warning: missing terminating ' character
> >Xsession: AMD-WARNING: starting "/usr/bin/ssh-agent
> >/usr/bin/ck-launch-session /usr/bin/dbus-launch --exit-with-session
> >icewm-session"
> >icewm-session: using /home/testuser/.icewm for private configuration files
> >IceWM: using /home/testuser/.icewm for private configuration files
> >icewmtray: using /home/testuser/.icewm for private configuration files
> >icewmbg: using /home/testuser/.icewm for private configuration files
> >XIO: fatal IO error 104 (Connection reset by peer) on X server ":0"
> > after 205 requests (205 known processed) with 2 events remaining.
> >XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
> > after 110 requests (105 known processed) with 0 events remaining.
> >XIO: fatal IO error 104 (Connection reset by peer) on X server ":0"
> > after 122 requests (122 known processed) with 0 events remaining.
> >Invalid MIT-MAGIC-COOKIE-1 keyicewmbg: Can't open display: :0. X must be
> >running and $DISPLAY set.
> Does the X server crash here? Any messages in Xorg log? I found a bug in X in Fedora that fails like this, might be the same.
In my case seems that icewmbg is the one to blame, but still have to check
before cloning #626331 and reassigning.
Possible upstream bug report:
http://sourceforge.net/tracker/?func=detail&atid=100031&aid=3289566&group_id=31
Possible Ubuntu launchpad bug report:
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/757610
If I have time today, I will try to reproduce the problem once again, but now
looking more carefully at Xorg log.
Regards,
--
Agustin
Reply to: