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 532138 - Evolution crashed : clicked on attachment button during memo creation
Evolution crashed : clicked on attachment button during memo creation
Status: RESOLVED DUPLICATE of bug 537555
Product: evolution
Classification: Applications
Component: Calendar
2.22.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-05-08 10:38 UTC by Akhil Laddha
Modified: 2009-08-28 05:37 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Akhil Laddha 2008-05-08 10:38:14 UTC
Evolution 2.22.1

Distribution: openSUSE 11.0 (i586) Beta1
Gnome Release: 2.22.1 2008-04-14 (SUSE)
BugBuddy Version: 2.22.0

System: Linux 2.6.25-rc9-17-pae #1 SMP 2008-04-15 22:54:53 +0200 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Gilouche
Icon Theme: Industrial

Memory status: size: 130199552 vsize: 130199552 resident: 10420224 share: 20983808 rss: 31404032 rss_rlim: 1791457280
CPU usage: start_time: 1210242729 rtime: 346 utime: 314 stime: 32 cutime:2 cstime: 28 timeout: 0 it_real_value: 0 frequency: 100

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

[?1034h[Thread debugging using libthread_db enabled]
[New Thread 0xb643a720 (LWP 10460)]
[New Thread 0xb136bb90 (LWP 10766)]
[New Thread 0xb1d45b90 (LWP 10765)]
[New Thread 0xb2587b90 (LWP 10472)]
0xffffe430 in __kernel_vsyscall ()

Thread 3 (Thread 0xb1d45b90 (LWP 10765))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 IA__g_spawn_sync
    at gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at gspawn.c line 682
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 google_breakpad::ExceptionHandler::InternalWriteMinidump
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #7 google_breakpad::ExceptionHandler::HandleException
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #8 <signal handler called>
  • #9 __kernel_vsyscall
  • #10 *__GI_raise
    at ../nptl/sysdeps/unix/sysv/linux/raise.c line 64
  • #11 *__GI_abort
    at abort.c line 88
  • #12 IA__g_logv
  • #13 IA__g_log
  • #14 g_type_class_ref
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_object_new
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_themed_icon_new_from_names
    from /usr/lib/libgio-2.0.so.0
  • #18 g_content_type_get_icon
    from /usr/lib/libgio-2.0.so.0
  • #19 ??
    from /usr/lib/libgio-2.0.so.0
  • #20 ??
  • #21 ??
    from /usr/lib/libgio-2.0.so.0
  • #22 ??


----------- .xsession-errors (5321 sec old) ---------------------
(gnome-screenshot:32254): GLib-GIO-CRITICAL **: g_themed_icon_constructed: assertion `themed->names != NULL && themed->names[0] != NULL' failed
(gnome-screenshot:32254): GLib-CRITICAL **: g_strv_length: assertion `str_array != NULL' failed
(gnome-screenshot:2242): GLib-GObject-WARNING **: IA__g_object_new_valist: object class `GThemedIcon' has no property named `names'
(gnome-screenshot:2242): GLib-GIO-CRITICAL **: g_themed_icon_constructed: assertion `themed->names != NULL && themed->names[0] != NULL' failed
(gnome-screenshot:2242): GLib-CRITICAL **: g_strv_length: assertion `str_array != NULL' failed
(gedit:8907): GLib-GObject-WARNING **: IA__g_object_new_valist: object class `GThemedIcon' has no property named `names'
(gedit:8907): GLib-GIO-CRITICAL **: g_themed_icon_constructed: assertion `themed->names != NULL && themed->names[0] != NULL' failed
(gedit:8907): GLib-CRITICAL **: g_strv_length: assertion `str_array != NULL' failed
--------------------------------------------------
Comment 1 Milan Crha 2008-09-22 17:33:34 UTC
Could be related to bug #537555 I guess.
Comment 2 Akhil Laddha 2009-08-28 05:37:12 UTC

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