Ubuntu
samba package

SIGSEGV on printing

Bug #356187 reported by Joerg Delker
2
Affects Status Importance Assigned to Milestone
samba (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: samba

Using: Ubuntu 8.04.2,
samba: Installed: 3.0.28a-1ubuntu4.7

After upgrading, smbd throws SIGSEGV when trying to print from a windows client to a smb print share.
Result: Nothing is printed. Windows shows error message.

gdb shows the following trace after attaching to the process:
(gdb) c
Continuing.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb7a596d0 (LWP 27999)]
0x080d09d7 in reply_printopen (conn=0x8530d88, inbuf=0x84ee298 "", outbuf=0x850e6e0 "", dum_size=58, dum_buffsize=131072)
    at smbd/reply.c:3623
3623 smbd/reply.c: No such file or directory.
        in smbd/reply.c
(gdb) bt
#0 0x080d09d7 in reply_printopen (conn=0x8530d88, inbuf=0x84ee298 "", outbuf=0x850e6e0 "", dum_size=58, dum_buffsize=131072)
    at smbd/reply.c:3623
#1 0x0810f93e in switch_message (type=192, inbuf=0x84ee298 "", outbuf=0x850e6e0 "", size=58, bufsize=131072) at smbd/process.c:1004
#2 0x08110d9b in smbd_process () at smbd/process.c:1031
#3 0x0835ec68 in main (argc=Cannot access memory at address 0x25
) at smbd/server.c:1120

Revision history for this message
Joerg Delker (ubuntu-delker) wrote :

Forgot to post the corresponding smbd.log:

Apr 6 13:00:08 elwood smbd[27999]: [2009/04/06 13:00:08, 0] lib/fault.c:fault_report(41)
Apr 6 13:00:08 elwood smbd[27999]: ===============================================================
Apr 6 13:00:08 elwood smbd[27999]: [2009/04/06 13:00:08, 0] lib/fault.c:fault_report(42)
Apr 6 13:00:08 elwood smbd[27999]: INTERNAL ERROR: Signal 11 in pid 27999 (3.0.28a)
Apr 6 13:00:08 elwood smbd[27999]: Please read the Trouble-Shooting section of the Samba3-HOWTO
Apr 6 13:00:08 elwood smbd[27999]: [2009/04/06 13:00:08, 0] lib/fault.c:fault_report(44)
Apr 6 13:00:08 elwood smbd[27999]:
Apr 6 13:00:08 elwood smbd[27999]: From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
Apr 6 13:00:08 elwood smbd[27999]: [2009/04/06 13:00:08, 0] lib/fault.c:fault_report(45)
Apr 6 13:00:08 elwood smbd[27999]: ===============================================================
Apr 6 13:00:08 elwood smbd[27999]: [2009/04/06 13:00:08, 0] lib/util.c:smb_panic(1633)
Apr 6 13:00:08 elwood smbd[27999]: PANIC (pid 27999): internal error
Apr 6 13:00:08 elwood smbd[27999]: [2009/04/06 13:00:08, 0] lib/util.c:log_stack_trace(1737)
Apr 6 13:00:08 elwood smbd[27999]: BACKTRACE: 9 stack frames:
Apr 6 13:00:08 elwood smbd[27999]: #0 /usr/sbin/smbd(log_stack_trace+0x2d) [0x828abbd]
Apr 6 13:00:08 elwood smbd[27999]: #1 /usr/sbin/smbd(smb_panic+0x5d) [0x828aced]
Apr 6 13:00:08 elwood smbd[27999]: #2 /usr/sbin/smbd [0x827556a]
Apr 6 13:00:08 elwood smbd[27999]: #3 [0xb7eed420]
Apr 6 13:00:08 elwood smbd[27999]: #4 /usr/sbin/smbd [0x810f93e]
Apr 6 13:00:08 elwood smbd[27999]: #5 /usr/sbin/smbd(smbd_process+0x89b) [0x8110d9b]
Apr 6 13:00:08 elwood smbd[27999]: #6 /usr/sbin/smbd(main+0xa18) [0x835ec68]
Apr 6 13:00:08 elwood smbd[27999]: #7 /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7af6450]
Apr 6 13:00:08 elwood smbd[27999]: #8 /usr/sbin/smbd [0x8094361]
Apr 6 13:00:08 elwood smbd[27999]: [2009/04/06 13:00:08, 0] lib/util.c:smb_panic(1638)
Apr 6 13:00:08 elwood smbd[27999]: smb_panic(): calling panic action [/usr/share/samba/panic-action 27999]
Apr 6 13:00:08 elwood smbd[27999]: [2009/04/06 13:00:08, 0] lib/util.c:smb_panic(1646)
Apr 6 13:00:08 elwood smbd[27999]: smb_panic(): action returned status 0
Apr 6 13:00:08 elwood smbd[27999]: [2009/04/06 13:00:08, 0] lib/fault.c:dump_core(181)
Apr 6 13:00:08 elwood smbd[27999]: dumping core in /var/log/samba/cores/smbd
Apr 6 13:00:08 elwood smbd[27999]:

Revision history for this message
Chuck Short (zulcss) wrote :

Hi,

I was wondering if you were still having this problem?

Regards
chuck

Changed in samba (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Chuck Short (zulcss) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
Chuck Short (zulcss) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in samba (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.