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 531539 - crash in Evolution Mail and Calendar: After setting my IMAP gm...
crash in Evolution Mail and Calendar: After setting my IMAP gm...
Status: RESOLVED DUPLICATE of bug 333224
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.22.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-05-05 12:13 UTC by mateusz.kaduk
Modified: 2008-05-08 13:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description mateusz.kaduk 2008-05-05 12:13:51 UTC 
What were you doing when the application crashed?
After setting my IMAP gmail account I did click on Calendar tag. It apears that some events where downloaded but evolution crashed.


Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-amd64 #1 SMP Fri Apr 18 23:08:22 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: glass-icons

Memory status: size: 515723264 vsize: 515723264 resident: 42221568 share: 23093248 rss: 42221568 rss_rlim: 18446744073709551615
CPU usage: start_time: 1209989446 rtime: 1133 utime: 1046 stime: 87 cutime:6 cstime: 12 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution'

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x2aca1dcabd00 (LWP 15272)]
[New Thread 0x42845950 (LWP 15403)]
[New Thread 0x41001950 (LWP 15334)]
(no debugging symbols found)
0x00002aca13a1cedf in waitpid () from /lib/libpthread.so.0

+ Trace 196931

Thread 1 (Thread 0x2aca1dcabd00 (LWP 15272))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 e_calendar_view_get_tooltips
    from /usr/lib/evolution/2.22/components/libevolution-calendar.so
  • #6 ??
    from /usr/lib/libglib-2.0.so.0
  • #7 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #8 ??
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #10 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #11 ??
  • #12 __libc_start_main
    from /lib/libc.so.6
  • #13 ??
  • #14 ??
  • #15 ??
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors (8 sec old) ---------------------
libecal-Message: e_cal_recur_generate_instances_of_rule(): bogus component, does not have DTSTART.  Skipping...
libecal-Message: e_cal_recur_generate_instances_of_rule(): bogus component, does not have DTSTART.  Skipping...
libecal-Message: e_cal_recur_generate_instances_of_rule(): bogus component, does not have DTSTART.  Skipping...
libecal-Message: e_cal_recur_generate_instances_of_rule(): bogus component, does not have DTSTART.  Skipping...
libecal-Message: e_cal_recur_generate_instances_of_rule(): bogus component, does not have DTSTART.  Skipping...
libecal-Message: e_cal_recur_generate_instances_of_rule(): bogus component, does not have DTSTART.  Skipping...
libecal-Message: e_cal_recur_generate_instances_of_rule(): bogus component, does not have DTSTART.  Skipping...
libecal-Message: e_cal_recur_generate_instances_of_rule(): bogus component, does not have DTSTART.  Skipping...
libecal-Message: e_cal_recur_generate_instances_of_rule(): bogus component, does not have DTSTART.  Skipping...
(evolution:15272): calendar-gui-WARNING **: Couldn't find event window
(evolution:15272): calendar-gui-WARNING **: Couldn't find event window
--------------------------------------------------
Comment 1 Akhil Laddha 2008-05-08 13:58:53 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but
the maintainers need more information to fix the bug. Could you please answer
the questions in the other report in order to help the developers?

*** This bug has been marked as a duplicate of 333224 ***