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 491592 - crash in Evolution Mail: Nothing that I know of.
crash in Evolution Mail: Nothing that I know of.
Status: RESOLVED DUPLICATE of bug 402506
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-10-30 02:36 UTC by majesticfear
Modified: 2007-10-30 11:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description majesticfear 2007-10-30 02:36:37 UTC
What were you doing when the application crashed?
Nothing that I know of.


Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-2-amd64 #1 SMP Thu Aug 30 23:43:59 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy P
Icon Theme: Industrial

Memory status: size: 238075904 vsize: 238075904 resident: 14618624 share: 6254592 rss: 14618624 rss_rlim: 18446744073709551615
CPU usage: start_time: 1193279751 rtime: 36 utime: 28 stime: 8 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/lib/bug-buddy/evolution-data-server-1.10'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0x2b0bba8b1310 (LWP 24958)]
[New Thread 0x42044950 (LWP 24998)]
[New Thread 0x40040950 (LWP 24959)]
0x00002b0bb8278a9f in waitpid () from /lib/libc.so.6

Thread 1 (Thread 0x2b0bba8b1310 (LWP 24958))

  • #0 waitpid
    from /lib/libc.so.6
  • #1 ??
    from /lib/libc.so.6
  • #2 system
    from /lib/libc.so.6
  • #3 gnome_segv_handler
    at server.c line 114
  • #4 <signal handler called>
  • #5 reload_cb
    at e-cal-backend-weather.c line 78
  • #6 g_timeout_dispatch
    at /build/buildd/glib2.0-2.14.1/glib/gmain.c line 3488
  • #7 IA__g_main_context_dispatch
    at /build/buildd/glib2.0-2.14.1/glib/gmain.c line 2061
  • #8 g_main_context_iterate
    at /build/buildd/glib2.0-2.14.1/glib/gmain.c line 2694
  • #9 IA__g_main_loop_run
    at /build/buildd/glib2.0-2.14.1/glib/gmain.c line 2898
  • #10 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #11 main
    at server.c line 393
  • #0 waitpid
    from /lib/libc.so.6


----------- .xsession-errors (3252 sec old) ---------------------
Window manager warning: 0x3e00589 () appears to be one of the offending windows with a timestamp of 2714170016.  Working around...
** (gnome-screensaver-command:24356): WARNING **: Unknown option --throttle
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1200003 (Top Expand)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
/usr/lib/python2.4/site-packages/apt/__init__.py:18: FutureWarning: apt API not stable yet
  warnings.warn("apt API not stable yet", FutureWarning)
current dist not found in meta-release file

(synaptic:26220): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed

(synaptic:26220): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed
evolution-shell-Message: Killing old version of evolution-data-server...
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
--------------------------------------------------
Comment 1 palfrey 2007-10-30 11:26:55 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 402506 ***