- Arch-general - lists.archlinux.org

[arch-general] MUA
by Arvid Picciani 19 Nov '09

19 Nov '09

Mutt grows old and still doesn't do threads the way i want. i've tried sup, but find it too early in development. Especcially it is unusable slow. Can somone recommend another MUA? thanks -- Arvid Asgaard Technologies

22 32

[arch-general] Test - Sorry but good reason for it. Please ignore
by Geoff 19 Nov '09

19 Nov '09

Sorry to post a test message, but I am an infrequent poster whose e-mails have not been getting through. I wrote to the list admins about it a while ago but got no response, so I have unsubscribed / resubscribed.

3 6

[arch-general] pam settings INSECURE
by Caleb Cushing 18 Nov '09

18 Nov '09

so here's the problem I've discovered http://xenoterracide.blogspot.com/2009/11/bypassing-disabled-accounts-with-… < links to arch bug included posting here because I believe both kde's and arch's developers responses are less than satisfactory. This is a security bug an easy to fix without making users lives more difficult. so I'm starting with /etc/pam.d/login auth required pam_shells.so #add this: why let someone login who has an invalid shells. /etc/pam.d/kdm # I'm pretty sure it should be 99% the same as login since it allows logins. #%PAM-1.0 auth requisite pam_nologin.so auth required pam_unix.so nullok auth required pam_shells.so # as my blog says setting an invalid shell is a common way of disabling accounts. auth required pam_tally.so onerr=succeed file=/var/log/faillog # use this to lockout accounts for 10 minutes after 3 failed attempts #auth required pam_tally.so deny=2 unlock_time=600 onerr=succeed file=/ account required pam_access.so account required pam_time.so account required pam_unix.so password required pam_unix.so #password required pam_cracklib.so difok=2 minlen=8 dcredit=2 ocredit=2 ret #password required pam_unix.so md5 shadow use_authtok session required pam_unix.so session required pam_env.so session required pam_limits.so also I believe pam_tally2 replaces pam_tally may wish to consider migrating (non urgent next release?) -- Caleb Cushing http://xenoterracide.blogspot.com

9 15

Re: [arch-general] arch-general Digest, Vol 61, Issue 39
by jelle van der waa 18 Nov '09

18 Nov '09

