Bug#220538: glabels: Segfaults when printing to cups printer

[Ramin Motakef]

Andrew Lau <netsnipe@users.sourceforge.net> writes:

> Hey everyone,
>
> On Thu, Nov 13, 2003 at 12:14:25PM +0100, Jordi Mallach wrote:
>> I'm not so sure this bug is the same as my bug.
>
> I think you're right Jordi. I just took a real look at the backtrace and
> it seems like these three lines keep recurring.
>
> #49 0x416955d9 in ERR_load_strings () from /usr/lib/i686/cmov/libcrypto.so.0.9.7
> #50 0x4173a540 in ssl3_undef_enc_method () from /usr/lib/i686/cmov/libssl.so.0.9.7
> #51 0x416fc088 in rand_ssleay_meth () from /usr/lib/i686/cmov/libcrypto.so.0.9.7
>
> Ramin, please disable SSL on your CUPS connection and see if the bug
> still happens. I'm not 100% sure about your backtrace, so please do the
> following.

How do i do that? Do i have to recompile cups? "Encryption Never"
doesn't seem to change anything in the backtrace.


> $ ulimit -c 1000000; glabels &

done

> crash it and the terminal should say core dumped.

As a note for others: to get a coredump i had to run
GNOME_DISABLE_CRASH_DIALOG=1 glabels --disable-crash-dialog


> $ gdb --core=core
> (gdb) bt
>
> If the output is different, please resend it. In the meantime, I'm going
> to reopen and reassign this bug report to libgnomecups1.0-1 and see if
> Ross Burton can make any sense out of it.

It is different, but i fear not very helpful:

(gdb) bt
#0  0x41682dba in ?? ()
#1  0x4167f3c5 in ?? ()
#2  0x41606540 in ?? ()
#3  0x41726540 in ?? ()
#4  0xbfffcb2c in ?? ()
#5  0x4167f348 in ?? ()
#6  0x416f50c0 in ?? ()
#7  0x08483640 in ?? ()
#8  0x08483640 in ?? ()
#9  0x41726540 in ?? ()
#10 0x0000000a in ?? ()
#11 0x00000001 in ?? ()
#12 0x41682db0 in ?? ()
#13 0x084826a4 in ?? ()
#14 0x416f50c0 in ?? ()
#15 0x416d9069 in ?? ()
#16 0x416f7b10 in ?? ()
#17 0x4167f040 in ?? ()
#18 0x08483640 in ?? ()
#19 0x41726540 in ?? ()
#20 0xbfffcb6c in ?? ()
#21 0x4167f000 in ?? ()
#22 0x416f50c0 in ?? ()
#23 0x416d9069 in ?? ()
#24 0x08483640 in ?? ()
#25 0xbfffd0f8 in ?? ()
#26 0x0000000a in ?? ()
#27 0x00000001 in ?? ()
#28 0x416d9069 in ?? ()
#29 0x14064057 in ?? ()
#30 0x416f50c0 in ?? ()
#31 0x416d9069 in ?? ()
#32 0x08483640 in ?? ()
#33 0x41682b28 in ?? ()
#34 0x08483640 in ?? ()
#35 0x41726540 in ?? ()
#36 0xbfffcbd0 in ?? ()
#37 0x41682b1a in ?? ()
#38 0x00000009 in ?? ()
#39 0x00000001 in ?? ()
#40 0x416d9069 in ?? ()
#41 0x00000184 in ?? ()
#42 0x416f50c0 in ?? ()
#43 0x41726540 in ?? ()
#44 0x14000000 in ?? ()
#45 0x416815b5 in ?? ()
#46 0x00000002 in ?? ()
#47 0x416f7720 in ?? ()
#48 0x0000022a in ?? ()
#49 0x416815d9 in ?? ()
#50 0x41726540 in ?? ()
#51 0x416e8088 in ?? ()

Is there an easy way to compile glable with debugging symbols with
cdbs?


> Ross: What on Earth is causing this? libgnomeprint, libgnomecupsys,
> cupsys, libssl? I can't tell where it's starting at the moment.

For what its worth:

I updated glabels on my Notebook, which also runs unstable but a
slightly older version and printing worked.

Then i updatet cupsys from 1.1.19final-3 to 1.1.19final-4. 
Printig still worked.

Then libcupsys2, also from 1.1.19final3 to 1.1.19final-4 and from
there on printing causes a segfault.

So i think libcupsys2 is to blame. I will try 1.1.20candidate6-1 as
soon as it get in the archive.


> Thanks in advanced,
> Andrew "Netsnipe" Lau
>

Greetings and thanks,
Ramin