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 445911 - crash in Tasks: send / receive emails
crash in Tasks: send / receive emails
Status: RESOLVED DUPLICATE of bug 373699
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 445923 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-06-10 01:35 UTC by victorpopa
Modified: 2007-06-11 11:48 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description victorpopa 2007-06-10 01:35:04 UTC
What were you doing when the application crashed?
send / receive emails


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Murrina-Eternal_Blue
Icon Theme: Fedora

Memory status: size: 106598400 vsize: 106598400 resident: 22650880 share: 16326656 rss: 22650880 rss_rlim: 4294967295
CPU usage: start_time: 1181439140 rtime: 80 utime: 69 stime: 11 cutime:0 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 -1208621344 (LWP 3176)]
[New Thread -1275073648 (LWP 3225)]
[New Thread -1220650096 (LWP 3199)]
(no debugging symbols found)
0x0059a402 in __kernel_vsyscall ()

Thread 1 (Thread -1208621344 (LWP 3176))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 <signal handler called>
  • #5 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #6 ??
    from /lib/libglib-2.0.so.0
  • #7 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #8 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #9 main
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
Loading "installonlyn" plugin
CalDAV Eplugin starting up ...
(evolution:3176): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(evolution:3176): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
** (evolution:3176): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:3176): DEBUG: mailto URL program: evolution
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
(evolution:3176): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(bug-buddy:3229): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(bug-buddy:3229): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
--------------------------------------------------
Comment 1 Akhil Laddha 2007-06-11 04:18:03 UTC
Thanks for the bug report. Unfortunately, that stack trace is not very useful
in determining the cause of the crash. Could you please install some debugging
packages [1] and reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the "details", now
containing way more information. Please copy that stacktrace and paste it as a
comment here.  Thanks!


[1] debugging packages for evolution, evolution-data-server and gtkhtml,
    plus debugging packages for some basic GNOME libs. More details can
    be found here:
    http://live.gnome.org/GettingTraces/DistroSpecificInstructions
Comment 2 Akhil Laddha 2007-06-11 04:20:37 UTC
*** Bug 445923 has been marked as a duplicate of this bug. ***
Comment 3 André Klapper 2007-06-11 11:48:01 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 373699 ***