Linked by Thom Holwerda on Sat 15th Aug 2009 17:55 UTC
X11, Window Managers Over the past couple of months, and especially over the past couple of weeks, I've been working very hard to write and complete my thesis. I performed all the work on Windows 7, but now that the thesis is finally done, submitted, and accepted, I installed Ubuntu - and immediately I was reminded of why I do not do any serious work on Linux: the train wreck that is X.org.
Thread beginning with comment 378740
To view parent comment, click here.
To read all comments associated with this story, please click here.
siride
Member since:
2006-01-02

XEmacs can disconnect and reconnect. If there is a bug in XLib causing abort()s for a disconnect, that can easily be changed (very easily). Now your point is moot.

Reply Parent Score: 2

Dima Member since:
2006-04-06

XEmacs can disconnect and reconnect.

No it doesn't:
xemacs: Fatal I/O Error 11 (Resource temporarily unavailable) on display connection "localhost:10.0"
after 2202 requests (2201 known processed) with 15 events remaining.
Autosaving and exiting...

Ok, it handled the disconnect by saving the file - but it certainly didn't try to reconnect. It exited, just like any other X app.

If there is a bug in XLib causing abort()s for a disconnect, that can easily be changed (very easily). Now your point is moot.

How old is Xlib? Why hasn't this been fixed?

Edited 2009-08-16 02:36 UTC

Reply Parent Score: 1

siride Member since:
2006-01-02

Probably because nobody has bothered to make this work from top to bottom of the client-side stack. No toolkit tries to make it work, so why should XLib devs bother making it work? There have been a few posts on the X.org mailing list regarding XLib's policy of aborting on failure and how it's wrong and apps should be able to reconnect, but there wasn't enough interest to do anything about it. It clearly is a more sane solution, though.

Reply Parent Score: 3