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 564745 - [Debian] crash in liborg-jylefort-mail-notification.so
[Debian] crash in liborg-jylefort-mail-notification.so
Status: RESOLVED NOTGNOME
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.24.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
: 553895 573979 575587 578216 578525 581270 588380 588451 588931 589087 589134 589220 591771 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-12-16 15:24 UTC by Reid Thompson
Modified: 2009-08-14 11:25 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description Reid Thompson 2008-12-16 15:24:54 UTC 
What were you doing when the application crashed?
Mail Notification 5.4 released May 22, 2008 causes SVN head Evolution to immediately crash


Distribution: Gentoo Base System release 2.0.0
Gnome Release: 2.24.2 2008-12-01 (Gentoo)
BugBuddy Version: 2.24.2

System: Linux 2.6.25-gentoo-r9 #2 SMP PREEMPT Mon Dec 1 08:55:24 EST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: KillBang Wow!
Icon Theme: gnome

Memory status: size: 167505920 vsize: 167505920 resident: 74768384 share: 22446080 rss: 74768384 rss_rlim: 18446744073709551615
CPU usage: start_time: 1229440234 rtime: 3586 utime: 3190 stime: 396 cutime:40 cstime: 14 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/evo/bin/evolution'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb672a6c0 (LWP 11917)]
[New Thread 0xb06c8b90 (LWP 12116)]
[New Thread 0xb3dffb90 (LWP 11944)]
0xffffe424 in __kernel_vsyscall ()

+ Trace 210853

Thread 1 (Thread 0xb672a6c0 (LWP 11917))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 IA__g_spawn_sync
    at ../../../glib/glib/gspawn.c line 382
  • #3 IA__g_spawn_command_line_sync
    at ../../../glib/glib/gspawn.c line 694
  • #4 run_bug_buddy
    at gnome-breakpad.cc line 223
  • #5 bugbuddy_segv_handle
    at gnome-breakpad.cc line 292
  • #6 <signal handler called>
  • #7 camel_message_info_uint32
    at ../../../evolution-data-server/camel/camel-folder-summary.c line 4550
  • #8 mn_evolution_server_get_unseen_messages
    from /opt/evo/lib/evolution/2.26/plugins/liborg-jylefort-mail-notification.so
  • #9 dbus_glib_marshal_mn_evolution_server_BOOLEAN__STRING_POINTER_POINTER
    from /opt/evo/lib/evolution/2.26/plugins/liborg-jylefort-mail-notification.so
  • #10 gobject_message_function
    at dbus-gobject.c line 1276
  • #11 _dbus_object_tree_dispatch_and_unlock
    at dbus-object-tree.c line 856
  • #12 dbus_connection_dispatch
    at dbus-connection.c line 4447
  • #13 message_queue_dispatch
    at dbus-gmain.c line 101
  • #14 IA__g_main_context_dispatch
    at ../../../glib/glib/gmain.c line 1814
  • #15 g_main_context_iterate
    at ../../../glib/glib/gmain.c line 2448
  • #16 IA__g_main_loop_run
    at ../../../glib/glib/gmain.c line 2656
  • #17 bonobo_main
    at bonobo-main.c line 311
  • #18 main
    at ../../../evolution/shell/main.c line 695
  • #0 __kernel_vsyscall 


----------- .xsession-errors (1882 sec old) ---------------------
(awn-applet-activation:9588): GdkPixbuf-CRITICAL **: gdk_pixbuf_new_from_file_at_scale: assertion `filename != NULL' failed
(awn-applet-activation:9588): Gtk-CRITICAL **: gtk_icon_theme_load_icon: assertion `icon_name != NULL' failed
(awn-applet-activation:9588): GdkPixbuf-CRITICAL **: gdk_pixbuf_new_from_file_at_scale: assertion `filename != NULL' failed
(awn-applet-activation:9588): Gtk-CRITICAL **: gtk_icon_theme_load_icon: assertion `icon_name != NULL' failed
(awn-applet-activation:9588): GdkPixbuf-CRITICAL **: gdk_pixbuf_new_from_file_at_scale: assertion `filename != NULL' failed
Launched application : 9636
Error - cannot end transaction. Rolling back...
Error - cannot end transaction. Rolling back...
Error - cannot end transaction. Rolling back...
Error - cannot end transaction. Rolling back...
Error - cannot end transaction. Rolling back...
--------------------------------------------------
Comment 1 Reid Thompson 2008-12-16 16:03:06 UTC 
applied patch to .c file noted in Mail Notification bug tracker 
https://bugs.launchpad.net/mail-notification/+bug/251031

at this link
https://bugs.launchpad.net/mail-notification/+bug/251031
to file src/mn-evolution-server.c
Comment 2 Akhil Laddha 2009-03-04 03:46:20 UTC 
*** Bug 573979 has been marked as a duplicate of this bug. ***
Comment 3 Fabio Durán Verdugo 2009-07-12 20:17:12 UTC 
*** Bug 588380 has been marked as a duplicate of this bug. ***
Comment 4 palfrey 2009-07-13 17:09:13 UTC 
*** Bug 588451 has been marked as a duplicate of this bug. ***
Comment 5 André Klapper 2009-07-18 13:22:20 UTC 
*** Bug 575587 has been marked as a duplicate of this bug. ***
Comment 6 André Klapper 2009-07-18 13:22:26 UTC 
*** Bug 578216 has been marked as a duplicate of this bug. ***
Comment 7 André Klapper 2009-07-18 13:22:32 UTC 
*** Bug 578525 has been marked as a duplicate of this bug. ***
Comment 8 André Klapper 2009-07-18 13:22:42 UTC 
*** Bug 581270 has been marked as a duplicate of this bug. ***
Comment 9 André Klapper 2009-07-18 13:22:53 UTC 
*** Bug 553895 has been marked as a duplicate of this bug. ***
Comment 10 André Klapper 2009-07-18 13:23:51 UTC 
*** Bug 588931 has been marked as a duplicate of this bug. ***
Comment 11 palfrey 2009-07-20 09:52:16 UTC 
*** Bug 589087 has been marked as a duplicate of this bug. ***
Comment 12 Fabio Durán Verdugo 2009-07-20 16:51:15 UTC 
*** Bug 589134 has been marked as a duplicate of this bug. ***
Comment 13 Fabio Durán Verdugo 2009-07-21 16:52:27 UTC 
*** Bug 589220 has been marked as a duplicate of this bug. ***
Comment 14 André Klapper 2009-08-14 11:25:49 UTC 
*** Bug 591771 has been marked as a duplicate of this bug. ***