On 26/10/13 10:37, Michael Meskes wrote:
> Package: libdbus-1-3
> Version: 1.6.16-1
> Severity: grave
>
> Most of the times cups comes up I get this:
>
> Oct 25 20:27:57 aragorn kernel: [ 389.581166] cupsd[2937]:
> segfault at 8 ip 00007faeb7c98cd0 sp 00007fff18af7148 error
> 4 in libdbus-1.so.3.7.5[7faeb7c72000+45000]
>
> Sometimes actually this only happens when the printer is
> switched on or a job is send to cups.
"thread apply all bt" backtrace from cupsd, please? Sorry, I don't know
anything specific about cupsd or how to debug it, apart from "nothing
related to printing ever works first time, including cupsd" :-) Cc'ing
cups maintainers in case they have useful advice on getting a backtrace
or core dump from it.
There are basically two possibilities for a segfault inside libdbus:
either libdbus has a bug, or another module used by cupsd (either the
daemon itself or some other library or plugin) is using libdbus
incorrectly (e.g. getting the refcounting of an object wrong, or using
it in threads without thread initialization). Without a backtrace, we
can't say which.
Why is this RC severity? If cupsd links libdbus, then almost by
definition it isn't "breaks unrelated software"...
S
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
