[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[pkg-wine-party] Bug#486150: marked as done (wine: err:reg:SCSI_getprocentry SCSI type line scan count error (fscanf returns 1, expected 2))

Your message dated Sun, 09 Aug 2009 18:47:18 +0200
with message-id <4A7EFD96.7080302@arcticnet.no>
and subject line Re: [pkg-wine-party] Bug#486150: wine: err:reg:SCSI_getprocentry SCSI type line scan count error (fscanf returns 1, expected 2)
has caused the Debian Bug report #486150,
regarding wine: err:reg:SCSI_getprocentry SCSI type line scan count error (fscanf returns 1, expected 2)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
486150: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=486150
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: wine
Version: 1.0-rc4-1
Severity: normal


I get this message from every wine program:

   err:reg:SCSI_getprocentry SCSI type line scan count error (fscanf returns 1, expected 2)

It seems to happen after parsing /proc/scsi/scsi, which looks like this on my system:

   Attached devices:
   Host: scsi0 Channel: 00 Id: 00 Lun: 00
     Vendor: ATA      Model: ST3500630AS      Rev: 3.AA
     Type:   Direct-Access                    ANSI  SCSI revision: 05
   Host: scsi4 Channel: 00 Id: 00 Lun: 00
     Vendor: AMCC     Model: 9650SE-16M DISK  Rev: 3.08
     Type:   Direct-Access                    ANSI  SCSI revision: 05
   Host: scsi4 Channel: 00 Id: 01 Lun: 00
     Vendor: AMCC     Model: 9650SE-16M DISK  Rev: 3.08
     Type:   Direct-Access                    ANSI  SCSI revision: 05
   Host: scsi5 Channel: 00 Id: 00 Lun: 00
     Vendor: Verbatim Model: STORE N GO       Rev: 5.00
     Type:   Direct-Access                    ANSI  SCSI revision: 00
   Host: scsi6 Channel: 00 Id: 00 Lun: 00
     Vendor:          Model: P990i            Rev: 1.0 
     Type:   Direct-Access                    ANSI  SCSI revision: 00

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.24-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages wine depends on:
ii  libwine-alsa                  1.0-rc4-1  Windows API implementation - ALSA 
ii  libwine-cms                   1.0-rc4-1  Windows API implementation - color
ii  libwine-gl                    1.0-rc4-1  Windows API implementation - OpenG
ii  libwine-gphoto2               1.0-rc4-1  Windows API implementation - camer
ii  libwine-ldap                  1.0-rc4-1  Windows API implementation - LDAP 
ii  libwine-print                 1.0-rc4-1  Windows API implementation - print
ii  libwine-sane                  1.0-rc4-1  Windows API implementation - scann
ii  wine-bin                      1.0-rc4-1  Windows API implementation - binar
ii  wine-utils                    1.0-rc4-1  Windows API implementation - utili

wine recommends no packages.

Versions of packages libwine depends on:
ii  ia32-libs                     2.5        ia32 shared libraries for use on a
ii  libc6-i386                    2.7-10     GNU C Library: 32bit shared librar

-- debconf information:
  wine/install_type:
  wine/del_wine_conf:
  wine/move_to_fhs:

--- End Message ---
--- Begin Message --- 
Version: 1.0.1-1

Marc Lehmann skrev:
> On Sun, Aug 09, 2009 at 12:34:51PM +0200, Ove Kaaven <ovek@arcticnet.no> wrote:
>>> I get this message from every wine program:
>>>
>>>    err:reg:SCSI_getprocentry SCSI type line scan count error (fscanf returns 1, expected 2)
>> While I believe that version of Wine *should* have parsed your
>> /proc/scsi/scsi fine, has this problem fixed itself since?
> 
> yes, 1.0.1-1 doesn't have this issue anymore.

OK, thanks, closing.

--- End Message ---
Reply to: