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 546361 - crash in Evolution Mail and Calendar: wollte einem Kontakt ein...
crash in Evolution Mail and Calendar: wollte einem Kontakt ein...
Status: RESOLVED DUPLICATE of bug 473924
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-08-05 04:33 UTC by tweety
Modified: 2008-08-05 05:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description tweety 2008-08-05 04:33:22 UTC
What were you doing when the application crashed?
wollte einem Kontakt eine nachricht schicken		


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

System: Linux 2.6.25-2-686 #1 SMP Fri Jul 18 17:46:56 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: gnome

Memory status: size: 40284160 vsize: 40284160 resident: 10870784 share: 8953856 rss: 10870784 rss_rlim: 4294967295
CPU usage: start_time: 1217910417 rtime: 6 utime: 6 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/lib/bug-buddy/evolution-exchange-storage'

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb651d720 (LWP 8107)]
[New Thread 0xb61e9b90 (LWP 8169)]
[New Thread 0xb622ab90 (LWP 8108)]
(no debugging symbols found)
0xb7f4b424 in __kernel_vsyscall ()

Thread 2 (Thread 0xb61e9b90 (LWP 8169))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 e2k_restriction_unref
    from /usr/lib/libexchange-storage-1.2.so.3
  • #7 ??
  • #8 ??


----------- .xsession-errors (507 sec old) ---------------------
** Message: GetValue variable 1 (1)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
--------------------------------------------------
Comment 1 Kandepu Prasad 2008-08-05 05:04:33 UTC
Google Translation: German » English

wanted a contact to send a message

Thanks for taking the time to report this bug.
Unfortunately, the stack trace is missing some elements that will help a lot to
solve the problem, so it will be hard for the developers to fix that crash.

Could you please help fixing this by installing some debugging packages [1],
start the application as normal, and try to reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the 'Details', now
containing way more information. Please copy that stacktrace and paste it as a
comment here. Thanks in advance!

[1] Please install debug packages for evolution, evolution-data-server,
gtkhtml, gtk, glib, glibc, orbit2, gnome-vfs, pango, libgnome and libgnomeui 
(as far as those packages are provided by your distribution).

More details can be found here: http://live.gnome.org/GettingTraces
Comment 2 Kandepu Prasad 2008-08-05 05:16:19 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 473924 ***