Your message dated Tue, 21 Oct 2008 18:18:04 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#385400: "swat: SWAT segfaults when fiddling with 
printer settings" bug still here?
has caused the Debian Bug report #385400,
regarding swat: SWAT segfaults when fiddling with printer settings
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 [EMAIL PROTECTED]
immediately.)


-- 
385400: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=385400
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: swat
Version: 3.0.23b-2
Severity: normal


previously reported under #36523.

SWAT is segfaulting when fiddling with printer settings.

Previously, 

use client driver = Yes 

was in [CANON] setting but gave inconsistent results in SWAT. I moved it 
to [global] and things have settled down since. (A corrupt CANON.tdb 
didn't help either).

smb.conf:

[global]
        workgroup = MSHOME
        server string = %h server (Samba %v)
        security = SHARE
        encrypt passwords = No
        obey pam restrictions = Yes
        passdb backend = tdbsam
        passwd program = /usr/bin/passwd %u
        passwd chat = *Enter\snew\sUNIX\spassword:* %n\n 
*Retype\snew\sUNIX\spassword:* %n\n .
        syslog = 0
        log file = /var/log/samba/log.%m
        max log size = 1000
        printcap name = cups
        dns proxy = No
        ldap ssl = no
        panic action = /usr/share/samba/panic-action %d
        invalid users = root
        printing = cups
        print command =
        lpq command = %p
        lprm command =
        use client driver = Yes

[homes]
        comment = Home Directories
        path = /home
        acl check permissions = No
        create mask = 0700
        directory mask = 0700
        guest ok = Yes

[printers]
        comment = All Printers
        path = /tmp
        create mask = 0700
        guest ok = Yes
        printable = Yes
        browseable = Yes

[print$]
        comment = Printer Drivers
        path = /var/lib/samba/printers
        write list = root

[symonec]
        path = /symonec
        read only = No
        guest ok = Yes

[victoriac]
        path = /victoriac
        read only = No
        guest ok = Yes

[victoriad]
        path = /victoriad
        read only = No
        guest ok = Yes

[mirror3]
        path = /mirror3
        read only = No
        guest ok = Yes

[CANON]
        path = /tmp
        guest ok = Yes
        printable = Yes
        browseable = Yes

/var/log/samba/log.swat:

[2006/08/30 09:23:29, 1] param/loadparm.c:lp_do_parameter(3434)
  WARNING: The "printer admin" option is deprecated
[2006/08/30 09:24:16, 1] param/loadparm.c:lp_do_parameter(3434)
  WARNING: The "printer admin" option is deprecated
[2006/08/30 09:25:20, 1] param/loadparm.c:lp_do_parameter(3434)
  WARNING: The "printer admin" option is deprecated
[2006/08/30 09:25:20, 0] lib/fault.c:fault_report(41)
  ===============================================================
[2006/08/30 09:25:20, 0] lib/fault.c:fault_report(42)
  INTERNAL ERROR: Signal 11 in pid 26132 (3.0.23b)
  Please read the Trouble-Shooting section of the Samba3-HOWTO
[2006/08/30 09:25:20, 0] lib/fault.c:fault_report(44)

  From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2006/08/30 09:25:20, 0] lib/fault.c:fault_report(45)
  ===============================================================
[2006/08/30 09:25:20, 0] lib/util.c:smb_panic(1592)
  PANIC (pid 26132): internal error
[2006/08/30 09:25:20, 0] lib/util.c:log_stack_trace(1699)
  BACKTRACE: 8 stack frames:
   #0 swat(log_stack_trace+0x23) [0x810f3c3]
   #1 swat(smb_panic+0x46) [0x810f4b6]
   #2 swat [0x80fdb8a]
   #3 [0xffffe420]
   #4 swat [0x80782e7]
   #5 swat(main+0x308) [0x8079d28]
   #6 /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xc8) [0x418a4ea8]
   #7 swat [0x8074511]
[2006/08/30 09:25:20, 0] lib/util.c:smb_panic(1600)
  smb_panic(): calling panic action [/usr/share/samba/panic-action 
26132]
[2006/08/30 09:25:24, 0] lib/util.c:smb_panic(1608)
  smb_panic(): action returned status 0

Email report:

To: [EMAIL PROTECTED]
Subject: Segfault in Samba
Message-Id: <[EMAIL PROTECTED]>
From: root <[EMAIL PROTECTED]>
Date: Wed, 30 Aug 2006 09:25:24 +0930

The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for pid 26132 (/usr/sbin/swat).

Below is a backtrace for this process generated with gdb, which shows
the state of the program at the time the error occurred. 

If the problem persists, you are encouraged to first install the 
samba-dbg package which contains the debugging symbols for samba 
binaries. Then submit the provided information as a bug report to 
Debian.
For information about the procedure for submitting bug reports , please 
see
http://www.debian.org/Bugs/Reporting or the reportbug(1) manpage.

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1477118272 (LWP 26132)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)

Versions of packages swat depends on:
ii  libc6                      2.3.6.ds1-4   GNU C Library: Shared libraries
ii  libcomerr2                 1.39-1        common error description library
ii  libcupsys2                 1.2.2-2       Common UNIX Printing System(tm) - 
ii  libgnutls13                1.4.2-1       the GNU TLS library - runtime libr
ii  libkrb53                   1.4.4~beta1-1 MIT Kerberos runtime libraries
ii  libldap2                   2.1.30-13+b1  OpenLDAP libraries
ii  libpam0g                   0.79-3.2      Pluggable Authentication Modules l
ii  libpopt0                   1.10-3        lib for parsing cmdline parameters
ii  netbase                    4.26          Basic TCP/IP networking system
ii  samba                      3.0.23b-2     a LanManager-like file and printer
ii  samba-doc                  3.0.23b-2     Samba documentation
ii  zlib1g                     1:1.2.3-13    compression library - runtime

swat recommends no packages.

-- debconf information:
* swat/smb_conf_warn:


--- End Message ---
--- Begin Message ---
> Christian Perrier wrote, on 2008-10-21 19:33:
>> Do you still experience this bug? From the bug log you compiled and
>> installed a debug version of swat and mentioned you'd report any
>> further problem, but nothing came so I assume you had no more problems
>> with swat when fiddling with printer settings.
>
> I've done very little with swat in the meantime and had no problems, so
> the problem may have been fixed by code clean-ups since then.


So, well, I think the only remaining option we have here is closing
the bug...

Thanks for your feedback.



Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to