Reflecting on my original issue from the perspective of a lay user, crashing the windowing system because a custom configuration file couldn't be parsed seems like a bug in its own right. A lay user may understandably react very strongly to seeing a black screen at startup. If they have a more technical friend, they will hopefully ask for help, but if they don't, they might wipe their (probably not backed up) hard drive by doing a fresh install of Ubuntu (or Windows) or throw away their computer altogether (assuming they can afford another). In this case, ignoring the no longer valid /etc/X11/xorg.conf.d/30-touchpad.conf and instead warning about its missing driver simply would have reverted my touchpad to its default settings. I would have noticed that my customizations were being ignored upon upgrading to Ubuntu 22.04 and immediately gone looking for the sloppy customization file I created by stitching together advice on the Internet. I realize that a lay user wouldn't be likely to attempt customizing X11, but you never know what outdated advice someone might copy and paste, and anything that can result in the total crippling of the system is majorly playing with fire.
-- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1977695 Title: Xorg fails to start: (EE) Error parsing the config file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1977695/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
