Bug#566508: how do I find out what the previous version was

2010-03-17 Thread Dan Aronson
I had just built the machine about a month before, so my guess is that  
it was the last published version, but happy to try to find out more.







--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#566508: libc6: error inside of python since last security upgrade

2010-01-23 Thread dan aronson
Package: libc6
Version: 2.7-18lenny2
Severity: important

Since I did the last security upgrade to this package I've been getting the 
following problem often, but not always during running of a cron job.

*** glibc detected *** /usr/bin/python: corrupted double-linked list: 
0x020dc920 ***
=== Backtrace: =
/lib/libc.so.6[0x7f73afabc928]
/lib/libc.so.6[0x7f73afabf679]
/lib/libc.so.6[0x7f73afac0314]
/lib/libc.so.6(realloc+0x12f)[0x7f73afac0f9f]
/usr/bin/python(_PyObject_GC_Resize+0x39)[0x4bd119]
/usr/bin/python(PyFrame_New+0x36d)[0x4dccbd]
/usr/bin/python(PyEval_EvalCodeEx+0x76)[0x492b06]
/usr/bin/python[0x4dd612]
/usr/bin/python(PyObject_Call+0x13)[0x4187b3]
/usr/bin/python[0x41f658]
/usr/bin/python(PyObject_Call+0x13)[0x4187b3]
/usr/bin/python(PyEval_EvalFrameEx+0x3d12)[0x48fef2]
/usr/bin/python(PyEval_EvalFrameEx+0x6872)[0x492a52]
/usr/bin/python(PyEval_EvalCodeEx+0x6ad)[0x49313d]
/usr/bin/python[0x4dd709]
/usr/bin/python(PyObject_Call+0x13)[0x4187b3]
/usr/bin/python(PyEval_EvalFrameEx+0x40b7)[0x490297]
/usr/bin/python(PyEval_EvalCodeEx+0x6ad)[0x49313d]
/usr/bin/python[0x4dd612]
/usr/bin/python(PyObject_Call+0x13)[0x4187b3]
/usr/bin/python(PyEval_CallObjectWithKeywords+0x72)[0x48b262]
/usr/bin/python(Py_Finalize+0x3e)[0x4b24ee]
/usr/bin/python[0x4b1fae]
/usr/bin/python(PyErr_PrintEx+0x18d)[0x4b21bd]
/usr/bin/python(PyRun_SimpleFileExFlags+0x13b)[0x4b2f0b]
/usr/bin/python(Py_Main+0xac2)[0x414542]
/lib/libc.so.6(__libc_start_main+0xe6)[0x7f73afa671a6]
/usr/bin/python[0x413989]
=== Memory map: 
0040-00525000 r-xp  08:01 78524  
/usr/bin/python2.5
00724000-00756000 rw-p 00124000 08:01 78524  
/usr/bin/python2.5
00756000-0075e000 rw-p 00756000 00:00 0 
01fcf000-020e9000 rw-p 01fcf000 00:00 0  [heap]
40f15000-40f16000 ---p 40f15000 00:00 0 
40f16000-41716000 rw-p 40f16000 00:00 0 
41716000-41717000 ---p 41716000 00:00 0 
41717000-41f17000 rw-p 41717000 00:00 0 
7f73a800-7f73a8021000 rw-p 7f73a800 00:00 0 
7f73a8021000-7f73ac00 ---p 7f73a8021000 00:00 0 
7f73ae3f7000-7f73ae40d000 r-xp  08:01 97731  
/lib/libgcc_s.so.1
7f73ae40d000-7f73ae60d000 ---p 00016000 08:01 97731  
/lib/libgcc_s.so.1
7f73ae60d000-7f73ae60e000 rw-p 00016000 08:01 97731  
/lib/libgcc_s.so.1
7f73ae60e000-7f73ae613000 r-xp  08:01 891
/usr/lib/python2.5/lib-dynload/binascii.so
7f73ae613000-7f73ae812000 ---p 5000 08:01 891
/usr/lib/python2.5/lib-dynload/binascii.so
7f73ae812000-7f73ae813000 rw-p 4000 08:01 891
/usr/lib/python2.5/lib-dynload/binascii.so
7f73ae813000-7f73ae816000 r-xp  08:01 884
/usr/lib/python2.5/lib-dynload/select.so
7f73ae816000-7f73aea16000 ---p 3000 08:01 884
/usr/lib/python2.5/lib-dynload/select.so
7f73aea16000-7f73aea17000 rw-p 3000 08:01 884
/usr/lib/python2.5/lib-dynload/select.so
7f73aea17000-7f73aea1a000 r-xp  08:01 876
/usr/lib/python2.5/lib-dynload/fcntl.so
7f73aea1a000-7f73aec19000 ---p 3000 08:01 876
/usr/lib/python2.5/lib-dynload/fcntl.so
7f73aec19000-7f73aec1b000 rw-p 2000 08:01 876
/usr/lib/python2.5/lib-dynload/fcntl.so
7f73aec1b000-7f73aec21000 r-xp  08:01 916
/usr/lib/python2.5/lib-dynload/collections.so
7f73aec21000-7f73aee2 ---p 6000 08:01 916
/usr/lib/python2.5/lib-dynload/collections.so
7f73aee2-7f73aee22000 rw-p 5000 08:01 916
/usr/lib/python2.5/lib-dynload/collections.so
7f73aee22000-7f73aee26000 r-xp  08:01 885
/usr/lib/python2.5/lib-dynload/cStringIO.so
7f73aee26000-7f73af025000 ---p 4000 08:01 885
/usr/lib/python2.5/lib-dynload/cStringIO.so
7f73af025000-7f73af027000 rw-p 3000 08:01 885
/usr/lib/python2.5/lib-dynload/cStringIO.so
7f73af027000-7f73af02b000 r-xp  08:01 882
/usr/lib/python2.5/lib-dynload/time.so
7f73af02b000-7f73af22a000 ---p 4000 08:01 882
/usr/lib/python2.5/lib-dynload/time.so
7f73af22a000-7f73af22c000 rw-p 3000 08:01 882
/usr/lib/python2.5/lib-dynload/time.so
7f73af22c000-7f73af233000 r-xp  08:01 890
/usr/lib/python2.5/lib-dynload/_struct.so
7f73af233000-7f73af432000 ---p 7000 08:01 890
/usr/lib/python2.5/lib-dynload/_struct.so
7f73af432000-7f73af434000 rw-p 6000 08:01 890
/usr/lib/python2.5/lib-dynload/_struct.so
7f73af434000-7f73af43b000 r-xp  08:01 875
/usr/lib/python2.5/lib-dynload/operator.so
7f73af43b000-7f73af63b000 ---p 

