Linked by Thom Holwerda on Sat 15th Aug 2009 17:55 UTC
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 378743
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: More anti-X bullcrap from the peanut gallery
by siride on Sun 16th Aug 2009 02:40
in reply to "RE[3]: More anti-X bullcrap from the peanut gallery"
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.
Member since:
2006-04-06
No it doesn't:
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.
How old is Xlib? Why hasn't this been fixed?
Edited 2009-08-16 02:36 UTC