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 486423 - crash in Evolution Mail: Start system
crash in Evolution Mail: Start system
Status: RESOLVED DUPLICATE of bug 470835
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-10-13 21:23 UTC by mail
Modified: 2007-12-06 04:57 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description mail 2007-10-13 21:23:15 UTC 
What were you doing when the application crashed?
Start system


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

System: Linux 2.6.23.0.1 #1 SMP PREEMPT Fri Oct 12 13:42:17 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 75587584 vsize: 75587584 resident: 14168064 share: 6205440 rss: 14168064 rss_rlim: 4294967295
CPU usage: start_time: 1192310409 rtime: 38 utime: 33 stime: 5 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/lib/bug-buddy/evolution-data-server-1.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 0xb7356b10 (LWP 4748)]
[New Thread 0xb586fb90 (LWP 4906)]
[New Thread 0xb406cb90 (LWP 4767)]
[New Thread 0xb70b3b90 (LWP 4749)]
(no debugging symbols found)
0xb7fca410 in __kernel_vsyscall ()

+ Trace 170034

Thread 1 (Thread 0xb7356b10 (LWP 4748))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libc.so.6
  • #2 do_system
    from /lib/i686/cmov/libc.so.6
  • #3 system
    from /lib/i686/cmov/libc.so.6
  • #4 system
    from /lib/i686/cmov/libpthread.so.0
  • #5 ??
  • #6 ??
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
    from /usr/lib/libgobject-2.0.so.0
  • #11 ??
  • #12 ??
  • #13 <signal handler called>
  • #14 g_type_check_instance_cast
    from /usr/lib/libgobject-2.0.so.0
  • #15 ??
    from /usr/lib/libORBit-2.so.0
  • #16 ??
  • #17 ??
  • #18 ??
  • #19 e_cal_util_generate_alarms_for_comp
    from /usr/lib/libecal-1.2.so.7
  • #20 ORBit_object_get_connection
    from /usr/lib/libORBit-2.so.0
  • #21 ORBit_small_invoke_stub
    from /usr/lib/libORBit-2.so.0
  • #22 ORBit_small_invoke_stub_n
    from /usr/lib/libORBit-2.so.0
  • #23 ORBit_c_stub_invoke
    from /usr/lib/libORBit-2.so.0
  • #24 GNOME_Evolution_Calendar_CalViewListener_notifyQueryDone
    from /usr/lib/libedata-cal-1.2.so.6
  • #25 e_data_cal_view_notify_done
    from /usr/lib/libedata-cal-1.2.so.6
  • #26 ??
    from /usr/lib/evolution-data-server-1.2/extensions/libecalbackendfile.so
  • #27 ??
  • #28 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
intVerToStrVer(pad.cpp:96)	 --- intVerToStrVer
intVerToStrVer(pad.cpp:96)	 --- intVerToStrVer
intVerToStrVer(pad.cpp:96)	 --- intVerToStrVer
intVerToStrVer(pad.cpp:96)	 --- intVerToStrVer
setParam(pad.cpp:303)	 --- setParam
setParam(pad.cpp:304)	 --- NOT YET THREAD SAFE!
intVerToStrVer(pad.cpp:96)	 --- intVerToStrVer
intVerToStrVer(pad.cpp:96)	 --- intVerToStrVer
intVerToStrVer(pad.cpp:96)	 --- intVerToStrVer
intVerToStrVer(pad.cpp:96)	 --- intVerToStrVer
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
(evolution:4638): camel-groupwise-provider-WARNING **: Could not connect..failure connecting
--------------------------------------------------
Comment 1 Akhil Laddha 2007-12-06 04:57:15 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 470835 ***