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 434379 - crash in Evolution: again.. watching videos ...
crash in Evolution: again.. watching videos ...
Status: RESOLVED DUPLICATE of bug 434376
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-04-29 15:43 UTC by gsalas
Modified: 2007-04-29 18:34 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description gsalas 2007-04-29 15:43:03 UTC
What were you doing when the application crashed?
again.. watching videos with gmplayer.


Distribution: Debian lenny/sid
Gnome Release: 2.18.1 2007-04-25 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.17 #2 Wed Aug 16 12:00:43 ECT 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: dlg-etiquette

Memory status: size: 94388224 vsize: 94388224 resident: 34684928 share: 16756736 rss: 34684928 rss_rlim: 4294967295
CPU usage: start_time: 1177861237 rtime: 3205 utime: 2291 stime: 914 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/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1232136512 (LWP 7679)]
[New Thread -1276150896 (LWP 7691)]
[New Thread -1256707184 (LWP 7690)]
[New Thread -1267188848 (LWP 7686)]
[New Thread -1248183408 (LWP 7685)]
[New Thread -1239753840 (LWP 7682)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 2 (Thread -1276150896 (LWP 7691))

  • #0 __kernel_vsyscall
  • #1 __lll_mutex_lock_wait
    from /lib/i686/cmov/libpthread.so.0
  • #2 _L_mutex_lock_88
    from /lib/i686/cmov/libpthread.so.0
  • #3 pthread_mutex_lock
    from /lib/i686/cmov/libpthread.so.0
  • #4 ??
  • #5 ??
  • #6 ??
  • #7 ??
  • #8 ??
  • #9 ??
    from /usr/lib/libcamel-provider-1.2.so.10
  • #10 ??
  • #11 ??
  • #12 <signal handler called>
  • #13 camel_index_add_name
    from /usr/lib/libcamel-1.2.so.10
  • #14 camel_folder_summary_info_new_from_parser
    from /usr/lib/libcamel-provider-1.2.so.10
  • #15 camel_folder_summary_add_from_parser
    from /usr/lib/libcamel-provider-1.2.so.10
  • #16 ??
    from /usr/lib/evolution-data-server-1.2/camel-providers-10/libcamellocal.so
  • #17 ??
  • #18 ??
  • #19 ??


----------- .xsession-errors (64 sec old) ---------------------
(evolution-2.10:7679): camel-WARNING **: Could not find key entry for word 'e0000000': Invalid or incomplete multibyte or wide character
(evolution-2.10:7679): camel-WARNING **: Could not find key entry for word 'e0000000': Invalid or incomplete multibyte or wide character
(evolution-2.10:7679): camel-WARNING **: Could not find key entry for word 'e0000000': Invalid or incomplete multibyte or wide character
(evolution-2.10:7679): camel-WARNING **: Could not find key entry for word 'e0000000': Invalid or incomplete multibyte or wide character
(evolution-2.10:7679): camel-WARNING **: Could not find key entry for word 'e0000000': Invalid or incomplete multibyte or wide character
--------------------------------------------------
Comment 1 Jonathon Jongsma 2007-04-29 18:34:34 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 434376 ***