Further similar segfaults today:
The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 15280 (/usr/sbin/smbd).
This means there was a problem with the program, such as a segfault.
Below is a backtrace for this process generated with gdb, which shows
the state of the
Further similar segfaults today:
The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 15280 (/usr/sbin/smbd).
This means there was a problem with the program, such as a segfault.
Below is a backtrace for this process generated with gdb, which shows
the state of the
Public bug reported:
Binary package hint: samba
Just to clarify my setup.
I have a HP Prolient DL140 G3 with an External MSA60 Disk Storage Array
setup as a file server for my users file areas. I have configured the
disk array as software raid5 with LVM on top of it. There are then
various LVM
Server is running Hardy LTS so it's 3.0.28a-1ubuntu4
--
Segfault in Samba
https://bugs.launchpad.net/bugs/264982
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-server-bugs mailing list
Public bug reported:
Binary package hint: samba
Just to clarify my setup.
I have a HP Prolient DL140 G3 with an External MSA60 Disk Storage Array
setup as a file server for my users file areas. I have configured the
disk array as software raid5 with LVM on top of it. There are then
various LVM
Server is running Hardy LTS so it's 3.0.28a-1ubuntu4
--
Segfault in Samba
https://bugs.launchpad.net/bugs/264982
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I'm sorry I can't do that. I live behind a http/https proxy so apport
will not work for me. See this bug for info.
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/94130
I have a .crash file though, is there any other way I can send it?
** Changed in: pidgin (Ubuntu)
Status: Won't
Public bug reported:
Binary package hint: pidgin
When using Pidgin connected to a OpenFire based jabber server pidgin
regularly closes. When I run it from the console I get the following
stack dump.
*** glibc detected *** pidgin: double free or corruption (fasttop): 0x084aa5a0
***
===
Public bug reported:
Binary package hint: samba
The machine is AMD64 running Ubuntu 6.06 LTS. It's configured as a
domain member in our Windows Active Directory Domain. It's configured as
a print server. It's using CUPS as it's printer backend. The backtrace
from the samba panic action script
Public bug reported:
I installed the 'apachetop' package on my AMD64 based LAMP server
installation. The init script provided in the package fails to start
fam. When I attempt to start fam via '/etc/init.d/fam start' the
following is outputted:
[EMAIL PROTECTED]:~# /etc/init.d/fam start
* -n
10 matches
Mail list logo
