Re: Crash on Attempt to Print with CUPS

From: Edward Ruggeri <ruggeri_at_uchicago.edu>
Date: Tue Mar 27 2007 - 06:23:39 CEST

On Mon, 26 Mar 2007 20:50:14 -0500, Hubert Figuiere <hfiguiere@teaser.fr>
wrote:
> Edward Ruggeri wrote:
>> I'm not sure if this is the right place for this question. I use
>> Gnome-Office on freeBSD. I don't have Gnome installed though -- I use
>> Xfce4. The applications generally run fine, except when I try to
>> print. If cupsd is running when I hit print in the file menu, the
>> program will immediately crash. If cupsd isn't running, there's no
>> problem.
>>
>> I noticed that most other applications print with the xfprint program,
>> but the "print sheets" dialogue seems to be different, perhaps it is
>> meant to work only with gnome? No other application exhibits this
>> behavior, besides all the gnome-office applications.
>
> Do you have a stack trace?
>
> Hub

I have copied below the report from Bug-Report. Thanks very much for any
possible thoughts.

System: FreeBSD 6.2-STABLE FreeBSD 6.2-STABLE #0: Mon Mar 19 15:28:22 CDT
2007 root@XXXXX.com:/usr/obj/usr/src/sys/KOLMOGOROV i386
X Vendor: The X.Org Foundation
X Vendor Release: 60900000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 44068 vsize: 44068 resident: 24628 share: 33497204
rss: 24628 rss_rlim: 6157
CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0
timeout: 0 it_real_value: 0 frequency: 133

Backtrace was generated from '/usr/local/bin/AbiWord-2.4'

(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...[New Thread 0x893f600 (LWP 100151)]
[New Thread 0x8569000 (runnable)]
[New LWP 100155]
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...[Switching to LWP 100155]
0x292904f7 in pthread_testcancel () from /lib/libpthread.so.2
#0 0x292904f7 in pthread_testcancel () from /lib/libpthread.so.2
#1 0x2928980f in pthread_mutexattr_init () from /lib/libpthread.so.2
#2 0x08561400 in ?? ()

Thread 3 (LWP 100155):
#0 0x292904f7 in pthread_testcancel () from /lib/libpthread.so.2
No symbol table info available.
#1 0x2928980f in pthread_mutexattr_init () from /lib/libpthread.so.2
No symbol table info available.
#2 0x08561400 in ?? ()
No symbol table info available.

Thread 2 (Thread 0x8569000 (runnable)):
#0 0x2930e977 in poll () from /lib/libc.so.6
No symbol table info available.
#0 0x292904f7 in pthread_testcancel () from /lib/libpthread.so.2

----------- .xsession-errors ---------------------
** (AbiWord-2.4:73113): WARNING **: rebuild_menu_cb, could not set value
of PhysicalSize to Letter
(gnome-terminal:73117): Vte-WARNING **: No handler for control sequence
`device-control-string' defined.
(AbiWord-2.4:93588): GnomePrintCupsPlugin-WARNING **: iconv does not
support ppd character encoding: UTF-8, trying CSISOLatin1
** (AbiWord-2.4:93588): WARNING **: Could not find child for option
"PhysicalSize" with id "Letter"
** (AbiWord-2.4:93588): WARNING **: rebuild_menu_cb, could not set value
of PhysicalSize to Letter
warning: Unable to get location for thread creation breakpoint: generic
error
Backtrace limit of 200 exceeded
/usr/local/share/gnome/bug-buddy/gdb-cmd:3: Error in sourced command file:
Backtrace limit of 200 exceeded
Backtrace limit of 200 exceeded
--------------------------------------------------
-----------------------------------------------
To unsubscribe from this list, send a message to
abiword-user-request@abisource.com with the word
unsubscribe in the message body.
Received on Tue Mar 27 06:23:06 2007

This archive was generated by hypermail 2.1.8 : Tue Mar 27 2007 - 06:23:07 CEST