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 494785 - crash in Evolution:
crash in Evolution:
Status: RESOLVED DUPLICATE of bug 426496
Product: evolution
Classification: Applications
Component: general
2.12.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-11-07 22:41 UTC by Mike
Modified: 2007-11-08 17:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Mike 2007-11-07 22:41:02 UTC
What were you doing when the application crashed?



Distribution: Mandriva Linux release 2008.0 (Cooker) for x86_64
Gnome Release: 2.19.5 2007-07-08 (Mandriva)
BugBuddy Version: 2.20.1

System: Linux 2.6.22.9-desktop-1mdv #1 SMP Wed Sep 26 22:36:49 CEST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Enabled
GTK+ Theme: Ia Ora Free
Icon Theme: gnome

Memory status: size: 802054144 vsize: 802054144 resident: 234688512 share: 38125568 rss: 234688512 rss_rlim: 18446744073709551615
CPU usage: start_time: 1194366002 rtime: 66027 utime: 55469 stime: 10558 cutime:347179 cstime: 16446 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47660956701456 (LWP 11210)]
[New Thread 1149540688 (LWP 11345)]
[New Thread 1090525520 (LWP 11343)]
[New Thread 1107310928 (LWP 11232)]
[New Thread 1124096336 (LWP 11231)]
[New Thread 1149274448 (LWP 11227)]
[New Thread 1140881744 (LWP 11226)]
[New Thread 1132489040 (LWP 11225)]
[New Thread 1115703632 (LWP 11222)]
[New Thread 1098918224 (LWP 11220)]
[New Thread 1082132816 (LWP 11218)]
(no debugging symbols found)
0x00002b58e929b8ae in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 47660956701456 (LWP 11210))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 g_cclosure_marshal_VOID__BOOLEAN
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 ??
  • #4 g_cclosure_marshal_VOID__BOOLEAN
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #5 g_cclosure_marshal_VOID__BOOLEAN
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #6 html_object_calc_size
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #7 html_engine_calc_size
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #8 g_cclosure_marshal_VOID__BOOLEAN
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #9 g_main_context_dispatch
    from /usr/lib64/libglib-2.0.so.0
  • #10 g_cclosure_marshal_VOID__BOOLEAN
    from /usr/lib64/libglib-2.0.so.0
  • #11 g_main_loop_run
    from /usr/lib64/libglib-2.0.so.0
  • #12 bonobo_main
    from /usr/lib64/libbonobo-2.so.0
  • #13 g_cclosure_marshal_VOID__BOOLEAN
  • #14 __libc_start_main
    from /lib64/libc.so.6
  • #15 g_cclosure_marshal_VOID__BOOLEAN
  • #16 ??
  • #17 ??
  • #0 waitpid
    from /lib64/libpthread.so.0


----------- .xsession-errors ---------------------
(gnome_segv:18109): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.
(gnome_segv:18109): atk-bridge-WARNING **: IOR not set.
(gnome_segv:18109): atk-bridge-WARNING **: Could not locate registry
(bug-buddy:18110): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.
(bug-buddy:18110): atk-bridge-WARNING **: IOR not set.
(bug-buddy:18110): atk-bridge-WARNING **: Could not locate registry
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  158
  Minor opcode:  6
  Resource id:  0x252
--------------------------------------------------
Comment 1 palfrey 2007-11-08 17:52:35 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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