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 481252 - crash in Tasks: Hämtade mail
crash in Tasks: Hämtade mail
Status: RESOLVED DUPLICATE of bug 434653
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-09-28 11:08 UTC by ricky
Modified: 2007-10-29 06:57 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description ricky 2007-09-28 11:08:01 UTC
Version: 2.10

What were you doing when the application crashed?
Hämtade mail


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 132689920 vsize: 132689920 resident: 49451008 share: 36196352 rss: 49451008 rss_rlim: 4294967295
CPU usage: start_time: 1190977253 rtime: 653 utime: 597 stime: 56 cutime:2 cstime: 8 timeout: 0 it_real_value: 0 frequency: 100

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

(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 -1208703264 (LWP 2874)]
[New Thread -1300575344 (LWP 3879)]
[New Thread -1245590640 (LWP 3878)]
[New Thread -1235096688 (LWP 3485)]
[New Thread -1256727664 (LWP 3479)]
[New Thread -1224103024 (LWP 2914)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208703264 (LWP 2874))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 <signal handler called>
  • #5 ??
    from /lib/libglib-2.0.so.0
  • #6 ??
    from /lib/libglib-2.0.so.0
  • #7 ??
    from /lib/libglib-2.0.so.0
  • #8 g_slice_free1
    from /lib/libglib-2.0.so.0
  • #9 g_slist_free_1
    from /lib/libglib-2.0.so.0
  • #10 g_slist_remove_all
    from /lib/libglib-2.0.so.0
  • #11 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 g_object_unref
    from /lib/libgobject-2.0.so.0
  • #13 gtk_rc_style_unref
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 g_datalist_id_set_data_full
    from /lib/libglib-2.0.so.0
  • #15 g_object_set_qdata_full
    from /lib/libgobject-2.0.so.0
  • #16 gtk_widget_modify_style
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 ??
    from /usr/lib/evolution/2.10/libefilterbar.so.0
  • #19 g_object_set_valist
    from /lib/libgobject-2.0.so.0
  • #20 g_object_set
    from /lib/libgobject-2.0.so.0
  • #21 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #22 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #23 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #24 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #25 ??
    from /lib/libglib-2.0.so.0
  • #26 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #27 ??
    from /lib/libglib-2.0.so.0
  • #28 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #29 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #30 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (318 sec old) ---------------------
A:  44.8 V:  44.8 A-V: -0.009 ct:  0.001 1022/1022 11%  0%  1.4% 1 0            
A:  44.9 V:  44.9 A-V: -0.008 ct:  0.001 1023/1023 11%  0%  1.4% 1 0            
X11 error: BadAlloc (insufficient reso
X11 error: BadAlloc (insufficient resources for operation)
A:  44.9 V:  44.9 A-V: -0.008 ct: -0.000 1024/1024 11%  0%  1.4% 1 0            
X11 error: BadAlloc (insufficient resources for operation)
A:  45.0 V:  45.0 A-V: -0.007 ct: -0.001 1025/1025 11%  0%  1.4% 1 0            
X11 error: BadAlloc (insufficient resources for operation)
A:  45.0 V:  45.0 A-V: -0.006 ct: -0.001 1026/1026 11%  0%  1.4% 1 0            
A:  45.0 V:  45.0 A-V: -0.006 ct: -0.002 1027/1027 11%  0%  1.4% 1 0            
X11 error: BadAlloc (insufficient reso
X11 error: BadAlloc (insufficient resources for operation)
A:  45.1 V:  45.1 A-V: -0.005 ct: -0.002 1028/1028 11%  0%  1.4% 1 0            
X11 error: BadAlloc (insufficient resources for operation)
A:  45.1 V:  45.1 A-V: -0.004 ct: -0.003 1029/1029 11%  0%  1.4% 1 0            
X11 error: BadAlloc (insufficient resources for operation)
A:  45.2 V:  45.2 A-V: -0.004 ct: -0.003 1030/1030 11%  0%  1.4% 1 0            
X11 error: BadAlloc (insufficient resources for operation)
A:  45.2 V:  45.2 A-V: -0.003 ct: -0.004 1031/1031 11%  0%  1.4% 1 0            
X11 error: BadAlloc (insufficient resources for operation)
A:  45.2 V:  45.2 A-V: -0.003 ct: -0.004 1032/1032 11%  0%  1.4% 1 0            
X11 error: BadAlloc (insufficient resources for operation)
A:  45.3 V:  45.3 A-V: -0.003 ct: -0.004 1033/1033 11%  0%  1.4% 1 0            
X11 error: BadAlloc (insufficient resources for operation)
A:  45.3 V:  45.3 A-V: -0.002 ct: -0.004 1034/1034 11%  0%  1.4% 1 0            
X11 error: BadAlloc (insufficient resources for operation)
A:  45.4 V:  45.4 A-V: -0.002 ct: -0.005 1035/1035 11%  0%  1.4% 1 0            
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Akhil Laddha 2007-10-29 06:57:29 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 434653 ***