GNOME Bugzilla – Bug 234075
Crash when trying to print tasks
Last modified: 2002-11-15 22:17:12 UTC
Package: Evolution Priority: Normal Version: 1.2.0 Synopsis: Crash when trying to print tasks Bugzilla-Product: Evolution Bugzilla-Component: Tasks Description: Description of Problem: I have made a custom view on my tasks. When I try to send it to the printer it crashes the tasks-component. My custom view is set up like this: Fields: Summary and categories Group by: categories then by priority Sort by: Categories then by priority Steps to reproduce the problem: 1. Make the custom view on your tasks as described above. 2. In the tasks view, click the printer icon on the toolbar. 3. In the dialog-box that appears, click the 'Print' button. This brings up a new dialog-box 4. In the next dialog-box, click the 'Print' button to send the tasks view as 'Generic Postscript' to the printer. 5. Now the processor-load goes to 100% for a couple of seconds and then the crash-dialog appears (and Bug-Buddy can be started...) Actual Results: Tasks-view component crashes. Expected Results: A print-out of my tasks view as I have configured it and as seen on the screen and in the print-preview. How often does this happen? Everytime I have tried it (twice). Additional Information: May come. I have no further time to investigate right now. Debugging Information: Backtrace was generated from '/usr/bin/evolution-calendar' (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 8192 (LWP 2147)] 0x420ae169 in wait4 () from /lib/i686/libc.so.6
+ Trace 30456
Thread 1 (Thread 8192 (LWP 2147))
Unknown reporter: ligaard@trillegaarden.dk, changed to bugbuddy-import@ximian.com. Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
*** This bug has been marked as a duplicate of 231551 ***