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 404871 - crash in Evolution: Deleted a mail - then sc...
crash in Evolution: Deleted a mail - then sc...
Status: RESOLVED DUPLICATE of bug 239441
Product: evolution
Classification: Applications
Component: general
2.8.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
: 404873 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-02-06 07:05 UTC by V Sridhar
Modified: 2007-10-22 22:56 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description V Sridhar 2007-02-06 07:05:47 UTC 
What were you doing when the application crashed?
Deleted a mail - then scrolled up. Using GARNOME build 2.16.3


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.3 2007-02-05 (GARNOME)
BugBuddy Version: 2.16.1

System: Linux 2.6.19-1.2895.fc6 #1 SMP Wed Jan 10 18:32:37 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled

Memory status: size: 199090176 vsize: 0 resident: 199090176 share: 0 rss: 42164224 rss_rlim: 0
CPU usage: start_time: 1170745129 rtime: 0 utime: 657 stime: 0 cutime:601 cstime: 0 timeout: 56 it_real_value: 0 frequency: 0

Backtrace was generated from '/home/vsridhars/apps/garnome/bin/evolution-2.8'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208333920 (LWP 6419)]
[New Thread -1318327408 (LWP 6499)]
[New Thread -1299190896 (LWP 6453)]
[New Thread -1303381104 (LWP 6450)]
[New Thread -1288701040 (LWP 6449)]
[New Thread -1276249200 (LWP 6447)]
[New Thread -1265759344 (LWP 6446)]
[New Thread -1255269488 (LWP 6443)]
[New Thread -1243350128 (LWP 6441)]
[New Thread -1232860272 (LWP 6440)]
[New Thread -1221977200 (LWP 6439)]
[New Thread -1211470960 (LWP 6437)]
0x00d03402 in __kernel_vsyscall ()

+ Trace 108374

Thread 1 (Thread -1208333920 (LWP 6419))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 libgnomeui_segv_handle
    from /home/vsridhars/apps/garnome/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 resort_node
    from /home/vsridhars/apps/garnome/lib/evolution/2.8/libetable.so.0
  • #5 etta_sort_info_changed
    from /home/vsridhars/apps/garnome/lib/evolution/2.8/libetable.so.0
  • #6 resort_model
    from /home/vsridhars/apps/garnome/lib/evolution/2.8/libetable.so.0
  • #7 g_idle_dispatch
    from /home/vsridhars/apps/garnome/lib/libglib-2.0.so.0
  • #8 g_main_context_dispatch
    from /home/vsridhars/apps/garnome/lib/libglib-2.0.so.0
  • #9 g_main_context_iterate
    from /home/vsridhars/apps/garnome/lib/libglib-2.0.so.0
  • #10 g_main_loop_run
    from /home/vsridhars/apps/garnome/lib/libglib-2.0.so.0
  • #11 bonobo_main
    from /home/vsridhars/apps/garnome/lib/libbonobo-2.so.0
  • #12 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors (15609 sec old) ---------------------
** (ssindex:3580): WARNING **: Unable to load key '/apps/gnumeric/core/sort/default/retain-formats'
** (ssindex:3580): WARNING **: Using default value 'true'
** (ssindex:3580): WARNING **: Unable to load key '/apps/gnumeric/core/sort/default/ascending'
** (ssindex:3580): WARNING **: Using default value 'true'
** (ssindex:3580): WARNING **: Unable to load key '/apps/gnumeric/core/sort/dialog/max-initial-clauses'
** (ssindex:3580): WARNING **: Using default value '10'
** (ssindex:3580): WARNING **: Unable to load key '/apps/gnumeric/dialogs/rs/unfocused'
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 palfrey 2007-02-06 17:45:16 UTC 
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 palfrey 2007-02-06 17:45:21 UTC 
*** Bug 404873 has been marked as a duplicate of this bug. ***
Comment 3 Diego Escalante Urrelo (not reading bugmail) 2007-06-17 06:47:38 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!
Comment 4 Tobias Mueller 2007-10-22 22:56:19 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 239441 ***