Re: We need a maintained-by-TU chrome/chromium... (Juan Diego) There are enough arch user maintained repo's, you could ask them to package it beside that how much work is AUR ;) 2009/11/18 <arch-general-request(a)archlinux.org> > Send arch-general mailing list submissions to > arch-general(a)archlinux.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://mailman.archlinux.org/mailman/listinfo/arch-general > or, via email, send a message with subject or body 'help' to > arch-general-request(a)archlinux.org > > You can reach the person managing the list at > arch-general-owner(a)archlinux.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of arch-general digest..." > > > Today's Topics: > > 1. Re: MUA (Alexandr Bashmakov) > 2. Re: pam settings INSECURE (bender02) > 3. Re: pam settings INSECURE (Xavier) > 4. Re: pam settings INSECURE (bender02) > 5. Re: pam settings INSECURE (Jan de Groot) > 6. We need a maintained-by-TU chrome/chromium... (Hamo) > 7. Re: pam settings INSECURE (Xavier) > 8. Re: We need a maintained-by-TU chrome/chromium... (Daenyth Blank) > 9. Re: We need a maintained-by-TU chrome/chromium... (Juan Diego) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 18 Nov 2009 17:26:04 +0700 > From: Alexandr Bashmakov <alex.teorver(a)gmail.com> > Subject: Re: [arch-general] MUA > To: General Discusson about Arch Linux <arch-general(a)archlinux.org> > Message-ID: > <7d16d2700911180226q14e0d1bbtf1ad3095687a38a5(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > http://notmuchmail.org/ > > > ------------------------------ > > Message: 2 > Date: Wed, 18 Nov 2009 12:58:46 +0100 > From: bender02 <bender02(a)archlinux.us> > Subject: Re: [arch-general] pam settings INSECURE > To: General Discusson about Arch Linux <arch-general(a)archlinux.org> > Message-ID: > <6eefa5460911180358n14f3937esc3a3dea388c09ef3(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > 2009/11/18 Ng Oon-Ee <ngoonee(a)gmail.com>: > > The *disadvantage* is that the devs/maintainers have to patch up-stream. > > This should be kept to a minimum, primarily to reduce their workload, > > and also because it is ASSUMED that if you use Arch, you're capable of > > doing the Right Thing (tm) according to your situation, or at least > > finding out how to. > > If you would take the time to look at the packages that are involved > in this (namely shadow and kdebase-workspace), you'd see that both > /etc/pam.d/login and /etc/pam.d/kde are manually suplied alongside the > PKGBUILDs. So in this case, it's not "patching" but straight > "replacing" the "upstream". > > > ------------------------------ > > Message: 3 > Date: Wed, 18 Nov 2009 14:07:39 +0100 > From: Xavier <shiningxc(a)gmail.com> > Subject: Re: [arch-general] pam settings INSECURE > To: General Discusson about Arch Linux <arch-general(a)archlinux.org> > Message-ID: > <91752840911180507l43f7899ncea46da9f73e2e1e(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > On Wed, Nov 18, 2009 at 6:40 AM, Caleb Cushing <xenoterracide(a)gmail.com> > wrote: > > so here's the problem I've discovered > > > http://xenoterracide.blogspot.com/2009/11/bypassing-disabled-accounts-with-… > > < links to arch bug included posting here because I believe both kde's > > and arch's developers responses are less than satisfactory. This is a > > security bug an easy to fix without making users lives more difficult. > > > > so I'm starting with /etc/pam.d/login > > > > auth ? ? ? ?required ? ?pam_shells.so #add this: why let someone login > > who has an invalid shells. > > > > > > /etc/pam.d/kdm # I'm pretty sure it should be 99% the same as login > > since it allows logins. > > > > #%PAM-1.0 > > auth ? ? ? ?requisite ? pam_nologin.so > > auth ? ? ? ?required ? ?pam_unix.so nullok > > auth ? ? ? ?required ? ?pam_shells.so # as my blog says setting an > > invalid shell is a common way of disabling accounts. > > auth ? ? ? ?required ? ?pam_tally.so onerr=succeed file=/var/log/faillog > > # use this to lockout accounts for 10 minutes after 3 failed attempts > > #auth ? ? ? required ? ?pam_tally.so deny=2 unlock_time=600 onerr=succeed > file=/ > > account ? ? required ? ?pam_access.so > > account ? ? required ? ?pam_time.so > > account ? ? required ? ?pam_unix.so > > password ? ?required ? ?pam_unix.so > > #password ? required ? ?pam_cracklib.so difok=2 minlen=8 dcredit=2 > ocredit=2 ret > > #password ? required ? ?pam_unix.so md5 shadow use_authtok > > session ? ? required ? ?pam_unix.so > > session ? ? required ? ?pam_env.so > > session ? ? required ? ?pam_limits.so > > > > also I believe pam_tally2 replaces pam_tally may wish to consider > > migrating (non urgent next release?) > > > > So basically you just need to add "auth required > pam_shells.so" to all pam files related to login, correct ? > Or what were the other problematic settings of pam.d/kde ? > > The comments about this being an upstream problem are invalid, as > these pam files are all shipped by arch : > http://repos.archlinux.org/wsvn/packages/kdebase-workspace/trunk/ > http://repos.archlinux.org/wsvn/packages/shadow/trunk/login > > Note that this problem probably exists with all login managers. For > example gdm does not have pam_shells.so either. > http://repos.archlinux.org/wsvn/packages/gdm/trunk/ > > And I am curious to know what the pam settings of other distro are > (debian,fedora,gentoo,..). > > Finally, maybe it makes sense to try keeping all the different pam > login files as consistent as possible. But I don't know enough about > pam to tell. > > > ------------------------------ > > Message: 4 > Date: Wed, 18 Nov 2009 14:17:24 +0100 > From: bender02 <bender02(a)archlinux.us> > Subject: Re: [arch-general] pam settings INSECURE > To: General Discusson about Arch Linux <arch-general(a)archlinux.org> > Message-ID: > <6eefa5460911180517m50a1edcbt518c04950f7203bb(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > On Wed, Nov 18, 2009 at 2:07 PM, Xavier <shiningxc(a)gmail.com> wrote: > > And I am curious to know what the pam settings of other distro are > > (debian,fedora,gentoo,..). > > > > Finally, maybe it makes sense to try keeping all the different pam > > login files as consistent as possible. But I don't know enough about > > pam to tell. > > Some other distros (opensuse, ubuntu, fedora at least) use > 'common-auth' (and probably some other 'common-*' files) in > /etc/pam.d/, which are then included in the particular pam files. > Hence all pam files are consistent. On the other hand, if you need > more fine-grained control, you need to edit and consolidate more files > than with the current arch setup. [I like arch's system better, but > who cares about that :)] > > > ------------------------------ > > Message: 5 > Date: Wed, 18 Nov 2009 14:24:24 +0100 > From: Jan de Groot <jan(a)jgc.homeip.net> > Subject: Re: [arch-general] pam settings INSECURE > To: General Discusson about Arch Linux <arch-general(a)archlinux.org> > Message-ID: <1258550664.4737.4.camel@jan> > Content-Type: text/plain; charset="UTF-8" > > On Wed, 2009-11-18 at 14:17 +0100, bender02 wrote: > > On Wed, Nov 18, 2009 at 2:07 PM, Xavier <shiningxc(a)gmail.com> wrote: > > > And I am curious to know what the pam settings of other distro are > > > (debian,fedora,gentoo,..). > > > > > > Finally, maybe it makes sense to try keeping all the different pam > > > login files as consistent as possible. But I don't know enough about > > > pam to tell. > > > > Some other distros (opensuse, ubuntu, fedora at least) use > > 'common-auth' (and probably some other 'common-*' files) in > > /etc/pam.d/, which are then included in the particular pam files. > > Hence all pam files are consistent. On the other hand, if you need > > more fine-grained control, you need to edit and consolidate more files > > than with the current arch setup. [I like arch's system better, but > > who cares about that :)] > > The reason for shipping custom pam files is because we don't have > common-* files in arch. The gdm file is a straight copy from the login > file, with some added modules for gnome-keyring to get that daemon > started on login. With common-auth, we could just @include common-auth > from the pam file, which is much easier. > > > > ------------------------------ > > Message: 6 > Date: Wed, 18 Nov 2009 21:48:26 +0800 > From: Hamo <hamo.by(a)gmail.com> > Subject: [arch-general] We need a maintained-by-TU chrome/chromium... > To: arch-general(a)archlinux.org > Message-ID: > <55b9903b0911180548r19eda9b9x1687aab9085c11eb(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Dear Archlinux users, > Chrome is likely to be a daily-use web browser and with the Chrome OS > releasing,it will become more and more reliable.Archlinux is a > rolling-release distribution and it aims at being bleeding edge.So we > should have a maintained-by-TU chrome/chromium and it is really > useful... > > -- > Nick Name:Hamo > Website:http://hamobai.com/ > > > ------------------------------ > > Message: 7 > Date: Wed, 18 Nov 2009 14:52:42 +0100 > From: Xavier <shiningxc(a)gmail.com> > Subject: Re: [arch-general] pam settings INSECURE > To: General Discusson about Arch Linux <arch-general(a)archlinux.org> > Message-ID: > <91752840911180552u6626b43at10e6e2c7667a2426(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > On Wed, Nov 18, 2009 at 2:24 PM, Jan de Groot <jan(a)jgc.homeip.net> wrote: > > On Wed, 2009-11-18 at 14:17 +0100, bender02 wrote: > >> On Wed, Nov 18, 2009 at 2:07 PM, Xavier <shiningxc(a)gmail.com> wrote: > >> > And I am curious to know what the pam settings of other distro are > >> > (debian,fedora,gentoo,..). > >> > > >> > Finally, maybe it makes sense to try keeping all the different pam > >> > login files as consistent as possible. But I don't know enough about > >> > pam to tell. > >> > >> Some other distros (opensuse, ubuntu, fedora at least) use > >> 'common-auth' (and probably some other 'common-*' files) in > >> /etc/pam.d/, which are then included in the particular pam files. > >> Hence all pam files are consistent. On the other hand, if you need > >> more fine-grained control, you need to edit and consolidate more files > >> than with the current arch setup. [I like arch's system better, but > >> who cares about that :)] > > > > The reason for shipping custom pam files is because we don't have > > common-* files in arch. The gdm file is a straight copy from the login > > file, with some added modules for gnome-keyring to get that daemon > > started on login. With common-auth, we could just @include common-auth > > from the pam file, which is much easier. > > > > > > That sounds good. > I filed http://bugs.archlinux.org/task/17188 > > > ------------------------------ > > Message: 8 > Date: Wed, 18 Nov 2009 08:54:40 -0500 > From: Daenyth Blank <daenyth+arch(a)gmail.com <daenyth%2Barch(a)gmail.com>> > Subject: Re: [arch-general] We need a maintained-by-TU > chrome/chromium... > To: General Discusson about Arch Linux <arch-general(a)archlinux.org> > Message-ID: > <ea09a6380911180554w59527b1bg81fd22d94fa75d55(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > On Wed, Nov 18, 2009 at 08:48, Hamo <hamo.by(a)gmail.com> wrote: > > Dear Archlinux users, > > Chrome is likely to be a daily-use web browser and with the Chrome OS > > releasing,it will become more and more reliable.Archlinux is a > > rolling-release distribution and it aims at being bleeding edge.So we > > should have a maintained-by-TU chrome/chromium and it is really > > useful... > > > If you're interested, I recommend finding a sponsor so that you can > apply... > > There are lots of software projects that would be good to have, but it > only makes sense to keep them in the repos if someone is interested in > maintaining them. > > > ------------------------------ > > Message: 9 > Date: Wed, 18 Nov 2009 23:05:06 +0900 > From: Juan Diego <juantascon(a)gmail.com> > Subject: Re: [arch-general] We need a maintained-by-TU > chrome/chromium... > To: General Discusson about Arch Linux <arch-general(a)archlinux.org> > Message-ID: > <b3095c50911180605h211fe211oee2a7b3902ab482a(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > I would be happy to maintain that package, but unfortunately Im not a TU > > dont you think archlinux should have something similar to ppa from > ubuntu so that it will be easier to maintain and promote personal > repositories, aur is a good option but if I would have to choose > between using a packages from aur or using a package from a personal > repository from somebody I wouldnt think it twice, I would choose the > personal repo one. > > On Wed, Nov 18, 2009 at 10:54 PM, Daenyth Blank <daenyth+arch(a)gmail.com<daenyth%2Barch(a)gmail.com>> > wrote: > > On Wed, Nov 18, 2009 at 08:48, Hamo <hamo.by(a)gmail.com> wrote: > >> Dear Archlinux users, > >> Chrome is likely to be a daily-use web browser and with the Chrome OS > >> releasing,it will become more and more reliable.Archlinux is a > >> rolling-release distribution and it aims at being bleeding edge.So we > >> should have a maintained-by-TU chrome/chromium and it is really > >> useful... > >> > > If you're interested, I recommend finding a sponsor so that you can > apply... > > > > There are lots of software projects that would be good to have, but it > > only makes sense to keep them in the repos if someone is interested in > > maintaining them. > > > > > ------------------------------ > > _______________________________________________ > arch-general mailing list > arch-general(a)archlinux.org > http://mailman.archlinux.org/mailman/listinfo/arch-general > > > End of arch-general Digest, Vol 61, Issue 39 > ******************************************** > -- Jelle

2 1

[arch-general] archlinuxfr bad virtualbox_bin-3.0.10-1 package
by David C. Rankin 18 Nov '09

18 Nov '09

Guys, The archlinuxfr server has a bad virtualbox package on it. There is a lot of things virtualbox is, but one thing it isn't is an 8 meg package: :: Retrieving packages from archlinuxfr... error: failed retrieving file 'virtualbox_bin-3.0.10-1-x86_64.pkg.tar.bz2' from repo.archlinux.fr : Not Found 22:57 alchemy:~/img/arch> pms virtualbox_bin :: Synchronizing package databases... testing is up to date core is up to date extra is up to date community-testing is up to date community is up to date archlinuxfr is up to date resolving dependencies... looking for inter-conflicts... Targets (1): virtualbox_bin-3.0.10-1 Total Download Size: 8.09 MB Total Installed Size: 88.87 MB Probably just a bad rsync... -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com

7 9

[arch-general] First install of gnome on Arch, pretty cool... (new artwork this time :-)
by David C. Rankin 18 Nov '09

18 Nov '09

Guys, Looking at the new desktop, I just had to take a screenshot and share. I never install gnome, but since I had enlightenment installed and a bunch of bits and pieces of gnome installed --> Why not? Working with it for a short period of time, I was quite pleased with it. Compiz works great with it, dark themes work as well. The base install is really crisp like kde3 was. (but like any desktop, you load it down with enough bells and whistles it slows down a bit) Long story short, I created a new cube cap for Arch (since it was pointed out my first set was of the old logo) and when done, I just had to send the screenshot in, so: (82k) http://www.3111skyline.com/download/ss/arch/archGnomeCompiz.jpg The Artwork for the caps: (108k) http://www.3111skyline.com/download/Archlinux/compiz/archCaps.png If you like the artwork, use it at will... -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com

3 3

[arch-general] only detect 1 cpu
by viodreamlistas＠gmail.com 17 Nov '09

17 Nov '09

Hi all! I have got a quad core procesor but my archlinux only detect 1 cpu. --- $ uname -a Linux Nemesis 2.6.31-ARCH #1 SMP PREEMPT Fri Oct 23 10:03:24 CEST 2009 x86_64 Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz GenuineIntel GNU/Linux --- $ cat /proc/cpuinfo cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz cpu cores : 1 .... --- I dont know how to do to detect the 4 cpus. Any sugestions? Thanks in advance! PD: Sorry for mi english. -- V!ODREAM

4 4

Re: [arch-general] old firewire stack?
by Roberto Malinverni 16 Nov '09

16 Nov '09

> I believe the kernel can only have 1 compiled at a time, so > you'll have to compile a custom kernel with the new stack... You _can_ compile both of them, but you need to blacklist the modules you don't want to use. > Last time we visited this topic, the new stack was incomplete > and unstable, and it also said so in the kernel configuration > menu. As I don't have any firewire devices, I never really > cared. Should we dump the old stack and switch to the new one > in the upgrade to 2.6.32? The Fedora Team switched to the new stack around fedora 8/9, causing a lot of troubles to the users: third party repos began then to offer the "old" modules as an addon. As for myself, the new stack couldn't even see my firewire external HD while the old stack worked fine - don't know with other kind of hardware. Roberto -- Il messaggio e' stato analizzato alla ricerca di virus o contenuti pericolosi da MailScanner, ed e' risultato non infetto.

2 1

[arch-general] netcfg v2.5 in [testing] - auto wireless configuration has changed
by James Rayner 15 Nov '09

15 Nov '09

netcfg v2.5rc1 This is easily the biggest release since 2.0. Many new features and some significant changes under the hood. There are also a few features which have had changed options and this needs to be noted. The most notable is that net-auto has been removed in favour of the net auto wireless setup. # Move to new auto-wireless The new automatic connection has proper roaming support and will prove more reliable than the old setup - particularly with more complicated wireless configurations. To migrate to the new automatic wireless setup: 1. pacman -S core/wpa_actiond 2. Set WIRELESS_INTERFACE="" to your wireless interface in /etc/rc.conf. For example WIRELESS_INTERFACE="wlan0" 3. Add net-auto-wireless to your DAEMONS=() array. # New features: - net-auto-wireless/wpa_actiond - Real wireless roaming/auto connection. Based on same principle as autowifi. Requires optional dependency: wpa_actiond - net-auto-wired - automatic ethernet configuration. Requires optional dependency: ifplugd - Interface configurations - set options for all profiles using an interface - Radio Kill switch awareness - requires enabling, see wiki. - Output hooks - Significant internal cleanup & improvement # Internal changes: - Uses wpa_supplicant for all wireless configuration by default, including wep/none security. This adds improves support for most and should improve reliability. - Uses iproute by default for all static configuration. net_tools which contains ifconfig is effectively obsolete and hasnt seen a release for over 8 years. The 'ethernet-iproute' and 'ethernet' connection types have been merged together to simply 'ethernet'. All options are still supported and existing configurations will continue to work for both types. A symlink has been made to ensure that profiles using 'ethernet-iproute' will continue to function. # Changes in configuration options - net-auto and AUTO_NETWORKS is now deprecated in favour of net-auto-wireless/net-auto-wired. - wireless: If you were previously specifying the wpa_supplicant driver in WPA_OPTS, you now need to specify it in WPA_DRIVER. - wireless: iwconfig based configuration for wep/none can be used by changing to wep-old or none-old. This should not be necessary and is left in place only for the possibility of very old drivers that do not support wpa_supplicant. - ethernet-iproute: Now that 'ethernet' is iproute based, those using 'ethernet-iproute' can change the name back. There is a symlink in place however, so existing configurations of either name will continue to function regardless. - wireless-dbus: This idea didn't really go anywhere and is now unsupported. The wpa_supplicant dbus interface is a huge pain and it doesn't fit well into the netcfg codebase. It is no longer included, however netcfg will automatically use 'wireless' for any 'wireless-dbus' configurations as the supported options are effectively the same. # Download: netcfg 2.5rc1 is in [testing]. The source is on the Arch Linux ftp and latest PKGBUILD in svn. ftp://ftp.archlinux.org/other/netcfg/netcfg-2.5.0rc1.tar.gz # Documentation: The wiki has been updated to reflect this release. For 2.5, the documentation can be found at: http://wiki.archlinux.org/index.php/Network_Profiles_development When it is released this will be moved to the Network Profiles page. There's also some updated documentation of the supported options for 'wireless' and 'ethernet' here: http://www.rayner.id.au/netcfg/ Keep in mind that wireless supports all the options of 'ethernet'. If options are not documented, then it's a bug and they should be (or it's deprecated, but should be mentioned anyway for completeness). # Contributors: I had a few big contributors to this release: Jim Pryor: Many internal changes and improvements Thomas Bächler: wpa_actiond based auto roaming/connection Thanks guys! That's all for now, please file any bug reports on the bug tracker. James

3 2

[arch-general] CUPS won't detect my usb printer
by Jim Burton 15 Nov '09

15 Nov '09

Hi, I'm new to arch and unable to set up my (USB) Canon printer. I've read quite a large number of threads on the forum about this and suppose my solution is in there somewhere but cups doesn't recognise my printer for some reason. Here's what I've tried: I've installed cups, ghostscript, gsfonts and gutenprint and blacklisted usblp. My printer is picked up by lsusb: Bus 005 Device 003: ID 04a9:1094 Canon, Inc. PIXMA iP3000x Printer and I think it has the right permissions: [jim@daisy ~]$ ls -l /dev/bus/usb/005/003 crw-rw---- 1 root lp 189, 514 2009-11-15 13:44 /dev/bus/usb/005/003 In the web interface when I go to add a printer there are none found. I have set cups logging to debug but there's nothing there that means anything to me. Here is some of the output when I try to find the printer in the web interface: D [15/Nov/2009:13:45:09 +0000] cupsdReadClient: 15 1.1 CUPS-Get-Printers 1 D [15/Nov/2009:13:45:09 +0000] CUPS-Get-Printers D [15/Nov/2009:13:45:09 +0000] CUPS-Get-Printers client-error-not-found: No destinations added. D [15/Nov/2009:13:45:09 +0000] Returning IPP client-error-not-found for CUPS-Get-Printers (no URI) from localhost D [15/Nov/2009:13:45:09 +0000] cupsdReadClient: 15 POST / HTTP/1.1 D [15/Nov/2009:13:45:09 +0000] cupsdAuthorize: No authentication data provided. D [15/Nov/2009:13:45:09 +0000] cupsdReadClient: 15 1.1 CUPS-Get-Devices 1 D [15/Nov/2009:13:45:09 +0000] CUPS-Get-Devices D [15/Nov/2009:13:45:09 +0000] cupsdIsAuthorized: username="" D [15/Nov/2009:13:45:09 +0000] Returning HTTP Unauthorized for CUPS-Get-Devices (no URI) from localhost D [15/Nov/2009:13:45:09 +0000] cupsdSendHeader: 15 WWW-Authenticate: Basic realm="CUPS", trc="y" D [15/Nov/2009:13:45:09 +0000] [CGI] cgi_null_passwd(prompt="Password for daemon on localhost? ") called! D [15/Nov/2009:13:45:09 +0000] [CGI] lang="en_US.UTF8", locale="/en_US"... D [15/Nov/2009:13:45:09 +0000] [CGI] lang="en_US.UTF8", locale="/en_US"... D [15/Nov/2009:13:45:09 +0000] cupsdReadClient: 15 WAITING Closing on EOF D [15/Nov/2009:13:45:09 +0000] cupsdCloseClient: 15 D [15/Nov/2009:13:45:09 +0000] cupsdSetBusyState: Not busy D [15/Nov/2009:13:45:09 +0000] PID 2650 (/usr/lib/cups/cgi-bin/admin.cgi) exited with no errors. D [15/Nov/2009:13:45:39 +0000] cupsdReadClient: 12 WAITING Closing on EOF D [15/Nov/2009:13:45:39 +0000] cupsdCloseClient: 12 What should I try next? Thanks, Jim

5 8