After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 315474 - printing in calendar crashes - daily view with many appts
printing in calendar crashes - daily view with many appts
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Calendar
2.2.x (obsolete)
Other All
: High critical
: ---
Assigned To: Chakravarthi
Evolution QA team
: 315676 315687 (view as bug list)
Depends on:
Blocks: 318200
 
 
Reported: 2005-09-07 17:28 UTC by Allen Riddell
Modified: 2005-12-20 20:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description Allen Riddell 2005-09-07 17:28:31 UTC
Steps to reproduce:
When I print -- (click on the print button _in the print dialog_)
crashes almost every time when I have many appts (like 10+)

Steps to reproduce the crash:
1. Make tons of appointments, ovrelapping etc
2. click on print button
3. click on print button _in print dialog_ -- crash..

Expected Results:


How often does this happen?

almost every time...

Additional Information:

It prints fine if there are only a few appts (althought sometimes it
crashes anyway.)




Stack trace:
Backtrace was generated from '/usr/bin/evolution'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
(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)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 1094947584 (LWP 12125)]
[New Thread 1530141616 (LWP 12334)]
[New Thread 1177820080 (LWP 12333)]
[New Thread 1109482416 (LWP 12129)]
(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)
(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)
0x40bb1201 in __waitpid_nocancel () from /lib/tls/libpthread.so.0

Thread 3 (Thread 1177820080 (LWP 12333))

  • #0 __lll_mutex_lock_wait
    from /lib/tls/libpthread.so.0
  • #1 _L_mutex_lock_29
    from /lib/tls/libpthread.so.0
  • #2 ??
  • #3 ??
  • #4 ??
  • #5 in6addr_any
    from /lib/tls/libc.so.6
  • #6 ??
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 es_menu_hook_get_type
  • #12 es_menu_hook_get_type
  • #13 <signal handler called>
  • #14 malloc_usable_size
    from /lib/tls/libc.so.6
  • #15 free
    from /lib/tls/libc.so.6
  • #16 g_free
    from /usr/lib/libglib-2.0.so.0
  • #17 ORBit_free_T
    from /usr/lib/libORBit-2.so.0
  • #18 ORBit_free
    from /usr/lib/libORBit-2.so.0
  • #19 ORBit_small_invoke_adaptor
    from /usr/lib/libORBit-2.so.0
  • #20 ORBit_POAObject_post_invoke
    from /usr/lib/libORBit-2.so.0
  • #21 ORBit_POAObject_post_invoke
    from /usr/lib/libORBit-2.so.0
  • #22 giop_thread_queue_process
    from /usr/lib/libORBit-2.so.0
  • #23 giop_thread_queue_process
    from /usr/lib/libORBit-2.so.0
  • #24 g_thread_pool_free
    from /usr/lib/libglib-2.0.so.0
  • #25 g_static_private_free
    from /usr/lib/libglib-2.0.so.0
  • #26 start_thread
    from /lib/tls/libpthread.so.0
  • #27 clone
    from /lib/tls/libc.so.6




Other information:
Comment 1 Brent Smith (smitten) 2005-09-12 02:27:50 UTC
*** Bug 315676 has been marked as a duplicate of this bug. ***
Comment 2 Brent Smith (smitten) 2005-09-12 04:36:23 UTC
*** Bug 315687 has been marked as a duplicate of this bug. ***
Comment 3 Chenthill P 2005-10-24 08:48:56 UTC
This 
Comment 4 Chakravarthi 2005-10-27 11:02:29 UTC
I see that some of the functions that are called in the trace (that lead up to 
the  crash ) can only be called from a call back function when there is a 
backend error. 

Can the reporter give information as to what backend he uses ?
for example (Personal, Exchange, Groupwise, http etc ..)

I also observed that this doesnot happen in evo-2.4 
(I created twenty appointments on a day for this purpose and tried 
multiple times)
Can the reporter please see if this occurs if he uses evo 2.4 ?

(The data is always stored in home directory's .evolution folder and
the configuration information is in .gconf/apps/evolution folder ...
WITHOUT changing eny of these ... please see if this occurs if evo 2.4 
is used... )

And if if does occur please connect gdb to evolution (or by using bug buddy)
generate another trace and attach it here ?

The rpms for evo 2.4 are available at :
ftp://ftp.ximian.com/pub/evolution-snapshot/suse-93-i586/

Please get back to us as soon as possible. Thanx in advance.
Comment 5 Chenthill P 2005-12-20 20:20:03 UTC
Closing this as there is no response from the reporter. Please re-open
providing the necessary information.