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 463328 - crash in Evolution: starting evolution
crash in Evolution: starting evolution
Status: RESOLVED DUPLICATE of bug 426496
Product: evolution
Classification: Applications
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-08-04 03:16 UTC by thanate
Modified: 2007-08-11 00:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description thanate 2007-08-04 03:16:05 UTC 
Version: 2.12.x

What were you doing when the application crashed?
starting evolution


Distribution: Debian lenny/sid
Gnome Release: 2.19.6 2007-07-31 (GARNOME)
BugBuddy Version: 2.19.0

System: Linux 2.6.22.1 #1 PREEMPT Tue Jul 10 14:28:46 MST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Enabled
GTK+ Theme: MurrinaEalm
Icon Theme: gnome

Memory status: size: 96493568 vsize: 96493568 resident: 32796672 share: 23003136 rss: 32796672 rss_rlim: 4294967295
CPU usage: start_time: 1186196559 rtime: 189 utime: 176 stime: 13 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/home/boat/garnome/bin/evolution'

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1232536784 (LWP 30151)]
[New Thread -1295090800 (LWP 30162)]
[New Thread -1255978096 (LWP 30161)]
[New Thread -1281610864 (LWP 30160)]
[New Thread -1272824944 (LWP 30159)]
[New Thread -1264395376 (LWP 30156)]
[New Thread -1247585392 (LWP 30154)]
0xb7fce410 in __kernel_vsyscall ()

+ Trace 152696

Thread 1 (Thread -1232536784 (LWP 30151))

  • #0 __kernel_vsyscall
  • #1 ??
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at gspawn.c line 364
  • #3 IA__g_spawn_command_line_sync
    at gspawn.c line 672
  • #4 run_bug_buddy
    at gnome-breakpad.cc line 121
  • #5 check_if_gdb
    at gnome-breakpad.cc line 191
  • #6 google_breakpad::ExceptionHandler::InternalWriteMinidump
    at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 225
  • #7 google_breakpad::ExceptionHandler::HandleException
    at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 196
  • #8 <signal handler called>
  • #9 html_object_get_left_margin
    at htmlobject.c line 1090
  • #10 get_lmargin
    at htmlcluev.c line 98
  • #11 html_cluev_do_layout
    at htmlcluev.c line 155
  • #12 html_object_calc_size
    at htmlobject.c line 1069
  • #13 html_engine_calc_size
    at htmlengine.c line 4971
  • #14 thaw_idle
    at htmlengine.c line 5561
  • #15 g_idle_dispatch
    at gmain.c line 4131
  • #16 IA__g_main_context_dispatch
    at gmain.c line 2061
  • #17 g_main_context_iterate
    at gmain.c line 2694
  • #18 IA__g_main_loop_run
    at gmain.c line 2898
  • #19 bonobo_main
    at bonobo-main.c line 311
  • #20 main
    at main.c line 594
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
(nautilus:29876): Liboobs-WARNING **: There was an unknown error communicating with the backends: The name org.freedesktop.SystemToolsBackends was not provided by any .service files
(nautilus:29876): Liboobs-WARNING **: There was an unknown error communicating with the backends: The name org.freedesktop.SystemToolsBackends was not provided by any .service files
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
CalDAV Eplugin starting up ...
** (evolution:30151): DEBUG: mailto URL command: evolution %s
** (evolution:30151): DEBUG: mailto URL program: evolution
Cannot access memory at address 0x0
Cannot access memory at address 0x0
--------------------------------------------------
Comment 1 Tobias Mueller 2007-08-11 00:10:18 UTC 
Hi!

Thanks for taking the time to report this bug.
I thinkg this particular bug has already been reported and it seems to be fixed as well :)

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