[bug-notifications] [cupsd 0004634]: CSWcupsd 1.4.3, REV=2010.06.29 no longer starts
Mantis Bug Tracker
noreply at opencsw.org
Fri Dec 17 09:38:13 CET 2010
A NOTE has been added to this issue.
======================================================================
https://www.opencsw.org/mantis/view.php?id=4634
======================================================================
Reported By: flod
Assigned To: maciej
======================================================================
Project: cupsd
Issue ID: 4634
Category: regular use
Reproducibility: always
Severity: block
Priority: normal
Status: feedback
======================================================================
Date Submitted: 2010-12-16 05:33 CET
Last Modified: 2010-12-17 09:38 CET
======================================================================
Summary: CSWcupsd 1.4.3,REV=2010.06.29 no longer starts
Description:
cupsd can no longer be started.
/var/svc/log/network-cswcups:default.log:
cups: unable to start scheduler.
[ Dec 16 05:25:20 Method "start" exited with status 1 ]
[ Dec 16 05:25:20 Executing start method
("/var/opt/csw/svc/method/svc-cswcups start") ]
ld.so.1: cupsd: fatal: relocation error: file /opt/csw/sbin/cupsd: symbol
_httpReadGNUTLS: referenced symbol not found
Killed
It looks like all cups packages are on 1.4.4. except CSWcupsd .
This should normally not happen when releasing.
======================================================================
----------------------------------------------------------------------
(0008582) maciej (manager) - 2010-12-17 09:38
https://www.opencsw.org/mantis/view.php?id=4634#c8582
----------------------------------------------------------------------
Bad news on sparc front. cupsd segfaults when reading configuration.
(dbx) run -f
Running: cupsd -f
(process id 11919)
Reading libc_psr.so.1
Reading en_US.UTF-8.so.3
Reading methods_unicode.so.3
t at 1 (l at 1) signal SEGV (no mapping at the fault address) in
cupsdReadConfiguration at 0x27894
0x00027894: cupsdReadConfiguration+0x24fc: ld [%o5], %i4
More information about the bug-notifications
mailing list