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 572194 - crash in Evolution Mail and Calendar: Started a gnome session
crash in Evolution Mail and Calendar: Started a gnome session
Status: RESOLVED DUPLICATE of bug 404626
Product: evolution
Classification: Applications
Component: BugBuddyBugs
unspecified
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-02-17 19:01 UTC by Pascal Terjan
Modified: 2009-02-18 05:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26



Description Pascal Terjan 2009-02-17 19:01:40 UTC
Version: 2.26.x

What were you doing when the application crashed?
Started a gnome session


Distribution: Mandriva Linux release 2009.1 (Cooker) for i586
Gnome Release: 2.25.91 2009-02-17 (Mandriva)
BugBuddy Version: 2.25.91

System: Linux 2.6.29-desktop-0.rc5.1mnb #1 SMP Mon Feb 16 17:18:32 EST 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10599902
Selinux: No
Accessibility: Disabled
GTK+ Theme: Simple Compact
Icon Theme: Tango-Blue-Materia
GTK+ Modules: canberra-gtk-module, gnomebreakpad

Memory status: size: 151146496 vsize: 151146496 resident: 11325440 share: 9154560 rss: 11325440 rss_rlim: 18446744073709551615
CPU usage: start_time: 1234897185 rtime: 13 utime: 10 stime: 3 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/lib/evolution/2.26/evolution-alarm-notify'

[Thread debugging using libthread_db enabled]
[New Thread 0xb64d86e0 (LWP 12777)]
[New Thread 0xb1129b90 (LWP 12871)]
[New Thread 0xb192ab90 (LWP 12866)]
[New Thread 0xb0928b90 (LWP 12864)]
[New Thread 0xb0127b90 (LWP 12855)]
[New Thread 0xb212bb90 (LWP 12830)]
[New Thread 0xb292cb90 (LWP 12828)]
[New Thread 0xb312db90 (LWP 12826)]
[New Thread 0xb392eb90 (LWP 12824)]
[New Thread 0xb412fb90 (LWP 12822)]
[New Thread 0xb4930b90 (LWP 12820)]
[New Thread 0xb5131b90 (LWP 12818)]
[New Thread 0xb5932b90 (LWP 12816)]
[New Thread 0xb6174b90 (LWP 12791)]
0xffffe424 in __kernel_vsyscall ()

Thread 1 (Thread 0xb64d86e0 (LWP 12777))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/libpthread.so.0
  • #2 IA__g_spawn_sync
    at gspawn.c line 382
  • #3 IA__g_spawn_command_line_sync
    at gspawn.c line 694
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 <signal handler called>
  • #7 ORBit_small_get_servant
    at orbit-small.c line 1252
  • #8 ORBit_small_get_connection_status
    at orbit-small.c line 1294
  • #9 connection_listen_cb
    at e-component-listener.c line 48
  • #10 link_connection_emit_broken
    at linc-connection.c line 146
  • #11 link_connection_broken_idle
    at linc-connection.c line 183
  • #12 g_idle_dispatch
    at gmain.c line 3922
  • #13 IA__g_main_context_dispatch
    at gmain.c line 1814
  • #14 g_main_context_iterate
    at gmain.c line 2448
  • #15 IA__g_main_loop_run
    at gmain.c line 2656
  • #16 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #17 main
    at notify-main.c line 165
The program is running.  Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal]


----------- .xsession-errors (19 sec old) ---------------------
(gnome-panel:12561): libglade-WARNING **: Unexpected element <requires-version> inside <glade-interface>.
*** Unable to locate valid config! Falling back to auto-detection...
*** Unable to locate valid config! Falling back to auto-detection...
*** Unable to locate valid config! Falling back to auto-detection...
*** Unable to locate valid config! Falling back to auto-detection...
*** Unable to locate PAC! Falling back to direct...
*** Unable to locate PAC! Falling back to direct...
*** Unable to locate PAC! Falling back to direct...
*** Unable to locate PAC! Falling back to direct...
Deadlock potential - avoiding evil bug!
Deadlock potential - avoiding evil bug!
(evolution-alarm-notify:12777): libecal-WARNING **: e-cal.c:4948: Unable to contact backend
(evolution-alarm-notify:12777): evolution-alarm-notify-WARNING **: alarm-queue.c:556: Could not get query for client
--------------------------------------------------
Comment 1 Akhil Laddha 2009-02-18 05:51:37 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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