[Bug 667746] [NEW] vt1708 card not recognized in 10.10

2010-10-28 Thread lewmur
Public bug reported: !! !!ALSA Information Script v 0.4.59 !! !!Script ran on: Tue Oct 12 13:42:35 UTC 2010 !!Linux Distribution !!-- Ubuntu 10.10 \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 10.10" !!DMI

[Bug 658516] Re: Sound Does Not Work - No Sound Card Recognized

2010-10-12 Thread lewmur
I'm having the same problem. "lspci" list the VT1708 but it isn't there in "Sound Preferences". -- Sound Does Not Work - No Sound Card Recognized https://bugs.launchpad.net/bugs/658516 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. --

[Bug 200868] Re: nvidia-settings doesn't have permissions to write xorg.conf

2009-10-25 Thread lewmur
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

[Bug 200868] Re: nvidia-settings doesn't have permissions to write xorg.conf

2009-06-25 Thread lewmur
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

[Bug 200868] Re: nvidia-settings doesn't have permissions to write xorg.conf

2009-06-24 Thread lewmur
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

[Bug 200868] Re: nvidia-settings doesn't have permissions to write xorg.conf

2009-06-24 Thread lewmur
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

[Bug 200868] Re: nvidia-settings doesn't have permissions to write xorg.conf

2009-06-23 Thread lewmur
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

[Bug 200868] Re: nvidia-settings doesn't have permissions to write xorg.conf

2009-06-23 Thread lewmur
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

[Bug 200868] Re: nvidia-settings doesn't have permissions to write xorg.conf

2009-06-23 Thread lewmur
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

[Bug 200868] Re: nvidia-settings doesn't have permissions to write xorg.conf

2008-11-04 Thread lewmur
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

[Bug 200868] Re: nvidia-settings doesn't have permissions to write xorg.conf

2008-11-04 Thread lewmur
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

[Bug 200868] Re: nvidia-settings doesn't have permissions to write xorg.conf

2008-11-03 Thread lewmur
"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

[Bug 200868] Re: nvidia-settings doesn't have permissions to write xorg.conf

2008-11-03 Thread lewmur
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

[Bug 200868] Re: nvidia-settings doesn't have permissions to write xorg.conf

2008-11-03 Thread lewmur
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

[Bug 200868] Re: nvidia-settings doesn't have permissions to write xorg.conf

2008-11-02 Thread lewmur
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

[Bug 200868] Re: nvidia-settings doesn't have permissions to write xorg.conf

2008-11-02 Thread lewmur
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