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 435124 - crash in Evolution: trying to startup evolut...
crash in Evolution: trying to startup evolut...
Status: RESOLVED DUPLICATE of bug 371529
Product: evolution
Classification: Applications
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
: 435190 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-05-02 09:05 UTC by renatogallo
Modified: 2007-06-11 09:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description renatogallo 2007-05-02 09:05:56 UTC 
Version: 2.12.x

What were you doing when the application crashed?
trying to startup evolution


Distribution: Slackware Slackware 11.1.0
Gnome Release: 2.18.1 2007-04-30 (GARNOME)
BugBuddy Version: 2.18.1

System: Linux 2.6.21-rc7 #2 SMP Wed Apr 18 17:46:42 CEST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10299905
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 118095872 vsize: 118095872 resident: 26521600 share: 16863232 rss: 26521600 rss_rlim: 4294967295
CPU usage: start_time: 1178096651 rtime: 153 utime: 135 stime: 18 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1233938752 (LWP 6788)]
[New Thread -1319109744 (LWP 6818)]
[New Thread -1310721136 (LWP 6817)]
[New Thread -1300767856 (LWP 6807)]
[New Thread -1289749616 (LWP 6800)]
[New Thread -1264583792 (LWP 6799)]
[New Thread -1281361008 (LWP 6798)]
[New Thread -1272972400 (LWP 6795)]
[New Thread -1254892656 (LWP 6793)]
0xb6ac3ad1 in ?? () from /lib/libpthread.so.0

+ Trace 131846

Thread 4 (Thread -1300767856 (LWP 6807))

  • #0 __lll_mutex_lock_wait
    from /lib/libpthread.so.0
  • #1 _L_mutex_lock_88
    from /lib/libpthread.so.0
  • #2 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #3 <signal handler called>
  • #4 camel_index_add_name
    at camel-index.c line 183
  • #5 camel_folder_summary_info_new_from_parser
    at camel-folder-summary.c line 1026
  • #6 camel_folder_summary_add_from_parser
    at camel-folder-summary.c line 931
  • #7 summary_update
    at camel-mbox-summary.c line 485
  • #8 mbox_summary_check
    at camel-mbox-summary.c line 572
  • #9 camel_local_summary_check
    at camel-local-summary.c line 268
  • #10 local_refresh_info
    at camel-local-folder.c line 476
  • #11 camel_folder_refresh_info
    at camel-folder.c line 298
  • #12 refresh_folder_refresh
    at mail-ops.c line 1585
  • #13 mail_msg_received
    at mail-mt.c line 582
  • #14 thread_dispatch
    at e-msgport.c line 1005
  • #15 start_thread
    from /lib/libpthread.so.0
  • #16 clone
    from /lib/libc.so.6 


----------- .xsession-errors ---------------------
kbluetoothd: NeighbourMonitor: reset credits:00:19:63:02:8D:13 3
kbluetoothd: NeighbourMonitor::processQueue
bubbles: warning: blocked event processing for 3446.5 secs!
bubbles: warning: only 0% idle over the last 3451 secs (at 1.2 FPS)
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  19
  Minor opcode:  0
  Resource id:  0x3800160
CalDAV Eplugin starting up ...
** (evolution-2.12:6788): DEBUG: mailto URL command: evolution %s
** (evolution-2.12:6788): DEBUG: mailto URL program: evolution
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
Cannot access memory at address 0xb
Cannot access memory at address 0xb
--------------------------------------------------
Comment 1 palfrey 2007-05-02 11:28:21 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.
Can you get us a stack trace with debugging symbols? Please see
http://live.gnome.org/GettingTraces for more information on how to do so.
Thanks in advance!
Comment 2 palfrey 2007-05-15 09:20:14 UTC 
*** Bug 435190 has been marked as a duplicate of this bug. ***
Comment 3 André Klapper 2007-06-11 09:26:58 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 371529 ***