@Edmond:
> I want to confirm this was a bug, but it has been fixed,
> Thanks Jinx-Wolf, your suggestion worked perfectly.
Just to clarify -- that doesn't sound like this bug "has been fixed". It sounds like you worked around the bug on your own machine, but the bug remains in un-worked-around installations of Ubuntu.
@froller:
> appending gksu before the menu command gives
> the appropriate permissions to write to the file.
True... but that's unrelated to this bug.
> Of course one needs to remove the /etc/X11/xorg.conf
> file first so the program can save as new.
To clarify -- if it weren't for this crasher bug, one should *not* need to do that. nvidia-settings is smart enough to read your existing xorg.conf and modify it -- the problem here is that it *crashes* when doing that, if the xorg.conf is missing a particular declaration. (which it apparently is on stock Ubuntu installs -- see comment 64, comment 69)
@Edmond:
> I want to confirm this was a bug, but it has been fixed,
> Thanks Jinx-Wolf, your suggestion worked perfectly.
Just to clarify -- that doesn't sound like this bug "has been fixed". It sounds like you worked around the bug on your own machine, but the bug remains in un-worked-around installations of Ubuntu.
@froller:
> appending gksu before the menu command gives
> the appropriate permissions to write to the file.
True... but that's unrelated to this bug.
> Of course one needs to remove the /etc/X11/xorg.conf
> file first so the program can save as new.
To clarify -- if it weren't for this crasher bug, one should *not* need to do that. nvidia-settings is smart enough to read your existing xorg.conf and modify it -- the problem here is that it *crashes* when doing that, if the xorg.conf is missing a particular declaration. (which it apparently is on stock Ubuntu installs -- see comment 64, comment 69)