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 452643 - crash in Evolution:
crash in Evolution:
Status: RESOLVED DUPLICATE of bug 334966
Product: evolution
Classification: Applications
Component: general
2.8.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-06-30 20:46 UTC by pat
Modified: 2007-06-30 22:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description pat 2007-06-30 20:46:56 UTC 
What were you doing when the application crashed?



Distribution: openSUSE 10.2 (X86-64)
Gnome Release: 2.16.3 2007-04-12 (SUSE)
BugBuddy Version: 2.16.1

System: Linux 2.6.18.8-0.3-default #1 SMP Tue Apr 17 08:42:35 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70199902
Selinux: No
Accessibility: Disabled

Memory status: size: 914448384 vsize: 914448384 resident: 24694784 share: 25419776 rss: 50114560 rss_rlim: -1153693696
CPU usage: start_time: 1183228082 rtime: 924 utime: 818 stime: 106 cutime:20 cstime: 8 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/gnome/bin/evolution-2.8'

Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47718218546336 (LWP 4465)]
[New Thread 1115703616 (LWP 4761)]
[New Thread 1124096320 (LWP 4738)]
[New Thread 1140881728 (LWP 4530)]
[New Thread 1132489024 (LWP 4525)]
[New Thread 1141147968 (LWP 4486)]
[New Thread 1107310912 (LWP 4479)]
[New Thread 1098918208 (LWP 4478)]
[New Thread 1090525504 (LWP 4477)]
[New Thread 1082132800 (LWP 4476)]
0x00002b6641019c5f in waitpid () from /lib64/libpthread.so.0

+ Trace 144923

Thread 1 (Thread 47718218546336 (LWP 4465))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /opt/gnome/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 strcmp
    from /lib64/libc.so.6
  • #4 e_shell_window_set_title
  • #5 impl_ShellView_setTitle
  • #6 GNOME_Evolution_ShellView_setTitle
    from /opt/gnome/lib64/evolution/2.8/libeshell.so.0
  • #7 e_component_view_set_title
    from /opt/gnome/lib64/evolution/2.8/libeshell.so.0
  • #8 view_changed_timeout
    from /opt/gnome/lib64/evolution/2.8/components/libevolution-mail.so
  • #9 g_timeout_dispatch
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #10 g_main_context_dispatch
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #11 g_main_context_iterate
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #12 g_main_loop_run
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #13 bonobo_main
    from /opt/gnome/lib64/libbonobo-2.so.0
  • #14 main
  • #0 waitpid
    from /lib64/libpthread.so.0 


----------- .xsession-errors ---------------------
Find Items 0
get pkelecy pop://pkelecy@mail.insightbb.com/
Find Items 0
get pat@mp-m.com pop://pat%40mp-m.com@mail.mp-m.com/
Find Items 0
get pat@magneticpowermotion.com pop://pat%40magneticpowermotion.com@mail.magneticpowermotion.com/
Find Items 0
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2c0005d (OpenOffice)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2c0005d (OpenOffice)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
** (bug-buddy:5158): WARNING **: Couldn't load icon for Bonobo Component Browser
** (bug-buddy:5158): WARNING **: Couldn't load icon for Open Folder
--------------------------------------------------
Comment 1 Karsten Bräckelmann 2007-06-30 22:20:41 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 334966 ***