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 463580 - crash in Evolution: after start evolution st...
crash in Evolution: after start evolution st...
Status: RESOLVED DUPLICATE of bug 339602
Product: evolution
Classification: Applications
Component: general
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-08-05 05:55 UTC by jin2478
Modified: 2007-08-17 08:39 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description jin2478 2007-08-05 05:55:24 UTC
What were you doing when the application crashed?
after start evolution stuck in 'storing folder' and finally crashed



Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.21-2-powerpc #1 Tue Jul 10 19:09:48 CEST 2007 ppc
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 161132544 vsize: 161132544 resident: 80662528 share: 21504000 rss: 80662528 rss_rlim: 4294967295
CPU usage: start_time: 1186292393 rtime: 41710 utime: 36658 stime: 5052 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 805592512 (LWP 21990)]
[New Thread 861881552 (LWP 22104)]
[New Thread 859981008 (LWP 22009)]
[New Thread 851592400 (LWP 22008)]
[New Thread 842806480 (LWP 22007)]
[New Thread 823649488 (LWP 22003)]
[New Thread 832038096 (LWP 22002)]
[New Thread 815260880 (LWP 21999)]
(no debugging symbols found)
0x0f1ee5a4 in ?? () from /lib/libpthread.so.0

Thread 3 (Thread 859981008 (LWP 22009))

  • #0 __lll_lock_wait
    from /lib/libpthread.so.0
  • #1 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #2 ??
  • #3 <signal handler called>
  • #4 camel_index_add_name
    from /usr/lib/libcamel-1.2.so.10
  • #5 camel_folder_summary_info_new_from_parser
    from /usr/lib/libcamel-provider-1.2.so.10
  • #6 camel_folder_summary_add_from_parser
    from /usr/lib/libcamel-provider-1.2.so.10
  • #7 ??
    from /usr/lib/evolution-data-server-1.2/camel-providers-10/libcamellocal.so
  • #8 ??
    from /usr/lib/evolution-data-server-1.2/camel-providers-10/libcamellocal.so
  • #9 camel_local_summary_check
    from /usr/lib/evolution-data-server-1.2/camel-providers-10/libcamellocal.so
  • #10 ??
    from /usr/lib/evolution-data-server-1.2/camel-providers-10/libcamellocal.so
  • #11 camel_folder_refresh_info
    from /usr/lib/libcamel-provider-1.2.so.10
  • #12 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #13 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #14 ??
    from /usr/lib/libedataserver-1.2.so.9
  • #15 start_thread
    from /lib/libpthread.so.0
  • #16 clone
    from /lib/libc.so.6


----------- .xsession-errors (4971818 sec old) ---------------------
/etc/gdm/PreSession/Default: Registering your session with wtmp and utmp
/etc/gdm/PreSession/Default: running: /usr/bin/sessreg -a -w /var/log/wtmp -u /var/run/utmp -x "/var/lib/gdm/:0.Xservers" -h "" -l ":0" "zhaojin"
/etc/gdm/Xsession: Beginning session setup...
SESSION_MANAGER=local/lager:/tmp/.ICE-unix/3847
Gnome-Message: gnome_execute_async_with_env_fds: returning -1
** Message: Not starting remote desktop server
Window manager warning: Failed to read saved session file /home/zhaojin/.metacity/sessions/1104908500-4468-1284404231.ms: Failed to open file '/home/zhaojin/.metacity/sessions/1104908500-4468-12844042
The application 'x-session-manager' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.
--------------------------------------------------
Comment 1 André Klapper 2007-08-17 08:39:29 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 339602 ***