Bug#341329: closed by Martin Michlmayr [EMAIL PROTECTED] (Kernel from Debian 3.1 no longer supported)

2008-06-20 Thread Dan Aronson
Well, I guess one way of dealing with bugs is to ignore them until they 
cease to be a problem.  Unfortunately this mechanism might not always 
keep the users satisfied. 


--dan

Debian Bug Tracking System wrote:

This is an automatic notification regarding your Bug report
which was filed against the kernel-image-2.6.8-3-386 package:

#341329: kernel-image-2.6.8-2-386: usb 2.0 pci card with ali 5273 chip not 
working

It has been closed by Martin Michlmayr [EMAIL PROTECTED].

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Martin Michlmayr [EMAIL 
PROTECTED] by
replying to this email.


  




Subject:
Kernel from Debian 3.1 no longer supported
From:
Martin Michlmayr [EMAIL PROTECTED]
Date:
Fri, 20 Jun 2008 17:09:08 +0200
To:
[EMAIL PROTECTED]

To:
[EMAIL PROTECTED]

Received:
(at 341329-done) by bugs.debian.org; 20 Jun 2008 15:10:42 +
X-Spam-Checker-Version:
SpamAssassin 3.1.4-bugs.debian.org_2005_01_02 (2006-07-26) on 
rietz.debian.org

