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 554747 - crash in Evolution Mail and Calendar: The application evolutio...
crash in Evolution Mail and Calendar: The application evolutio...
Status: RESOLVED DUPLICATE of bug 541872
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-10-02 17:28 UTC by ag3945
Modified: 2008-10-03 05:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description ag3945 2008-10-02 17:28:13 UTC
What were you doing when the application crashed?
The application evolution did not crashed. I have juste closed it,  but bug buddy apear every time i close evolution, saying that evolution application does crashed.
		


Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-1-openvz-amd64 #1 SMP Wed Sep 24 14:59:35 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Nuvola
Icon Theme: Nuvola

Memory status: size: 580358144 vsize: 580358144 resident: 69910528 share: 32018432 rss: 69910528 rss_rlim: 18446744073709551615
CPU usage: start_time: 1222959732 rtime: 674 utime: 607 stime: 67 cutime:3 cstime: 10 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 0x7fcecb94c700 (LWP 1591)]
(no debugging symbols found)
0x00007fcec72345ff in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0x7fcecb94c700 (LWP 1591))

  • #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 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/xulrunner-1.9/libxul.so
  • #6 <signal handler called>
  • #7 ??
  • #8 ??
    from /usr/lib/xulrunner-1.9/libxul.so
  • #9 ??
    from /usr/lib/xulrunner-1.9/libxul.so
  • #10 ??
    from /usr/lib/xulrunner-1.9/libxul.so
  • #11 ??
    from /usr/lib/xulrunner-1.9/libxul.so
  • #12 ??
    from /usr/lib/xulrunner-1.9/libxul.so
  • #13 ??
    from /usr/lib/xulrunner-1.9/libxul.so
  • #14 XRE_TermEmbedding
    from /usr/lib/xulrunner-1.9/libxul.so
  • #15 ??
    from /usr/lib/xulrunner-1.9/libxul.so
  • #16 gecko_shutdown
    from /usr/lib/evolution/2.22/plugins/liborg-gnome-evolution-rss.so
  • #17 exit
    from /lib/libc.so.6
  • #18 __libc_start_main
    from /lib/libc.so.6
  • #19 ??
  • #20 ??
  • #21 ??
  • #22 ??
  • #23 ??
  • #24 ??
  • #0 waitpid
    from /lib/libpthread.so.0


----------- .xsession-errors ---------------------
  (org.freedesktop.Hal.NoSuchDevice) No device with id /org/freedesktop/Hal/devices/net_80_00_60_0f_e8_00
** (nm-applet:32678): WARNING **: <WARN>  nma_dbus_device_get_driver_cb(): dbus returned an error.
  (org.freedesktop.NetworkManager.DeviceNotFound) The requested network device does not exist.
ERROR:dbus.connection:Exception in handler for D-Bus signal:
Traceback (most recent call last):
  File "/var/lib/python-support/python2.5/dbus/connection.py", line 214, in maybe_handle_message
    self._handler(*args, **kwargs)
TypeError: evolution_new_mail_callback() takes at most 2 arguments (3 given)
RSS Plugin enabled (evolution 2.22, evolution-rss 0.1.0)
RSS: cleaning all remaining sessions ...done
--------------------------------------------------
Comment 1 Akhil Laddha 2008-10-03 05:02:40 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 541872 ***