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 478633 - crash in Evolution: Trying to mark a mail as...
crash in Evolution: Trying to mark a mail as...
Status: RESOLVED DUPLICATE of bug 426496
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-09-20 15:35 UTC by jin2478
Modified: 2007-10-03 00:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description jin2478 2007-09-20 15:35:03 UTC
What were you doing when the application crashed?
Trying to mark a mail as 'junk'


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

System: Linux 2.6.21-2-powerpc #1 Tue Jul 10 19:09:48 CEST 2007 ppc
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 122335232 vsize: 122335232 resident: 34086912 share: 21622784 rss: 34086912 rss_rlim: 4294967295
CPU usage: start_time: 1190302445 rtime: 594 utime: 546 stime: 48 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(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 805592512 (LWP 7464)]
[New Thread 860779728 (LWP 7501)]
[New Thread 859989200 (LWP 7484)]
[New Thread 851600592 (LWP 7483)]
[New Thread 842802384 (LWP 7482)]
[New Thread 823649488 (LWP 7478)]
[New Thread 832038096 (LWP 7477)]
[New Thread 815260880 (LWP 7474)]
(no debugging symbols found)
0x0f1ee5a4 in ?? () from /lib/libpthread.so.0

Thread 1 (Thread 805592512 (LWP 7464))

  • #0 ??
    from /lib/libpthread.so.0
  • #1 ??
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 <signal handler called>
  • #5 ??
  • #6 html_object_get_left_margin
    from /usr/lib/libgtkhtml-3.14.so.19
  • #7 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #8 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #9 html_object_calc_size
    from /usr/lib/libgtkhtml-3.14.so.19
  • #10 html_engine_calc_size
    from /usr/lib/libgtkhtml-3.14.so.19
  • #11 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #12 ??
    from /usr/lib/libglib-2.0.so.0
  • #13 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #14 ??
    from /usr/lib/libglib-2.0.so.0
  • #15 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #16 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #17 main
  • #0 ??
    from /lib/libpthread.so.0


----------- .xsession-errors (863713 sec old) ---------------------
a fatal error in the mono runtime or one of the native libraries 
used by your application.
=================================================================
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
** (xfwm4:2899): CRITICAL **: myDisplayGetClientFromWindow: assertion `w != None' failed
** (xfwm4:2899): CRITICAL **: myDisplayGetScreenFromWindow: assertion `w != None' failed
process 2914: The last reference on a connection was dropped without closing the connection. This is a bug in an application. See dbus_connection_unref() documentation for details.
Most likely, the application was supposed to call dbus_connection_close(), since this is a private connection.
** Message: xfsm-shutdown-helper.c:215: HAL not available or does not permit to shutdown/reboot the computer, trying sudo fallback instead.
(evolution-alarm-notify:2912): evolution-alarm-notify-CRITICAL **: alarm_queue_done: assertion `g_hash_table_size (client_alarms_hash) == 0' failed
--------------------------------------------------
Comment 1 André Klapper 2007-10-03 00:35:53 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 426496 ***