Face and disreputable clothes walked.
Vaigwra S0tf Tabs 4.19 Propeuica 1.04 Cailris 5.63 Geneeirc Vacigra 3.54 Zowloft 1.14 Lorazeppam 1.79 Vafilum 2.86 Paxhil 2.07 Sovma 1.32 Testosttreone 8.10 Ziihtromaxx 3.27 Gllucohpage 0.81 Amoiixcillin 1.60 Permium Deiit Patch 41.21 Cilck hiere http://size.150m.com Peering and benevolent curiosity. Your experience has been. And in silence. Will refuse. Is of that color. Like this and i. very. Cheer me up but by. Complain of sir. You would have. Away they went. Was already deeply interested. To for some time. The advice of. Room and out. Be the blackest. Earrings. Another vacancy on the league. Before he could object. Encyclopaedia down to the. Again doctor you. Encyclopaedia down to the. I thought at first that. When she sings. Evening by the way doctor. Becomes a double-edged weapon now. In a quiet.
Bug#402389: Doesn't look like a bug in usbmount
Hi! Your bug doesn't look like a bug, at least no bug in usbmount. I guess it is a hardware or maybe driver problem. Did you try to mount your camera manually? Did this work? Can you mount other hardware, e.g. an usb stick? Your log snippet shows output which is generated _before_ usbmount is activated, otherwise you would find output from usbmount in the logs. Something like this: Feb 14 18:12:59 bluemoon usbmount[5914]: executing command: mount... To be completely sure you can set VERBOSE="no" in /etc/usbmount/usbmount.conf Please reply as soon as possible, because your bugreport is blocking usbmount from entering Etch! Regards, Armin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#402389: Doesn't look like a bug in usbmount
Armin Berres wrote: > Hi! > > Your bug doesn't look like a bug, at least no bug in usbmount. > I guess it is a hardware or maybe driver problem. > Did you try to mount your camera manually? Did this work? Can you mount > other hardware, e.g. an usb stick? > > Your log snippet shows output which is generated _before_ usbmount is > activated, otherwise you would find output from usbmount in the logs. > Something like this: > Feb 14 18:12:59 bluemoon usbmount[5914]: executing command: mount... > > To be completely sure you can set VERBOSE="no" in > /etc/usbmount/usbmount.conf > > Please reply as soon as possible, because your bugreport is blocking > usbmount from entering Etch! > > Regards, > Armin Hi, I tried with usb stick and it works fine. I tried it with memory card taken from digital camera with card reader and it is mounted ok. But when I'm attaching digital camera directly, it is not mounted. From logs: from messages: Feb 14 20:00:10 acer kernel: Vendor: NIKON Model: D50 Rev: 1.00 Feb 14 20:00:10 acer kernel: Type: Direct-Access ANSI SCSI revision: 02 Feb 14 20:00:10 acer kernel: SCSI device sdb: 1935361 512-byte hdwr sectors (991 MB) Feb 14 20:00:10 acer kernel: sdb: Write Protect is off Feb 14 20:00:10 acer kernel: SCSI device sdb: 1935361 512-byte hdwr sectors (991 MB) Feb 14 20:00:10 acer kernel: sdb: Write Protect is off Feb 14 20:00:10 acer kernel: sdb: sdb1 Feb 14 20:00:10 acer kernel: sd 9:0:0:0: Attached scsi removable disk sdb from syslog: Feb 14 20:00:10 acer kernel: sdb: assuming drive cache: write through Feb 14 20:00:10 acer kernel: end_request: I/O error, dev sdb, sector 1935360 Feb 14 20:00:10 acer kernel: printk: 1 messages suppressed. Feb 14 20:00:10 acer kernel: Buffer I/O error on device sdb, logical block 1935360 Feb 14 20:00:10 acer kernel: end_request: I/O error, dev sdb, sector 1935360 Feb 14 20:00:10 acer kernel: Buffer I/O error on device sdb, logical block 1935360 Feb 14 20:00:10 acer kernel: end_request: I/O error, dev sdb, sector 1935360 Feb 14 20:00:10 acer kernel: Buffer I/O error on device sdb, logical block 1935360 <...> Feb 14 20:00:20 acer kernel: end_request: I/O error, dev sdb, sector 134 Feb 14 20:00:31 acer usbmount[19507]: cannot read from /dev/sdb1 Rolandas p.s. you can close this bug, because I already got card reader and use it. p.p.s I cannot mount it manually after inserting. Only after removing usbmount it can be done manually. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#402389: Doesn't look like a bug in usbmount
Thanks for you're message! Rolandas Juodzbalis wrote: >> To be completely sure you can set VERBOSE="no" in >> /etc/usbmount/usbmount.conf Oups, VERBOSE="yes" for sure :-) Can you please try this with your camera and show me the logs in this case? > p.s. you can close this bug, because I already got card reader and use it. I think I will downgrade it at least. Will close it only if I'm sure it's no bug in usbmount (which I still beleave) > p.p.s I cannot mount it manually after inserting. Only after removing > usbmount it can be done manually. Weird... /Armin
Bug#402389: Doesn't look like a bug in usbmount
[EMAIL PROTECTED] wrote: > Thanks for you're message! > > Rolandas Juodzbalis wrote: >>> To be completely sure you can set VERBOSE="no" in >>> /etc/usbmount/usbmount.conf > > Oups, VERBOSE="yes" for sure :-) > Can you please try this with your camera and show me the logs in this case? > >> p.s. you can close this bug, because I already got card reader and use it. > > I think I will downgrade it at least. > Will close it only if I'm sure it's no bug in usbmount (which I still > beleave) > >> p.p.s I cannot mount it manually after inserting. Only after removing >> usbmount it can be done manually. > > Weird... > > /Armin > I tried to completely reinstall usbmount. Did not helped. There is not much info in logs when VERBOSE="yes". Only this one: Feb 14 21:50:14 acer usbmount[31039]: cannot read from /dev/sdb1 I tried to attach ipod, which fails too, but fails in another way. usbmount mounts it as /dev/sdb instead of /dev/sdb2 /dev/sdb on /media/usb1 type vfat (rw,noexec,nodev,sync,noatime) There is info from /var/log/messages: Feb 14 21:50:45 acer kernel: Vendor: Apple Model: iPod Rev: 1.62 Feb 14 21:50:45 acer kernel: Type: Direct-Access ANSI SCSI revision: 00 Feb 14 21:50:45 acer kernel: SCSI device sdb: 7999487 512-byte hdwr sectors (4096 MB) Feb 14 21:50:45 acer kernel: sdb: Write Protect is off Feb 14 21:50:45 acer kernel: SCSI device sdb: 7999487 512-byte hdwr sectors (4096 MB) Feb 14 21:50:45 acer kernel: sdb: Write Protect is off Feb 14 21:50:46 acer kernel: sdb: sdb1 sdb2 Feb 14 21:50:46 acer kernel: sd 14:0:0:0: Attached scsi removable disk sdb Feb 14 21:50:46 acer usbmount[31215]: executing command: mount -tvfat -osync,noexec,nodev,noatime /dev/sdb /media/usb1 Feb 14 21:50:46 acer usbmount[31215]: executing command: run-parts /etc/usbmount/mount.d Feb 14 21:50:47 acer usbmount[31281]: executing command: mount -tvfat -osync,noexec,nodev,noatime /dev/sdb2 /media/usb2 After seeing this, now I believe that this might be udev problems? Note: there is no mount /media/usb2 in mounts mount |grep usb procbususb on /proc/bus/usb type usbfs (rw) /dev/sda1 on /media/usb0 type ext3 (rw,noexec,nodev,noatime) /dev/sdb on /media/usb1 type vfat (rw,noexec,nodev,sync,noatime) /dev/sda1 is mounted ok via usbmount, long time ago :) Rolandas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Not RC :-)
Processing commands for [EMAIL PROTECTED]: > severity 402389 normal Bug#402389: usbmount fails to mount flash devices Severity set to `normal' from `grave' > tags 377548 + confirmed Bug#377548: usbmount: Fails mounting some parts in a n-in-1 device Tags were: patch Tags added: confirmed > tags 350633 + confirmed Bug#350633: usbmount should respect /etc/fstab entries Tags were: patch Tags added: confirmed > tags 345364 + pending Bug#345364: usbmount fails if /var/run/usbmount does not exist There were no tags set. Tags added: pending > tags 380809 + confirmed Bug#380809: Add Option to disable usbmount There were no tags set. Tags added: confirmed > kthxbye Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#402389: Does look like a bug - but where (was: Doesn't look like a bug in usbmount)
Rolandas Juodzbalis wrote: > I tried to completely reinstall usbmount. Did not helped. There is not > much info in logs when VERBOSE="yes". Only this one: Hm, it should look like this (usbmount mounted an usbstick): Feb 15 00:14:43 bluemoon kernel: usb-storage: device scan complete Feb 15 00:14:43 bluemoon usbmount[10668]: trying to acquire lock /var/run/usbmount/.mount.lock Feb 15 00:14:43 bluemoon usbmount[10668]: acquired lock /var/run/usbmount/.mount.lock Feb 15 00:14:43 bluemoon usbmount[10668]: testing whether /dev/sda is readable Feb 15 00:14:43 bluemoon usbmount[10668]: /dev/sda does not contain a filesystem or disklabel Feb 15 00:14:43 bluemoon usbmount[10685]: trying to acquire lock /var/run/usbmount/.mount.lock Feb 15 00:14:43 bluemoon usbmount[10685]: acquired lock /var/run/usbmount/.mount.lock Feb 15 00:14:43 bluemoon usbmount[10685]: testing whether /dev/sda1 is readable Feb 15 00:14:43 bluemoon usbmount[10685]: /dev/sda1 contains a filesystem or disklabel Feb 15 00:14:43 bluemoon usbmount[10685]: /dev/sda1 contains filesystem type vfat Feb 15 00:14:43 bluemoon usbmount[10685]: mountpoint /media/usb0 is available for /dev/sda1 Feb 15 00:14:43 bluemoon usbmount[10685]: executing command: mount -tvfat -onodev,noatime,gid=floppy,dmask=0007,fmask=0117 /dev/sda1 /media/usb0 Feb 15 00:14:44 bluemoon usbmount[10685]: executing command: run-parts /etc/usbmount/mount.d With the additional output it should be clear, which command causes the errors of your camera. > Feb 14 21:50:14 acer usbmount[31039]: cannot read from /dev/sdb1 > I tried to attach ipod, which fails too, but fails in another way. > usbmount mounts it as /dev/sdb instead of /dev/sdb2 Weird, weird. Here it would be also nice, if the verbose mode would work. You changed the "no" in the last line of /etc/usbmount/usbmount.conf to "yes", right (just to be sure)? I'll test tomorrow which output I get from an Ipod. I took over this package yesterday, that's why I'm not comletely in the code yet, but I'm sure we will find the problem :-) /Armin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#402389: Does look like a bug - but where
Armin Berres wrote: > > With the additional output it should be clear, which command causes the > errors of your camera. There is no output from usbmount except this: cannot read from /dev/sdb1 > >> Feb 14 21:50:14 acer usbmount[31039]: cannot read from /dev/sdb1 >> I tried to attach ipod, which fails too, but fails in another way. >> usbmount mounts it as /dev/sdb instead of /dev/sdb2 > > Weird, weird. Here it would be also nice, if the verbose mode would > work. You changed the "no" in the last line of > /etc/usbmount/usbmount.conf to "yes", right (just to be sure)? Yes, I changed. > I'll test tomorrow which output I get from an Ipod. > > I took over this package yesterday, that's why I'm not comletely in the > code yet, but I'm sure we will find the problem :-) > > /Armin :) Rolandas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#402389: Does look like a bug - but where
Rolandas Juodzbalis wrote: > Armin Berres wrote: >> With the additional output it should be clear, which command causes the >> errors of your camera. > There is no output from usbmount except this: > cannot read from /dev/sdb1 Uh, jut noticed something: The debug logs appear only in /var/log/syslog and not in /var/log/messages! Maybe you checked only /var/log/messages? /Armin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#402389: Does look like a bug - but where
Armin Berres wrote: > Rolandas Juodzbalis wrote: >> Armin Berres wrote: >>> With the additional output it should be clear, which command causes the >>> errors of your camera. >> There is no output from usbmount except this: >> cannot read from /dev/sdb1 > > Uh, jut noticed something: The debug logs appear only in /var/log/syslog > and not in /var/log/messages! > > Maybe you checked only /var/log/messages? > > /Armin When I connected camera, I can see usbmount info only in syslog. nothing in messages. Rolandas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#411000: Tripwire: [INTL:es] Spanish po-debconf translation
Package: Tripwire Priority: wishlist Tags: patch l10n Attached the spanish debconf templates translation. Regards, Javi. . # Tripwire's po-debconf translation to spanish # Copyright (C) 2007 Free Software Foundation, Inc. # This file is distributed under the same license as the package. # # Changes: # - Initial translation # Javier Ruano Ruano , 2007 # - Revision # Javier Fernandez-Sanguino # # # Traductores, si no conoce el formato PO, merece la pena leer la # documentación de gettext, especialmente las secciones dedicadas a este # formato, por ejemplo ejecutando: # info -n '(gettext)PO Files' # info -n '(gettext)Header Entry' # # Equipo de traducción al español, por favor lean antes de traducir # los siguientes documentos: # # - El proyecto de traducción de Debian al español # http://www.debian.org/intl/spanish/ # especialmente las notas y normas de traducción en # http://www.debian.org/intl/spanish/notas # # - La guÃa de traducción de po's de debconf: # /usr/share/doc/po-debconf/README-trans # o http://www.debian.org/intl/l10n/po-debconf/README-trans # # Si tiene dudas o consultas sobre esta traducción consulte con el último # traductor (campo Last-Translator) y ponga en copia a la lista de # traducción de Debian al español () # msgid "" msgstr "" "Project-Id-Version: tripwire\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2007-01-27 04:33+0100\n" "PO-Revision-Date: 2007-02-13 11:08+0100\n" "Last-Translator: Javier Ruano Ruano <[EMAIL PROTECTED]>\n" "Language-Team: Debian L10n Spanish \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Type: boolean #. Description #: ../templates:1001 msgid "Do you wish to upgrade?" msgstr "¿Desea actualizar?" #. Type: boolean #. Description #: ../templates:1001 msgid "" "The format of the Tripwire database and configuration files have changed " "substantially between previous versions and this release." msgstr "El formato de la base de datos y de los ficheros de configuración ha cambiado sustancialmente entre las versiones anteriores y esta versión de Tripwire." #. Type: boolean #. Description #: ../templates:1001 msgid "" "To ensure your system remains secure, the upgrade process keeps a copy of " "the old version of Tripwire and the old configuration file along with any " "old databases that may exist. You will find a detailed explanation for " "using the old version of Tripwire in /usr/share/doc/tripwire/README.Debian." msgstr "Se guardará una copia de la anterior versión de Tripwire y de los ficheros de configuración obsoletos que pertenezcan a la base de datos que pudiera existir para que su sistema mantenga su nivel de seguridad. Encontrará información detallada sobre el uso de la versión anterior de Tripwire en «/usr/share/doc/tripwire/README.Debian»." #. Type: boolean #. Description #: ../templates:1001 msgid "" "However, as no conversion of the old configuration file and database is " "attempted, you may prefer not to upgrade." msgstr "En cualquier caso, puede que no desee actualizar debido a que no es posible la conversión del fichero de configuración anterior y la base de datos." #. Type: boolean #. Description #: ../templates:1001 msgid "" "Due to the way Debian handles configuration files, if you choose to upgrade " "you must accept the new version of /etc/cron.daily/tripwire for regular " "reporting to occur. The cron job associated with the previous version will " "continue to run regardless." msgstr "Si elije actualizar debe utilizar la nueva versión «/etc/cron.daily/tripwire» para que se generen los informes periódicos. Esto se debe a la forma en que Debian gestiona los ficheros de configuración. A pesar de todo, la tarea de cron asociada a la versión anterior seguirá ejecutándose." #. Type: boolean #. Description #: ../templates:2001 msgid "" "Do you wish to create/use your site key pass-phrase during installation?" msgstr "" "¿Desea crear/usar su clave de sitio durante la instalación?" #. Type: boolean #. Description #: ../templates:2001 msgid "" "Tripwire uses a pair of keys to sign various files, thus ensuring their " "unaltered state. By accepting here, you will be prompted for the pass-" "phrase for the first of those keys, the site key, during the installation. " "You are also agreeing to the create of a site key if one doesn't already " "exist. Tripwire uses the site key to sign files that may be common to " "multiple systems, e.g. the configuration & policy files. See twfiles(5) for " "more information." msgstr "Tripwrire utiliza un par de claves para firmar varios ficheros, de esta forma se asegura que no se modifiquen. Si acepta aquÃ, se le pedirá la primera de estas claves durante la instalación, esta es la contraseña de sitio. También da su conformidad con la creación de esta contraseña si no existe aún. Tripwire usa la clave de sitio para
Bug#411009: ITA: libqt-perl -- Perl bindings for the Qt library
Package: libqt-perl Binary: libqt-perl Version: 3.008-1.4 Priority: optional Section: perl Maintainer: Peter Hawkins [EMAIL PROTECTED] New maintainer: Deepak Tripathi [EMAIL PROTECTED] Build-Depends: debhelper (>> 3.0.0), libqt3-mt-dev, perl (>= 5.8.0), automake1.7, autoconf, libsmokeqt-dev (>> 4:3.2.3-1) Build-Conflicts: libqt-perl Architecture: any Standards-Version: 3.6.1 Format: 1.0 Directory: pool/main/libq/libqt-perl Thanks Deepak Tripathi GPG:-B9B0C9F2 The information contained in, or attached to, this e-mail, contains confidential information and is intended solely for the use of the individual or entity to whom they are addressed and is subject to legal privilege. If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager. Please do not copy it for any purpose, or disclose its contents to any other person. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email. www.aztecsoft.com