X-Spam-Status:
No, score=-5.0 required=4.0 tests=BAYES_00,VERSION autolearn=no 
version=3.1.4-bugs.debian.org_2005_01_02

Return-path:
[EMAIL PROTECTED]
Received:
from sorrow.cyrius.com ([65.19.161.204]) by rietz.debian.org with 
esmtp (Exim 4.63) (envelope-from [EMAIL PROTECTED]) id 1K9iGA-0007Dr-8f 
for [EMAIL PROTECTED]; Fri, 20 Jun 2008 15:10:42 +

Received:
by sorrow.cyrius.com (Postfix, from userid 10) id 0AC14D8D4; Fri, 20 
Jun 2008 15:10:41 + (UTC)

Received:
by deprecation.cyrius.com (Postfix, from userid 1000) id 85A51150FB7; 
Fri, 20 Jun 2008 17:09:08 +0200 (CEST)

Message-ID:
[EMAIL PROTECTED]
MIME-Version:
1.0
Content-Type:
text/plain; charset=us-ascii
Content-Disposition:
inline
User-Agent:
Mutt/1.5.17+20080114 (2008-01-14)


Version: 2.6.8-99+rm

You reported a bug against the Linux kernel (version 2.6.8) that was
shipped with Debian 3.1 (sarge).  Since Debian 3.1 is no longer
supported and the kernel has changed so much that it would be very
difficult to verify every outstanding bug from 2.6.8, I'm hereby
closing your bug report.

If you still see this issue with the kernel from the upcoming release
of Debian (lenny, version 5.0), then please me know and I'll be happy
to reopen this bug report.

Thanks.

  




Subject:
kernel-image-2.6.8-2-386: usb 2.0 pci card with ali 5273 chip not working
From:
Dan Aronson [EMAIL PROTECTED]
Date:
Tue, 29 Nov 2005 17:24:52 -0800
To:
Debian Bug Tracking System [EMAIL PROTECTED]

To:
Debian Bug Tracking System [EMAIL PROTECTED]

Received:
(at submit) by bugs.debian.org; 30 Nov 2005 01:31:31 +
Return-path:
[EMAIL PROTECTED]
Received:
from smtp114.sbc.mail.mud.yahoo.com ([68.142.198.213]) by 
spohr.debian.org with smtp (Exim 4.50) id 1EhGol-00063g-DM for 
[EMAIL PROTECTED]; Tue, 29 Nov 2005 17:31:31 -0800

Received:
(qmail 44544 invoked from network); 30 Nov 2005 01:31:00 -
Received:
from unknown (HELO dan-server.catolabs.org) 
([EMAIL PROTECTED]@71.141.111.135 with plain) by 
smtp114.sbc.mail.mud.yahoo.com with SMTP; 30 Nov 2005 01:31:00 -

