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 558624 - crash in Evolution Mail and Calendar: looking at /changing fol...
crash in Evolution Mail and Calendar: looking at /changing fol...
Status: RESOLVED DUPLICATE of bug 533743
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.22.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
: 547562 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-10-31 02:19 UTC by kinguin7
Modified: 2008-12-23 17:36 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description kinguin7 2008-10-31 02:19:50 UTC
What were you doing when the application crashed?
looking at /changing folder subscriptions


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

System: Linux 2.6.25-kinguin7forkv4.5 #1 SMP Sun Jul 20 19:32:53 CDT 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 97230848 vsize: 97230848 resident: 32550912 share: 20029440 rss: 32550912 rss_rlim: 4294967295
CPU usage: start_time: 1225418319 rtime: 380 utime: 344 stime: 36 cutime:2 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb66ac6d0 (LWP 10610)]
[New Thread 0xb44ffb90 (LWP 11182)]
[New Thread 0xb5adab90 (LWP 10694)]
0xffffe424 in __kernel_vsyscall ()

Thread 2 (Thread 0xb44ffb90 (LWP 11182))

  • #0 __kernel_vsyscall
  • #1 __lll_lock_wait
    from /lib/i686/cmov/libpthread.so.0
  • #2 _L_lock_89
    from /lib/i686/cmov/libpthread.so.0
  • #3 pthread_mutex_lock
    from /lib/i686/cmov/libpthread.so.0
  • #4 segv_redirect
    at main.c line 528
  • #5 <signal handler called>
  • #6 ??
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 ??
  • #12 ??
  • #13 ??
  • #14 ??
  • #15 ??
  • #16 ??
  • #17 ??
  • #18 ??
  • #19 ??
  • #20 ??
  • #21 ??
  • #22 ??
  • #23 ??
  • #24 ??
  • #25 ??
  • #26 ??
  • #27 ??
  • #28 gnome_help_display
    from /usr/lib/evolution/2.22/plugins/liborg-gnome-exchange-operations.so
  • #29 ??
  • #30 ??
  • #31 ??
  • #32 ??
  • #33 ??
  • #34 ??
  • #35 ??
  • #36 ??
  • #37 ??
    from /usr/lib/libstdc++.so.6
  • #38 ??
  • #39 ??
  • #40 ??
  • #41 ??
  • #42 ??
  • #43 ??
  • #44 ??
  • #45 ??
  • #46 transfer_messages_exec
    at mail-ops.c line 954


----------- .xsession-errors (1218 sec old) ---------------------
[ConvConfHandler] isPreferred contentType: application/pdf
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2e00003 (Evince Doc)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
CalDAV Eplugin starting up ...
evolution-shell-Message: Killing old version of evolution-data-server...
** (evolution:10610): DEBUG: mailto URL command: evolution %s
** (evolution:10610): DEBUG: mailto URL program: evolution
(evolution:10610): gtkhtml-WARNING **: Cannot create spell dictionary instance (iid:OAFIID:GNOME_Spell_Dictionary:0.3)
(evolution:10610): Bonobo-WARNING **: Activation exception 'Failed to activate 'OAFIID:GNOME_Spell_Control:0.3''
CalDAV Eplugin starting up ...
evolution-shell-Message: Killing old version of evolution-data-server...
(evolution:10610): gtkhtml-WARNING **: oo
--------------------------------------------------
Comment 1 Akhil Laddha 2008-10-31 05:34:23 UTC
*** Bug 547562 has been marked as a duplicate of this bug. ***
Comment 2 Kandepu Prasad 2008-10-31 20:38:49 UTC
Thanks for taking the time to report this bug.
Unfortunately, that 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 install some debugging packages [1], start the application as
normal, and 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] debugging packages for evolution, evolution-data-server,
evolution-exchange, gtkhtml, gtk2, glib2, glibc, orbit2, libsoup, gnome-vfs, 
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 3 André Klapper 2008-12-23 17:36:25 UTC
Kandepu: What exactly are you missing in this trace?

Same as bug 533743 comment 3.

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