Ubuntu
samba package

Panic or segfault in Samba

Bug #1958743 reported by araemo on 2022-01-23

This bug report is a duplicate of: Bug #1955588: Panic or segfault in Samba. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	samba (Ubuntu)	Incomplete	Undecided	Unassigned

Bug Description

I am reporting this based on the "Panic or segfault in Samba" automatic notification. I have installed the samba-dbgsym package, and this is the first report I have received since installing that.

I do not know the specific actions being taken at the time of the panic or segfault, since this is a file server accessed by multiple users, and there was no noticeable user impact.

I am attaching the dgb report and the log file that contains the segmentation fault message.

Revision history for this message

araemo (araemo) wrote on 2022-01-23:

Panic email/gdb trace Edit (3.8 KiB, text/plain)

Revision history for this message

araemo (araemo) wrote on 2022-01-23:

client-specific log file with error message Edit (1.8 KiB, text/plain)

Log file attached.

Revision history for this message

Sergio Durigan Junior (sergiodj) wrote on 2022-01-24:

Thank you for taking the time to file a bug report.

I appreciate the fact that you attached the stack trace and tried to provide more information about the segfault, but I would like to take a step back and ask if you could try to provide some information about what was being done when the segfault happened. Do you think you could try to come up with a reproducer? Have you experienced this more than once? Also, could you provide more information about your system? I'm interested in knowing which Ubuntu release you're using, and what your Samba package version is.

Since there is not enough information in your report to begin triage or to
differentiate between a local configuration problem and a bug in Ubuntu, I
am marking this bug as "Incomplete". We would be grateful if you would:
provide a more complete description of the problem, explain why you
believe this is a bug in Ubuntu rather than a problem specific to your
system, and then change the bug status back to "New".

For local configuration issues, you can find assistance here:
http://www.ubuntu.com/support/community