Received:
from dan by dan-server.catolabs.org with local (Exim 4.50 #1 (Debian)) 
id 1EhGiL-0001tl-3C for [EMAIL PROTECTED]; Tue, 29 Nov 2005 
17:24:53 -0800

Received:
by dan-server.catolabs.org (tmda-sendmail, from uid 1000); Tue, 29 Nov 
2005 17:24:52 -0800 (PST)

Received:
from dan by dan-server.catolabs.org with local (Exim 4.50 #1 (Debian)) 
id 1EhGiK-0001td-Fa for [EMAIL PROTECTED]; Tue, 29 Nov 2005 
17:24:52 -0800

Content-Type:
text/plain; charset=us-ascii
MIME-Version:
1.0
Content-Transfer-Encoding:
7bit
X-Mailer:
reportbug 3.8
Message-ID:
[EMAIL PROTECTED]
X-Delivery-Agent:
TMDA/1.0.3 (Seattle Slew)
Sender:
Dan Aronson [EMAIL PROTECTED]
Delivered-To:
[EMAIL PROTECTED]
X-Spam-Checker-Version:
SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on 
spohr.debian.org

X-Spam-Status:
No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no 
version=2.60-bugs.debian.org_2005_01_02



Package: kernel-image-2.6.8-2-386
Version: 2.6.8-16
Severity: important

I recently bouch a compusa brand usb 2.0 2 port card
(model pci-usbali5273-2p-2).  It doesn't work, the ehci module
reports:

ehci_hcd :02:0d.3: ALi Corporation USB 2.0 Controller
ehci_hcd :02:0d.3: BIOS handoff failed (112, 1010001)
ehci_hcd :02:0d.3: can't reset
ehci_hcd :02:0d.3: init :02:0d.3 fail, -95
ehci_hcd: probe of :02:0d.3 failed with error -95


-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-386
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages kernel-image-2.6.8-2-386 depends on:
ii  coreutils [fileutils] 5.2.1-2The GNU core utilities
ii  initrd-tools  0.1.81.1

Bug#400803: firefox: this version seems to have printing problems

2006-11-28 Thread dan aronson

Package: firefox
Version: 1.5.dfsg+1.5.0.7-2
Severity: important

*** Please type your report below this line ***
the printProgress.dtd file used by printProgress.xul which is used when 
printing seems to
be not where it is expected to be.  This caused errors while printing, I 
was changed the
location in printProgress.xul to where the dtd actually was, and now 
printing seems to

work.



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

Versions of packages firefox depends on:
ii  debianutils   2.17   Miscellaneous utilities 
specific t
ii  fontconfig2.4.1-2generic font configuration 
library

ii  libatk1.0-0   1.12.3-1   The ATK accessibility toolkit
ii  libc6 2.3.6.ds1-8GNU C Library: Shared libraries
ii  libcairo2 1.2.4-4The Cairo 2D vector 
graphics libra
ii  libfontconfig12.4.1-2generic font configuration 
library
ii  libfreetype6  2.2.1-5FreeType 2 font engine, 
shared lib

ii  libgcc1   1:4.1.1-19 GCC support library
ii  libglib2.0-0  2.12.4-1   The GLib library of C routines
ii  libgtk2.0-0   2.8.20-3   The GTK+ graphical user 
interface
ii  libjpeg62 6b-13  The Independent JPEG 
Group's JPEG
ii  libpango1.0-0 1.14.7-1   Layout and rendering of 
internatio

ii  libpng12-01.2.8rel-7 PNG library - runtime
ii  libstdc++64.1.1-19   The GNU Standard C++ Library v3
ii  libx11-6  2:1.0.3-3  X11 client-side library
ii  libxft2   2.1.8.2-8  FreeType-based font drawing 
librar

ii  libxinerama1  1:1.0.1-4.1X11 Xinerama extension library
ii  libxp61:1.0.0.xsf1-1 X Printing Extension 
(Xprint) clie

ii  libxt61:1.0.2-2  X11 toolkit intrinsics library
ii  psmisc22.3-1 Utilities that use the proc 
filesy

ii  zlib1g1:1.2.3-13 compression library - runtime

firefox recommends no packages.

-- no debconf information



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#341329: kernel-image-2.6.8-2-386: usb 2.0 pci card with ali 5273 chip not working

2005-11-30 Thread Dan Aronson

Horms wrote:


In article [EMAIL PROTECTED] you wrote:
 



I think I need to write a canned response for 2.6.8 bugs:

As upstream kernel development moves at a rapid pace its virtually
impossible to backport other than trivial fixes. Without spending
a lot of time investingating your problem, would it be possible
to see if the 2.6.12 backport to sarge, a significantly newer kernel,
helps your immediate problem.

http://packages.vergenet.net/sarge-backports/
 



Absolutely.  I'll give it a try and let you know the results.

--dan




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#341329: kernel-image-2.6.8-2-386: usb 2.0 pci card with ali 5273 chip not working

2005-11-30 Thread Dan Aronson

Dan Aronson wrote:


Horms wrote:

In article 
[EMAIL PROTECTED] 
you wrote:

[...]





would it be possible
to see if the 2.6.12 backport to sarge, a significantly newer kernel,
helps your immediate problem.

http://packages.vergenet.net/sarge-backports/
 



Absolutely.  I'll give it a try and let you know the results.


Uh, which deb files should I try to install?

--dan



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#341329: kernel-image-2.6.8-2-386: usb 2.0 pci card with ali 5273 chip not working

2005-11-30 Thread Dan Aronson
Seems to be a BIOS bug that backported 2.6.12 gets past.  Fine solution 
for me.


--dan

ehci_hcd :02:0d.3: ALi Corporation USB 2.0 Controller
ehci_hcd :02:0d.3: debug port 1
ehci_hcd :02:0d.3: BIOS handoff failed (112, 1010001)
ehci_hcd :02:0d.3: continuing after BIOS bug...
ehci_hcd :02:0d.3: new USB bus registered, assigned bus number 5
ehci_hcd :02:0d.3: irq 209, io mem 0x4070
ehci_hcd :02:0d.3: USB 2.0 initialized, EHCI 1.00, driver 10 Dec 2004

Horms wrote:


In article [EMAIL PROTECTED] you wrote:
 


Package: kernel-image-2.6.8-2-386
Version: 2.6.8-16
Severity: important

I recently bouch a compusa brand usb 2.0 2 port card
(model pci-usbali5273-2p-2).  It doesn't work, the ehci module
reports:

ehci_hcd :02:0d.3: ALi Corporation USB 2.0 Controller
ehci_hcd :02:0d.3: BIOS handoff failed (112, 1010001)
ehci_hcd :02:0d.3: can't reset
ehci_hcd :02:0d.3: init :02:0d.3 fail, -95
ehci_hcd: probe of :02:0d.3 failed with error -95
   



I think I need to write a canned response for 2.6.8 bugs:

As upstream kernel development moves at a rapid pace its virtually
impossible to backport other than trivial fixes. Without spending
a lot of time investingating your problem, would it be possible
to see if the 2.6.12 backport to sarge, a significantly newer kernel,
helps your immediate problem.

http://packages.vergenet.net/sarge-backports/

 






--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#341329: kernel-image-2.6.8-2-386: usb 2.0 pci card with ali 5273 chip not working

2005-11-30 Thread Dan Aronson

Horms,
 I don't know why I didn't see it yesterday when I looked, but this 
seems to be the same bug
as 316848.  Sorry for making you reply again.  I'll be even more careful 
next time.


--dan

Horms wrote:


In article [EMAIL PROTECTED] you wrote:
 


Package: kernel-image-2.6.8-2-386
Version: 2.6.8-16
Severity: important

I recently bouch a compusa brand usb 2.0 2 port card
(model pci-usbali5273-2p-2).  It doesn't work, the ehci module
reports:

ehci_hcd :02:0d.3: ALi Corporation USB 2.0 Controller
ehci_hcd :02:0d.3: BIOS handoff failed (112, 1010001)
ehci_hcd :02:0d.3: can't reset
ehci_hcd :02:0d.3: init :02:0d.3 fail, -95
ehci_hcd: probe of :02:0d.3 failed with error -95
   



I think I need to write a canned response for 2.6.8 bugs:

As upstream kernel development moves at a rapid pace its virtually
impossible to backport other than trivial fixes. Without spending
a lot of time investingating your problem, would it be possible
to see if the 2.6.12 backport to sarge, a significantly newer kernel,
helps your immediate problem.

http://packages.vergenet.net/sarge-backports/

 






--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#341329: kernel-image-2.6.8-2-386: usb 2.0 pci card with ali 5273 chip not working

2005-11-30 Thread Dan Aronson
As I wrote, the in 2.6.12 the driver now reports that there is a BIOS 
bug, but then recovers
and finishes loading, I haven't yet tried a device on it, but it does 
show up correctly

in /proc/bus/usb/devices.

--dan

Horms wrote:


On Wed, Nov 30, 2005 at 12:44:29PM -0800, Dan Aronson wrote:
 


Horms,
I don't know why I didn't see it yesterday when I looked, but this 
seems to be the same bug
as 316848.  Sorry for making you reply again.  I'll be even more careful 
next time.
   



No problem. Just to clarify. You still see the same bug in 2.6.12?

 






--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#341329: kernel-image-2.6.8-2-386: usb 2.0 pci card with ali 5273 chip not working

2005-11-29 Thread Dan Aronson
Package: kernel-image-2.6.8-2-386
Version: 2.6.8-16
Severity: important

I recently bouch a compusa brand usb 2.0 2 port card
(model pci-usbali5273-2p-2).  It doesn't work, the ehci module
reports:

ehci_hcd :02:0d.3: ALi Corporation USB 2.0 Controller
ehci_hcd :02:0d.3: BIOS handoff failed (112, 1010001)
ehci_hcd :02:0d.3: can't reset
ehci_hcd :02:0d.3: init :02:0d.3 fail, -95
ehci_hcd: probe of :02:0d.3 failed with error -95


-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-386
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages kernel-image-2.6.8-2-386 depends on:
ii  coreutils [fileutils] 5.2.1-2The GNU core utilities
ii  initrd-tools  0.1.81.1   tools to create initrd image for p
ii  module-init-tools 3.2-pre1-2 tools for managing Linux kernel mo

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#315016: samba: panic called from smbd_server_fd

2005-06-20 Thread Dan Aronson

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

Below is a backtrace for this process generated with gdb, which shows
the state of the program at the time the error occured.  You are
encouraged to submit this 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/libthread_db.so.1.
(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)
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 8426)]
(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)
0x40245808 in waitpid () from /lib/libc.so.6
#0  0x40245808 in waitpid () from /lib/libc.so.6
#1  0x402cd880 in ?? () from /lib/libc.so.6
#2  0x401de4c2 in strtold_l () from /lib/libc.so.6
#3  0x081eb261 in smb_panic2 ()
#4  0x081eb1ea in smb_panic ()
#5  0x082645e3 in smbd_server_fd ()
#6  0x082654ce in main ()

