Re: [Dorset] CUPS authentication question
On Thu, 2013-12-05 at 21:02 +, Tim Allen wrote: Yes, so my understanding is that any job not owned by the authenticated user (who is not a member of lpadmin) should show as withheld, No -- the JobPrivateValues attributes would. But they are none, so JobPrivateAccess has no effect. Think of it like chmod 755 * -- 755 would be JobPrivateAccess, * would be JobPrivateValues. Tim. */ signature.asc Description: This is a digitally signed message part -- Next meeting: Bournemouth, Tuesday, 2014-01-07 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ New thread on mailing list: mailto:dorset@mailman.lug.org.uk How to Report Bugs Effectively: http://goo.gl/4Xue
Re: [Dorset] CUPS authentication question
Hi Tim On 06/12/13 10:04, Tim Waugh wrote: On Thu, 2013-12-05 at 21:02 +, Tim Allen wrote: Yes, so my understanding is that any job not owned by the authenticated user (who is not a member of lpadmin) should show as withheld, No -- the JobPrivateValues attributes would. But they are none, so JobPrivateAccess has no effect. Think of it like chmod 755 * -- 755 would be JobPrivateAccess, * would be JobPrivateValues. Yes, you're right. JobPrivateValues default and JobPrivateAccess default should do what I wanted. It looks like JobPrivateAccess is broke (basically ignored) in 1.5, setting JobPrivateValues none at least gets back to pre-1.5 behaviour. Cheers Tim -- Next meeting: Bournemouth, Tuesday, 2014-01-07 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ New thread on mailing list: mailto:dorset@mailman.lug.org.uk How to Report Bugs Effectively: http://goo.gl/4Xue
Re: [Dorset] CUPS authentication question
On Fri, 2013-12-06 at 10:49 +, Tim Allen wrote: It looks like JobPrivateAccess is broke (basically ignored) in 1.5, setting JobPrivateValues none at least gets back to pre-1.5 behaviour. I'm not sure why you think it isn't working. Can you give an example that doesn't behave as you expect? (I've just re-read all your messages in this thread, and I don't see one that wasn't explained by my 'chmod' analogy.) Tim. */ signature.asc Description: This is a digitally signed message part -- Next meeting: Bournemouth, Tuesday, 2014-01-07 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ New thread on mailing list: mailto:dorset@mailman.lug.org.uk How to Report Bugs Effectively: http://goo.gl/4Xue
Re: [Dorset] CUPS authentication question
Hi Tim On 06/12/13 12:09, Tim Waugh wrote: On Fri, 2013-12-06 at 10:49 +, Tim Allen wrote: It looks like JobPrivateAccess is broke (basically ignored) in 1.5, setting JobPrivateValues none at least gets back to pre-1.5 behaviour. I'm not sure why you think it isn't working. Can you give an example that doesn't behave as you expect? (I've just re-read all your messages in this thread, and I don't see one that wasn't explained by my 'chmod' analogy.) Here's the relevant sections of cupsd.conf: DefaultAuthType Basic WebInterface Yes Location / Order allow,deny Allow @LOCAL /Location Location /jobs AuthType Default Require valid-user Order allow,deny Allow @LOCAL /Location Policy default JobPrivateAccess default JobPrivateValues default SubscriptionPrivateAccess default SubscriptionPrivateValues default Log on to CUPS Jobs web page as user1. All jobs (user1 and any other user) show Name Unknown, User Withheld for each job. This is correct for default JobPrivateValues (from manual, The default values are job-name, job-originating-host-name, and job-originating-user-name.) But incorrect for JobPrivateAccess (should be @OWNER, @SYSTEM). In fact, it doesn't matter what we put for JobPrivateAccess (all, user1, anything else), the result is the same - access is barred. OK, test2, let's get rid of the jobs location but require authentication to the server whole: change cupsd.conf to: DefaultAuthType Basic WebInterface Yes Location / AuthType Default Require valid-user Order allow,deny Allow @LOCAL /Location Policy default JobPrivateAccess default JobPrivateValues default SubscriptionPrivateAccess default SubscriptionPrivateValues default With this, everything works as expected (although of course now we need to be a valid user to print). Logging on to CUPS web interface as user1, every print job owned by user1 is fully shown, all other jobs show Name Unknown, User Withheld. So there's a problem with JobPrivateAccess picking up on Location /jobs (whereas JobPrivateValues does correctly recognise that location). Cheers Tim -- Next meeting: Bournemouth, Tuesday, 2014-01-07 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ New thread on mailing list: mailto:dorset@mailman.lug.org.uk How to Report Bugs Effectively: http://goo.gl/4Xue
[Dorset] NVidia graphics help please
Hi, I could do with some help. I recently installed a new Nvidia card and was able to get it working with a good resolution by trying to replace the 'nouveau' driver with the appropriate nvidia legacy driver. Then one day about a week ago after some kubuntu 13.10 updates it reverted to 1280x1024 which gives me quite a funny fat screen. I have tried all sort of things to get in back, but at one stage got it to 640x480. I cannot seem to get it working properly. This is what I just found in dmesg. [ 28.523214] NVRM: The NVIDIA GeForce4 MX 4000 GPU installed in this system is [ 28.523214] NVRM: supported through the NVIDIA 96.43.xx Legacy drivers. Please [ 28.523214] NVRM: visit http://www.nvidia.com/object/unix.html for more [ 28.523214] NVRM: information. The 304.88 NVIDIA driver will ignore [ 28.523214] NVRM: this GPU. Continuing probe... [ 28.523240] NVRM: No NVIDIA graphics adapter found! [ 28.652919] NVRM: The NVIDIA GeForce4 MX 4000 GPU installed in this system is [ 28.652919] NVRM: supported through the NVIDIA 96.43.xx Legacy drivers. Please [ 28.652919] NVRM: visit http://www.nvidia.com/object/unix.html for more [ 28.652919] NVRM: information. The 304.88 NVIDIA driver will ignore [ 28.652919] NVRM: this GPU. Continuing probe... [ 28.652941] NVRM: No NVIDIA graphics adapter found! lspci shows the nvidia card installed. Can anyone give me any hints about what I do now? Peter -- Next meeting: Bournemouth, Tuesday, 2014-01-07 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ New thread on mailing list: mailto:dorset@mailman.lug.org.uk How to Report Bugs Effectively: http://goo.gl/4Xue
Re: [Dorset] NVidia graphics help please
It looks like you've got the newer version of the nvidia drivers which do not support the card you are using any more. According to the errors in that log, you need use the older, legacy package found here: http://www.nvidia.com/object/linux-display-ia32-96.43.23-driver.html if you are running 32bit or here: http://www.nvidia.com/object/linux-display-amd64-96.43.23-driver.html if you are running 64bit. I'm not sure if kubuntu includes packages for those older nvidia drivers (which you should use if they do) but if they don't, downloading and installing the appropriate package should provide you with the correct driver version for your card. On 6 December 2013 14:21, Peter Merchant madsmad...@netscape.net wrote: Hi, I could do with some help. I recently installed a new Nvidia card and was able to get it working with a good resolution by trying to replace the 'nouveau' driver with the appropriate nvidia legacy driver. Then one day about a week ago after some kubuntu 13.10 updates it reverted to 1280x1024 which gives me quite a funny fat screen. I have tried all sort of things to get in back, but at one stage got it to 640x480. I cannot seem to get it working properly. This is what I just found in dmesg. [ 28.523214] NVRM: The NVIDIA GeForce4 MX 4000 GPU installed in this system is [ 28.523214] NVRM: supported through the NVIDIA 96.43.xx Legacy drivers. Please [ 28.523214] NVRM: visit http://www.nvidia.com/object/unix.html for more [ 28.523214] NVRM: information. The 304.88 NVIDIA driver will ignore [ 28.523214] NVRM: this GPU. Continuing probe... [ 28.523240] NVRM: No NVIDIA graphics adapter found! [ 28.652919] NVRM: The NVIDIA GeForce4 MX 4000 GPU installed in this system is [ 28.652919] NVRM: supported through the NVIDIA 96.43.xx Legacy drivers. Please [ 28.652919] NVRM: visit http://www.nvidia.com/object/unix.html for more [ 28.652919] NVRM: information. The 304.88 NVIDIA driver will ignore [ 28.652919] NVRM: this GPU. Continuing probe... [ 28.652941] NVRM: No NVIDIA graphics adapter found! lspci shows the nvidia card installed. Can anyone give me any hints about what I do now? Peter -- Next meeting: Bournemouth, Tuesday, 2014-01-07 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ New thread on mailing list: mailto:dorset@mailman.lug.org.uk How to Report Bugs Effectively: http://goo.gl/4Xue -- Andrew Montgomery-Hurrell Professional Geek Blog: http://darkliquid.co.uk Twitter: http://twitter.com/darkliquid Fiction: http://www.protagonize.com/author/darkliquid -- Next meeting: Bournemouth, Tuesday, 2014-01-07 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ New thread on mailing list: mailto:dorset@mailman.lug.org.uk How to Report Bugs Effectively: http://goo.gl/4Xue
Re: [Dorset] NVidia graphics help please
On 06/12/13 14:33, Andrew Montgomery-Hurrell wrote: It looks like you've got the newer version of the nvidia drivers which do not support the card you are using any more. According to the errors in that log, you need use the older, legacy package found here: http://www.nvidia.com/object/linux-display-ia32-96.43.23-driver.html if you are running 32bit or here: http://www.nvidia.com/object/linux-display-amd64-96.43.23-driver.html if you are running 64bit. I'm not sure if kubuntu includes packages for those older nvidia drivers (which you should use if they do) but if they don't, downloading and installing the appropriate package should provide you with the correct driver version for your card. On 6 December 2013 14:21, Peter Merchant madsmad...@netscape.net wrote: Hi, I could do with some help. I recently installed a new Nvidia card and was able to get it working with a good resolution by trying to replace the 'nouveau' driver with the appropriate nvidia legacy driver. Then one day about a week ago after some kubuntu 13.10 updates it reverted to 1280x1024 which gives me quite a funny fat screen. I have tried all sort of things to get in back, but at one stage got it to 640x480. I cannot seem to get it working properly. This is what I just found in dmesg. [ 28.523214] NVRM: The NVIDIA GeForce4 MX 4000 GPU installed in this system is [ 28.523214] NVRM: supported through the NVIDIA 96.43.xx Legacy drivers. Please [ 28.523214] NVRM: visit http://www.nvidia.com/object/unix.html for more [ 28.523214] NVRM: information. The 304.88 NVIDIA driver will ignore [ 28.523214] NVRM: this GPU. Continuing probe... [ 28.523240] NVRM: No NVIDIA graphics adapter found! [ 28.652919] NVRM: The NVIDIA GeForce4 MX 4000 GPU installed in this system is [ 28.652919] NVRM: supported through the NVIDIA 96.43.xx Legacy drivers. Please [ 28.652919] NVRM: visit http://www.nvidia.com/object/unix.html for more [ 28.652919] NVRM: information. The 304.88 NVIDIA driver will ignore [ 28.652919] NVRM: this GPU. Continuing probe... [ 28.652941] NVRM: No NVIDIA graphics adapter found! lspci shows the nvidia card installed. Can anyone give me any hints about what I do now? Peter I Know how that happened. In searching for a clue I came across a command line to apt-get install the nvidia software and did it. I did already have the firmware download that you mentioned from the first time that I got it working. When I try and run this script I get this message and I don't know how to get around it. ERROR: The kernel header file '/lib/modules/3.11.0-14-generic/build/include/linux/version.h' does not exist. The most likely reason for this is that the kernel source files in '/lib/modules/3.11.0-14-generic/build' have not been configured. I don't know what to do to configure this file. Peter -- Next meeting: Bournemouth, Tuesday, 2014-01-07 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ New thread on mailing list: mailto:dorset@mailman.lug.org.uk How to Report Bugs Effectively: http://goo.gl/4Xue
