sudo chmod +x /usr/share/screen-resolution-extra/nvidia-polkit fix write
problem
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/200868
Title:
nvidia-settings doesn't have permissions
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-X,
which is subscribed to nvidia-settings in ubuntu.
@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-X,
which is subscribed to nvidia-settin
** 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-X,
which is subscribed to nvidia-settings in ubuntu.
___
@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-X,
which i
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-X,
which is subscribed to nvidia-settings in ubuntu.
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-X,
which is subscribed to nvidia-settings in
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-X,
which is subscribed to
** 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-X,
which is subscribed
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
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-X,
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-X,
which is subscribed to nvidia-settings in ub
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
32 matches
Mail list logo
