Bug#380663: cupsd SEGV

2006-08-22 Thread Benedict Adamson
Kenshi Muto wrote: ... I suspect your file hasn't any Printer line by something reason. ... Correct. I manually added a Printer line to /etc/cups/classes.conf and was then able to start cupsd. I initially tried to use lpadmin, but that failed because it tries to communicate with cupsd. I

Bug#380663: cupsd SEGV

2006-08-13 Thread Kenshi Muto
At Wed, 09 Aug 2006 22:40:24 +0100, Benedict Adamson wrote: The stack trace given by gdb is as follows: #0 cupsdFindAvailablePrinter (name=0x80ba720 Postscript) at classes.c:282 #1 0x0807dfef in cupsdCheckJobs () at job.c:343 #2 0x080667e9 in main (argc=2, argv=0xaff09534) at main.c:551

Bug#380663: cupsd SEGV

2006-08-09 Thread Kenshi Muto
At Tue, 08 Aug 2006 23:53:29 +0100, Benedict Adamson wrote: Running /usr/sbin/cupsd -F under gdb shows that the immediate cause of the crash is a SEGV. FWIW, here is the top of the stack trace: #0 0x08052511 in ?? () #1 0x080ba720 in ?? () #2 0xa7d60c45 in _IO_file_sync () from

Bug#380663: cupsd SEGV

2006-08-09 Thread Benedict Adamson
Kenshi Muto wrote: ... I still couldn't reproduce your problem. Could you check again with nostripped version? ... The stack trace given by gdb is as follows: #0 cupsdFindAvailablePrinter (name=0x80ba720 Postscript) at classes.c:282 #1 0x0807dfef in cupsdCheckJobs () at job.c:343 #2

Bug#380663: cupsd SEGV

2006-08-08 Thread Benedict Adamson
I have the same problem, but using cupsys 1.2.2-1. Running /usr/sbin/cupsd -F under gdb shows that the immediate cause of the crash is a SEGV. FWIW, here is the top of the stack trace: #0 0x08052511 in ?? () #1 0x080ba720 in ?? () #2 0xa7d60c45 in _IO_file_sync () from