|
|||||||||||
|
debian-user-digest Digest V2007 #3009
From: <debian-user-digest-request(at)lists.debian.org>
Date: Sat Dec 15 2007 - 17:57:59 EST
debian-user-digest Digest Volume 2007 : Issue 3009 Today's Topics: Re: Using exim as SMTP-AUTH client [ Felix Karpfen
Date: Sat, 15 Dec 2007 19:03:44 +0000 (UTC)
From: Felix Karpfen <felixk@webone.com.au>
To: debian-user@lists.debian.org
Message-ID: On Thu, 13 Dec 2007 16:49:09 -0500, Celejar wrote: > On Thu, 13 Dec 2007 20:24:14 +0000 (UTC) >>=20 > see this thread for an account of some trouble I once had using exim That reference helped a lot! My error message, when attempting to send mail from my GMail account, was (from memory) virtually identical with that quoted in the bug report. Given that I have exim4/4.63-17, I may be lucky; the bug has been fixed. I shall soon know if that was the problem; at least, I now know where to look. Many thanks Felix
--=20
Date: Sat, 15 Dec 2007 13:24:53 -0600 (CST)
From: Jude DaShiell <jdashiel@shellworld.net>
To: debian-user@lists.debian.org
I have a couple different email accounts one has pop address as incoming.verizon.net and another has incoming email address of mail.shellworld.net and the same for outgoing address. Having had a look at the alpine configuration file, it doesn't appear to have a place to document the incoming email address be it pop or imap unless I'm missing something here.
Date: Sat, 15 Dec 2007 21:46:58 +0100
Message-Id: <200712152146.59026.cave.dnb@tiscali.fr> Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit
On Wednesday 12 December 2007 20:23, Peter Werner wrote:
Thanks Peter for your reply, and the link. Unfortunately it only deals with Aptitude, and Dpkg, and there appears to be no way to put a hold on an individual package with Apt ( at least not on the Apt version on Fedora). I also posted this question to apt-rpm@lists.laiskiainen.org. Someone there suggested pinning, and having tried various incantations in /etc/apt/preferences, this one appears to work.
Package: fltk
The fltk version 1.1.7* is referring to fltk-1.1.7-1.fc5, which is the installed version of fltk, and installed using rpm -Uvh <path to fltk package>. I replaced the fltk-1.1.8-0.3.r5750.fc7 version with the fc5 version, as the fc7 version creates problems with ZynnAddSubFX. Ignore the rpm stuff as it refers to Fedora, but apart from that the pinning appears to be working ok. I ran an apt-get update, and no warning about pinning problems. Followed that with an apt-get dist-upgrade -s, and got no packages to be upgraded, which confirmed that the pinning was working. Opened Synaptic, and installed version of fltk was showing as 1.1.7-1.fc5, and available version of fltk is also showing as 1.1.7-1.fc5, which again showed that the pinning was working. Thanks again for your help with an Apt problem on Fedora, and btw, I still havn't had a reply to this problem I sent to the Fedora list. They're probably too occupied with Yum problems, or just didn't have an answer. Nigel.
Date: Sat, 15 Dec 2007 14:47:04 -0600
boundary="----=_Part_3201_21460621.1197751624335" ------=_Part_3201_21460621.1197751624335 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline I am running Debian Sid with a 2.6.10 kernel and an HP OfficeJet 5510 All-In-One printer attached through a USB port, using CUPS for all printing. Since updating my entire installation recently, I have not been able to communicate with the printer, although it was working previously. The problem exists whether I use the CUPS admin web-browser application, or the HPLIP utilities. In web searches of the HPLIP web site and various email forums, I have found information about previous similar problems in HPLIP, but most are regarding old problems that have been fixed, and none of the more recent suggestions have worked for me. Here are the errors I see in /var/log/syslog.
Dec 15 13:32:14 fwy-li officejet_5500_series?serial=MY55DG135K96:
io/hpmud/musb.c 549: invalid product id string: Operation not permitted
Dec 15 13:32:14 fwy-li officejet_5500_series?serial=MY55DG135K96:
io/hpmud/musb.c 1003: unable to open
Here are relevant installed packages.
fwy-li:/home/fwy# dpkg -l "hp*" cupsys
+++-==============-==============-============================================ ii cupsys 1.3.4-2 Common UNIX Printing System(tm) - server pn hp-ppd Here is the output of the 'lsusb' command, where is appears that the device is recognized properly.
fwy-li:/home/fwy# lsusb
Here is the output of the 'hp-probe' command, which also looks correct. fwy-li:/home/fwy# hp-probe -busb HP Linux Imaging and Printing System (ver. 2.7.10) Printer Discovery Utility ver. 4.0 Copyright (c) 2001-7 Hewlett-Packard Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. | DEVICE DISCOVERY | Device URI Model ------------------------------------------------- ------------------------ hp:/usb/officejet_5500_series?serial=MY55DG135K96 HP officejet 5500 series Found 1 printer(s) on the 'usb' bus. Here is the output of the '/usr/lib/cups/backend/hp' command. fwy-li:/home/fwy# /usr/lib/cups/backend/hp direct hp:/usb/officejet_5500_series?serial=MY55DG135K96 "HP officejet 5500 series" "HP officejet 5500 series USB MY55DG135K96 HPLIP" "MFG:HP;MDL:officejet 5500 series;CLS:PRINTER;DES:officejet 5500 series;SN:MY55DG135K96;" And finally, here is the output of the 'lpinfo -l -v' command.
fwy-li:/home/fwy# lpinfo -l -v
class = network
info = AppSocket/HP JetDirect
make-and-model = Unknown
device-id =
Device: uri = beh
class = network
info = Backend Error Handler
make-and-model = Unknown
device-id =
Device: uri = hpfax
class = direct
info = HP Fax (HPLIP)
make-and-model = Unknown
device-id =
Device: uri = hp
class = direct
info = HP Printer (HPLIP)
make-and-model = Unknown
device-id =
Device: uri = http
class = network
info = Internet Printing Protocol (http)
make-and-model = Unknown
device-id =
Device: uri = ipp
class = network
info = Internet Printing Protocol (ipp)
make-and-model = Unknown
device-id =
Device: uri = lpd
class = network
info = LPD/LPR Host or Printer
make-and-model = Unknown
device-id =
Device: uri = parallel:/dev/lp0
class = direct
info = LPT #1
make-and-model = Unknown
device-id =
Device: uri = scsi
class = direct
info = SCSI Printer
make-and-model = Unknown
device-id =
Device: uri = smb
class = network
info = Windows Printer via SAMBA
make-and-model = Unknown
The HPLIP Toolbox application (hp-toolbox) sees the printer with the correct URL, but cannot communicate with it. It displays the message 'ERROR: Device not found. Please check connection and power-on device.' I have tried setting up the printer using both hp-setup and CUPS, with the same results. Yet the physical USB connection is fine and the power is on. Based on similar postings I have seen on the web, I have tried changing the URL from the default hp:/usb/officejet_5500_series?serial=MY55DG135K96 to usb://hp/officejet%205500%20series?serial=MY55DG135K96, but this caused CUPS to think that the printer was disconnected. Other postings suggested that permissions or other information set in the udev rules files (/etc/udev/rules.d/*) were causing problems. However, I am not using udev, so I don't think these points are relevant. Is this a bug in the Debian hplip 2.7.10 package?
Thx in advance,
------=_Part_3201_21460621.1197751624335 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline I am running Debian Sid with a 2.6.10 kernel and an HP OfficeJet 5510 All-In-One printer attached through a USB port, using CUPS for all printing. Since updating my entire installation recently, I have not been able to communicate with the printer, although it was working previously. The problem exists whether I use the CUPS admin web-browser application, or the HPLIP utilities. In web searches of the HPLIP web site and various email forums, I have found information about previous similar problems in HPLIP, but most are regarding old problems that have been fixed, and none of the more recent suggestions have worked for me. ii hplip-gui 2.7.10-5 HP Linux Printing and Imaging - GUI utilitie<br>pn hplip-ppds <none> (no description available)<br>pn hpoj <none> (no description available)<br> un hpoj-xojpanel <none> (no description available)<br>pn hpscanpbm <none> (no description available)<br>pn hpsockd <none> (no description available)<br><br><br>Here is the output of the 'lsusb' command, where is appears that the device is recognized properly.
------=_Part_3201_21460621.1197751624335--
Date: Sat, 15 Dec 2007 16:08:24 -0500
Message-ID: <20071215160824.752084a2@localhost> Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Sun, 2 Dec 2007 13:18:22 +0000 (UTC) debian-user-digest-request@lists.debian.org wrote: > This is still very much a work in progress, so anybody with comments Thanks Dave. I tried this and it seems to work well (using thunar). So, I've tossed most of gnome, and am using fluxbox exclusively now. Mark
Date: Sat, 15 Dec 2007 13:28:50 -0800
Message-id: <20071215212850.GA16514@alpaca> Content-type: text/plain; charset=us-ascii Content-disposition: inline
On Sat, Dec 15, 2007 at 09:46:58PM +0100, Nigel Henry <cave.dnb@tiscali.fr> was heard to say:
Apt and aptitude will read dpkg hold states. Daniel
Date: Sat, 15 Dec 2007 23:30:29 +0200
Message-ID: <880dece00712151330p2a891c13qcb63a8c389630b98@mail.gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 Content-Disposition: inline T24gMTQvMTIvMjAwNywgQnJhZCBSb2dlcnMgPGJyYWRAZmluZWJ5Lm1lLnVrPiB3cm90ZToKPiBU aGUgd2VpcmRlc3QgdGhpbmcgSSd2ZSBzZWVuIGlzIGEgcHJvZ3JhbW1hYmxlIHJlbW90ZSBjb250 cm9sbGVyIChmb3IKPiBUVnMsIFZDUnMsIGV0Yy4pIHdoaWNoIGNhbiBiZSB1cGRhdGVkIGZyb20g dGhlIHN1cHBsaWVycyB3ZWIgc2l0ZS4KPiBKdXN0IHB1dCB0aGUgdm9sdW1lIHJpZ2h0IHVwIG9u IHlvdXIgUENzIHNwZWFrZXJzLCBhbmQgaG9sZCB0aGUKPiBjb250cm9sbGVyIHZlcnkgY2xvc2Ug dG8gdGhlIGNvbmUgb2Ygb25lIG9mIHRoZSBzcGVha2Vycy4KPiBPaCwgYW5kIEknZCByZWNvbW1l bmQgd2VhcmluZyBlYXItcGx1Z3Mgd2hpbHN0IHlvdSdyZSBkb2luZyBpdCwKPiB0b28uICAgOi0p CgpXZSBoYXZlIHRoYXQgYXQgaG9tZSwgdG9vLiBXZWxsLCBhdCBsZWFzdCB0aGUgd2lmZSB0aGlu a3Mgc28uIFRoYXQncwpob3cgc2hlIHByb2dyYW1zIG1lLiBJJ2xsIHRyeSB0aGUgZWFyLXBsdWdz IHRpcCwgdGhhbmtzIQoKRG90YW4gQ29oZW4KCmh0dHA6Ly93aGF0LWlzLXdoYXQuY29tCmh0dHA6 Ly9naWJiZXJpc2guY28uaWwK15At15Et15It15Mt15Qt15Ut15Yt15ct15gt15kt15ot15st15wt 150t154t158t16At16Et16It16Mt16Qt16Ut16Yt16ct16gt16kt16oKCkE6IEJlY2F1c2UgaXQg bWVzc2VzIHVwIHRoZSBvcmRlciBpbiB3aGljaCBwZW9wbGUgbm9ybWFsbHkgcmVhZCB0ZXh0LgpR OiBXaHkgaXMgdG9wLXBvc3Rpbmcgc3VjaCBhIGJhZCB0aGluZz8K
Date: Sat, 15 Dec 2007 15:46:09 -0600
protocol="application/pgp-signature"; boundary="ibTvN161/egqYuK8"
Content-Disposition: inline
--ibTvN161/egqYuK8 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable
On Wed, 2007.12.05 10:14, Douglas A. Tutty wrote:
I've been through the BIOS, but there are no diagnostics available there. --ibTvN161/egqYuK8 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE-----
iD8DBQFHZEsh9XC8Sh1vpNARAmmJAKCBb6qsM1Kd2GAM4lMuVS2q9ozjdwCfT1k0
Ixmus9OnVGUzzh0KDhKLXw8=
Date: Sat, 15 Dec 2007 21:51:57 +0000
--Sig_/g_8dS+QUbp/zQNEzwV_94u/
On Sat, 15 Dec 2007 23:30:29 +0200
Hello Dotan, > We have that at home, too. Well, at least the wife thinks so. That's YW. :-)
--=20
/ ) "The blindingly obvious is
/ _)rad never immediately apparent"
I don't believe you have to be an idiot to get somewhere these days Bombsite Boy - The Adverts
--Sig_/g_8dS+QUbp/zQNEzwV_94u/
-----BEGIN PGP SIGNATURE-----
iD8DBQFHZEx/SXvR9Iq2E38RAjUzAJsFCixr8iTxg2bomm+vUPLjXz4gMQCfbcAs
MfxfHhuP8aKoFAs073h1Jug=
Date: 15 Dec 2007 09:27:53 -0800
"abdelkader belahcene" <abelahcene@gmail.com> writes: > Hi, `apt-cache search pcb` shows: pcb - printed circuit board (pcb) design program gerbv - Gerber file viewer for PCB design kicad - Electronic schematic and PCB design software -- Carl Johnson carlj@peak.org End of debian-user-digest Digest V2007 Issue #3009 **************************************************Received on Sat Dec 15 17:58:13 2007 This archive was generated by hypermail 2.1.8 : Wed Mar 19 2008 - 02:58:02 EDT |
||||||||||
|
|||||||||||