Bug 10764 - Core Dump when accessing Printer Properties
Core Dump when accessing Printer Properties
Status: NEW
Product: Samba 4.1 and newer
Classification: Unclassified
Component: Printing
PPC Linux
: P5 normal
: ---
Assigned To: David Disseldorp
Samba QA Contact
Depends on:
  Show dependency treegraph
Reported: 2014-08-08 12:02 UTC by Tom
Modified: 2014-08-11 06:47 UTC (History)
1 user (show)

See Also:

The syslog with backtrace (63.90 KB, text/plain)
2014-08-11 06:03 UTC, Tom
no flags Details
level 10 logfile (591.42 KB, application/x-gzip)
2014-08-11 06:47 UTC, Tom
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tom 2014-08-08 12:02:07 UTC
I setup a print-server on a debian wheezy powerpc system using samba 4.1.9 from wheezy backports. I followed the steps in the wiki
I'm looged in Administrator from my x64 Win8.1 Client and
when i try to right-click on a printer an show its properties or change its default settings i get an alert stating "printer properties cannot be displayed" and most of the time smbd core dumps.
I setup the ADC using 4.1.3 and at that time could not install the postscript-drivers due to rpc errors. So i updated to 4.1.9. Tehe rpc errors are gone, i can install the PS-Drivers using cupsaddsmb wiithout errors, but i cannot access them....
Anyone else seen this before ?

my smb.conf:
# Global parameters
	workgroup = XXXX
	realm = AD.XXXX.DE
	netbios name = DNS2
	server role = active directory domain controller
	server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl, winbind, ntp_signd, kcc, dnsupdate
	idmap_ldb:use rfc2307 = yes
	load printers = yes
	printing = CUPS
	printcap name = CUPS
	cups server = cups.xxxx.de
	bind interfaces only = yes
	interfaces =
	rpc_server:spoolss = external
	rpc_daemon:spoolssd = fork

	path = /var/lib/samba/sysvol/ad.xxxx.de/scripts
	read only = No

	path = /var/spool/samba
	printable = yes
	read only = no
	guest ok = yes
	printing = CUPS

	path = /var/lib/samba/printers
	comment = printer drivers
	writeable = yes
	write list = @"domain admins"

	path = /var/lib/samba/sysvol
	read only = No

the log file:

[2014/08/08 08:42:49.777316,  0] ../source3/lib/util.c:785(smb_panic_s3)
  PANIC (pid 3963): assert failed: pjob->jobid == jobid
[2014/08/08 08:42:49.779026,  0] ../source3/lib/util.c:896(log_stack_trace)
  BACKTRACE: 28 stack frames:
   #0 /usr/lib/powerpc-linux-gnu/libsmbconf.so.0(log_stack_trace+0x40) [0x200725b0]
   #1 /usr/lib/powerpc-linux-gnu/libsmbconf.so.0(smb_panic_s3+0x44) [0x200726d0]
   #2 /usr/lib/powerpc-linux-gnu/libsamba-util.so.0(smb_panic+0x54) [0x20746ef0]
   #3 /usr/lib/powerpc-linux-gnu/samba/libsmbd_base.so.0(+0xae07c) [0x2045407c]
   #4 /usr/lib/powerpc-linux-gnu/samba/libsmbd_base.so.0(print_queue_status+0x538) [0x2045a594]
   #5 /usr/lib/powerpc-linux-gnu/samba/libsmbd_base.so.0(+0x1e4100) [0x2058a100]
   #6 /usr/lib/powerpc-linux-gnu/samba/libsmbd_base.so.0(_spoolss_RouterRefreshPrinterChangeNotify+0x378) [0x2058cfb8]
   #7 /usr/lib/powerpc-linux-gnu/samba/libsmbd_base.so.0(+0x1f8d68) [0x2059ed68]
   #8 /usr/lib/powerpc-linux-gnu/samba/libsmbd_base.so.0(+0x1d944c) [0x2057f44c]
   #9 /usr/lib/powerpc-linux-gnu/samba/libsmbd_base.so.0(process_complete_pdu+0x12e8) [0x205814e4]
   #10 /usr/lib/powerpc-linux-gnu/samba/libsmbd_base.so.0(process_incoming_data+0x178) [0x2057d7a4]
   #11 /usr/lib/powerpc-linux-gnu/samba/libsmbd_base.so.0(np_write_send+0x1c0) [0x2057df04]
   #12 /usr/lib/powerpc-linux-gnu/samba/libsmbd_base.so.0(smb2_ioctl_named_pipe+0x184) [0x2051dd2c]
   #13 /usr/lib/powerpc-linux-gnu/samba/libsmbd_base.so.0(smbd_smb2_request_process_ioctl+0x504) [0x2051d1dc]
   #14 /usr/lib/powerpc-linux-gnu/samba/libsmbd_base.so.0(smbd_smb2_request_dispatch+0xa4c) [0x2050f0f4]
   #15 /usr/lib/powerpc-linux-gnu/samba/libsmbd_base.so.0(+0x169c00) [0x2050fc00]
   #16 /usr/lib/powerpc-linux-gnu/samba/libsmbd_base.so.0(+0x169e78) [0x2050fe78]
   #17 /usr/lib/powerpc-linux-gnu/libsmbconf.so.0(run_events_poll+0x2fc) [0x200976b0]
   #18 /usr/lib/powerpc-linux-gnu/libsmbconf.so.0(+0x4b838) [0x20097838]
   #19 /usr/lib/powerpc-linux-gnu/libtevent.so.0(_tevent_loop_once+0xdc) [0x1fb19c1c]
   #20 /usr/lib/powerpc-linux-gnu/samba/libsmbd_base.so.0(smbd_process+0xdb8) [0x204fa7f4]
   #21 /usr/sbin/smbd(+0x9a70) [0x207c1a70]
   #22 /usr/lib/powerpc-linux-gnu/libsmbconf.so.0(run_events_poll+0x2fc) [0x200976b0]
   #23 /usr/lib/powerpc-linux-gnu/libsmbconf.so.0(+0x4b838) [0x20097838]
   #24 /usr/lib/powerpc-linux-gnu/libtevent.so.0(_tevent_loop_once+0xdc) [0x1fb19c1c]
   #25 /usr/sbin/smbd(main+0x1204) [0x207be2c4]
   #26 /lib/powerpc-linux-gnu/libc.so.6(+0x1fd4c) [0x1f99cd4c]
   #27 /lib/powerpc-linux-gnu/libc.so.6(+0x1ff10) [0x1f99cf10]
[2014/08/08 08:42:49.782734,  0] ../source3/lib/dumpcore.c:317(dump_core)
  dumping core in /var/log/samba/cores/smbd
  STATUS=daemon 'smbd' finished starting up and ready to serve connectionsPANIC: assert failed at ../source3/printing/printing.c(486): pjob->jobid == jobid
Comment 1 David Disseldorp 2014-08-08 12:16:58 UTC
Thanks for the report. I'll see if I can find a powerpc big-endian machine to machine to reproduce this on.

In the meantime, it'd help if you could attach the full level 10 smbd logs, even more so if you could capture the network traffic at the time of the panic.
Comment 2 Tom 2014-08-11 06:03:55 UTC
Created attachment 10188 [details]
The syslog with backtrace
Comment 3 Tom 2014-08-11 06:47:34 UTC
Created attachment 10189 [details]
level 10 logfile

This occurence of the crash happened at 7:48:56. The contents of the logfile starts at 7:48:58. I couldn't find other logs with a timestamp before the crash.
Pls tell me this file isn't what you need.