Ubuntu
samba package

smbd crashed with SIGABRT in push_ucs2_talloc()

Bug #957667 reported by Stephen Cradock on 2012-03-17

This bug report is a duplicate of: Bug #916576: smbd crashed with SIGABRT in push_ucs2_talloc()/lp_servicename returns NULL. Edit Remove

This bug affects 1 person

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

Bug Description

I enabled sharing on my Public folder, had to install samba. Restarted as instructed, sharing enabled, file transfer worked to an external machine. Then this crash happened.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: samba 2:3.6.3-1ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Fri Mar 16 20:40:05 2012
ExecutablePath: /usr/sbin/smbd
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
ProcCmdline: smbd -F
ProcEnviron:
PATH=(custom, no user)
TERM=linux
Signal: 6
SourcePackage: samba
StacktraceTop:
?? () from /lib/x86_64-linux-gnu/libc.so.6
push_ucs2_talloc ()
E_md4hash ()
create_volume_objectid ()
?? ()
Title: smbd crashed with SIGABRT in push_ucs2_talloc()
UpgradeStatus: Upgraded to precise on 2012-02-12 (33 days ago)
UserGroups:

Tags:

Revision history for this message

Stephen Cradock (s-cradock) wrote on 2012-03-17:

Dependencies.txt Edit (3.0 KiB, text/plain; charset="utf-8")

visibility:

private → public

Revision history for this message

Apport retracing service (apport) wrote on 2012-03-17: This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #916576, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

tags:

removed: need-amd64-retrace

Revision history for this message

Stephen Cradock (s-cradock) wrote on 2012-03-17:

The duplicate status may be correct, but it is not possible to get to the report #916576. This may be because it is marked private. Please change the status of the original report so that those interested can access it.

Is there any reason why bug reports default to "Private"? It seems pointless to me - if no-one can see a report we cannot mark oit as aaffecting us, add possibly useful information, or even know that it exists, unless we happen to report an identical bug.

Please reconsider the Default status for all bugs!