GNOME Bugzilla – Bug 451144
clicked "previous week" button on calendar
Last modified: 2009-09-22 03:44:22 UTC
What were you doing when the application crashed? I clicked "previous week" button on calendar. Distribution: Debian lenny/sid Gnome Release: 2.18.2 2007-05-28 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.18-4-amd64 #1 SMP Mon Mar 26 11:36:53 CEST 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Afterhours Icon Theme: Iris Memory status: size: 459214848 vsize: 459214848 resident: 38871040 share: 20054016 rss: 38871040 rss_rlim: 18446744073709551615 CPU usage: start_time: 1182837763 rtime: 351 utime: 325 stime: 26 cutime:494 cstime: 38 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 47517292803504 (LWP 4315)] [New Thread 1098918208 (LWP 5015)] [New Thread 1132755264 (LWP 4337)] [New Thread 1132489024 (LWP 4330)] [New Thread 1124096320 (LWP 4329)] [New Thread 1115703616 (LWP 4326)] [New Thread 1107310912 (LWP 4324)] [New Thread 1090525504 (LWP 4321)] [New Thread 1082132800 (LWP 4318)] 0x00002b377479bc9f in waitpid () from /lib/libpthread.so.0
+ Trace 143766
Thread 1 (Thread 47517292803504 (LWP 4315))
----------- .xsession-errors (695 sec old) --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 No whitepoint found No whitepoint found (gnome-background-properties:4433): background-properties-WARNING **: Unknown Tag: comment (gnome-background-properties:4433): background-properties-WARNING **: Unknown Tag: comment ** Message: drive = 0 ** Message: volume = 0 --------------------------------------------------
*** Bug 477808 has been marked as a duplicate of this bug. ***
Complete trace with Evo debug symbols, thanks for reporting. Confirming report.
*** Bug 487426 has been marked as a duplicate of this bug. ***
Crash in calendar so moving component as 'calendar' with keyword STACKTRACE
*** Bug 468193 has been marked as a duplicate of this bug. ***
*** Bug 480435 has been marked as a duplicate of this bug. ***
*** Bug 480781 has been marked as a duplicate of this bug. ***
*** Bug 492242 has been marked as a duplicate of this bug. ***
I guess this is only the 2.10 (gnome-2-18) version issue, and I think that is fixed in 2.12 and above, because there has been committed some patches fixing reference counting in tasks, memos and I guess in calendar too. (The g_object_ref is called on old event->client, which is not NULL, but is probably freed already, thus it crashed in previous version.) Can some of the reporter test this on actual Evolution (stable 2.12.x), please?
*** Bug 509649 has been marked as a duplicate of this bug. ***
*** Bug 512756 has been marked as a duplicate of this bug. ***
*** Bug 516394 has been marked as a duplicate of this bug. ***
*** Bug 519812 has been marked as a duplicate of this bug. ***
Thanks for taking the time to report this bug; however, closing due to lack of response of the reporter, sorry. if you still see this issue with a current release of evolution (2.22.x or later), please reopen. thanks in advance.
*** Bug 542082 has been marked as a duplicate of this bug. ***
Reopening the bug as per dup in 2.22.x
Chen rewrote this quite heavily in actual trunk (2.23.90) recently. Let's see how it will work in 2.24.
*** Bug 551734 has been marked as a duplicate of this bug. ***
*** Bug 553340 has been marked as a duplicate of this bug. ***
*** Bug 554667 has been marked as a duplicate of this bug. ***
*** Bug 570913 has been marked as a duplicate of this bug. ***
*** Bug 574969 has been marked as a duplicate of this bug. ***
*** Bug 482360 has been marked as a duplicate of this bug. ***
This version is no longer maintained, which means that it will not receive any further security or bug fix updates. The current stable GNOME and Evolution version is 2.26. Can you please check again whether this issue still happens in Evolution 2.24 or 2.26 and update this report by adding a comment and changing the "Version" field? Thanks a lot. Again thank you for reporting this bug and we are sorry it could not be fixed for the version you originally used here. Without feedback this report will be closed as INCOMPLETE in 6 weeks.
Comments from launchpad: >>> Ik werk ondertussen niet meer met Ubuntu of een andere Linux derivaat. <<< and >>> I am afraid that I haven't kept up with this bug however guess that it was solved from my point of view as a user as I no longer have the problem. At the time of my bug report I was unable to print emails from within Evolution now I print without problem. As far as Karmic goes, currently I just don't have the time to establish a new system for testing, I am sorry. <<< Since the reporter of the launchpad bug never responded, I guess from launchpads point of view this bug can savely be closed.
Thanks Martin.