Idea
#13906: Include Xorg-edit, a graphical editor for xorg.conf, by default on Ubuntu
|
| |
21
|
|
|
Written by kernel_script the 30 Sep 08 at 21:11.
Category: Accessibility.
Related to:
Nothing/Others.
Status: New
|
|
|
Description
Include Xorg-edit, a GUI editor for xorg.conf, by default on Ubuntu.
I see a lot of people that don't have their monitor resolution set properly, and have to edit xorg.conf to do so.
If it comes by default, it will be a great and helpful tool for lay persons and beginners.
Info:
http://ubuntuforums.org/showthread.php?t=156243
http://www.deesaster.org/progxorg.php
If it is not possible, at least, put it on the Ubuntu repositories.
Attachments
Duplicates
Comments
|
Ubuwu wrote on the 30 Sep 08 at 21:39
| |
In intrepid, xorg.conf is almost empty on most systems so there shouldn't be much need to edit it. I think this is a valuable utility to have in the repositories, but not to include by default.
|
|
Eldmannen wrote on the 30 Sep 08 at 22:32
|
Xorg.conf is being faded away.
It was something needed before, but now we got auto-detection. :)
|
|
kernel_script wrote on the 1 Oct 08 at 02:20
|
Guys, the problem, is that i see a lot of people that don't have their monitor resolution set properly, and have to edit xorg.conf to do so.
If this problem will completely vanished on Intrepid, awesome, if not, it will be a great and helpful tool for lay persons and beginners.
|
|
ikonia wrote on the 1 Oct 08 at 08:24
|
xorg is being made more and more dynamic, which is a great think, however as the original poster said, some people will have to up hardcoded options into the xorg.conf file to make up for failing detection, or miss-detection, or unusual configurations.
Having a specific editor for this seems a waste, there are multiple X11 text editors available that will allow you to edit this file.
The number of people with issues are either
a.) a very small minority with genuine issues
b.) users of third party drivers (nvidia/ati) which it would be impractical to build a managment tool for as they are both closed source and change on a frequent basis, with not all options compatible.
With time this will go (xorg matures more, ati open up drivers etc etc).
I don't see the point of a specific tool when both graphical and non-graphical (X11) editors are available for people to use, and support resources (forum/wiki/irc) explain to the minority how to resolve the issue.
|
|
Tree MendUs wrote on the 1 Oct 08 at 10:48
|
Ikonia,
Do you have the names of any of those editors that you could place here, for those who may want to use them?
kernel_script,
I submitted a package request for this program a few hours back, and it has already gone to importance level = "wishlist", and staus level = "triaged".
"triaged" means it is in line for being worked on.
This happened fairly quickly, so it looks like some of the packaging team is keen to see this one happen.
Good idea !
Considerate of others .
Here's an additional idea ...
In the case of the automatic detection system either not working, or not giving optimal result, or user wants to force a setting,
then this program could be used for making the adjustements.
The information could be sent back to Xorg (email, website webform entry, or sent from inside the program [with user's consent]).
That way the program will actually "help" improve the automated functions in Xorg, so that less people will "need" the program in future, than need it now.
But the program will always be helpful to add settings for new or unheard of devices, to Xorg's automatic system as time goes by.
|
|
ikonia wrote on the 1 Oct 08 at 13:24
|
your missing the point.
1.) xorg.conf is a simple text file, nothing more, ANY text editor gedit, vi, emacs, nano, whatever will be able to edit it.
2.) if autodetection fails or has issues, as I said in my original post it is normally down to a.) unsupported hardware - nothing xorg can do about that, b.) 3rd party drivers (nvidia/ati) nothing xorg can do about that
Things will change as drivers become more available so the detection will work, but until then, there is nothing that can be done, and a pretty interface to edit it is a waste of time when you consider the vast ammount of guides/tools/docs/support available to help the relative minority with these issues.
and triaged does not mean "due to be worked on" it means "acknowledged" in that, it's been catagorised as a wish list eg: it doesn't exist but a user (eg: you) would like to exist in the future. It has now been triaged, and taken out of the "active" bugs in progress and put in a more appropriate place.
|
|
andruk wrote on the 1 Oct 08 at 21:23
|
This would best be left in the repos, and not on the live CD.
+1
|
|
adelie wrote on the 1 Oct 08 at 21:31
|
Aside from the fact that xorg.conf is very straight forward, and the fact that anything practical for a GUI could easily be replaced by automation, you must be talking about something very specific that already exists or is presently being worked upon (xdmx is AWSOME!!!), I am left with one last question...
What use is a GUI when X fails?
-1 not an idea
|
|
Tree MendUs wrote on the 2 Oct 08 at 06:14
|
Auto detection may fail, but you still can get a default monitor setting.
It works, but is hardly a top performer.
I had a problem when upgrading from Edgy to Feisty with mouse recognition - it was due to settings for a "tablet" in xorg.conf and I didn't even run a tablet.
I had to manually edit this file, which involved getting familiar with how the whole thing worked, and a reasonable amount of research - as a result I tweaked the monitor at the same time, and got an understanding of dual monitor setups.
A GUI is not just having the graphics, it has all the help/knowledge that is associated with each choice that needs to be made - usually built in (and if not built in then it can be added in later versions).
|
|
kernel_script wrote on the 10 Oct 08 at 18:36
|
@adelie
I did not got your point.
I clearly said that Xorg-edit is a XORG.CONF EDITOR. It is NOT a X recover tool. Ubuntu already have a nice and cool X recover tool.
And of course it's a idea.
I did two proposals if you did not saw: Include it by default on Ubunut OR put it on repositories.
|
|
kernel_script wrote on the 10 Oct 08 at 18:39
|
Correcting:
*Ubuntu
|
|
borsook wrote on the 10 Oct 08 at 18:48
| |
I've been using Ubuntu since 7.04 and in each and every edition (including 8.10 beta) I was forced to edit it to get the right resolution. That said I'm not sure if the GUI is that necessary... the file is pretty well laid out...
|
Post your comment
|
|
|
Ubuntuforums.org thread #156243