xorg.conf changed on start of lightdm service

Bug #1574154 reported by Jos Nouwen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

After upgrading from 15.10 (Wily) to 16.04 (Xenial), X wont start. It appears that my xorg.conf is modified such that I get a non-working way (I get a coredump in the video driver I think). I have a Thinkpad T530 with dual video cards, so I change the from the nvidia that is somewere(?) auto selected back to intel. Alas, restarting of lightdm service does not work: xorg.conf is re-modified. Manually starting a X session with 'startx' (after correcting xorg.conf) works as expected. Alas, nobody logs about this; that would have helped me find the culprit..

Who modifies my xorg.conf? Why? This never happened before, and should IMHO not be done.

Temporary solution: 'chattr +i /etc/X11/xorg.conf'. This makes auto-changing impossible. But this is a hack. I should be allowed to change my system such that it works the way I want.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg (not installed)
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: MATE
Date: Sun Apr 24 05:45:17 2016
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: Upgraded to xenial on 2016-04-21 (2 days ago)

Revision history for this message
Jos Nouwen (josn) wrote :
Revision history for this message
Paul White (paulw2u) wrote :

We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time.

Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.

Do you still see a problem related to the one that you reported when using a currently supported version of Ubuntu? Please let us know if you do otherwise this report can be left to expire in approximately 60 days time.

Thank you for helping make Ubuntu better.

Changed in xorg (Ubuntu):
status: New → Incomplete
Revision history for this message
Jos Nouwen (josn) wrote :

Wow, a reply on a bug report after 6 years! I did not mean this to be negative, just surprised that I got a response this late. I forgot all about it, but this brings a lot back. Back then, I was mostly wondering what was in the mind of someone to change a user-modifiable config file..

But anyway, the T540 is running 20.04 now, and I dont see that problem anymore; maybe because I dont use a xorg.conf currently. And, the T540 is currently retiring ;-)

Anyway, No problem for me anymore. Status can be changed to 'Time made us forget this' ;-)

Btw: I'm still proud of my quick fix: 'chattr +i xorg.conf' ;-)

Revision history for this message
Paul White (paulw2u) wrote :

Thanks for your reply. Yes, some bug reports
do seem to be forgotten. ;o)

Closing as "Invalid" on the basis the issue was
never confirmed by another user and the Xenial
release is now EOL.

Changed in xorg (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.