cupsd crashes

Bug #23103 reported by Pascual Muñoz
12
Affects Status Importance Assigned to Milestone
cupsys (Ubuntu)
Invalid
Medium
Martin Pitt

Bug Description

After upgrading from Ubuntu Hoary 5.04 to Breezy 5.10 cupsd crashes when starting.
I set in cupsd.conf LogLevel debug6762 and start /etc/init.d/cupsys start

In /var/log/cups/error.log I find:

I [03/Oct/2005:19:22:03 +0200] Full reload complete.
D [03/Oct/2005:19:22:03 +0200] StartListening: NumListeners=1
D [03/Oct/2005:19:22:03 +0200] StartListening: address=7f000001 port=631
D [03/Oct/2005:19:22:03 +0200] ResumeListening: setting input bits...
d [03/Oct/2005:19:22:03 +0200] ResumeListening: Adding fd 0 to InputSet...
d [03/Oct/2005:19:22:03 +0200] StartServer: Adding fd 2 to InputSet...
d [03/Oct/2005:19:22:03 +0200] AddCert: adding certificate for pid 0
E [03/Oct/2005:19:22:03 +0200] Unable to write pid file

Revision history for this message
Matt Zimmerman (mdz) wrote :

Working fine here; please run it under strace -f and send the output

Revision history for this message
Pascual Muñoz (pascual-ieee) wrote :

Created an attachment (id=4316)
strace -f -o cupsd.output.txt cupsd

Revision history for this message
Martin Pitt (pitti) wrote :

19061 open("/var/run/cups/cupsd.pid", O_RDWR|O_CREAT, 0644) = -1 EACCES (Permission denied)

That really seems to be the problem. However, /var/run/cups should be owned by cupsys:lpadmin. Do you have any idea why it isn't for you?

Changed in cupsys:
assignee: debzilla → pitti
status: Unconfirmed → Needs Info
Revision history for this message
Martin Pitt (pitti) wrote :

Do you still have this problem with the latest Dapper? What is

  ls -ld /var/run/cups

and

  ls -l /var/run/cups

for you?

Revision history for this message
Martin Pitt (pitti) wrote :

No answer for a month and lacking information. Dapper has a new version of cupsys with many fixes.

Please reopen this bug if you still encounter this. Thank you!

Changed in cupsys:
status: Needs Info → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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