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 618761 - crash in Evolution Mail: Editing a reply to a (pl...
crash in Evolution Mail: Editing a reply to a (pl...
Status: RESOLVED DUPLICATE of bug 617805
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.28.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2010-05-16 06:19 UTC by drdent42
Modified: 2010-05-16 20:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.29/2.30



Description drdent42 2010-05-16 06:19:11 UTC
What were you doing when the application crashed?
Editing a reply to a (plain text) message.  However, evolution now crashes spontaneously roughly every 15 minutes on all machines I have Debian testing installed on frequently without even triggering Bug Buddy.  When run from the command-line the crash is typicallly a "Segfault".

Machines I have include two 32-bit desktops and two 64-bit laptops, all four of which are different hardware.  All have NVIDIA graphics but all four are different GPUs and the crashes occur with both the free "nv" Xorg driver and the proprietary drivers from NVIDIA.  If you folks send me another message saying you can't reproduce this then I know you're not even trying.


Distribution: Debian squeeze/sid
Gnome Release: 2.30.0 2010-04-26 (Debian)
BugBuddy Version: 2.30.0

System: Linux 2.6.33.4 #1 SMP PREEMPT Fri May 14 15:46:46 MDT 2010 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10706901
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: gnome
GTK+ Modules: gnomebreakpad, canberra-gtk-module

Memory status: size: 323248128 vsize: 323248128 resident: 63672320 share: 27070464 rss: 63672320 rss_rlim: 18446744073709551615
CPU usage: start_time: 1273989262 rtime: 11717 utime: 5999 stime: 5718 cutime:74 cstime: 16 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xa54fcb70 (LWP 18932)]
[New Thread 0xa5cfdb70 (LWP 18931)]
[New Thread 0xa6cffb70 (LWP 18930)]
[New Thread 0xac6f1b70 (LWP 18929)]
[New Thread 0xaeef6b70 (LWP 18927)]
[New Thread 0xaf6f7b70 (LWP 18926)]
[New Thread 0xb11ffb70 (LWP 18925)]
[New Thread 0xb22feb70 (LWP 18923)]
[New Thread 0xb2affb70 (LWP 18922)]
[New Thread 0xae6f5b70 (LWP 18921)]
[New Thread 0xb09feb70 (LWP 18919)]
[New Thread 0xad6f3b70 (LWP 18918)]
[New Thread 0xadef4b70 (LWP 18917)]
[New Thread 0xa64feb70 (LWP 18641)]
[New Thread 0xb402ab70 (LWP 18613)]
[New Thread 0xafef8b70 (LWP 18550)]
[New Thread 0xabef0b70 (LWP 18549)]
[New Thread 0xaaeeeb70 (LWP 18547)]
[New Thread 0xab6efb70 (LWP 18545)]
[New Thread 0xb4857b70 (LWP 18527)]
[New Thread 0xb5058b70 (LWP 18526)]
0xb7716424 in __kernel_vsyscall ()

Thread 1 (Thread 0xb59bdad0 (LWP 18521))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 __kernel_vsyscall
  • #7 raise
    from /lib/i686/cmov/libc.so.6
  • #8 abort
    from /lib/i686/cmov/libc.so.6
  • #9 g_assertion_message
    from /lib/libglib-2.0.so.0
  • #10 ??
    from /usr/lib/libgnome-keyring.so.0
  • #11 gnome_keyring_find_items_sync
    from /usr/lib/libgnome-keyring.so.0
  • #12 ??
    from /usr/lib/libedataserverui-1.2.so.8
  • #13 ??
    from /usr/lib/libedataserverui-1.2.so.8
  • #14 ??
    from /usr/lib/libedataserverui-1.2.so.8
  • #15 ??
    from /lib/libglib-2.0.so.0
  • #16 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #17 ??
    from /lib/libglib-2.0.so.0
  • #18 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #19 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #20 ??
  • #21 __libc_start_main
    from /lib/i686/cmov/libc.so.6
  • #22 ??
A debugging session is active.

	Inferior 1 [process 18521] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]


---- Critical and fatal warnings logged during execution ----

** evolution **: file gkr-operation.c: line 350 (gkr_operation_request): should not be reached 


----------- .xsession-errors (9 sec old) ---------------------
** (evolution:18521): CRITICAL **: file gkr-operation.c: line 350 (gkr_operation_request): should not be reached
**
ERROR:gkr-operation.c:392:gkr_operation_block: code should not be reached
[fvwm][AddWindow]: new window:
  name:      Bug Buddy
  icon name: (unknown)
  resource:  bug-buddy
  class:     Bug-buddy
[fvwm][__explain_placement]: placed new window 0x4200003 'Bug Buddy':
  initial size 514x231
  desk 0 (current desk)
  current page
  screen: current screen: 0 0 1600x1200 (current screen)
  position 548 499  (used program specified position)
--------------------------------------------------
Comment 1 André Klapper 2010-05-16 20:54:17 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 bug 617805 ***