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 441588 - crash in Evolution Mail: I
crash in Evolution Mail: I
Status: RESOLVED DUPLICATE of bug 434552
Product: evolution
Classification: Applications
Component: general
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-05-27 13:32 UTC by mojaves
Modified: 2007-05-27 14:31 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description mojaves 2007-05-27 13:32:20 UTC
What were you doing when the application crashed?
I've just closed the main evolution window


Distribution: Debian 4.0 (sid)
Gnome Release: 2.18.1 2007-04-25 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.20.10-k8 #1 PREEMPT Sun Apr 29 10:37:19 CEST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 415744000 vsize: 415744000 resident: 57888768 share: 18796544 rss: 57888768 rss_rlim: 18446744073709551615
CPU usage: start_time: 1180271235 rtime: 1605 utime: 1418 stime: 187 cutime:1 cstime: 2 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 47014047778224 (LWP 3347)]
[New Thread 1157933376 (LWP 3390)]
[New Thread 1157667136 (LWP 3389)]
[New Thread 1140881728 (LWP 3387)]
[New Thread 1115703616 (LWP 3384)]
[New Thread 1107310912 (LWP 3383)]
[New Thread 1098918208 (LWP 3361)]
[New Thread 1090525504 (LWP 3360)]
(no debugging symbols found)
0x00002ac248cd4c9f in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 47014047778224 (LWP 3347))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 ??
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 strcmp
    from /lib/libc.so.6
  • #4 e_shell_window_set_title
  • #5 ??
  • #6 GNOME_Evolution_ShellView_setTitle
    from /usr/lib/evolution/2.10/libeshell.so.0
  • #7 e_component_view_set_title
    from /usr/lib/evolution/2.10/libeshell.so.0
  • #8 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #9 ??
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #11 ??
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #13 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #14 main
  • #0 waitpid
    from /lib/libpthread.so.0


----------- .xsession-errors (66019004 sec old) ---------------------
Gnome-Message: gnome_execute_async_with_env_fds: returning -1
Gnome-Message: gnome_execute_async_with_env_fds: returning -1
X connection to :20.0 broken (explicit kill or server shutdown).
Window manager warning: Lost connection to the display ':20.0';
most likely the X server was shut down or you killed/destroyed
the window manager.
The application 'nautilus' lost its connection to the display :20.0;
most likely the X server was shut down or you killed/destroyed
the application.
The application 'gnome-volume-manager' lost its connection to the display :20.0;
most likely the X server was shut down or you killed/destroyed
the application.
The application 'gnome-panel' lost its connection to the display :20.0;
most likely the X server was shut down or you killed/destroyed
the application.
--------------------------------------------------
Comment 1 palfrey 2007-05-27 14:31:22 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 434552 ***