Is it going to be released for Karmic?
--
nvidia-settings doesn't have permissions to write xorg.conf
https://bugs.launchpad.net/bugs/200868
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.u
@Arthur
I had to update screen-resolution-extra because of a change in the new
PolicyKit. Otherwise when I launched nvidia-settings from the command line I
got this error:
dbus.exceptions.DBusException: org.freedesktop.PolicyKit1.Error.Failed: Error
parsing subject struct
It works well now.
Pl
** Attachment added: "xorg.conf"
http://launchpadlibrarian.net/37855959/xorg.conf
--
nvidia-settings doesn't have permissions to write xorg.conf
https://bugs.launchpad.net/bugs/200868
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
** Branch linked: lp:ubuntu/nvidia-settings
--
nvidia-settings doesn't have permissions to write xorg.conf
https://bugs.launchpad.net/bugs/200868
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
@Artur
That's because your settings won't be written if your xorg.conf is not valid.
Please attach your xorg.conf
--
nvidia-settings doesn't have permissions to write xorg.conf
https://bugs.launchpad.net/bugs/200868
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Not fixed. Got:
1) Failed to parse existing X config file '/etc/X11/xorg.conf'!
2) Unable to open X config file '/etc/X11/xorg.conf' for writing.
Zainstalowana: 190.53-0ubuntu1
** Changed in: nvidia-settings (Ubuntu)
Status: Fix Released => Confirmed
--
nvidia-settings doesn't have per
That was fast. Thanks, Alberto! :)
--
nvidia-settings doesn't have permissions to write xorg.conf
https://bugs.launchpad.net/bugs/200868
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
This bug was fixed in the package nvidia-settings - 190.53-0ubuntu1
---
nvidia-settings (190.53-0ubuntu1) lucid; urgency=low
* New upstream release (LP: #417410).
* debian/control:
- Add build dependency on cdbs.
- Remove build dependency on dpatch.
- Add lpia architec
** Changed in: nvidia-settings (Ubuntu)
Status: Confirmed => In Progress
--
nvidia-settings doesn't have permissions to write xorg.conf
https://bugs.launchpad.net/bugs/200868
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
I guess that Albertio is going to fix this bug by the new upstream of
nvidia-settings ;) good luck!
--
nvidia-settings doesn't have permissions to write xorg.conf
https://bugs.launchpad.net/bugs/200868
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: nvidia-settings (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
--
nvidia-settings doesn't have permissions to write xorg.conf
https://bugs.launchpad.net/bugs/200868
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
That is the solution I offered about four releases ago. Check reply #18
in this thread. Then read all the guff I received for daring to suggest
you run a GUI app as superuser.
--
nvidia-settings doesn't have permissions to write xorg.conf
https://bugs.launchpad.net/bugs/200868
You received this
a good solution si to change the shortcut to
gksu "nvidia-settings"
in order to run as root, and so you can save xorg.conf in /etc/X11 .
this is normal, as the shortcut is in the "system" > "administration" menu.
--
nvidia-settings doesn't have permissions to write xorg.conf
https://bugs.launchpa
Thank you!! We'll need someone to review the patch ( Albero Milone? ).
Are all those direct changes to files (except in ./debian/ folder) for
policy kit and dbus?
To speed things up, I'm including a debdiff patch. I compared it to
current jaunty.
In case you're wondering how I did the debdiff:
$
I have made my own fix that uses PolicyKit and a dbus service, I have made this
to learn the build and PPA process and how to use PolicyKit and dbus.
https://launchpad.net/~morten-justesen/+archive/ppa/+sourcepub/682796/+listing-archive-extra
But I thought I would share it, it works but I must war
I for one must agree with lewmur. I think it is an absolute joke that
this hasn't been fixed by now. Users do not care how you fix it as long
as you do. In the moment, an application that everyone that I've ever
talked to uses who runs Ubuntu and has an nvidia card, is fundamentally
broken as far a
As I said, there is no .nividia-settings-rc file on my machine so I
don't much care where it is saved. And at the rate its taking I'm not
really concerned about what happens after "the bug is later fixed." It
will undoubtedly occur after I've installed another release anyway. I'm
not going to do
lewmur, .nvidia-settings-rc is not an executable, it's a configuration
file that nvidia-settings uses to save user preferences for the server
configuration. Wearing my "Ubuntu user" hat, I would personally prefer
not having it save things like my brightness and contrast settings in
root's home dir
https://bugs.launchpad.net/ubuntu/+source/nvidia-
settings/+bug/200868/comments/39
This pretty much says it all. Alberto was going to write the patch but
asked the higher ups how they wanted it done and never got a response.
"If you run with gksudo you're running a full GUI app as root for no
r
I have just noticed that this was assigned to Alberto Milone 6 months back, but
it was assigned to him by someone else. That was a wrong move probably, because
it's like saying "I got this, I'll do this ASAP".
After 6 months of no progress, I'll set it to "Nobody" in case someone wishes
to take
To those who feel I've been overly aggressive in my comments, I'll just
say that after dealing with this situation through three releases, my
patience has worn thin. Over a year ago, I went so far as to write a
script that would warn the user about the dangers of running the applet
as root, check
Ubuntu makes the installation of Nvidia drivers easy as in no other
major distribution. Nobody forced the Ubuntu developers to so -- but
they did, and personally I consider this a wise decision and one reason
for the success of Ubuntu. I guess that most Ubuntu users with Nvidia
graphic card do inst
While lewmur IMHO is a big aggressive in his opinion, I have to agree
with him. This is a big usability issue for nvidia users (~25%). I
completely agree with Savvas Radevic as well. While a gksudo fix might
not be the most ideal way to solve this problem, it is the only thing we
have right now - a
Actually, once a quick 'fix' like this gets implemented there is zero
motivation to work on the proper fix and it'll probably never happen.
Either way, it isn't up to me since I don't handle this package.
--
nvidia-settings doesn't have permissions to write xorg.conf
https://bugs.launchpad.net/b
> Again, if you have a BETTER solution, then implement it. Don't just
> talk about it. Otherwise I'll keep advising people to do what works
I'd have to agree with this comment, Ubuntu is (or should be) all
about the human needs, not the "proper" thing to do (which seems to
take enough time to be
You are certainly welcome to advise them of your workaround for this
bug. I just don't believe such a thing should be added to the package.
--
nvidia-settings doesn't have permissions to write xorg.conf
https://bugs.launchpad.net/bugs/200868
You received this bug notification because you are a me
And I say there is a very good reason for doing so. It is the only way
to get dual monitors to work for the average user. The only other way
is to change the ownership of xorg.conf which belongs to root to begin
with. There is NOT a good reason for not allowing nvidia-settings to
run with root p
If you run with gksudo you're running a full GUI app as root for no
reason _and_ causing a bug because the .nvidia-settings-rc file will be
saved for the root user instead of for the user running the app so
setting changes they make that _don't_ write to xorg.conf will not be
saved in the correct l
I'd really like for someone to explain in REAL terms, not some
theoretical BS, just what makes gksudo a hack, and Policy-Kit, which no
one seems to be capable of implementing, not a hack. If gksudo is a
hack, I'll still take a working hack over a non-working Policy-Kit
everyday of the week.
--
n
Calling something that works perfectly well a hack is nonsense. The
perfectionists that keep claiming this have had plenty of time to fix
this in the so called "right way" and it still hasn't been done. It is
totally asinine to let this situation continue for two years when there
is a perfectly s
Hacks are not fixes. Also, is this program even installed by default?
Paper cuts are only for things installed by default.
--
nvidia-settings doesn't have permissions to write xorg.conf
https://bugs.launchpad.net/bugs/200868
You received this bug notification because you are a member of Ubuntu
Bu
I disagree that this is not a good papercut - if all that is required is
to append gksudo to the front of the launcher for the nvidia-settings -
then this should be done.
And, yes I have read the above comments (8 etc) about superuser access -
however, I fully agree with what Christian Funder Somm
This is actually not a good paper cut because "it requires writing more
than a few lines of code". If there was an accepted patch and the only
thing left was to apply it to the package then it would probably qualify
but the sudo tricks and menu editing are hacks and the PolicyKit
solution was never
Definitely a good papercut. Easily solvable and very much affecting (without
this, your settings changes just silently fail for the most part)
--
nvidia-settings doesn't have permissions to write xorg.conf
https://bugs.launchpad.net/bugs/200868
You received this bug notification because you are a
** Also affects: hundredpapercuts
Importance: Undecided
Status: New
--
nvidia-settings doesn't have permissions to write xorg.conf
https://bugs.launchpad.net/bugs/200868
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
This issue appears to still be complicated/unresolved to many end-users,
as I have twice now explained to them on how to properly do this. Please
continue to find the best possible solution.
--
nvidia-settings doesn't have permissions to write xorg.conf
https://bugs.launchpad.net/bugs/200868
You
@Nietzsche Keen: The first solution is not really a solution, as a user
should be able to use all parts of the nvidia-settings gui when launched
from the menu (rather than from the command-line with sudo), and
currently that doesn't work with changing the resolution and refresh
rates. Running sud
I should elaborate on how to save root Nvidia settings;
After choosing the proper resolution, choose "Apply" "OK", "Save to X
Configuration File"
This should set the proper settings for the root. (Even though you are
probably the primary user and operating under the first username you set
up, you
The simple solution is that there are two places in which settings must be
changed.
The first is in Nvidia settings as root user - run: sudo nvidia-settings from
terminal.
Second, change the resolution settings under System-Preferences-Screen
Resolution
You may need to reboot between steps.
Th
Somebody from Ubuntu needs to decide whether the setuid PolicyKit helper
is acceptable, or if something more complicated involving a daemon that
connects to dbus needs to be written. If running a daemon is required,
then we probably won't be able to support it in the upstream code.
Assigning to A
Hi,
I just have to add that I have had this problem in the last couple Ubunutu
releases too, only just getting to grips with what it means to be part of the
community and report this sort of problem. If the app is put in the menu it
should work?? If people think it is too dangerous to run as roo
As an intermediate user who has recently succeeded in setting up dual
screens in intrepid, i'd like to offer my two cents here. Most novices
are never going to find this menu because it doesnt come in with the
drivers. I had to google deep to find the nvidia-settings package. I ran
into this issue
Yeah, I think everyone knows how to work around this bug... its a
feature request.
---
Kyriacos wrote:
> save the xorg.conf on the desktop
> and
> cp /etc/X11/xorg.conf /etc/X11/xorg.bak
> sudo cp /home/you/Desktop/xorg.c
save the xorg.conf on the desktop
and
cp /etc/X11/xorg.conf /etc/X11/xorg.bak
sudo cp /home/you/Desktop/xorg.conf /etc/X11/xorg.conf
ctr+alt + backspace
Tada!!!
--
nvidia-settings doesn't have permissions to write xorg.conf
https://bugs.launchpad.net/bugs/200868
You received this bug notific
By dbus part I really meant PolicyKit “mechanism". The mechanism is a
separate program. Basically the mechanism is started with root
privileges and acts as a dbus server to which you can connect from your
client application (nvidia-settings) which is also called “agent”. When
you request the author
I threw together a prototype patch (attached) and uploaded a build to my
PPA. Let me know if this is what you meant. I didn't quite understand
what you meant by "put a function [...] in the dbus part." I wanted to
keep the setuid part as simple as possible, so I left all of the parser
stuff in t
As discussed in #xorg-devel, you might want to put a function (e.g. from
the parser that you use in nvidia-settings) which can write the settings
with root privileges in the dbus part. Nvidia-settings should then pass
the configuration to that function through dbus.
--
nvidia-settings doesn't hav
I've been thinking about exactly this issue. As for supporting
PolicyKit in the upstream release, we ought to be able to get away with
dlopening libpolkit-dbus.so.2 at runtime and using the helpers from that
if they exist. I've got a prototype that I threw together that I'll try
to clean up and a
Both nv.sh and nv1.sh should be placed in the /etc/X11 directory with
the Menu pointing to nv1.sh.
--
nvidia-settings doesn't have permissions to write xorg.conf
https://bugs.launchpad.net/bugs/200868
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Alberto;
Using PolicyKit is obviously the best appraoch and your effort is apprieciated.
All I intended the script alternative to be is something to use while that is
being done. Take a look at these and see if they won't work.
nv1.sh
echo "It is not recommended that this application be run in
lewmur: I volunteered to add the support for PolicyKit to nvidia-
settings but of course if you want to write a script yourself you're
more than welcome to do so.
--
nvidia-settings doesn't have permissions to write xorg.conf
https://bugs.launchpad.net/bugs/200868
You received this bug notificati
"Rationale: nvidia-settings doesn't have to be launched as root as it
saves the user's settings to ~/.nvidia-settings-rc (so as to have per
user settings)."
It may save some of the settings there, but not all. Try setting up
dual monitors without modifying xorg.conf.
And I still haven't seen any
Has anyone filed this to nvidia?
--
nvidia-settings doesn't have permissions to write xorg.conf
https://bugs.launchpad.net/bugs/200868
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.
lewmur: had you read comment 8 you would have seen the reason why
nvidia-settings shouldn't run as root. Anyway, here's my point:
"Rationale: nvidia-settings doesn't have to be launched as root as it
saves the user's settings to ~/.nvidia-settings-rc (so as to have per
user settings)."
--
nvidia
It is generally always a bad idea to have things run as superuser that
don't absolutely need to. Since Alberto is the maintainer for the NVIDIA
stuff, I trust his word when he says it doesn't have to. He's also
working on this, so what's the fuss about?
BTW, had you read the bug I linked, you woul
For those purist that think it is too dangerous to have nvidia-settings
run as superuser by default, create a script that allows the user to
choose whether run it directly or as superuser and have it warn them of
the danger of possibly having to manually replace xorg-conf from the
CLI. Then have t
Oh?? There is a law saying "Don't run nvidia-settings" as a superuser?
Nonsense. So long as it requires the sudo password, there is no reason
not to do so except FUD. It is far better to have nvidia-settings write
to xorg-conf than to have a novice doing so through a terminal editor.
BTW, if yo
His point is that you are not supposed to run nvidia-settings as a
superuser and therefore shouldn't tell people to change their menus.
BTW, I am not affected by this bug in Intrepid. Apart from bug #286424,
nvidia-settings started from the Administration menu (without gksu)
works perfectly for me
I did read them. And your point is?
--
nvidia-settings doesn't have permissions to write xorg.conf
https://bugs.launchpad.net/bugs/200868
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
lewmur: please read comment 8 and the next comments.
--
nvidia-settings doesn't have permissions to write xorg.conf
https://bugs.launchpad.net/bugs/200868
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
Solution: Edit the menu properties for Nvidia X Server Settings and
change the "Type" from "Application" to "Application in Terminal." Then
place "sudo" at the beginning of the "Command Line." Then when the Menu
option is clicked, a terminal window is openned and you are asked for
the sudo passw
Okay :)
--
nvidia-settings doesn't have permissions to write xorg.conf
https://bugs.launchpad.net/bugs/200868
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.
I can file an SRU when the patch is ready but then the MOTU-SRU team
will decide what to do.
--
nvidia-settings doesn't have permissions to write xorg.conf
https://bugs.launchpad.net/bugs/200868
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
1) would indeed be the best solution in my opinion, assuming xorg.conf
is the only way to actually apply these settings, and xorg.conf must
require superuser access to modify.
Can't we send it out as a patch for Intrepid after the release then?
--
nvidia-settings doesn't have permissions to writ
I could work on solution 1) and forward the patch to NVIDIA and the
Debian maintainer of nvidia-settings. It's too late to do it for
Intrepid though.
--
nvidia-settings doesn't have permissions to write xorg.conf
https://bugs.launchpad.net/bugs/200868
You received this bug notification because yo
I fully agree! The problem is just that the user probably won't know
which settings that require xorg.conf write-acess (and shouldn't need
to!). Seeing that nvidia-settings doesn't use any kind of privilege
escalation system, the user might get stuck with an error after changing
settings. Assuming
Christian, no, please read what I wrote in comment 8. Nvidia-settings
shouldn't be launched with root privileges unless you need to modify
your xorg.conf.
--
nvidia-settings doesn't have permissions to write xorg.conf
https://bugs.launchpad.net/bugs/200868
You received this bug notification becau
Isn't that exactly the point? :)
If nvidia-settings requires superuser access, then the menu shortcut for
Ubuntu should probably be prefixed with "gksu"?
There doesn't seem to be much point in having a graphical frontend in
the menu if users are required to jump into a terminal and prefix "sudo"
Christian:
if you launch it with "sudo" you will be able to save your settings.
I'm pretty sure that NVIDIA is aware of the problem,however I don't
think that adopting a solution with PolicyKit upstream is an ideal
solution for them as it would prevent nvidia-settings from working on
systems that
Alberto, if nvidia-settings throws an "Access denied" error message when
changing any of the settings, surely this is more of a bug than a
wishlist item?
--
nvidia-settings doesn't have permissions to write xorg.conf
https://bugs.launchpad.net/bugs/200868
You received this bug notification becaus
Rationale: nvidia-settings doesn't have to be launched as root as it
saves the user's settings to ~/.nvidia-settings-rc (so as to have per
user settings). What we could do is make it use PolicyKit to ask the
password only when the xorg.conf must be modified.
I'm marking this as a wishlist report.
I can confirm it is still broken in Inteprid beta1.
--
nvidia-settings doesn't have permissions to write xorg.conf
https://bugs.launchpad.net/bugs/200868
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
It would be better for nvidia-settings not to be in the main menu than
to fail to save its settings although it shouldn't be too easy to mess
around with an important file like xorg.conf.
--
nvidia-settings doesn't have permissions to write xorg.conf
https://bugs.launchpad.net/bugs/200868
You rec
Policy-Kit
--
nvidia-settings doesn't have permissions to write xorg.conf
https://bugs.launchpad.net/bugs/200868
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubun
> nvidia-settings isn't using the new Gnome privileges escalation system
> (I can't remember what it was called).
You mean AppArmor?
--
nvidia-settings doesn't have permissions to write xorg.conf
https://bugs.launchpad.net/bugs/200868
You received this bug notification because you are a member
Confirming since I got this too. This is on Hardy beta, installed from
2008-03-20 live CD.
This really really ought to be fixed before Hardy release.
** Changed in: nvidia-settings (Ubuntu)
Status: New => Confirmed
--
nvidia-settings doesn't have permissions to write xorg.conf
https://b
It seems like the issue here is that nvidia-settings isn't using the new
Gnome privileges escalation system (I can't remember what it was
called). It should at a minimal be called with gksu (which would prompt
for a password), and at best use the privilege escalation system.
--
nvidia-settings do
xorg.conf is a critical system file for most users, IMO. An unprivileged
user should not have write access. It may be wise to prompt for the root
password, instead of simply exiting with an error.
--
nvidia-settings doesn't have permissions to write xorg.conf
https://bugs.launchpad.net/bugs/20086
78 matches
Mail list logo
