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 489014 - crash in Tasks: opening the mail program...
crash in Tasks: opening the mail program...
Status: RESOLVED DUPLICATE of bug 364700
Product: evolution
Classification: Applications
Component: Tasks
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-10-22 13:52 UTC by steve
Modified: 2007-10-22 22:28 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description steve 2007-10-22 13:52:30 UTC 
Version: 2.10

What were you doing when the application crashed?
opening the mail program for the first time; after the pigin program opened



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 116916224 vsize: 116916224 resident: 38199296 share: 31244288 rss: 38199296 rss_rlim: 4294967295
CPU usage: start_time: 1193061110 rtime: 35 utime: 30 stime: 5 cutime:1 cstime: 4 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 -1209121056 (LWP 15939)]
[New Thread -1248859248 (LWP 15975)]
[New Thread -1226814576 (LWP 15972)]
(no debugging symbols found)
0x0012d402 in __kernel_vsyscall ()

+ Trace 171947

Thread 1 (Thread -1209121056 (LWP 15939))

  • #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_context_iteration
    from /lib/libglib-2.0.so.0
  • #8 link_main_iteration
    from /usr/lib/libORBit-2.so.0
  • #9 giop_recv_buffer_get
    from /usr/lib/libORBit-2.so.0
  • #10 ORBit_small_invoke_stub
    from /usr/lib/libORBit-2.so.0
  • #11 ORBit_small_invoke_stub_n
    from /usr/lib/libORBit-2.so.0
  • #12 ORBit_c_stub_invoke
    from /usr/lib/libORBit-2.so.0
  • #13 Bonobo_ActivationContext_activateMatchingFull
    from /usr/lib/libbonobo-activation.so.4
  • #14 bonobo_activation_activate
    from /usr/lib/libbonobo-activation.so.4
  • #15 bonobo_activation_activate_from_id
    from /usr/lib/libbonobo-activation.so.4
  • #16 ??
    from /usr/lib/evolution/2.10/components/libevolution-calendar.so
  • #17 ??
    from /lib/libglib-2.0.so.0
  • #18 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #19 ??
    from /lib/libglib-2.0.so.0
  • #20 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #21 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #22 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
localuser:sbaxter being added to access control list
SESSION_MANAGER=local/anaconda5.uml.edu:/tmp/.ICE-unix/15746
CalDAV Eplugin starting up ...
evolution-shell-Message: Killing old version of evolution-data-server...
** (evolution:15939): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:15939): 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
--------------------------------------------------
Comment 1 Tobias Mueller 2007-10-22 22:28:52 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 364700 ***