On Jun 19, 2005, at 10:53 PM, Christian Perrier wrote:


Quoting Dan Aronson ([EMAIL PROTECTED]):


Package: samba
Version: 3.0.14a-3
Severity: normal

Last night I tried to connect to a samba share for osx (Tiger  
10.4.1).

I never configured samba on this new 3.1 install.  Today I found lots
of email from the 'panic action' script.




Forwarding some of these as part of the bug report might help...

Doing so, please answer to the bug report and not to me.







--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#315016: samba: panic called from smbd_server_fd

2005-06-19 Thread Dan Aronson
Package: samba
Version: 3.0.14a-3
Severity: normal

Last night I tried to connect to a samba share for osx (Tiger 10.4.1).
I never configured samba on this new 3.1 install.  Today I found lots
of email from the 'panic action' script.

-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.4.27-2-386
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages samba depends on:
ii  debconf [debconf-2.0]   1.4.30.13Debian configuration management sy
ii  libacl1 2.2.23-1 Access control list shared library
ii  libattr12.4.16-1 Extended attribute shared library
ii  libc6   2.3.2.ds1-22 GNU C Library: Shared libraries an
ii  libcomerr2  1.37-2sarge1 common error description library
ii  libcupsys2-gnutls10 1.1.23-10Common UNIX Printing System(tm) - 
ii  libkrb531.3.6-2  MIT Kerberos runtime libraries
ii  libldap22.1.30-8 OpenLDAP libraries
ii  libpam-modules  0.76-22  Pluggable Authentication Modules f
ii  libpam-runtime  0.76-22  Runtime support for the PAM librar
ii  libpam0g0.76-22  Pluggable Authentication Modules l
ii  libpopt01.7-5lib for parsing cmdline parameters
ii  logrotate   3.7-5Log rotation utility
ii  netbase 4.21 Basic TCP/IP networking system
ii  samba-common3.0.14a-3Samba common files used by both th

-- debconf information:
  samba/nmbd_from_inetd:
  samba/run_mode: daemons
  samba/log_files_moved:
  samba/tdbsam: false
  samba/generate_smbpasswd: true


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]